PHYLOCK no longer works with v3.13 and 3.14

User discussion and information resource forum for Image products.

PHYLOCK no longer works with v3.13 and 3.14

Postby timg11 » Sat Dec 09, 2017 10:13 am

My last successful image was with 3.11. Here is the log:

[11/29/2017 6:14:43 AM] C:\Program Files (x86)\TeraByte\imagew64.exe /b /un /d:?C: /f:S:\IMAGES\MARS\Auto\MARS_W10.TBI /max:640MiB /vb /mf /logl:50
[11/29/2017 6:14:43 AM] Image for Windows (x64) 3.11
[11/29/2017 6:14:43 AM] Starting ...
imagew64.exe /b /un /d:w2@0x4 /f:"S:\IMAGES\MARS\Auto\MARS_W10" /max:640MiB /vb
/logl:50 /plur /pldcs:2KiB /plcs:16KiB
[11/29/2017 6:14:44 AM] Unable to lock volume \\?\Volume{0f9cc681-18ef-4892-98e1-0a03a8f0832f} (C:)
[11/29/2017 6:14:44 AM] PHYLock is waiting for drive writing to stop ...
[11/29/2017 6:14:44 AM] PHYLOCK: Check Point - DLD
[11/29/2017 6:14:44 AM] PHYLOCK: Check Point - SCLN
[11/29/2017 6:14:44 AM] PHYLOCK: Check Point - BSFN
[11/29/2017 6:14:44 AM] PHYLOCK: Check Point - SFN:C:\PHYLOCK.SWP
[11/29/2017 6:14:44 AM] PHYLOCK: Check Point - GNR
[11/29/2017 6:14:44 AM] PHYLOCK: Check Point - NR:15394
[11/29/2017 6:14:44 AM] PHYLOCK: Check Point - SII VF
[11/29/2017 6:14:44 AM] PHYLOCK: Check Point - SSR
[11/29/2017 6:14:44 AM] PHYLOCK: Check Point - WLS
[11/29/2017 6:15:44 AM] PHYLOCK: Check Point - SH
[11/29/2017 6:15:44 AM] PHYLOCK: Check Point - ULV
[11/29/2017 6:15:44 AM] PHYLOCK: Check Point - CSF
[11/29/2017 6:15:44 AM] PHYLock using drive C:
[11/29/2017 6:15:44 AM] PHYLOCK: Check Point - EF
[11/29/2017 6:15:44 AM] PHYLOCK: Check Point - SWP:2147483648
[11/29/2017 6:15:44 AM] PHYLOCK: Check Point - FMLCN
[11/29/2017 6:15:44 AM] PHYLOCK: Check Point - SVCN:0 EC:1
[11/29/2017 6:15:44 AM] PHYLOCK: Check Point - CH
[11/29/2017 6:15:44 AM] PHYLOCK: Check Point - RQTFH
[11/29/2017 6:15:44 AM] PHYLOCK: Check Point - SWITCH
[11/29/2017 6:15:44 AM] PHYLOCK: Check Point - CU
[11/29/2017 6:15:44 AM] PHYLOCK: Check Point - CUC
[11/29/2017 6:15:44 AM] PHYLOCK: Check Point - EXIT
[11/29/2017 6:15:44 AM] PHYLock Started
[11/29/2017 6:15:44 AM] PHYLock Using Disk
[11/29/2017 6:15:44 AM] PHYLock version 14
[11/29/2017 6:15:44 AM] Backup: Drive 2 (C:) Basic data partition Partition (04) 243632 MiB NTFS
[11/29/2017 6:15:44 AM] To: S:\IMAGES\MARS\Auto\MARS_W10.TBI
[11/29/2017 6:36:33 AM] INFO: Total Sectors:498958336 Total Allocated:295597968
[11/29/2017 6:36:33 AM] INFO: 277264352 Sector(s) backed up
[11/29/2017 6:36:33 AM] Time Elapsed: 0:00:20:49
[11/29/2017 6:36:39 AM] Validating: Basic data partition Partition (04) 243632 MiB NTFS
[11/29/2017 6:36:39 AM] From: S:\IMAGES\MARS\Auto\MARS_W10.TBI
[11/29/2017 7:07:48 AM] Time Elapsed: 0:00:31:09

I missed 3.12, but updated to 3.13 on 12/2. On 12/3, the next time IFW auto-ran, my image failed, with this in the log:

