February 5, 201511 yr Have a Seagate Barracuda 3tb drive that I want to add to the array. I started the pre-clear process on it last night, and things went according to plan at ~80mb/s. It finished around 1pm today, and then started the post-read. Surprisingly though, it is going at a rate of 1mb/s. I stopped all activity on the server (i.e. I aborted the files I was copying onto it) and spun the drives down while keeping the array up, thinking that it was a bandwidth issue. However, the speed did not change at all. It's been 3h at that rate, and it'll take forever to finish. I have scanned the forums here to see whether it can help. I noticed some people have seen this issue. I have taken two SMART reports 3h apart to try to see changes, and reviewed the unRAID logs but there's nothing in them. I've now pulled the drive, and will try to repeat this in another computer to see what I get. Any ideas? I don't know how to interpret the SMART report. Thank you. SMART_-_Log_1pm.txt SMART_-_Log_4pm.txt Logs.txt
February 5, 201511 yr Nothing's in the syslog as to why it would be so slow, but with 1344 reallocated sectors and 8 pending right now (and 566 reported uncorrectable), I'd give some serious thoughts as to whether or not you'd trust that drive anyways.
February 5, 201511 yr Author Excellent help Squid. I did not pick those numbers up, wasn't sure how I should read them. I put the HD into another computer, same motherboard. Pre-read was going at ~150mb/s, it read as much in 2 minutes than the other did in 3.5 hours. In any case, once I got SeaTools burnt onto DVD, I ran it and the drive quickly failed the short-test. Guess that's a good enough reason to RMA it. I did check the same numbers on all my other drives in my unRAID setup, and they all are showing 0 for those numbers. One of the drives however is showing: ID# ATTRIBUTE NAME FLAG VALUE WORST THRESH TYPE UPDATED FAILED RAW VALUE 1 Raw Read Error Rate 0x000f 102 099 006 Pre-fail Always Never 4237176 3 Spin Up Time 0x0003 093 092 000 Pre-fail Always Never 0 4 Start Stop Count 0x0032 094 094 020 Old age Always Never 7029 5 Reallocated Sector Ct 0x0033 098 098 036 Pre-fail Always Never 3664 7 Seek Error Rate 0x000f 075 060 030 Pre-fail Always Never 33249786 9 Power On Hours 0x0032 074 074 000 Old age Always Never 23017 10 Spin Retry Count 0x0013 100 100 097 Pre-fail Always Never 0 12 Power Cycle Count 0x0032 100 100 020 Old age Always Never 159 183 Runtime Bad Block 0x0032 100 100 000 Old age Always Never 0 184 End-to-End Error 0x0032 100 100 099 Old age Always Never 0 187 Reported Uncorrect 0x0032 100 100 000 Old age Always Never 0 188 Command Timeout 0x0032 100 083 000 Old age Always Never 0 0 116 189 High Fly Writes 0x003a 100 100 000 Old age Always Never 0 190 Airflow Temperature Cel 0x0022 063 052 045 Old age Always Never 37 (Min/Max 34/38) 191 G-Sense Error Rate 0x0032 100 100 000 Old age Always Never 0 192 Power-Off Retract Count 0x0032 100 100 000 Old age Always Never 141 193 Load Cycle Count 0x0032 033 033 000 Old age Always Never 134426 194 Temperature Celsius 0x0022 037 048 000 Old age Always Never 37 (0 18 0 0 0) 197 Current Pending Sector 0x0012 100 100 000 Old age Always Never 0 198 Offline Uncorrectable 0x0010 100 100 000 Old age Offline Never 0 199 UDMA CRC Error Count 0x003e 200 086 000 Old age Always Never 49595 240 Head Flying Hours 0x0000 100 253 000 Old age Offline Never 6798h+38m+42.518s 241 Total LBAs Written 0x0000 100 253 000 Old age Offline Never 49983417428478 242 Total LBAs Read 0x0000 100 253 000 Old age Offline Never 33701642252754 When the current parity check is complete, I'll shut the machine down and run SeaTools on that drive as well. Thank you for the help.
February 5, 201511 yr Author Aaarghhh... The thing only had 2 years warranty. And I'm just beyond it. Sigh...
February 5, 201511 yr Community Expert Technically a non-zero value for reallocated sectors is OK as long as it is stable and not steadily increasing. However when the value starts getting large then one has to wonder if there is some underlying issue with the disk and if it can be trusted. Hopefully the SMART monitoring that is now available with v6 will help by giving notifications when such values are changing.
Archived
This topic is now archived and is closed to further replies.