TeraByte Unlimited

Using version 2.99 of IFW, I was always able to save my C: drive (about 25 GB) to any other large drive, including a USB thumb drive with 105 GB of free space. Now that I upgraded to v3.06a (because of Windows 10 changes), when I try to save my C: drive to the USB thumb drive, it always fails with the error message "Unable to write data to file". Where should I begin looking to try to resolve this?

the log that shows the windows error code.

"terabite" wrote in message news:[email protected]...

Using version 2.99 of IFW, I was always able to save my C: drive (about 25
GB) to any other large drive, including a USB thumb drive with 105 GB of
free space. Now that I upgraded to v3.06a (because of Windows 10 changes),
when I try to save my C: drive to the USB thumb drive, it always fails with
the error message "Unable to write data to file". Where should I begin
looking to try to resolve this?

Thanks. Here's what it says:

[2017-06-22 11:39:23 AM] Image for Windows (x64) 3.06a
[2017-06-22 11:39:23 AM] Starting ...
imagew64.exe /b /d:w0@0x4 /f:"F:\E450" /max:4GiB /v /vb /enc:1
[2017-06-22 11:39:23 AM] PHYLock is waiting for drive writing to stop ...
[2017-06-22 11:40:46 AM] PHYLock using drive C:
[2017-06-22 11:40:46 AM] PHYLock Started
[2017-06-22 11:40:46 AM] PHYLock Using Disk
[2017-06-22 11:40:46 AM] PHYLock version 14
[2017-06-22 11:40:46 AM] Backup: Drive 0 (C:) os Partition (04) 236000 MiB NTFS
[2017-06-22 11:40:46 AM] To: F:\E450.TBI
[2017-06-22 11:48:42 AM] Error writing to F:\E450.1 (Buf:0000000004D70000 CurFP:3982233600 Bytes:983040 Err:2h)
[2017-06-22 11:48:42 AM] INFO: Total Sectors:483328000 Total Allocated:109204504
[2017-06-22 11:48:42 AM] Operation Completed with Error Code 4
[2017-06-22 11:48:42 AM] Unable to write data to file!
[2017-06-22 12:15:52 PM] Stop

Even though IFW.LOG didn't provide any additional information, that alone suggested to me that there might be something wrong with the USB drive itself. So I ejected the drive, removed it, inserted it back in again, and only *then* did Windows report that it had detected a problem with the drive. It offered to try to repair it, and I accepted. Then Image for Windows worked fine.

I mention all of this only in case someone else in the future has a similar problem, so they might be able to find this post by searching and try this procedure.

Thanks again!

https://msdn.microsoft.com/en-us/library/windows/desktop/ms681382(v=vs.85).aspx

error 2 = file not found ?

Is it being deleted or blocked by something?

look while that message is displayed.

"terabite" wrote in message news:[email protected]...

Thanks. Here's what it says:

[2017-06-22 11:39:23 AM] Image for Windows (x64) 3.06a
[2017-06-22 11:39:23 AM] Starting ...
imagew64.exe /b /d:w0@0x4 /f:"F:\E450" /max:4GiB /v /vb /enc:1
[2017-06-22 11:39:23 AM] PHYLock is waiting for drive writing to stop ...
[2017-06-22 11:40:46 AM] PHYLock using drive C:
[2017-06-22 11:40:46 AM] PHYLock Started
[2017-06-22 11:40:46 AM] PHYLock Using Disk
[2017-06-22 11:40:46 AM] PHYLock version 14
[2017-06-22 11:40:46 AM] Backup: Drive 0 (C:) os Partition (04) 236000 MiB
NTFS
[2017-06-22 11:40:46 AM] To: F:\E450.TBI
[2017-06-22 11:48:42 AM] Error writing to F:\E450.1 (Buf:0000000004D70000
CurFP:3982233600 Bytes:983040 Err:2h)
[2017-06-22 11:48:42 AM] INFO: Total Sectors:483328000 Total
Allocated:109204504
[2017-06-22 11:48:42 AM] Operation Completed with Error Code 4
[2017-06-22 11:48:42 AM] Unable to write data to file!
[2017-06-22 12:15:52 PM] Stop

Even though IFW.LOG didn't provide any additional information, that alone
suggested to me that there might be something wrong with the USB drive
itself. So I ejected the drive, removed it, inserted it back in again, and
only *then* did Windows report that it had detected a problem with the
drive. It offered to try to repair it, and I accepted. Then Image for
Windows worked fine.

I mention all of this only in case someone else in the future has a similar
problem, so they might be able to find this post by searching and try this
procedure.

Thanks again!