Need to find drive with bad block

Event Viewer: "The device, \Device\Harddisk0\DR0, has a bad block."

Got a Windows 10 BSOD, possibly from writing to a bad block. How can I
determine which drive is DR0? Can I assume C:? All partitions are on
the same disk. Drive O: is an external drive.
https://i.imgur.com/m7F1CH1.jpg

Will chkdsk /x /f /r check the entire hard drive, or must I specify a
specific drive (chkdsk c: /x /f /r )? Thanks.

M.L. wrote:

Event Viewer: "The device, \Device\Harddisk0\DR0, has a bad block."

Got a Windows 10 BSOD, possibly from writing to a bad block. How can I
determine which drive is DR0? Can I assume C:? All partitions are on
the same disk. Drive O: is an external drive.
https://i.imgur.com/m7F1CH1.jpg

Will chkdsk /x /f /r check the entire hard drive, or must I specify a
specific drive (chkdsk c: /x /f /r )? Thanks.

DR0 is the first partition on Harddisk0.

Do you have more than one /internal/ disk (whether HDD or SDD)? If no,
you only have the one disk and its partitions to test. If yes, which
disk is attached to the SATA-0 header on the motherboard?

If you have nothing of the OS in other partitions (e.g., pagefile) then
the only disk with the bad block is the one that has the partition where
the OS is installed. The OS shouldn't crash because of a bad block on a
data-only drive.

Have you yet ran "chkdsk /r" on EVERY drive (which is a partition on a
disk, not the disk itself)? The surface scan will take a long time for
really large-sized partitions.

If "chkdsk /r" doesn't eliminate the bad block error, could be you have
a marginally bad disk or bad hardware (e.g., SATA controller). Try
using the disk manufacturer's diagnostics software. There are pro tools
to thoroughly test a drive, like Spinrite and HDD Regenerator, but their
cost is about the same as buying a new HDD (so you buy those tools to
keep in your software toolkit for reuse later, like for company
workstations). It might be cheaper to get HD Sentinel, or similar, to
do the surface testing (not available in free version, only in $30
payware version). I have the Standard edition ($20) which has a surface
test but I'll upgrade to the Pro edition ($30) because it has better
diagnostics. Besides the disk diagnostics, it also monitors the
S.M.A.R.T. attributes of a drive. Rather than you trying to figure out
which attributes are important to what type of drive (HDD vs SDD) and
analyze their values, HD Sentinel will indicate the health of the disk.
I'm sure there are plenty of other similar tools (for SMART monitoring
and disk diagnostics), perhaps even some for free, but back a few years
when I was looking at various candidates I chose HD Sentinel, and I
haven't bothered revisiting what other diag tools there are available.

Have you yet saved all your data files to elsewhere?

On 03/12/2018 19:59, M.L. wrote:


Event Viewer: "The device, \Device\Harddisk0\DR0, has a bad block."

Got a Windows 10 BSOD, possibly from writing to a bad block. How can I
determine which drive is DR0? Can I assume C:? All partitions are on
the same disk. Drive O: is an external drive.
https://i.imgur.com/m7F1CH1.jpg

In 'Disk Management';
On the 'View' tab select 'Bottom' then click 'Graphical'.


Will chkdsk /x /f /r check the entire hard drive, or must I specify a
specific drive (chkdsk c: /x /f /r )? Thanks.

Event Viewer: "The device, \Device\Harddisk0\DR0, has a bad block."

Got a Windows 10 BSOD, possibly from writing to a bad block. How can I
determine which drive is DR0? Can I assume C:? All partitions are on
the same disk. Drive O: is an external drive.
https://i.imgur.com/m7F1CH1.jpg

In 'Disk Management';
On the 'View' tab select 'Bottom' then click 'Graphical'.

Thanks for your reply. The bottom view was already set to Graphical.
And the bottom cells displayed the same info as the top listing in the
linked pic.

The laptop HD is a Seagate ST500LT012 2.5". I'm going to peruse the
Seagate site to see if they have HD diagnostic tools that can scan the
entire drive for faults.

