cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
Announcements

758
Views
0
Helpful
3
Replies
Highlighted

4RU MSP Server RAID error

Hello everyone,

I booted one of our servers this morning and was greeted with the following mesage:

Press <Ctrl><A> for Adapter RAID Configuration Utility

Controller #00: Host RAID - ESB2 at PCI Bus:00, Dev:1F, Func:02

No logical drives found

No Int 13 Drives to support

Bios not installed!

Not surpisingly it did not boot into SUSE but rather to a command prompt that looks like this:

(none) :/#

Also the following message was displayed right before the POST ended:

fsck.ext2 /dev/disk/by-id/scsi-3600605b001ee7cc014615a2a0b37acaa-part1 failed (status 0x8). Run manually!

Any idea as to what happened and recommendations for a solution?

Thanks.

Everyone's tags (1)
3 REPLIES 3
Cisco Employee

Re: 4RU MSP Server RAID error

The message is from the adaptec onboard raid controller which is not used.  This message is always displayed on boot.  The megaraid controller will ask for to enter the raid utility.

Press for Adapter RAID Configuration Utility

Controller #00: Host RAID - ESB2 at PCI Bus:00, Dev:1F, Func:02

No logical drives found

No Int 13 Drives to support

Bios not installed!

Can you provide further logs after this?  After these logs you should see the LSI raid controller and drives listed.  If not it should at least show some error message related to the controller.

Thanks

Dave Aicher

Re: 4RU MSP Server RAID error

Thanks for the response Dave. I will check it in the morning for the information you requested.

Thanks.

Re: 4RU MSP Server RAID error

David,

Here are the logs after the initial ones I provided:

usbcore: registered new driver hidden

usbcore: regidtered new driver usbhid

drivers/usb/input/mid-core.c: V2.6: USB HID core driver

/sbin/fsck.xfs: XFS file system                                     failed

fasck failed for at least one file system (not /)

Please repair manually and reboot

The root file system is already mounted read-write

Here is some additional information:

The superblock could not be read or does not  describe a correct ext2 file system. If the device

is valid and it really contains ext2 file system (and not swap or ufs or something else), then the

superblock is corrupt and you might try running e2fsck with an alternate superblock:

e2fsck -b 8193

Thanks.

CreatePlease to create content
Content for Community-Ad
August's Community Spotlight Awards
This widget could not be displayed.