Ok. Simple question.

[Guest]

I have a rather embarrassingly simple dilemma. My hdd is starting to whine
under heavy use, and it is rather old, (6 years and only one new o/s install)
I ran ScanDisk and of course it took quite a while. I went about my business
and let ScanDisk do it's thing, checking frequently, I got interested in
Painkiller Jane and missed the final report. Where is the report and what is
the name of it? I am so embarrassed because I am an experienced user and cant
find a simple file. So please no lashes with wet spaghetti noodles.

 

[Rock]

I have a rather embarrassingly simple dilemma. My hdd is starting to whine
under heavy use, and it is rather old, (6 years and only one new o/s
install)
I ran ScanDisk and of course it took quite a while. I went about my
business
and let ScanDisk do it's thing, checking frequently, I got interested in
Painkiller Jane and missed the final report. Where is the report and what
is
the name of it? I am so embarrassed because I am an experienced user and
cant
find a simple file. So please no lashes with wet spaghetti noodles.

Look in Event Viewer, in the Application log for an event labeled Winlogon.
Start | Run | eventvwr.msc | Ok.

I suggest you also download a drive diagnostic utility from the hard drive
manufacturer's web site. That will create a bootable floppy or CD. Boot
from that and run the diagnostics.

Make sure you have a full and complete backup of important data. Maybe
think about cloning or imaging the drive now before it fails.

 

