Disk Error on W10

The IO operation at logical block address 0x3a4fcf00 for Disk 1 (PDO name:
\Device\00000038) was retried.
using W10 V 20H2 Build 19042.508 Xperince pack 120.2212.31.0

I have formatted the drive....deleted the drive....reinstalled the AMD
Drivers...
and it just keeps coming back.
Any suggestions?? any Help?? anyone else have this??

peter

pk121 wrote:

Any suggestions??

throw it away, buy a new one

"Andy Burns" wrote in message ...

pk121 wrote:

Any suggestions??

throw it away, buy a new one

an explanation would be helpful

"pk121" wrote:

"Andy Burns" wrote
pk121 wrote:

Any suggestions??

throw it away, buy a new one

an explanation would be helpful

Please get a real newsreader.

John Doe wrote:
"pk121" wrote:

"Andy Burns" wrote
pk121 wrote:

Any suggestions??

throw it away, buy a new one

an explanation would be helpful

Please get a real newsreader.

You mean the QuoteFix thing :-)
A toast to MSFT and their inability to quote...

Paul

On 11 Sep 2020, pk121 wrote
(in article ):

"Andy Burns" wrote in message ...

pk121 wrote:

Any suggestions??

throw it away, buy a new one

an explanation would be helpful

you’re having i/o errors. The drive is not long for the world. Get rid of
it.

On Fri, 11 Sep 2020 12:48:01 -0600, pk121 wrote:

I have formatted the drive....deleted the drive....reinstalled the AMD
Drivers...
and it just keeps coming back.
Any suggestions?? any Help?? anyone else have this??

If you want a diagnostic test of the hard disk drive, this may help:
o What hardware diagnostic stress-testing freeware can you recommend?
https://groups.google.com/forum/#!topic/alt.comp.freeware/dkkdOmL95d8

I'm writing a tutorial, as we type, so if you wait a bit,
you can follow the tutorial where, after about five or ten minutes (it took
me days) you will have your HDD diagnostic tests ready to run.

A link to the tutorial will be posted to that thread when ready.
NOTE: It takes longer to write it up than it takes to do it.

pk121 wrote:
"Andy Burns" wrote in message ...
pk121 wrote:

Any suggestions??

throw it away, buy a new one

an explanation would be helpful

The file system has clusters. They're 8 sectors
or 4096 bytes in length. That's the default when you
install Windows 10 and allow Windows 10 to prep the partition.

If the OS ever read-scans a partition, and it finds a
single sector which is bad ("CRC error"), it says to itself
"which cluster does this belong to?".

It then adds the cluster number to $BADCLUS.
$BADCLUS is a way of mapping out bad clusters,
so they're no longer used. If you poke a hole in
a file with $BADCLUS, I presume there is data loss
occurring. In any case, find an article which discusses
how $BADCLUS works, and it may clarify the data loss part.

The ideal situation, for a user who wants to run
with a bad cluster is:

1) Format partition NTFS.
2) Do a CHKDSK, including the option which causes
a read verify from end to end.
3) The cluster is mapped out, the one with the error.
4) Now, do a file-by-file copy of the backed up file
system, to the file system with the (patched-up)
defect. Since the file system will now refuse to use
a location in $BADCLUS, you cannot endanger any file
by storing it there. Any little dialog boxes, no longer
have to raise their ugly heads.

Of course, this sequence is un-possible, as you're trying
to do this for a Windows 10 C: partition, which is a *pig*
in terms of file system feature usage. It's very hard
to make identical file-by-file copies and make them
exactly identical. If this was a data-only partition
on Drive #2, then the file-by-file copy done in step 4
would be dead easy. Data partitions use very few file
system features. Normally the permissions are quite
benign.

Now, a smart person, noticing that the bad cluster raises
it's ugly head so soon, that says the bad cluster is
nearer to the beginning of the partition. A person
could resize the partition, pushing the origin forward
X number of gigabytes, until that cluster is no longer
within the file system.

People have done that before, taking a large disk
and moving/resizing partitions to avoid bad spot(s),
and make "pseudo-clean" partitions. Then hoping that
no more bad spots appear.

