CHKDSK error.

I'm trying to fix a 4TB data disk (Seagate) that
cannot be CHKDSKed.

The CHKDSK starts but soon gives an error...

"An unspecified error occurred (766f6c756d652e63
470)".

I have tried....
sfc /scannow (as administrator)


and DISM, but nothing works.



Also, the cmd command does not work; the "cmd"
shows up on the start menu but will not start as
administrator or anything else.

(I have been doing the scans from another instance
of Windows10 on this same machine.)

Peter Jason wrote:
I'm trying to fix a 4TB data disk (Seagate) that
cannot be CHKDSKed.

The CHKDSK starts but soon gives an error...

"An unspecified error occurred (766f6c756d652e63
470)".

I have tried....
sfc /scannow (as administrator)


and DISM, but nothing works.



Also, the cmd command does not work; the "cmd"
shows up on the start menu but will not start as
administrator or anything else.

(I have been doing the scans from another instance
of Windows10 on this same machine.)


https://answers.microsoft.com/en-us/...1-efdc41897bf9

From a link off that page...

"wow I somehow just fixed it. I assigned a letter to
the system reserved and out of coriousity I went to
tools under properties and tried to click on error
checking link again (which by the way never worked the
other million times i tried it) and the link worked it
said i needed to dismount the drive to run and then it
ran and it said fixed the problem and i rebooted and no
error so i think it is fixed thanks for your help"

Which implies as a wild assed guess, it's related to
the mounting or dismounting of a hidden volume.

CHKDSK doesn't have to be done with a
drive letter, and can be done with a GUID as well. That's
if you have a way of figuring out the GUID of System Reserved
or whatever.

Hidden partition types of 0x27 instead of 0x07 might play a part,
but I doubt you could even get a CHKDSK to kick off, unless
it was visible.

No guarantees, but you might have better luck running
CHKDSK with the right parameters, from Command Prompt via
an emergency boot CD or via a Windows 10 install DVD
Command Prompt troubleshooting window.

Now, if the partition in question is a large NTFS on a GPT
disk and is just data and the partition type is a standard
0x07, I have no idea why an error like that pops up. I could
only see the one hit in Google.

Paul

On Fri, 04 Jan 2019 08:08:21 -0500, Paul
wrote:

Peter Jason wrote:
I'm trying to fix a 4TB data disk (Seagate) that
cannot be CHKDSKed.

The CHKDSK starts but soon gives an error...

"An unspecified error occurred (766f6c756d652e63
470)".

I have tried....
sfc /scannow (as administrator)


and DISM, but nothing works.



Also, the cmd command does not work; the "cmd"
shows up on the start menu but will not start as
administrator or anything else.

(I have been doing the scans from another instance
of Windows10 on this same machine.)


https://answers.microsoft.com/en-us/...1-efdc41897bf9

From a link off that page...

"wow I somehow just fixed it. I assigned a letter to
the system reserved and out of coriousity I went to
tools under properties and tried to click on error
checking link again (which by the way never worked the
other million times i tried it) and the link worked it
said i needed to dismount the drive to run and then it
ran and it said fixed the problem and i rebooted and no
error so i think it is fixed thanks for your help"

Which implies as a wild assed guess, it's related to
the mounting or dismounting of a hidden volume.

CHKDSK doesn't have to be done with a
drive letter, and can be done with a GUID as well. That's
if you have a way of figuring out the GUID of System Reserved
or whatever.

Hidden partition types of 0x27 instead of 0x07 might play a part,
but I doubt you could even get a CHKDSK to kick off, unless
it was visible.

No guarantees, but you might have better luck running
CHKDSK with the right parameters, from Command Prompt via
an emergency boot CD or via a Windows 10 install DVD
Command Prompt troubleshooting window.

Now, if the partition in question is a large NTFS on a GPT
disk and is just data and the partition type is a standard
0x07, I have no idea why an error like that pops up. I could
only see the one hit in Google.

Paul


Thanks.

I'll get right on to it.

On 1/3/2019 5:42 PM, Peter Jason wrote:
I'm trying to fix a 4TB data disk (Seagate) that
cannot be CHKDSKed.

The CHKDSK starts but soon gives an error...

"An unspecified error occurred (766f6c756d652e63
470)".

I have tried....
sfc /scannow (as administrator)


and DISM, but nothing works.



Also, the cmd command does not work; the "cmd"
shows up on the start menu but will not start as
administrator or anything else.

(I have been doing the scans from another instance
of Windows10 on this same machine.)

To add Run as Admin:
https://www.tenforums.com/tutorials/...dows-10-a.html
and
https://www.tenforums.com/tutorials/...dows-10-a.html

On Fri, 04 Jan 2019 12:42:52 +1100, Peter Jason wrote:

I'm trying to fix a 4TB data disk (Seagate) that
cannot be CHKDSKed.

Is it a NAS?

The CHKDSK starts but soon gives an error...

"An unspecified error occurred (766f6c756d652e63
470)".

I have tried....
sfc /scannow (as administrator)


and DISM, but nothing works.



Also, the cmd command does not work; the "cmd"
shows up on the start menu but will not start as
administrator or anything else.

(I have been doing the scans from another instance
of Windows10 on this same machine.)

Lucifer wrote:
On Fri, 04 Jan 2019 12:42:52 +1100, Peter Jason wrote:

I'm trying to fix a 4TB data disk (Seagate) that
cannot be CHKDSKed.

Is it a NAS?

The CHKDSK starts but soon gives an error...

"An unspecified error occurred (766f6c756d652e63
470)".

I have tried....
sfc /scannow (as administrator)


and DISM, but nothing works.



Also, the cmd command does not work; the "cmd"
shows up on the start menu but will not start as
administrator or anything else.

(I have been doing the scans from another instance
of Windows10 on this same machine.)

This is what the error looks like. You can see this
disk is in serious trouble because CHKDSK reports
"replacing bad clusters". Then, when it gets to the
end of doing that, it's going to be updating something
important as a "last step", and that "last step" is
likely compromised by a large number of surface errors
on the disk.

https://filestore.community.support....e-b4094f878467

Another example here.

https://i.stack.imgur.com/NHEF7.jpg

( https://superuser.com/questions/1254...756d652e63-470 )

Paul