Disk Error on W10

"Paul" wrote in message ...

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
sorry forgot to mention also ran chkdsk...all ok

"VanguardLH" wrote in message ...

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.
Van
I actually did all of what you mentioned....after posting for help.
I realized after the format that I should be running Chkdsk
I remembered a WD drive (like mine) has check tools available
and I need to leave a note to self that I should give more info
i blame it on old age lol
peter

On 9/11/2020 5:07 PM, pk121 wrote:
"Paul" wrote in message ...

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
sorry forgot to mention also ran chkdsk...all ok


Please, when replying to a message and quoting it, be sure to prefix all
the lines of the quote with a sign. Almost any decent newsreader will
do that automatically.

If you don't do that, it's hard to see what you're quoting and what
you're saying.



--
Ken

"pk121" wrote in message ...

"VanguardLH" wrote in message ...

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.
Van
I actually did all of what you mentioned....after posting for help.
I realized after the format that I should be running Chkdsk
I remembered a WD drive (like mine) has check tools available
and I need to leave a note to self that I should give more info
i blame it on old age lol
peter
testing the indent

On 9/12/2020 8:06 AM, pk121 wrote:
"pk121" wrote in message ...

"VanguardLH" wrote in message ...

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.
Van
I actually did all of what you mentioned....after posting for help.
I realized after the format that I should be running Chkdsk
I remembered a WD drive (like mine) has check tools available
and I need to leave a note to self that I should give more info
i blame it on old age lol
peter
testing the indent



I'll try one more time. Either format your replies properly with a
before quoted lines or I (and probably many others here) will killfile
you. Your replies are nearly impossible to understand.



--
Ken

pk121 wrote:

VanguardLH wrote:
snipped

I actually did all of what you mentioned....after posting for help.
I realized after the format that I should be running Chkdsk
I remembered a WD drive (like mine) has check tools available
and I need to leave a note to self that I should give more info
i blame it on old age lol
peter
testing the indent

If you're going to continue using a broken NNTP client then *YOU* have
to edit your replies to compensate for what the broken NNTP client does
not do, like prefix quoted lines (usually with one, or more, greater
than signs). If the client won't do it, then you have to.

Microsoft broke Windows Live Mail as of version 15. They changed an
internal component that neglected to quote the cited text. Then they
abandoned (discontinued support) of the product before they bothered to
fix it. Your replies turn into garbage with your reply content mixed
into the cited content.

Other reported problems is deleted e-mail keep returning, the Sender
column in the Sent folder shows the sender instead of the recipient
while also omitting the account name in the Account column, has a
problem with digitally signed e-mail (same as back in Outlook Express).
WLM doesn't support TLS 1.3 which is what the majority of e-mail
providers now require. SSL 3.0 was deprecated because it was insecure.
TLS 1.0 was SSL 3.0 renamed (so TLS 1.0 is also deprecated as being
insecure); however, TLS change the handshaking sequence to become
incompatible with SSL. Many providers now require TLS 1.3 for encrypted
connections. TLS 1.3 was ratified in Aug-2018. WLM was discontinued
back in Jun-2016.

Either change to a superior NNTP client, or *YOU* must compensate for
its screwups, like having to do the indentation by prefixing quotation
character(s) to all quoted lines to show proper hierarchy within the
body of your reply messsage, and indentation with the prefixed quoting
character is also required for the attribution lines. Because posters
tend to be lazy (also note the next comment about trimming), I have a
filter to colorize posts submitted by users of WLM v15+ (prior versions
are okay) since most never bother to do the formatting that disappeared
when Microsoft broke WLM. The colorizing gives me a heads up that the
poster's message is likely flattened (no quoting, loss of hierarchy)
making more difficult the differentiation between quoted and reply
content.

Trimming your reply is also part of Usenet netiquette and appreciated by
your readers. Provide sufficient context for your reply so the reply is
understood, not the entire history of a discussion.

Note the "in message news:messageID" in the attribution line is
superfluous. Anyone that wants that information can look in the
References header of your replies. The References header is used to
specify the hierarchy of replies within a subthread. The MIDs get
prepended to the References header. Adding the parent MID to the
attribution line just adds superfluous noise to it.

If you add your name at the end, that should be in a signature block,
not in the body of your post. However, since it should duplicate your
name in the comment field of your From header, a signature composed
merely of your name is superfluous.


Back to the original topic ...

Did you yet use a SMART tool to look at the Pending count to see if it
is zero?

