Chkdsk errors in SP2 installation

[Sam]

I've had a problem which is driving me nuts. It all started about 2
weeks ago when I'd occasionally get an error in the Event Viewer that
would say: Event ID 55, "The file system structure on the disk is
corrupt and unusable. Please run the chkdsk utility on the volume C:."
So last week I repartitioned/formatted and reinstalled Windows XP-pro.
This is on a year-old Maxtor 120mb HD that's partitioned into two
sections. Windows is on the first partition (that's the one I
reformatted). I haven't touched the second partition.

Well this week I start getting that same message again... not all the
time, but just once in awhile. So I run chkdsk from the command prompt
and it says there's errors. chkntfs says the disk is not dirty. Using
the Error Checker in the disk Properties/Tools says the disk is OK.
I've run chkdsk /f and chkdsk /r multiple times and still come up with
some ugly type errors. Below are some examples run from the Windows
command prompt, from 3 different times:

CHKDSK is verifying indexes (stage 2 of 3)...
Deleting index entry 15-cz9q.epm in index $I30 of file 102629.
Deleting index entry 15-dy9p.epm in index $I30 of file 102629.
Deleting index entry 15-ex9o.epm in index $I30 of file 102629.
Deleting index entry 15-fw9n.epm in index $I30 of file 102629.
Index verification completed.

