Proxmox installation on RAID LSI MegaRAID SAS

C

csolano

Renowned Member
Mar 9, 2016
5
0
66
50
Hi all,
i got a Fujitsu Server Primergy RX2520 M1 with a LSI SAS RAID controller.
Model: LSI MegaRAID RAID Ctrl SAS 6G 5/6 512 Mb

I can't install promox on it from an usb stick after set the RAID up from controller bios. Built a RAID 1 with two 300 Gb SAS disks.
The installation process goes on but when 50-60% of packages ares installed the proccess freezes and server restarts. Tried it several times with same result.
- Tried to install Debian 8 (latest version,1st DVD iso from an usb stick) and got the same result.
Tried with advanced installation boot too using dmraid driver: linux /install.amd/vmlinuz video=vesa:ywrap,mtrr vga=788 \ -- quiet dmraid=true
- Tried to install CentOS 7 too (latest version, everyhing iso from CentOS site) and same result.
Tested with dmraid at boot too.
- Tried to install Xen Server 6.2 and installation was successful:
A lspci shows the RAID on Xen Servers as
RAID bus controller: LSI Logic / Symbios Logic MegaRAID SAS 2108 [Liberator] (rev 05)

Left the machine powered on with Xen Server 6.2 and one day after it was freezed.

Should i try any trick to install Proxmox or should it behave normal and recognice the RAID controller without problems and finish the installation?

Could the RAID controller be damaged?. It is new, never used, and the controller bios says that all is ok.
Hope someone has experience with these raid controller and can help me.

Ty very much!.
 
did you update controller firmware to latest version?

I'd test raid controller with livecd (e.g. gparted) and
Code: 
dd if=/dev/sda of=/dev/null bs=1M conv=sync
dd if=/dev/zero of=/dev/sda bs=1M conv=sync
dd if=/dev/sda of=/dev/sda bs=1M conv=sync
if any error then controller is failing.

after that i'd try install proxmox again.
 
  • Like
Reactions: csolano
LiSergey said:
did you update controller firmware to latest version?

I'd test raid controller with livecd (e.g. gparted) and
Code: 
dd if=/dev/sda of=/dev/null bs=1M conv=sync
dd if=/dev/zero of=/dev/sda bs=1M conv=sync
dd if=/dev/sda of=/dev/sda bs=1M conv=sync
if any error then controller is failing.

after that i'd try install proxmox again.
Click to expand...
Will try. Ty very much.
 
same problem on my fujitsu rx2520 m1 with lsi raid5 d2616. the other day i opened a support ticket and fujitsu changed my controller but the problem was the same with the new one, so the controller works properly but i think something is going wrong at kernel level.

debian wheezy instead works fine, i performed an upgrade to jessie and.... the problem appeared again!

obviously unable to obtain usefull support from the vendor, because of the os not certified! tomorrow i will try with red hat 7.2
 
Hi tonix.
We solved the problem upgrading the server bios firmware.
Download the firmware upgrade DVD from support at Fujitsu site. We upgraded it using irmc interface but maybe you can do it booting from a pendrive or DVD device.
 
hi csolano, thanks for your answer! tomorrow i will give it a try, what's your controller model?

thanks

toni
 
LSI MegaRAID RAID Ctrl SAS 6G 5/6 512 Mb
But as I said before, I had to upgrade the motherboard firmware to make it work. Not the raid controller one. BTW I upgraded it too ;-)
 
the firmware upgrade solved the issue!! Thanks a lot

i downloaded the updated motherboard bios from fujitsu and installed from windows because unable to upgrade from irmc, no controller firmware updated or required.

This was the syslog entry before the kernel panic and the automatic reboot of the server:

Mar 28 16:33:11 prx01 kernel: [ 62.021338] {1}[Hardware Error]: Hardware error from APEI Generic Hardware Error Source: 1
Mar 28 16:33:11 prx01 kernel: [ 62.021349] {1}[Hardware Error]: It has been corrected by h/w and requires no further action
Mar 28 16:33:11 prx01 kernel: [ 62.021354] {1}[Hardware Error]: event severity: corrected
Mar 28 16:33:11 prx01 kernel: [ 62.021358] {1}[Hardware Error]: Error 0, type: corrected
Mar 28 16:33:11 prx01 kernel: [ 62.021361] {1}[Hardware Error]: fru_text: CorrectedErr
Mar 28 16:33:11 prx01 kernel: [ 62.021365] {1}[Hardware Error]: section_type: PCIe error
Mar 28 16:33:11 prx01 kernel: [ 62.021369] {1}[Hardware Error]: command: 0x0010, status: 0x0147
Mar 28 16:33:11 prx01 kernel: [ 62.021373] {1}[Hardware Error]: device_id: 0000:00:00.0
Mar 28 16:33:11 prx01 kernel: [ 62.021376] {1}[Hardware Error]: slot: 0
Mar 28 16:33:11 prx01 kernel: [ 62.021380] {1}[Hardware Error]: secondary_bus: 0x00
Mar 28 16:33:11 prx01 kernel: [ 62.021383] {1}[Hardware Error]: vendor_id: 0x1000, device_id: 0x0079
Mar 28 16:33:11 prx01 kernel: [ 62.021387] {1}[Hardware Error]: class_code: 000401

meaning of the error code: 0x0147 Warning Consistency Check started on an inconsistent VD %s
 
tonix said:
the firmware upgrade solved the issue!! Thanks a lot

i downloaded the updated motherboard bios from fujitsu and installed from windows because unable to upgrade from irmc, no controller firmware updated or required.

This was the syslog entry before the kernel panic and the automatic reboot of the server:

Mar 28 16:33:11 prx01 kernel: [ 62.021338] {1}[Hardware Error]: Hardware error from APEI Generic Hardware Error Source: 1
Mar 28 16:33:11 prx01 kernel: [ 62.021349] {1}[Hardware Error]: It has been corrected by h/w and requires no further action
Mar 28 16:33:11 prx01 kernel: [ 62.021354] {1}[Hardware Error]: event severity: corrected
Mar 28 16:33:11 prx01 kernel: [ 62.021358] {1}[Hardware Error]: Error 0, type: corrected
Mar 28 16:33:11 prx01 kernel: [ 62.021361] {1}[Hardware Error]: fru_text: CorrectedErr
Mar 28 16:33:11 prx01 kernel: [ 62.021365] {1}[Hardware Error]: section_type: PCIe error
Mar 28 16:33:11 prx01 kernel: [ 62.021369] {1}[Hardware Error]: command: 0x0010, status: 0x0147
Mar 28 16:33:11 prx01 kernel: [ 62.021373] {1}[Hardware Error]: device_id: 0000:00:00.0
Mar 28 16:33:11 prx01 kernel: [ 62.021376] {1}[Hardware Error]: slot: 0
Mar 28 16:33:11 prx01 kernel: [ 62.021380] {1}[Hardware Error]: secondary_bus: 0x00
Mar 28 16:33:11 prx01 kernel: [ 62.021383] {1}[Hardware Error]: vendor_id: 0x1000, device_id: 0x0079
Mar 28 16:33:11 prx01 kernel: [ 62.021387] {1}[Hardware Error]: class_code: 000401

meaning of the error code: 0x0147 Warning Consistency Check started on an inconsistent VD %s
Click to expand...
Awesome! Glad to hear :-)
 
You must log in or register to reply here.
Top Bottom