On 9/11/2020 2:48 PM, 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??

peter
try https://www.hdsentinel.com/ without buying for a test of all
drives on your PC

On Sat, 12 Sep 2020 09:06:53 -0600, pk121 wrote:

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

chkdsk driveletter /r

Neat. I forgot about that command for the hardware testing tutorial!
o I'm gonna add your suggested cut-&-paste one liner:

o Win+R %comspec% /k chkdsk C: /r {control+shift+enter}
The type of the file system is NTFS.
Cannot lock current drive.
Chkdsk cannot run because the volume is in use by another
process. Would you like to schedule this volume to be
checked the next time the system restarts? (Y/N) y
This volume will be checked the next time the system restarts.

thanks

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??

peter
new reader test

VanguardLH wrote:
pk121 wrote:

VanguardLH wrote:
snipped

I actually did all of what you mentioned....after posting for help.
I realized after the format that I should be running Chkdsk
I remembered a WD drive (like mine) has check tools available
and I need to leave a note to self that I should give more info
i blame it on old age lol
peter
testing the indent

If you're going to continue using a broken NNTP client then *YOU* have
to edit your replies to compensate for what the broken NNTP client does
not do, like prefix quoted lines (usually with one, or more, greater
than signs). If the client won't do it, then you have to.

Microsoft broke Windows Live Mail as of version 15. They changed an
internal component that neglected to quote the cited text. Then they
abandoned (discontinued support) of the product before they bothered to
fix it. Your replies turn into garbage with your reply content mixed
into the cited content.

Other reported problems is deleted e-mail keep returning, the Sender
column in the Sent folder shows the sender instead of the recipient
while also omitting the account name in the Account column, has a
problem with digitally signed e-mail (same as back in Outlook Express).
WLM doesn't support TLS 1.3 which is what the majority of e-mail
providers now require. SSL 3.0 was deprecated because it was insecure.
TLS 1.0 was SSL 3.0 renamed (so TLS 1.0 is also deprecated as being
insecure); however, TLS change the handshaking sequence to become
incompatible with SSL. Many providers now require TLS 1.3 for encrypted
connections. TLS 1.3 was ratified in Aug-2018. WLM was discontinued
back in Jun-2016.

Either change to a superior NNTP client, or *YOU* must compensate for
its screwups, like having to do the indentation by prefixing quotation
character(s) to all quoted lines to show proper hierarchy within the
body of your reply messsage, and indentation with the prefixed quoting
character is also required for the attribution lines. Because posters
tend to be lazy (also note the next comment about trimming), I have a
filter to colorize posts submitted by users of WLM v15+ (prior versions
are okay) since most never bother to do the formatting that disappeared
when Microsoft broke WLM. The colorizing gives me a heads up that the
poster's message is likely flattened (no quoting, loss of hierarchy)
making more difficult the differentiation between quoted and reply
content.

Trimming your reply is also part of Usenet netiquette and appreciated by
your readers. Provide sufficient context for your reply so the reply is
understood, not the entire history of a discussion.

Note the "in message news:messageID" in the attribution line is
superfluous. Anyone that wants that information can look in the
References header of your replies. The References header is used to
specify the hierarchy of replies within a subthread. The MIDs get
prepended to the References header. Adding the parent MID to the
attribution line just adds superfluous noise to it.

If you add your name at the end, that should be in a signature block,
not in the body of your post. However, since it should duplicate your
name in the comment field of your From header, a signature composed
merely of your name is superfluous.


Back to the original topic ...

Did you yet use a SMART tool to look at the Pending count to see if it
is zero?

I changed to Seamonkey...now need to learn how to use it.
was using Win Live Mail.....thanks for the advice
peter

Peter Kaupp wrote:
....
I changed to Seamonkey...now need to learn how to use it.
was using Win Live Mail.....thanks for the advice
peter

FYI. SeaMonkey's web browser is old, slow, and uses a lot of resources (e.g., RAM
and CPU).
--
Life's so loco! ..!.. *isms, sins, hates, (d)evil, illnesses (e.g., COVID-19/2019-nCoV/SARS-CoV-2), deaths (RIP), interruptions, stresses, heat waves, fires, out(r)ages, dramas, unlucky #4, 2020, greeds, bugs (e.g., crashes & female mosquitoes), etc.
Note: A fixed width font (Courier, Monospace, etc.) is required to see this signature correctly.
/\___/\ Ant(Dude) @ http://aqfl.net & http://antfarm.home.dhs.org /
/ /\ /\ \ http://antfarm.ma.cx. Please nuke ANT if replying by e-mail.
| |o o| |
\ _ /
( )

