BoatBanter.com

BoatBanter.com (https://www.boatbanter.com/)
-   General (https://www.boatbanter.com/general/)
-   -   chkdsk (https://www.boatbanter.com/general/159895-chkdsk.html)

Mr. Luddite January 27th 14 06:19 PM

chkdsk
 
On 1/27/2014 1:16 PM, Hank wrote:
On 1/27/2014 12:07 PM, Mr. Luddite wrote:
On 1/27/2014 11:33 AM, Boating All Out wrote:
In article ,
says...

On 1/27/2014 10:03 AM, F.O.A.D. wrote:
On 1/27/14, 9:20 AM, Poco Loco wrote:
On Sun, 26 Jan 2014 21:08:52 -0500, "F.O.A.D."
wrote:

On 1/26/14, 8:54 PM, Poco Loco wrote:
On 26 Jan 2014 21:56:01 GMT, F.O.A.D. wrote:

Forgotten the joys of chkdsk on windoze... Yawn.

What the hell are you doing with chkdsk? Windows for Workgroups?
That's an old one, for sure.



Chkdsk is one of the tools that is easily available on Windoze 7.
It's
still useful, if maddeningly slow. It can find and repair simple
problems that might come up on hard drives running Windoze.

The 'chkdsk' tool has been around for a long time. Glad you found it
and hope it helps.


I'm surprised so many of you windoze acolytes don't run it at least
once
a month in order to seek out and repair those bad clusters the OS
creates.


I don't know Harry. For kicks I just ran chkdsk on this five year old
Vista laptop for the first time since I bought it. Took about 20-25
minutes and reported zero bad files or clusters. I've used this
computer a lot.

I did on a heavily used 500gb drive on my Win7 system. 4 years old.
Took about 30 seconds. Zero bad files or clusters.
Harry's living in the past.


30 seconds to run a check on a 500Gb drive? That's too fast to be
believable.

My Vista laptop only has a 285Gb drive and it took almost 25 minutes.
When chkdsk first started, it just sat there for a while doing nothing.
I was about to close it thinking it wasn't doing anything when it
suddenly started reporting "stage 1 of 3" activities, then "stage 2 of
3", etc. It displayed percentage of completion of the disk scan as it
worked.

Are you sure you didn't shut it down before it even started?


Don't you need to specify some paramaters when you run it from the
command prompt. I'll bet he forgot.


Yup. Just like using DOS





Hank January 27th 14 06:23 PM

chkdsk
 
On 1/27/2014 1:06 PM, Mr. Luddite wrote:
On 1/27/2014 12:57 PM, Hank wrote:
On 1/27/2014 12:12 PM, Mr. Luddite wrote:
On 1/27/2014 12:02 PM, wrote:
On Mon, 27 Jan 2014 11:22:33 -0500, "Mr. Luddite"
wrote:

On 1/27/2014 10:03 AM, F.O.A.D. wrote:

I'm surprised so many of you windoze acolytes don't run it at least
once
a month in order to seek out and repair those bad clusters the OS
creates.


I don't know Harry. For kicks I just ran chkdsk on this five year old
Vista laptop for the first time since I bought it. Took about 20-25
minutes and reported zero bad files or clusters. I've used this
computer a lot.


Generally you only get crosslinked and orphan clusters when you do
power dumps without a shutdown, closing all open files.
I think it is a worse problem with FAT drives than NTFS drives.

Norton DD does a whole lot better job with this than CHKDSK. It can
fix partition table problems and other beasies that make a PC a
doorstop.


Every computer we've had, including my wife's, have been allergic to
Norton. If a new computer comes with it I never enable it. If it *has*
been enabled (like on a couple of my wife's computers) I purge the disk
of any remnants of Norton. It caused more problems than it prevented,
IMO.


I hear you. Also AVG antivirus is worth avoiding. When you have it it's
slow and when you try to get rid of it it keeps on popping up.


Been using AVG (free version) for years. I like it a lot and have
never noticed any ill affects or slow down of the computers, unlike with
Norton or McAfee.


I thought it was AVG that came bundled. Maybe it was McAffee. I don't know.

Mr. Luddite January 27th 14 06:30 PM

chkdsk
 
On 1/27/2014 1:23 PM, Hank wrote:
On 1/27/2014 1:06 PM, Mr. Luddite wrote:
On 1/27/2014 12:57 PM, Hank wrote:
On 1/27/2014 12:12 PM, Mr. Luddite wrote:
On 1/27/2014 12:02 PM, wrote:
On Mon, 27 Jan 2014 11:22:33 -0500, "Mr. Luddite"
wrote:

On 1/27/2014 10:03 AM, F.O.A.D. wrote:

I'm surprised so many of you windoze acolytes don't run it at least
once
a month in order to seek out and repair those bad clusters the OS
creates.


I don't know Harry. For kicks I just ran chkdsk on this five year
old
Vista laptop for the first time since I bought it. Took about 20-25
minutes and reported zero bad files or clusters. I've used this
computer a lot.


Generally you only get crosslinked and orphan clusters when you do
power dumps without a shutdown, closing all open files.
I think it is a worse problem with FAT drives than NTFS drives.

Norton DD does a whole lot better job with this than CHKDSK. It can
fix partition table problems and other beasies that make a PC a
doorstop.


Every computer we've had, including my wife's, have been allergic to
Norton. If a new computer comes with it I never enable it. If it
*has*
been enabled (like on a couple of my wife's computers) I purge the
disk
of any remnants of Norton. It caused more problems than it prevented,
IMO.


I hear you. Also AVG antivirus is worth avoiding. When you have it it's
slow and when you try to get rid of it it keeps on popping up.


Been using AVG (free version) for years. I like it a lot and have
never noticed any ill affects or slow down of the computers, unlike with
Norton or McAfee.


I thought it was AVG that came bundled. Maybe it was McAffee. I don't know.


More likely McAfee. I don't think AVG comes bundled with any computer.

Boating All Out January 27th 14 06:45 PM

chkdsk
 
In article ,
says...


30 seconds to run a check on a 500Gb drive? That's too fast to be
believable.

My Vista laptop only has a 285Gb drive and it took almost 25 minutes.
When chkdsk first started, it just sat there for a while doing nothing.
I was about to close it thinking it wasn't doing anything when it
suddenly started reporting "stage 1 of 3" activities, then "stage 2 of
3", etc. It displayed percentage of completion of the disk scan as it
worked.

Are you sure you didn't shut it down before it even started?


All right, I was off. I brought out the stopwatch. 32.18 seconds.

C:\Windows\system32chkdsk d:
The type of the file system is NTFS.
Volume label is WD500-S1-500GB-Part.

WARNING! F parameter not specified.
Running CHKDSK in read-only mode.

CHKDSK is verifying files (stage 1 of 3)...
106496 file records processed.
File verification completed.
13 large file records processed.
0 bad file records processed.
0 EA records processed.
0 reparse records processed.
CHKDSK is verifying indexes (stage 2 of 3)...
119452 index entries processed.
Index verification completed.
0 unindexed files scanned.
0 unindexed files recovered.
CHKDSK is verifying security descriptors (stage 3 of 3)...
106496 file SDs/SIDs processed.
Security descriptor verification completed.
6479 data files processed.
CHKDSK is verifying Usn Journal...
9256552 USN bytes processed.
Usn Journal verification completed.
Windows has checked the file system and found no problems.

488383487 KB total disk space.
423552356 KB in 77125 files.
31428 KB in 6480 indexes.
0 KB in bad sectors.
196667 KB in use by the system.
65536 KB occupied by the log file.
64603036 KB available on disk.

Mr. Luddite January 27th 14 07:39 PM

chkdsk
 
On 1/27/2014 1:45 PM, Boating All Out wrote:

In article ,
says...


30 seconds to run a check on a 500Gb drive? That's too fast to be
believable.

My Vista laptop only has a 285Gb drive and it took almost 25 minutes.
When chkdsk first started, it just sat there for a while doing nothing.
I was about to close it thinking it wasn't doing anything when it
suddenly started reporting "stage 1 of 3" activities, then "stage 2 of
3", etc. It displayed percentage of completion of the disk scan as it
worked.

Are you sure you didn't shut it down before it even started?


All right, I was off. I brought out the stopwatch. 32.18 seconds.

C:\Windows\system32chkdsk d:
The type of the file system is NTFS.
Volume label is WD500-S1-500GB-Part.

WARNING! F parameter not specified.
Running CHKDSK in read-only mode.

CHKDSK is verifying files (stage 1 of 3)...
106496 file records processed.


First big difference: Mine reported 604373 files processed.

File verification completed.
13 large file records processed.


2nd big difference: Mine reported 2212 large file records

0 bad file records processed.
0 EA records processed.


Everything else is basically the same with differences for hard drive
volume name, capacity, etc. Still took about 20 minutes to complete.
When it finished it automatically shut down before I could copy and
paste the results and I didn't bother going looking for the log.

Interesting because I am currently only using about 130Gb of the 285Gb
drive.



Boating All Out January 27th 14 08:03 PM

chkdsk
 
In article ,
says...

On 1/27/2014 1:45 PM, Boating All Out wrote:

In article ,
says...


30 seconds to run a check on a 500Gb drive? That's too fast to be
believable.

My Vista laptop only has a 285Gb drive and it took almost 25 minutes.
When chkdsk first started, it just sat there for a while doing nothing.
I was about to close it thinking it wasn't doing anything when it
suddenly started reporting "stage 1 of 3" activities, then "stage 2 of
3", etc. It displayed percentage of completion of the disk scan as it
worked.

Are you sure you didn't shut it down before it even started?


All right, I was off. I brought out the stopwatch. 32.18 seconds.

C:\Windows\system32chkdsk d:
The type of the file system is NTFS.
Volume label is WD500-S1-500GB-Part.

WARNING! F parameter not specified.
Running CHKDSK in read-only mode.

CHKDSK is verifying files (stage 1 of 3)...
106496 file records processed.


First big difference: Mine reported 604373 files processed.

File verification completed.
13 large file records processed.


2nd big difference: Mine reported 2212 large file records

0 bad file records processed.
0 EA records processed.


Everything else is basically the same with differences for hard drive
volume name, capacity, etc. Still took about 20 minutes to complete.
When it finished it automatically shut down before I could copy and
paste the results and I didn't bother going looking for the log.

Interesting because I am currently only using about 130Gb of the 285Gb
drive.


It's apples and oranges, since yours is a Vista box.


Mr. Luddite January 27th 14 08:43 PM

chkdsk
 
On 1/27/2014 3:25 PM, wrote:
On Mon, 27 Jan 2014 12:45:36 -0600, Boating All Out
wrote:

In article ,
says...


30 seconds to run a check on a 500Gb drive? That's too fast to be
believable.

My Vista laptop only has a 285Gb drive and it took almost 25 minutes.
When chkdsk first started, it just sat there for a while doing nothing.
I was about to close it thinking it wasn't doing anything when it
suddenly started reporting "stage 1 of 3" activities, then "stage 2 of
3", etc. It displayed percentage of completion of the disk scan as it
worked.

Are you sure you didn't shut it down before it even started?


All right, I was off. I brought out the stopwatch. 32.18 seconds.

C:\Windows\system32chkdsk d:
The type of the file system is NTFS.
Volume label is WD500-S1-500GB-Part.

WARNING! F parameter not specified.
Running CHKDSK in read-only mode.

CHKDSK is verifying files (stage 1 of 3)...
106496 file records processed.
File verification completed.
13 large file records processed.
0 bad file records processed.
0 EA records processed.
0 reparse records processed.
CHKDSK is verifying indexes (stage 2 of 3)...
119452 index entries processed.
Index verification completed.
0 unindexed files scanned.
0 unindexed files recovered.
CHKDSK is verifying security descriptors (stage 3 of 3)...
106496 file SDs/SIDs processed.
Security descriptor verification completed.
6479 data files processed.
CHKDSK is verifying Usn Journal...
9256552 USN bytes processed.
Usn Journal verification completed.
Windows has checked the file system and found no problems.

488383487 KB total disk space.
423552356 KB in 77125 files.
31428 KB in 6480 indexes.
0 KB in bad sectors.
196667 KB in use by the system.
65536 KB occupied by the log file.
64603036 KB available on disk.


You only ran stage 1, Stage 2 is the slow one.
My C: has about 70,000 files and runs in about 20 seconds (1, 2, 3)




Look at his report again. It ran all three stages.



F.O.A.D. January 27th 14 08:44 PM

chkdsk
 
On 1/27/14, 3:43 PM, Mr. Luddite wrote:
On 1/27/2014 3:25 PM, wrote:
On Mon, 27 Jan 2014 12:45:36 -0600, Boating All Out
wrote:

In article ,
says...


30 seconds to run a check on a 500Gb drive? That's too fast to be
believable.

My Vista laptop only has a 285Gb drive and it took almost 25 minutes.
When chkdsk first started, it just sat there for a while doing nothing.
I was about to close it thinking it wasn't doing anything when it
suddenly started reporting "stage 1 of 3" activities, then "stage 2 of
3", etc. It displayed percentage of completion of the disk scan as it
worked.

Are you sure you didn't shut it down before it even started?

All right, I was off. I brought out the stopwatch. 32.18 seconds.

C:\Windows\system32chkdsk d:
The type of the file system is NTFS.
Volume label is WD500-S1-500GB-Part.

WARNING! F parameter not specified.
Running CHKDSK in read-only mode.

CHKDSK is verifying files (stage 1 of 3)...
106496 file records processed.
File verification completed.
13 large file records processed.
0 bad file records processed.
0 EA records processed.
0 reparse records processed.
CHKDSK is verifying indexes (stage 2 of 3)...
119452 index entries processed.
Index verification completed.
0 unindexed files scanned.
0 unindexed files recovered.
CHKDSK is verifying security descriptors (stage 3 of 3)...
106496 file SDs/SIDs processed.
Security descriptor verification completed.
6479 data files processed.
CHKDSK is verifying Usn Journal...
9256552 USN bytes processed.
Usn Journal verification completed.
Windows has checked the file system and found no problems.

488383487 KB total disk space.
423552356 KB in 77125 files.
31428 KB in 6480 indexes.
0 KB in bad sectors.
196667 KB in use by the system.
65536 KB occupied by the log file.
64603036 KB available on disk.


You only ran stage 1, Stage 2 is the slow one.
My C: has about 70,000 files and runs in about 20 seconds (1, 2, 3)




Look at his report again. It ran all three stages.



I just ran the Apple equivalent of chkdsk...took a minute, found nothing
to fix.

--
There’s no point crying over spilled 4-Methylcyclohexanemethanol.

Boating All Out January 27th 14 08:59 PM

chkdsk
 
In article ,
says...

On Mon, 27 Jan 2014 12:45:36 -0600, Boating All Out
wrote:

In article ,
says...


30 seconds to run a check on a 500Gb drive? That's too fast to be
believable.

My Vista laptop only has a 285Gb drive and it took almost 25 minutes.
When chkdsk first started, it just sat there for a while doing nothing.
I was about to close it thinking it wasn't doing anything when it
suddenly started reporting "stage 1 of 3" activities, then "stage 2 of
3", etc. It displayed percentage of completion of the disk scan as it
worked.

Are you sure you didn't shut it down before it even started?


All right, I was off. I brought out the stopwatch. 32.18 seconds.

C:\Windows\system32chkdsk d:
The type of the file system is NTFS.
Volume label is WD500-S1-500GB-Part.

WARNING! F parameter not specified.
Running CHKDSK in read-only mode.

CHKDSK is verifying files (stage 1 of 3)...
106496 file records processed.
File verification completed.
13 large file records processed.
0 bad file records processed.
0 EA records processed.
0 reparse records processed.
CHKDSK is verifying indexes (stage 2 of 3)...
119452 index entries processed.
Index verification completed.
0 unindexed files scanned.
0 unindexed files recovered.
CHKDSK is verifying security descriptors (stage 3 of 3)...
106496 file SDs/SIDs processed.
Security descriptor verification completed.
6479 data files processed.
CHKDSK is verifying Usn Journal...
9256552 USN bytes processed.
Usn Journal verification completed.
Windows has checked the file system and found no problems.

488383487 KB total disk space.
423552356 KB in 77125 files.
31428 KB in 6480 indexes.
0 KB in bad sectors.
196667 KB in use by the system.
65536 KB occupied by the log file.
64603036 KB available on disk.


You only ran stage 1, Stage 2 is the slow one.
My C: has about 70,000 files and runs in about 20 seconds (1, 2, 3)


I ran stages 1,2,3. Says so above.
"r" parameter wasn't needed, as I see no problems.


Mr. Luddite January 27th 14 09:23 PM

chkdsk
 
On 1/27/2014 3:47 PM, wrote:
On Mon, 27 Jan 2014 14:39:56 -0500, "Mr. Luddite"
wrote:

On 1/27/2014 1:45 PM, Boating All Out wrote:

In article ,
says...


30 seconds to run a check on a 500Gb drive? That's too fast to be
believable.

My Vista laptop only has a 285Gb drive and it took almost 25 minutes.
When chkdsk first started, it just sat there for a while doing nothing.
I was about to close it thinking it wasn't doing anything when it
suddenly started reporting "stage 1 of 3" activities, then "stage 2 of
3", etc. It displayed percentage of completion of the disk scan as it
worked.

Are you sure you didn't shut it down before it even started?

All right, I was off. I brought out the stopwatch. 32.18 seconds.

C:\Windows\system32chkdsk d:
The type of the file system is NTFS.
Volume label is WD500-S1-500GB-Part.

WARNING! F parameter not specified.
Running CHKDSK in read-only mode.

CHKDSK is verifying files (stage 1 of 3)...
106496 file records processed.


First big difference: Mine reported 604373 files processed.

File verification completed.
13 large file records processed.


2nd big difference: Mine reported 2212 large file records

0 bad file records processed.
0 EA records processed.


Everything else is basically the same with differences for hard drive
volume name, capacity, etc. Still took about 20 minutes to complete.
When it finished it automatically shut down before I could copy and
paste the results and I didn't bother going looking for the log.

Interesting because I am currently only using about 130Gb of the 285Gb
drive.


You can put a redirect on the command line and write the output to a
file

chkdsk c: c:\ myfile.txt

Then your output will be in "myfile.txt" in the root directory of the
C: drive.
The other way to see the output is to open the command prompt and
enter it there instead of using the run line.
If you want the time stamp
type in prompt $p$g$t
(gets you time, directory and the "" prompt)





Thanks. I sorta thought it might automatically write it to a log file
but I didn't bother looking for it. That's the first time I've used
chkdsk since Windows 3.1 I think.

The Apple vs Windows debate is really meaningless IMO. Whatever works
for you and meets your needs is what you become familiar with and tend
to like.

My take on the critics of each is this: Mac users represent about 30
percent of computer users last I knew. That's up about 10 percent from
10 years ago. Originally Macs were considered to be "hack proof" mainly
because the hackers targeted the much larger Windows user base. Those
using Macs unfortunately propagated an "elitist" attitude, looking down
their noses at the lowly Windows users. In many ways it was justified.
Microsoft went through many iterations of their Windows OS systems
trying to stay ahead of the hackers. With the introduction of XP and
now Win 7, they have produced a decent OS that is not as prone to hacker
attacks. Win 8 seems to be a more flashy version of Win 7 to me.

Apple users on the other hand can no longer make the claim of being hack
proof. There have been at least two incidences of an Apple OS being
hacked in the past year.

Then you have the millions who use Windows everyday yet continue to
bitch and complain about "Windoze". I don't know why. I think it's
because it became "cool" to be anti-windows years ago and the trend
continues even though we probably use some form of Windows XP or above
everyday, even if we don't go near a computer. Virtually every ATM
machine in the USA is running Windows XP as are cash registers, point of
sale outlets and even ...(gasp) ... commercial airplanes.

I suspect many of the complaints are due to people buying cheap,
underpowered computers that struggle to run anything but expect it to be
a top performer because it is new. That's one thing you really can't do
with a Mac. Even the least expensive laptops are designed to run fine on
the Apple OSX.

The only complaint I have about Apple computers is that I think they and
their accessories are way over-priced. Apple wants $79 for a DVD
writer/CD player for the iMac. I took Harry's advice and bought a
Samsung that looks almost identical, works fine and cost half of what
Apple wants for theirs.







All times are GMT +1. The time now is 08:57 PM.

Powered by vBulletin® Copyright ©2000 - 2025, Jelsoft Enterprises Ltd.
Copyright ©2004 - 2014 BoatBanter.com