Ms-Dos chkdsk

  • Thread starter Thread starter JamesJ
  • Start date Start date
J

JamesJ

Is there a chkdsk.exe that can be run from dos on a ntfs?
I need to run another chkdsk other than the one that is
on the WindowsXP setup cd.

Thanks,
James
 
JamesJ said:
Is there a chkdsk.exe that can be run from dos on a ntfs?
I need to run another chkdsk other than the one that is
on the WindowsXP setup cd.
Click to expand...


No
you cannot run dos chkdsk on an NTFS drive


if you have a major problem
you can boot from your XP cd and run chkdsk /r from the repair console
 
I've done that 20 times and the error returns. New hard drive and a new ATA
cable didn't work.
 
What error exactly? Any error messages? We can't help if
we don't know the error messages.
 
This is an excellent utility to test a hard drive for hardware issues.
however it does not understand ntfs and may erase the data.
www.grc.com

--PA
 
JamesJ said:
I've done that 20 times and the error returns. New hard drive and a new ATA
cable didn't work.
Click to expand...
Go to the hard drive manufacturer's web site and download their
diagnostic test utility. Run that to check out the drive for possible
hardware defects.

Also it is possible that some of your background software is
interfering with the operation of CHKDSK. Try booting your computer
into Safe Mode or boot to the Windows XP Recovery Console and then run
CHKDSK with the /R parameter.


Good luck

Ron Martell Duncan B.C. Canada
--
Microsoft MVP (1997 - 2006)
On-Line Help Computer Service
http://onlinehelp.bc.ca
Syberfix Remote Computer Repair

"Anyone who thinks that they are too small to make a difference
has never been in bed with a mosquito."
 
Been there, done that.
Seagate's diagnostic software locks up at times forcing
a ctrl-alt-del. When it does finish it really gives no useful
info other than test passed with inconsistencies.
CHKDSK /R fixes the errors.
But when I restart and run xp and then run CHKDSK /P it
finds one or more errors in the volume, again.
Once the errors is fixed from the Recovery Console using
CHKDSK /R I can boot to xp's setup cd, run the Recovery Console,
and check the disk for errors and there will be none. It's
only when I boot to the operating system (xp) that the errors
return.
This originally occurred on 40gb hd. Replaced the hd, same errors on
the new one. Changed the ATA cable, no help. Did a fresh install
of xp, no help.
The only thing now is the controller which is on my mother board.

Thanks,
James
 
I've posted before but no fix yet.
When I run chkdsk /p from the Recover Console on the xp
setup cod chkdsk reports one or more errors in the volume.
I run chkdsk /r and the errors are fixed until I restart and run
xp then restart to the cd and run chkdsk /p it finds the errors again.
If I, for instance, fix the errors using chkdsk /r I can boot again and
again
to the setup cd and run chkdsk /p it finds no errors. It's not until
I boot to the operating system that the errors are created, apparently.
I've done the following.

Run Seagate's diagnostic software.(which locks up at times)
It tells me the test passed with inconsistancies.(whatever the heck that
means.)

I've installed a new hard drive. Only thing the tech copied all
from my old 40gb to the new 160gb. So the problem might have
moved over to the new hd.

I've changed the ATA cable.

I did a fresh(raw) install of xp. on the 40gb prior to deciding to purchase
a new
hard drive. Did a fresh(raw) install of xp on the 160gb. No help.

Currently I have only the 160gb drive in my computer.
The only thing now is the controller which is on the motherboard.

XP and all my software seems to be running fine.

James
 
JamesJ said:
I've posted before but no fix yet.
When I run chkdsk /p from the Recover Console on the xp
setup cod chkdsk reports one or more errors in the volume.
I run chkdsk /r and the errors are fixed until I restart and run
xp then restart to the cd and run chkdsk /p it finds the errors again.
If I, for instance, fix the errors using chkdsk /r I can boot again and
again
Click to expand...


Run a RAM test and a HD diagnostic as something is definately not right.

BTW: I have seen that problem before and found that clocking the RAM down a
bit
"solved" the problem
 
Someone else suggested clocking down the ram but didn't
elaberate on the procedure.
Can you help here?

James
 
I've never used /r or /p. From WinXP you can go to Start > Run and run CMD
which will give you a DOS window, then type chkdsk /f and it will reboot and
run a repair on startup. That fixes physical errors on a hard disk. Those
errors do not transfer over if you move to a new hard disk. Software errors
can be caused by the physical errors if the software was written to the
physical location on the disk where the errors were.
 
Eric said:
I've never used /r or /p. From WinXP you can go to Start > Run and run CMD
which will give you a DOS window, then type chkdsk /f and it will reboot and
run a repair on startup. That fixes physical errors on a hard disk. Those
errors do not transfer over if you move to a new hard disk. Software errors
can be caused by the physical errors if the software was written to the
physical location on the disk where the errors were.
Click to expand...

That is not quite correct.
/F fixes errors in the data structure of the disk.
/R locates bad sectors and recovers data if possible, also fixes
errors in data structure.
/P is diagnostic only. It tests the drive but does not fix or recover
anything.

Ron Martell Duncan B.C. Canada
--
Microsoft MVP (1997 - 2006)
On-Line Help Computer Service
http://onlinehelp.bc.ca
Syberfix Remote Computer Repair

"Anyone who thinks that they are too small to make a difference
has never been in bed with a mosquito."
 
you did not mention if this is a SATA or IDE drive if its a new SATA2 you
might have to add a jumper.
 
Back
Top