TeraByte Unlimited

When creating an image, IFW has occasionally thrown an error that prompts to increase cache size.
A clean install has always corrected that; no cache size change required. Until now...

Using 2.87, despite a clean install, it was necessary to increase cache size to write on the W7 drive.
But no increase was needed for the alternative 8.1 IFW install: another drive - same machine.

Why? No intentional/known changes have been made to either O/S.

Look in the ifw.log for the phylock error then see
http://www.terabyteunlimited.com/kb/article.php?id=551


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

When creating an image, IFW has occasionally thrown an error that prompts to
increase cache size.
A clean install has always corrected that; no cache size change required.
Until now...

Using 2.87, despite a clean install, it was necessary to increase cache size
to write on the W7 drive.
But no increase was needed for the alternative 8.1 IFW install: another
drive - same machine.

Why? No intentional/known changes have been made to either O/S.

TeraByte Support wrote:
> Look in the ifw.log for the phylock error then see
> http://www.terabyteunlimited.com/kb/article.php?id=551

[2/15/2014 8:18:54 AM] PHYLock Error 0002h

Confirms a RAM cache error, but sheds little light on why - for the first time.

I increased the sizes when I installed IFW and don't have problems.

Don't know why yours is intermittent.
Mary

On 2/17/2014 3:50 PM, borate wrote:
> TeraByte Support wrote:
>> Look in the ifw.log for the phylock error then see
>>
>
> [
> http://www.terabyteunlimited.com/kb/article.php?id=551
> ](http://www.terabyteunlimited.com/kb/article.php?id=551)
>
> [2/15/2014 8:18:54 AM] PHYLock Error 0002h
>
> Confirms a RAM cache error, but sheds little light on why - for the first time.
>
>

what's in your log file... run it at /logl:50 for more details. If you're
using RAM mode for the main in use windows partition, you'll probably always
run out of cache space, at least the ntfs log file will constantly be
changing.

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

TeraByte Support wrote:
> Look in the ifw.log for the phylock error then see
>

[
http://www.terabyteunlimited.com/kb/article.php?id=551
](http://www.terabyteunlimited.com/kb/article.php?id=551)

[2/15/2014 8:18:54 AM] PHYLock Error 0002h

Confirms a RAM cache error, but sheds little light on why - for the first
time.

TeraByte Support wrote:
> what's in your log file... run it at /logl:50 for more details. If you're
> using RAM mode for the main in use windows partition, you'll probably
> always run out of cache space, at least the ntfs log file will constantly be changing.

NEVER changed cache size and never a problem over the past decade - on either O/S.
Don't mind upping cache size, just odd that it suddenly requires it.

[2/15/2014 8:16:16 AM] Image for Windows 2.87 (GUI)
[2/15/2014 8:16:16 AM] Starting ...
imagew.exe /b /d:w0@0x2 /f:"K:\IFW\W7_64_S_Logitech" /v
[2/15/2014 8:16:16 AM] PHYLock is waiting for drive writing to stop ...
[2/15/2014 8:16:24 AM] PHYLock using drive C:
[2/15/2014 8:16:24 AM] PHYLock Started
[2/15/2014 8:16:24 AM] PHYLock Using Disk
[2/15/2014 8:16:24 AM] PHYLock version 11
[2/15/2014 8:16:24 AM] Backup: Drive 0 (C:) MBR 1 Partition (02) 114371 MiB HPFS/NTFS
[2/15/2014 8:16:24 AM] To: K:\IFW\W7_64_S_Logitech.TBI
[2/15/2014 8:18:54 AM] PHYLock Error 0002h
[2/15/2014 8:18:54 AM] INFO: Total Sectors:234231808 Total Allocated:94021328
[2/15/2014 8:18:55 AM] Deleting incomplete or failed backup.
[2/15/2014 8:18:55 AM] Deleting K:\IFW\W7_64_S_Logitech.TBI
[2/15/2014 8:18:56 AM] Operation Completed with Error Code 204
[2/15/2014 8:18:56 AM] PHYLock failed to cache all changes. Please increase the cache size in settings.
[2/15/2014 8:20:36 AM] Stop

No Norton installed here.

don't forget to run a chkdsk /f on the various source partitions as well and
may want to scan the surface with manufacturers utility in case delay
writing is causing it.

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

TeraByte Support wrote:
> what's in your log file... run it at /logl:50 for more details. If you're
> using RAM mode for the main in use windows partition, you'll probably
> always run out of cache space, at least the ntfs log file will constantly
> be changing.

NEVER changed cache size and never a problem over the past decade - on
either O/S.
Don't mind upping cache size, just odd that it suddenly requires it.

[2/15/2014 8:16:16 AM] Image for Windows 2.87 (GUI)
[2/15/2014 8:16:16 AM] Starting ...
imagew.exe /b /d:w0@0x2 /f:"K:\IFW\W7_64_S_Logitech" /v
[2/15/2014 8:16:16 AM] PHYLock is waiting for drive writing to stop ...
[2/15/2014 8:16:24 AM] PHYLock using drive C:
[2/15/2014 8:16:24 AM] PHYLock Started
[2/15/2014 8:16:24 AM] PHYLock Using Disk
[2/15/2014 8:16:24 AM] PHYLock version 11
[2/15/2014 8:16:24 AM] Backup: Drive 0 (C:) MBR 1 Partition (02) 114371 MiB
HPFS/NTFS
[2/15/2014 8:16:24 AM] To: K:\IFW\W7_64_S_Logitech.TBI
[2/15/2014 8:18:54 AM] PHYLock Error 0002h
[2/15/2014 8:18:54 AM] INFO: Total Sectors:234231808 Total
Allocated:94021328
[2/15/2014 8:18:55 AM] Deleting incomplete or failed backup.
[2/15/2014 8:18:55 AM] Deleting K:\IFW\W7_64_S_Logitech.TBI
[2/15/2014 8:18:56 AM] Operation Completed with Error Code 204
[2/15/2014 8:18:56 AM] PHYLock failed to cache all changes. Please increase
the cache size in settings.
[2/15/2014 8:20:36 AM] Stop

No Norton installed here.