I had a drive that is 8 years old in a TrueNAS server. I just replaced it today because of too many errors. I put it in my Windows machine and ran short and long test with HD Sentinel and it failed both of those.
But in the general info, it shows 100% health.
Why does a failed drive show 100% health?
- hdsentinel
- Site Admin
- Posts: 3128
- Joined: 2008.07.27. 17:00
- Location: Hungary
- Contact:
Re: Why does a failed drive show 100% health?
Very-very rarely but this may happen. As I remember, found only 2 similar cases, similarly on drives which are relatively old, after the designed lifetime reached.
Generally the drive should record problem(s) into the self-monitoring S.M.A.R.T. data when the appropriate sector accessed (read/written) but as you can see, this did not happen now, so seems the drive did not record the problem(s) yet.
This is why generally extremely important to
- in addition to checking/monitoring the status and the health of the drive (especially when the drive is used for more than 5 years) perform tests to reveal possible issues or confirm that the hard disk drive is still working correctly. As you saw, the internal tests showed problems
- prepare for planned replacement when the drive is near (or over) the end of designed lifetime (when the estimated remaining lifetime is 100 days or lower).
Seems interesting case.
Can you please use Report menu -> Send test report to developer option?
Would be nice to examine the actual drive status, verify the raw S.M.A.R.T. values and check if/how things could be improved, reported differently. Depending on the drive model, firmware, probably we can see minor issues / errors we can report to increase attention in similar situation.
Thanks for your attention!
Generally the drive should record problem(s) into the self-monitoring S.M.A.R.T. data when the appropriate sector accessed (read/written) but as you can see, this did not happen now, so seems the drive did not record the problem(s) yet.
This is why generally extremely important to
- in addition to checking/monitoring the status and the health of the drive (especially when the drive is used for more than 5 years) perform tests to reveal possible issues or confirm that the hard disk drive is still working correctly. As you saw, the internal tests showed problems
- prepare for planned replacement when the drive is near (or over) the end of designed lifetime (when the estimated remaining lifetime is 100 days or lower).
Seems interesting case.
Can you please use Report menu -> Send test report to developer option?
Would be nice to examine the actual drive status, verify the raw S.M.A.R.T. values and check if/how things could be improved, reported differently. Depending on the drive model, firmware, probably we can see minor issues / errors we can report to increase attention in similar situation.
Thanks for your attention!
-
- Posts: 4
- Joined: 2023.08.29. 21:54
Re: Why does a failed drive show 100% health?
Thanks for the response.
I also ran a surface test overnight and it reported 3 bad sectors. Just surprised that the health still shows 100%. I in no way trust this drive for any type of critical data. I was going to discard it, but since it still reads and writes, I might fill it up with documents and JPG's and archive it.
Is there something that I should do to remap the bad sectors before I use it as an archive?
I purchased HD Sentinel last week to test 6 new drives that were going into the NAS to make sure I was getting new drives and that none of them were DOA. With this bad drive showing 100% health, I am no nervous about trusting those same results on the new drive.
I sent the test in as you instructed.
Sincerely,
Kirk
I also ran a surface test overnight and it reported 3 bad sectors. Just surprised that the health still shows 100%. I in no way trust this drive for any type of critical data. I was going to discard it, but since it still reads and writes, I might fill it up with documents and JPG's and archive it.
Is there something that I should do to remap the bad sectors before I use it as an archive?
I purchased HD Sentinel last week to test 6 new drives that were going into the NAS to make sure I was getting new drives and that none of them were DOA. With this bad drive showing 100% health, I am no nervous about trusting those same results on the new drive.
I sent the test in as you instructed.
Sincerely,
Kirk
-
- Posts: 4
- Joined: 2023.08.29. 21:54
Re: Why does a failed drive show 100% health?
Here is the log for the surface test:
Code: Select all
8/29/2023 4:09:52 PM Sequential test, Disk: [2] 3726 GB WDC WD40EFRX-68WT0N0 [WD-WCC4E2VAJD7N] [Read]
8/29/2023 4:10:00 PM ! Error: 23 Data error (cyclic redundancy check)., Sector: 726000
8/29/2023 4:10:16 PM ! Error: 23 Data error (cyclic redundancy check)., Sector: 726376, Block: 0
8/29/2023 4:10:20 PM ! Error: 23 Data error (cyclic redundancy check)., Sector: 726376, Block: 0
8/29/2023 4:10:24 PM ! Error: 23 Data error (cyclic redundancy check)., Sector: 726376, Block: 0
8/29/2023 4:10:27 PM ! Error: 23 Data error (cyclic redundancy check)., Sector: 726377, Block: 0
8/29/2023 4:10:31 PM ! Error: 23 Data error (cyclic redundancy check)., Sector: 726377, Block: 0
8/29/2023 4:10:35 PM ! Error: 23 Data error (cyclic redundancy check)., Sector: 726377, Block: 0
8/29/2023 4:10:38 PM ! Error: 23 Data error (cyclic redundancy check)., Sector: 726378, Block: 0
8/29/2023 4:10:42 PM ! Error: 23 Data error (cyclic redundancy check)., Sector: 726378, Block: 0
8/29/2023 4:10:46 PM ! Error: 23 Data error (cyclic redundancy check)., Sector: 726378, Block: 0
8/29/2023 4:10:49 PM ! Error: 23 Data error (cyclic redundancy check)., Sector: 726379, Block: 0
8/29/2023 4:10:53 PM ! Error: 23 Data error (cyclic redundancy check)., Sector: 726379, Block: 0
8/29/2023 4:10:57 PM ! Error: 23 Data error (cyclic redundancy check)., Sector: 726379, Block: 0
8/29/2023 4:11:01 PM ! Error: 23 Data error (cyclic redundancy check)., Sector: 726380, Block: 0
8/29/2023 4:11:04 PM ! Error: 23 Data error (cyclic redundancy check)., Sector: 726380, Block: 0
8/29/2023 4:11:08 PM ! Error: 23 Data error (cyclic redundancy check)., Sector: 726380, Block: 0
8/29/2023 4:11:12 PM ! Error: 23 Data error (cyclic redundancy check)., Sector: 726381, Block: 0
8/29/2023 4:11:15 PM ! Error: 23 Data error (cyclic redundancy check)., Sector: 726381, Block: 0
8/29/2023 4:11:19 PM ! Error: 23 Data error (cyclic redundancy check)., Sector: 726381, Block: 0
8/29/2023 4:11:23 PM ! Error: 23 Data error (cyclic redundancy check)., Sector: 726382, Block: 0
8/29/2023 4:11:27 PM ! Error: 23 Data error (cyclic redundancy check)., Sector: 726382, Block: 0
8/29/2023 4:11:30 PM ! Error: 23 Data error (cyclic redundancy check)., Sector: 726382, Block: 0
8/29/2023 4:11:34 PM ! Error: 23 Data error (cyclic redundancy check)., Sector: 726383, Block: 0
8/29/2023 4:11:38 PM ! Error: 23 Data error (cyclic redundancy check)., Sector: 726383, Block: 0
8/29/2023 4:11:41 PM ! Error: 23 Data error (cyclic redundancy check)., Sector: 726383, Block: 0
8/29/2023 4:11:49 PM ! Error: 23 Data error (cyclic redundancy check)., Sector: 730000, Block: 0
8/29/2023 4:11:53 PM ! Error: 23 Data error (cyclic redundancy check)., Sector: 730000, Block: 0
8/29/2023 4:11:56 PM ! Error: 23 Data error (cyclic redundancy check)., Sector: 730000, Block: 0
8/29/2023 4:12:00 PM ! Error: 23 Data error (cyclic redundancy check)., Sector: 730001, Block: 0
8/29/2023 4:12:04 PM ! Error: 23 Data error (cyclic redundancy check)., Sector: 730001, Block: 0
8/29/2023 4:12:08 PM ! Error: 23 Data error (cyclic redundancy check)., Sector: 730001, Block: 0
8/29/2023 4:12:11 PM ! Error: 23 Data error (cyclic redundancy check)., Sector: 730002, Block: 0
8/29/2023 4:12:15 PM ! Error: 23 Data error (cyclic redundancy check)., Sector: 730002, Block: 0
8/29/2023 4:12:19 PM ! Error: 23 Data error (cyclic redundancy check)., Sector: 730002, Block: 0
8/29/2023 4:12:22 PM ! Error: 23 Data error (cyclic redundancy check)., Sector: 730003, Block: 0
8/29/2023 4:12:26 PM ! Error: 23 Data error (cyclic redundancy check)., Sector: 730003, Block: 0
8/29/2023 4:12:30 PM ! Error: 23 Data error (cyclic redundancy check)., Sector: 730003, Block: 0
8/29/2023 4:12:33 PM ! Error: 23 Data error (cyclic redundancy check)., Sector: 730004, Block: 0
8/29/2023 4:12:37 PM ! Error: 23 Data error (cyclic redundancy check)., Sector: 730004, Block: 0
8/29/2023 4:12:41 PM ! Error: 23 Data error (cyclic redundancy check)., Sector: 730004, Block: 0
8/29/2023 4:12:45 PM ! Error: 23 Data error (cyclic redundancy check)., Sector: 730005, Block: 0
8/29/2023 4:12:48 PM ! Error: 23 Data error (cyclic redundancy check)., Sector: 730005, Block: 0
8/29/2023 4:12:52 PM ! Error: 23 Data error (cyclic redundancy check)., Sector: 730005, Block: 0
8/29/2023 4:12:56 PM ! Error: 23 Data error (cyclic redundancy check)., Sector: 730006, Block: 0
8/29/2023 4:12:59 PM ! Error: 23 Data error (cyclic redundancy check)., Sector: 730006, Block: 0
8/29/2023 4:13:03 PM ! Error: 23 Data error (cyclic redundancy check)., Sector: 730006, Block: 0
8/29/2023 4:13:07 PM ! Error: 23 Data error (cyclic redundancy check)., Sector: 730007, Block: 0
8/29/2023 4:13:11 PM ! Error: 23 Data error (cyclic redundancy check)., Sector: 730007, Block: 0
8/29/2023 4:13:14 PM ! Error: 23 Data error (cyclic redundancy check)., Sector: 730007, Block: 0
8/29/2023 4:13:22 PM ! Error: 23 Data error (cyclic redundancy check)., Sector: 733624, Block: 0
8/29/2023 4:13:25 PM ! Error: 23 Data error (cyclic redundancy check)., Sector: 733624, Block: 0
8/29/2023 4:13:29 PM ! Error: 23 Data error (cyclic redundancy check)., Sector: 733624, Block: 0
8/29/2023 4:13:33 PM ! Error: 23 Data error (cyclic redundancy check)., Sector: 733625, Block: 0
8/29/2023 4:13:36 PM ! Error: 23 Data error (cyclic redundancy check)., Sector: 733625, Block: 0
8/29/2023 4:13:40 PM ! Error: 23 Data error (cyclic redundancy check)., Sector: 733625, Block: 0
8/29/2023 4:13:44 PM ! Error: 23 Data error (cyclic redundancy check)., Sector: 733626, Block: 0
8/29/2023 4:13:48 PM ! Error: 23 Data error (cyclic redundancy check)., Sector: 733626, Block: 0
8/29/2023 4:13:51 PM ! Error: 23 Data error (cyclic redundancy check)., Sector: 733626, Block: 0
8/29/2023 4:13:55 PM ! Error: 23 Data error (cyclic redundancy check)., Sector: 733627, Block: 0
8/29/2023 4:13:59 PM ! Error: 23 Data error (cyclic redundancy check)., Sector: 733627, Block: 0
8/29/2023 4:14:02 PM ! Error: 23 Data error (cyclic redundancy check)., Sector: 733627, Block: 0
8/29/2023 4:14:06 PM ! Error: 23 Data error (cyclic redundancy check)., Sector: 733628, Block: 0
8/29/2023 4:14:10 PM ! Error: 23 Data error (cyclic redundancy check)., Sector: 733628, Block: 0
8/29/2023 4:14:13 PM ! Error: 23 Data error (cyclic redundancy check)., Sector: 733628, Block: 0
8/29/2023 4:14:17 PM ! Error: 23 Data error (cyclic redundancy check)., Sector: 733629, Block: 0
8/29/2023 4:14:21 PM ! Error: 23 Data error (cyclic redundancy check)., Sector: 733629, Block: 0
8/29/2023 4:14:25 PM ! Error: 23 Data error (cyclic redundancy check)., Sector: 733629, Block: 0
8/29/2023 4:14:28 PM ! Error: 23 Data error (cyclic redundancy check)., Sector: 733630, Block: 0
8/29/2023 4:14:32 PM ! Error: 23 Data error (cyclic redundancy check)., Sector: 733630, Block: 0
8/29/2023 4:14:36 PM ! Error: 23 Data error (cyclic redundancy check)., Sector: 733630, Block: 0
8/29/2023 4:14:39 PM ! Error: 23 Data error (cyclic redundancy check)., Sector: 733631, Block: 0
8/29/2023 4:14:43 PM ! Error: 23 Data error (cyclic redundancy check)., Sector: 733631, Block: 0
8/29/2023 4:14:47 PM ! Error: 23 Data error (cyclic redundancy check)., Sector: 733631, Block: 0
8/29/2023 4:14:54 PM ! Error: 23 Data error (cyclic redundancy check)., Sector: 737248, Block: 0
8/29/2023 4:14:58 PM ! Error: 23 Data error (cyclic redundancy check)., Sector: 737248, Block: 0
8/29/2023 4:15:02 PM ! Error: 23 Data error (cyclic redundancy check)., Sector: 737248, Block: 0
8/29/2023 4:15:05 PM ! Error: 23 Data error (cyclic redundancy check)., Sector: 737249, Block: 0
8/29/2023 4:15:09 PM ! Error: 23 Data error (cyclic redundancy check)., Sector: 737249, Block: 0
8/29/2023 4:15:13 PM ! Error: 23 Data error (cyclic redundancy check)., Sector: 737249, Block: 0
8/29/2023 4:15:16 PM ! Error: 23 Data error (cyclic redundancy check)., Sector: 737250, Block: 0
8/29/2023 4:15:20 PM ! Error: 23 Data error (cyclic redundancy check)., Sector: 737250, Block: 0
8/29/2023 4:15:24 PM ! Error: 23 Data error (cyclic redundancy check)., Sector: 737250, Block: 0
8/29/2023 4:15:28 PM ! Error: 23 Data error (cyclic redundancy check)., Sector: 737251, Block: 0
8/29/2023 4:15:31 PM ! Error: 23 Data error (cyclic redundancy check)., Sector: 737251, Block: 0
8/29/2023 4:15:35 PM ! Error: 23 Data error (cyclic redundancy check)., Sector: 737251, Block: 0
8/29/2023 4:15:39 PM ! Error: 23 Data error (cyclic redundancy check)., Sector: 737252, Block: 0
8/29/2023 4:15:42 PM ! Error: 23 Data error (cyclic redundancy check)., Sector: 737252, Block: 0
8/29/2023 4:15:46 PM ! Error: 23 Data error (cyclic redundancy check)., Sector: 737252, Block: 0
8/29/2023 4:15:50 PM ! Error: 23 Data error (cyclic redundancy check)., Sector: 737253, Block: 0
8/29/2023 4:15:53 PM ! Error: 23 Data error (cyclic redundancy check)., Sector: 737253, Block: 0
8/29/2023 4:15:57 PM ! Error: 23 Data error (cyclic redundancy check)., Sector: 737253, Block: 0
8/29/2023 4:16:01 PM ! Error: 23 Data error (cyclic redundancy check)., Sector: 737254, Block: 0
8/29/2023 4:16:05 PM ! Error: 23 Data error (cyclic redundancy check)., Sector: 737254, Block: 0
8/29/2023 4:16:08 PM ! Error: 23 Data error (cyclic redundancy check)., Sector: 737254, Block: 0
8/29/2023 4:16:12 PM ! Error: 23 Data error (cyclic redundancy check)., Sector: 737255, Block: 0
8/29/2023 4:16:16 PM ! Error: 23 Data error (cyclic redundancy check)., Sector: 737255, Block: 0
8/29/2023 4:16:19 PM ! Error: 23 Data error (cyclic redundancy check)., Sector: 737255, Block: 0
8/29/2023 4:16:27 PM ! Error: 23 Data error (cyclic redundancy check)., Sector: 741816, Block: 0
8/29/2023 4:16:31 PM ! Error: 23 Data error (cyclic redundancy check)., Sector: 741816, Block: 0
8/29/2023 4:16:35 PM ! Error: 23 Data error (cyclic redundancy check)., Sector: 741816, Block: 0
8/29/2023 4:16:38 PM ! Error: 23 Data error (cyclic redundancy check)., Sector: 741817, Block: 0
8/29/2023 4:16:42 PM ! Error: 23 Data error (cyclic redundancy check)., Sector: 741817, Block: 0
8/29/2023 4:16:46 PM ! Error: 23 Data error (cyclic redundancy check)., Sector: 741817, Block: 0
8/29/2023 4:16:50 PM ! Error: 23 Data error (cyclic redundancy check)., Sector: 741818, Block: 0
8/29/2023 4:16:53 PM ! Error: 23 Data error (cyclic redundancy check)., Sector: 741818, Block: 0
8/29/2023 4:16:57 PM ! Error: 23 Data error (cyclic redundancy check)., Sector: 741818, Block: 0
8/29/2023 4:17:01 PM ! Error: 23 Data error (cyclic redundancy check)., Sector: 741819, Block: 0
8/29/2023 4:17:04 PM ! Error: 23 Data error (cyclic redundancy check)., Sector: 741819, Block: 0
8/29/2023 4:17:08 PM ! Error: 23 Data error (cyclic redundancy check)., Sector: 741819, Block: 0
8/29/2023 4:17:12 PM ! Error: 23 Data error (cyclic redundancy check)., Sector: 741820, Block: 0
8/29/2023 4:17:15 PM ! Error: 23 Data error (cyclic redundancy check)., Sector: 741820, Block: 0
8/29/2023 4:17:19 PM ! Error: 23 Data error (cyclic redundancy check)., Sector: 741820, Block: 0
8/29/2023 4:17:23 PM ! Error: 23 Data error (cyclic redundancy check)., Sector: 741821, Block: 0
8/29/2023 4:17:27 PM ! Error: 23 Data error (cyclic redundancy check)., Sector: 741821, Block: 0
8/29/2023 4:17:30 PM ! Error: 23 Data error (cyclic redundancy check)., Sector: 741821, Block: 0
8/29/2023 4:17:34 PM ! Error: 23 Data error (cyclic redundancy check)., Sector: 741822, Block: 0
8/29/2023 4:17:38 PM ! Error: 23 Data error (cyclic redundancy check)., Sector: 741822, Block: 0
8/29/2023 4:17:41 PM ! Error: 23 Data error (cyclic redundancy check)., Sector: 741822, Block: 0
8/29/2023 4:17:45 PM ! Error: 23 Data error (cyclic redundancy check)., Sector: 741823, Block: 0
8/29/2023 4:17:49 PM ! Error: 23 Data error (cyclic redundancy check)., Sector: 741823, Block: 0
8/29/2023 4:17:53 PM ! Error: 23 Data error (cyclic redundancy check)., Sector: 741823, Block: 0
8/29/2023 4:18:05 PM ! Error: 23 Data error (cyclic redundancy check)., Sector: 760376, Block: 0
8/29/2023 4:18:09 PM ! Error: 23 Data error (cyclic redundancy check)., Sector: 760376, Block: 0
8/29/2023 4:18:13 PM ! Error: 23 Data error (cyclic redundancy check)., Sector: 760376, Block: 0
8/29/2023 4:18:17 PM ! Error: 23 Data error (cyclic redundancy check)., Sector: 760377, Block: 0
8/29/2023 4:18:20 PM ! Error: 23 Data error (cyclic redundancy check)., Sector: 760377, Block: 0
8/29/2023 4:18:24 PM ! Error: 23 Data error (cyclic redundancy check)., Sector: 760377, Block: 0
8/29/2023 4:18:28 PM ! Error: 23 Data error (cyclic redundancy check)., Sector: 760378, Block: 0
8/29/2023 4:18:31 PM ! Error: 23 Data error (cyclic redundancy check)., Sector: 760378, Block: 0
8/29/2023 4:18:35 PM ! Error: 23 Data error (cyclic redundancy check)., Sector: 760378, Block: 0
8/29/2023 4:18:39 PM ! Error: 23 Data error (cyclic redundancy check)., Sector: 760379, Block: 0
8/29/2023 4:18:43 PM ! Error: 23 Data error (cyclic redundancy check)., Sector: 760379, Block: 0
8/29/2023 4:18:46 PM ! Error: 23 Data error (cyclic redundancy check)., Sector: 760379, Block: 0
8/29/2023 4:18:50 PM ! Error: 23 Data error (cyclic redundancy check)., Sector: 760380, Block: 0
8/29/2023 4:18:54 PM ! Error: 23 Data error (cyclic redundancy check)., Sector: 760380, Block: 0
8/29/2023 4:18:57 PM ! Error: 23 Data error (cyclic redundancy check)., Sector: 760380, Block: 0
8/29/2023 4:19:01 PM ! Error: 23 Data error (cyclic redundancy check)., Sector: 760381, Block: 0
8/29/2023 4:19:05 PM ! Error: 23 Data error (cyclic redundancy check)., Sector: 760381, Block: 0
8/29/2023 4:19:08 PM ! Error: 23 Data error (cyclic redundancy check)., Sector: 760381, Block: 0
8/29/2023 4:19:12 PM ! Error: 23 Data error (cyclic redundancy check)., Sector: 760382, Block: 0
8/29/2023 4:19:16 PM ! Error: 23 Data error (cyclic redundancy check)., Sector: 760382, Block: 0
8/29/2023 4:19:20 PM ! Error: 23 Data error (cyclic redundancy check)., Sector: 760382, Block: 0
8/29/2023 4:19:23 PM ! Error: 23 Data error (cyclic redundancy check)., Sector: 760383, Block: 0
8/29/2023 4:19:27 PM ! Error: 23 Data error (cyclic redundancy check)., Sector: 760383, Block: 0
8/29/2023 4:19:31 PM ! Error: 23 Data error (cyclic redundancy check)., Sector: 760383, Block: 0
8/29/2023 4:19:39 PM ! Error: 23 Data error (cyclic redundancy check)., Sector: 764000, Block: 0
8/29/2023 4:19:42 PM ! Error: 23 Data error (cyclic redundancy check)., Sector: 764000, Block: 0
8/29/2023 4:19:46 PM ! Error: 23 Data error (cyclic redundancy check)., Sector: 764000, Block: 0
8/29/2023 4:19:50 PM ! Error: 23 Data error (cyclic redundancy check)., Sector: 764001, Block: 0
8/29/2023 4:19:53 PM ! Error: 23 Data error (cyclic redundancy check)., Sector: 764001, Block: 0
8/29/2023 4:19:57 PM ! Error: 23 Data error (cyclic redundancy check)., Sector: 764001, Block: 0
8/29/2023 4:19:58 PM ! Error: Unrecoverable Error Block: 0
8/29/2023 4:20:05 PM ! Error: 23 Data error (cyclic redundancy check)., Sector: 782120, Block: 1
8/29/2023 4:20:08 PM ! Error: 23 Data error (cyclic redundancy check)., Sector: 782120, Block: 1
8/29/2023 4:20:12 PM ! Error: 23 Data error (cyclic redundancy check)., Sector: 782120, Block: 1
8/29/2023 4:20:16 PM ! Error: 23 Data error (cyclic redundancy check)., Sector: 782121, Block: 1
8/29/2023 4:20:19 PM ! Error: 23 Data error (cyclic redundancy check)., Sector: 782121, Block: 1
8/29/2023 4:20:23 PM ! Error: 23 Data error (cyclic redundancy check)., Sector: 782121, Block: 1
8/29/2023 4:20:27 PM ! Error: 23 Data error (cyclic redundancy check)., Sector: 782122, Block: 1
8/29/2023 4:20:31 PM ! Error: 23 Data error (cyclic redundancy check)., Sector: 782122, Block: 1
8/29/2023 4:20:34 PM ! Error: 23 Data error (cyclic redundancy check)., Sector: 782122, Block: 1
8/29/2023 4:20:38 PM ! Error: 23 Data error (cyclic redundancy check)., Sector: 782123, Block: 1
8/29/2023 4:20:42 PM ! Error: 23 Data error (cyclic redundancy check)., Sector: 782123, Block: 1
8/29/2023 4:20:45 PM ! Error: 23 Data error (cyclic redundancy check)., Sector: 782123, Block: 1
8/29/2023 4:20:49 PM ! Error: 23 Data error (cyclic redundancy check)., Sector: 782124, Block: 1
8/29/2023 4:20:53 PM ! Error: 23 Data error (cyclic redundancy check)., Sector: 782124, Block: 1
8/29/2023 4:20:57 PM ! Error: 23 Data error (cyclic redundancy check)., Sector: 782124, Block: 1
8/29/2023 4:21:00 PM ! Error: 23 Data error (cyclic redundancy check)., Sector: 782125, Block: 1
8/29/2023 4:21:04 PM ! Error: 23 Data error (cyclic redundancy check)., Sector: 782125, Block: 1
8/29/2023 4:21:08 PM ! Error: 23 Data error (cyclic redundancy check)., Sector: 782125, Block: 1
8/29/2023 4:21:11 PM ! Error: 23 Data error (cyclic redundancy check)., Sector: 782126, Block: 1
8/29/2023 4:21:15 PM ! Error: 23 Data error (cyclic redundancy check)., Sector: 782126, Block: 1
8/29/2023 4:21:19 PM ! Error: 23 Data error (cyclic redundancy check)., Sector: 782126, Block: 1
8/29/2023 4:21:22 PM ! Error: 23 Data error (cyclic redundancy check)., Sector: 782127, Block: 1
8/29/2023 4:21:26 PM ! Error: 23 Data error (cyclic redundancy check)., Sector: 782127, Block: 1
8/29/2023 4:21:30 PM ! Error: 23 Data error (cyclic redundancy check)., Sector: 782127, Block: 1
8/29/2023 4:21:37 PM ! Error: 23 Data error (cyclic redundancy check)., Sector: 785744, Block: 1
8/29/2023 4:21:41 PM ! Error: 23 Data error (cyclic redundancy check)., Sector: 785744, Block: 1
8/29/2023 4:21:45 PM ! Error: 23 Data error (cyclic redundancy check)., Sector: 785744, Block: 1
8/29/2023 4:21:48 PM ! Error: 23 Data error (cyclic redundancy check)., Sector: 785745, Block: 1
8/29/2023 4:21:52 PM ! Error: 23 Data error (cyclic redundancy check)., Sector: 785745, Block: 1
8/29/2023 4:21:56 PM ! Error: 23 Data error (cyclic redundancy check)., Sector: 785745, Block: 1
8/29/2023 4:22:00 PM ! Error: 23 Data error (cyclic redundancy check)., Sector: 785746, Block: 1
8/29/2023 4:22:03 PM ! Error: 23 Data error (cyclic redundancy check)., Sector: 785746, Block: 1
8/29/2023 4:22:07 PM ! Error: 23 Data error (cyclic redundancy check)., Sector: 785746, Block: 1
8/29/2023 4:22:11 PM ! Error: 23 Data error (cyclic redundancy check)., Sector: 785747, Block: 1
8/29/2023 4:22:14 PM ! Error: 23 Data error (cyclic redundancy check)., Sector: 785747, Block: 1
8/29/2023 4:22:18 PM ! Error: 23 Data error (cyclic redundancy check)., Sector: 785747, Block: 1
8/29/2023 4:22:22 PM ! Error: 23 Data error (cyclic redundancy check)., Sector: 785748, Block: 1
8/29/2023 4:22:26 PM ! Error: 23 Data error (cyclic redundancy check)., Sector: 785748, Block: 1
8/29/2023 4:22:29 PM ! Error: 23 Data error (cyclic redundancy check)., Sector: 785748, Block: 1
8/29/2023 4:22:33 PM ! Error: 23 Data error (cyclic redundancy check)., Sector: 785749, Block: 1
8/29/2023 4:22:37 PM ! Error: 23 Data error (cyclic redundancy check)., Sector: 785749, Block: 1
8/29/2023 4:22:40 PM ! Error: 23 Data error (cyclic redundancy check)., Sector: 785749, Block: 1
8/29/2023 4:22:44 PM ! Error: 23 Data error (cyclic redundancy check)., Sector: 785750, Block: 1
8/29/2023 4:22:48 PM ! Error: 23 Data error (cyclic redundancy check)., Sector: 785750, Block: 1
8/29/2023 4:22:52 PM ! Error: 23 Data error (cyclic redundancy check)., Sector: 785750, Block: 1
8/29/2023 4:22:55 PM ! Error: 23 Data error (cyclic redundancy check)., Sector: 785751, Block: 1
8/29/2023 4:22:59 PM ! Error: 23 Data error (cyclic redundancy check)., Sector: 785751, Block: 1
8/29/2023 4:23:03 PM ! Error: 23 Data error (cyclic redundancy check)., Sector: 785751, Block: 1
8/29/2023 4:23:10 PM ! Error: 23 Data error (cyclic redundancy check)., Sector: 789368, Block: 1
8/29/2023 4:23:14 PM ! Error: 23 Data error (cyclic redundancy check)., Sector: 789368, Block: 1
8/29/2023 4:23:18 PM ! Error: 23 Data error (cyclic redundancy check)., Sector: 789368, Block: 1
8/29/2023 4:23:21 PM ! Error: 23 Data error (cyclic redundancy check)., Sector: 789369, Block: 1
8/29/2023 4:23:25 PM ! Error: 23 Data error (cyclic redundancy check)., Sector: 789369, Block: 1
8/29/2023 4:23:29 PM ! Error: 23 Data error (cyclic redundancy check)., Sector: 789369, Block: 1
8/29/2023 4:23:32 PM ! Error: 23 Data error (cyclic redundancy check)., Sector: 789370, Block: 1
8/29/2023 4:23:36 PM ! Error: 23 Data error (cyclic redundancy check)., Sector: 789370, Block: 1
8/29/2023 4:23:40 PM ! Error: 23 Data error (cyclic redundancy check)., Sector: 789370, Block: 1
8/29/2023 4:23:44 PM ! Error: 23 Data error (cyclic redundancy check)., Sector: 789371, Block: 1
8/29/2023 4:23:47 PM ! Error: 23 Data error (cyclic redundancy check)., Sector: 789371, Block: 1
8/29/2023 4:23:51 PM ! Error: 23 Data error (cyclic redundancy check)., Sector: 789371, Block: 1
8/29/2023 4:23:55 PM ! Error: 23 Data error (cyclic redundancy check)., Sector: 789372, Block: 1
8/29/2023 4:23:58 PM ! Error: 23 Data error (cyclic redundancy check)., Sector: 789372, Block: 1
8/29/2023 4:24:02 PM ! Error: 23 Data error (cyclic redundancy check)., Sector: 789372, Block: 1
8/29/2023 4:24:06 PM ! Error: 23 Data error (cyclic redundancy check)., Sector: 789373, Block: 1
8/29/2023 4:24:09 PM ! Error: 23 Data error (cyclic redundancy check)., Sector: 789373, Block: 1
8/29/2023 4:24:13 PM ! Error: 23 Data error (cyclic redundancy check)., Sector: 789373, Block: 1
8/29/2023 4:24:17 PM ! Error: 23 Data error (cyclic redundancy check)., Sector: 789374, Block: 1
8/29/2023 4:24:21 PM ! Error: 23 Data error (cyclic redundancy check)., Sector: 789374, Block: 1
8/29/2023 4:24:24 PM ! Error: 23 Data error (cyclic redundancy check)., Sector: 789374, Block: 1
8/29/2023 4:24:28 PM ! Error: 23 Data error (cyclic redundancy check)., Sector: 789375, Block: 1
8/29/2023 4:24:32 PM ! Error: 23 Data error (cyclic redundancy check)., Sector: 789375, Block: 1
8/29/2023 4:24:35 PM ! Error: 23 Data error (cyclic redundancy check)., Sector: 789375, Block: 1
8/29/2023 4:24:43 PM ! Error: 23 Data error (cyclic redundancy check)., Sector: 797056, Block: 1
8/29/2023 4:24:47 PM ! Error: 23 Data error (cyclic redundancy check)., Sector: 797056, Block: 1
8/29/2023 4:24:50 PM ! Error: 23 Data error (cyclic redundancy check)., Sector: 797056, Block: 1
8/29/2023 4:24:54 PM ! Error: 23 Data error (cyclic redundancy check)., Sector: 797057, Block: 1
8/29/2023 4:24:58 PM ! Error: 23 Data error (cyclic redundancy check)., Sector: 797057, Block: 1
8/29/2023 4:25:02 PM ! Error: 23 Data error (cyclic redundancy check)., Sector: 797057, Block: 1
8/29/2023 4:25:05 PM ! Error: 23 Data error (cyclic redundancy check)., Sector: 797058, Block: 1
8/29/2023 4:25:09 PM ! Error: 23 Data error (cyclic redundancy check)., Sector: 797058, Block: 1
8/29/2023 4:25:13 PM ! Error: 23 Data error (cyclic redundancy check)., Sector: 797058, Block: 1
8/29/2023 4:25:16 PM ! Error: 23 Data error (cyclic redundancy check)., Sector: 797059, Block: 1
8/29/2023 4:25:20 PM ! Error: 23 Data error (cyclic redundancy check)., Sector: 797059, Block: 1
8/29/2023 4:25:24 PM ! Error: 23 Data error (cyclic redundancy check)., Sector: 797059, Block: 1
8/29/2023 4:25:27 PM ! Error: 23 Data error (cyclic redundancy check)., Sector: 797060, Block: 1
8/29/2023 4:25:31 PM ! Error: 23 Data error (cyclic redundancy check)., Sector: 797060, Block: 1
8/29/2023 4:25:35 PM ! Error: 23 Data error (cyclic redundancy check)., Sector: 797060, Block: 1
8/29/2023 4:25:39 PM ! Error: 23 Data error (cyclic redundancy check)., Sector: 797061, Block: 1
8/29/2023 4:25:42 PM ! Error: 23 Data error (cyclic redundancy check)., Sector: 797061, Block: 1
8/29/2023 4:25:46 PM ! Error: 23 Data error (cyclic redundancy check)., Sector: 797061, Block: 1
8/29/2023 4:25:50 PM ! Error: 23 Data error (cyclic redundancy check)., Sector: 797062, Block: 1
8/29/2023 4:25:53 PM ! Error: 23 Data error (cyclic redundancy check)., Sector: 797062, Block: 1
8/29/2023 4:25:57 PM ! Error: 23 Data error (cyclic redundancy check)., Sector: 797062, Block: 1
8/29/2023 4:26:01 PM ! Error: 23 Data error (cyclic redundancy check)., Sector: 797063, Block: 1
8/29/2023 4:26:05 PM ! Error: 23 Data error (cyclic redundancy check)., Sector: 797063, Block: 1
8/29/2023 4:26:08 PM ! Error: 23 Data error (cyclic redundancy check)., Sector: 797063, Block: 1
8/29/2023 4:26:17 PM ! Error: 23 Data error (cyclic redundancy check)., Sector: 800680, Block: 1
8/29/2023 4:26:20 PM ! Error: 23 Data error (cyclic redundancy check)., Sector: 800680, Block: 1
8/29/2023 4:26:24 PM ! Error: 23 Data error (cyclic redundancy check)., Sector: 800680, Block: 1
8/29/2023 4:26:28 PM ! Error: 23 Data error (cyclic redundancy check)., Sector: 800681, Block: 1
8/29/2023 4:26:31 PM ! Error: 23 Data error (cyclic redundancy check)., Sector: 800681, Block: 1
8/29/2023 4:26:35 PM ! Error: 23 Data error (cyclic redundancy check)., Sector: 800681, Block: 1
8/29/2023 4:26:39 PM ! Error: 23 Data error (cyclic redundancy check)., Sector: 800682, Block: 1
8/29/2023 4:26:42 PM ! Error: 23 Data error (cyclic redundancy check)., Sector: 800682, Block: 1
8/29/2023 4:26:46 PM ! Error: 23 Data error (cyclic redundancy check)., Sector: 800682, Block: 1
8/29/2023 4:26:50 PM ! Error: 23 Data error (cyclic redundancy check)., Sector: 800683, Block: 1
8/29/2023 4:26:54 PM ! Error: 23 Data error (cyclic redundancy check)., Sector: 800683, Block: 1
8/29/2023 4:26:57 PM ! Error: 23 Data error (cyclic redundancy check)., Sector: 800683, Block: 1
8/29/2023 4:27:01 PM ! Error: 23 Data error (cyclic redundancy check)., Sector: 800684, Block: 1
8/29/2023 4:27:05 PM ! Error: 23 Data error (cyclic redundancy check)., Sector: 800684, Block: 1
8/29/2023 4:27:08 PM ! Error: 23 Data error (cyclic redundancy check)., Sector: 800684, Block: 1
8/29/2023 4:27:12 PM ! Error: 23 Data error (cyclic redundancy check)., Sector: 800685, Block: 1
8/29/2023 4:27:16 PM ! Error: 23 Data error (cyclic redundancy check)., Sector: 800685, Block: 1
8/29/2023 4:27:20 PM ! Error: 23 Data error (cyclic redundancy check)., Sector: 800685, Block: 1
8/29/2023 4:27:23 PM ! Error: 23 Data error (cyclic redundancy check)., Sector: 800686, Block: 1
8/29/2023 4:27:27 PM ! Error: 23 Data error (cyclic redundancy check)., Sector: 800686, Block: 1
8/29/2023 4:27:31 PM ! Error: 23 Data error (cyclic redundancy check)., Sector: 800686, Block: 1
8/29/2023 4:27:34 PM ! Error: 23 Data error (cyclic redundancy check)., Sector: 800687, Block: 1
8/29/2023 4:27:38 PM ! Error: 23 Data error (cyclic redundancy check)., Sector: 800687, Block: 1
8/29/2023 4:27:42 PM ! Error: 23 Data error (cyclic redundancy check)., Sector: 800687, Block: 1
8/29/2023 4:27:50 PM ! Error: 23 Data error (cyclic redundancy check)., Sector: 804304, Block: 1
8/29/2023 4:27:54 PM ! Error: 23 Data error (cyclic redundancy check)., Sector: 804304, Block: 1
8/29/2023 4:27:58 PM ! Error: 23 Data error (cyclic redundancy check)., Sector: 804304, Block: 1
8/29/2023 4:28:01 PM ! Error: 23 Data error (cyclic redundancy check)., Sector: 804305, Block: 1
8/29/2023 4:28:05 PM ! Error: 23 Data error (cyclic redundancy check)., Sector: 804305, Block: 1
8/29/2023 4:28:09 PM ! Error: 23 Data error (cyclic redundancy check)., Sector: 804305, Block: 1
8/29/2023 4:28:12 PM ! Error: 23 Data error (cyclic redundancy check)., Sector: 804306, Block: 1
8/29/2023 4:28:16 PM ! Error: 23 Data error (cyclic redundancy check)., Sector: 804306, Block: 1
8/29/2023 4:28:20 PM ! Error: 23 Data error (cyclic redundancy check)., Sector: 804306, Block: 1
8/29/2023 4:28:24 PM ! Error: 23 Data error (cyclic redundancy check)., Sector: 804307, Block: 1
8/29/2023 4:28:27 PM ! Error: 23 Data error (cyclic redundancy check)., Sector: 804307, Block: 1
8/29/2023 4:28:31 PM ! Error: 23 Data error (cyclic redundancy check)., Sector: 804307, Block: 1
8/29/2023 4:28:35 PM ! Error: 23 Data error (cyclic redundancy check)., Sector: 804308, Block: 1
8/29/2023 4:28:38 PM ! Error: 23 Data error (cyclic redundancy check)., Sector: 804308, Block: 1
8/29/2023 4:28:42 PM ! Error: 23 Data error (cyclic redundancy check)., Sector: 804308, Block: 1
8/29/2023 4:28:46 PM ! Error: 23 Data error (cyclic redundancy check)., Sector: 804309, Block: 1
8/29/2023 4:28:50 PM ! Error: 23 Data error (cyclic redundancy check)., Sector: 804309, Block: 1
8/29/2023 4:28:53 PM ! Error: 23 Data error (cyclic redundancy check)., Sector: 804309, Block: 1
8/29/2023 4:28:57 PM ! Error: 23 Data error (cyclic redundancy check)., Sector: 804310, Block: 1
8/29/2023 4:29:01 PM ! Error: 23 Data error (cyclic redundancy check)., Sector: 804310, Block: 1
8/29/2023 4:29:04 PM ! Error: 23 Data error (cyclic redundancy check)., Sector: 804310, Block: 1
8/29/2023 4:29:08 PM ! Error: 23 Data error (cyclic redundancy check)., Sector: 804311, Block: 1
8/29/2023 4:29:12 PM ! Error: 23 Data error (cyclic redundancy check)., Sector: 804311, Block: 1
8/29/2023 4:29:15 PM ! Error: 23 Data error (cyclic redundancy check)., Sector: 804311, Block: 1
8/29/2023 4:29:24 PM ! Error: 23 Data error (cyclic redundancy check)., Sector: 807928, Block: 1
8/29/2023 4:29:27 PM ! Error: 23 Data error (cyclic redundancy check)., Sector: 807928, Block: 1
8/29/2023 4:29:31 PM ! Error: 23 Data error (cyclic redundancy check)., Sector: 807928, Block: 1
8/29/2023 4:29:35 PM ! Error: 23 Data error (cyclic redundancy check)., Sector: 807929, Block: 1
8/29/2023 4:29:38 PM ! Error: 23 Data error (cyclic redundancy check)., Sector: 807929, Block: 1
8/29/2023 4:29:42 PM ! Error: 23 Data error (cyclic redundancy check)., Sector: 807929, Block: 1
8/29/2023 4:29:43 PM ! Error: Unrecoverable Error Block: 1
8/29/2023 4:29:56 PM ! Error: 23 Data error (cyclic redundancy check)., Sector: 3457592, Block: 4
8/29/2023 4:29:59 PM ! Error: 23 Data error (cyclic redundancy check)., Sector: 3457592, Block: 4
8/29/2023 4:30:03 PM ! Error: 23 Data error (cyclic redundancy check)., Sector: 3457592, Block: 4
8/29/2023 4:30:07 PM ! Error: 23 Data error (cyclic redundancy check)., Sector: 3457593, Block: 4
8/29/2023 4:30:10 PM ! Error: 23 Data error (cyclic redundancy check)., Sector: 3457593, Block: 4
8/29/2023 4:30:14 PM ! Error: 23 Data error (cyclic redundancy check)., Sector: 3457593, Block: 4
8/29/2023 4:30:18 PM ! Error: 23 Data error (cyclic redundancy check)., Sector: 3457594, Block: 4
8/29/2023 4:30:22 PM ! Error: 23 Data error (cyclic redundancy check)., Sector: 3457594, Block: 4
8/29/2023 4:30:25 PM ! Error: 23 Data error (cyclic redundancy check)., Sector: 3457594, Block: 4
8/29/2023 4:30:29 PM ! Error: 23 Data error (cyclic redundancy check)., Sector: 3457595, Block: 4
8/29/2023 4:30:33 PM ! Error: 23 Data error (cyclic redundancy check)., Sector: 3457595, Block: 4
8/29/2023 4:30:36 PM ! Error: 23 Data error (cyclic redundancy check)., Sector: 3457595, Block: 4
8/29/2023 4:30:40 PM ! Error: 23 Data error (cyclic redundancy check)., Sector: 3457596, Block: 4
8/29/2023 4:30:44 PM ! Error: 23 Data error (cyclic redundancy check)., Sector: 3457596, Block: 4
8/29/2023 4:30:47 PM ! Error: 23 Data error (cyclic redundancy check)., Sector: 3457596, Block: 4
8/29/2023 4:30:51 PM ! Error: 23 Data error (cyclic redundancy check)., Sector: 3457597, Block: 4
8/29/2023 4:30:55 PM ! Error: 23 Data error (cyclic redundancy check)., Sector: 3457597, Block: 4
8/29/2023 4:30:59 PM ! Error: 23 Data error (cyclic redundancy check)., Sector: 3457597, Block: 4
8/29/2023 4:31:02 PM ! Error: 23 Data error (cyclic redundancy check)., Sector: 3457598, Block: 4
8/29/2023 4:31:06 PM ! Error: 23 Data error (cyclic redundancy check)., Sector: 3457598, Block: 4
8/29/2023 4:31:10 PM ! Error: 23 Data error (cyclic redundancy check)., Sector: 3457598, Block: 4
8/29/2023 4:31:13 PM ! Error: 23 Data error (cyclic redundancy check)., Sector: 3457599, Block: 4
8/29/2023 4:31:17 PM ! Error: 23 Data error (cyclic redundancy check)., Sector: 3457599, Block: 4
8/29/2023 4:31:21 PM ! Error: 23 Data error (cyclic redundancy check)., Sector: 3457599, Block: 4
8/29/2023 4:31:29 PM ! Error: 23 Data error (cyclic redundancy check)., Sector: 3483400, Block: 4
8/29/2023 4:31:33 PM ! Error: 23 Data error (cyclic redundancy check)., Sector: 3483400, Block: 4
8/29/2023 4:31:36 PM ! Error: 23 Data error (cyclic redundancy check)., Sector: 3483400, Block: 4
8/29/2023 4:31:40 PM ! Error: 23 Data error (cyclic redundancy check)., Sector: 3483401, Block: 4
8/29/2023 4:31:44 PM ! Error: 23 Data error (cyclic redundancy check)., Sector: 3483401, Block: 4
8/29/2023 4:31:48 PM ! Error: 23 Data error (cyclic redundancy check)., Sector: 3483401, Block: 4
8/29/2023 4:31:51 PM ! Error: 23 Data error (cyclic redundancy check)., Sector: 3483402, Block: 4
8/29/2023 4:31:55 PM ! Error: 23 Data error (cyclic redundancy check)., Sector: 3483402, Block: 4
8/29/2023 4:31:59 PM ! Error: 23 Data error (cyclic redundancy check)., Sector: 3483402, Block: 4
8/29/2023 4:32:02 PM ! Error: 23 Data error (cyclic redundancy check)., Sector: 3483403, Block: 4
8/29/2023 4:32:06 PM ! Error: 23 Data error (cyclic redundancy check)., Sector: 3483403, Block: 4
8/29/2023 4:32:10 PM ! Error: 23 Data error (cyclic redundancy check)., Sector: 3483403, Block: 4
8/29/2023 4:32:13 PM ! Error: 23 Data error (cyclic redundancy check)., Sector: 3483404, Block: 4
8/29/2023 4:32:17 PM ! Error: 23 Data error (cyclic redundancy check)., Sector: 3483404, Block: 4
8/29/2023 4:32:21 PM ! Error: 23 Data error (cyclic redundancy check)., Sector: 3483404, Block: 4
8/29/2023 4:32:25 PM ! Error: 23 Data error (cyclic redundancy check)., Sector: 3483405, Block: 4
8/29/2023 4:32:28 PM ! Error: 23 Data error (cyclic redundancy check)., Sector: 3483405, Block: 4
8/29/2023 4:32:32 PM ! Error: 23 Data error (cyclic redundancy check)., Sector: 3483405, Block: 4
8/29/2023 4:32:36 PM ! Error: 23 Data error (cyclic redundancy check)., Sector: 3483406, Block: 4
8/29/2023 4:32:39 PM ! Error: 23 Data error (cyclic redundancy check)., Sector: 3483406, Block: 4
8/29/2023 4:32:43 PM ! Error: 23 Data error (cyclic redundancy check)., Sector: 3483406, Block: 4
8/29/2023 4:32:47 PM ! Error: 23 Data error (cyclic redundancy check)., Sector: 3483407, Block: 4
8/29/2023 4:32:51 PM ! Error: 23 Data error (cyclic redundancy check)., Sector: 3483407, Block: 4
8/29/2023 4:32:54 PM ! Error: 23 Data error (cyclic redundancy check)., Sector: 3483407, Block: 4
8/29/2023 4:33:02 PM ! Error: 23 Data error (cyclic redundancy check)., Sector: 3487024, Block: 4
8/29/2023 4:33:05 PM ! Error: 23 Data error (cyclic redundancy check)., Sector: 3487024, Block: 4
8/29/2023 4:33:09 PM ! Error: 23 Data error (cyclic redundancy check)., Sector: 3487024, Block: 4
8/29/2023 4:33:13 PM ! Error: 23 Data error (cyclic redundancy check)., Sector: 3487025, Block: 4
8/29/2023 4:33:17 PM ! Error: 23 Data error (cyclic redundancy check)., Sector: 3487025, Block: 4
8/29/2023 4:33:20 PM ! Error: 23 Data error (cyclic redundancy check)., Sector: 3487025, Block: 4
8/29/2023 4:33:24 PM ! Error: 23 Data error (cyclic redundancy check)., Sector: 3487026, Block: 4
8/29/2023 4:33:28 PM ! Error: 23 Data error (cyclic redundancy check)., Sector: 3487026, Block: 4
8/29/2023 4:33:31 PM ! Error: 23 Data error (cyclic redundancy check)., Sector: 3487026, Block: 4
8/29/2023 4:33:35 PM ! Error: 23 Data error (cyclic redundancy check)., Sector: 3487027, Block: 4
8/29/2023 4:33:39 PM ! Error: 23 Data error (cyclic redundancy check)., Sector: 3487027, Block: 4
8/29/2023 4:33:42 PM ! Error: 23 Data error (cyclic redundancy check)., Sector: 3487027, Block: 4
8/29/2023 4:33:46 PM ! Error: 23 Data error (cyclic redundancy check)., Sector: 3487028, Block: 4
8/29/2023 4:33:50 PM ! Error: 23 Data error (cyclic redundancy check)., Sector: 3487028, Block: 4
8/29/2023 4:33:54 PM ! Error: 23 Data error (cyclic redundancy check)., Sector: 3487028, Block: 4
8/29/2023 4:33:57 PM ! Error: 23 Data error (cyclic redundancy check)., Sector: 3487029, Block: 4
8/29/2023 4:34:01 PM ! Error: 23 Data error (cyclic redundancy check)., Sector: 3487029, Block: 4
8/29/2023 4:34:05 PM ! Error: 23 Data error (cyclic redundancy check)., Sector: 3487029, Block: 4
8/29/2023 4:34:08 PM ! Error: 23 Data error (cyclic redundancy check)., Sector: 3487030, Block: 4
8/29/2023 4:34:12 PM ! Error: 23 Data error (cyclic redundancy check)., Sector: 3487030, Block: 4
8/29/2023 4:34:16 PM ! Error: 23 Data error (cyclic redundancy check)., Sector: 3487030, Block: 4
8/29/2023 4:34:20 PM ! Error: 23 Data error (cyclic redundancy check)., Sector: 3487031, Block: 4
8/29/2023 4:34:23 PM ! Error: 23 Data error (cyclic redundancy check)., Sector: 3487031, Block: 4
8/29/2023 4:34:27 PM ! Error: 23 Data error (cyclic redundancy check)., Sector: 3487031, Block: 4
8/29/2023 4:34:34 PM ! Error: 23 Data error (cyclic redundancy check)., Sector: 3490648, Block: 4
8/29/2023 4:34:38 PM ! Error: 23 Data error (cyclic redundancy check)., Sector: 3490648, Block: 4
8/29/2023 4:34:42 PM ! Error: 23 Data error (cyclic redundancy check)., Sector: 3490648, Block: 4
8/29/2023 4:34:46 PM ! Error: 23 Data error (cyclic redundancy check)., Sector: 3490649, Block: 4
8/29/2023 4:34:49 PM ! Error: 23 Data error (cyclic redundancy check)., Sector: 3490649, Block: 4
8/29/2023 4:34:53 PM ! Error: 23 Data error (cyclic redundancy check)., Sector: 3490649, Block: 4
8/29/2023 4:34:57 PM ! Error: 23 Data error (cyclic redundancy check)., Sector: 3490650, Block: 4
8/29/2023 4:35:00 PM ! Error: 23 Data error (cyclic redundancy check)., Sector: 3490650, Block: 4
8/29/2023 4:35:04 PM ! Error: 23 Data error (cyclic redundancy check)., Sector: 3490650, Block: 4
8/29/2023 4:35:08 PM ! Error: 23 Data error (cyclic redundancy check)., Sector: 3490651, Block: 4
8/29/2023 4:35:11 PM ! Error: 23 Data error (cyclic redundancy check)., Sector: 3490651, Block: 4
8/29/2023 4:35:15 PM ! Error: 23 Data error (cyclic redundancy check)., Sector: 3490651, Block: 4
8/29/2023 4:35:19 PM ! Error: 23 Data error (cyclic redundancy check)., Sector: 3490652, Block: 4
8/29/2023 4:35:23 PM ! Error: 23 Data error (cyclic redundancy check)., Sector: 3490652, Block: 4
8/29/2023 4:35:26 PM ! Error: 23 Data error (cyclic redundancy check)., Sector: 3490652, Block: 4
8/29/2023 4:35:30 PM ! Error: 23 Data error (cyclic redundancy check)., Sector: 3490653, Block: 4
8/29/2023 4:35:34 PM ! Error: 23 Data error (cyclic redundancy check)., Sector: 3490653, Block: 4
8/29/2023 4:35:37 PM ! Error: 23 Data error (cyclic redundancy check)., Sector: 3490653, Block: 4
8/29/2023 4:35:41 PM ! Error: 23 Data error (cyclic redundancy check)., Sector: 3490654, Block: 4
8/29/2023 4:35:45 PM ! Error: 23 Data error (cyclic redundancy check)., Sector: 3490654, Block: 4
8/29/2023 4:35:49 PM ! Error: 23 Data error (cyclic redundancy check)., Sector: 3490654, Block: 4
8/29/2023 4:35:52 PM ! Error: 23 Data error (cyclic redundancy check)., Sector: 3490655, Block: 4
8/29/2023 4:35:56 PM ! Error: 23 Data error (cyclic redundancy check)., Sector: 3490655, Block: 4
8/29/2023 4:36:00 PM ! Error: 23 Data error (cyclic redundancy check)., Sector: 3490655, Block: 4
8/29/2023 4:36:07 PM ! Error: 23 Data error (cyclic redundancy check)., Sector: 3494272, Block: 4
8/29/2023 4:36:11 PM ! Error: 23 Data error (cyclic redundancy check)., Sector: 3494272, Block: 4
8/29/2023 4:36:15 PM ! Error: 23 Data error (cyclic redundancy check)., Sector: 3494272, Block: 4
8/29/2023 4:36:18 PM ! Error: 23 Data error (cyclic redundancy check)., Sector: 3494273, Block: 4
8/29/2023 4:36:22 PM ! Error: 23 Data error (cyclic redundancy check)., Sector: 3494273, Block: 4
8/29/2023 4:36:26 PM ! Error: 23 Data error (cyclic redundancy check)., Sector: 3494273, Block: 4
8/29/2023 4:36:29 PM ! Error: 23 Data error (cyclic redundancy check)., Sector: 3494274, Block: 4
8/29/2023 4:36:33 PM ! Error: 23 Data error (cyclic redundancy check)., Sector: 3494274, Block: 4
8/29/2023 4:36:37 PM ! Error: 23 Data error (cyclic redundancy check)., Sector: 3494274, Block: 4
8/29/2023 4:36:40 PM ! Error: 23 Data error (cyclic redundancy check)., Sector: 3494275, Block: 4
8/29/2023 4:36:44 PM ! Error: 23 Data error (cyclic redundancy check)., Sector: 3494275, Block: 4
8/29/2023 4:36:48 PM ! Error: 23 Data error (cyclic redundancy check)., Sector: 3494275, Block: 4
8/29/2023 4:36:52 PM ! Error: 23 Data error (cyclic redundancy check)., Sector: 3494276, Block: 4
8/29/2023 4:36:55 PM ! Error: 23 Data error (cyclic redundancy check)., Sector: 3494276, Block: 4
8/29/2023 4:36:59 PM ! Error: 23 Data error (cyclic redundancy check)., Sector: 3494276, Block: 4
8/29/2023 4:37:03 PM ! Error: 23 Data error (cyclic redundancy check)., Sector: 3494277, Block: 4
8/29/2023 4:37:06 PM ! Error: 23 Data error (cyclic redundancy check)., Sector: 3494277, Block: 4
8/29/2023 4:37:10 PM ! Error: 23 Data error (cyclic redundancy check)., Sector: 3494277, Block: 4
8/29/2023 4:37:14 PM ! Error: 23 Data error (cyclic redundancy check)., Sector: 3494278, Block: 4
8/29/2023 4:37:18 PM ! Error: 23 Data error (cyclic redundancy check)., Sector: 3494278, Block: 4
8/29/2023 4:37:21 PM ! Error: 23 Data error (cyclic redundancy check)., Sector: 3494278, Block: 4
8/29/2023 4:37:25 PM ! Error: 23 Data error (cyclic redundancy check)., Sector: 3494279, Block: 4
8/29/2023 4:37:29 PM ! Error: 23 Data error (cyclic redundancy check)., Sector: 3494279, Block: 4
8/29/2023 4:37:32 PM ! Error: 23 Data error (cyclic redundancy check)., Sector: 3494279, Block: 4
8/30/2023 1:46:46 AM Test completed
- hdsentinel
- Site Admin
- Posts: 3128
- Joined: 2008.07.27. 17:00
- Location: Hungary
- Contact:
Re: Why does a failed drive show 100% health?
Thanks for the report, I double checked and yes, now I see the status.
> I also ran a surface test overnight and it reported 3 bad sectors. Just surprised that the health still shows 100%.
According the report, the drive has 88% Health now and the text description shows the reason and the problems:
There are 20 weak sectors found on the disk surface. They may be remapped any time in the later use of the disk.
More information: https://www.hdsentinel.com/hard_disk_case_weak_sectors.php
Generally it is not rare that such hard disk problems may remain unnoticed for longer time, sometimes even months or years (!), as described in the Support -> Knowledge Base -> Hard Disk Cases -> Bad sectors article:
https://www.hdsentinel.com/hard_disk_case_bad_sectors.php
As you can see, the disk test revealed the problems with the sectors and forced the disk drive to finally record them into the S.M.A.R.T. attributes, exactly as should.
The purpose of the Read test is exactly this: to reveal such issues - or confirm that the drive can be used and the status is stable.
And in such situations, when problems detected, the Disk menu -> Surface test -> Reinitialise Disk Surface test is the best way to repair: to force the hard disk drive to repair such sectors (and possible others too), to reallocate them if required to prevent later use.
> I in no way trust this drive for any type of critical data.
I can completely understand and agree you. But not (only) because of the issues you see now: in most cases, such problems are usually related to operating environment (cables, connections, power source). If the drive used for many-many years in the NAS, there is good chance that the NAS has power supply issue which resulted in the damaged sectors. I mean that if you replace the drive - you may see similar on a new drive too.
Personally I'd surely perform the mentioned Disk menu -> Surface test -> Reinitialise Disk Surface test (which clears all data) and then try a new read test, just to be sure - and decide what to do after that: if the new read test shows no issues (ideally) then the drive can be still used.
(if you prefer, you can send developer-reports similarly after the tests, so then it is possible to follow the status change, check the results).
However, as mentioned, the drive is far over the designed lifetime. According the experiences, the chances of sudden failure (even at high Health % levels) is higher at this point. The drive may work for many more years - but can produce errors or fail suddenly when the estimated remaining lifetime is 100 days or lower which is an indication when we should plan replacement in a critical environment.
So personally I'd use only for secondary storage (not for critical data) exactly as you wrote.
> I was going to discard it, but since it still reads and writes, I might fill it up with documents and JPG's and archive it.
Yes, for secondary storage (not critical data) it can be still acceptable.
> Is there something that I should do to remap the bad sectors before I use it as an archive?
Yes of course, the mentioned Disk menu -> Surface test -> Reinitialise Disk Surface test is the ideal way to force the hard disk remap the bad sectors if required. It is possible that there is no need to remap them (if the problems caused by the operating environment, the NAS).
> I purchased HD Sentinel last week to test 6 new drives that were going into the NAS to make sure
> I was getting new drives and that none of them were DOA.
> With this bad drive showing 100% health, I am no nervous about trusting those same results on the new drive.
I completely understand and agree you. This is exactly why I always recommend to DO NOT trust the displayed status (really!) even for a new drive, but perform some testing on a disk drive, exactly to reveal such problems long before they can cause troubles - or confirm that the drive is initially working correctly.
Please check Support -> Frequently Asked Questions -> Hard disk health is low or recently changed or I just installed a new (used) hard disk. How can I perform a deep analysis?
https://www.hdsentinel.com/faq.php#tests
page for details: the suggested tests to be performed even on a new drive.
This is especially important if the drive is used in a NAS where (even we can monitor the status, as described at https://www.hdsentinel.com/how_to_monitor_network_attached_storage_nas_status.php ) but we may have limited disk access, so can't perform disk testing/repairing.
> I also ran a surface test overnight and it reported 3 bad sectors. Just surprised that the health still shows 100%.
According the report, the drive has 88% Health now and the text description shows the reason and the problems:
There are 20 weak sectors found on the disk surface. They may be remapped any time in the later use of the disk.
More information: https://www.hdsentinel.com/hard_disk_case_weak_sectors.php
Generally it is not rare that such hard disk problems may remain unnoticed for longer time, sometimes even months or years (!), as described in the Support -> Knowledge Base -> Hard Disk Cases -> Bad sectors article:
https://www.hdsentinel.com/hard_disk_case_bad_sectors.php
As you can see, the disk test revealed the problems with the sectors and forced the disk drive to finally record them into the S.M.A.R.T. attributes, exactly as should.
The purpose of the Read test is exactly this: to reveal such issues - or confirm that the drive can be used and the status is stable.
And in such situations, when problems detected, the Disk menu -> Surface test -> Reinitialise Disk Surface test is the best way to repair: to force the hard disk drive to repair such sectors (and possible others too), to reallocate them if required to prevent later use.
> I in no way trust this drive for any type of critical data.
I can completely understand and agree you. But not (only) because of the issues you see now: in most cases, such problems are usually related to operating environment (cables, connections, power source). If the drive used for many-many years in the NAS, there is good chance that the NAS has power supply issue which resulted in the damaged sectors. I mean that if you replace the drive - you may see similar on a new drive too.
Personally I'd surely perform the mentioned Disk menu -> Surface test -> Reinitialise Disk Surface test (which clears all data) and then try a new read test, just to be sure - and decide what to do after that: if the new read test shows no issues (ideally) then the drive can be still used.
(if you prefer, you can send developer-reports similarly after the tests, so then it is possible to follow the status change, check the results).
However, as mentioned, the drive is far over the designed lifetime. According the experiences, the chances of sudden failure (even at high Health % levels) is higher at this point. The drive may work for many more years - but can produce errors or fail suddenly when the estimated remaining lifetime is 100 days or lower which is an indication when we should plan replacement in a critical environment.
So personally I'd use only for secondary storage (not for critical data) exactly as you wrote.
> I was going to discard it, but since it still reads and writes, I might fill it up with documents and JPG's and archive it.
Yes, for secondary storage (not critical data) it can be still acceptable.
> Is there something that I should do to remap the bad sectors before I use it as an archive?
Yes of course, the mentioned Disk menu -> Surface test -> Reinitialise Disk Surface test is the ideal way to force the hard disk remap the bad sectors if required. It is possible that there is no need to remap them (if the problems caused by the operating environment, the NAS).
> I purchased HD Sentinel last week to test 6 new drives that were going into the NAS to make sure
> I was getting new drives and that none of them were DOA.
> With this bad drive showing 100% health, I am no nervous about trusting those same results on the new drive.
I completely understand and agree you. This is exactly why I always recommend to DO NOT trust the displayed status (really!) even for a new drive, but perform some testing on a disk drive, exactly to reveal such problems long before they can cause troubles - or confirm that the drive is initially working correctly.
Please check Support -> Frequently Asked Questions -> Hard disk health is low or recently changed or I just installed a new (used) hard disk. How can I perform a deep analysis?
https://www.hdsentinel.com/faq.php#tests
page for details: the suggested tests to be performed even on a new drive.
This is especially important if the drive is used in a NAS where (even we can monitor the status, as described at https://www.hdsentinel.com/how_to_monitor_network_attached_storage_nas_status.php ) but we may have limited disk access, so can't perform disk testing/repairing.
-
- Posts: 4
- Joined: 2023.08.29. 21:54
Re: Why does a failed drive show 100% health?
Thank you for the very through reply.