Ant wrote:
Peter Kaupp wrote:
...
I changed to Seamonkey...now need to learn how to use it.
was using Win Live Mail.....thanks for the advice
peter

FYI. SeaMonkey's web browser is old, slow, and uses a lot of resources (e.g., RAM
and CPU).

Seamonkey is a suite (like Netscape Communicator before it),
and has a USENET-news-capable agent with working quoting.

Thunderbird, Seamonkey, and Netscape Communicator share
some code. The source files, you can see ns_
routines in there, which came from Netscape.

You don't have to use the browser portion of Seamonkey
if you don't want to.

The browser portion of Seamonkey supports the HTML rendering
that the USENET reader might call for.

The current version of Seamonkey is unlikely to work on WinXP,
and evil forces on the Internet are now working on seeing that
we can't use 2.31 any more. You'd need a Seamonkey up around
2.49.4 or so. That's Google at work for you, working to undermine
the freedom of the Internet. The current version of Seamonkey is
likely higher than that value (zooming away from WinXP).

Paul

Peter Kaupp wrote:
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??

peter
new reader test


It's working.

Using a bad block scan of the drive at the physical layer
would reveal where the problem is, and suggest what
approach to use. As others have suggested, running a drive
which presents real CRC errors - the drive is telling you
it's near end of life. It's run out of spare sectors near
the damaged area. There could be the possibility of
further data loss near the CRC error.

https://www.system-rescue-cd.org/Download/

# 64 bit version
https://osdn.net/projects/systemresc...md64-6.1.8.iso

# if CPU only supports 32 bit
https://osdn.net/projects/systemresc...i686-6.1.8.iso

It says to use "startx" if you want, which starts up
the OS GUI, but you don't even need to do that much.

The terminal window without "startx" has no scrollback,
and using "startx" gives you a better place to work.

Doing a "reboot now" should cleanly end the session.
Since you're root, no "sudo" needed.

Example of my session, testing sda for read errors.

https://i.postimg.cc/0j4DT3vM/Sys-Rescue64.gif

Paul

"Paul" wrote in message ...

Peter Kaupp wrote:
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??

peter
new reader test


It's working.

Using a bad block scan of the drive at the physical layer
would reveal where the problem is, and suggest what
approach to use. As others have suggested, running a drive
which presents real CRC errors - the drive is telling you
it's near end of life. It's run out of spare sectors near
the damaged area. There could be the possibility of
further data loss near the CRC error.

https://www.system-rescue-cd.org/Download/

# 64 bit version
https://osdn.net/projects/systemresc...md64-6.1.8.iso

# if CPU only supports 32 bit
https://osdn.net/projects/systemresc...i686-6.1.8.iso

It says to use "startx" if you want, which starts up
the OS GUI, but you don't even need to do that much.

The terminal window without "startx" has no scrollback,
and using "startx" gives you a better place to work.

Doing a "reboot now" should cleanly end the session.
Since you're root, no "sudo" needed.

Example of my session, testing sda for read errors.

https://i.postimg.cc/0j4DT3vM/Sys-Rescue64.gif

Paul

Thanks Paul
I am downloading it now and will run and test tommorow

"pk121" wrote in message ...

"Paul" wrote in message ...

Peter Kaupp wrote:
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??

peter
new reader test


It's working.

Using a bad block scan of the drive at the physical layer
would reveal where the problem is, and suggest what
approach to use. As others have suggested, running a drive
which presents real CRC errors - the drive is telling you
it's near end of life. It's run out of spare sectors near
the damaged area. There could be the possibility of
further data loss near the CRC error.

https://www.system-rescue-cd.org/Download/

# 64 bit version
https://osdn.net/projects/systemresc...md64-6.1.8.iso

# if CPU only supports 32 bit
https://osdn.net/projects/systemresc...i686-6.1.8.iso

It says to use "startx" if you want, which starts up
the OS GUI, but you don't even need to do that much.

The terminal window without "startx" has no scrollback,
and using "startx" gives you a better place to work.

Doing a "reboot now" should cleanly end the session.
Since you're root, no "sudo" needed.

Example of my session, testing sda for read errors.

https://i.postimg.cc/0j4DT3vM/Sys-Rescue64.gif

Paul

Thanks Paul


I am downloading it now and will run and test tommorow

damn still no