-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Wednesday, 2010-01-27 at 23:54 -0600, David C. Rankin wrote:
Happily, there is some magic somewhere in dmraid that makes this work OK. The key is to boot with some other media so that the 2 disks in question are not mounted or used by the booted OS. After fsck'ing the disk in question, mount both disks say under /mnt/a and /mnt/b. Then if 'b' was the drive fsck'ed, do a cp -a /mnt/a/* /mnt/b. Then re-enable the array in the bios on the next boot and all is well.
Run smartctl --test=long /dev/sda, then sdb, etc. After it finishes, fsck the array. Notice that copying one disk to the other, ie, rewriting a disk, is what is done to force the disk to remap sectors when there are uncorrectable or pending errors.
What I want to know is: "Is there any individual disk level error correction performed on disks in dmraid arrays, or is it as it looks -- no fsck error correction is ever performed on individual disks in a dmraid array?"
As we said, fsck should not be used to correct those errors. - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (GNU/Linux) iEYEARECAAYFAktiBeAACgkQtTMYHG2NR9WShwCfY/yeAcfpw6f+dkrnZ2E83hph 23AAmgNLX/S2K2gPK+tY0OqJi4CJhKd6 =Mj+O -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org