5
2
I'm archiving my media collection onto BD-R Dual Layer discs but keep getting the following IO errors at the end of the writing process (usually > 95% complete) :
:-[ WRITE@LBA=168e800h failed with SK=5h/END OF USER AREA ENCOUNTERED ON THIS TRACK]: Input/output error
:-( write failed: Input/output error
/dev/sr0: flushing cache
/dev/sr0: closing track
/dev/sr0: closing session
:-[ CLOSE SESSION failed with SK=5h/INVALID FIELD IN CDB]: Input/output error
/dev/sr0: reloading tray
My archiving process is detailed below:
dirsplit -m -s 46G /path/to/folder
> divides the original 61G folder into two folders whose size is <= 46GB. (Blu-Ray DL capacity being 50050629632 bytes == 46.61GB)genisoimage -ldots -allow-lowercase -allow-multidot -d -iso-level 4 -l -o /path/to/file.iso /path/to/folder
> generates an iso image which is compatible with OS X folder structure and filenames.growisofs -Z /dev/sr0=/path/to/file.iso
> writes iso image to Blu-ray disc.
The interesting thing is that I am able to successfully mount and read from the burned disc, even though growisofs failed to close the session. But I'm not sure wether all of the data was written to the disc.
I compared the md5 checksums of both the disc and the img file (thanks to a nifty tip from ewindisch over at Unix&Linux) but the two strings did not match. The output from dd said that the disc was 48GB in size rather than the 46GB image that was written to it.
However, running cmp -b -l /path/to/image.iso /dev/sr0
returned cmp: EOF on /dev/sr0
which means that the disc image is smaller than the iso file.
So as far as I can tell, growisofs
partially wrote the image to the disc but stopped short for some reason. Although I can mount the "incomplete" disc, I need to find why the burning stopped short.
Can anyone point me in the right direction? I can't find any records in /var/log/*
written by growisofs and can only go on the cryptic output at the top of this page.
This worked for me without needing
-overburn
on a single layer BD-R. K3B claimed the disc wasn't large enough even though it was. I'm guessing not leaving the 256 MB to spare was the reason. – user369450 – 2017-12-14T15:39:32.923Thanks for the tip @Beef, I'll let you know how it turns out after giving it another go. – danielcraigie – 2013-04-01T12:12:41.553