March 5, 201511 yr I have exchanged a 500 GB disk for a 2 TB disk and it was rebuild. In the syslog I saw multiple read errors on another disk, disk3, during the time that the exchanged disk, disk18, was rebuild. Can you please advise me on the cause of this and on what to do now? syslog is attached. syslog_3.zip
March 5, 201511 yr Since you were just in the machine, the first thing to do would be to check that you didn't disturb the other cables to the drives. I would stop the rebuild, shut down the system, reseat all of the cables to all of the hard drives, along with power connectors, and also reseat them at your controller card.
March 5, 201511 yr Author Since you were just in the machine, the first thing to do would be to check that you didn't disturb the other cables to the drives. I would stop the rebuild, shut down the system, reseat all of the cables to all of the hard drives, along with power connectors, and also reseat them at your controller card. Thanks for the fast reply. The rebuild already finished. The errors occurred a few hours after 500 GB (The size of the disk that was replaced. How do I start a new rebuild?
March 5, 201511 yr To force a rebuild on a drive, you have to stop the array. Set the drive you want to rebuild as missing / not installed. Start the array, stop the array, set the drive back to be installed, start the array. It will start rebuilding. But, since you were getting read errors, I would run md5 checks against the drive which just rebuilt (assuming you've made md5's for the files)
March 5, 201511 yr Author Too late. The disk with the read errors shows up a red ball now. The disks are in a Supermicro 5in3 case on a M1015 controller.
March 5, 201511 yr Too late. The disk with the read errors shows up a red ball now. The disks are in a Supermicro 5in3 case on a M1015 controller. I'm not surprised. Reseat that drive tray and rebuild the disk.
March 5, 201511 yr Author May have to replace that disk first. Short smartctl test shows read error too beginning at 70%. Yesterday the system showed no errors when I ran a parity check after rebuilding the parity check.
March 5, 201511 yr Author How do I write the SMART attributes to a file? Stupid question I know but starting to panic now.
March 5, 201511 yr Since you're on 6, you can just click the disk then select disk attributes. Copy and paste via windows. Or if you want to do it via the command prompt, smartctl -A /dev/sd??? > /boot/smartattributes.txt
March 5, 201511 yr Author Disk 3 attached to port: sdr ID# ATTRIBUTE NAME FLAG VALUE WORST THRESH TYPE UPDATED FAILED RAW VALUE 1 Raw Read Error Rate 0x002f 200 200 051 Pre-fail Always Never 385 3 Spin Up Time 0x0027 253 179 021 Pre-fail Always Never 2075 4 Start Stop Count 0x0032 099 099 000 Old age Always Never 1371 5 Reallocated Sector Ct 0x0033 200 200 140 Pre-fail Always Never 0 7 Seek Error Rate 0x002e 100 253 000 Old age Always Never 0 9 Power On Hours 0x0032 093 092 000 Old age Always Never 5194 10 Spin Retry Count 0x0032 100 100 000 Old age Always Never 0 11 Calibration Retry Count 0x0032 100 253 000 Old age Always Never 0 12 Power Cycle Count 0x0032 100 100 000 Old age Always Never 30 192 Power-Off Retract Count 0x0032 200 200 000 Old age Always Never 26 193 Load Cycle Count 0x0032 200 200 000 Old age Always Never 2827 194 Temperature Celsius 0x0022 121 105 000 Old age Always Never 31 196 Reallocated Event Count 0x0032 200 200 000 Old age Always Never 0 197 Current Pending Sector 0x0032 200 200 000 Old age Always Never 0 198 Offline Uncorrectable 0x0030 100 253 000 Old age Offline Never 0 199 UDMA CRC Error Count 0x0032 200 200 000 Old age Always Never 0 200 Multi Zone Error Rate 0x0008 100 253 000 Old age Offline Never 0 smartattributes.txt
March 5, 201511 yr Author Did a short smart in putty and it showed read failure after 70%. Did a short smart test on the dashboard in the webgui and it showed no errors.
March 5, 201511 yr Author Seems it was the disk after all. I reseated all cables. Reseated the disk in the cage. But still no dice. Sometimes the disk red balled after 5 writes, sometimes after 100000. But it red balled anyhow. I then took the disk outside the cage and connected it with a separate sata and power cable. I again got a red ball. I now exchanged the disk with another disk to the same cables. It is now at close to 400000 writes and 5% rebuild and still running without error. RMA another RED to WD again. 8 months old.
March 8, 201511 yr Seems it was the disk after all. I reseated all cables. Reseated the disk in the cage. But still no dice. Sometimes the disk red balled after 5 writes, sometimes after 100000. But it red balled anyhow. I then took the disk outside the cage and connected it with a separate sata and power cable. I again got a red ball. I now exchanged the disk with another disk to the same cables. It is now at close to 400000 writes and 5% rebuild and still running without error. RMA another RED to WD again. 8 months old. Thats why I use wd blacks. Reds seem too inconsistent. Blacks cost more but are rock solid and come with a 5 year warranty.
Archived
This topic is now archived and is closed to further replies.