Weird access deniel problems to a non system disk

  • Thread starter Thread starter David F
  • Start date Start date
D

David F

Using Windows 2000 Pro + SP4.
I have a bootable system HD (C:) and a data HD (D:).
Drive C: has programs only and drive D: data only.
All of a sudden, I have access problems to certain folders
on drive D:.
I know for sure that it has nothing to do with the programs
on drive C: because I have back drives that are a clone of
drive C:, have been created well before the problem on D:
occured and when I try using those backup system drives
I see the same phenomena. Here are the symptoms:

Windows Explorer can access the root and many folders
but for certain folders, I have to wait very long to open the
folder in the Folder pane (when clicking the + sign) and as
keep going down the tree I finaly hit hit a folder for which
after some lenghty wait it respond:
"Path xxx is not accessible.
Error performing in page operation."

When trying to run Chkdsk D: I get immediately the response:
"Access denied" w/o out it even progress anywhere. This is
in spite Windows Explorer does not have access problem
to that drive in general.!

When trying to select a drive in the Explorer's folder pane,
then Properties->Tools->Error Checking, I get immediately,
seemingly w/o even progressing a bit the response:
"Windows was unable to complete the disk check".

Given that madness that went into drive D:, I don't know even
where/how to start analyzing the problem.

Does anybody know a decent and reliable tool that can tell
what is the problem, that instead of responding with such
infamous idiotic messages such "Access denied", it will tell
WHY is the access denied, or the "...inpage operation"
mentioned above, etc., that tells me nothing and possibly
even help to fix the problem, or at least help salvage folders
which are still reliably accessible?

Many thanks in advance,
David
 
The drive may have failed. Download and run a diagnostic utility from the
drive manufacturer's web site.

After backup you can also run;
chkdsk /r
from the recovery console command line. (/r implies /f )

To start the Recovery Console, start the computer from the Windows 2000
Setup CD or the Windows 2000 Setup floppy disks. If you do not have Setup
floppy disks and your computer cannot start from the Windows 2000 Setup CD,
use another Windows 2000-based computer to create the Setup floppy disks. At
the "Welcome to Setup" screen. Press F10 or R to repair a Windows 2000
installation, and then press C to use the Recovery Console. The Recovery
Console then prompts you for the administrator password. If you do not have
the correct password, Recovery Console does not allow access to the
computer. If an incorrect password is entered three times, the Recovery
Console quits and restarts the computer. Note If the registry is corrupted
or missing or no valid installations are found, the Recovery Console starts
in the root of the startup volume without requiring a password. You cannot
access any folders, but you can carry out commands such as chkdsk, fixboot,
and fixmbr for limited disk repairs. Once the password has been validated,
you have full access to the Recovery Console, but limited access to the hard
disk. You can only access the following folders on your computer: drive
root, %systemroot% or %windir%

--
Regards,

Dave Patrick ....Please no email replies - reply in newsgroup.
Microsoft Certified Professional
Microsoft MVP [Windows]
http://www.microsoft.com/protect

:
| Using Windows 2000 Pro + SP4.
| I have a bootable system HD (C:) and a data HD (D:).
| Drive C: has programs only and drive D: data only.
| All of a sudden, I have access problems to certain folders
| on drive D:.
| I know for sure that it has nothing to do with the programs
| on drive C: because I have back drives that are a clone of
| drive C:, have been created well before the problem on D:
| occured and when I try using those backup system drives
| I see the same phenomena. Here are the symptoms:
|
| Windows Explorer can access the root and many folders
| but for certain folders, I have to wait very long to open the
| folder in the Folder pane (when clicking the + sign) and as
| keep going down the tree I finaly hit hit a folder for which
| after some lenghty wait it respond:
| "Path xxx is not accessible.
| Error performing in page operation."
|
| When trying to run Chkdsk D: I get immediately the response:
| "Access denied" w/o out it even progress anywhere. This is
| in spite Windows Explorer does not have access problem
| to that drive in general.!
|
| When trying to select a drive in the Explorer's folder pane,
| then Properties->Tools->Error Checking, I get immediately,
| seemingly w/o even progressing a bit the response:
| "Windows was unable to complete the disk check".
|
| Given that madness that went into drive D:, I don't know even
| where/how to start analyzing the problem.
|
| Does anybody know a decent and reliable tool that can tell
| what is the problem, that instead of responding with such
| infamous idiotic messages such "Access denied", it will tell
| WHY is the access denied, or the "...inpage operation"
| mentioned above, etc., that tells me nothing and possibly
| even help to fix the problem, or at least help salvage folders
| which are still reliably accessible?
|
| Many thanks in advance,
| David
|
|
 
