lh6000 u3

[Dmitry Melekhov_2]

Hello!

I have two lh6000 u3. I have Suse Linux installed on them. Problem is that after server reset Linux can't boot- during initrd unpacking it founds crc error. Another reset solves problem.
drives are on buil-it netraid afapter.
Looks like problem appear after I
upgraded drives firmware to HP04.

[Greg Carlson]

If this problem started immediately after you had flashed firmware from HP03 to HP04 fw on one or more hard drives you have a few options.

If you only had one hard drive that had that firmware upgrade performed on then boot into ctrl-M and mark it as failed and then attempt to boot back into your NOS and see if the error is resolved. If it is resolved perform a rebuild of the drive that you had marked as failed.

If you had more than one hdd that had the fw upgrade on your choices are limited. Try the above procedure one by one on hard drives that had the fw upgrade. Mark one drive failed and boot to the NOS, if no change go back to ctrl-M and mark that drive back to online and mark the next drive that had the upgrade and so on until all drives that had the fw upgrade have been tested. You can only mark one drive as failed at any one time when trying to boot back to the NOS. This will test if it is one hdd that is causing the problem. Otherwise you are probably looking at reconfiguring the array, initialize the array and restore from backup.

Good luck..

[Dmitry Melekhov_2]

Hello!

I have 2 servers and this probelm is on both.
btw, boot partition is on raid1 drive...

[Arimo Laine_2]

Hello.

Did you update also the server BIOSes and drivers?

Cheers,
Arimo

[Dmitry Melekhov_2]

btw, if system boots it works well.
There is no data corruption, etc...

[Greg Carlson]

Dimitry,

There probably isn't data corruption, but if this started immediately after your fw upgrade it is how the controller is communicating with the hard drives. Whenever you perform a bios or firmware flash there is always a risk that something will happen that will prevent you from booting back to the NOS on the next boot. I know of one time when after a hdd fw flash was performed they had errors booting back to their operating system and the process of marking one of the upgraded hdd's to failed resolved the errors. Just a suggestion..