[12/3/2017 6:35:01 AM] C:\Program Files (x86)\TeraByte\imagew64.exe /b /un /d:?C: /f:S:\IMAGES\MARS\Auto\MARS_W10.TBI /max:640MiB /vb /mf /logl:50
[12/3/2017 6:35:01 AM] Image for Windows (x64) 3.13
[12/3/2017 6:35:01 AM] Starting ...
imagew64.exe /b /un /d:w2@0x4 /f:"S:\IMAGES\MARS\Auto\MARS_W10" /max:640MiB /vb
/logl:50 /plur /pldcs:2KiB /plcs:16KiB
[12/3/2017 6:35:02 AM] Unable to lock volume \\?\Volume{0f9cc681-18ef-4892-98e1-0a03a8f0832f} (C:)
[12/3/2017 6:35:02 AM] PHYLock is waiting for drive writing to stop ...
[12/3/2017 6:35:02 AM] PHYLOCK: Check Point - DLD
[12/3/2017 6:35:02 AM] PHYLOCK: Check Point - SCLN
[12/3/2017 6:35:02 AM] PHYLOCK: Check Point - BSFN
[12/3/2017 6:35:02 AM] PHYLOCK: Check Point - SFN:
[12/3/2017 6:35:02 AM] PHYLOCK: Check Point - GNR
[12/3/2017 6:35:02 AM] PHYLOCK: Check Point - NR:29327
[12/3/2017 6:35:02 AM] PHYLOCK: Check Point - SII VF
[12/3/2017 6:35:02 AM] PHYLOCK: Check Point - SSR
[12/3/2017 6:35:02 AM] PHYLOCK: Check Point - WLS
[12/3/2017 6:35:40 AM] PHYLOCK: Check Point - SH
[12/3/2017 6:35:40 AM] PHYLOCK: Check Point - CUC
[12/3/2017 6:35:40 AM] PHYLOCK: Check Point - EXIT
[12/3/2017 6:35:40 AM] PHYLock Started
[12/3/2017 6:35:40 AM] PHYLock Using RAM
[12/3/2017 6:35:40 AM] PHYLock version 14
[12/3/2017 6:35:40 AM] Backup: Drive 2 (C:) Basic data partition Partition (04) 243632 MiB NTFS
[12/3/2017 6:35:40 AM] To: S:\IMAGES\MARS\Auto\MARS_W10.TBI
[12/3/2017 6:55:06 AM] PHYLock Error 0003h
[12/3/2017 6:55:06 AM] INFO: Total Sectors:498958336 Total Allocated:301967552
[12/3/2017 6:55:06 AM] Time Elapsed: 0:00:19:26
[12/3/2017 6:55:06 AM] Deleting incomplete or failed backup.
[12/3/2017 6:55:07 AM] Deleting S:\IMAGES\MARS\Auto\MARS_W10.1
[12/3/2017 6:55:07 AM] Deleting S:\IMAGES\MARS\Auto\MARS_W10.10
...snip...
[12/3/2017 6:55:09 AM] Deleting S:\IMAGES\MARS\Auto\MARS_W10.TBI
[12/3/2017 6:55:09 AM] Time Elapsed: 0:00:20:08
[12/3/2017 6:55:09 AM] Operation Completed with Error Code 204
[12/3/2017 6:55:09 AM] PHYLock failed to cache all changes. Please increase the cache size in settings.
[12/3/2017 6:55:09 AM] Stop


Since then I have increased PHYlock RAM size, disk size, and the "memory" slider, several times, but I always get the same failure.
RAM size is now 32768, Disk Size is 4096, and "memory" slider is one step right of center.
Nothing has changed on the system other than updating IFW.
I have done a CHKDSK /F and the volume is clean.

I observe that with 3.11, I see "PHYLOCK: Check Point - SFN:C:\PHYLOCK.SWP" and "PHYLock Using Disk"
With 3.13 (and 3.14) I see "PHYLock Using RAM" and it fails every time.
My RAM size has not changed. My disk is a Samsung NVMe SSD-950, and has about 90G of free space.

The "Use disk storage" checkbox in PHYLOCK settings is still checked.
Is there a way to force use of disk storage for PHYLOCK? Why would PHYLOCK have lost the ability to correctly select the workable storage option?
timg11
 
