TeraByte Unlimited

Title says it all. I'm getting consistent errors, under both VSS and PHYlock, with a complete backup. I'm not doing anything different from usual.

IfW 2.83, clean install Win 8 Pro (tried to back up a pristine install before use!), newish Intel/Asus platform, memtest86+, nothing unusual I'm aware of. None the less, both VSS and PHYLock consistently report byte-by-byte validation errors.

I'm used to relying on byte-for-byte for backup integrity for crucial backups.While VSS has had verification issues in the past, usually one or the other works, this is the first time both are failing me and no idea what to do. I'd like to solve it rather than skip it since without byte-by-byte there's no firm certainty the backup is exact. The disk is a Samsung 840 Pro SSD with no SMART, reallocation, or other visible errors (as one would expect for SSD, as firmware handles any), chkdsk /scan reports no issues, the system isn't overclocked and temp is under 50 C, and driver is Intel RST 12.8.0.1016.

logl:50 shows 2 partitions verifying before the 3rd (the OS) fails. The error log reads:

[23/10/2013 06:51:23] Byte-for-Byte failure at LBA 76928 offset 0 (0)
[23/10/2013 06:51:23] DATA AS BACKED UP: (00000000060E0000)
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
[23/10/2013 06:51:23] DATA NOW ON DISK: (0000000002BE0000)
68 62 69 6E 00 30 00 00 00 10 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
D0 FF FF FF 57 00 69 00 6E 00 64 00 6F 00 77 00
73 00 20 00 42 00 6F 00 6F 00 74 00 20 00 4D 00
61 00 6E 00 61 00 67 00 65 00 72 00 00 00 00 00
A8 FF FF FF 6E 6B 20 00 4B 5F 65 0B 2A CF CE 01
03 00 00 00 38 2E 00 00 00 00 00 00 00 00 00 00
FF FF FF FF FF FF FF FF 01 00 00 00 D8 29 00 00
68 01 00 00 FF FF FF FF 00 00 00 00 00 00 00 00
0E 00 00 00 0C 00 00 00 02 00 00 00 08 00 00 00
31 32 30 30 30 30 30 35 E0 FF FF FF 76 6B 07 00
4E 00 00 00 70 32 00 00 01 00 00 00 01 00 30 30
45 6C 65 6D 65 6E 74 30 F8 FF FF FF A8 30 00 00
E0 FF FF FF 76 6B 07 00 0C 00 00 00 C0 2F 00 00
01 00 00 00 01 00 00 00 45 6C 65 6D 65 6E 74 00
A8 FF FF FF 6E 6B 20 00 4B 5F 65 0B 2A CF CE 01
02 00 00 00 38 2E 00 00 00 00 00 00 00 00 00 00
FF FF FF FF FF FF FF FF 01 00 00 00 D0 2F 00 00
68 01 00 00 FF FF FF FF 00 00 00 00 00 00 00 00
0E 00 00 00 50 00 00 00 03 00 00 00 08 00 00 00
31 34 30 30 30 30 30 36 E0 FF FF FF 76 6B 07 00
50 00 00 00 68 31 00 00 07 00 00 00 01 00 00 00
45 6C 65 6D 65 6E 74 00 A8 FF FF FF 7B 00 37 00
65 00 61 00 32 00 65 00 31 00 61 00 63 00 2D 00
32 00 65 00 36 00 31 00 2D 00 34 00 37 00 32 00
38 00 2D 00 61 00 61 00 61 00 33 00 2D 00 38 00
39 00 36 00 64 00 39 00 64 00 30 00 61 00 39 00
66 00 30 00 65 00 7D 00 00 00 00 00 00 00 00 00
E8 FF FF FF 6C 66 02 00 58 0E 00 00 44 65 73 63
E8 0E 00 00 45 6C 65 6D A8 FF FF FF 6E 6B 20 00
4B 5F 65 0B 2A CF CE 01 03 00 00 00 38 2E 00 00
00 00 00 00 00 00 00 00 FF FF FF FF FF FF FF FF
[23/10/2013 06:51:24] Operation Completed with Error Code 200
[23/10/2013 06:51:24] Byte-for-Byte comparison failed
[23/10/2013 07:11:02] Stop

