Whaler_99 Posted August 5, 2022 Share Posted August 5, 2022 Recently replaced a 3TB with 8TB drive. Drive was precleared, all good. After rebuild, I started moving data from another small drive onto it and errors re: Current Pending Sector and Offline Uncorrectable popped up. I stopped the disk copy, ran a smart extended disk test which came up ok. Started copying some data again, no errors but seems very slow. Wondering if this disk is going? # ATTRIBUTE NAME FLAG VALUE WORST THRESHOLD TYPE UPDATED FAILED RAW VALUE 1 Raw read error rate 0x000f 083 064 006 Pre-fail Always Never 220584408 3 Spin up time 0x0003 092 092 000 Pre-fail Always Never 0 4 Start stop count 0x0032 099 099 020 Old age Always Never 1936 5 Reallocated sector count 0x0033 100 100 010 Pre-fail Always Never 0 7 Seek error rate 0x000f 083 060 045 Pre-fail Always Never 194565708 9 Power on hours 0x0032 072 072 000 Old age Always Never 24975h+44m+59.718s 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 104 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 100 000 Old age Always Never 0 0 0 189 High fly writes 0x003a 100 100 000 Old age Always Never 0 190 Airflow temperature cel 0x0022 067 057 040 Old age Always Never 33 (min/max 28/35) 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 37 193 Load cycle count 0x0032 095 095 000 Old age Always Never 10495 194 Temperature celsius 0x0022 033 043 000 Old age Always Never 33 (0 17 0 0 0) 195 Hardware ECC recovered 0x001a 083 064 000 Old age Always Never 220584408 197 Current pending sector 0x0012 100 100 000 Old age Always Never 16 198 Offline uncorrectable 0x0010 100 100 000 Old age Offline Never 16 199 UDMA CRC error count 0x003e 200 200 000 Old age Always Never 0 240 Head flying hours 0x0000 100 253 000 Old age Offline Never 3579h+07m+24.507s 241 Total lbas written 0x0000 100 253 000 Old age Offline Never 86117390702 242 Total lbas read 0x0000 100 253 000 Old age Offline Never 508513967238 If someone could take a look and let me know. Anything to worry about with those to options sitting at 16? Don't seem to be increasing. tower-smart-20220805-0739.zip Quote Link to comment
trurl Posted August 5, 2022 Share Posted August 5, 2022 Do you have another you could replace it with? Then you could try preclearing it again to see if those pending sectors would get reallocated. Quote Link to comment
Whaler_99 Posted August 5, 2022 Author Share Posted August 5, 2022 21 minutes ago, trurl said: Do you have another you could replace it with? Then you could try preclearing it again to see if those pending sectors would get reallocated. Yes I do, so do the normal routine to replace the drive. After replacement drive rebuilds and array back to normal, I add it back in, anything special I need to do considering it would have been part of the array previously? Quote Link to comment
trurl Posted August 5, 2022 Share Posted August 5, 2022 2 minutes ago, Whaler_99 said: I add it back in I didn't say anything about adding it back in. I suggested preclearing it again to see if the pending sectors become reallocated sectors. Depends on the results of that whether you put it in the array. Quote Link to comment
Whaler_99 Posted August 5, 2022 Author Share Posted August 5, 2022 8 minutes ago, trurl said: I didn't say anything about adding it back in. I suggested preclearing it again to see if the pending sectors become reallocated sectors. Depends on the results of that whether you put it in the array. Sorry, phrased wrong. Add it back into the server, but not the array itself. To do a preclear on it. Quote Link to comment
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.