HPE Proliant Servers

  • Hi,


    Just received my Gen8.
    I planned to install OMV on SSD, and use ODD sata, but after some research this morning, it seems impossible to properly boot from port5.
    My data disks will not be in a RAID (I'm using snapraid), and forcing SSD boot with raid 0 trick is not reliable for me, if a reboot / cold boot is not possible.


    So what are the possible solutions ?

    • install omv on USB (+SSD for data)?
    • install omv on sd card (+SSD for data)?
    • use USB only for boot partition, and keep other installation partitions on SSD ?

    Thanks

  • I would definitely advice third option:
    "use USB only for boot partition, and keep other installation partitions on SSD(on ODD/5th port)

    Hi,
    Connect only your SSD on your Gen8, then, activate in Bios, AHCI (not raid).
    Install OMV on the SSD. Restart.
    After that, OMV will boot on your SSD, without volume raid. Then, with OMV you will be able to create your volume.

    U are not saying where to put ssd :(1) 5th port or (2)front hdd bay?


    1. this option shall work BUT ONLY PARTLY!!!
    Wherever it is needed a reset(bootup)(becouse of reason of whatsoever) of Gen8,
    he NEEDS to get HDD`s OUT of front bay`s before of bootup!!!
    Otherways it will NOT bootup.


    Therefor is boot(grub) on usb stick is needed!!!


    2.That is possible and easy way. Bad side of it is,that he( Mika91) cannot use ssd for more use(saveing) of data on ssd.
    AND the most important, he is LoosinG one bay a front/ in start.

  • On my Gen8, i made 2 different setups from scratch.


    1st one, with 4 x 4 TB HDD connected on 1.2.3.4 th port, and 1 SSD (5th port, instead of CD/DVD drive). => OMV2, then OMV3 upgrade. Works fine.


    2nd setup, with HP smartarray p410 card, and 4 HDD connected on it with miniSAS/SATA cables. The Same SSD but this time, connected on 1st SATA port of Motherboard. Works fine too.

  • Hello me again...


    Can someone tell me or explain to me some unortodox mystery that hunts from this morning.


    I have HP proliant Gen8 microserver.
    One or two years ago i installed Omv on HP with ODD/5th sta port and Grub on intern usb port.
    Because of some amateur handeling i needed to reinstall. That went without a problem two day`s ago.
    Till then i was preoccupied with copying grub on usb.
    This morning i discovered that Omv on ODD and 3 hdd`s(1,2,4port) is BOOTING UP without problem ?!?!
    Same OMV3...etc.


    One of the few "wtf" moments in my life!


    Can someone explain please (just do not say "that`s a job of Gremlins) ???

  • This seems to be rather a long thread!! Having got hold of a Gen7 N54L I starting searching for some sort of sensor monitoring, I came across this which lead onto this and from the first link led me to this


    Has anyone installed these? I have installed lm-sensors but that just displays

    Code
    k10temp-pci-00c3
    Adapter: PCI adapter
    temp1: +30.1°C (high = +70.0°C)
    (crit = +100.0°C, hyst = +95.0°C)

    Further information is here once installed those drivers will display more information.

  • i have a proliant dl160 gen 6 that i am trying to use omv with and have the OS on a 32gb flashdrive. and there are no drives set up in the raid config at boot and when i go to the web config after the server boots up, i have no ability to see any drives in there. does the gen 6 server not have the ability to use the raid card directly with omv

  • i have no ability to see any drives in there. does the gen 6 server not have the ability to use the raid card directly with omv

    Put simply no, you'll need to change the bios settings, disable the raid option in the bios and set it to something like AHCI. OMV does not support hardware raid out of the box, it will require a driver and the option enable hardware raid. But, doing that, if it works, OMV will see your drives as one and you have no way of monitoring the raid itself.

  • Put simply no, you'll need to change the bios settings, disable the raid option in the bios and set it to something like AHCI. OMV does not support hardware raid out of the box, it will require a driver and the option enable hardware raid. But, doing that, if it works, OMV will see your drives as one and you have no way of monitoring the raid itself.

    so i need to go into the bios and change from raid to ahci? and this will give omv the ability to control the raid card, or it just isnt possible with my current server?

  • so i need to go into the bios and change from raid to ahci? and this will give omv the ability to control the raid card, or it just isnt possible with my current server?

    Having searched for that particular server, it has a P410 raid card, which is a dedicated raid card to get that server to work with OMV you'll need an HBA card something like a Dell PERC H200 or H310 flashed to IT mode.

  • Having searched for that particular server, it has a P410 raid card, which is a dedicated raid card to get that server to work with OMV you'll need an HBA card something like a Dell PERC H200 or H310 flashed to IT mode.

    so i need to go into the bios and change from raid to ahci? and this will give omv the ability to control the raid card, or it just isnt possible with my current server?

    With that card, you either have to let it create the raid array and OMV will see one drive -OR- you have to create a single drive raid 0 array for each drive (I know it sounds terrible). Otherwise, you will have to go with geaves idea.

    omv 5.5.9 usul | 64 bit | 5.4 proxmox kernel | omvextrasorg 5.3.6
    omv-extras.org plugins source code and issue tracker - github


    Please read this before posting a question.
    Please don't PM for support... Too many PMs!

  • Hello,


    I come to you to understand and find a solution.


    I have a HP DL380e G8. After several unsuccessful installation attempts, I managed to install OVM 4 via an SSD in a USB external box. I tried to reinstall OMV4 after a bad handling making the system unstable and I find myself with the same problem. Namely after the installation of OMV succeeded and reboot to restart on the disk, it does not find a bootable disk.


    I had managed to solve this problem by going through a SSD in usb, but this solution seems to no longer work for no apparent reason.



    For information during the installation and boot no disk except the SSD are connected.



    Similarly in order to have a transparent view on the RAID, I have the p420 RAID card in HBA mode.




    P.S:Here are also the topics that I had created so that you have more information on the configuration and advice / solutions that I had already been told.


    28351-OMV-and-Raid-controller/?postID=212206#post212206
    28468-no-bootable-disk-after-installation/?postID=212314#post212314

  • I'm using P420 and P822 in my all NASes and I have no problem running OMV with them.
    They run in proper RAID mode and are not flashed to IT (HBA) mode.


    On one server I have a P420 with 4 SSDs attached (2 Raid-1 for OS and 2 Raid-1 for VirtualBox and Docker), then I have the data drives on a dedicated disk shelf connected to the P822.
    On the other I have a P420 with a 2 SSD (Raid-1 for OS, swap and Docker) and then 4 WD RED drives.


    I have had no problems what-so-ever with these raid card as the P-series HP raid cards are fully open source and the drivers have been built-in the kernel for a long time.
    That doesn't hold true for the H-series that are HBA only.

  • My OMV boot concerns are not related to my p420 RAID card. I have it in my message to give you more details.


    Why did I go on the HBA mode? I wanted to have a "NAS" with a fairly large storage capacity (about 44TB).Having a fairly fast configuration and with a lot of ram, I thought to move to 2 array of 7 disks 4TB in RAIDZ.


    For that I need that the OS can handle the RAID and at the same time a machine with more than 8 sata are rare and it is often the machines with RAID cards that manage that, the card raid was therefore logical choice.



    In my previous test, I realized that even when trying to install DEBIAN on the machine, the drive was not recognized as bootable.
    After having successfully used an externally connected USB SSD which had solved my concerns, I find myself again with an unrecognized disk at boot time.


    What I would like to find and understand with your help is why it is not recognized as bootable when it has already been. I did different tests with different settings in the bios no change.


    The only difference between my current attempt and the previous one is that I remember that during my attempts, OMV could not partition the SSD, after a partition deletion and formatting in FAT from my PC, I I try to install it again and it works. I will try to do this again and keep you informed.



    I hope that from your side you can give me some tracks too.


    EDIT:
    I just deleted the partitions and format the SSD, successfully installed again successfully, and then the server did not find a bootable disk.
    it is to believe that GRUB does not settle or installs in the wrong place or badly. I can not understand why I have succeeded 1 time and nothing since.

  • You need to possibly update grub, do you install from USB or CD

    I had already thought about this possibility, looking at the documentation, it is besides that that the idea of installing debian at first metait came and made it possible to see that I had the same worries of boot . that's also why I said "as if" because it does not seem to come from grub.


    Regarding the grub, it is present on the disc. here are 2 screenshots, one showing that grub is installed on the SSD, and a second showing the result of a "parted" to verify that the SSD includes a boot part.


    If you need, I can send you the grub file



    Capture_du_2019-09-27_17-48-53.png



    Capture_du_2019-09-27_17-48-18.png

  • Namely after the installation of OMV succeeded and reboot to restart on the disk, it does not find a bootable disk.

    The only reason I asked was from the above, that implies you used a USB flash drive for the install and the outcome therefore is correct. Grub expects to find the install drive and not the drive OMV has been installed on. This post and thread might be of some help

Participate now!

Don’t have an account yet? Register yourself now and be a part of our community!