The log shows a hint of a pattern from previous attempts:

[19/10/2013 17:31:28] Byte-for-Byte failure at LBA 36702538 offset 0 (21504) [PHYLock]
[19/10/2013 18:56:24] Operation Completed with Error Code 0 [PHYLock]
[21/10/2013 00:05:07] Byte-for-Byte failure at LBA 41344 offset 0 (0) [PHYLock]
[21/10/2013 02:54:46] Byte-for-Byte failure at LBA 32258242 offset 0 (33792) [PHYLock]
[21/10/2013 03:03:19] Byte-for-Byte failure at LBA 76928 offset 0 (0) [VSS]
[21/10/2013 15:25:55] Byte-for-Byte failure at LBA 10654938 offset 0 (46080) [PHYLock]
[23/10/2013 06:51:23] Byte-for-Byte failure at LBA 76928 offset 0 (0) [VSS backing up to network share]
[23/10/2013 07:57:19] Byte-for-Byte failure at LBA 48986144 offset 0 (16384) [PHYLock backing up to local disk - immediately afterwards with no reboot]
[23/10/2013 08:04:49] Byte-for-Byte failure at LBA 15734271 offset 0 (65024) [identical rerun without reboot]
[23/10/2013 08:11:18] Byte-for-Byte failure at LBA 76928 offset 0 (0) [identical rerun switching back to VSS + local disk]

Does the consistency of "76928" suggest it could be something quite specific and not a random issue?

I haven't tried backing up a comparable second disk to see if that has the same issue, or the same disk accessed as a data disk from a second boot, or IfD/IfL based backup. I also haven't swapped cables over, although dodgy cables would usually lead to BSOD which I'm not getting. So there are options.

Ideally I do want the standard IfW backup to work and would like to solve why it isn't.

I suppose the first thing is to identify what happens if I substitute a different booted OS, IfW install, IfW/IfD/IfL, or backup disk/target disk. But it's a bit hit and miss to just try random fixes. Any suggestions what to look at, or what diagnostic info to get, first?

You could download "findlbaf" from the ftp site and find out which files are using the problem sectors. It may help in finding the cause.
ftp://ftp.terabyteunlimited.com/findlbaf.zip

If you're using RAID1, run a consistency check.

Otherwise, consider changing out the memory.

Of course run chkdsk/f on all drives as well.



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

Title says it all. I'm getting consistent errors, under both VSS and
PHYlock, with a complete backup. I'm not doing anything different from
usual.

IfW 2.83, clean install Win 8 Pro (tried to back up a pristine install
before use!), newish Intel/Asus platform, memtest86+, nothing unusual I'm
aware of. None the less, both VSS and PHYLock consistently report
byte-by-byte validation errors.

I'm used to relying on byte-for-byte for backup integrity for crucial
backups.While VSS has had verification issues in the past, usually one or
the other works, this is the first time both are failing me and no idea
what to do. I'd like to solve it rather than skip it since without
byte-by-byte there's no firm certainty the backup is exact. The disk is a
Samsung 840 Pro SSD with no SMART, reallocation, or other visible errors (as
one would expect for SSD, as firmware handles any), chkdsk /scan reports no
issues, the system isn't overclocked and temp is under 50 C, and driver is
Intel RST 12.8.0.1016.

logl:50 shows 2 partitions verifying before the 3rd (the OS) fails. The
error log reads:

