What is the best way forward with this, The device, \Device\Harddisk1\DR1, has a bad block.
Question What is the best way forward
- Thread starter mick1964
- Start date
Some reading.
https://www.minitool.com/backup-tips/current-pending-sector-count.html
Pay attention to the part about a backup.
- May 29, 2013
- 38,243
- 3,627
- 156,790
Once it has one, there is no way to predict when the next one or the fatal one will happen. If you choose to be OCD about backups, then you could continue to use this device. The question is "How much is the data worth?" If it is game captures, then maybe it doesn't matter. If it is your raw video of a birthday for your grandparent that is now in the hospital, then why risk it.
I have already removed all data from the Drive but is there a way to mark that bad sector so I can use the rest of it for unimportant files.
- Apr 18, 2014
- 2,552
- 459
- 22,390
As said above, that is already marked bad by the drive, therefore, CrystalDisk can read/show it and there's really no telling when it will get worse; and it will at some time. Sometimes it stays the way it is for a while (few months, a year) and sometimes the damage spreads quickly like wild fire.
Some users do partition the drive in a way that the partition/s they're going to use fall on the good sectors and the area with the bad sectors/blocks is left as 'Unallocated' space so the head/actuator assembly actually leaves that part alone and doesn't go there to those sectors (no data) and some actually say/think that can prolong the drives life.
I would also add that I haven't seen have any documented data/proof that it actually affects drive longevity; just word of mouth. Bottomline is you can never tell when the drive (any dirve for that matter) will fail.
Some users do partition the drive in a way that the partition/s they're going to use fall on the good sectors and the area with the bad sectors/blocks is left as 'Unallocated' space so the head/actuator assembly actually leaves that part alone and doesn't go there to those sectors (no data) and some actually say/think that can prolong the drives life.
I would also add that I haven't seen have any documented data/proof that it actually affects drive longevity; just word of mouth. Bottomline is you can never tell when the drive (any dirve for that matter) will fail.
- Mar 16, 2013
- 176,579
- 20,431
- 184,590
I recently had a 16TB Toshiba Enterprise go from "one bad sector" to 14,000+ in about 8 days.
It was about 7 months old.
Continue to use it monitor smart often it will either get worse or stay the same.
Don't put anything on it that you can't afford to lose.
Maybe. The SMART data you posted is showing 2 pending sectors. That means the drive found them suspicious (likely bad) but hasn't confirmed it yet. It probably won't be until the next write operation that they are either found good and returned to service or marked bad and reallocated.
First, I'd run a full surface scan with either HDDScan or Victoria. See if one of them finds more bad and/or slow sectors. If there aren't any more (or only a few more), the simplest way to have the drive deal with them may be to use the official WD utility to run a full scan. It should offer the option to reallocate them. The reason I'm suggesting using both utilities is because HDDScan and Victoria will give more informative results but can have trouble making the drive reallocate the sectors (likely because of Windows). The WD utility has a better chance of being successful.
If there are only a few bad sectors (like <15) there's a chance they may not spread and you can continue using the drive, though I wouldn't trust it with anything important. If there's like 20+, there's a good chance they'll spread, rendering the drive extremely untrustworthy at best. If you do continue using the drive, I'd periodically run scans with HDDScan or Victoria, to make sure new ones aren't appearing. If they are, I'd consider the drive toast.
Thanks for your reply, I have it being checked thru Victoria Test & Repair its at 54% of the test so far with these results so far.
Victoria 5.37 HDD/SSD | Device 3 log file. 27/03/2024
09:14:44 : Starting Victoria 5.37 HDD/SSD. 8xCPU, 3677.33 MHz, Windows 10 x64 found.
09:14:44 : [Hint] Recommend 32-bit Windows XP for a best work!
09:14:44 : Warning! Windows x64 detected! PIO mode supported on Windows x86 only.
09:14:44 : API access enabled, device #0
09:14:44 : Press F1 to About/HELP
09:14:44 : Get drive passport... OK
09:14:44 : Model: KINGSTON SA400S37480G; Capacity 937703088 LBAs; SN: ; FW: SHFK70.5
09:15:11 : Get drive passport... OK
09:15:11 : Model: WDC WD40EZRZ-00WN9B0; Capacity 7814037168 LBAs; SN: WD-WCC4E5DDZ4A8; FW: 80.00A80
09:15:42 : Recallibration... OK
09:15:42 : Starting Reading, LBA=0..7814037167, FULL, sequential access, timeout 10000ms
09:16:41 : Warning! Block start at 17252352 (9 GB) = 1579 ms
09:16:43 : Warning! Block start at 17256448 (9 GB) = 1688 ms
09:16:50 : Warning! Block start at 17410048 (9 GB) = 1016 ms
09:17:06 : Warning! Block start at 20676608 (11 GB) = 3109 ms
09:17:08 : Warning! Block start at 20680704 (11 GB) = 1078 ms
09:17:09 : Warning! Block start at 20682752 (11 GB) = 1562 ms
09:17:11 : Warning! Block start at 20686848 (11 GB) = 1141 ms
09:18:59 : Block start at 45215744 (23 GB) Read error: UNCR "Data error (cyclic redundancy check)"
09:19:01 : Warning! Block start at 45223936 (23 GB) = 1031 ms
Most issues seems to be not long after the start of the test so maybe I can partition the Drive like you say and just use the good part.
This is a recertified Drive from WD and has lasted about 13 months my first and last recertified Drive.
- Apr 18, 2014
- 2,552
- 459
- 22,390
A full surface scan is what can actually kill such a drive (with pending/bad sectors) that is to push it off the edge. Because during the full surface test the drive works vigorously a long time reading all sectors. Periodic tests would also probably kill it sooner since it means putting too much stress on the drive.
I personally think there is no need for periodic scans. If you decide you want to keep using it you can monitor SMART data and see if the number of pending/reallocated sectors rises. If the numbers go up it means the drive is deteriorating and total failure is imminent.
As said above, don't trust the drive, you can keep using but don't leave anything important on it. Treat it as if it's going to die any second.
I personally think there is no need for periodic scans. If you decide you want to keep using it you can monitor SMART data and see if the number of pending/reallocated sectors rises. If the numbers go up it means the drive is deteriorating and total failure is imminent.
As said above, don't trust the drive, you can keep using but don't leave anything important on it. Treat it as if it's going to die any second.
Scan finished with these results
Victoria 5.37 HDD/SSD | Device 3 log file. 27/03/2024
09:14:44 : Starting Victoria 5.37 HDD/SSD. 8xCPU, 3677.33 MHz, Windows 10 x64 found.
09:14:44 : [Hint] Recommend 32-bit Windows XP for a best work!
09:14:44 : Warning! Windows x64 detected! PIO mode supported on Windows x86 only.
09:14:44 : API access enabled, device #0
09:14:44 : Press F1 to About/HELP
09:14:44 : Get drive passport... OK
09:14:44 : Model: KINGSTON SA400S37480G; Capacity 937703088 LBAs; SN: ; FW: SHFK70.5
09:15:11 : Get drive passport... OK
09:15:11 : Model: WDC WD40EZRZ-00WN9B0; Capacity 7814037168 LBAs; SN: WD-WCC4E5DDZ4A8; FW: 80.00A80
09:15:42 : Recallibration... OK
09:15:42 : Starting Reading, LBA=0..7814037167, FULL, sequential access, timeout 10000ms
09:16:41 : Warning! Block start at 17252352 (9 GB) = 1579 ms
09:16:43 : Warning! Block start at 17256448 (9 GB) = 1688 ms
09:16:50 : Warning! Block start at 17410048 (9 GB) = 1016 ms
09:17:06 : Warning! Block start at 20676608 (11 GB) = 3109 ms
09:17:08 : Warning! Block start at 20680704 (11 GB) = 1078 ms
09:17:09 : Warning! Block start at 20682752 (11 GB) = 1562 ms
09:17:11 : Warning! Block start at 20686848 (11 GB) = 1141 ms
09:18:59 : Block start at 45215744 (23 GB) Read error: UNCR "Data error (cyclic redundancy check)"
09:19:01 : Warning! Block start at 45223936 (23 GB) = 1031 ms
18:47:49 : Screenshot C:\Users\windy\Desktop\Victoria537\LOGS\WDC WD40EZRZ-00WN9B0__WD-WCC4E5DDZ4A8\SCR\27-03-2024__18-47-49__Scan saved
18:47:49 : *** Scan results: Warnings - 8, errors - 1. Last block at 7814037167 (4.0 TB), time 9 hours 32 minutes 7 seconds.
18:47:49 : 0 of 1 defects successfully remapped.
18:47:49 : Speed: Maximum 163 MB/s. Average 81 MB/s. Minimum 0 MB/s. 423 points.
That doesn't look good. What is the SMART data showing now? I suspect the bad sectors will continue to spread. I don't suppose this drive is still under warranty?
I suppose you could try leaving the most affected portion of the drive unpartitioned but I'm not optimistic about the long term prospects. Some partitioning utilities won't let you leave free space before a new partition. The simplest workaround would be to create a small partition, before your main partition and then delete it, after creating the second one. In your case, I'd probably leave the first 100GB (at least 50GB) unpartitioned.
I disagree. The SMART values aren't going to rise until the drive notices something is wrong. It's not going to notice until it tries to access an affected sector. If this portion of the drive is left unpartitioned, bad sectors could spread like wildfire and the SMART values may never change.
TRENDING THREADS
-
News AMD says Intel's 'horrible product' is causing Ryzen 9 9800X3D shortages- Started by Admin
- Replies: 75
-
-
-
News Jensen says DLSS 4 "predicts the future" to increase framerates without introducing latency
- Started by Admin
- Replies: 88
-
Discussion PSU recommendations and power supply discussion thread - Tom's hardware- Started by Darkbreeze
- Replies: 2K
-
News Nvidia's GeForce RTX 5070 at $549 — How does it stack up to the previous generation RTX 4070?
- Started by Admin
- Replies: 77
Latest posts
-
Question New Build=Marvel Rivals crashes=PC blue screens and boot up issues
- Latest: Kerrigan Rose
-
-
-
-
-
Facebook
Twitter
Instagram