Corrupt File

[Bill Sharpe]

I am having a problem trying to delete a leftover file, eqnedt32.cnt, on
my D: drive. Any attempt to rename, move, or delete the file gives me a
"File or folder is corrupt and unreadable. Please run chkdsk" message. I
have also tried to remove the containing folder, but I get the same result.

I have run chkdsk /f and /r on drive D:. Neither finds any bad sectors.

My concern is that every few days I get a Windows startup message saying
Windows needs to check disk d:. If I let it go ahead and check it runs
chkdsk and doesn't find any errors. I could live with the one bad file
here if Windows wouldn't insist on offering to check the disk at
startup. This happens a couple times a week at startup.

I am using Windows XP Pro with SP2. I have tried ccleaner, which
indicates that it is removing the file or its containing folder, but the
offending file is still there after ccleaner runs.

Any suggestions are welcome.

 

[philo]

I am having a problem trying to delete a leftover file, eqnedt32.cnt, on
my D: drive. Any attempt to rename, move, or delete the file gives me a
"File or folder is corrupt and unreadable. Please run chkdsk" message. I
have also tried to remove the containing folder, but I get the same result.

I have run chkdsk /f and /r on drive D:. Neither finds any bad sectors.

My concern is that every few days I get a Windows startup message saying
Windows needs to check disk d:. If I let it go ahead and check it runs
chkdsk and doesn't find any errors. I could live with the one bad file
here if Windows wouldn't insist on offering to check the disk at
startup. This happens a couple times a week at startup.

I am using Windows XP Pro with SP2. I have tried ccleaner, which
indicates that it is removing the file or its containing folder, but the
offending file is still there after ccleaner runs.

Any suggestions are welcome.

Go to the website of the harddrive's mfg
andf get their diagnostic utility and run it ..
the drive may be failing

 

[Bill Sharpe]

Go to the website of the harddrive's mfg
andf get their diagnostic utility and run it ..
the drive may be failing

A Google search located this thread:
http://www.wilderssecurity.com/showthread.php?t=145505

The corrupt file is from a recovered Acronis True Image backup.
Apparently this is not a hard disk problem. There are several solutions
offered in the thread, including using Linux to delete the offending
file or creating another True Image file backup without the offending
file, formatting the drive, and restoring the backup.

I will investigate the first approach, which appears much less drastic
than the second one...

Bill

 

[philo]

A Google search located this thread:
http://www.wilderssecurity.com/showthread.php?t=145505

The corrupt file is from a recovered Acronis True Image backup.
Apparently this is not a hard disk problem. There are several solutions
offered in the thread, including using Linux to delete the offending
file or creating another True Image file backup without the offending
file, formatting the drive, and restoring the backup.

I will investigate the first approach, which appears much less drastic
than the second one...

Bill

Depending where the file is...
you may be able to boot to the repair console and delete it from there

 

[Bill Sharpe]

Depending where the file is...
you may be able to boot to the repair console and delete it from there

The file is not on the system drive. According to one message in the
lengthy thread I quoted, this approach has been tried and has not
worked. But thanks for the suggestion.

Bill

 

[philo]

The file is not on the system drive. According to one message in the
lengthy thread I quoted, this approach has been tried and has not
worked. But thanks for the suggestion.

Bill

Yes...
the repair console does have limitations!

 

[Bill Sharpe]

Yes...
the repair console does have limitations!

There were actually 8 corrupted files in my Acronis Recovered Files
folder. I backed up my D Drive, leaving this folder out of the backup,
using Acronis True Image, formatted the drive -- had to do this in safe
mode -- and then recovered the files from the backup set. Fairly simple,
but took several hours time.

Bill