[23/10/2013 06:51:23] Byte-for-Byte failure at LBA 76928 offset 0 (0)
[23/10/2013 06:51:23] DATA AS BACKED UP: (00000000060E0000)
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
[23/10/2013 06:51:23] DATA NOW ON DISK: (0000000002BE0000)
68 62 69 6E 00 30 00 00 00 10 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
D0 FF FF FF 57 00 69 00 6E 00 64 00 6F 00 77 00
73 00 20 00 42 00 6F 00 6F 00 74 00 20 00 4D 00
61 00 6E 00 61 00 67 00 65 00 72 00 00 00 00 00
A8 FF FF FF 6E 6B 20 00 4B 5F 65 0B 2A CF CE 01
03 00 00 00 38 2E 00 00 00 00 00 00 00 00 00 00
FF FF FF FF FF FF FF FF 01 00 00 00 D8 29 00 00
68 01 00 00 FF FF FF FF 00 00 00 00 00 00 00 00
0E 00 00 00 0C 00 00 00 02 00 00 00 08 00 00 00
31 32 30 30 30 30 30 35 E0 FF FF FF 76 6B 07 00
4E 00 00 00 70 32 00 00 01 00 00 00 01 00 30 30
45 6C 65 6D 65 6E 74 30 F8 FF FF FF A8 30 00 00
E0 FF FF FF 76 6B 07 00 0C 00 00 00 C0 2F 00 00
01 00 00 00 01 00 00 00 45 6C 65 6D 65 6E 74 00
A8 FF FF FF 6E 6B 20 00 4B 5F 65 0B 2A CF CE 01
02 00 00 00 38 2E 00 00 00 00 00 00 00 00 00 00
FF FF FF FF FF FF FF FF 01 00 00 00 D0 2F 00 00
68 01 00 00 FF FF FF FF 00 00 00 00 00 00 00 00
0E 00 00 00 50 00 00 00 03 00 00 00 08 00 00 00
31 34 30 30 30 30 30 36 E0 FF FF FF 76 6B 07 00
50 00 00 00 68 31 00 00 07 00 00 00 01 00 00 00
45 6C 65 6D 65 6E 74 00 A8 FF FF FF 7B 00 37 00
65 00 61 00 32 00 65 00 31 00 61 00 63 00 2D 00
32 00 65 00 36 00 31 00 2D 00 34 00 37 00 32 00
38 00 2D 00 61 00 61 00 61 00 33 00 2D 00 38 00
39 00 36 00 64 00 39 00 64 00 30 00 61 00 39 00
66 00 30 00 65 00 7D 00 00 00 00 00 00 00 00 00
E8 FF FF FF 6C 66 02 00 58 0E 00 00 44 65 73 63
E8 0E 00 00 45 6C 65 6D A8 FF FF FF 6E 6B 20 00
4B 5F 65 0B 2A CF CE 01 03 00 00 00 38 2E 00 00
00 00 00 00 00 00 00 00 FF FF FF FF FF FF FF FF
[23/10/2013 06:51:24] Operation Completed with Error Code 200
[23/10/2013 06:51:24] Byte-for-Byte comparison failed
[23/10/2013 07:11:02] Stop

The log shows a hint of a pattern from previous attempts:

[19/10/2013 17:31:28] Byte-for-Byte failure at LBA 36702538 offset 0 (21504)
[PHYLock]
[19/10/2013 18:56:24] Operation Completed with Error Code 0 [PHYLock]
[21/10/2013 00:05:07] Byte-for-Byte failure at LBA 41344 offset 0 (0)
[PHYLock]
[21/10/2013 02:54:46] Byte-for-Byte failure at LBA 32258242 offset 0 (33792)
[PHYLock]
[21/10/2013 03:03:19] Byte-for-Byte failure at LBA 76928 offset 0 (0) [VSS]
[21/10/2013 15:25:55] Byte-for-Byte failure at LBA 10654938 offset 0 (46080)
[PHYLock]
[23/10/2013 06:51:23] Byte-for-Byte failure at LBA 76928 offset 0 (0) [VSS
backing up to network share]
[23/10/2013 07:57:19] Byte-for-Byte failure at LBA 48986144 offset 0 (16384)
[PHYLock backing up to local disk - immediately afterwards with no reboot]
[23/10/2013 08:04:49] Byte-for-Byte failure at LBA 15734271 offset 0 (65024)
[identical rerun without reboot]
[23/10/2013 08:11:18] Byte-for-Byte failure at LBA 76928 offset 0 (0)
[identical rerun switching back to VSS + local disk]

Does the consistency of "76928" suggest it could be something quite specific
and not a random issue?