Event Viewer: "The device, \Device\Harddisk0\DR0, has a bad block."

Got a Windows 10 BSOD, possibly from writing to a bad block. How can I
determine which drive is DR0? Can I assume C:? All partitions are on
the same disk. Drive O: is an external drive.
https://i.imgur.com/m7F1CH1.jpg

Will chkdsk /x /f /r check the entire hard drive, or must I specify a
specific drive (chkdsk c: /x /f /r )? Thanks.

DR0 is the first partition on Harddisk0.

Do you have more than one /internal/ disk (whether HDD or SDD)? If no,
you only have the one disk and its partitions to test.

Good to know. There's only one internal HD on my laptop.

If you have nothing of the OS in other partitions (e.g., pagefile) then
the only disk with the bad block is the one that has the partition where
the OS is installed. The OS shouldn't crash because of a bad block on a
data-only drive.

More good info.

Have you yet ran "chkdsk /r" on EVERY drive (which is a partition on a
disk, not the disk itself)? The surface scan will take a long time for
really large-sized partitions.

I've only ever ran chkdsk on my C: drive.

If "chkdsk /r" doesn't eliminate the bad block error, could be you have
a marginally bad disk or bad hardware (e.g., SATA controller). Try
using the disk manufacturer's diagnostics software.

That's exactly what I plan to do. The laptop HD is a Seagate
ST500LT012 2.5" SATA. I'm going to visit the Seagate site for
diagnostic tools to scan for faults.

Have you yet saved all your data files to elsewhere?

I keep anything of importance on my external HD. At worst I'll need to
reinstall apps. I also have a VANTEC SATA to USB adapter that can read
a drive that's dead due to bad blocks. Thanks for your reply
VanguardLH.

In article , M.L.
wrote:

I also have a VANTEC SATA to USB adapter that can read
a drive that's dead due to bad blocks.

a drive with bad blocks isn't necessarily dead, however, it would take
more than just a usb adapter to read those bad blocks.

M.L. wrote:

Event Viewer: "The device, \Device\Harddisk0\DR0, has a bad block."

Got a Windows 10 BSOD, possibly from writing to a bad block. How can I
determine which drive is DR0? Can I assume C:? All partitions are on
the same disk. Drive O: is an external drive.
https://i.imgur.com/m7F1CH1.jpg
In 'Disk Management';
On the 'View' tab select 'Bottom' then click 'Graphical'.

Thanks for your reply. The bottom view was already set to Graphical.
And the bottom cells displayed the same info as the top listing in the
linked pic.

The laptop HD is a Seagate ST500LT012 2.5". I'm going to peruse the
Seagate site to see if they have HD diagnostic tools that can scan the
entire drive for faults.

There will be a Seagate tool that runs from Windows.
The "MSDOS" or "FREEDOS" version, does not boot on all
modern hardware, so I would not pick that one to get
the job done.

*******

In addition, there is a SMART tab in this tool.
The Reallocated Sector and Current Pending Sector "data" fields
are the ones to watch. Normally, they're equal to zero.

http://www.hdtune.com/files/hdtune_255.exe

You can also run the Benchmark curve, but since this is windows 10,
you'll never get a moments peace, and the OS will "probe" the drive
while you're trying to benchmark it. This gives sloppy downward
spikes which aren't really there. The existence of downward
spikes can spell trouble - if only the OS would leave the
disk alone long enough for this test to run!

You *can* (I discovered this today) run HDTune while the
Macrium Emergency boot CD is the booted OS. There is a
Command Prompt button near the bottom of the screen. You CD
to the Program Files containing the HDTune.exe. Note that, the
"flavor" of Macrium disc (32-bit) must match the executable
HDTune.exe (32 bit only), and for most people, it requires
a special effort to make 32 bit media for this purpose.
All of my regular Macrium emergency boot CDs are x64 ones,
and HDTune won't run.

https://i.postimg.cc/SxwGD7w0/Macriu...Disk-Bench.jpg

The OS in that case, is less likely to mess up the benchmark.

