Seagate Exos X16... bin or....?


Recommended Posts

So long story short..

 

I have a Seagate Exos X16 16TB in my array which started to build up its Reallocated sector count.. increasing 4 times over a 3 month window up-to 120.

 

I contacted Seagate by phone and the guy said to me.. oh yeah, its failing, that needs replaced, complete the details I will send you.

 

Completed all the details and tech support told me 120 sectors is like 0.000000000001% so perfectly normal, and you should run tests on Seatools (Short Generic, Long Generic & Fix All). Bought a WD Ultrastar HC550 18TB to replace it, removed the drive to test it, and it passed all them all.

 

Have put it back into my server and ran a pre clear and its failed (see Preclear 1 below).

 

I then ran a short & extended SMART and it passed both.

 

Ran a 2nd Pre Clear and this evening has failed it (see Preclear 2 below). The reallocated sector count is now 128.

 

What should I do? Keep pushing Seagate, or just scrap the disk? Its 1 year old..given it cost circa £260 ($320+), and is a "enterprise" disc seems fairly poor tbh...

 

See reports below:

 

Preclear 1:

 

Mar 08 00:14:19 preclear_disk_WL20S7J5_20799: Post-Read: dd output: 4354662+0 records out

Mar 08 00:14:19 preclear_disk_WL20S7J5_20799: Post-Read: dd output: 9132388122624 bytes (9.1 TB, 8.3 TiB) copied, 36555.7 s, 250 MB/s

Mar 08 00:14:19 preclear_disk_WL20S7J5_20799: Post-Read: dd output: 4356060+0 records in

Mar 08 00:14:19 preclear_disk_WL20S7J5_20799: Post-Read: dd output: 4356059+0 records out

Mar 08 00:14:19 preclear_disk_WL20S7J5_20799: Post-Read: dd output: 9135317843968 bytes (9.1 TB, 8.3 TiB) copied, 36568.6 s, 250 MB/s

Mar 08 00:14:19 preclear_disk_WL20S7J5_20799: Post-Read: dd output: 4357445+0 records in

Mar 08 00:14:19 preclear_disk_WL20S7J5_20799: Post-Read: dd output: 4357445+0 records out

Mar 08 00:14:19 preclear_disk_WL20S7J5_20799: Post-Read: dd output: 9138224496640 bytes (9.1 TB, 8.3 TiB) copied, 36581.5 s, 250 MB/s

Mar 08 00:14:19 preclear_disk_WL20S7J5_20799: Post-Read: dd output: 4358815+0 records in

Mar 08 00:14:19 preclear_disk_WL20S7J5_20799: Post-Read: dd output: 4358814+0 records out

Mar 08 00:14:19 preclear_disk_WL20S7J5_20799: Post-Read: dd output: 9141095497728 bytes (9.1 TB, 8.3 TiB) copied, 36594.3 s, 250 MB/s

Mar 08 00:14:19 preclear_disk_WL20S7J5_20799: Post-Read: dd output: 4360038+0 records in

Mar 08 00:14:19 preclear_disk_WL20S7J5_20799: Post-Read: dd output: 4360037+0 records out

Mar 08 00:14:19 preclear_disk_WL20S7J5_20799: Post-Read: dd output: 9143660314624 bytes (9.1 TB, 8.3 TiB) copied, 36606.1 s, 250 MB/s

Mar 08 00:14:19 preclear_disk_WL20S7J5_20799: Post-Read: dd output: 4361325+0 records in

Mar 08 00:14:19 preclear_disk_WL20S7J5_20799: Post-Read: dd output: 4361324+0 records out

Mar 08 00:14:19 preclear_disk_WL20S7J5_20799: Post-Read: dd output: 9146359349248 bytes (9.1 TB, 8.3 TiB) copied, 36618 s, 250 MB/s

Mar 08 00:14:20 preclear_disk_WL20S7J5_20799: Post-Read: post-read verification failed!

Mar 08 00:14:21 preclear_disk_WL20S7J5_20799: S.M.A.R.T.: Error:

Mar 08 00:14:21 preclear_disk_WL20S7J5_20799: S.M.A.R.T.:

Mar 08 00:14:21 preclear_disk_WL20S7J5_20799: S.M.A.R.T.: ATTRIBUTE               INITIAL NOW  STATUS

Mar 08 00:14:21 preclear_disk_WL20S7J5_20799: S.M.A.R.T.: Reallocated_Sector_Ct   120     120  -Mar 08 00:14:21 preclear_disk_WL20S7J5_20799: S.M.A.R.T.: Power_On_Hours          6391    6443 Up 52

Mar 08 00:14:21 preclear_disk_WL20S7J5_20799: S.M.A.R.T.: Reported_Uncorrect      0       0    -Mar 08 00:14:21 preclear_disk_WL20S7J5_20799: S.M.A.R.T.: Airflow_Temperature_Cel 23      35   Up 12

Mar 08 00:14:21 preclear_disk_WL20S7J5_20799: S.M.A.R.T.: Current_Pending_Sector  0       0    -Mar 08 00:14:21 preclear_disk_WL20S7J5_20799: S.M.A.R.T.: Offline_Uncorrectable   0       0    -Mar 08 00:14:22 preclear_disk_WL20S7J5_20799: S.M.A.R.T.: UDMA_CRC_Error_Count    0       0    -Mar 08 00:14:22 preclear_disk_WL20S7J5_20799: S.M.A.R.T.: Mar 08 00:14:22 preclear_disk_WL20S7J5_20799: error encountered, exiting ...

 

Preclear 2:

 

