Chkdsk hangs

[Michel S.]

Hello !

Chkdsk hangs while executed at boot time in step 5 of 5 (checking the
free space).

I restated the computer and performed another chkdsk (with /f /r), and
it still hangs at the same cluster number..

Any ideas ? Suggestions ?

Thanks

 

[Malke]

Hello !

Chkdsk hangs while executed at boot time in step 5 of 5 (checking the
free space).

I restated the computer and performed another chkdsk (with /f /r), and
it still hangs at the same cluster number..

Any ideas ? Suggestions ?

Back up your data. Run a hard drive diagnostic with a utility downloaded
from the drive mftr.'s website (or you can use Seagate's SeaTools-DOS). You
will create a bootable CD with the file you download. You will need
third-party burning software to do this such as Roxio, Nero, or the free
CDBurnerXP Pro (I believe it runs on Vista)..

http://www.cdburnerxp.se/

Boot with the CD you made and do a thorough test of the drive. If it fails
any physical tests, replace it.

Malke

 

[Michel S.]

Malke a formulé ce mardi :

Back up your data. Run a hard drive diagnostic with a utility downloaded
from the drive mftr.'s website (or you can use Seagate's SeaTools-DOS). You
will create a bootable CD with the file you download. You will need
third-party burning software to do this such as Roxio, Nero, or the free
CDBurnerXP Pro (I believe it runs on Vista)..

http://www.cdburnerxp.se/

Boot with the CD you made and do a thorough test of the drive. If it fails
any physical tests, replace it.

Malke

Thanks for your reply.

I downloaded and ran the "Drive Fitness Test" utility from Hitachi (the
drive is an HTS542525K9SA00), and both the Quick Test and the Advanced
Test returned with "no error found".

Any other suggestion ?

 

[Malke]

Michel S. wrote:

Thanks for your reply.

I downloaded and ran the "Drive Fitness Test" utility from Hitachi (the
drive is an HTS542525K9SA00), and both the Quick Test and the Advanced
Test returned with "no error found".

Any other suggestion ?

What caused you to run Chkdsk in the first place? Were you having problems?
If the hard drive test shows that the drive is physically sound, then
apparently you have some file system corruption. This doesn't usually
happen all by itself. What is the recent history of the machine?

Malke

 

[Alias]

Malke

MS-MVP
Elephant Boy Computers
www.elephantboycomputers.com
Don't Panic!

Spammer!

Frank

 

[Frank]

MS-MVP
Elephant Boy Computers
www.elephantboycomputers.com
Don't Panic!

Spammer!

Frank

Now your name is Frank...LOL!
You've really got some problems don't you?
How pathetic a person you really are.
Frank

 

[Michel S.]

Malke a exprimé avec précision :

Michel S. wrote:



What caused you to run Chkdsk in the first place? Were you having problems?
If the hard drive test shows that the drive is physically sound, then
apparently you have some file system corruption. This doesn't usually
happen all by itself. What is the recent history of the machine?

Malke

First time I hear we need a justification to run routine maintenance
programs on our PCs !!

The recent history is simple : system was freshly reinstalled from a
recovery disk set (it's an HP Notebook) + all updates dowloaded and
installed.

I just wanted to perform a chkdsk + defrag.. Never got thru the
chkdsk, as you may guess.

BTW, chkdsk (without /F) reported that errors were found on the disk
and that I needed to do a chkdsk /F to have them fixed.

Before the system hang, no errors were reported.

 

[Malke]

First time I hear we need a justification to run routine maintenance
programs on our PCs !!

Chkdsk is not part of routine maintenance. It is normally not ever run
unless there is a problem with the file system. One always takes a chance
of data corruption when running Chkdsk, which is why it isn't done unless
it is really needed.

The recent history is simple : system was freshly reinstalled from a
recovery disk set (it's an HP Notebook) + all updates dowloaded and
installed.

I just wanted to perform a chkdsk + defrag.. Never got thru the
chkdsk, as you may guess.

BTW, chkdsk (without /F) reported that errors were found on the disk
and that I needed to do a chkdsk /F to have them fixed.

Before the system hang, no errors were reported.

Vista defrags on the fly, so you don't need to do it yourself. It is rarely
necessary to defrag on an XP or Vista system anyway unless you do a lot of
video-editing or the like. In XP, once every 6 months on a well-tuned
system is plenty.

If your system is running well, I would simply leave it alone.

Malke

 

[NoStop]

Chkdsk is not part of routine maintenance. It is normally not ever run
unless there is a problem with the file system. One always takes a chance
of data corruption when running Chkdsk, which is why it isn't done unless
it is really needed.


Vista defrags on the fly, so you don't need to do it yourself. It is
rarely necessary to defrag on an XP or Vista system anyway unless you do a
lot of video-editing or the like. In XP, once every 6 months on a
well-tuned system is plenty.

Does Vista do background defrags on a scheduled basis or does it only defrag
when it decides that it is required?

If your system is running well, I would simply leave it alone.

Malke

Cheers.

--
Vista will make you speechless!
http://tinyurl.com/38zv7x

Proprietary Software: a 20th Century software business model.

Q: What OS is built for lusers?
A: Which one requires running lusermgr.msc to create them?

Frank, hard at work on his Vista computer all day:
http://redwing.hutman.net/~mreed/warriorshtm/compost.htm

 

[Michel S.]

Malke a présenté l'énoncé suivant :

Chkdsk is not part of routine maintenance. It is normally not ever run
unless there is a problem with the file system. One always takes a chance
of data corruption when running Chkdsk, which is why it isn't done unless
it is really needed.

1) Any documented reference to this ?

2) IMHO, it is normal to check the health of a new drive just to make
sure it is in good condition to begin with and to check from time to
time if it's developing bad sectors, has cross linked files or other
problems and then take appropriate action before it's too late.

3) As I said previously, chkdsk without /F (or check drive for errors
without any box checked from drive properties -> tools) reported that
Windows found errors on file system and recommended to execute chkdsk
with /F. That's what lead me to perform a chkdsk at boot time.

4) We are getting away from the main topic whic is : why does chkdsk
at boot time hangs or freezes while the disk manufacturer's extended
diagnostic doesn't find any problem with the drive ?

Vista defrags on the fly,

Then explain me why, by default, defrag is scheduled to run once a week
in Vista ?

It is rarely
necessary to defrag on an XP or Vista system anyway unless you do a lot of
video-editing or the like. In XP, once every 6 months on a well-tuned
system is plenty.

After a full O/S & Softwares install + updates + patches is completed,
where a lot of files have been extracted and moved around, it appears
to me the right moment to perform a defrag of these files which,
theorically, will not change in the near future.