*******

The DR0 is a total mystery. Van will enjoy this.

Grab this program.

http://www.chrysocome.net/downloads/dd-0.6beta3.zip

You'll need an Administrator command prompt, as this interacts
with the physical layer of the storage system.

cd /d %userprofile%\Downloads

dd --list

To save the output to a text file

dd --list 2 dd_out.txt

notepad dd_out.txt

and you can then paste into a message.

Any place the DR? nomenclature is used, I copied it here.
This is a subset of the lines, intended to focus on just
the mystery meat. See how charmingly inconsistent this
convention is ? And, as a bonus, "DR?" is not the only
modifier possible. There are others. It looks like it
might be a per-disk identifier (whole disk). Partition0
is a reference or pointer to the whole disk drive.
(Partition1 would be the first partition.)

NT Block Device Objects
\\?\Device\Floppy0
\\?\Device\Harddisk0\Partition0
link to \\?\Device\Harddisk0\DR0
Fixed hard disk media. Block size = 512
size is 500107862016 bytes Win2K HDD

\\?\Device\Harddisk1\Partition0
link to \\?\Device\Harddisk1\DR1
Fixed hard disk media. Block size = 512
size is 1000204886016 bytes WinXP HDD

\\?\Device\Harddisk2\Partition0
link to \\?\Device\Harddisk2\DR2
Fixed hard disk media. Block size = 512
size is 2000398934016 bytes Data storage drive

\\?\Device\Harddisk3\Partition0
link to \\?\Device\Harddisk3\DR0
Fixed hard disk media. Block size = 512
size is 4278190080 bytes 4GB DataRAM software RAMDisk

The first three are SATA, the last is software.
Notice how the naming scheme starts over for
the last one.

I've *never* been able to find a description
of this, even in the canonical namespace webpage.

The bad block isn't going anywhere. The HDTune
error scan (last tab) can be used to scan the
entire disk. HDTune doesn't care about $BADCLUS
and so HDTune will always be able to see this
so-called bad block. A CHKDSK run in fix mode
can add the bad block to $BADCLUS on the affected
partition (CHKDSK reads every sector for this,
and that takes hours).

Since Windows 10 has "robust background checking",
that's another consideration when it comes to
"where did my bad block go". I don't know how
the background checks that modern Windows does,
affect this particular error situation. Normally
you'd run CHKDSK in "fix" mode, where it reads
every cluster and puts the bad ones in $BADCLUS.

Paul

M.L. wrote:

I've only ever ran chkdsk on my C: drive.

That only tests the integrity of the file system, not the sectors on the
physical disk. The /r switch will actually test the sectors.

On 12/3/18 11:59 AM, M.L. wrote:


Event Viewer: "The device, \Device\Harddisk0\DR0, has a bad block."

Got a Windows 10 BSOD, possibly from writing to a bad block. How can I
determine which drive is DR0? Can I assume C:? All partitions are on
the same disk. Drive O: is an external drive.
https://i.imgur.com/m7F1CH1.jpg

Will chkdsk /x /f /r check the entire hard drive, or must I specify a
specific drive (chkdsk c: /x /f /r )? Thanks.


Hi ML,

I see everyone has told you how to figure it out. Plan on
replacing the hard drive. Clonezilla is a good tool. Make sure
the new hard drive is the same size or larger than the one.
(I can't be 1 MB smaller than the original. There are ways
around it: you have resize the partition smaller.)

https://clonezilla.org/

-T

On 12/4/18 2:08 AM, T wrote:
On 12/3/18 11:59 AM, M.L. wrote:


Event Viewer: "The device, \Device\Harddisk0\DR0, has a bad block."

Got a Windows 10 BSOD, possibly from writing to a bad block. How can I
determine which drive is DR0? Can I assume C:? All partitions are on
the same disk. Drive O: is an external drive.
https://i.imgur.com/m7F1CH1.jpg

Will chkdsk /x /f /r check the entire hard drive, or must I specify a
specific drive (chkdsk c: /x /f /r )? Thanks.