[Lil' Dave]

I have a rather embarrassingly simple dilemma. My hdd is starting to whine
under heavy use, and it is rather old, (6 years and only one new o/s
install)
I ran ScanDisk and of course it took quite a while. I went about my
business
and let ScanDisk do it's thing, checking frequently, I got interested in
Painkiller Jane and missed the final report. Where is the report and what
is
the name of it? I am so embarrassed because I am an experienced user and
cant
find a simple file. So please no lashes with wet spaghetti noodles.

There is no scandisk in XP. Other prior MS OSes with scandisk, check
scandisk.log file. Either way, the report on the screen doesn't go away
until dismissed by the user.
Dave

 

[Rock]

I have a rather embarrassingly simple dilemma. My hdd is starting to whine
under heavy use, and it is rather old, (6 years and only one new o/s
install)
I ran ScanDisk and of course it took quite a while. I went about my
business
and let ScanDisk do it's thing, checking frequently, I got interested in
Painkiller Jane and missed the final report. Where is the report and what
is
the name of it? I am so embarrassed because I am an experienced user and
cant
find a simple file. So please no lashes with wet spaghetti noodles.

Additional, it's chkdsk in XP, not scandisk.

 

[Guest]

Ok, thanks.
This is what the file read:
A disk check has been scheduled.
Windows will now check the disk.
Cleaning up minor inconsistencies on the drive.
Cleaning up 1051 unused index entries from index $SII of file 0x9.
Cleaning up 1051 unused index entries from index $SDH of file 0x9.
Cleaning up 1051 unused security descriptors.
CHKDSK is verifying file data (stage 4 of 5)...
Read failure with status 0xc000009c at offset 0x7d626d000 for 0x10000 bytes.
Read failure with status 0xc000009c at offset 0x7d626d000 for 0x1000 bytes.
Windows replaced bad clusters in file 48871
of name \Doom 3\Regan\SAVEGA~1\AUTOSA~3.SAV.
File data verification completed.
CHKDSK is verifying free space (stage 5 of 5)...
Free space verification is complete.
Adding 1 bad clusters to the Bad Clusters File.
CHKDSK discovered free space marked as allocated in the
master file table (MFT) bitmap.
Correcting errors in the Volume Bitmap.
Windows has made corrections to the file system.

150496919 KB total disk space.
50400464 KB in 125034 files.
49952 KB in 9059 indexes.
20 KB in bad sectors.
235283 KB in use by the system.
65536 KB occupied by the log file.
99811200 KB available on disk.

4096 bytes in each allocation unit.
37624229 total allocation units on disk.
24952800 allocation units available on disk.
And I also poked around in some of the error reports, and, well, there were
many... at least more than two! Just kidding. But there were dozens and
dozens reporting a bad block. My question here is: Are all of these reports
different instances of the same bad block or is it that many bad blocks that
have been reported? I haven't noticed any dramatic performance loss. It is
slow once in a while, but then again it's old! And Yes I intend to back up my
drive contents, and sooner or later a new drive is in order. (Hello, SCSI
controller card and drives!) My student advisor has (don't yell at me if I
get the name wrong, I've slept since then...) Symantec Ghost. It works very
well. We ghost a 20 gig hdd in less than 4 minutes. But my 160 might take
just a wee bit longer, though.
Anyways, thanks for the help, and your patience reading this long-winded post.

 

[Rock]

Ok, thanks.
This is what the file read:
A disk check has been scheduled.
Windows will now check the disk.
Cleaning up minor inconsistencies on the drive.
Cleaning up 1051 unused index entries from index $SII of file 0x9.
Cleaning up 1051 unused index entries from index $SDH of file 0x9.
Cleaning up 1051 unused security descriptors.
CHKDSK is verifying file data (stage 4 of 5)...
Read failure with status 0xc000009c at offset 0x7d626d000 for 0x10000
bytes.
Read failure with status 0xc000009c at offset 0x7d626d000 for 0x1000
bytes.
Windows replaced bad clusters in file 48871
of name \Doom 3\Regan\SAVEGA~1\AUTOSA~3.SAV.
File data verification completed.
CHKDSK is verifying free space (stage 5 of 5)...
Free space verification is complete.
Adding 1 bad clusters to the Bad Clusters File.
CHKDSK discovered free space marked as allocated in the
master file table (MFT) bitmap.
Correcting errors in the Volume Bitmap.
Windows has made corrections to the file system.

150496919 KB total disk space.
50400464 KB in 125034 files.
49952 KB in 9059 indexes.
20 KB in bad sectors.
235283 KB in use by the system.
65536 KB occupied by the log file.
99811200 KB available on disk.

4096 bytes in each allocation unit.
37624229 total allocation units on disk.
24952800 allocation units available on disk.
And I also poked around in some of the error reports, and, well, there
were
many... at least more than two! Just kidding. But there were dozens and
dozens reporting a bad block. My question here is: Are all of these
reports
different instances of the same bad block or is it that many bad blocks
that
have been reported? I haven't noticed any dramatic performance loss. It is
slow once in a while, but then again it's old! And Yes I intend to back up
my
drive contents, and sooner or later a new drive is in order. (Hello, SCSI
controller card and drives!) My student advisor has (don't yell at me if I
get the name wrong, I've slept since then...) Symantec Ghost. It works
very
well. We ghost a 20 gig hdd in less than 4 minutes. But my 160 might take
just a wee bit longer, though.
Anyways, thanks for the help, and your patience reading this long-winded
post.

You're welcome. If I were you I would replace the drive asap before things
get worse.

 

[Lil' Dave]

Ok, thanks.
This is what the file read:
A disk check has been scheduled.
Windows will now check the disk.
Cleaning up minor inconsistencies on the drive.
Cleaning up 1051 unused index entries from index $SII of file 0x9.
Cleaning up 1051 unused index entries from index $SDH of file 0x9.
Cleaning up 1051 unused security descriptors.
CHKDSK is verifying file data (stage 4 of 5)...
Read failure with status 0xc000009c at offset 0x7d626d000 for 0x10000
bytes.
Read failure with status 0xc000009c at offset 0x7d626d000 for 0x1000
bytes.
Windows replaced bad clusters in file 48871
of name \Doom 3\Regan\SAVEGA~1\AUTOSA~3.SAV.
File data verification completed.
CHKDSK is verifying free space (stage 5 of 5)...
Free space verification is complete.
Adding 1 bad clusters to the Bad Clusters File.
CHKDSK discovered free space marked as allocated in the
master file table (MFT) bitmap.
Correcting errors in the Volume Bitmap.
Windows has made corrections to the file system.

150496919 KB total disk space.
50400464 KB in 125034 files.
49952 KB in 9059 indexes.
20 KB in bad sectors.
235283 KB in use by the system.
65536 KB occupied by the log file.
99811200 KB available on disk.

4096 bytes in each allocation unit.
37624229 total allocation units on disk.
24952800 allocation units available on disk.
And I also poked around in some of the error reports, and, well, there
were
many... at least more than two! Just kidding. But there were dozens and
dozens reporting a bad block. My question here is: Are all of these
reports
different instances of the same bad block or is it that many bad blocks
that
have been reported? I haven't noticed any dramatic performance loss. It is
slow once in a while, but then again it's old! And Yes I intend to back up
my
drive contents, and sooner or later a new drive is in order. (Hello, SCSI
controller card and drives!) My student advisor has (don't yell at me if I
get the name wrong, I've slept since then...) Symantec Ghost. It works
very
well. We ghost a 20 gig hdd in less than 4 minutes. But my 160 might take
just a wee bit longer, though.
Anyways, thanks for the help, and your patience reading this long-winded
post.

Doesn't matter the capacity of the hard drive regarding time in saving data.
What matters is the amount of file data in imaging.
Dave