HPE Proliant Servers

carferrari · 21. Juni 2016

Hello,

I'm trying to install OMV 2.1 on a ML110 G9.
Once solved the small problems related to the UEFI bios option, I'm now stuck with the NIC not being recognized.
Based on the official HP specifications, the board is equipped with a Broadcom 5717C0 Dual-port 1Gb.
It seems that the usual tg3.ko module is not supporting this NIC and even the installation of the Debian 7.11 no-free (including firmware) lead to the same result.
Strangely enough, peeking on the HP site, it looks like that the NIC drivers provided for linux (only SLES and RH) still refer to "tg3" (eg:kmod-tg3-3.137m-3.rhel6u7.x86_64.rpm).

any hint?
thank you

OhMyVirtual · 22. Juli 2016

So, I was trying to get OMV installed on a logical array I created (using ACU in ILO) out of 2 SSDs on the Bi20i Embedded RAID controller on my HP Gen8 microserver,
but the OMV install does not see the Logical volume,
it only sees/detects the two separate SSDs.
How do I make OMV install see the Logical Array properly (to install on..) ?

I really prefer to use SATA3 and RAID-1 for the bootdrive, so I don't want to use the extra SATA single drive option.

OhMyVirtual · 22. Juli 2016

Zitat von OhMyVirtual

So, I was trying to get OMV installed on a logical array I created (using ACU in ILO) out of 2 SSDs on the B120i Embedded RAID controller on my HP Gen8 microserver,
but the OMV install does not see the Logical volume,
it only sees/detects the two separate SSDs.
How do I make OMV install see the Logical Array properly (to install on..) ?

I really prefer to use SATA3 and RAID-1 for the bootdrive, so I don't want to use the extra SATA single drive option.

Alles anzeigen

OMG, I see that there are just no debian drivers for the B120i hardware RAID functionality. Geez. Is that still an issue in linux server-world? Why does HP use such obscure hardware then, knowing that would be crap with Debian. https://access.redhat.com/articles/118133

ryecoaaron · 22. Juli 2016