Hi ML,

I see everyone has told you how to figure it out.Â* Plan on
replacing the hard drive.Â* Clonezilla is a good tool.Â* Make sure
the new hard drive is the same size or larger than the one.
(I can't be 1 MB smaller than the original.Â* There are ways
around it: you have resize the partition smaller.)

https://clonezilla.org/

-T


There is a section in advanced settings to skip bad sectors.
You will have to use it.

nospam wrote:
In article , M.L.
wrote:

I also have a VANTEC SATA to USB adapter that can read
a drive that's dead due to bad blocks.

a drive with bad blocks isn't necessarily dead, however, it would take
more than just a usb adapter to read those bad blocks.

If a drive reports a CRC error for a sector, it might be
a good idea to check the SMART table before it's too late.

It could be the disk is nearly dead, and out of reallocation
sectors.

At the very least, you do a *full* backup before
you do anything else. A backup to an external storage
device of some sort. With a full backup, you can restore
to the new hard drive you buy to replace it.

gddrescue on Linux can make a backup copy of the drive,
if a Windows utility like Macrium refuses to do so.

Paul

I've only ever ran chkdsk on my C: drive.

That only tests the integrity of the file system, not the sectors on the
physical disk. The /r switch will actually test the sectors.

I downloaded SeaTools for Windows and SeaTools Bootable. The Windows
tool notified me of failure but couldn't fix the errors causing the
fail. It suggested creating and using a SeaTools Bootable USB disk
which is capable of fixing errors. I ran the same tests with the
bootable USB and all tests passed after their scan fix. I want to
thank you VanguardLH and all those who replied with advice.

M.L. wrote:

VanguardLH wrote:

M.L. wrote:

I've only ever ran chkdsk on my C: drive.

That only tests the integrity of the file system, not the sectors on
the physical disk. The /r switch will actually test the sectors.

I downloaded SeaTools for Windows and SeaTools Bootable. The Windows
tool notified me of failure but couldn't fix the errors causing the
fail. It suggested creating and using a SeaTools Bootable USB disk
which is capable of fixing errors. I ran the same tests with the
bootable USB and all tests passed after their scan fix. I want to
thank you VanguardLH and all those who replied with advice.

No mention in your opening post as to the frequency of the reported bad
block in the Event Viewer. Was the frequency so often that now after
using SeaTools that you are sure the error cause has gone away?

On 03/12/2018 20.59, M.L. wrote:


Event Viewer: "The device, \Device\Harddisk0\DR0, has a bad block."

Got a Windows 10 BSOD, possibly from writing to a bad block.

It should not happen on a write, but on a read.

The disk firmware, when asked to write on a bad sector, writes instead
on a reserved spare sector and maps it, so that the computer never sees
that bad sector again (assuming the spare area is not spent).

On the other hand, a read would fail.

--
Cheers, Carlos.

On 12/4/18 2:18 AM, T wrote:
On 12/4/18 2:08 AM, T wrote:
On 12/3/18 11:59 AM, M.L. wrote:


Event Viewer: "The device, \Device\Harddisk0\DR0, has a bad block."

Got a Windows 10 BSOD, possibly from writing to a bad block. How can I
determine which drive is DR0? Can I assume C:? All partitions are on
the same disk. Drive O: is an external drive.
https://i.imgur.com/m7F1CH1.jpg

Will chkdsk /x /f /r check the entire hard drive, or must I specify a
specific drive (chkdsk c: /x /f /r )? Thanks.


Hi ML,

I see everyone has told you how to figure it out.Â* Plan on
replacing the hard drive.Â* Clonezilla is a good tool.Â* Make sure
the new hard drive is the same size or larger than the one.
(I can't be 1 MB smaller than the original.Â* There are ways
around it: you have resize the partition smaller.)

https://clonezilla.org/

-T


There is a section in advanced settings to skip bad sectors.
You will have to use it.


Advanced setting is called "Expert" and skip bad sectors is
called "Rescue". I cloned one this way yesterday. Had about
30 bad sectors that got skipped.