November 14, 201213 yr When I got home from vacation, I noticed one of my WD 2TB green drives were red balled. Not knowing what might have caused this and not sure how many writes the drive might be missing, I decided to put a spare precleared 2 TB green drive in its place and rebuild. The data rebuild process was a success. I then decided to run a couple of test on the "failed" drive. I used the WD software on my windows machine. One was a short and one was a long test. Both passed. I then decided to try preclearing the drive. It went smoothly and appeared to complete all 10 steps, but says: Sorry: disk /dev/sdb MBR could NOT be precleared Any ideas? This is using preclear 1.13 on 5rc8a using the -A command. I use the -A command since this drive is for my 4.7 unraid server and that is what I used for the other drives in service. Thanks.
November 16, 201213 yr When I got home from vacation, I noticed one of my WD 2TB green drives were red balled. Not knowing what might have caused this and not sure how many writes the drive might be missing, I decided to put a spare precleared 2 TB green drive in its place and rebuild. The data rebuild process was a success. I then decided to run a couple of test on the "failed" drive. I used the WD software on my windows machine. One was a short and one was a long test. Both passed. I then decided to try preclearing the drive. It went smoothly and appeared to complete all 10 steps, but says: Sorry: disk /dev/sdb MBR could NOT be precleared Any ideas? This is using preclear 1.13 on 5rc8a using the -A command. I use the -A command since this drive is for my 4.7 unraid server and that is what I used for the other drives in service. Thanks. Attach the preclear reports (from in /boot/preclear_reports ) Typically, if you get that error and it went through all 10 phases it is because the post-read phase did NOT read back all zeros when it went to verify the disk was cleared. The actual cause can be a bad disk, a bad disk controller,, a bad motherboard chipset, a bad power supply, or bad memory, or incorrectly configured memory (wrong voltage, timing, or clock speed) Joe L.
November 16, 201213 yr Author Does the report not survive a reboot because its not there and I did reboot the system since the test? Should I try preclearing it again? Thanks.
November 16, 201213 yr Does the report not survive a reboot because its not there and I did reboot the system since the test? Should I try preclearing it again? Thanks. The reports always survive reboot if in /boot/preclear_reports. You can try preclearing again. a "red" indicator says at least one "write" to the drive failed. You should power down and verify all cables to the disk involved are secure on both ends and seated properly. Joe L
Archived
This topic is now archived and is closed to further replies.