What causes Corrupted Files?

  • Thread starter Thread starter Rainy
  • Start date Start date
R

Rainy

Periodically, I am having to deal with my Maxtor One Touch external drive
500GB having corrupted files. I moved some of my files off that drive and
have had no trouble with those files.. Is there something I can do to
prevent this. or is it a bad drive? thanks Rainy
 
Rainy said:
Periodically, I am having to deal with my Maxtor One Touch external drive
500GB having corrupted files. I moved some of my files off that drive and
have had no trouble with those files.. Is there something I can do to
prevent this. or is it a bad drive? thanks Rainy
Click to expand...

Various things can cause this, from defective or damaged disks to bad USB
cables or external case hardware to subtle memory errors.

What exactly do you mean by "corrupted"? Are there any specific error
messages presented?

Would suggest first that you be sure that your files are backed up on
another drive, then run basic disk-checking utitlies, such as chkdsk with
the /R switch.

HTH
-pk
 
yes files, today for instance it was a font file I ran chckdsk after i was
told about it.. I run it with the /F parameter.. isn't that correct.. I
thought the F was for fix.. I'm assuming the R is for repair but I am
guessing.. thanks for your input.. hugs Rainy
Rainy said:
Periodically, I am having to deal with my Maxtor One Touch external drive
500GB having corrupted files. I moved some of my files off that drive and
have had no trouble with those files.. Is there something I can do to
prevent this. or is it a bad drive? thanks Rainy
Click to expand...

Various things can cause this, from defective or damaged disks to bad USB
cables or external case hardware to subtle memory errors.

What exactly do you mean by "corrupted"? Are there any specific error
messages presented?

Would suggest first that you be sure that your files are backed up on
another drive, then run basic disk-checking utitlies, such as chkdsk with
the /R switch.

HTH
-pk
 
Thanks DL, I went to the website and found a way to use the Maxtor manager
which I have on my computer to test the drive.. hugs Rainy


See what utilities Maxtor has on their site to test the drive
 
yes files, today for instance it was a font file I ran chckdsk after i was
told about it.. I run it with the /F parameter.. isn't that correct.. I
thought the F was for fix.. I'm assuming the R is for repair . . .
Click to expand...

CLI parameters are probably documented in the Help department
or else displayed at a CMD prompt by CHKDSK /?

If a Windows font file has been corrupted it seems wiser to replace
it from the WinXP instal file (CD or HDD) via SFC = System File
Checker. But the physical integrity of the HDD is more important.
 
Yes I could easily replace it.. or not miss it if It were deleted. Will do
this next time.. You will have to explain what CLI parameters are.. chkdsk
/? so that is what I am asking.. what is R and what is F.. and what is
CLI.. thanks Rainy ps it was not a windows font file.. I have thousands
more on my computer.. quite the collector I am.. lol over 90,000 .. lol like
I said I would not miss it.. I only have windows font files in the windows
font folder.. all the rest are on my external drive..


yes files, today for instance it was a font file I ran chckdsk after i was
told about it.. I run it with the /F parameter.. isn't that correct.. I
thought the F was for fix.. I'm assuming the R is for repair . . .
Click to expand...

CLI parameters are probably documented in the Help department
or else displayed at a CMD prompt by CHKDSK /?

If a Windows font file has been corrupted it seems wiser to replace
it from the WinXP instal file (CD or HDD) via SFC = System File
Checker. But the physical integrity of the HDD is more important.
 
Rainy said:
Yes I could easily replace it.. or not miss it if It were deleted. Will
do
this next time.. You will have to explain what CLI parameters are.. chkdsk
/? so that is what I am asking.. what is R and what is F.. and what is
CLI.. thanks Rainy ps it was not a windows font file.. I have thousands
more on my computer.. quite the collector I am.. lol over 90,000 .. lol
like
I said I would not miss it.. I only have windows font files in the windows
font folder.. all the rest are on my external drive..
Click to expand...

CLI = Command Line Interface. It's what you see when you open a command
prompt. For a full list of XP's command line tools, open Help and Support
and type "command line tools". The first entry gives you a list.

If you open a command prompt and type "chkdsk /?" - note the space - you'll
get a text listing of what the parameters, or switches, are and what they
do.

Using Windows Help to see command line prompts, just type chkdsk into the
search section. This can be easier to read than the command prompt
version.

The difference between /F and /R (case does not matter) is that the /R
switch goes a bit further and not only tries to fix the disk error, but also
tries to Recover information from the bad section.

But if you are getting bad sectors on the disk, I'd suggest replacing it.
Where I am, bare 500-gig drives are under $100.

HTH
-pk
 