Mar 12 16:59:59 preclear_disk_WL20S7J5_26333: Post-Read: dd output: 2699491+0 records out

Mar 12 16:59:59 preclear_disk_WL20S7J5_26333: Post-Read: dd output: 5661242949632 bytes (5.7 TB, 5.1 TiB) copied, 21601.7 s, 262 MB/s

Mar 12 16:59:59 preclear_disk_WL20S7J5_26333: Post-Read: dd output: 2700906+0 records in

Mar 12 16:59:59 preclear_disk_WL20S7J5_26333: Post-Read: dd output: 2700905+0 records out

Mar 12 16:59:59 preclear_disk_WL20S7J5_26333: Post-Read: dd output: 5664208322560 bytes (5.7 TB, 5.2 TiB) copied, 21613.5 s, 262 MB/s

Mar 12 16:59:59 preclear_disk_WL20S7J5_26333: Post-Read: dd output: 2702307+0 records in

Mar 12 16:59:59 preclear_disk_WL20S7J5_26333: Post-Read: dd output: 2702306+0 records out

Mar 12 16:59:59 preclear_disk_WL20S7J5_26333: Post-Read: dd output: 5667146432512 bytes (5.7 TB, 5.2 TiB) copied, 21625.3 s, 262 MB/s

Mar 12 16:59:59 preclear_disk_WL20S7J5_26333: Post-Read: dd output: 2703688+0 records in

Mar 12 16:59:59 preclear_disk_WL20S7J5_26333: Post-Read: dd output: 2703687+0 records out

Mar 12 16:59:59 preclear_disk_WL20S7J5_26333: Post-Read: dd output: 5670042599424 bytes (5.7 TB, 5.2 TiB) copied, 21637.2 s, 262 MB/s

Mar 12 16:59:59 preclear_disk_WL20S7J5_26333: Post-Read: dd output: 2705138+0 records in

Mar 12 16:59:59 preclear_disk_WL20S7J5_26333: Post-Read: dd output: 2705137+0 records out

Mar 12 16:59:59 preclear_disk_WL20S7J5_26333: Post-Read: dd output: 5673083469824 bytes (5.7 TB, 5.2 TiB) copied, 21650 s, 262 MB/s

Mar 12 16:59:59 preclear_disk_WL20S7J5_26333: Post-Read: dd output: 2706623+0 records in

Mar 12 16:59:59 preclear_disk_WL20S7J5_26333: Post-Read: dd output: 2706622+0 records out

Mar 12 16:59:59 preclear_disk_WL20S7J5_26333: Post-Read: dd output: 5676197740544 bytes (5.7 TB, 5.2 TiB) copied, 21662.9 s, 262 MB/s

Mar 12 16:59:59 preclear_disk_WL20S7J5_26333: Post-Read: post-read verification failed!

Mar 12 17:00:01 preclear_disk_WL20S7J5_26333: S.M.A.R.T.: Error:

Mar 12 17:00:01 preclear_disk_WL20S7J5_26333: S.M.A.R.T.:

Mar 12 17:00:01 preclear_disk_WL20S7J5_26333: S.M.A.R.T.: ATTRIBUTE               INITIAL NOW  STATUS

Mar 12 17:00:01 preclear_disk_WL20S7J5_26333: S.M.A.R.T.: Reallocated_Sector_Ct   120     128  Up 8

Mar 12 17:00:01 preclear_disk_WL20S7J5_26333: S.M.A.R.T.: Power_On_Hours          6508    6556 Up 48

Mar 12 17:00:01 preclear_disk_WL20S7J5_26333: S.M.A.R.T.: Reported_Uncorrect      0       0    -Mar 12 17:00:01 preclear_disk_WL20S7J5_26333: S.M.A.R.T.: Airflow_Temperature_Cel 31      37   Up 6

Mar 12 17:00:01 preclear_disk_WL20S7J5_26333: S.M.A.R.T.: Current_Pending_Sector  0       0    -Mar 12 17:00:01 preclear_disk_WL20S7J5_26333: S.M.A.R.T.: Offline_Uncorrectable   0       0    -Mar 12 17:00:01 preclear_disk_WL20S7J5_26333: S.M.A.R.T.: UDMA_CRC_Error_Count    0       0    -Mar 12 17:00:01 preclear_disk_WL20S7J5_26333: S.M.A.R.T.: Mar 12 17:00:02 preclear_disk_WL20S7J5_26333: error encountered, exiting ...

 

Edited by djglenn
Link to comment
1 minute ago, Vr2Io said:

I won't waste time and electricity to do that, best got RMA.

 

Would love to, but given its about 14months old, Seagate are telling me its "perfectly fine" as passed the Seatools tests, and the reallocated sectors are minor. I am not sure they recognise PreClear failures and what that could point to as a failure mode.. 

Link to comment
5 minutes ago, djglenn said:

 

Would love to, but given its about 14months old, Seagate are telling me its "perfectly fine" as passed the Seatools tests, and the reallocated sectors are minor. I am not sure they recognise PreClear failures and what that could point to as a failure mode.. 

They only accept Seatools, I will take RMA and state Seatools fail ( even actually not ) and waiting for replacement. I believe they won't perform extend test.

Edited by Vr2Io
  • Thanks 1
Link to comment
21 minutes ago, djglenn said:

 

Would love to, but given its about 14months old, Seagate are telling me its "perfectly fine" as passed the Seatools tests, and the reallocated sectors are minor. I am not sure they recognise PreClear failures and what that could point to as a failure mode.. 

reallocated sectors could only be considered minor if the number is relatively low and is also STABLE.   This last criteria appears to not be met.

  • Thanks 1
Link to comment

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.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.