Hi DAvid,


Unfortunately your drive seems to be failing.

I ran into the same problems like you 3 days ago.
My Maxtor 200GB was failing. I was able to save 150GB.
From missing 30GB I managed to salvage 25GB. Sigh....
I even fixed the disk.

Here's what to do and to do NOT:
-----------------------------------
To avoid further damage to your data:
1. DO NOT access the drive unless really neccessary.
2. DO NOT run windows DiskCheck and Chkdsk (/r)
3. DO NOT defrag the drive.
4. DO NOT run a diagnostic from the drive manufacturer YET.
5. BEST PRACTICE is to make a disk image to another disk
.. (set imager to ignore read errors)
.. a. Disconnect failing drive to avoid more damage.
.. b. Copy/repair data on the image disk.
.. If best practice is not possible then work on your failing drive.
6. Copy all accessible data to another disk (or burn to a cd/dvd).
7. Write down which folders / files report errors while copying.
8. If all important data could be copied, skip the next step.
9. If still important but inaccessible data left to salvage surf to
.. www.runtime.org and get GetDataBack for NTFS (or FAT)
.. You'll need something to register the program.
.. You'll be amazed to see what this tool is capable of.
.. Follow the steps as instructed by GetDataBack.
10. Run the diagnostic tool provided by the drive manufacturer.
.. Even if the tool suggests to return the drive, depending on the
.. defect, you might be able to fix the drive.

To be continued...
But first report your results back here.

HTH,
John7



Dave Patrick said:
The drive may have failed. Download and run a diagnostic utility from the
drive manufacturer's web site.

After backup you can also run;
chkdsk /r
from the recovery console command line. (/r implies /f )

To start the Recovery Console, start the computer from the Windows 2000
Setup CD or the Windows 2000 Setup floppy disks. If you do not have Setup
floppy disks and your computer cannot start from the Windows 2000 Setup CD,
use another Windows 2000-based computer to create the Setup floppy disks. At
the "Welcome to Setup" screen. Press F10 or R to repair a Windows 2000
installation, and then press C to use the Recovery Console. The Recovery
Console then prompts you for the administrator password. If you do not have
the correct password, Recovery Console does not allow access to the
computer. If an incorrect password is entered three times, the Recovery
Console quits and restarts the computer. Note If the registry is corrupted
or missing or no valid installations are found, the Recovery Console starts
in the root of the startup volume without requiring a password. You cannot
access any folders, but you can carry out commands such as chkdsk, fixboot,
and fixmbr for limited disk repairs. Once the password has been validated,
you have full access to the Recovery Console, but limited access to the hard
disk. You can only access the following folders on your computer: drive
root, %systemroot% or %windir%

--
Regards,

Dave Patrick ....Please no email replies - reply in newsgroup.
Microsoft Certified Professional
Microsoft MVP [Windows]
http://www.microsoft.com/protect

:
| Using Windows 2000 Pro + SP4.
| I have a bootable system HD (C:) and a data HD (D:).
| Drive C: has programs only and drive D: data only.
| All of a sudden, I have access problems to certain folders
| on drive D:.
| I know for sure that it has nothing to do with the programs
| on drive C: because I have back drives that are a clone of
| drive C:, have been created well before the problem on D:
| occured and when I try using those backup system drives
| I see the same phenomena. Here are the symptoms:
|
| Windows Explorer can access the root and many folders
| but for certain folders, I have to wait very long to open the
| folder in the Folder pane (when clicking the + sign) and as
| keep going down the tree I finaly hit hit a folder for which
| after some lenghty wait it respond:
| "Path xxx is not accessible.
| Error performing in page operation."
|
| When trying to run Chkdsk D: I get immediately the response:
| "Access denied" w/o out it even progress anywhere. This is
| in spite Windows Explorer does not have access problem
| to that drive in general.!
|
| When trying to select a drive in the Explorer's folder pane,
| then Properties->Tools->Error Checking, I get immediately,
| seemingly w/o even progressing a bit the response:
| "Windows was unable to complete the disk check".
|
| Given that madness that went into drive D:, I don't know even
| where/how to start analyzing the problem.
|
| Does anybody know a decent and reliable tool that can tell
| what is the problem, that instead of responding with such
| infamous idiotic messages such "Access denied", it will tell
| WHY is the access denied, or the "...inpage operation"
| mentioned above, etc., that tells me nothing and possibly
| even help to fix the problem, or at least help salvage folders
| which are still reliably accessible?
|
| Many thanks in advance,
| David
|
|
Click to expand...
 
Back
Top