Rainy said:
Yes I could easily replace it.. or not miss it if It were deleted. Will
do
this next time.. You will have to explain what CLI parameters are.. chkdsk
/? so that is what I am asking.. what is R and what is F.. and what is
CLI.. thanks Rainy ps it was not a windows font file.. I have thousands
more on my computer.. quite the collector I am.. lol over 90,000 .. lol
like
I said I would not miss it.. I only have windows font files in the windows
font folder.. all the rest are on my external drive..




CLI parameters are probably documented in the Help department
or else displayed at a CMD prompt by CHKDSK /?

If a Windows font file has been corrupted it seems wiser to replace
it from the WinXP instal file (CD or HDD) via SFC = System File
Checker. But the physical integrity of the HDD is more important.
Click to expand...
CLI = Command Line Interpreter. For Windows XP, this program is cmd.exe.
For this discussion, entering CHKDSK /? at the cmd prompt causes chkdsk to
list all of the parameters that you can use with chkdsk.

Jim
 
My disk was cheaper than that. under $50..brand new too.. . thanks for all
the information I will look in help. I will not replace it unless I am
certain it's the drive's fault and someone suggested it might be a usb
cables..or even a memory error. .I don't have a lot of money to throw
around.. will do the R parameter next if I have to do Chkdsk.. This time I
tried and got the prompt I had to have full rights, the same prompt you get
when you try to chkdsk C in Windows.. but they asked me if I wanted to do
it on boot, I said yes.. thanks again.. hugs, Rainy
Rainy said:
Yes I could easily replace it.. or not miss it if It were deleted. Will
do
this next time.. You will have to explain what CLI parameters are.. chkdsk
/? so that is what I am asking.. what is R and what is F.. and what is
CLI.. thanks Rainy ps it was not a windows font file.. I have thousands
more on my computer.. quite the collector I am.. lol over 90,000 .. lol
like
I said I would not miss it.. I only have windows font files in the windows
font folder.. all the rest are on my external drive..
Click to expand...

CLI = Command Line Interface. It's what you see when you open a command
prompt. For a full list of XP's command line tools, open Help and Support
and type "command line tools". The first entry gives you a list.

If you open a command prompt and type "chkdsk /?" - note the space - you'll
get a text listing of what the parameters, or switches, are and what they
do.

Using Windows Help to see command line prompts, just type chkdsk into the
search section. This can be easier to read than the command prompt
version.

The difference between /F and /R (case does not matter) is that the /R
switch goes a bit further and not only tries to fix the disk error, but also
tries to Recover information from the bad section.

But if you are getting bad sectors on the disk, I'd suggest replacing it.
Where I am, bare 500-gig drives are under $100.

HTH
-pk
 
it wasn't a windows font file.. but yes easier to replace it.. or simply
delete it.. hugs Rainy

Rainy said:
Yes I could easily replace it.. or not miss it if It were deleted. Will
do
this next time.. You will have to explain what CLI parameters are.. chkdsk
/? so that is what I am asking.. what is R and what is F.. and what is
CLI.. thanks Rainy ps it was not a windows font file.. I have thousands
more on my computer.. quite the collector I am.. lol over 90,000 .. lol
like
I said I would not miss it.. I only have windows font files in the windows
font folder.. all the rest are on my external drive..




CLI parameters are probably documented in the Help department
or else displayed at a CMD prompt by CHKDSK /?

If a Windows font file has been corrupted it seems wiser to replace
it from the WinXP instal file (CD or HDD) via SFC = System File
Checker. But the physical integrity of the HDD is more important.
Click to expand...
CLI = Command Line Interpreter. For Windows XP, this program is cmd.exe.
For this discussion, entering CHKDSK /? at the cmd prompt causes chkdsk to
list all of the parameters that you can use with chkdsk.

Jim
 
Patrick said:
CLI = Command Line Interface. It's what you see when you open a
command prompt. For a full list of XP's command line tools, open
Help and Support and type "command line tools". The first entry
gives you a list.
If you open a command prompt and type "chkdsk /?" - note the space -
you'll get a text listing of what the parameters, or switches, are
and what they do.

Using Windows Help to see command line prompts, just type chkdsk into
the search section. This can be easier to read than the command
prompt version.

The difference between /F and /R (case does not matter) is that the /R
switch goes a bit further and not only tries to fix the disk error,
but also tries to Recover information from the bad section.

But if you are getting bad sectors on the disk, I'd suggest replacing
it. Where I am, bare 500-gig drives are under $100.

HTH
-pk
Click to expand...

/R continues on to check the empty portions/areas of the disk and all of
it for bad sectors. /F tries to recover or fix any errors it finds but
does nothing in the areas of the disk where there are no files and does
not mark bad sectors. /R also prevents future writes to bad blocks.

