Checking file system on C:

Page 2 - Seeking answers? Join the AnandTech community: where nearly half-a-million members share solutions and discuss the latest tech.
Toggle sidebar Toggle sidebar
DasFox

DasFox

Diamond Member
Sep 4, 2003
4,668
46
91
Ok check it out chkdsk with the Maxtor installed:

Checking file system on C:
The type of the file system is NTFS.

A disk check has been scheduled.
Windows will now check the disk.
Cleaning up minor inconsistencies on the drive.
Cleaning up 20 unused index entries from index $SII of file 0x9.
Cleaning up 20 unused index entries from index $SDH of file 0x9.
Cleaning up 20 unused security descriptors.
CHKDSK is verifying file data (stage 4 of 5)...
File data verification completed.
CHKDSK is verifying free space (stage 5 of 5)...
Free space verification is complete.

16386268 KB total disk space.
3704420 KB in 12265 files.
3184 KB in 783 indexes.
0 KB in bad sectors.
79744 KB in use by the system.
65536 KB occupied by the log file.
12598920 KB available on disk.

4096 bytes in each allocation unit.
4096567 total allocation units on disk.
3149730 allocation units available on disk.


Well sheesh it's not the Raptor then and I switched the memory and the samething happened, so 2 hards and 2 different sticks of memory all the same. And with this Maxtor installed it's not using the nForce IDE drivers, because as I said previous I can't boot with them.

Hmmm what's the deal?
 
flexy

flexy

Diamond Member
Sep 28, 2001
8,464
155
106
tru different nforce drivers...nf4 IDE drivers are HORRIBLE...the first time i had NO problem is with the last ones(vers 6.66 <-- no joke :) and/or the ones who JUST came out (february, 3rd).

ALSO...have problems with a SATA drive and "enabled command queuing" in devicemanager/nf4 sata adapter.

You might want to check somewhere in the sata device options.

ALso..i would (if not already) get the latest nf4 drivers who have just been released...or just use MS drivers.

And yeah....check into bios too.
 
DasFox

DasFox

Diamond Member
Sep 4, 2003
4,668
46
91
flexy, check somewhere in the sata device options? And yeah....check into bios too?, for what, sorry you lost me?

Lord Evermore, GUESS what?

Here is my other box I tested this on also:

Checking file system on C:
The type of the file system is NTFS.

A disk check has been scheduled.
Windows will now check the disk.
Cleaning up minor inconsistencies on the drive.
Cleaning up 17 unused index entries from index $SII of file 0x9.
Cleaning up 17 unused index entries from index $SDH of file 0x9.
Cleaning up 17 unused security descriptors.
CHKDSK is verifying file data (stage 4 of 5)...
File data verification completed.
CHKDSK is verifying free space (stage 5 of 5)...
Free space verification is complete.

35840983 KB total disk space.
3761584 KB in 9785 files.
2392 KB in 633 indexes.
0 KB in bad sectors.
77519 KB in use by the system.
65536 KB occupied by the log file.
31999488 KB available on disk.

4096 bytes in each allocation unit.
8960245 total allocation units on disk.
7999872 allocation units available on disk.


LMAO oh man there was nothing wrong with this Raptor on my SLI box, AH HA HA HA

Oh well dude live and learn, I must admit it was a WHIRL trying to figure this out and all along it's just this way.

Strange I never really noticed this all these years running Windows, but then I never really messed with chkdsk, so I never really payed attention to it

WoOT ;)


 
L

Lord Evermore

Diamond Member
Oct 10, 1999
9,558
0
76
Well like I said, I have never ever seen these messages when running chkdsk, on dozens of machines. I can't imagine what you're doing that is causing it on multiple systems. I assume you're not running any special applications, or using any security settings or encryption or anything out of the ordinary.

It certainly doesn't seem like Microsoft has much of a handle on the cause of it. If it's a non-issue, why does chkdsk tell you there are problems, then say it fixed them, when it didn't fix them? I assume that the fix they put in Win2k SP1 also prevented the issue in XP by the time XP SP2 came out. I can understand cached and unused security descriptors, but why does chkdsk look for that, assume it's a problem, but not fix it?

