perpetual phylock lockout and new numbers
Posted: Thu Nov 11, 2021 10:05 pm
strange log messages:
EnvironmentW: u;uy;hash;comp:11;max:4GiB;logl:4;of:0x200;evlogl:4;logmax:10MiB;logfile:E:\IFD.LOG;sch:0@0x405:\;csig;v;wco
IMAGEW64.EXE /ue /copy /sd:3@0x5 /td:0@0x405 /nvn:"Win10(64)"
11/11/2021 03:10:28 PM] E:\Program Files (x86)\TeraByte Drive Image Backup and Restore Suite\TeraByte OSD Tool Suite Pro\win\IMAGEW64.EXE /ue /copy /sd:3@0x5 /td:0@0x405 /nvn:Win10(64)
[11/11/2021 03:10:28 PM] Image for Windows (x64) 3.47
[11/11/2021 03:10:28 PM] Starting ...
[11/11/2021 03:10:28 PM] IMAGEW64.EXE /copy /uy /u /sd:#0x607EE52B@0x5 /td:#0xD1EB1C88@0x405 /csig /wco /nvn:"Win10(64)"
[11/11/2021 03:10:28 PM] Windows 10 Pro 21H1 64-bit (10.0.19043.1.100)
[11/11/2021 03:10:31 PM] Unable to obtain a lock on drive
[11/11/2021 03:10:31 PM]
[11/11/2021 03:10:31 PM] The volume is in use by an application or Windows itself. Please close the offending application and retry or use a recovery boot disk. Visit www.terabyteunlimited.com/howto/ for details.
[11/11/2021 03:10:31 PM]
[11/11/2021 03:10:31 PM] You can also attempt to invalidate all opened handles and force a dismount by choosing ignore.
[11/11/2021 03:10:43 PM] Unable to obtain a lock on drive
these messages continue for 15 minutes then I cancelled it.
image version 3.47 seems to show some new and different information than before,
namely: sd:#0x607EE52B@0x5 /td:#0xD1EB1C88@0x405
When the command given to the program was: /sd:3@0x5 /td:0@0x405
1) any ideas how I can determine why phylock is not allowing access, and which volume is trying to be locked?
2) why the different (Drive/Partition Number vs NTSIG) source and dest numbers ?
It's just a little confusing to verify what is being backed up and if I convert to using NTSIG, will make the command line much longer.
3) Additionally the statement: You can also attempt to invalidate all opened handles and force a dismount by choosing ignore.
I did not see anywhere an option to IGNORE? Maybe I need to look closer.
thanks
EnvironmentW: u;uy;hash;comp:11;max:4GiB;logl:4;of:0x200;evlogl:4;logmax:10MiB;logfile:E:\IFD.LOG;sch:0@0x405:\;csig;v;wco
IMAGEW64.EXE /ue /copy /sd:3@0x5 /td:0@0x405 /nvn:"Win10(64)"
11/11/2021 03:10:28 PM] E:\Program Files (x86)\TeraByte Drive Image Backup and Restore Suite\TeraByte OSD Tool Suite Pro\win\IMAGEW64.EXE /ue /copy /sd:3@0x5 /td:0@0x405 /nvn:Win10(64)
[11/11/2021 03:10:28 PM] Image for Windows (x64) 3.47
[11/11/2021 03:10:28 PM] Starting ...
[11/11/2021 03:10:28 PM] IMAGEW64.EXE /copy /uy /u /sd:#0x607EE52B@0x5 /td:#0xD1EB1C88@0x405 /csig /wco /nvn:"Win10(64)"
[11/11/2021 03:10:28 PM] Windows 10 Pro 21H1 64-bit (10.0.19043.1.100)
[11/11/2021 03:10:31 PM] Unable to obtain a lock on drive
[11/11/2021 03:10:31 PM]
[11/11/2021 03:10:31 PM] The volume is in use by an application or Windows itself. Please close the offending application and retry or use a recovery boot disk. Visit www.terabyteunlimited.com/howto/ for details.
[11/11/2021 03:10:31 PM]
[11/11/2021 03:10:31 PM] You can also attempt to invalidate all opened handles and force a dismount by choosing ignore.
[11/11/2021 03:10:43 PM] Unable to obtain a lock on drive
these messages continue for 15 minutes then I cancelled it.
image version 3.47 seems to show some new and different information than before,
namely: sd:#0x607EE52B@0x5 /td:#0xD1EB1C88@0x405
When the command given to the program was: /sd:3@0x5 /td:0@0x405
1) any ideas how I can determine why phylock is not allowing access, and which volume is trying to be locked?
2) why the different (Drive/Partition Number vs NTSIG) source and dest numbers ?
It's just a little confusing to verify what is being backed up and if I convert to using NTSIG, will make the command line much longer.
3) Additionally the statement: You can also attempt to invalidate all opened handles and force a dismount by choosing ignore.
I did not see anywhere an option to IGNORE? Maybe I need to look closer.
thanks