0 badclus 0 badclus
+-----+------------+----------+-----------+----------+
| MBR | partition | badspot | partition | badspot |
+-----+------------+----------+-----------+----------+

A check of SMART will tell you how bad the disk is,
and whether "ye should abandon all hope". Andy is bang on
here - the CRC error tells you the drive has no spares in
the small area in question, which suggests you might see
the Reallocated in dire shape, and the appearance of more
bad clusters could be right around the corner, complete
with various degrees of data loss.

If you like roulette where the house has the odds,
then it's nothing but disk losses for you... That's
why Andy told you to chuck it.

Now, me personally, I need to keep drives like that
in my inventory, so I can practice data recovery on
them. If you don't have drives with CRC errors, it's
possible by various means to "fake it", but perhaps
not portably (like if I wanted to compare a Linux
recovery method and a Windows recovery method). Real
CRC errors make good test cases for me :-) But I don't
keep my "good" data on there. Just test partitions
and see if I can recover stuff.

By all means, continue to fiddle with your $BADCLUS.
As long as *none* of the files on C: matter to you,
what's the harm ? Like, say a $BADCLUS appears right
in the middle of your email PST. The PST, the whole thing,
could be ruined. And so on. Some file formats are such,
a small defect ruins them. A Macrium .mrimg works that way!
That means using a drive with "CRC pimples" appearing,
would be a **** poor choice for storing fresh Macrium .mrimg.
The files could be ruined very easily from an odds
perspective.

I did my first data recovery around 1985 or so :-)
It was loads of fun, that's for sure. On drives that
cost $1200 to $1500 or so.

Carry on.

Paul

Paul wrote:

John Doe wrote:
"pk121" wrote:
"Andy Burns" wrote
pk121 wrote:

Any suggestions??

throw it away, buy a new one

an explanation would be helpful

Please get a real newsreader.

You mean the QuoteFix thing :-)
A toast to MSFT and their inability to quote...

Microsoft's inability to do anything except Windows has always shown
through. And that's just because Windows is a money cow. Necessity is
the mother of invention.




--

Time to move to a new motherboard!

On Fri, 11 Sep 2020 17:27:10 -0400, Paul wrote:

Now, a smart person, noticing that the bad cluster raises
it's ugly head so soon, that says the bad cluster is
nearer to the beginning of the partition. A person
could resize the partition, pushing the origin forward
X number of gigabytes, until that cluster is no longer
within the file system.

Paul,
Do you think this tool, on Hirens Boot CD, will show the user
enough information to determine "where" the bad clusters lie?
https://i.postimg.cc/WpGqxJJq/hiren14.jpg

It's called "HDTune" and that's a look at my disk yesterday:
https://i.postimg.cc/fTjR2hs9/hiren10.jpg

Arlen Holder wrote:
On Fri, 11 Sep 2020 17:27:10 -0400, Paul wrote:

Now, a smart person, noticing that the bad cluster raises
it's ugly head so soon, that says the bad cluster is
nearer to the beginning of the partition. A person
could resize the partition, pushing the origin forward
X number of gigabytes, until that cluster is no longer
within the file system.

Paul,
Do you think this tool, on Hirens Boot CD, will show the user
enough information to determine "where" the bad clusters lie?
https://i.postimg.cc/WpGqxJJq/hiren14.jpg

It's called "HDTune" and that's a look at my disk yesterday:
https://i.postimg.cc/fTjR2hs9/hiren10.jpg

ddrescue might give you exact locations.

I can't tell you because I have no drive with CRC errors
available for testing. I have Reallocations but they don't
allow ddrescue testing such that the log will have
some nice entries in it.

HDTune shows red colored "blocks". The blocks are huge and
encompass many many clusters. It is likely good enough for
gross partition planning. For example, if all the red blocks were
up near the end of the disk, it would be easy to shrink a partition
to avoid that area.

For dodging a picket fence of errors, you'd want a bit more
precision or something.

