TeraByte Unlimited

Logs show that Phylock gets a lock in less than a minute.

At HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Class\{4D36E967-E325-11CE-BFC1-08002BE10318}...

One entry in UpperFilters - phylock partmgr

One entry in LowerFilters - EhStorClass

Look at the differences and check the file its in, it may be a security file that is handled special. You can check the lba, if it's always the same or same file, it is something like that, otherwise if it moves around and changes, it's a problem with hardware. Using PHYLock backs up more than using VSS and the programs high reliability error detection will detect any problems whether hardware or something in Windows.

TeraByte Support wrote: Fri Jul 21, 2023 2:28 am You can check the lba, if it's always the same or same file, it is something like that, otherwise if it moves around and changes, it's a problem with hardware.

There is no LBA entry in ifw.log saying where it failed, even turned up to debug.

Error 94's...which I've seen reported here as far back as 2013.

I'm done with Phylock.

IFW using VSS, and two other imaging products using VSS, work fine.

What does your .log show? It gives you the LBA and if debug level high enough a comparison of the data.

It giving the error means it's doing its job.

The log level was set to 0x9 -

0x1 – Error messages only
0x2 – Include warning messages
0x3 – Include status messages
0x4 – Include information messages
0x9 – Include debugging information

As mentioned, no LBA was logged.

I would say it isn't doing its job if all it logs is Error Code 94.