NTFS vs Scandisk & Minor Inconsistencies

  • Thread starter Thread starter Usman
  • Start date Start date
U

Usman

A few weeks earlier, I installed a new seagate hard
drive on my pc and I transferred my my OS files on the
new hard disk/partition using Seagate Diskwizard 2003.
Everything was successfully done and the new drive
successully booted into the OS. Another change that I did
was that I changed my file system to NTFS. Now I am
experiencing a changed behaviour on my system.
(1) Previously, whenever my computer had shut down
improperly (because of a power failure), scandisk used to
automatically scan for any changes. Since the above
upgradation/changed file system/new hard drive, I have
never seen scandisk appearing automatically. My question
is; Is it normal behaviour? or something is wrong with my
pc. Is it normal for my pc not to start automatic
scandisk after an improper shut down under NTFS.
(2) After this new situation, whenever, my pc shuts
down improperly, I manually prefer a complete scan using
the properties of my OS partition (C drive in my case)
and accepting a scan at the next startup (as it prompts
me so). The problem here is that after every scan, a
report named 'bootex' is generated and almost everytime I
find some minor inconsistencies on my drive. They,
however, do not appear again after a consecutive 2 or
three complete scans. As a guide, I am posting the report
(bootex)generated by windows in double quotes:

""Checking file system on C:
The type of the file system is NTFS.
Volume label is USMAN.

A disk check has been scheduled.
Windows will now check the disk.
Cleaning up minor inconsistencies on the drive.
Cleaning up 4 unused index entries from index $SII of
file 0x9.
Cleaning up 4 unused index entries from index $SDH of
file 0x9.
Cleaning up 4 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.

7976240 KB total disk space.
5079600 KB in 30984 files.
9416 KB in 3646 indexes.
0 KB in bad sectors.
84480 KB in use by the system.
41936 KB occupied by the log file.
2802744 KB available on disk.

4096 bytes in each allocation unit.
1994060 total allocation units on disk.
700686 allocation units available on disk.

Internal Info:
67 a3 00 00 51 87 00 00 cf a8 00 00 00 00 00 00
g...Q...........
f5 01 00 00 00 00 00 00 72 00 00 00 00 00 00
00 ........r.......
ce 35 1d 02 00 00 00 00 f2 f4 46 0e 00 00 00
00 .5........F.....
c0 0e 16 02 00 00 00 00 6e 69 97 3a 01 00 00
00 ........ni.:....
0e 2f b6 2f 00 00 00 00 be 71 98 81 01 00 00
00 ././.....q......
99 9e 36 00 00 00 00 00 08 79 00 00 00 00 00
00 ..6......y......
00 c0 08 36 01 00 00 00 3e 0e 00 00 00 00 00
00 ...6....>.......

Windows has finished checking your disk.
Please wait while your computer restarts.""


My question here is that Is it a cause of concern for me
to have unused index entries (sometimes there are 2 or 4
or 6 or 8 unused index entries). And as I said earlier,
it takes me 2 or 3 scans to have a report devoid of any
inconsistencies. Could someone from MSFT guide me as to
what is wrong with my pc. I am using Windows XP
Professional Edition. And in case it is relevant, I have
two hard drives of 6 and 5 partitions respectively. Plus,
I am running a P4 1.6 GHz processor over Intel D850MV
motherboard with all the latest bios drivers.

Thanking in anticipation over a useful guideline......
 
it's normal,scandisk won't run auto. If there's problem
with file integrity ,i believe xp/ntfs will run chkdsk.
 
not fr ms - tho this will get you started - ie
1/
ms warns you of possible inconsistencies in
'converting to ntfs' - ie
Convert
....
Remarks
....
The location of the MFT is different on volumes that have
been converted from previous version of NTFS, so volume
performance might not be as good on volumes converted
from Windows NT.
Volumes converted from FAT to NTFS lack some performance
benefits compared to volumes initially formatted with
NTFS. On converted volumes, the MFT might become
fragmented. In addition, on converted boot volumes, NTFS
permissions are not applied after the volume is
converted.
2/
scandisk - no longer supported/avail in win xp
chkdsk.exe/checkdisk/ - now used in win xp - as it was
orig used in win ver 2-6+
note
avail in 'gui or command prompt/command line'
3/
win xp - does not normally start 'checkdisk' at
'start up' - tho it does on 'certain prob conditions'
or give you the option to run/esp when you have
'ntfs - req disk to be locked/ie before win xp runs'
4/
chk w/seagate on 'operating conditions' of their
'diskwizard 2003 under win xp os' for details/info
5/
'checkdisk' - can be run repeatedly til it has
cleaned up 'disk errors/flaws'
6/
if you haven't already done so - you might consider
'splitting up your pagefile' - and/or having a
'pagefile for ea hd'
ie
How to Configure Paging Files for Optimization and
Recovery in Windows XP
http://support.microsoft.com/search/preview.aspx?
scid=kb;en-us;Q314482
and
take it fr there

hth
God Bless
hutch

-----Original Message-----
A few weeks earlier, I installed a new seagate hard
drive on my pc and I transferred my my OS files on the
new hard disk/partition using Seagate Diskwizard 2003.
Everything was successfully done and the new drive
successully booted into the OS. Another change that I did
was that I changed my file system to NTFS. Now I am
experiencing a changed behaviour on my system.
(1) Previously, whenever my computer had shut down
improperly (because of a power failure), scandisk used to
automatically scan for any changes. Since the above
upgradation/changed file system/new hard drive, I have
never seen scandisk appearing automatically. My question
is; Is it normal behaviour? or something is wrong with my
pc. Is it normal for my pc not to start automatic
scandisk after an improper shut down under NTFS.
(2) After this new situation, whenever, my pc shuts
down improperly, I manually prefer a complete scan using
the properties of my OS partition (C drive in my case)
and accepting a scan at the next startup (as it prompts
me so). The problem here is that after every scan, a
report named 'bootex' is generated and almost everytime I
find some minor inconsistencies on my drive. They,
however, do not appear again after a consecutive 2 or
three complete scans. As a guide, I am posting the report
(bootex)generated by windows in double quotes:

""Checking file system on C:
The type of the file system is NTFS.
Volume label is USMAN.

A disk check has been scheduled.
Windows will now check the disk.
Cleaning up minor inconsistencies on the drive.
Cleaning up 4 unused index entries from index $SII of
file 0x9.
Cleaning up 4 unused index entries from index $SDH of
file 0x9.
Cleaning up 4 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.
Click to expand...
..............note - clipped here........................
 
Greetings --

With WinXP, Chkdsk (Scandisk was a Win9x application) will/should
launch automatically on startup if the OS boot loader detects a
potential problem with the files. When using the FAT32 file system,
an unexpected shutdown is very likely to cause just the sorts of
problems that would trigger such automatic scans. Now that you're
using the NTFS file system, you're much less likely to experience the
same sort of damage and/or file corruption after an unexpected
shutdown, so Chkdsk is much less likely to need to run.

A better explanation of the way NTFS works is here:

FAT & NTFS File Systems in Windows XP
http://www.aumha.org/a/ntfs.htm


Bruce Chambers

--
Help us help you:



You can have peace. Or you can have freedom. Don't ever count on
having both at once. -- RAH
 
Greetings --

I'm afraid I can't answer that question for you. Perhaps someone
else will know.

Bruce Chambers

--
Help us help you:



You can have peace. Or you can have freedom. Don't ever count on
having both at once. -- RAH
 
Back
Top