I don't like being told "oh just ignore that horrible error, it doesn't mean anything".
 
DasFox

DasFox

Diamond Member
Sep 4, 2003
4,668
46
91
Well all I'm doing is right clicking on the drive, going to 'Properties' 'Tools' 'Check Now' and then I'm checking both options to fix and scan for bad sectors that's all I'm doing and yes on two different seperate machines it does the same report showing this clean up, fix or whatever, but one thing I know for sure, on one box it has been running now for 9 months and I know for a fact it has no hardware problems.

So at least I see there is no problem, just looks like the way it is on some boxes, like either this is just normal or a bug, or a incompatibility, but anyways like I said I know my hardware is good. ;)

WoOT

THANKS Lord Evermore for all your help and input PLEASE let me know if you ever hear anything more on this just PM me.

Well here's to hoping this little fluke or whatever it is, DIES in Vista, LOL.
 
flexy

flexy

Diamond Member
Sep 28, 2001
8,464
155
106
right click "my computer" - properties - hardware - device manager - ide/atapi controllers - nvidia nforce4 paralell/serial ata controller

click on any of them --- > primary or secondary channel...there are options...look whether "command queuing" is chekcked (if yes, uncheck)..and for hte motherboard i would just look where you usually get the bios and check if there's a new one out.

also...do you have any entries in your "event viewer" (settings, control-panel, administrative tools, event viewer) which are IDE related ?

As said when i had NF4 drivers before the 6.66 i always had some weird entry regarding my page-file and only the 6.66 nforce drivers fixed that.

i do NOT think that under normal circumstances an error like yours should appear...thats just weird.

DO you have any tweak-tools installed or 3rd part tools/virus-killers etc....does this happen on a fresh install of XP ?
 
flexy

flexy

Diamond Member
Sep 28, 2001
8,464
155
106
btw...lol..why ALWAYS run a chkdsk on reboot ? I never run a chkdsk on reboot ? then just DONT RUN IT :)

 
DasFox

DasFox

Diamond Member
Sep 4, 2003
4,668
46
91
flexy, this happens on two seperate boxes I have, all completely different hardware, with the same message, over index $SII of file 0x9 and index $SDH of file 0x9 and the unused security descriptors.

On one box I am on at the moment a socket A, nForce2 for the IDE channel on it there are no options for "command queuing". I do not have tweak-tools installed or 3rd part tools/virus-killers etc.. installed and on my other box a nForce4 SLI, this happens on a fresh clean install of XP. Both boxes also have the latest bios installed.

My nForce2 box I have used for 9 months now, so I know there are no hardware issues.

I don't run chkdsk on reboot, I was just doing this to run tests on the hard drive I just purchased a Raptor 150, I wanted to make sure for my money it was ok and after running chkdsk I noticed this and then tried to figure out why it was showing this all the time, then I saw the samething was happening on both my boxes, so I really don't know.

Alot of people say this is normal and not a problem, also Microsoft talks about this as well as not a problem, even if the article is for 2000:

http://support.microsoft.com/kb/255008/EN-US/

THANKS
 
D

duragezic

Lifer
Oct 11, 1999
11,234
4
81
Interesting DasFox.

I have very similar issues.

I only skimmed the thread, but I appear to be in the same position as you.

Just today in fact, out of the many many days its been happening, I was messing with it.

I ran multiple drive tests on my WD 800JB 80JB and my Seagate 7200.8 250GB. I was using SeaTools online cause I knew the Seagate seemed fvck.

So, the basic and SMART tests check out, but the file system always and has always brought up errors "that need to be fixed". The help recommends using chkdsk /f to fix. So I ran chkdsk /f /v on all of my drivers. The Seagate 250gb split into 2 partitions showed "errors that needed to be fixed" on both. The WD 800JB showed "warnings" that weren't really problems. After running chkdsk on all 3,I tested them again, this time they all came up with "errors". Fvcking a I thought, nice fixes!!! So I ran the scan disk that is scheduled before XP is loaded. Even after doing it on all three, they still come with inconsistency errors.