RHEL 7 uses the old 3.10 kernel and maybe the driver hasn't been backported. According to the Debian page, Jessie's 3.16 kernel (same as wheezy's backports 3.16 kernel) supports. With OMV 3.x, you can use the 4.6 backports kernel which should definitely support it. So, you just need to use OMV 3.x.

OhMyVirtual · 22. Juli 2016

But when I use OMV3 will I ever be able to easily update to a stable without having to reinstall the entire OS and plugins? I like to be at the in-place OS upgrade level, like with debian..

Besides, I'd really prefer to use the syncthing multi-user plugin, which is intended for OMV2.*

abpostelnicu · 22. Juli 2016

I guess for the software raid solution like:

B120i or B320i you could try using this version of the driver:

http://downloads.linux.hpe.com/SDR/project/ubuntu-hpdsa/

For me it didn't work since it failed to build module for kernel 4.6

Code

Loading new hpdsa-1.2.6.116d DKMS files...
First Installation: checking all kernels...
Building only for 4.6.0-0.bpo.1-amd64
Building for architecture amd64
Building initial module for 4.6.0-0.bpo.1-amd64
Error! Bad return status for module build on kernel: 4.6.0-0.bpo.1-amd64 (amd64)
Consult /var/lib/dkms/hpdsa/1.2.6.116d/build/make.log for more information.
Creating index of upgradeable packages ...
Creating index of openmediavault plugins ...

and even more info:

Code

DKMS make.log for hpdsa-1.2.6.116d for kernel 4.6.0-0.bpo.1-amd64 (amd64)
Fri Jul 22 16:34:23 EEST 2016
make: Entering directory '/var/lib/dkms/hpdsa/1.2.6.116d/build'
sudo chmod 755 ./build/buildit
KERNEL_PATH=/lib/modules/4.6.0-0.bpo.1-amd64/build BUILD_TYPE=DKMS ./build/buildit
BUILDIT_DIR = /var/lib/dkms/hpdsa/1.2.6.116d/build/./build MODULE_DIR= /var/lib/dkms/hpdsa/1.2.6.116d/build/./build/.. COMPAT_DIR=
Making the hpdsa.ko kernel module
make -j 5 -C /lib/modules/4.6.0-0.bpo.1-amd64/build LSI_FW_FLASH=1 M=/var/lib/dkms/hpdsa/1.2.6.116d/build/./build/.. V=1 FLAVOR=4.6.0-0.bpo.1-amd64 RAIDSTACK_DRIVER=1
make[1]: Entering directory '/usr/src/linux-headers-4.6.0-0.bpo.1-amd64'
make -C /usr/src/linux-headers-4.6.0-0.bpo.1-amd64 KBUILD_SRC=/usr/src/linux-headers-4.6.0-0.bpo.1-common \
-f /usr/src/linux-headers-4.6.0-0.bpo.1-common/Makefile
test -e include/generated/autoconf.h -a -e include/config/auto.conf || (                \
echo >&2;                                                       \
echo >&2 "  ERROR: Kernel configuration is invalid.";           \
echo >&2 "         include/generated/autoconf.h or include/config/auto.conf are missing.";\
echo >&2 "         Run 'make oldconfig && make prepare' on kernel src to fix it.";      \
echo >&2 ;                                                      \
/bin/false)
mkdir -p /var/lib/dkms/hpdsa/1.2.6.116d/build/./build/../.tmp_versions ; rm -f /var/lib/dkms/hpdsa/1.2.6.116d/build/./build/../.tmp_versions/*
make -f /usr/src/linux-headers-4.6.0-0.bpo.1-common/scripts/Makefile.build obj=/var/lib/dkms/hpdsa/1.2.6.116d/build/./build/..
   rm -f /var/lib/dkms/hpdsa/1.2.6.116d/build/./build/../built-in.o; ar rcsD /var/lib/dkms/hpdsa/1.2.6.116d/build/./build/../built-in.o
(cat /dev/null;   echo kernel//var/lib/dkms/hpdsa/1.2.6.116d/build/./build/../hpdsa.ko;) > /var/lib/dkms/hpdsa/1.2.6.116d/build/./build/../modules.order
   gcc-4.9 -Wp,-MD,/var/lib/dkms/hpdsa/1.2.6.116d/build/./build/../.hp_dsa.o.d  -nostdinc -isystem /usr/lib/gcc/x86_64-linux-gnu/4.9/include -I/usr/src/linux-headers-4.6.0-0.bpo.1-common/arch/x86/include -Iarch/x86/include/generated/uapi -Iarch/x86/include/generated  -$
<command-line>:0:1: error: macro names must be identifiers
In file included from /var/lib/dkms/hpdsa/1.2.6.116d/build/./build/../hp_dsa.c:50:0:
/var/lib/dkms/hpdsa/1.2.6.116d/build/./build/../hp_dsa.c: In function 'hpdsa_ahci_request_irq':
/var/lib/dkms/hpdsa/1.2.6.116d/build/./build/../hpdsa_kernel_compat.h:34:38: error: 'IRQF_DISABLED' undeclared (first use in this function)
 #define SATA_MSIX_REQUEST_IRQ_FLAGS (IRQF_DISABLED)
                                      ^
/var/lib/dkms/hpdsa/1.2.6.116d/build/./build/../hp_dsa.c:3111:7: note: in expansion of macro 'SATA_MSIX_REQUEST_IRQ_FLAGS'
       SATA_MSIX_REQUEST_IRQ_FLAGS,
       ^
/var/lib/dkms/hpdsa/1.2.6.116d/build/./build/../hpdsa_kernel_compat.h:34:38: note: each undeclared identifier is reported only once for each function it appears in
 #define SATA_MSIX_REQUEST_IRQ_FLAGS (IRQF_DISABLED)
                                      ^
/var/lib/dkms/hpdsa/1.2.6.116d/build/./build/../hp_dsa.c:3111:7: note: in expansion of macro 'SATA_MSIX_REQUEST_IRQ_FLAGS'
       SATA_MSIX_REQUEST_IRQ_FLAGS,
       ^
/var/lib/dkms/hpdsa/1.2.6.116d/build/./build/../hp_dsa.c: In function 'hpdsa_submit_command':
/var/lib/dkms/hpdsa/1.2.6.116d/build/./build/../hp_dsa.c:4053:15: warning: cast from pointer to integer of different size [-Wpointer-to-int-cast]
  c->busaddr = (u32)c;
               ^
/var/lib/dkms/hpdsa/1.2.6.116d/build/./build/../hp_dsa.c: In function 'hpdsa_map_sg_chain_block':
/var/lib/dkms/hpdsa/1.2.6.116d/build/./build/../hp_dsa.c:4643:14: warning: assignment makes integer from pointer without a cast
   temp64.val = sg_block;
              ^
In file included from /var/lib/dkms/hpdsa/1.2.6.116d/build/./build/../hp_dsa.c:50:0:
/var/lib/dkms/hpdsa/1.2.6.116d/build/./build/../hp_dsa.c: In function 'hpdsa_cache_pci_init':
/var/lib/dkms/hpdsa/1.2.6.116d/build/./build/../hpdsa_kernel_compat.h:857:40: error: 'IRQF_DISABLED' undeclared (first use in this function)
 # define CACHE_MSIX_REQUEST_IRQ_FLAGS (IRQF_DISABLED)
                                        ^
/var/lib/dkms/hpdsa/1.2.6.116d/build/./build/../hp_dsa.c:5314:6: note: in expansion of macro 'CACHE_MSIX_REQUEST_IRQ_FLAGS'
      CACHE_MSIX_REQUEST_IRQ_FLAGS,
      ^
/var/lib/dkms/hpdsa/1.2.6.116d/build/./build/../hp_dsa.c: In function 'hpdsa_sas_adapter_pci_init':
/var/lib/dkms/hpdsa/1.2.6.116d/build/./build/../hpdsa_kernel_compat.h:859:38: error: 'IRQF_DISABLED' undeclared (first use in this function)
 # define SAS_MSIX_REQUEST_IRQ_FLAGS (IRQF_DISABLED)
                                      ^
/var/lib/dkms/hpdsa/1.2.6.116d/build/./build/../hp_dsa.c:5696:7: note: in expansion of macro 'SAS_MSIX_REQUEST_IRQ_FLAGS'
       SAS_MSIX_REQUEST_IRQ_FLAGS,
       ^
/usr/src/linux-headers-4.6.0-0.bpo.1-common/scripts/Makefile.build:296: recipe for target '/var/lib/dkms/hpdsa/1.2.6.116d/build/./build/../hp_dsa.o' failed
make[4]: *** [/var/lib/dkms/hpdsa/1.2.6.116d/build/./build/../hp_dsa.o] Error 1
/usr/src/linux-headers-4.6.0-0.bpo.1-common/Makefile:1446: recipe for target '_module_/var/lib/dkms/hpdsa/1.2.6.116d/build/./build/..' failed
make[3]: *** [_module_/var/lib/dkms/hpdsa/1.2.6.116d/build/./build/..] Error 2
Makefile:146: recipe for target 'sub-make' failed
make[2]: *** [sub-make] Error 2
Makefile:8: recipe for target 'all' failed
make[1]: *** [all] Error 2

Alles anzeigen

ryecoaaron · 22. Juli 2016

Zitat von OhMyVirtual

But when I use OMV3 will I ever be able to easily update to a stable without having to reinstall the entire OS and plugins? I like to be at the in-place OS upgrade level, like with debian..

Yes. OMV 3.x does not know it is beta/stable/etc. So, it is just like updating any other package. Updating from OMV 2.x to 3.x is a much larger upgrade that involves moving from Debian Wheezy to Jessie. If you want to use your raid controller, you pretty much need to use OMV 3.x.

Zitat von abpostelnicu

but what about hp raid plugin?

It was updated for OMV 3.0.25+ about 17 days ago - read

abpostelnicu · 22. Juli 2016

Zitat von ryecoaaron

Yes. OMV 3.x does not know it is beta/stable/etc. So, it is just like updating any other package. Updating from OMV 2.x to 3.x is a much larger upgrade that involves moving from Debian Wheezy to Jessie. If you want to use your raid controller, you pretty much need to use OMV 3.x.
It was updated for OMV 3.0.25+ about 17 days ago - read

I know, that i meant was if it has support for b120i or P222? A link for a tutorial on how to get B120i work on my omv 3.0 setup i have also installed 4.6 kernel.

Thank you

ryecoaaron · 22. Juli 2016

Sorry, I don't have a b120i. So, I can't really help with that. I doubt you will find a tutorial since OMV 3.x hasn't technically been released yet. What isn't working?

abpostelnicu · 22. Juli 2016

i've tried to install the driver that i've posted a couple of posts back and i get the error regarding the kernel missing some include files.

ryecoaaron · 22. Juli 2016

According to what I read, you shouldn't need an external driver. Did you try it without it? What is the output of lspci

abpostelnicu · 22. Juli 2016

yes of course, and it seems 4 independent volumes despite that i've setup only 1 raid 5 volume though hp management interface.

ryecoaaron · 22. Juli 2016

If it sees the drives, then it sounds like the driver is working. Not sure what is wrong in this case.

abpostelnicu · 22. Juli 2016

I think the correct behavior would have been to see only one volume the raid5 one. Anyway if I check the access type for the volumes it is ahci.

ryecoaaron · 22. Juli 2016

I agree that the correct behavior is only seeing one volume (I work on HP DL380s with P410i raid controllers all the time) but you would not see any drives if the proper driver was not loaded. There is no ahci option with the P410i but I am also using SAS drives.

abpostelnicu · 22. Juli 2016

Well the b120i is very different than your pcix card. This is integrated on the mb, and the communication with the chip is done through ahci. That's why I see the drivers.

ryecoaaron · 22. Juli 2016

This seems like more work than it is worth. Why not use mdadm raid for the boot volume? You can use the standard Debian installer to do that and then install OMV on top of that. Very simple. Plus, if the motherboard fails, you could move your setup to another computer. If you use the b120i for raid, you would have to have another b120i based motherboard to recover.

Personally, I don't think the boot volume needs raid as long as you back it up once in a while (backup plugin and cron job).

abpostelnicu · 22. Juli 2016

Yes you are right mdadm is a way better options.
How can I backup my boot partition / using cron tab? Is there a plugin for this?

OhMyVirtual · 22. Juli 2016

Zitat von abpostelnicu

I know, that i meant was if it has support for b120i or P222? A link for a tutorial on how to get B120i work on my omv 3.0 setup i have also installed 4.6 kernel.
Thank you

The P222 is fully supported, for me OMV 2.* showed all Arrays created on the P222 during install of OMV. I have the p222 card added to my Gen8 in the extra PCI-E slot. You could even boot from one of the arrays on that controller if you would want that. An advantage to using the P222 to boot from is that it is blazing fast compared to just AHCI, the ODD-SATA port, USB, SD-card or the B120i controller (even when it would be in RAID 0). The reason I don't want to boot from it, is because I need a really large disk array externally, so my p222 card is already occupied with a lot of other work.

ryecoaaron · 22. Juli 2016

If you install openmediavault-backup (from omv-extras), you can use the command: omv-mkconf backup in a scheduled job (within OMV's web interface) to backup the system drive (rsync files to data drive and makes a copy of mbr and partition table).

Jetzt mitmachen!