On 7/17/06, Jason Murray <[EMAIL PROTECTED]> wrote:
I've tried, again, to fix my raid array with raidctl -R. I did it on the
console port this time so I could capture the output from ddb>
Here is some output:
yay!
I then use raidctl -S to monitor the reconstruction. Things go well
until the 48% mark. Then I get:
wd1d: uncorrectable data error reading fsbn 111722176 of
11722176-111722303 (wd1 bn 114343984; cn 113436 tn 7 sn 55), retrying
/wd1: transfer error, downgrading to Ultra-DMA mode 4
wd1(pciide0:1:0): using PIO mode 4, Ultra-DMA mode 4
wd1d: uncorrectable data error reading fsbn 111722176 of
111722176-111722303 (wd1 bn 114343984; cn 113436 tn 7 sn 55), retrying
wd1d: uncorrectable data error reading fsbn 111722248 of
111722176-111722303 (wd1 bn 114344056; cn 113436 tn 9 sn 1), retrying
wd1d: uncorrectable data error reading fsbn 111722248 of
111722176-111722303 (wd1 bn 114344056; cn 113436 tn 9 sn 1)
raid0: IO Error. Marking /dev/wd1d as failed.
Recon read failed !
panic: RAIDframe error at line 1518 file
/usr/src/sys/dev/raidframe/rf_reconstruct.c
Stopped at Debugger+0x4: leave
In case the output is not clear enough, there is an error reading
block numbers 11722176 through 111722303 on wd1. This is not an issue
with raidframe. This is an issue with your IDE disk. (or ide
controller, etc...)
Test the disk thoroughly using badblocks from the e2fstools port and I
am sure it will reproduce the exact same console output. and panic,
though a different backtrace.
That OpenbSD crashes when an ide disk fails to communicate properly is
not the fault of OpenBSD, and definitly not raidframe. OpenBSD actualy
tried to do you a favor and step down the communication speed ( /wd1:
transfer error, downgrading to Ultra-DMA mode 4 ), in case it were the
fault of the ide controller or what have you.
I think I can easily guess that this is why raidframe marked the disk
bad in the first place. You need to replace the disk with a fresh disk
of similar or greater geometry size, copy the disklabel onto the new
disk, and reconstruct. This is what raid is for. Unfortunatly for you,
your raid is both software and ide. This is why the kernel panics.
