Hi,
> libburn : SORRY : SCSI error on read_10(297920,32): [3 11 05] Medium error.
> L-EC uncorrectable error.
That's bad news for your hardware. A data chunk of 64 KiB did not match
its inner checksums. So the drive refuses to hand out these 64 KiB.
You would have to try the media in other drives to get an impression
whether it's the media or your drive which are to blame.
> Media checks : lba , size , quality
> Media region : 297824 , 32 , - unreadable
> Media region : 297920 , 32 , - unreadable
> Media region : 298048 , 32 , - unreadable
Just three unreadable chunks, quite near together. Not even 600 MiB away
from the medium start.
If it was necessary you could copy the damaged image to a data file on
hard disk (e.g. $HOME/bdre.img):
xorriso -indev /dev/sr0 -check_media data_to="$HOME"/bdre.img --
You could even try several times or on several BD drives by having a
file bdre.map which records which blocks were read successfully and
which are yet missing in bdre.img:
xorriso \
-indev /dev/sr0 \
-check_media data_to="$HOME"/bdre.img sector_map="$HOME"/bdre.map --
The already successfully read blocks will not be tried again.
One may carry medium, bdre.img, and bdre.map from computer to computer
in order to find a drive which can read the missing blocks.
The fact that command -indev did work shows that the directory tree is
not hit by the bad spots.
So, perfectly restored or not, the file bdre.img should be mountable
and the damaged tar archive should be readable. Dunno what tar will do
when it encounters 64 KiB of zeros in the middle of an archive where it
would expect some of its metadata.
This is a good opportunity to practice for a case of media which are ok
after recording but turn out to be slightly rotten much later.
------------------------------------------------------------------------
But well, this is also the classic situation for Defect Management:
Some few bad spots on a large, elsewise good medium.
So you should try with one of the problematic media whether it works
slowly but correctly if you set
-stream_recording "off"
It might be that Defect Management goes mad and lets the drive gnaw
endlessly not only on the bad spots above, but also on many other spots.
Or it might be that you have a rare case where Defect Management fulfills
the hopes which it stirs up.
Have a nice day :)
Thomas
