Jump to content
  • 0
Sign in to follow this  
apricotandpearjam

Verification Fails On 80Gb M-Disc Burn

Question

Hey guys.

Ive had to throw away 2 expensive m-discs because the verification fails after burning the m-disc.

This means i cannot now read the data on the disc and it has to be thrown away.

 

Any ideas why this is happening?

 

Share this post


Link to post
Share on other sites

1 answer to this question

Recommended Posts

  • 0

I stopped using the built-in verification years ago as it would fail for good discs sometimes. I have never seen it alert me on a significant discrepancy with good quality discs.

Could it be that small changes are detected that are not significant, e.g. the normally invisible files that are related to the volume and/or Finder window display could get updated during the burning process, and those files may perhaps only differ in modification date: enough to detect a difference, but the produced disc is essentially the same as the source. I would think the burning app (Toast) should take care of that behind the scenes, but that's hard to verify for an end user, if it doesn't produce a list of exactly what is different.

If the disc is readable, perhaps you can verify manually with checksums? That would check just the data files that you care about.

Edited by theoldarchiver

Share this post


Link to post
Share on other sites

Please sign in to comment

You will be able to leave a comment after signing in



Sign In Now
Sign in to follow this  

×