Critical hardware error with Perc4e/DC controller on PowerEdge 850

Harald_Jensas at Dell.com Harald_Jensas at Dell.com
Fri Apr 21 03:44:37 CDT 2006


> -----Original Message-----
> From: linux-poweredge-bounces at dell.com 
> [mailto:linux-poweredge-bounces at dell.com] On Behalf Of Michael Stucki
> Sent: 21 April 2006 10:35
> To: linux-poweredge-Lists
> Subject: Critical hardware error with Perc4e/DC controller on 
> PowerEdge 850
> 
> Hi folks,
> 
> I'm having a serious problem on a fresh Dell PowerEdge 850 
> system. After working for a while, the system reports 
> problems with the RAID controller (see below).
> 
> Further operation is not possible until I perform a hard 
> reset of the system.
> 
> I have searched a lot on several websites as well as this 
> mailing list archive. Although I found the problem described 
> in several places, it should not occur with my Perc4e/DC 
> controller and the firmware version I am using (521X).
> 
> Currently I'm using a Debian Sarge system with Linux 2.6.16.9 
> but the same problem already appeared with a 2.4.31 kernel 
> which I used to initially setup the system.
> 
> Below is a copy of the logfile output (copied via SSH 
> cut/paste since the logs can't be written on the HD anymore).
> 
> Thanks for any help.
> - michael
> 
> megaraid: aborting-4544 cmd=2a <c=2 t=0 l=0> megaraid abort: 
> 4544:31[255:128], fw owner [...]
> megaraid: 2 outstanding commands. Max wait 180 sec megaraid 
> mbox: Wait for 2 commands to complete:180 megaraid mbox: Wait 
> for 2 commands to complete:175 [...] megaraid mbox: Wait for 
> 2 commands to complete:0 megaraid mbox: critical hardware error!
> megaraid: hw error, cannot reset
> megaraid: hw error, cannot reset
> sd 2:2:0:0: scsi: Device offlined - not ready after error 
> recovery sd 2:2:0:0: SCSI error: return code = 0x50000
> end_request: I/O error, dev sda, sector 4686096 Buffer I/O 
> error on device sda3, logical block 71682 lost page write due 
> to I/O error on sda3 [...] sd 2:2:0:0: rejecting I/O to 
> offline device [...] Aborting journal on device sda6.
> sd 2:2:0:0: rejecting I/O to offline device Aborting journal 
> on device sda3.
> EXT3-fs error (device sda6) in ext3_reserve_inode_write: 
> Journal has aborted sd 2:2:0:0: rejecting I/O to offline 
> device EXT3-fs error (device sda6) in ext3_dirty_inode: 
> Journal has aborted sd 2:2:0:0: rejecting I/O to offline 
> device [...] journal commit I/O error ext3_abort called.
> EXT3-fs error (device sda3): ext3_journal_start_sb: Detected 
> aborted journal Remounting filesystem read-only ext3_abort called.
> EXT3-fs error (device sda6): ext3_journal_start_sb: Detected 
> aborted journal Remounting filesystem read-only journal 
> commit I/O error sd 2:2:0:0: rejecting I/O to offline device 
> EXT3-fs error (device sda6): ext3_find_entry: reading 
> directory #4194340 offset 0 sd 2:2:0:0: rejecting I/O to 
> offline device EXT3-fs error (device sda6): ext3_find_entry: 
> reading directory #4194334 offset 1 sd 2:2:0:0: rejecting I/O 
> to offline device sd 2:2:0:0: rejecting I/O to offline device 
> EXT3-fs error (device sda6): ext3_find_entry: reading 
> directory #4194351 offset 0 sd 2:2:0:0: rejecting I/O to 
> offline device EXT3-fs error (device sda6): 
> ext3_get_inode_loc: unable to read inode block - 
> inode=4194411, block=8388632 sd 2:2:0:0: rejecting I/O to 
> offline device sd 2:2:0:0: rejecting I/O to offline device
> 
> _______________________________________________
> Linux-PowerEdge mailing list
> Linux-PowerEdge at dell.com
> http://lists.us.dell.com/mailman/listinfo/linux-poweredge
> Please read the FAQ at http://lists.us.dell.com/faq
> 


I would suggest having a look at the RAID controller log using lintty, or a DOS bootable floppy to read it.

 (linttylog-1.00-0.i386.rpm)

or

ttylog.exe for DOS.


//
Harald Jensås



More information about the Linux-PowerEdge mailing list