Server Building > Hard Drives and Controllers
Preclear and Failed Drives
Joe L.:
--- Quote from: bw1 on April 21, 2012, 09:44:34 AM ---To run preclear with email notifications, use something like:
./preclear_disk.sh -m youremail@email.com -M 4 /dev/sdX
--- End quote ---
That will work, but ONLY is you installed and configured MAIL on your server. If you did not, the mail option will not work.
As far as moving your data...
Once you assign the disks to your array, and the array shares are visible on your LAN, moving data is as simple as copying the file with your file-explorer on your PC. I strongly suggest assigning a parity drive on the unRAID array first, before populating it with files. It makes recovery much easier if a disk were to fail in its first few hours/days of operation.
rvijay007:
Is it possible to run pre clear without writing any data (read-only) to test drives on a quarterly basis for possible read failures, especially if those drives aren't being accessed on any regular frequency?
Basically, this would allow for some amount of data integrity checking and possible drive failure in the future. Trying to catch potential drive failures as early as possible.
Joe L.:
--- Quote from: rvijay007 on July 16, 2012, 07:13:48 AM ---Is it possible to run pre clear without writing any data (read-only) to test drives on a quarterly basis for possible read failures, especially if those drives aren't being accessed on any regular frequency?
Basically, this would allow for some amount of data integrity checking and possible drive failure in the future. Trying to catch potential drive failures as early as possible.
--- End quote ---
To run the post-read-verify only on a drive (the drive will not be written to).
preclear_disk.sh -V [-A|-a] /dev/???
options to preclear_disk.sh can be seen by typing
preclear_disk.sh -?
Joe L.
c3:
--- Quote from: rvijay007 on July 16, 2012, 07:13:48 AM ---Is it possible to run pre clear without writing any data (read-only) to test drives on a quarterly basis for possible read failures, especially if those drives aren't being accessed on any regular frequency?
Basically, this would allow for some amount of data integrity checking and possible drive failure in the future. Trying to catch potential drive failures as early as possible.
--- End quote ---
The suggested monthly parity checks help too.
trevorp:
This may be an old topic, but since I just voted, I figured I'd weigh in here with my rationale too.
I used to only pre-clear once. Then I bought a WD30EZRX drive from Newegg.
I pre-cleared it as usual. Reading the output of the pre-clear script, I noticed it said that I had 3 sectors pending re-allocation before the run, and 4 after pre-read cycle 1. It ended with 35 sectors pending re-allocation.
So I fired up round 2. After it was done, I had 42 sectors pending re-allocation.
Round 3, and the drive vomited all over my syslog and got yanked. I don't have the results, as it never finished, but if I recall it was in the multiple tens of thousands range.
The replacement drive survived 3 rounds of pre-clearing fine.
I just purchased 2 more WD30EZRX drives, one of which survived the 3 rounds of pre-clearing fine, and the other was so DOA it never even started the pre-clear cycle.
I think I'll be switching to the badblocks + pre-clear method from here on out though.
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version