Posts: 170
Joined: Sun Oct 02, 2011 9:31 am

Re: PHYLOCK no longer works with v3.13 and 3.14

Postby TeraByte Support » Sat Dec 09, 2017 12:49 pm

Put everything back to defaults.

Then run chkdsk /f on all of your drive letters. Do C: last since it will
need to be scheduled for next reboot, then reboot to have it complete it.

If everything at defaults and still using ram, uninstall IFW and reinstall
it.

Also, you need to ensure partmgr is part of upperfilters under
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Class\{4D36E967-E325-11CE-BFC1-08002BE10318}
or it can cause issues in the system in general that prevents certain things
from being able to find drive letters properly.





"timg11" wrote in message news:14449@public.image...

My last successful image was with 3.11. Here is the log:

[11/29/2017 6:14:43 AM] C:\Program Files (x86)\TeraByte\imagew64.exe /b /un
/d:?C: /f:S:\IMAGES\MARS\Auto\MARS_W10.TBI /max:640MiB /vb /mf /logl:50
[11/29/2017 6:14:43 AM] Image for Windows (x64) 3.11
[11/29/2017 6:14:43 AM] Starting ...
imagew64.exe /b /un /d:w2@0x4 /f:"S:\IMAGES\MARS\Auto\MARS_W10" /max:640MiB
/vb
/logl:50 /plur /pldcs:2KiB /plcs:16KiB
[11/29/2017 6:14:44 AM] Unable to lock volume
\\?\Volume{0f9cc681-18ef-4892-98e1-0a03a8f0832f} (C:)
[11/29/2017 6:14:44 AM] PHYLock is waiting for drive writing to stop ...
[11/29/2017 6:14:44 AM] PHYLOCK: Check Point - DLD
[11/29/2017 6:14:44 AM] PHYLOCK: Check Point - SCLN
[11/29/2017 6:14:44 AM] PHYLOCK: Check Point - BSFN
[11/29/2017 6:14:44 AM] PHYLOCK: Check Point - SFN:C:\PHYLOCK.SWP
[11/29/2017 6:14:44 AM] PHYLOCK: Check Point - GNR
[11/29/2017 6:14:44 AM] PHYLOCK: Check Point - NR:15394
[11/29/2017 6:14:44 AM] PHYLOCK: Check Point - SII VF
[11/29/2017 6:14:44 AM] PHYLOCK: Check Point - SSR
[11/29/2017 6:14:44 AM] PHYLOCK: Check Point - WLS
[11/29/2017 6:15:44 AM] PHYLOCK: Check Point - SH
[11/29/2017 6:15:44 AM] PHYLOCK: Check Point - ULV
[11/29/2017 6:15:44 AM] PHYLOCK: Check Point - CSF
[11/29/2017 6:15:44 AM] PHYLock using drive C:
[11/29/2017 6:15:44 AM] PHYLOCK: Check Point - EF
[11/29/2017 6:15:44 AM] PHYLOCK: Check Point - SWP:2147483648
[11/29/2017 6:15:44 AM] PHYLOCK: Check Point - FMLCN
[11/29/2017 6:15:44 AM] PHYLOCK: Check Point - SVCN:0 EC:1
[11/29/2017 6:15:44 AM] PHYLOCK: Check Point - CH
[11/29/2017 6:15:44 AM] PHYLOCK: Check Point - RQTFH
[11/29/2017 6:15:44 AM] PHYLOCK: Check Point - SWITCH
[11/29/2017 6:15:44 AM] PHYLOCK: Check Point - CU
[11/29/2017 6:15:44 AM] PHYLOCK: Check Point - CUC
[11/29/2017 6:15:44 AM] PHYLOCK: Check Point - EXIT
[11/29/2017 6:15:44 AM] PHYLock Started
[11/29/2017 6:15:44 AM] PHYLock Using Disk
[11/29/2017 6:15:44 AM] PHYLock version 14
[11/29/2017 6:15:44 AM] Backup: Drive 2 (C:) Basic data partition Partition
(04) 243632 MiB NTFS
[11/29/2017 6:15:44 AM] To: S:\IMAGES\MARS\Auto\MARS_W10.TBI
[11/29/2017 6:36:33 AM] INFO: Total Sectors:498958336 Total
Allocated:295597968
[11/29/2017 6:36:33 AM] INFO: 277264352 Sector(s) backed up
[11/29/2017 6:36:33 AM] Time Elapsed: 0:00:20:49
[11/29/2017 6:36:39 AM] Validating: Basic data partition Partition (04)
243632 MiB NTFS
[11/29/2017 6:36:39 AM] From: S:\IMAGES\MARS\Auto\MARS_W10.TBI
[11/29/2017 7:07:48 AM] Time Elapsed: 0:00:31:09