Regular "dd" stops on the first CRC error, and consequently
a user can still use it, except they have to learn how to use
"seek" and "skip" operators to steer it to the right starting
address to pick up the test and test the next session. Every
error requires "dd" to be restarted as a read-verifier. You could
probably script that if you were a crafty individual. Whereas
ddrescue, it lives for situations like that and the hard
part is decoding the logfile later. The logfile uses notations
to compress the content. "Bad block at 1234 for 103 sectors"
but in a human-unfriendly syntax.

Paul

pk121 wrote:

The IO operation at logical block address 0x3a4fcf00 for Disk 1 (PDO name:
\Device\00000038) was retried.
using W10 V 20H2 Build 19042.508 Xperince pack 120.2212.31.0

I have formatted the drive....

There is more than one manufacturer of hard disk drives (HDDs) and solid
state drives (SSDs) along with multiple models of products by each
manufacturer. Could be an internal or external (removable) drive.
Don't expect focused responses on vague descriptions.

deleted the drive....reinstalled the AMD Drivers... and it just keeps
coming back.

Formatting doesn't do a surface check. In a command shell with admin
privileges, run:

chkdsk driveletter /r

In addition, get and use the diagnostics tool from whomever manufactured
the drive (you didn't give brand and model or even the type of drive,
like HDD versus SSD).

For an HDD, use a SMART tool to look at the Current Pending Sector Count
attribute. That shows how many bad sectors were discovered but are
still awaiting reallocation to reserve sectors. That is, sectors were
found that were bad, are pending reallocation to reserve sectors (for
remapping), and once reallocated the Pending count goes down. If the
Pending count does not decrease after, say, a reboot then there are no
more reserve sectors to which bads one can get remapped which means
those sectors remain bad.

https://kb.acronis.com/content/9133

That's for an HDD. Again, you never gave any information on just what
drive by brand, model, and type is causing problems. SSDs won't have a
Pending attribute for SMART data due to their wear leveling scheme.
SMART attributes for SSDs have not yet become as standardized as with
HDDs, so get the health monitor tool from whomever made the SSD to see
what it says regarding the health of the SSD.

On Fri, 11 Sep 2020 12:48:01 -0600, "pk121" wrote:

The IO operation at logical block address 0x3a4fcf00 for Disk 1 (PDO name:
\Device\00000038) was retried.
using W10 V 20H2 Build 19042.508 Xperince pack 120.2212.31.0

I have formatted the drive....deleted the drive....reinstalled the AMD
Drivers...
and it just keeps coming back.
Any suggestions?? any Help?? anyone else have this??

I've had thousands of disk errors in Event Viewer very similar to yours
over the past 10-12 years and in each and every case reseating the SATA
cable clears it up for a period of time. Eventually I replace the cable
which clears up the errors on that drive for a few more years. Across two
PCs I have 26 drives connected internally, so 'retry' errors are common. I
don't even worry about it until it gets really bad. I've never seen that
error caused by a failing drive. For me, it's always cable-related.

It's a lot cheaper to reseat or replace a cable than to do the same with a
hard drive, so I would try that first.

"Paul" wrote in message ...

pk121 wrote:
"Andy Burns" wrote in message ...
pk121 wrote:

Any suggestions??

throw it away, buy a new one

an explanation would be helpful

The file system has clusters. They're 8 sectors
or 4096 bytes in length. That's the default when you
install Windows 10 and allow Windows 10 to prep the partition.

If the OS ever read-scans a partition, and it finds a
single sector which is bad ("CRC error"), it says to itself
"which cluster does this belong to?".

It then adds the cluster number to $BADCLUS.
$BADCLUS is a way of mapping out bad clusters,
so they're no longer used. If you poke a hole in
a file with $BADCLUS, I presume there is data loss
occurring. In any case, find an article which discusses
how $BADCLUS works, and it may clarify the data loss part.

The ideal situation, for a user who wants to run
with a bad cluster is:

1) Format partition NTFS.
2) Do a CHKDSK, including the option which causes
a read verify from end to end.
3) The cluster is mapped out, the one with the error.
4) Now, do a file-by-file copy of the backed up file
system, to the file system with the (patched-up)
defect. Since the file system will now refuse to use
a location in $BADCLUS, you cannot endanger any file
by storing it there. Any little dialog boxes, no longer
have to raise their ugly heads.

