Unable to start PHYLock for drive C: You may need to reduce the cache size. [Solved]
Unable to start PHYLock for drive C: You may need to reduce the cache size. [Solved]
Out of nowhere, IFW 2.85 has started giving me issues with PHYLock failing to lock a drive for backup. It's been working fine for years. I read the bulletin about this and have been steadily decreasing /plcs from 16384. I'm down to 12288 and still getting this error. I added /logl:50 to try and obtain more info so someone here can tell me what the actual problem is. Please keep in mind that the system has been working fine with all of the arguments listed for years.
Windows XP system with 4GB of RAM, and 75 GB HD partition IFW is backing up.
Here's the log:
[4/28/22 9:05:30 PM] /b /uy /ui /err /d:1 /purge:-6 /plvolf /pldisk:1 /pldcs:4095 /plcs:12288 /plmem:0 /iobs:A /plmwt:1 /logl:50 /logfile:c:\documents and settings\xxxx\desktop\ifw.log /f:t:\Fullback\Server\C\$~MM$-$~DD$-$~YYYY$
[4/28/22 9:05:30 PM] Image for Windows 2.85 (GUI)
[4/28/22 9:05:30 PM] Starting ...
imagew.exe /b /uy /ui /d:w1 /f:"t:\Fullback\Server\C\$~MM$-$~DD$-$~YYYY$" /iobs:0 /err /purge:-6
[4/28/22 9:05:31 PM] Deleting t:\Fullback\Server\C\04-28-2022.TBI
[4/28/22 9:05:32 PM] Unable to lock volume \\?\Volume{cb169a90-cfce-11dc-8681-806d6172696f} (C:)
[4/28/22 9:05:32 PM] PHYLock is waiting for drive writing to stop ...
[4/28/22 9:05:32 PM] PHYLOCK: Check Point - DLD
[4/28/22 9:05:32 PM] PHYLOCK: Check Point - SCLN
[4/28/22 9:05:32 PM] PHYLOCK: Check Point - BSFN
[4/28/22 9:05:32 PM] PHYLOCK: Check Point - SFN:C:\PHYLOCK.SWP
[4/28/22 9:05:32 PM] PHYLOCK: Check Point - GNR
[4/28/22 9:05:36 PM] PHYLOCK: Check Point - NR:69934
[4/28/22 9:05:39 PM] PHYLOCK: Check Point - EXIT
[4/28/22 9:05:39 PM] PHYLock Failed to Start
[4/28/22 9:05:39 PM] Unable to start PHYLock for drive C:
You may need to reduce the cache size.
[4/28/22 9:05:39 PM] Locking Ignored
[4/28/22 9:05:45 PM] Backup: Drive 1 (C:) C_RAID_75GB Partition (01) 76317 MiB FAT-32
[4/28/22 9:05:45 PM] To: t:\Fullback\Server\C\04-28-2022.TBI
[4/28/22 10:37:56 PM] INFO: Total Sectors:156296322 Total Allocated:142306024
[4/28/22 10:37:56 PM] INFO: 133950184 Sector(s) backed up
[4/28/22 10:37:59 PM] Operation Completed with Error Code 0
Windows XP system with 4GB of RAM, and 75 GB HD partition IFW is backing up.
Here's the log:
[4/28/22 9:05:30 PM] /b /uy /ui /err /d:1 /purge:-6 /plvolf /pldisk:1 /pldcs:4095 /plcs:12288 /plmem:0 /iobs:A /plmwt:1 /logl:50 /logfile:c:\documents and settings\xxxx\desktop\ifw.log /f:t:\Fullback\Server\C\$~MM$-$~DD$-$~YYYY$
[4/28/22 9:05:30 PM] Image for Windows 2.85 (GUI)
[4/28/22 9:05:30 PM] Starting ...
imagew.exe /b /uy /ui /d:w1 /f:"t:\Fullback\Server\C\$~MM$-$~DD$-$~YYYY$" /iobs:0 /err /purge:-6
[4/28/22 9:05:31 PM] Deleting t:\Fullback\Server\C\04-28-2022.TBI
[4/28/22 9:05:32 PM] Unable to lock volume \\?\Volume{cb169a90-cfce-11dc-8681-806d6172696f} (C:)
[4/28/22 9:05:32 PM] PHYLock is waiting for drive writing to stop ...
[4/28/22 9:05:32 PM] PHYLOCK: Check Point - DLD
[4/28/22 9:05:32 PM] PHYLOCK: Check Point - SCLN
[4/28/22 9:05:32 PM] PHYLOCK: Check Point - BSFN
[4/28/22 9:05:32 PM] PHYLOCK: Check Point - SFN:C:\PHYLOCK.SWP
[4/28/22 9:05:32 PM] PHYLOCK: Check Point - GNR
[4/28/22 9:05:36 PM] PHYLOCK: Check Point - NR:69934
[4/28/22 9:05:39 PM] PHYLOCK: Check Point - EXIT
[4/28/22 9:05:39 PM] PHYLock Failed to Start
[4/28/22 9:05:39 PM] Unable to start PHYLock for drive C:
You may need to reduce the cache size.
[4/28/22 9:05:39 PM] Locking Ignored
[4/28/22 9:05:45 PM] Backup: Drive 1 (C:) C_RAID_75GB Partition (01) 76317 MiB FAT-32
[4/28/22 9:05:45 PM] To: t:\Fullback\Server\C\04-28-2022.TBI
[4/28/22 10:37:56 PM] INFO: Total Sectors:156296322 Total Allocated:142306024
[4/28/22 10:37:56 PM] INFO: 133950184 Sector(s) backed up
[4/28/22 10:37:59 PM] Operation Completed with Error Code 0
Last edited by Montclair on Mon Aug 22, 2022 6:59 am, edited 1 time in total.
Re: Unable to start PHYLock for drive C: You may need to reduce the cache size.
You should definitely consider upgrading to 2.99. I’m not sure if this particular is problem is fixed but I know that 2.99 fixes various issues.
Re: Unable to start PHYLock for drive C: You may need to reduce the cache size.
Thanks, but there's really no reason to do so on an older XP machine that was working fine for years with these parameters. Nothing has changed on the system in years, other than PHYLock now producing that error. Plus, that will break the UBCD boot disk we have with IFW loaded already and we'd have to redo that. Appreciate the reply, though.
-
- Posts: 3738
- Joined: Thu May 05, 2011 10:37 pm
Re: Unable to start PHYLock for drive C: You may need to reduce the cache size.
V2.x is no longer supported, some of this may still apply to it: https://www.terabyteunlimited.com/kb/kb ... ck-errors/
Re: Unable to start PHYLock for drive C: You may need to reduce the cache size.
Well you support PHYLock don't you? You can't tell me what the problem is here based on this?TeraByte Support wrote: ↑Sat Apr 30, 2022 5:42 am V2.x is no longer supported, some of this may still apply to it: https://www.terabyteunlimited.com/kb/kb ... ck-errors/
[4/28/22 9:05:32 PM] PHYLock is waiting for drive writing to stop ...
[4/28/22 9:05:32 PM] PHYLOCK: Check Point - DLD
[4/28/22 9:05:32 PM] PHYLOCK: Check Point - SCLN
[4/28/22 9:05:32 PM] PHYLOCK: Check Point - BSFN
[4/28/22 9:05:32 PM] PHYLOCK: Check Point - SFN:C:\PHYLOCK.SWP
[4/28/22 9:05:32 PM] PHYLOCK: Check Point - GNR
[4/28/22 9:05:36 PM] PHYLOCK: Check Point - NR:69934
[4/28/22 9:05:39 PM] PHYLOCK: Check Point - EXIT
[4/28/22 9:05:39 PM] PHYLock Failed to Start
Re: Unable to start PHYLock for drive C: You may need to reduce the cache size.
Could the HD be failing?
-
- Posts: 3738
- Joined: Thu May 05, 2011 10:37 pm
Re: Unable to start PHYLock for drive C: You may need to reduce the cache size.
That is an old version of PHYLock, there is a new version with V3.
-
- Posts: 795
- Joined: Fri Aug 12, 2011 5:58 pm
Re: Unable to start PHYLock for drive C: You may need to reduce the cache size.
I appreciate the frustration, but couldn't it just as validly be said that PHYLock hasn't changed on that system in years?Montclair wrote: ↑Fri Apr 29, 2022 10:03 pmThanks, but there's really no reason to do so on an older XP machine that was working fine for years with these parameters. Nothing has changed on the system in years, other than PHYLock now producing that error. Plus, that will break the UBCD boot disk we have with IFW loaded already and we'd have to redo that. Appreciate the reply, though.
-
- Posts: 3738
- Joined: Thu May 05, 2011 10:37 pm
Re: Unable to start PHYLock for drive C: You may need to reduce the cache size.
By the way, the legacy installer for V3 is needed to install on XP. It's on the downloads page for the drive image suite.
Re: Unable to start PHYLock for drive C: You may need to reduce the cache size.
Of course, therefore, why is it failing now when it hasn't for years and nothing has changed? The drive has no errors and isn't failing.Bob Coleman wrote: ↑Sun May 01, 2022 1:18 am I appreciate the frustration, but couldn't it just as validly be said that PHYLock hasn't changed on that system in years?
Obviously, something has changed to generate the error and unfortunately, despite providing the debug codes from the log, it looks as though I'm not going to get pointed in the correct direction other than being asked to upgrade. It's not the money to upgrade that's the problem, it's the hassle of having to rebuild the boot CD for this machine.