I haven't tried backing up a comparable second disk to see if that has the
same issue, or the same disk accessed as a data disk from a second boot, or
IfD/IfL based backup. I also haven't swapped cables over, although dodgy
cables would usually lead to BSOD which I'm not getting. So there are
options.

Ideally I do want the standard IfW backup to work and would like to solve
why it isn't.

I suppose the first thing is to identify what happens if I substitute a
different booted OS, IfW install, IfW/IfD/IfL, or backup disk/target disk.
But it's a bit hit and miss to just try random fixes. Any suggestions what
to look at, or what diagnostic info to get, first?

I have exactly the same issue. I just installed a Samsung 840 as the systems boot (C:) drive, and reassigned existing drives to other letters. I also installed IFW 2.84.

The IFW backup saves to a local drive on the machine (not over the network).

The backup ran successfully as a scheduled task until I installed the SSD. I am using "fsutil behavior set disabledeletenotify 1" before the backup and "fsutil behavior set disabledeletenotify 0" after the backup, so TRIM is turned off while the backup takes place.

The system has been rock-solid for years.
There must be something about SSDs that causes this issue?

My log (same as Stilez - backup up all zeros, data on disk is something else when verified)

[11/6/2013 6:57:48 AM] Byte-for-Byte failure at LBA 245016703 offset 0 (16384)
[11/6/2013 6:57:48 AM] DATA AS BACKED UP: (05364000)
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
-----snip-----
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
[11/6/2013 6:57:48 AM] DATA NOW ON DISK: (018A4000)
E0 81 BD 5A E2 CA A4 5D F6 10 B4 FA 2D 0B 66 60
C1 64 4B 66 E6 E6 E8 DA CA 56 D2 03 AF DF EE A8
A3 69 72 A5 D6 C7 0B 24 88 CE 30 A3 9C 60 D0 8A
FB BE 1D 1A E2 3C 90 24 01 92 05 8E CC 78 1E 0B
-----snip-----
A3 32 5A 92 35 F1 B4 DA F6 23 B1 B8 2E 76 61 AC
3E 08 06 93 EB 6F E9 2A 62 CF F1 5E 59 4A 9D D8
BB 32 15 0D 4E A9 2D B7 B8 F2 2A B7 29 A8 28 C3
[11/6/2013 6:57:48 AM] Deleting incomplete or failed backup.

Then VSS isn't protecting that area from changing or you need to run
chkdsk/f on your partition(s). If you want to find the file, use the
findlbaf to search based on the LBA. If it's TRIM related (doesn't look
like it since the data used to be zeros but now in use, not the other way
around), then you can use the disable trim option in your backup options.
Or for any case you can switch over to using PHYLock which protects
everything.

See http://www.terabyteunlimited.com/kb/article.php?id=151


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

I have exactly the same issue. I just installed a Samsung 840 as the systems
boot (C:) drive, and reassigned existing drives to other letters. I also
installed IFW 2.84.

The IFW backup saves to a local drive on the machine (not over the network).

The backup ran successfully as a scheduled task until I installed the SSD.
I am using "fsutil behavior set disabledeletenotify 1" before the backup and
"fsutil behavior set disabledeletenotify 0" after the backup, so TRIM is
turned off while the backup takes place.

The system has been rock-solid for years.
There must be something about SSDs that causes this issue?

My log (same as Stilez - backup up all zeros, data on disk is something else
when verified)

[11/6/2013 6:57:48 AM] Byte-for-Byte failure at LBA 245016703 offset 0
(16384)
[11/6/2013 6:57:48 AM] DATA AS BACKED UP: (05364000)
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
-----snip-----
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
[11/6/2013 6:57:48 AM] DATA NOW ON DISK: (018A4000)
E0 81 BD 5A E2 CA A4 5D F6 10 B4 FA 2D 0B 66 60
C1 64 4B 66 E6 E6 E8 DA CA 56 D2 03 AF DF EE A8
A3 69 72 A5 D6 C7 0B 24 88 CE 30 A3 9C 60 D0 8A
FB BE 1D 1A E2 3C 90 24 01 92 05 8E CC 78 1E 0B
-----snip-----
A3 32 5A 92 35 F1 B4 DA F6 23 B1 B8 2E 76 61 AC
3E 08 06 93 EB 6F E9 2A 62 CF F1 5E 59 4A 9D D8
BB 32 15 0D 4E A9 2D B7 B8 F2 2A B7 29 A8 28 C3
[11/6/2013 6:57:48 AM] Deleting incomplete or failed backup.

