December 29, 201015 yr I have received a replacement for a seagate 1.5tb that would not power on. The replacement is a refurb and I had noticed that after a previous preclear and use, the reallocated counts increased - so I put it back on the shelf. I have decided to have another go and have just completed another preclear. What do you think of the results? Should I send it back? Drive = ST31500341AS Thanks Tony =========================================================================== = unRAID server Pre-Clear disk /dev/sdg = cycle 1 of 1 = Disk Pre-Clear-Read completed DONE = Step 1 of 10 - Copying zeros to first 2048k bytes DONE = Step 2 of 10 - Copying zeros to remainder of disk to clear it DONE = Step 3 of 10 - Disk is now cleared from MBR onward. DONE = Step 4 of 10 - Clearing MBR bytes for partition 2,3 & 4 DONE = Step 5 of 10 - Clearing MBR code area DONE = Step 6 of 10 - Setting MBR signature bytes DONE = Step 7 of 10 - Setting partition 1 to precleared state DONE = Step 8 of 10 - Notifying kernel we changed the partitioning DONE = Step 9 of 10 - Creating the /dev/disk/by* entries DONE = Step 10 of 10 - Testing if the clear has been successful. DONE = Disk Post-Clear-Read completed DONE Disk Temperature: 38C, Elapsed Time: 23:52:00 ============================================================================ == == Disk /dev/sdg has been successfully precleared == ============================================================================ S.M.A.R.T. error count differences detected after pre-clear note, some 'raw' values may change, but not be an indication of a problem 55c55 < 1 Raw_Read_Error_Rate 0x000f 110 099 006 Pre-fail Always - 170502277 --- > 1 Raw_Read_Error_Rate 0x000f 117 099 006 Pre-fail Always - 125149733 58,59c58,59 < 5 Reallocated_Sector_Ct 0x0033 098 098 036 Pre-fail Always - 100 < 7 Seek_Error_Rate 0x000f 065 060 030 Pre-fail Always - 3630817 --- > 5 Reallocated_Sector_Ct 0x0033 098 098 036 Pre-fail Always - 105 > 7 Seek_Error_Rate 0x000f 066 060 030 Pre-fail Always - 3747850 63c63 < 187 Reported_Uncorrect 0x0032 028 028 000 Old_age Always - 72 --- > 187 Reported_Uncorrect 0x0032 001 001 000 Old_age Always - 122 65,69c65,69 < 189 High_Fly_Writes 0x003a 060 060 000 Old_age Always - 40 < 190 Airflow_Temperature_Cel 0x0022 068 061 045 Old_age Always - 32 (Lifetime Min/Max 24/32) < 195 Hardware_ECC_Recovered 0x001a 047 032 000 Old_age Always < 197 Current_Pending_Sector 0x0012 100 100 000 Old_age Always - 2 < 198 Offline_Uncorrectable 0x0010 100 100 000 Old_age Offline - 2 --- > 189 High_Fly_Writes 0x003a 035 035 000 Old_age Always - 65 > 190 Airflow_Temperature_Cel 0x0022 062 059 045 Old_age Always - 38 (Lifetime Min/Max 24/41) > 195 Hardware_ECC_Recovered 0x001a 055 032 000 Old_age Always > 197 Current_Pending_Sector 0x0012 100 100 000 Old_age Always - 0 > 198 Offline_Uncorrectable 0x0010 100 100 000 Old_age Offline - 0 71,73c71,73 < 240 Head_Flying_Hours 0x0000 100 253 000 Old_age Offline - 67959267526682 < 241 Total_LBAs_Written 0x0000 100 253 000 Old_age Offline - 1034285378 < 242 Total_LBAs_Read 0x0000 100 253 000 Old_age Offline - 3709303039 --- > 240 Head_Flying_Hours 0x0000 100 253 000 Old_age Offline - 277639570917426 > 241 Total_LBAs_Written 0x0000 100 253 000 Old_age Offline - 3966143492 > 242 Total_LBAs_Read 0x0000 100 253 000 Old_age Offline - 3113440727 76c76 < ATA Error Count: 72 (device log contains only the most recent five errors) --- > ATA Error Count: 122 (device log contains only the most recent five errors) 91c91 < Error 72 occurred at disk power-on lifetime: 2599 hours (108 days + 7 hours) --- > Error 122 occurred at disk power-on lifetime: 2628 hours (109 days + 12 hours) 102,106c102,106 < 25 00 00 ff ff ff ef 00 1d+20:29:26.691 READ DMA EXT < 27 00 00 00 00 00 e0 00 1d+20:29:26.658 READ NATIVE MAX ADDRESS EXT < ec 00 00 00 00 00 a0 02 1d+20:29:26.638 IDENTIFY DEVICE < ef 03 46 00 00 00 a0 02 1d+20:29:26.618 SET FEATURES [set transfer mode] < 27 00 00 00 00 00 e0 00 1d+20:29:26.579 READ NATIVE MAX ADDRESS EXT --- > 25 00 08 ff ff ff ef 00 13:33:54.290 READ DMA EXT > 27 00 00 00 00 00 e0 00 13:33:54.261 READ NATIVE MAX ADDRESS EXT > ec 00 00 00 00 00 a0 02 13:33:54.241 IDENTIFY DEVICE > ef 03 45 00 00 00 a0 02 13:33:54.221 SET FEATURES [set transfer mode] > 27 00 00 00 00 00 e0 00 13:33:54.171 READ NATIVE MAX ADDRESS EXT 108c108 < Error 71 occurred at disk power-on lifetime: 2599 hours (108 days + 7 hours) --- > Error 121 occurred at disk power-on lifetime: 2628 hours (109 days + 12 hours) 119,123c119,123 < 25 00 00 ff ff ff ef 00 1d+20:29:23.718 READ DMA EXT < 27 00 00 00 00 00 e0 00 1d+20:29:23.679 READ NATIVE MAX ADDRESS EXT < ec 00 00 00 00 00 a0 02 1d+20:29:23.639 IDENTIFY DEVICE < ef 03 46 00 00 00 a0 02 1d+20:29:23.618 SET FEATURES [set transfer mode] < 27 00 00 00 00 00 e0 00 1d+20:29:23.509 READ NATIVE MAX ADDRESS EXT --- > 25 00 08 ff ff ff ef 00 13:33:51.330 READ DMA EXT > 27 00 00 00 00 00 e0 00 13:33:51.301 READ NATIVE MAX ADDRESS EXT > ec 00 00 00 00 00 a0 02 13:33:51.281 IDENTIFY DEVICE > ef 03 45 00 00 00 a0 02 13:33:51.262 SET FEATURES [set transfer mode] > 27 00 00 00 00 00 e0 00 13:33:51.131 READ NATIVE MAX ADDRESS EXT 125c125 < Error 70 occurred at disk power-on lifetime: 2599 hours (108 days + 7 hours) --- > Error 120 occurred at disk power-on lifetime: 2628 hours (109 days + 12 hours) 136,140c136,140 < 25 00 00 ff ff ff ef 00 1d+20:29:20.745 READ DMA EXT < 27 00 00 00 00 00 e0 00 1d+20:29:20.709 READ NATIVE MAX ADDRESS EXT < ec 00 00 00 00 00 a0 02 1d+20:29:20.689 IDENTIFY DEVICE < ef 03 46 00 00 00 a0 02 1d+20:29:20.671 SET FEATURES [set transfer mode] < 27 00 00 00 00 00 e0 00 1d+20:29:20.619 READ NATIVE MAX ADDRESS EXT --- > 25 00 08 ff ff ff ef 00 13:33:48.370 READ DMA EXT > 27 00 00 00 00 00 e0 00 13:33:48.341 READ NATIVE MAX ADDRESS EXT > ec 00 00 00 00 00 a0 02 13:33:48.321 IDENTIFY DEVICE > ef 03 45 00 00 00 a0 02 13:33:48.305 SET FEATURES [set transfer mode] > 27 00 00 00 00 00 e0 00 13:33:48.171 READ NATIVE MAX ADDRESS EXT 142c142 < Error 69 occurred at disk power-on lifetime: 2599 hours (108 days + 7 hours) --- > Error 119 occurred at disk power-on lifetime: 2628 hours (109 days + 12 hours) 153,157c153,157 < 25 00 00 ff ff ff ef 00 1d+20:29:17.739 READ DMA EXT < 27 00 00 00 00 00 e0 00 1d+20:29:17.710 READ NATIVE MAX ADDRESS EXT < ec 00 00 00 00 00 a0 02 1d+20:29:17.688 IDENTIFY DEVICE < ef 03 46 00 00 00 a0 02 1d+20:29:17.670 SET FEATURES [set transfer mode] < 27 00 00 00 00 00 e0 00 1d+20:29:17.558 READ NATIVE MAX ADDRESS EXT --- > 25 00 08 ff ff ff ef 00 13:33:45.430 READ DMA EXT > 27 00 00 00 00 00 e0 00 13:33:45.401 READ NATIVE MAX ADDRESS EXT > ec 00 00 00 00 00 a0 02 13:33:45.381 IDENTIFY DEVICE > ef 03 45 00 00 00 a0 02 13:33:45.348 SET FEATURES [set transfer mode] > 27 00 00 00 00 00 e0 00 13:33:45.221 READ NATIVE MAX ADDRESS EXT 159c159 < Error 68 occurred at disk power-on lifetime: 2599 hours (108 days + 7 hours) --- > Error 118 occurred at disk power-on lifetime: 2628 hours (109 days + 12 hours) 170,174c170,174 < 25 00 00 ff ff ff ef 00 1d+20:29:14.806 READ DMA EXT < 27 00 00 00 00 00 e0 00 1d+20:29:14.768 READ NATIVE MAX ADDRESS EXT < ec 00 00 00 00 00 a0 02 1d+20:29:14.748 IDENTIFY DEVICE < ef 03 46 00 00 00 a0 02 1d+20:29:14.732 SET FEATURES [set transfer mode] < 27 00 00 00 00 00 e0 00 1d+20:29:14.668 READ NATIVE MAX ADDRESS EXT --- > 25 00 08 ff ff ff ef 00 13:33:42.469 READ DMA EXT > 27 00 00 00 00 00 e0 00 13:33:42.441 READ NATIVE MAX ADDRESS EXT > ec 00 00 00 00 00 a0 02 13:33:42.421 IDENTIFY DEVICE > ef 03 45 00 00 00 a0 02 13:33:42.402 SET FEATURES [set transfer mode] > 27 00 00 00 00 00 e0 00 13:33:42.351 READ NATIVE MAX ADDRESS EXT ============================================================================ root@Tower:/boot#
December 29, 201015 yr Run one more preclear and if it comes back with similar results I would send it back. I would also bitch at Seagate for sending out a defective "refurb" drive.
December 29, 201015 yr Run one more preclear and if it comes back with similar results I would send it back. I would also bitch at Seagate for sending out a defective "refurb" drive. I agree... when you started there were two sectors pending re-allocation. You said that you previously pre-cleared it and then used it. The pending-reallocation sectors are not a good sign. They were detected after the initial pre-clear in either the post-read, or in the subsequent use of the drive. The 2 sectors were successfully re-allocated in this pre-clear cycle, but so were several others (the re-allocated count went from 100 to 105) so it must have found 3 more. The continued detection of additional un-readable sectors is not a good sign. I expect an additional pre-clear cycles will eventually find more un-readable sectors. My advice... send it back as a defective RMA replacement. Joe L.
December 29, 201015 yr When returning Seagate drives for warantee replacement they want you to run SeaTools and indicate the Test Code that the software generates. In this case it will pass most likely, you can enter the following test code: 659DC7AE - Failed other diagnostic tools, I'm confident it is a bad drive http://www.seagate.com/staticfiles/support/seatools/seatools-test-codes.html
December 29, 201015 yr Author thanks all for your help I will send it off to seagate. Happy New Year Tony
December 29, 201015 yr I ordered four 2TB Seagate LP's last week when they newegg had them for $85. One of them failed right after spin-up. smartctl showed it as FAILED, and syslog was getting hammered with errors. preclean ran for 8 hours and got to 2% of the initial read. I am sending it back, and hope I get a good one. The 8 in my unRAID have been bought since Black Friday and are my first Seagate drives ever, and this doesn't give me a warm fuzzy out of the gate.
December 29, 201015 yr I ordered four 2TB Seagate LP's last week when they newegg had them for $85. One of them failed right after spin-up. smartctl showed it as FAILED, and syslog was getting hammered with errors. preclean ran for 8 hours and got to 2% of the initial read. I am sending it back, and hope I get a good one. The 8 in my unRAID have been bought since Black Friday and are my first Seagate drives ever, and this doesn't give me a warm fuzzy out of the gate. One of the drives I have for a customers build failed right out of the gate. I ran 2 passes of preclear on it and it it came back with some 6500 reallocated sectors and said it was "FAILING_NOW." Well no **** sherlock. I did an RMA on the drive and am waiting for one back. I have gotten 10 of the drives and had one fail so far. The rest have survived there mandatory 3 passes of preclear and there firmware updated.
Archived
This topic is now archived and is closed to further replies.