Backup - unable to read file or directory

When doing a full backup (Windows Home Premium), I get the above message.
with a rather long and unfortunately unmemorable hex number. Unfortunately,
it doesn't say what file it is having a problem with, which is really less
than helpful. I have run chkdsk on all my drives, and it produced not a
squeak, so I have absolutely no idea what file is causing the problem. Also,
I don't think it is helpful to abort the backup because you can't read a file
(or directory). The backup should just carry on and then give you a list of
files it had problems with.

I'm currently running an incremental backup which appears to have picked up
where the full backup left off, but its rather difficult to tell.

How do I find and fix the issue?

Are you backing up to a FAT32 external hard drive?

"ThosRTanner" <> wrote in message
news:20779EE4-9380-470F-82DE-...
> When doing a full backup (Windows Home Premium), I get the above message.
> with a rather long and unfortunately unmemorable hex number.
> Unfortunately,
> it doesn't say what file it is having a problem with, which is really less
> than helpful. I have run chkdsk on all my drives, and it produced not a
> squeak, so I have absolutely no idea what file is causing the problem.
> Also,
> I don't think it is helpful to abort the backup because you can't read a
> file
> (or directory). The backup should just carry on and then give you a list
> of
> files it had problems with.
>
> I'm currently running an incremental backup which appears to have picked
> up
> where the full backup left off, but its rather difficult to tell.
>
> How do I find and fix the issue?

"Bob" wrote:

> Are you backing up to a FAT32 external hard drive?
No, it's an external NTFS drive

>
> "ThosRTanner" <> wrote in message
> news:20779EE4-9380-470F-82DE-...
> > When doing a full backup (Windows Home Premium), I get the above message.
> > with a rather long and unfortunately unmemorable hex number.
> > Unfortunately,
> > it doesn't say what file it is having a problem with, which is really less
> > than helpful. I have run chkdsk on all my drives, and it produced not a
> > squeak, so I have absolutely no idea what file is causing the problem.
> > Also,
> > I don't think it is helpful to abort the backup because you can't read a
> > file
> > (or directory). The backup should just carry on and then give you a list
> > of
> > files it had problems with.
> >
> > I'm currently running an incremental backup which appears to have picked
> > up
> > where the full backup left off, but its rather difficult to tell.
> >
> > How do I find and fix the issue?
>
>