Checks a disk and displays a status report.


CHKDSK [volume[[path]filename]]] [/F] [/V] [/R] [/X] [/I] [/C]
[/L[:size]]


volume Specifies the drive letter (followed by a colon),
mount point, or volume name.
filename FAT/FAT32 only: Specifies the files to check for
fragmenta
/F Fixes errors on the disk.
/V On FAT/FAT32: Displays the full path and name of every
fil
on the disk.
On NTFS: Displays cleanup messages if any.
/R Locates bad sectors and recovers readable information
(implies /F).
/L:size NTFS only: Changes the log file size to the specified
num
of kilobytes. If size is not specified, displays
current
size.
/X Forces the volume to dismount first if necessary.
All opened handles to the volume would then be invalid
(implies /F).
/I NTFS only: Performs a less vigorous check of index
entries
/C NTFS only: Skips checking of cycles within the folder
structure.

The /I or /C switch reduces the amount of time required to run Chkdsk by
skipping certain checks of the volume.
 
thanks Twayne.. I'm a little confused, I know my limits! Are you saying
that if I typed chkdsk /I that F is implied?.. I sure would like to reduce
the amount of time this takes.. sometimes an hour and a half that I would
rather be on my computer..thanks for all the input.. I did look in help..
and typed in chkdsk it gave some help as suggested.. :) hugs Rainy
Patrick said:
CLI = Command Line Interface. It's what you see when you open a
command prompt. For a full list of XP's command line tools, open
Help and Support and type "command line tools". The first entry
gives you a list.
If you open a command prompt and type "chkdsk /?" - note the space -
you'll get a text listing of what the parameters, or switches, are
and what they do.

Using Windows Help to see command line prompts, just type chkdsk into
the search section. This can be easier to read than the command
prompt version.

The difference between /F and /R (case does not matter) is that the /R
switch goes a bit further and not only tries to fix the disk error,
but also tries to Recover information from the bad section.

But if you are getting bad sectors on the disk, I'd suggest replacing
it. Where I am, bare 500-gig drives are under $100.

HTH
-pk
Click to expand...

/R continues on to check the empty portions/areas of the disk and all of
it for bad sectors. /F tries to recover or fix any errors it finds but
does nothing in the areas of the disk where there are no files and does
not mark bad sectors. /R also prevents future writes to bad blocks.

Checks a disk and displays a status report.


CHKDSK [volume[[path]filename]]] [/F] [/V] [/R] [/X] [/I] [/C]
[/L[:size]]


volume Specifies the drive letter (followed by a colon),
mount point, or volume name.
filename FAT/FAT32 only: Specifies the files to check for
fragmenta
/F Fixes errors on the disk.
/V On FAT/FAT32: Displays the full path and name of every
fil
on the disk.
On NTFS: Displays cleanup messages if any.
/R Locates bad sectors and recovers readable information
(implies /F).
/L:size NTFS only: Changes the log file size to the specified
num
of kilobytes. If size is not specified, displays
current
size.
/X Forces the volume to dismount first if necessary.
All opened handles to the volume would then be invalid
(implies /F).
/I NTFS only: Performs a less vigorous check of index
entries
/C NTFS only: Skips checking of cycles within the folder
structure.

The /I or /C switch reduces the amount of time required to run Chkdsk by
skipping certain checks of the volume.
 
Rainy wrote:

No. In fact, /I wouldn't be recommended right now. It skips a lot of
testing. Run the chkdsk /r after you're done using the computer if
you're concerned about time. Cutting corners will, well, cut corners
and like any shoddy work, won't be a complete check. If you can't find
a couple hours to let the test run, IMO you're shooting yourself in the
foot. Do it right and with luck it'll be much faster in the overall
than having to run it again. And again. And ...

Twayne


thanks Twayne.. I'm a little confused, I know my limits! Are you
saying that if I typed chkdsk /I that F is implied?.. I sure would
like to reduce the amount of time this takes.. sometimes an hour and
a half that I would rather be on my computer..thanks for all the
input.. I did look in help.. and typed in chkdsk it gave some help as
in message
Patrick said:
CLI = Command Line Interface. It's what you see when you open a
command prompt. For a full list of XP's command line tools, open
Help and Support and type "command line tools". The first entry
gives you a list.
If you open a command prompt and type "chkdsk /?" - note the space -
you'll get a text listing of what the parameters, or switches, are
and what they do.

Using Windows Help to see command line prompts, just type chkdsk into
the search section. This can be easier to read than the command
prompt version.

The difference between /F and /R (case does not matter) is that the
/R switch goes a bit further and not only tries to fix the disk
error, but also tries to Recover information from the bad section.

