Windows appears to not be checking my booting volume which is on a IDE controller card. It says:
Checking file system on E:
The type of the system is NTFS.
Cannot open volume for direct access.
Windows has finished checking the disk.
Printable View
Windows appears to not be checking my booting volume which is on a IDE controller card. It says:
Checking file system on E:
The type of the system is NTFS.
Cannot open volume for direct access.
Windows has finished checking the disk.
That only relates to XP. I saw another one about CrypKey which I don't think I have. It said to open Devices from the control panel but there is nothing called devices. If it meant to say device manager which comes from system there is nothing there called networkx.
Thats for NT....You don't say whether you are on Nt or 2k
What service pack are you up to?
Its W2000 SP4. I can run check disk from within W2000 and I think all I don't get is the bad sector testing? I can use something else for that.
That would imply an issue on the ide card - checked for bios updates for the ide card?
Mmmm ok before we get into a big debate .. what about using the windows cd to get to console & running chkdsk there ?
This is down to how windows NT family (so including xp & w2k) insists on booting from enumerated info from bios, when other bits of windows documentation insist that it doesn't do that, well billy boy it does .. :rolleyes:
Well no you can't use 'something else' for that (not from inside windows anyway), not only will chkdsk do a surface scan (what I think you mean by 'bad sector testing') but it needs to look at system areas such as the MFT & bootstrap which otherwise are 'in use' (by windoze) & therefore can't get done..Quote:
..can run check disk from within W2000 and I think all I don't get is the bad sector testing..
In a command prompt type "chkdsk e: /f" then reboot.
Or in the recovery console "chkdsk /p"
I am already trying to run CHKDSK from the command prompt. I don't think I am able to get the recovery console.
So its important to know (here) that 'prompt' is just emmulated dos, so no advantage there as it still has everything you want to sort out 'in use' (just the same as running it from within windows) .. & here for your ed-ification is a KB - Description of the Windows 2000 Recovery Console - Microsoft Knowledge Base Article - 229716 - all you need is either the 3 floppy boot disks or a windows cd (suitable 'destructions' in the link ;))Quote:
Originally Posted by Fraser
If none of that is sorting it out 'sufficiently' then you are back with looking for bios updates as per Noo's suggestion, but I'd think if anything affecting it, it'll be the motherboards bios & not the controllers bios
We never seem to have actually asked - but why ? (why are we 'needing' chkdsk ?)
When I run CHKDSK via the command prompt window Windows asks if I want CHKDSK to run the next time the computer is booted. That is when the "Cannot open volume for direct access" message comes.
Quote:
Originally Posted by Fraser
If 2k has the same limits as NT4. I expect you cannot chkdsk any drive over 8GB as the primary boot drive or any partion of 8GB or more on any secondary partion. (Using basic NTFS)
If you use the Dynamic disk structures that 2k offers I suspect that you can work around the 8GB limit but I am fairly sure that you can create, format and install 2K on a disk structure that it simpily cannot do chkdsk on at boot time or with 2k full up.
The boot volume is less than 8GBs. I suspect than Microsoft did not test this on computers with IDE cards.
2k NTFS is not the same as NT NTFS and furthermore does not have the limitations that the NT version of NTFS has.
I have a Win XP PRO unit that is doing the same thing. Are you running Diskkeeper? I have Ghosted to new larger drive the problem followed. I have just finished removing original drive and ran chkdsk \f by putting drive in another unit. Chkdsk did run, have not put the disk back in original unit yet. I tried running chkdsk from a repair install using both /p and /r neither attempt resolved anything. I have reinstalled windows which temporally fixes problem until I reinstall diskkeeper. I have checked microsoft KB with "Cannot open volume for direct access", this is listed in KB but says this is unresolved by Microsoft. So far I have used a 20 and a 80 gig drive.Quote:
Originally Posted by Fraser