Page 1 of 1

Phylock error writing to DVD

Posted: Mon Dec 02, 2013 3:33 am
by borate
IFW verified that a W7 partition image to a hard disk was valid. I attempted to burn the same image to DVD set.
About ten minutes into the process it failed with a Phylock "increase cache" error.
Direct-to-DVD writes have always succeeded in the past without incident.

The same error has been seen before when writing to a hard disk, and is always resolved by reinstalling IFW cleanly.
In this case, that had already been done.

Bingburn - burning the same image to DVDs - was next. Yet, as you may note in another post, that failed as well.

The scorecard: one coaster for the direct-write attempt, and an incomplete set of three discs for the Bingburn try.
Suggestions welcomed on how either of these methods can be made to succeed.

Re: Phylock error writing to DVD

Posted: Mon Dec 02, 2013 6:32 am
by TeraByte Support
You can check the .log to get the error and adjust as needed...
http://www.terabyteunlimited.com/kb/article.php?id=551

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

IFW verified that a W7 partition image to a hard disk was valid. I
attempted to burn the same image to DVD set.
About ten minutes into the process it failed with a Phylock "increase cache"
error.
Direct-to-DVD writes have always succeeded in the past without incident.

The same error has been seen before when writing to a hard disk, and is
always resolved by reinstalling IFW cleanly.
In this case, that had already been done.

Bingburn - burning the same image to DVDs - was next. Yet, as you may note
in another post, that failed as well.

The scorecard: one coaster for the direct-write attempt, and an incomplete
set of three discs for the Bingburn try.
Suggestions welcomed on how either of these methods can be made to succeed.


Re: Phylock error writing to DVD

Posted: Mon Dec 02, 2013 3:30 pm
by borate
TeraByte Support wrote:
> You can check the .log to get the error and adjust as needed...
> http://www.terabyteunlimited.com/kb/article.php?id=551

The IFW.log did not contain info on that attempted transfer.

Retried the direct-to-DVD approach from another drive that contained more free
space than the drive used in the initial failed attempt (920 Gb vs. 67). Perhaps
that made a difference. The burn succeeded.