But if you are getting bad sectors on the disk, I'd suggest replacing
it. Where I am, bare 500-gig drives are under $100.

HTH
-pk
Click to expand...

/R continues on to check the empty portions/areas of the disk and all
of it for bad sectors. /F tries to recover or fix any errors it
finds but does nothing in the areas of the disk where there are no
files and does not mark bad sectors. /R also prevents future writes
to bad blocks.

Checks a disk and displays a status report.


CHKDSK [volume[[path]filename]]] [/F] [/V] [/R] [/X] [/I] [/C]
[/L[:size]]


volume Specifies the drive letter (followed by a colon),
mount point, or volume name.
filename FAT/FAT32 only: Specifies the files to check for
fragmenta
/F Fixes errors on the disk.
/V On FAT/FAT32: Displays the full path and name of
every fil
on the disk.
On NTFS: Displays cleanup messages if any.
/R Locates bad sectors and recovers readable information
(implies /F).
/L:size NTFS only: Changes the log file size to the
specified num
of kilobytes. If size is not specified, displays
current
size.
/X Forces the volume to dismount first if necessary.
All opened handles to the volume would then be
invalid (implies /F).
/I NTFS only: Performs a less vigorous check of index
entries
/C NTFS only: Skips checking of cycles within the folder
structure.

The /I or /C switch reduces the amount of time required to run Chkdsk
by skipping certain checks of the volume.
Click to expand...
 
thanks, I will... appreciate the input.. hugs Rainy
Rainy wrote:

No. In fact, /I wouldn't be recommended right now. It skips a lot of
testing. Run the chkdsk /r after you're done using the computer if
you're concerned about time. Cutting corners will, well, cut corners
and like any shoddy work, won't be a complete check. If you can't find
a couple hours to let the test run, IMO you're shooting yourself in the
foot. Do it right and with luck it'll be much faster in the overall
than having to run it again. And again. And ...

Twayne


thanks Twayne.. I'm a little confused, I know my limits! Are you
saying that if I typed chkdsk /I that F is implied?.. I sure would
like to reduce the amount of time this takes.. sometimes an hour and
a half that I would rather be on my computer..thanks for all the
input.. I did look in help.. and typed in chkdsk it gave some help as
in message
Patrick said:
CLI = Command Line Interface. It's what you see when you open a
command prompt. For a full list of XP's command line tools, open
Help and Support and type "command line tools". The first entry
gives you a list.
If you open a command prompt and type "chkdsk /?" - note the space -
you'll get a text listing of what the parameters, or switches, are
and what they do.

Using Windows Help to see command line prompts, just type chkdsk into
the search section. This can be easier to read than the command
prompt version.

The difference between /F and /R (case does not matter) is that the
/R switch goes a bit further and not only tries to fix the disk
error, but also tries to Recover information from the bad section.

But if you are getting bad sectors on the disk, I'd suggest replacing
it. Where I am, bare 500-gig drives are under $100.

HTH
-pk
Click to expand...

/R continues on to check the empty portions/areas of the disk and all
of it for bad sectors. /F tries to recover or fix any errors it
finds but does nothing in the areas of the disk where there are no
files and does not mark bad sectors. /R also prevents future writes
to bad blocks.

Checks a disk and displays a status report.


CHKDSK [volume[[path]filename]]] [/F] [/V] [/R] [/X] [/I] [/C]
[/L[:size]]


volume Specifies the drive letter (followed by a colon),
mount point, or volume name.
filename FAT/FAT32 only: Specifies the files to check for
fragmenta
/F Fixes errors on the disk.
/V On FAT/FAT32: Displays the full path and name of
every fil
on the disk.
On NTFS: Displays cleanup messages if any.
/R Locates bad sectors and recovers readable information
(implies /F).
/L:size NTFS only: Changes the log file size to the
specified num
of kilobytes. If size is not specified, displays
current
size.
/X Forces the volume to dismount first if necessary.
All opened handles to the volume would then be
invalid (implies /F).
/I NTFS only: Performs a less vigorous check of index
entries
/C NTFS only: Skips checking of cycles within the folder
structure.

The /I or /C switch reduces the amount of time required to run Chkdsk
by skipping certain checks of the volume.
Click to expand...
 
90,000 FONTS ???
Not all in the fonts folder right?



--
~~~~~~~~~~~~~~~~~~
Rob Giordano
Microsoft MVP Expression
 
of course not.. lol I don't think windows likes too many more than about
300.. I only have windows fonts there .. hugs Rainy..
90,000 FONTS ???
Not all in the fonts folder right?



--
~~~~~~~~~~~~~~~~~~
Rob Giordano
Microsoft MVP Expression
 
Back
Top