|
|||||||
![]() |
|
|
LinkBack | Thread Tools | Search this Thread | Rate Thread | Display Modes |
|
|
#1 |
|
Member (8 bit)
Join Date: Mar 2000
Posts: 157
|
chkdsk problem
Howdy I'm haveing a problem and hope I can explain it correctly..I cant get Powerquest drive image 7.0 to work apparently it's haveing trouble getting info from the disk so I decided to do a chkdsk.I started a .CMD and told it to do a CHKDSK at next reboot.I rebooted and get this error message..
"Checking file system on C.Type of file system is NTFS.Cannot open volume for direct access to check disk.Windows is done checking" Does anyone have any idea what the problem is. This is on Windows XP PRO SP2 with a SATA raid.. |
|
|
|
|
|
#2 |
|
Member (4 bit)
Join Date: Feb 2006
Posts: 9
|
Have you tried specifying switch options such as "/x" & "/f" ???
Give it a try & see if that does anything. I usually like to specify everything at the prompt (for example): " C:>chkdsk c: /x /f " (w/out the quotation marks, of course). By the sounds of your post, your volume must dismount first in order for chkdsk to access it. But a reboot should startup chkdsk w/out a hitch. Another option to explore, execute above command from safe mode & restart. Just a thought ... |
|
|
|
|
|
#3 | |
|
Member (8 bit)
Join Date: Mar 2000
Posts: 157
|
Quote:
|
|
|
|
|
|
|
#4 |
|
Member (4 bit)
Join Date: Feb 2006
Posts: 9
|
/x - Forces the volume to dismount if necessary.
/f - Fixes errors on the disk. I always find it better to be clear (when executing programs/commands) to specify the volume I'm working with and any switches (such as above). |
|
|
|
|
|
#5 |
|
Member (12 bit)
Join Date: Nov 2001
Location: Woodland Hills, CA (suburb of Los Angeles)
Posts: 4,014
|
. . . if you suspect the problem lies mainly with PowerQuest's handling of the RAID setup (seems likely enough) - try seeing if a program update is available for your version. I saw a thread online a few days ago, which mentions Drive Image didn't work well with RAID arrays until version 7.0.1 or later.
Some mentions of trouble with the unmountable volume error pointed to corruption that sometimes can be fixed by chkdsk with the /f switch that cyclonus has pointed you to. Give that a try as well. . . . Gary |
|
|
|
|
|
#6 | |
|
Member (8 bit)
Join Date: Mar 2000
Posts: 157
|
Quote:
|
|
|
|
|
![]() |
| Bookmarks |
| Thread Tools | Search this Thread |
| Display Modes | Rate This Thread |
|
|