The Seagate (but IIRC NOT the WD) always had errors that never got fixed with the file system, so I was gonna RMA many months ago when it randomly and mysteriously lost a partition. But the RMA form didn't work in any of my 3 browsers so I ignored it. I overhauled my computer last week with a new NF4 mobo, new Opteron, and new video card, yet STILL the problems persist. But i've heard some weird crap going on yesterday and today and if its my WD 80gb, well I guess I'll find out and lose whatevers on there. But the Seagate is easily under warranty, so I'm gonna RMA it still ASAP.

But still, I don't get WTF is going on here, why nothing can get fixed by utilities, plus it seems to be a rare occurence with just us two, yet the tests still bring up errors that act like they are easily fixed with scan disk. Me and Dasfox have completely different CPUS, memory, mobo, hard drives, etc.

edit: Wow two separate boxes! I basically have had it on two separates too, since it happened through several fresh installs of XP and with completely different hardware.

I too have the newest BIOS, tried multiple utilities like Partition Magics file system check, and now that I pay attention... SAME index addresses. WTF? I just ran chkdsk /f /v again, same crap about security descriptors and index entries at the same index.

On ALL disks and partitions.

Note both of these are completely different partitioning and formatting than with the NF2. I tried fresh installs long ago yet the file system still somehow had errors on a newly formatted drive/partition.



 
S

shl0791

Member
Aug 2, 2001
72
0
0
I used to have those HD problems in the past.
have you tried a bigger PSU?
I run 4 hd, and 2 dvd rom drives... and a x800 xl. Using a 350watt psu, I'd get checkdisk, before loading winxp all the time.
Windows would tell I'd have errors on c: and other drives.
Since I've switched over to a 500 watt Psu, I don't have those errors anymore.. maybe that's why Lifeguard can't detect any errors, but winxp does?
 
S

sandeep108

Senior member
May 24, 2005
220
0
0
I have always got similar HDD chkdsk errors on several boxes, Intel/AMD. I just ignore them now.
 
DasFox

DasFox

Diamond Member
Sep 4, 2003
4,668
46
91
Well I don't think there are any hard drive failures with this, I have had this happening on one particular hard drive now for 9 months and it purrs like a kitten.

Ok I'm not sure if I'm on the spot here or not, but in the 'Services' I have the 'IPSEC Services' disabled, in fact I have alot of services disabled that I don't use and seemed as though they might not be a issue as this one, so I just started to think about this, as could this be why?

THANKS

P.S. I'll enable the IPSEC Services again and run the chkdsk over and let you all know what happens.
 
X

xtknight

Elite Member
Oct 15, 2004
12,974
0
71
Originally posted by: DasFox
Ok I'm not sure if I'm on the spot here or not, but in the 'Services' I have the 'IPSEC Services' disabled, in fact I have alot of services disabled that I don't use and seemed as though they might not be a issue as this one, so I just started to think about this, as could this be why?
Click to expand...

Nope, IPSEC is just a network filtering layer. It isn't going to affect your hard disk.
 
DasFox

DasFox

Diamond Member
Sep 4, 2003
4,668
46
91
Originally posted by: shl0791
I used to have those HD problems in the past.
have you tried a bigger PSU?
I run 4 hd, and 2 dvd rom drives... and a x800 xl. Using a 350watt psu, I'd get checkdisk, before loading winxp all the time.
Windows would tell I'd have errors on c: and other drives.
Since I've switched over to a 500 watt Psu, I don't have those errors anymore.. maybe that's why Lifeguard can't detect any errors, but winxp does?
Click to expand...

I already have big PSUs, a Antec True Power 550w and a Antec Neo HE 550W, I don't think this is the problem.
 
DasFox

DasFox

Diamond Member
Sep 4, 2003
4,668
46
91
Sheesh I've been looking into this almost a week now and no one either here, or Google, or on IRC has a 100% answer to this, or solution. I hope someone can finally step forward and clarify this.

THANKS
 
You must log in or register to reply here.

TRENDING THREADS

COMPANY
RESOURCES
FOLLOW
Top Bottom