Dell PE1850/2850 RAID array issue with RHEL4

[Nicky Peeters]

I have tried it, but it dumps a tty.log that starts from after my  
recent reboot.
I guess I've got to force my machine to crash somehow, and then run  
the tool again?

Also, when I found the machine in its pitifull, diskless state, I  
only had access to 'dmesg'
and to my regret I did not see any errors in that output of the  
MegaRaid driver.

After my reboot, my syslog had no lines about MegaRaid either. It  
just stopped logging at some point in time.

Thanks for the info, I hope I can catch my Perc in the act next time  
using the linttylog utility !

Nicky

On 04 Aug 2006, at 16:37, Hansjörg Maurer wrote:

> Hi
>
> our errors where almost similar
>
> Jul 22 02:08:44 intra kernel: megaraid abort: 21963824[255:129],  
> driver
> owner
> Jul 22 02:08:44 intra kernel: megaraid: aborting-21963825 cmd=2a <c=2
> t=1 l=0>
> Jul 22 02:08:44 intra kernel: megaraid abort: 21963825[255:129],  
> driver
> owner
> Jul 22 02:08:44 intra kernel: megaraid: aborting-21963826 cmd=2a <c=2
> t=1 l=0>
> Jul 22 02:08:44 intra kernel: megaraid abort: 21963826[255:129],  
> driver
> owner
> Jul 22 02:08:44 intra kernel: megaraid: resetting the host...
>
> and
> http://www.firehat.org/repodata/repoview/linttylog-0-1.00-0.html
> detects  finaly an hardware issue like I described in a previos mail
>
> Give it a try :-)
>
> Hansjörg
>
>
> Herman Vega wrote:
>
>> hi all
>>
>> We had similar problem last week, we resolved to change the perc4/dc
>> to advantec scsi cards next week.
>>
>> Jul 28 22:00:01 nod1 kernel: megaraid: aborting-16591038 cmd=2a  
>> <c=2 t=0 l=0>
>> Jul 28 22:00:01 nod1 kernel: megaraid abort: scsi cmd:16591071, do  
>> now own
>> Jul 28 22:00:01 nod1 kernel: megaraid: resetting the host...
>> Jul 28 22:00:01 nod1 kernel: megaraid mbox: reset sequence completed
>> successfully
>> Jul 28 22:00:01 nod1 kernel: megaraid: fast sync command timed out
>> Jul 28 22:00:01 nod1 kernel: megaraid: reservation reset failed
>> Jul 28 22:00:01 nod1 kernel: megaraid: resetting the host...
>> Jul 28 22:00:01 nod1 kernel: scsi: Device offlined - not ready after
>> error recovery: host 1 channel 2 id 0 lun 0
>> Jul 28 22:00:01 nod1 last message repeated 36 times
>> Jul 28 22:00:01 nod1 kernel: SCSI error : <1 2 0 0> return code =  
>> 0x70018
>> Jul 28 22:00:01 nod1 kernel: end_request: I/O error, dev sdb,  
>> sector 314795551
>> Jul 28 22:00:01 nod1 kernel: Buffer I/O error on device sdb1, logical
>> block 39349436
>> Jul 28 22:00:01 nod1 kernel: lost page write due to I/O error on sdb1
>> Jul 28 22:00:01 nod1 kernel: scsi1 (0:0): rejecting I/O to offline  
>> device
>> Jul 28 22:00:01 nod1 kernel: SCSI error : <1 2 0 0> return code =  
>> 0x70018
>> Jul 28 22:00:01 nod1 kernel: end_request: I/O error, dev sdb,  
>> sector 314798975
>> Jul 28 22:00:01 nod1 kernel: scsi1 (0:0): rejecting I/O to offline  
>> device
>> Jul 28 22:00:01 nod1 last message repeated 138 times
>> Jul 28 22:00:01 nod1 kernel: __journal_remove_journal_head: freeing
>> b_committed_data
>> Jul 28 22:00:01 nod1 kernel: __journal_remove_journal_head: freeing
>> b_committed_data
>> Jul 28 22:00:01 nod1 kernel: ext3_abort called.
>> Jul 28 22:00:01 nod1 kernel: EXT3-fs error (device sdb1):
>> ext3_journal_start_sb: Detected aborted journal
>> Jul 28 22:00:01 nod1 kernel: Remounting filesystem read-only
>> Jul 28 22:00:01 nod1 kernel: EXT3-fs error (device sdb1) in
>> start_transaction: Journal has aborted
>> Jul 28 22:00:01 nod1 kernel: scsi1 (0:0): rejecting I/O to offline  
>> device
>> Jul 28 22:00:01 nod1 kernel: scsi1 (0:0): rejecting I/O to offline  
>> device
>> Jul 28 22:00:02 nod1 kernel: scsi1 (0:0): rejecting I/O to offline  
>> device
>> Jul 28 22:00:02 nod1 kernel: EXT3-fs error (device sdb1):
>> ext3_find_entry: reading directory #18989559 offset 0
>>
>>
>> On 7/28/06, wolf2k5 <wolf2k5 at gmail.com> wrote:
>>
>>
>>> Hi all,
>>>
>>> We've a few Dell PowerEdge 1850 and 2850 servers running RHEL4 U3
>>> (some i386, others x86_64). The 1850s have RAID1 arrays, the 2850s
>>> have RAID1 and RAID arrays. We applied the latest BIOS and RAID
>>> firmware to all servers.
>>>
>>>
>>
>>
>>
>
> _______________________________________________
> 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
>