I missed 3.12, but updated to 3.13 on 12/2. On 12/3, the next time IFW
auto-ran, my image failed, with this in the log:

[12/3/2017 6:35:01 AM] C:\Program Files (x86)\TeraByte\imagew64.exe /b /un
/d:?C: /f:S:\IMAGES\MARS\Auto\MARS_W10.TBI /max:640MiB /vb /mf /logl:50
[12/3/2017 6:35:01 AM] Image for Windows (x64) 3.13
[12/3/2017 6:35:01 AM] Starting ...
imagew64.exe /b /un /d:w2@0x4 /f:"S:\IMAGES\MARS\Auto\MARS_W10" /max:640MiB
/vb
/logl:50 /plur /pldcs:2KiB /plcs:16KiB
[12/3/2017 6:35:02 AM] Unable to lock volume
\\?\Volume{0f9cc681-18ef-4892-98e1-0a03a8f0832f} (C:)
[12/3/2017 6:35:02 AM] PHYLock is waiting for drive writing to stop ...
[12/3/2017 6:35:02 AM] PHYLOCK: Check Point - DLD
[12/3/2017 6:35:02 AM] PHYLOCK: Check Point - SCLN
[12/3/2017 6:35:02 AM] PHYLOCK: Check Point - BSFN
[12/3/2017 6:35:02 AM] PHYLOCK: Check Point - SFN:
[12/3/2017 6:35:02 AM] PHYLOCK: Check Point - GNR
[12/3/2017 6:35:02 AM] PHYLOCK: Check Point - NR:29327
[12/3/2017 6:35:02 AM] PHYLOCK: Check Point - SII VF
[12/3/2017 6:35:02 AM] PHYLOCK: Check Point - SSR
[12/3/2017 6:35:02 AM] PHYLOCK: Check Point - WLS
[12/3/2017 6:35:40 AM] PHYLOCK: Check Point - SH
[12/3/2017 6:35:40 AM] PHYLOCK: Check Point - CUC
[12/3/2017 6:35:40 AM] PHYLOCK: Check Point - EXIT
[12/3/2017 6:35:40 AM] PHYLock Started
[12/3/2017 6:35:40 AM] PHYLock Using RAM
[12/3/2017 6:35:40 AM] PHYLock version 14
[12/3/2017 6:35:40 AM] Backup: Drive 2 (C:) Basic data partition Partition
(04) 243632 MiB NTFS
[12/3/2017 6:35:40 AM] To: S:\IMAGES\MARS\Auto\MARS_W10.TBI
[12/3/2017 6:55:06 AM] PHYLock Error 0003h
[12/3/2017 6:55:06 AM] INFO: Total Sectors:498958336 Total
Allocated:301967552
[12/3/2017 6:55:06 AM] Time Elapsed: 0:00:19:26
[12/3/2017 6:55:06 AM] Deleting incomplete or failed backup.
[12/3/2017 6:55:07 AM] Deleting S:\IMAGES\MARS\Auto\MARS_W10.1
[12/3/2017 6:55:07 AM] Deleting S:\IMAGES\MARS\Auto\MARS_W10.10
....snip...
[12/3/2017 6:55:09 AM] Deleting S:\IMAGES\MARS\Auto\MARS_W10.TBI
[12/3/2017 6:55:09 AM] Time Elapsed: 0:00:20:08
[12/3/2017 6:55:09 AM] Operation Completed with Error Code 204
[12/3/2017 6:55:09 AM] PHYLock failed to cache all changes. Please increase
the cache size in settings.
[12/3/2017 6:55:09 AM] Stop


Since then I have increased PHYlock RAM size, disk size, and the "memory"
slider, several times, but I always get the same failure.
RAM size is now 32768, Disk Size is 4096, and "memory" slider is one step
right of center.
Nothing has changed on the system other than updating IFW.
I have done a CHKDSK /F and the volume is clean.

