Does CHKDSK command scan locked folders?

[Alceryes]

I'm working on a laptop hard disk in my test bed system (both WinXP).
A "chkdsk e: /f /r" command reveals nothing wrong with the hard disk. But
when I booted up the administrator account (my system) and tried to take
ownership of the drive (and all subfolders) it started clicking like crazy
after just a minute.
It seems that the chkdsk command ignored parts of the hard disk because they
were locked or it could just be coinsidense...(?)

 

[Malke]

I'm working on a laptop hard disk in my test bed system (both WinXP).
A "chkdsk e: /f /r" command reveals nothing wrong with the hard disk.
But when I booted up the administrator account (my system) and tried
to take ownership of the drive (and all subfolders) it started
clicking like crazy after just a minute.
It seems that the chkdsk command ignored parts of the hard disk
because they were locked or it could just be coinsidense...(?)

Run a diagnostic on the drive with a utility downloaded from the hard
drive mftr. Clicking is a Bad Thing and the drive mftr.'s diagnostic
will be more precise in determining if there is a problem. Do a
thorough scan.

Malke

 

[Galen]

In Alceryes <[email protected]> had this to say:

My reply is at the bottom of your sent message:

I'm working on a laptop hard disk in my test bed system (both WinXP).
A "chkdsk e: /f /r" command reveals nothing wrong with the hard disk.
But when I booted up the administrator account (my system) and tried
to take ownership of the drive (and all subfolders) it started
clicking like crazy after just a minute.
It seems that the chkdsk command ignored parts of the hard disk
because they were locked or it could just be coinsidense...(?)

I'm assuming you ran it from the command line, scheduled it, and rebooted
and then it did the scan?


As it runs from outside of the OS without any account being logged into (I'm
guessing you didn't do it from the recovery console) it will happily check
the disk and file structure for any/all files. That awful clicking noise you
heard is a potential bad sign however and it's time to look into replacing
the drive IF you're sure that it's the drive itself that was making the
noise though in a laptop I can't really think of what else might have been
making the noise so it probably is the drive. Using one of the various
tools, with SMART enabled, does the drive read as healthy?

Galen
--

"You know that a conjurer gets no credit when once he has explained his
trick; and if I show you too much of my method of working, you will
come to the conclusion that I am a very ordinary individual after all."

Sherlock Holmes

 

[Alceryes]

As it runs from outside of the OS without any account being logged into

(I'm guessing you didn't do it from the recovery console) it will happily
check the disk and file structure for any/all files.

All tests were run from a test computer (hard disk in question, chained as
secondary). If what you say is true they why have I run into several
instances where folders on the "test" hard disk give me an access denied
message? This is happened on many occasions with multiple HD's in my test
system.
I know my test bed OS is perfectly clean. I also booted from a powermax disk
and the advanced scan reported the hard disk was fine as well. That's why
I'm wondering about the 'chkdsk' command(?)
I knew the HD was toast the instant I started hearing the clicking. The HD
in question is now in the freezer so that later I'll have the best chance of
getting as much data off as possible.
--


"I don't cheat to survive. I cheat to LIVE!!"
- Alceryes

 

[Malke]

All tests were run from a test computer (hard disk in question,
chained as secondary). If what you say is true they why have I run
into several instances where folders on the "test" hard disk give me
an access denied message? This is happened on many occasions with
multiple HD's in my test system.
I know my test bed OS is perfectly clean. I also booted from a
powermax disk and the advanced scan reported the hard disk was fine as
well. That's why I'm wondering about the 'chkdsk' command(?)
I knew the HD was toast the instant I started hearing the clicking.
The HD in question is now in the freezer so that later I'll have the
best chance of getting as much data off as possible.

The "access denied"messages are because you are trying to get those
files from a Windows XP system user account that doesn't own the files.
The "access denied" error message on files is easily solved by taking
ownership of those files. Either type "take ownership" into XP's Help &
Support or see this link:

Take Ownership of a File or Folder in Windows XP [Q308421] -
http://support.microsoft.com/?kbid=308421

Malke

 

[Galen]

In Alceryes <[email protected]> had this to say:

My reply is at the bottom of your sent message:

All tests were run from a test computer (hard disk in question,
chained as secondary). If what you say is true they why have I run
into several instances where folders on the "test" hard disk give me
an access denied message? This is happened on many occasions with
multiple HD's in my test system.
I know my test bed OS is perfectly clean. I also booted from a
powermax disk and the advanced scan reported the hard disk was fine
as well. That's why I'm wondering about the 'chkdsk' command(?)
I knew the HD was toast the instant I started hearing the clicking.
The HD in question is now in the freezer so that later I'll have the
best chance of getting as much data off as possible.

Are you doing the chkdsk from outside the OS?

I'd do as Malke has suggested and take ownership of the files - take
ownership of what you can access RIGHT now and then worry about the ones
that you can't access. Getting as much data back as you can is likely your
primary goal at this point and continued attempts to run the heads across
the platters is (from the sounds of this) not in your best interest. So long
as you're inside the OS you'll have trouble doing much with files that you
don't have access to. It might be worth trying it from the recovery console.
Reboot to the XP CD and follow the prompts to use RC and then bring up the
help because the commands are different for chkdsk in RC. However don't do
so until you've recovered all the data that you can unless this is a matter
of dire importance in which case take it to a specialized recovery company
in your area or one found online.

That'd be where I'd go from here.

Galen
--

"You know that a conjurer gets no credit when once he has explained his
trick; and if I show you too much of my method of working, you will
come to the conclusion that I am a very ordinary individual after all."

Sherlock Holmes