TeraByte Support wrote:
> Then VSS isn't protecting that area from changing or you need to run
> chkdsk/f on your partition(s).

I ran CHKDSK /F on all drives and found no problems.

If you want to find the file, use the
> findlbaf to search based on the LBA.

Will do - I never heard of findlbaf before now, but Google took me to a link in another thread here.

If it's TRIM related (doesn't look
> like it since the data used to be zeros but now in use, not the other way
> around), then you can use the disable trim option in your backup options.

I am using Disable Trim - I think. I have "fsutil behavior set disabledeletenotify 1" on the line before IMAGEW.EXE, and "fsutil behavior set disabledeletenotify 0" right afterwards. Correct?


> Or for any case you can switch over to using PHYLock which protects
> everything.

I was using PHYLOCK when this error started. I switched to VSS, but it did not help the problem.


>
> See http://www.terabyteunlimited.com/kb/article.php?id=151
>
>

I tried to use findlbaf. Here's my command, and the output:

C:\>findlbaf 0 100159223
Finding file using LBA 100159223 on drive 0...
Found Partition: MBR 0 238473MB (0001) HPFS/NTFS
Scanning files...
Unable to process file \$Secure
Unable to process file \$Extend\$ObjId
Unable to process file \$Extend\$Quota
Unable to process file \$Extend\$Reparse
Unable to process file \$Extend\$UsnJrnl


At this point it stops and waits indefinitely. (until I eventually hit CTRL-C).
For a 200G SSD drive with < 100G used, how long should findlbaf take? I gave it about 10 minutes.

Here are the LBA numbers where byte for byte failures are reported (on successive days)
6780450 245016703 181786143 100159223 71362095

It can take a while, when it's done it would print something about what it
found or not and go back to the prompt.

If PHYLock does it as well then sounds like you have a real issue. For one,
if you're using mirroring, run the verify and fix option in the RAID
software. That will fix it. Otherwise, you may have a real memory issue or
a firmware problem on the SSD drive. I'd start by checking the firmware,
then changing out the ram and checking it's timing in the BIOS.


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

I tried to use findlbaf. Here's my command, and the output:

C:\>findlbaf 0 100159223
Finding file using LBA 100159223 on drive 0...
Found Partition: MBR 0 238473MB (0001) HPFS/NTFS
Scanning files...
Unable to process file \$Secure
Unable to process file \$Extend\$ObjId
Unable to process file \$Extend\$Quota
Unable to process file \$Extend\$Reparse
Unable to process file \$Extend\$UsnJrnl


At this point it stops and waits indefinitely. (until I eventually hit
CTRL-C).
For a 200G SSD drive with < 100G used, how long should findlbaf take? I
gave it about 10 minutes.

Here are the LBA numbers where byte for byte failures are reported (on
successive days)
6780450 245016703 181786143 100159223 71362095

Looking back over IFW.LOG, I see that the line "Unable to lock volume \\?\Volume{74f2741b......" never appeared until I installed the SSD. Is it related to the SSD, or is it something new with 2.84?


The complete log is below.