I observe that with 3.11, I see "PHYLOCK: Check Point - SFN:C:\PHYLOCK.SWP"
and "PHYLock Using Disk"
With 3.13 (and 3.14) I see "PHYLock Using RAM" and it fails every time.
My RAM size has not changed. My disk is a Samsung NVMe SSD-950, and has
about 90G of free space.

The "Use disk storage" checkbox in PHYLOCK settings is still checked.
Is there a way to force use of disk storage for PHYLOCK? Why would PHYLOCK
have lost the ability to correctly select the workable storage option?

TeraByte Support
 
Posts: 2422
Joined: Thu May 05, 2011 3:37 pm

Re: PHYLOCK no longer works with v3.13 and 3.14

Postby timg11 » Sat Dec 09, 2017 5:04 pm

TeraByte Support wrote:
> Put everything back to defaults.

What are the defaults? The PHYlock/VSS tab does not have a "restore defaults" button. Would the uninstall / reinstall process reset to defaults?

>
> Then run chkdsk /f on all of your drive letters. Do C: last since it will
> need to be scheduled for next reboot, then reboot to have it complete it.
>

So even though IFW is imaging drive C: and writing to a network drive, it could still be affected by a disk issue on local drive H: ???
I already did a CHKDSK /F on drive C: and nothing was found, but I can do the other drives as well. Good practice once in a while.
I have a CHKDSK /SCAN in the scheduled task that runs IFW. If it detects an issues, it exits and reports the problem.
Should I add a CHKDKSK for all local drives that are not imaged?



> If everything at defaults and still using ram, uninstall IFW and reinstall
>
> it.
>
> Also, you need to ensure partmgr is part of upperfilters under
>
> HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Class\{4D36E967-E325-11CE-BFC1-08002BE10318}
>
> or it can cause issues in the system in general that prevents certain
> things
> from being able to find drive letters properly.
>

UpperFilters contains:
phylock
partmgr
timg11
 
Posts: 170
Joined: Sun Oct 02, 2011 9:31 am

Re: PHYLOCK no longer works with v3.13 and 3.14

Postby TeraByte Support » Sun Dec 10, 2017 10:06 am

If I recall, the manual has a picture with the defaults.

How many partitions are on the source drive and what are the file system
types and free space on each one? A pic from Computer Management should
give that (in the listview section above the graphic layout).

It picks the one with the most free space, if no drive letter, I can see it
would end up not having a file name.

"timg11" wrote in message news:14455@public.image...

TeraByte Support wrote:
> Put everything back to defaults.

What are the defaults? The PHYlock/VSS tab does not have a "restore
defaults" button. Would the uninstall / reinstall process reset to
defaults?

>

TeraByte Support
 
Posts: 2422
Joined: Thu May 05, 2011 3:37 pm

Re: PHYLOCK no longer works with v3.13 and 3.14

Postby Bob Coleman » Sun Dec 10, 2017 11:11 am

Regarding restoring PHYLock settings to defaults, would removing all PHYLock related entries from ifw,ini do it?
Bob Coleman
 
Posts: 442
Joined: Fri Aug 12, 2011 10:58 am

Re: PHYLOCK no longer works with v3.13 and 3.14

Postby TeraByte Support » Sun Dec 10, 2017 2:11 pm

the /plur option is on so it's the registry entries that would need to be
removed as well.

A uninstall/reinstall should do it as well, no need to reboot if same
version if though it will ask (only does for phylock driver updates - which
also occurs on daylight saving time changes).

"Bob Coleman" wrote in message news:14457@public.image...

Regarding restoring PHYLock settings to defaults, would removing all PHYLock
related entries from ifw,ini do it?

TeraByte Support
 
Posts: 2422
Joined: Thu May 05, 2011 3:37 pm

Re: PHYLOCK no longer works with v3.13 and 3.14

Postby timg11 » Thu Dec 14, 2017 4:39 pm

I got it working again by enabling VSS. I'm trying to remember - is there any "downside" with VSS, or should I just leave it that way?

I was trying to figure out if the sudden failure of PHYLOCK with no changes to the drive or computer (other than updating to IFW 3.13) was just a random co-incidence, triggered by a Windows Update, or was actually caused by a change in 3.13? The drive topology, system configuration, etc has not changed for over a year.
timg11
 
Posts: 170
Joined: Sun Oct 02, 2011 9:31 am


Return to Image for DOS/Linux/Windows