Details for PERC 4e/Di ???

Mark Watts m.watts at eris.qinetiq.com
Wed Mar 23 11:36:31 CST 2005


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1


> Hi,
>
> I have a PE2800, has a 'PERC 4e/Di Standard FW 5130' RAID controller card.
> After finishing the install and rebooting I get this:
> sda: asking for cache data failed
> sda: assuming drive cache: write through
>        sda: sda1 sda2 sda3 sda4
> My Linux server was frozen for unknown reason, any idea. ???. iam using
> fedora3 ....
>
> More details:
>
> I installed Fedora Core 3 on a Dell Poweredge 2800.  The Dell has a 'PERC
> 4e/Di Standard FW 5130' RAID controller card. The install went well--no
> problems.  However, after finishing the install and rebooting I get this:
> *****************
> SCSI subsystem initialized
> megaraid cmm: 2.20.2.0 (Release Date: Thu Aug 19 09:58:33 EDT 2004)
> megaraid: 2.20.4.0 (Release Date: Mon Sep 27 22:15:07 EDT 2004)
> megaraid: probe new device 0x1028:0x0013:0x1028:0x016e: bus 2:slot 14:func
> 0 ACPI: PCI interrupt 0000:02:0e.0[A] -> GSI 46 (level, low) -> IRQ 201
> megaraid: fw version:[513O] bios version:[H418]
> scsi0 : LSI Logic MegaRAID driver
> scsi[0]: scanning scsi channel 0 [Phy 0] for non-raid devices
> scsi[0]: scanning scsi channel 1 [Phy 1] for non-raid devices
>   Vendor: PE/PV     Model: 1x8 SCSI BP       Rev: 1.0
>   Type:   Processor                          ANSI SCSI revision: 02
> scsi[0]: scanning scsi channel 2 [virtual] for logical drives
>   Vendor: MegaRAID  Model: LD 0 RAID5  139G  Rev: 513O
>   Type:   Direct-Access                      ANSI SCSI revision: 02
> SCSI device sda: 286228480 512-byte hdwr sectors (146549 MB)
> sda: asking for cache data failed
> sda: assuming drive cache: write through
>  sda: sda1 sda2 sda3 sda4
> Attached scsi disk sda at scsi0, channel 2, id 0, lun 0
> EXT3-fs: INFO: recovery required on readonly filesystem.
> EXT3-fs: write access will be enabled during recovery.
> kjournald starting.  Commit interval 5 seconds
> EXT3-fs: sda4: orphan cleanup on readonly fs
> ext3_orphan_cleanup: deleting unreferenced inode 4878318
> EXT3-fs: sda4: 1 orphan inode deleted
> EXT3-fs: recovery complete.
> EXT3-fs: mounted files

The fact that you got past detecting the raid devices and got stuck somewhere 
in/after the partition mounting suggests that it may not be a fault of the 
megaraid2 driver.

I have to admit that I've never used a 4e/Di, only a 4e/Si so I don't know how 
much they differ in driver requirements.

Mark.


- -- 
Mark Watts
Senior Systems Engineer
QinetiQ Trusted Information Management
Trusted Solutions and Services Group
GPG Public Key ID: 455420ED

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)

iD8DBQFCQakjBn4EFUVUIO0RAmW0AJ9p3Akb99VWinM51gGpsjSJmDZXiACdGU2L
MkgPNc5YJFFcY4qO5er9xAg=
=t1jX
-----END PGP SIGNATURE-----




More information about the Linux-PowerEdge mailing list