[11/9/2013 10:21:44 AM] /b /un /d:?C: /f:H:\IMAGES\MARS\Auto7\MARS7C.TBI /max:640MiB /vb /mf /logl:50
[11/9/2013 10:21:44 AM] Image for Windows 2.84 (GUI)
[11/9/2013 10:21:44 AM] Starting ...
imagew.exe /b /un /d:w1@0x1 /f:"H:\IMAGES\MARS\Auto7\MARS7C" /max:640MiB /vb
[11/9/2013 10:21:45 AM] Unable to lock volume \\?\Volume{74f2741b-be6e-11de-9c43-806e6f6e6963} (C:)
[11/9/2013 10:21:45 AM] PHYLock is waiting for drive writing to stop ...
[11/9/2013 10:21:45 AM] PHYLOCK: Check Point - DLD
[11/9/2013 10:21:45 AM] PHYLOCK: Check Point - SCLN
[11/9/2013 10:21:45 AM] PHYLOCK: Check Point - BSFN
[11/9/2013 10:21:45 AM] PHYLOCK: Check Point - SFN:C:\PHYLOCK.SWP
[11/9/2013 10:21:45 AM] PHYLOCK: Check Point - GNR
[11/9/2013 10:21:45 AM] PHYLOCK: Check Point - NR:8881
[11/9/2013 10:21:45 AM] PHYLOCK: Check Point - SII VF
[11/9/2013 10:21:45 AM] PHYLOCK: Check Point - SSR
[11/9/2013 10:21:45 AM] PHYLOCK: Check Point - WLS
[11/9/2013 10:22:02 AM] PHYLOCK: Check Point - SH
[11/9/2013 10:22:02 AM] PHYLOCK: Check Point - ULV
[11/9/2013 10:22:02 AM] PHYLOCK: Check Point - CSF
[11/9/2013 10:22:02 AM] PHYLock using drive C:
[11/9/2013 10:22:02 AM] PHYLOCK: Check Point - EF
[11/9/2013 10:22:02 AM] PHYLOCK: Check Point - SWP:2147483648
[11/9/2013 10:22:02 AM] PHYLOCK: Check Point - FMLCN
[11/9/2013 10:22:02 AM] PHYLOCK: Check Point - SVCN:0 EC:1
[11/9/2013 10:22:02 AM] PHYLOCK: Check Point - CH
[11/9/2013 10:22:02 AM] PHYLOCK: Check Point - RQTFH
[11/9/2013 10:22:02 AM] PHYLOCK: Check Point - SWITCH
[11/9/2013 10:22:02 AM] PHYLOCK: Check Point - CU
[11/9/2013 10:22:02 AM] PHYLOCK: Check Point - CUC
[11/9/2013 10:22:02 AM] PHYLOCK: Check Point - EXIT
[11/9/2013 10:22:02 AM] PHYLock Started
[11/9/2013 10:22:02 AM] PHYLock Using Disk
[11/9/2013 10:22:02 AM] PHYLock version 11
[11/9/2013 10:22:02 AM] Backup: Drive 1 (C:) C-MARS-W7-ssd Partition (01) 238473 MiB HPFS/NTFS
[11/9/2013 10:22:02 AM] To: H:\IMAGES\MARS\Auto7\MARS7C.TBI
[11/9/2013 10:41:21 AM] INFO: Total Sectors:488392002 Total Allocated:154896024
[11/9/2013 10:41:21 AM] INFO: 142056400 Sector(s) backed up
[11/9/2013 10:41:21 AM] Validating: C-MARS-W7-ssd Partition (01) 238473 MiB HPFS/NTFS
[11/9/2013 10:41:21 AM] From: H:\IMAGES\MARS\Auto7\MARS7C.TBI
[11/9/2013 10:41:58 AM] Byte-for-Byte failure at LBA 6249215 offset 0 (8192)
[11/9/2013 10:41:58 AM] DATA AS BACKED UP: (04F82000)
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
----snip------
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
[11/9/2013 10:41:58 AM] DATA NOW ON DISK: (01B02000)
B7 7A C1 37 14 E1 0B 17 0D EA 1D 56 17 10 05 76
----snip------
0E 12 89 C2 43 7E 15 59 9D 7D F0 E5 F3 D0 67 08
[11/9/2013 10:41:58 AM] Deleting incomplete or failed backup.

there is more detail in 2.84, that would be normal.

do you have RAID 1 setup (mirroring) ?


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

