Majed B. said at 13/09/2009 23:49: > If your data is backed up, doing everything from scratch is your best > bet, and I'll tell you why you shouldn't try to patch up your current > situation: I know this is the best way forward, however finding time to do this is harder. Obviously, if push comes to shove, I'll have to do it. Just trying to avoid it. > 1) Have you written a single byte to the array(s) when the first disk > was thrown out of the array? > If yes, then adding it again will be equal to adding a new hard disk. > If no, then why was it trying to resync? I think it's already flagged > dirty but you've got 99.2% worth of data... The good disk was kicked because of a configuration error. There have been writes since then (on the /var partition) hence the required resync. > 2) Your disk that is currently running the RAID1 array has bad sectors. > If you try to clone that, you'll fail to clone all sectors, which > means loss of data. Understood. > 3) Ignoring bad sectors means you'll end up with corrupt Physical > Volumes under the LVM (Since your arrays are Physical Volumes of the > LVM). This will also cause problems with the filesystem. The bad sector is in an unallocated part of the PV - there are no LVs on it. Thankfully the bad sector is right at the end of the disk. > I would suggest buying TWO new disks and reinstall everything and > restore your backup(s) then data. It's better than spending numerous > hours trying to find out why a service isn't working, then after days > you realize that some binaries are corrupt or the config files. I can checksum all the binaries and compare to a known good system and the config files are all backed up. I've rebooted recently and it all works now with the bad sector present, so I'm not concerned about this since it seems unlikely to happen. > The reason I say TWO new disks, is that you already have one disk with > bad sectors, and the other popped out of the array for a reason. Do > not add the 2nd disk until you're truly sure there's nothing wrong > with it (run smartd and execute short and long tests, try to read the > whole disk a few times using dd: dd if=/dev/sdc of=/de/null bs=10M). > > If you see link errors in the kernel/dmesg, change your SATA cables. I've run SMART tests on the good disk and it appears fine. I'll do a dd of the whole disk to verify before I reuse it. Ronny -- Ronny Adsetts Technical Director Amazing Internet Ltd, London t: +44 20 8607 9535 f: +44 20 8607 9536 w: www.amazinginternet.com Registered office: UK House, 82 Heath Road, Twickenham TW1 4BW Registered in England. Company No. 4042957
Attachment:
signature.asc
Description: OpenPGP digital signature
