Can't write image to disk

[JoRene41]

I suddenly have started being unable to back up my PC using the same backup device I have successfully used in the past. I continue to get the error that the file can't be written to disk, regardless of whether I use the Phylock or VVS. I had no problem until recently. I have doubled the cache size in options and still have the problem. What can I do to solve this? I am using a large usb external harddrive and the problem never occurred before. I reformatted the drive to be sure it was not a problem with the drive.

Please help, as I depend on IFW to back up my computer. Has something changed in recent versions of IFW that could cause this problem?

Thank you!

[TeraByte Support]

can't be written to disk means it can't write the file. You can look in
the .log file for the actual write error showing the windows error code. In
general you'd want to chkdsk /f the target drive, and/or scan it for bad
sectors using something like spinrite.

"JoRene41" wrote in message news:13412@public.image...

I suddenly have started being unable to back up my PC using the same backup
device I have successfully used in the past. I continue to get the error
that the file can't be written to disk, regardless of whether I use the
Phylock or VVS. I had no problem until recently. I have doubled the cache
size in options and still have the problem. What can I do to solve this? I
am using a large usb external harddrive and the problem never occurred
before. I reformatted the drive to be sure it was not a problem with the
drive.

Please help, as I depend on IFW to back up my computer. Has something
changed in recent versions of IFW that could cause this problem?

Thank you!

[JoRene41]

I checked the drive from disk properties and it said it had no errors, I then attached it to a different computer and tried to back up a partition and it backed up the drive with no errors and is almost finished validating the file. Why would it work on one computer and not another? It is a 2 TB external drive.

I also ran a check disk/ f on the drive from a command prompt and after a lengthy time got an error that there was not enough room on the drive to Write the file corrections, even though it was an empty partition with over a TB free. There were no files n the drive and it had just been reformatted to NTFS from exfat.

Any suggestions. The computer it worked on is an older 32 bit running win10 and the one it didn't work on is a newer 64 bit running the same OS. The drive has worked as recently as January on the same computer.

Thank you again for any help.

[JoRene41]

An update. After using the drive successfully on a different computer, I decided to plug it into a different usb port on the computer where it did not work. It backed up perfectly and in addition, took 1/5 the time that it was predicted to take when using the other usb port. All the ports on the laptop are usb3, but I'm assuming the one port is defective in some way. Hopefully that is the end of the problem....other than trying to fix the bad port.

[DrTeeth]

On Thu, 16 Mar 2017 13:44:54 PDT, just as I was about to take a herb,
"TeraByte Support" disturbed my
reverie and wrote:

> In
>general you'd want to chkdsk /f the target drive, and/or scan it for bad
>sectors using something like spinrite.

Don't forget that chkdsk /r can scan for bad sectors too. It will mark
them as "bad" and transfer the contents to a good one.
--
Cheers,

DrT

"If you want to find out what is wrong
with democracy, spend five minutes with
the average voter." - Winston Churchill

[JoRene41]

Did the chkdsk/r and drive tested perfect...no errors. It might have been the usb port. I won't use that port to back up.