-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Wednesday, 2010-01-20 at 01:22 -0600, David C. Rankin wrote:
Thank you a lot. The disk is part of a mirrored set so basically I just need to split the array and run both standalone until I get the new drive back from seagate.
No need. Just keep the disk in place, and replace it when the new one arrives, if you want to replace it. But please notice that having some bad sectors is not a disaster: it is a normal working occurrence. So much it is normal that the manufacturer has put some spare sectors. As I said, it is only important if the number increases, not if it remains stable. That value is a warning, not an alarm. For the moment. Also notice that Seagate will replace the disk free of charge when that spare space is spent, during the warranty period, but might refuse if only 10 sectors are used. Anyway, you will have to run the full external test and obtain the failure code in order to get an RMA. And yes, as the disk in a raid, there is no danger in running the full test. You have another copy of the data, and you will learn if the damage is bigger.
I have a another new 750G drive that I could use in the interim or just leave them running standalone until the replacement gets here. I bet the bad sectors haven't been remapped due to the dmraid setup.
No, not related.
I don't know if the disk can remap the sectors when the drive is part of an array
Of course it can.
-- I don't know what that would do to the sync among the disks??
Nothing. Except... The HD tries to move the data in a bad sector to a spare sector; but the data itself might be bad (read failure). Notice that this is an operation that happens totally inside the HD, without any consideration for the mirrored disk. Nobody outside of the HD knows about the problem. The result could be that both sides had different data after the operation. However, the remapping occurs only during a write operation, so the preceding scenario would not happen. - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (GNU/Linux) iEYEARECAAYFAktXmYUACgkQtTMYHG2NR9Wx1gCfYooo6TqYdS+SGSNu/9NXQk3h 9c8AnRUG5Ji/sNjsUdwncEfzYlOWzHh3 =+U4W -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org