Jason Murray writes: > 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: > > # raidctl -s raid0 > raid0 Components: > /dev/wd0d: failed > /dev/wd1d: optimal > No spares. > Parity status: DIRTY > Reconstruction is 100% complete. > Parity Re-write is 100% complete. > Copyback is 100% complete. > > So I attempt an inplace reconstruction of wd0d. > > # > # raidctl -R /dev/wd0d raid0 > Closing the opened device: /dev/wd0d > About to (re-)open the device for rebuilding: /dev/wd0d > RECON: Initiating in-place reconstruction on > row 0 col 0 -> spare at row 0 col 0. > Quiescence reached... > > 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 > RUN AT LEAST 'trace' AND 'ps' AND INCLUDE OUTPUT WHEN REPORTING THIS PANIC! > > DO NOT EVEN BOTHER REPORTING THIS WITHOUT INCLUDING THAT INFORMATION! > > This concerns me because I need wd1d to rebuild my failed wd0d. Any > ideas? Drive cables maybe? Any help is greatly appreciated.
You have recent backups, right? wd1 is failing/dying. At this point you're probably better off in attempting to use 'dd' to recover as many bits as you can... (if you do a 'dump' of the filesystem you can probably tell from that whether or not there is any 'live data' in the portion that is unreadable.... if there isn't any live data, then you can use 'dd' to make as much of a copy as possible of wd1, and use that as the base for reconstructing the RAID set.) Later... Greg Oster
