Good day gentlemen. Please help with LEAP 15.1 installing. I have a HP proliant with P400 smart array controller. This controller does not have a hpsa support. On preiveous version of SUSE 42.2 I use kernel command “cciss.cciss_allow_hpsa=0” and installing was successful.
So, can you help me with install SUSE 15.1
The following is a recent article which at the bottom includes an option to try to use the cciss driver. Although for RHEL, looks to me it might also work on other distros including openSUSE.
Unsupported, but if it works, why not?
https://access.redhat.com/solutions/874443
Also,
As should be expected, it’s important to understand if your storage array is recognized on POST or not. And accordingly, you should be certain your BIOS firmware has been updated to the latest possible.
You didn’t post your Proliant model,
But you can use the following hp forums thread as a guide… although it’s for a Windows machine, the parts that relate to POST should apply no matter the OS.
HTH,
TSU
According to these commits, hpsa should support everything cciss supported. If it does not work for you, open bug report:
commit c8cd71f1f32a6227ecadbbbaaf3147a41292ecb5Author: Hannes Reinecke <hare@suse.de>
Date: Tue Aug 15 08:58:09 2017 +0200
scsi: hpsa: Remove 'hpsa_allow_any' module option
As the cciss driver has been removed there are no overlapping
PCI IDs anymore, and the 'hpsa_allow_any' flag can be removed.
Signed-off-by: Hannes Reinecke <hare@suse.com>
Signed-off-by: Martin K. Petersen <martin.petersen@oracle.com>
commit 253d2464df446456c0bba5ed4137a7be0b278aa8
Author: Hannes Reinecke <hare@suse.de>
Date: Tue Aug 15 08:58:08 2017 +0200
scsi: cciss: Drop obsolete driver
The hpsa driver now has support for all boards the cciss driver
used to support, so this patch removes the cciss driver and
make hpsa an alias to cciss.
Signed-off-by: Hannes Reinecke <hare@suse.com>
Acked-by: Don Brace <don.brace@microsemi.com>
Signed-off-by: Martin K. Petersen <martin.petersen@oracle.com>
You didn’t post your Proliant model
The model is ProLiant BL460c G1 with HP StorageWorks SB40c
Although for RHEL, looks to me it might also work on other distros including openSUSE.
kernel (4.12) command hpsa.hpsa_allow_any=1 - No results, but if I make a start system with kernel 4.4 (with command cciss.cciss_allow_hpsa=0)- system run properly
Hi
That option is no longer present in the kernel module;
/sbin/modinfo hpsa |grep parm:
parm: hpsa_simple_mode
This is storage blade, not RAID controller. According to information on HP site, it includes Smart Array P400, which should be supported by hpsa.
Yes Smart Array P400 (see first topic),
It’s a good news! but why then the kernel 4.12 does not detect controller? but 4.4 works
There is no information to even start to guess. Show at least dmesg output when driver fails to detect controller as well as “lspci -mmnn” output.
00:00.0 “Host bridge [0600]” “Intel Corporation [8086]” “5000P Chipset Memory Controller Hub [25d8]” -rb1 “Hewlett-Packard Company [103c]” “Device [31fd]”
00:02.0 “PCI bridge [0604]” “Intel Corporation [8086]” “5000 Series Chipset PCI Express x4 Port 2 [25e2]” -rb1 “” “”
00:03.0 “PCI bridge [0604]” “Intel Corporation [8086]” “5000 Series Chipset PCI Express x4 Port 3 [25e3]” -rb1 “” “”
00:04.0 “PCI bridge [0604]” “Intel Corporation [8086]” “5000 Series Chipset PCI Express x4 Port 4 [25e4]” -rb1 “” “”
00:05.0 “PCI bridge [0604]” “Intel Corporation [8086]” “5000 Series Chipset PCI Express x4 Port 5 [25e5]” -rb1 “” “”
00:06.0 “PCI bridge [0604]” “Intel Corporation [8086]” “5000 Series Chipset PCI Express x4 Port 6 [25e6]” -rb1 “” “”
00:07.0 “PCI bridge [0604]” “Intel Corporation [8086]” “5000 Series Chipset PCI Express x4 Port 7 [25e7]” -rb1 “” “”
00:10.0 “Host bridge [0600]” “Intel Corporation [8086]” “5000 Series Chipset FSB Registers [25f0]” -rb1 “Hewlett-Packard Company [103c]” “ProLiant DL140 G3 [31fd]”
00:10.1 “Host bridge [0600]” “Intel Corporation [8086]” “5000 Series Chipset FSB Registers [25f0]” -rb1 “Hewlett-Packard Company [103c]” “ProLiant DL140 G3 [31fd]”
00:10.2 “Host bridge [0600]” “Intel Corporation [8086]” “5000 Series Chipset FSB Registers [25f0]” -rb1 “Hewlett-Packard Company [103c]” “ProLiant DL140 G3 [31fd]”
00:11.0 “Host bridge [0600]” “Intel Corporation [8086]” “5000 Series Chipset Reserved Registers [25f1]” -rb1 “Hewlett-Packard Company [103c]” “ProLiant DL140 G3 [31fd]”
00:13.0 “Host bridge [0600]” “Intel Corporation [8086]” “5000 Series Chipset Reserved Registers [25f3]” -rb1 “Hewlett-Packard Company [103c]” “ProLiant DL140 G3 [31fd]”
00:15.0 “Host bridge [0600]” “Intel Corporation [8086]” “5000 Series Chipset FBD Registers [25f5]” -rb1 “Hewlett-Packard Company [103c]” “ProLiant DL140 G3 [31fd]”
00:16.0 “Host bridge [0600]” “Intel Corporation [8086]” “5000 Series Chipset FBD Registers [25f6]” -rb1 “Hewlett-Packard Company [103c]” “ProLiant DL140 G3 [31fd]”
00:1c.0 “PCI bridge [0604]” “Intel Corporation [8086]” “631xESB/632xESB/3100 Chipset PCI Express Root Port 1 [2690]” -r09 “” “”
00:1d.0 “USB controller [0c03]” “Intel Corporation [8086]” “631xESB/632xESB/3100 Chipset UHCI USB Controller #1 [2688]” -r09 “Hewlett-Packard Company [103c]” “ProLiant DL140 G3 [31fe]”
00:1d.1 “USB controller [0c03]” “Intel Corporation [8086]” “631xESB/632xESB/3100 Chipset UHCI USB Controller #2 [2689]” -r09 “Hewlett-Packard Company [103c]” “ProLiant DL140 G3 [31fe]”
00:1d.2 “USB controller [0c03]” “Intel Corporation [8086]” “631xESB/632xESB/3100 Chipset UHCI USB Controller #3 [268a]” -r09 “Hewlett-Packard Company [103c]” “ProLiant DL140 G3 [31fe]”
00:1d.3 “USB controller [0c03]” “Intel Corporation [8086]” “631xESB/632xESB/3100 Chipset UHCI USB Controller #4 [268b]” -r09 “Hewlett-Packard Company [103c]” “Device [31fe]”
00:1d.7 “USB controller [0c03]” “Intel Corporation [8086]” “631xESB/632xESB/3100 Chipset EHCI USB2 Controller [268c]” -r09 -p20 “Hewlett-Packard Company [103c]” “ProLiant DL140 G3 [31fe]”
00:1e.0 “PCI bridge [0604]” “Intel Corporation [8086]” “82801 PCI Bridge [244e]” -rd9 -p01 “” “”
00:1f.0 “ISA bridge [0601]” “Intel Corporation [8086]” “631xESB/632xESB/3100 Chipset LPC Interface Controller [2670]” -r09 “” “”
01:03.0 “VGA compatible controller [0300]” “Advanced Micro Devices, Inc. [AMD/ATI] [1002]” “ES1000 [515e]” -r02 “Hewlett-Packard Company [103c]” “Device [31fb]”
01:04.0 “System peripheral [0880]” “Compaq Computer Corporation [0e11]” “Integrated Lights Out Controller [b203]” -r03 “Hewlett-Packard Company [103c]” “Device [3305]”
01:04.2 “System peripheral [0880]” “Compaq Computer Corporation [0e11]” “Integrated Lights Out Processor [b204]” -r03 “Hewlett-Packard Company [103c]” “Device [3305]”
01:04.4 “USB controller [0c03]” “Hewlett-Packard Company [103c]” “Integrated Lights-Out Standard Virtual USB Controller [3300]” “Hewlett-Packard Company [103c]” “iLO2 [3305]”
01:04.6 “IPMI SMIC interface [0c07]” “Hewlett-Packard Company [103c]” “Integrated Lights-Out Standard KCS Interface [3302]” -p01 “Hewlett-Packard Company [103c]” “iLO2 [3305]”
02:00.0 “PCI bridge [0604]” “Broadcom [1166]” “EPB PCI-Express to PCI-X Bridge [0103]” -rc3 “” “”
03:00.0 “Ethernet controller [0200]” “Broadcom Limited [14e4]” “NetXtreme II BCM5708S Gigabit Ethernet [16ac]” -r12 “Hewlett-Packard Company [103c]” “NC373i Integrated Multifunction Gigabit Server Adapter [703b]”
04:00.0 “PCI bridge [0604]” “Intel Corporation [8086]” “6311ESB/6321ESB PCI Express Upstream Port [3500]” -r01 “” “”
04:00.3 “PCI bridge [0604]” “Intel Corporation [8086]” “6311ESB/6321ESB PCI Express to PCI-X Bridge [350c]” -r01 “” “”
05:00.0 “PCI bridge [0604]” “Intel Corporation [8086]” “6311ESB/6321ESB PCI Express Downstream Port E1 [3510]” -r01 “” “”
05:01.0 “PCI bridge [0604]” “Intel Corporation [8086]” “6311ESB/6321ESB PCI Express Downstream Port E2 [3514]” -r01 “” “”
06:00.0 “PCI bridge [0604]” “Broadcom [1166]” “EPB PCI-Express to PCI-X Bridge [0103]” -rc3 “” “”
07:00.0 “Ethernet controller [0200]” “Broadcom Limited [14e4]” “NetXtreme II BCM5708S Gigabit Ethernet [16ac]” -r12 “Hewlett-Packard Company [103c]” “NC373i Integrated Multifunction Gigabit Server Adapter [703b]”
0a:00.0 “PCI bridge [0604]” “Broadcom [1166]” “EPB PCI-Express to PCI-X Bridge [0103]” -rb4 “” “”
0b:04.0 “PCI bridge [0604]” “Broadcom [1166]” “BCM5785 [HT1000] PCI/PCI-X Bridge [0104]” -rb2 “” “”
0b:08.0 “RAID bus controller [0104]” “Hewlett-Packard Company [103c]” “Smart Array E200i (SAS Controller) [3238]” “Hewlett-Packard Company [103c]” “Smart Array E200i [3211]”
0d:00.0 “RAID bus controller [0104]” “Hewlett-Packard Company [103c]” “Smart Array Controller [3230]” -r03 “Hewlett-Packard Company [103c]” “P400 SAS Controller [3234]”
Sorry, but dmesg output very big to add here
DropMeFiles – free one-click file sharing service - dmesg output in attached file
Please use suspaste.org, not third party sites full of advertisements.
2.319512] hpsa 0000:0b:08.0: legacy board ID: 0x3211103c 2.319533] hpsa 0000:0b:08.0: legacy board ID: 0x3211103c
2.319768] hpsa 0000:0b:08.0: Physical aborts not supported
2.319769] hpsa 0000:0b:08.0: Logical aborts not supported
2.319771] hpsa 0000:0b:08.0: HP SSD Smart Path aborts not supported
2.404181] scsi host0: hpsa
2.404276] hpsa can't handle SMP requests
2.471778] hpsa 0000:0b:08.0: scsi 0:0:0:0: masked Direct-Access HP DG146A3516 PHYS DRV SSDSmartPathCap- En- Exp=0
2.471783] hpsa 0000:0b:08.0: scsi 0:0:1:0: masked Direct-Access HP DG146A3516 PHYS DRV SSDSmartPathCap- En- Exp=0
2.471786] hpsa 0000:0b:08.0: scsi 0:1:0:0: added Direct-Access HP LOGICAL VOLUME RAID-1(+0) SSDSmartPathCap- En- Exp=1
2.471788] hpsa 0000:0b:08.0: scsi 0:3:0:0: added RAID HP E200i controller SSDSmartPathCap- En- Exp=1
Here is your first RAID controller with disks
2.473625] hpsa 0000:0d:00.0: legacy board ID: 0x3234103c
2.473633] hpsa 0000:0d:00.0: legacy board ID: 0x3234103c
2.473636] hpsa 0000:0d:00.0: can't disable ASPM; OS doesn't have ASPM control
2.473904] hpsa 0000:0d:00.0: Physical aborts not supported
2.473906] hpsa 0000:0d:00.0: Logical aborts not supported
2.473908] hpsa 0000:0d:00.0: HP SSD Smart Path aborts not supported
And here is your P400. So far it looks like there are no disks connected to P400. If you have evidences that it is not the case (like dmesg from previous version that shows disks connected to it) you should open bug report.
There is no indication that this is related to alleged hpsa issue. Systemd fails to find swap by UUID. The most obvious explanation is that you recreated swap that changed its UUID. Check with blkid current value and update /etc/fstab if necessary.
The dmesg output (kernel 4.4.180-102) on the same server use parameter cciss.cciss_allow_hpsa=0. The 6 hard disk in raid connected to P400 controller and work properly. If the parameter is not included on 4.4 - the same problem
0.000000] Command line: BOOT_IMAGE=/boot/vmlinuz-4.4.180-102-default root=UUID=ab2e6183-d2ce-4425-8520-327710a282e8 cciss.cciss_allow_hpsa=0 resume=/dev/disk/by-uuid/fee52b59-38ce-4ab1-9286-eec9c1bb2421 splash=silent quiet showopts
0.000000] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-4.4.180-102-default root=UUID=ab2e6183-d2ce-4425-8520-327710a282e8 cciss.cciss_allow_hpsa=0 resume=/dev/disk/by-uuid/fee52b59-38ce-4ab1-9286-eec9c1bb2421 splash=silent quiet showopts
2.504118] cciss 0000:0b:08.0: cciss0: <0x3238> at PCI 0000:0b:08.0 IRQ 25 using DAC
2.515995] cciss/c0d0: p1 p2
2.516782] scsi host0: cciss
2.518668] cciss 0000:0d:00.0: can't disable ASPM; OS doesn't have ASPM control
2.636149] cciss 0000:0d:00.0: cciss1: <0x3230> at PCI 0000:0d:00.0 IRQ 26 using DAC
2.662850] cciss/c1d0: p1
2.663211] scsi host1: cciss
3.367565] BTRFS: device fsid ab2e6183-d2ce-4425-8520-327710a282e8 devid 1 transid 1885147 /dev/cciss/c0d0p1
3.367725] BTRFS: device fsid 0e31ee92-288b-4a21-ab56-2f2a74d0e69a devid 1 transid 1786809 /dev/cciss/c1d0p1
3.480364] BTRFS info (device cciss/c0d0p1): disk space caching is enabled
3.480368] BTRFS info (device cciss/c0d0p1): has skinny extents
3.688104] clocksource: Switched to clocksource tsc
4.078082] systemd-journald[136]: Received SIGTERM from PID 1 (systemd).
4.212218] systemd: 22 output lines suppressed due to ratelimiting
5.037148] random: nonblocking pool is initialized
5.148971] systemd[1]: RTC configured in localtime, applying delta of 180 minutes to system time.
6.472225] BTRFS info (device cciss/c0d0p1): disk space caching is enabled
8.228956] Adding 6303740k swap on /dev/cciss/c0d0p2. Priority:-1 extents:1 across:6303740k FS
8.232420] gpio_ich: ACPI BAR is unavailable, GPI 0 - 15 unavailable
8.232546] gpio_ich: GPIO from 462 to 511 on gpio_ich
8.341900] EDAC MC: Ver: 3.0.0
8.412294] [drm] Initialized drm 1.1.0 20060810
8.424796] BTRFS info (device cciss/c1d0p1): disk space caching is enabled
745.282301] BTRFS info (device cciss/c0d0p1): qgroup scan completed (inconsistency flag cleared)
[12631.470469] perf interrupt took too long (5261 > 2500), lowering kernel.perf_event_max_sample_rate to 50000
[12632.390424] perf interrupt took too long (5259 > 5000), lowering kernel.perf_event_max_sample_rate to 25000
So, if I made a new install 15.1 the P400 controller does not displayed when marking up the hard drive
fdisk output on kernel 4.4
Диск /dev/cciss/c0d0: 136,7 GiB, 146778685440 байт, 286677120 секторов
Disk model: LOGICAL VOLUME
Единицы: секторов по 1 * 512 = 512 байт
Размер сектора (логический/физический): 512 байт / 512 байт
Размер I/O (минимальный/оптимальный): 512 байт / 512 байт
Тип метки диска: dos
Идентификатор диска: **0x402b8cfb**
Устр-во Загрузочный начало Конец Секторы Размер Идентификатор Тип
**/dev/cciss/c0d0p1 * 2048 274069503 274067456 130,7G 83 Linux
/dev/cciss/c0d0p2 274069504 286676991 12607488 6G 82 Linux своп / Solaris**
Диск /dev/cciss/c1d0: 410,1 GiB, 440345714688 байт, 860050224 секторов
Disk model: LOGICAL VOLUME
Единицы: секторов по 1 * 512 = 512 байт
Размер сектора (логический/физический): 512 байт / 512 байт
Размер I/O (минимальный/оптимальный): 512 байт / 512 байт
Тип метки диска: dos
Идентификатор диска: **0x59555f57**
Устр-во Загрузочный начало Конец Секторы Размер Идентификатор Тип
**/dev/cciss/c1d0p1 2048 860049407 860047360 410,1G 83 Linux**
Thanks guys. Problem was solved by SERVER Firmware update.
Тип метки диска: dos
“Disk label type: dos” - this is not good.
Expected: gpt.
Maybe it is better to reinstall OS with reformatting a drives.
Don’t think DOS format supports over 2 TB drives. Main reason GPT was invented
Very large drives are supported, but there are limitations to the file system objects (and files).
So, for instance on a multi-terrabyte drive a DOS partition is perfectly fine for a partition that contains only the bootloader, and DOS is pretty much a universally recognized and supported file format.
TSU
Thank you very much for your attention, but in the near future I do not think to extend disk size. Therefore, it makes no sense to change.