Looking back over IFW.LOG, I see that the line "Unable to lock volume
\\?\Volume{74f2741b......" never appeared until I installed the SSD. Is it
related to the SSD, or is it something new with 2.84?


The complete log is below.

[11/9/2013 10:21:44 AM] /b /un /d:?C: /f:H:\IMAGES\MARS\Auto7\MARS7C.TBI
/max:640MiB /vb /mf /logl:50
[11/9/2013 10:21:44 AM] Image for Windows 2.84 (GUI)
[11/9/2013 10:21:44 AM] Starting ...
imagew.exe /b /un /d:w1@0x1 /f:"H:\IMAGES\MARS\Auto7\MARS7C" /max:640MiB /vb
[11/9/2013 10:21:45 AM] Unable to lock volume
\\?\Volume{74f2741b-be6e-11de-9c43-806e6f6e6963} (C:)
[11/9/2013 10:21:45 AM] PHYLock is waiting for drive writing to stop ...
[11/9/2013 10:21:45 AM] PHYLOCK: Check Point - DLD
[11/9/2013 10:21:45 AM] PHYLOCK: Check Point - SCLN
[11/9/2013 10:21:45 AM] PHYLOCK: Check Point - BSFN
[11/9/2013 10:21:45 AM] PHYLOCK: Check Point - SFN:C:\PHYLOCK.SWP
[11/9/2013 10:21:45 AM] PHYLOCK: Check Point - GNR
[11/9/2013 10:21:45 AM] PHYLOCK: Check Point - NR:8881
[11/9/2013 10:21:45 AM] PHYLOCK: Check Point - SII VF
[11/9/2013 10:21:45 AM] PHYLOCK: Check Point - SSR
[11/9/2013 10:21:45 AM] PHYLOCK: Check Point - WLS
[11/9/2013 10:22:02 AM] PHYLOCK: Check Point - SH
[11/9/2013 10:22:02 AM] PHYLOCK: Check Point - ULV
[11/9/2013 10:22:02 AM] PHYLOCK: Check Point - CSF
[11/9/2013 10:22:02 AM] PHYLock using drive C:
[11/9/2013 10:22:02 AM] PHYLOCK: Check Point - EF
[11/9/2013 10:22:02 AM] PHYLOCK: Check Point - SWP:2147483648
[11/9/2013 10:22:02 AM] PHYLOCK: Check Point - FMLCN
[11/9/2013 10:22:02 AM] PHYLOCK: Check Point - SVCN:0 EC:1
[11/9/2013 10:22:02 AM] PHYLOCK: Check Point - CH
[11/9/2013 10:22:02 AM] PHYLOCK: Check Point - RQTFH
[11/9/2013 10:22:02 AM] PHYLOCK: Check Point - SWITCH
[11/9/2013 10:22:02 AM] PHYLOCK: Check Point - CU
[11/9/2013 10:22:02 AM] PHYLOCK: Check Point - CUC
[11/9/2013 10:22:02 AM] PHYLOCK: Check Point - EXIT
[11/9/2013 10:22:02 AM] PHYLock Started
[11/9/2013 10:22:02 AM] PHYLock Using Disk
[11/9/2013 10:22:02 AM] PHYLock version 11
[11/9/2013 10:22:02 AM] Backup: Drive 1 (C:) C-MARS-W7-ssd Partition (01)
238473 MiB HPFS/NTFS
[11/9/2013 10:22:02 AM] To: H:\IMAGES\MARS\Auto7\MARS7C.TBI
[11/9/2013 10:41:21 AM] INFO: Total Sectors:488392002 Total
Allocated:154896024
[11/9/2013 10:41:21 AM] INFO: 142056400 Sector(s) backed up
[11/9/2013 10:41:21 AM] Validating: C-MARS-W7-ssd Partition (01) 238473 MiB
HPFS/NTFS
[11/9/2013 10:41:21 AM] From: H:\IMAGES\MARS\Auto7\MARS7C.TBI
[11/9/2013 10:41:58 AM] Byte-for-Byte failure at LBA 6249215 offset 0 (8192)
[11/9/2013 10:41:58 AM] DATA AS BACKED UP: (04F82000)
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
----snip------
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
[11/9/2013 10:41:58 AM] DATA NOW ON DISK: (01B02000)
B7 7A C1 37 14 E1 0B 17 0D EA 1D 56 17 10 05 76
----snip------
0E 12 89 C2 43 7E 15 59 9D 7D F0 E5 F3 D0 67 08
[11/9/2013 10:41:58 AM] Deleting incomplete or failed backup.