Of course, this sequence is un-possible, as you're trying
to do this for a Windows 10 C: partition, which is a *pig*
in terms of file system feature usage. It's very hard
to make identical file-by-file copies and make them
exactly identical. If this was a data-only partition
on Drive #2, then the file-by-file copy done in step 4
would be dead easy. Data partitions use very few file
system features. Normally the permissions are quite
benign.

Now, a smart person, noticing that the bad cluster raises
it's ugly head so soon, that says the bad cluster is
nearer to the beginning of the partition. A person
could resize the partition, pushing the origin forward
X number of gigabytes, until that cluster is no longer
within the file system.

People have done that before, taking a large disk
and moving/resizing partitions to avoid bad spot(s),
and make "pseudo-clean" partitions. Then hoping that
no more bad spots appear.

0 badclus 0 badclus
+-----+------------+----------+-----------+----------+
| MBR | partition | badspot | partition | badspot |
+-----+------------+----------+-----------+----------+

A check of SMART will tell you how bad the disk is,
and whether "ye should abandon all hope". Andy is bang on
here - the CRC error tells you the drive has no spares in
the small area in question, which suggests you might see
the Reallocated in dire shape, and the appearance of more
bad clusters could be right around the corner, complete
with various degrees of data loss.

If you like roulette where the house has the odds,
then it's nothing but disk losses for you... That's
why Andy told you to chuck it.

Now, me personally, I need to keep drives like that
in my inventory, so I can practice data recovery on
them. If you don't have drives with CRC errors, it's
possible by various means to "fake it", but perhaps
not portably (like if I wanted to compare a Linux
recovery method and a Windows recovery method). Real
CRC errors make good test cases for me :-) But I don't
keep my "good" data on there. Just test partitions
and see if I can recover stuff.

By all means, continue to fiddle with your $BADCLUS.
As long as *none* of the files on C: matter to you,
what's the harm ? Like, say a $BADCLUS appears right
in the middle of your email PST. The PST, the whole thing,
could be ruined. And so on. Some file formats are such,
a small defect ruins them. A Macrium .mrimg works that way!
That means using a drive with "CRC pimples" appearing,
would be a **** poor choice for storing fresh Macrium .mrimg.
The files could be ruined very easily from an odds
perspective.

I did my first data recovery around 1985 or so :-)
It was loads of fun, that's for sure. On drives that
cost $1200 to $1500 or so.

Carry on.

Paul
OS and boot is on an SSD drive..I have 2 identical WD platter drives
It was one of those.....I had to check device manager to see which one
I backed the files(not a boot drive nor W10 drive) with True Image
I formatted the Drive twice....went into device manager to check drives by
connection
as I had read connectors could be a problem.. Up came a bunch of Intel
drivers oops!!
must be leftover from when I changed Mobo and CPU from Intel to AMD but did
not reinstall
W10 new...(slap on wrist!) I deleted all of them except the Intel wireless
and the Intel SSD.
Rebooted and no more disk errors............I restored the backed up files
to the drive
rebooted and still no disk errors..............(cross my fingers)
thanks for the help everyone
peter

"Arlen Holder" wrote in message ...

On Fri, 11 Sep 2020 12:48:01 -0600, pk121 wrote:

I have formatted the drive....deleted the drive....reinstalled the AMD
Drivers...
and it just keeps coming back.
Any suggestions?? any Help?? anyone else have this??

If you want a diagnostic test of the hard disk drive, this may help:
o What hardware diagnostic stress-testing freeware can you recommend?
https://groups.google.com/forum/#!topic/alt.comp.freeware/dkkdOmL95d8

I'm writing a tutorial, as we type, so if you wait a bit,
you can follow the tutorial where, after about five or ten minutes (it took
me days) you will have your HDD diagnostic tests ready to run.

A link to the tutorial will be posted to that thread when ready.
NOTE: It takes longer to write it up than it takes to do it.

I ran the WD diagnostic tool...everythin was fine

ty
peter