Brian Chivers wrote:
> John Cooper wrote:
>> Hi, has anyone had trouble with the Perc4e/Di on board RAID controller
>> where it will not create partitions on any Linux install? I'm not sure
>> if it is a megaraid driver bug or controller bug. I'm installing on an
>> old Dell Poweredge 2600 server. At the point it partitions the disk, the
>> mkfs fails immediately with similar output to this :-
>>
>> megaraid: aborting-29762 cmd=2a <c=2 t=0 l=0>
>> megaraid abort: 29762:21[255:128], fw owner
>> megaraid: aborting-29763 cmd=2a <c=2 t=0 l=0>
>> megaraid abort: 29763:39[255:128], fw owner
>> megaraid: aborting-29764 cmd=2a <c=2 t=0 l=0>
>> megaraid abort: 29764:16[255:128], fw owner
>> megaraid: aborting-29768 cmd=2a <c=2 t=0 l=0>
>> megaraid abort: 29768:53[255:128], fw owner
>> ....
>> megaraid: aborting-29831 cmd=2a <c=2 t=0 l=0>
>> megaraid abort: 29831:8[255:128], fw owner
>> megaraid: resetting the host...
>> megaraid: 64 outstanding commands. Max wait 180 sec
>> megaraid mbox: Wait for 64 commands to complete:180
>> megaraid mbox: Wait for 64 commands to complete:175
>>
>> megaraid mbox counts down to 0, and then...
>>
>> megaraid mbox: critical hardware error!
>> megaraid: resetting the host...
>> megaraid: hw error, cannot reset
>> megaraid: resetting the host...
>> megaraid: hw error, cannot reset
>> SCSI error : <0 2 0 0> return code = 0x6000000
>> end_request: I/O error, dev sda, sector 242938701
>> Buffer I/O error on device dm-4, logical block 9893952 lost page write
>> due to I/O error on dm-4
>> scsi0 (0:0): rejecting I/O to offline device
>>
> I've got a few of these on 1800's and have noticed this scrolling past
> every now & then but the box runs fine & installed OK with Etch. I also
> have one with Smoothwall Advanced Server & this would throw up the error
> but the box works fine so was naughty & ignored it. The CentOS5's have
> installed fine and I've not noticed it.
>
> I have a couple of "spare" 2600's sitting on the shelf but I don't think
> the have the Perc4e's in but I'll have a look later if you like
>
I decided to change the RAID battery and 128MB RAM (PC100) and it now
installs perfectly as RAID1. Looks like the RAM as I removed the battery
first which automatically changes the RAID from Write Back to Write
Through when creating the array. This didn't make any difference so it
looks like if you see these errors and you have the latest BIOS and FW
installed, your raid controller RAM is worth replacing.
Battery is P/N 1K178 (~£20 eBay)
RAM is P/N 13JPJ, Dell Poweredge PERC memory 2500, 2550, 2600, 2650
series 128MB PC100 100MHz 168pin Dimm CL2 (~£25 eBay)
Thanks, John.
--
--------------------------------------------------------------
Discover Linux - Open Source Solutions to Business and Schools
http://discoverlinux.co.uk
--------------------------------------------------------------