(I've had this identical result twice after running chkdsk /f)

CHKDSK is verifying security descriptors (stage 3 of 3)...
Security descriptor verification completed.
Correcting errors in the Volume Bitmap.
Windows found problems with the file system.

CHKDSK is recovering lost files.
Recovering orphaned file 15-pfE2h.tmp (100278) into directory file 102629.
CHKDSK is verifying security descriptors (stage 3 of 3)...
Security descriptor verification completed.
Correcting errors in the master file table's (MFT) BITMAP attribute.
CHKDSK discovered free space marked as allocated in the volume bitmap.
Windows found problems with the file system.

So I've run the Powermax utility from Maxtor and it said the disk is
certified error free. That means that the disk should be physically OK
at least. So, what's causing the NTFS errors? There seems to be
something with "file 102629" that seems to pop up over and over again.

Thanks.

Sam

 

[Guest]

Are you running chkdsk this way? To run CHKDSK /F you must use the Run box,
answer yes when asked "run at next boot?" and then reboot and let it run and
fix the file errors. You cannot fix errors from a command prompt. If you are
doing it this way and still not having success, you should boot to the XP CD
and use the Recovery Console to fix the problems. Use Chksdk /R to run the
fix, since /F doesn't work in the Recovery Console. You can also correct the
MBR and much more.
http://support.microsoft.com/default.aspx?scid=kb;en-us;314058&Product=winxp
I suspect the 2 partitions might be causing your problems. You should run a
checkdisk repair on both partitions.

 

[Rock]

I've had a problem which is driving me nuts. It all started about 2
weeks ago when I'd occasionally get an error in the Event Viewer that
would say: Event ID 55, "The file system structure on the disk is
corrupt and unusable. Please run the chkdsk utility on the volume C:."
So last week I repartitioned/formatted and reinstalled Windows XP-pro.
This is on a year-old Maxtor 120mb HD that's partitioned into two
sections. Windows is on the first partition (that's the one I
reformatted). I haven't touched the second partition.

Well this week I start getting that same message again... not all the
time, but just once in awhile. So I run chkdsk from the command prompt
and it says there's errors. chkntfs says the disk is not dirty. Using
the Error Checker in the disk Properties/Tools says the disk is OK.
I've run chkdsk /f and chkdsk /r multiple times and still come up with
some ugly type errors. Below are some examples run from the Windows
command prompt, from 3 different times:


(I've had this identical result twice after running chkdsk /f)




So I've run the Powermax utility from Maxtor and it said the disk is
certified error free. That means that the disk should be physically OK
at least. So, what's causing the NTFS errors? There seems to be
something with "file 102629" that seems to pop up over and over again.

Thanks.

Sam

Sam, to be sure the drive is not failing, download a drive diagnostic
utility from Maxtor's web site. This should create a boot floppy disk
to run the diagnostics.

 

[Sam]

Are you running chkdsk this way? To run CHKDSK /F you must use the Run box,
answer yes when asked "run at next boot?" and then reboot and let it run and
fix the file errors. You cannot fix errors from a command prompt. If you are
doing it this way and still not having success, you should boot to the XP CD
and use the Recovery Console to fix the problems. Use Chksdk /R to run the
fix, since /F doesn't work in the Recovery Console. You can also correct the
MBR and much more.
http://support.microsoft.com/default.aspx?scid=kb;en-us;314058&Product=winxp
I suspect the 2 partitions might be causing your problems. You should run a
checkdisk repair on both partitions.

I use the command window (CMD) to run chkdsk. I could be wrong, but I
don't think it makes any difference when you do it from the Run
window. When I see errors, then I use the chkdsk /f command, say Yes
and it runs during the next boot.

Since I wrote the above, I've gone to the Recovery Console and used
the fixmbr command. I also ran chkdsk there as well... it prompted to
use the /p option to fix problems so I did that. The last chkdsk in
Windows said:

CHKDSK is verifying security descriptors (stage 3 of 3)...
Security descriptor verification completed.
Correcting errors in the Volume Bitmap.
Windows found problems with the file system.

As I said, I don't think it's bad sectors, since the same problem
wouldn't have occurred before and after a re-partition and reformat of
the C: partition. I've also run chkdsk /f on the other partition as
well. Also having done some extensive testing of the harddrive itself
(using both PowerMax and Spinrite 6.0) show no disk errors at all.

Sam

 

[Sam]

Sam, to be sure the drive is not failing, download a drive diagnostic
utility from Maxtor's web site. This should create a boot floppy disk
to run the diagnostics.

That's what the Powermax utility is. I downloaded the latest version
from Maxtor and ran it last night. Earlier this week I used Spinrite
6.0 and so far I'm error free as far as the physical disk is
concerned.

Sam

 

[Steve Nielsen]

I've had a problem which is driving me nuts. It all started about 2
weeks ago when I'd occasionally get an error in the Event Viewer that
would say: Event ID 55, "The file system structure on the disk is
corrupt and unusable. Please run the chkdsk utility on the volume C:."
So last week I repartitioned/formatted and reinstalled Windows XP-pro.
This is on a year-old Maxtor 120mb HD that's partitioned into two
sections. Windows is on the first partition (that's the one I
reformatted). I haven't touched the second partition.

Well this week I start getting that same message again... not all the
time, but just once in awhile. So I run chkdsk from the command prompt
and it says there's errors. chkntfs says the disk is not dirty. Using
the Error Checker in the disk Properties/Tools says the disk is OK.
I've run chkdsk /f and chkdsk /r multiple times and still come up with
some ugly type errors. Below are some examples run from the Windows
command prompt, from 3 different times:


(I've had this identical result twice after running chkdsk /f)




So I've run the Powermax utility from Maxtor and it said the disk is
certified error free. That means that the disk should be physically OK
at least. So, what's causing the NTFS errors? There seems to be
something with "file 102629" that seems to pop up over and over again.

Thanks.

Sam

I suggest testing RAM using Memtest86 and also test all the system
hardware using manufacturer's diagnostics if you can. Something is
corrupting the file system.

Steve

 

[Sam]

Sometime on, or about Fri, 01 Oct 2004 15:16:44 -0700, Steve Nielsen
wrote:

I suggest testing RAM using Memtest86 and also test all the system
hardware using manufacturer's diagnostics if you can. Something is
corrupting the file system.

Steve

One thing I've noticed is that the 3.3v line of my power supply isn't
steady... it varies from 3.10 to 3.38v. Since the tolerances for this
line are supposed to be less than 4%, I'm wondering if this could be a
contributing factor. I've tested this using 3 different utilities and
get the same results.

Sam

 

[Rock]

That's what the Powermax utility is. I downloaded the latest version
from Maxtor and ran it last night. Earlier this week I used Spinrite
6.0 and so far I'm error free as far as the physical disk is
concerned.

Sam

Ok, I missed the powermax part of your post.

 

[Sam]

Ok, I missed the powermax part of your post.

No problem... I appreciate the response anyhow.

Sam