Re: Burning and mounting written BDs

[Kjetil Kjernsmo]

Hi! 

I hope everyone is having a great end of year!

I'm happy to report that I also managed to successfully burn a 50 GB M-Disc, 
it checks out and can be mounted an all! Now, I have just one to go.

On lørdag 30. desember 2023 10:23:14 CET you wrote:
> > 2023-12-27T00:49:06.631449+01:00 robin kernel: [4685133.115719]
> > isofs_fill_super: bread failed, dev=sr0, iso_blknum=16, block=16
> 
> This human readable date and log timestamp looks too near to the time
> 
> of your first reported mount failure:
> > > [4683501.642523] isofs_fill_super: bread failed, dev=sr0, iso_blknum=16,
> > > block=16
> The difference is only 1632 seconds. So i don't think that this is from
> the attempt to mount the 25 GB medium of your second burn run.

Hmmm, yeah... I just found dmesg -T, that should help me with that in the 
future :-) Is there anything I could grep for? I just don't think I saw 
anything but that message... I did see some messages around UDF when I had k3b 
open, it was probably annoyed by that it was a BD but didn't have UDF, but I 
haven't had k3b running now recently.

> This does not tell the received SCSI error code. But the texts "Illegal
> Request" and "Illegal mode for this track" are listed in SCSI specs as
> meaning of sense code [5 64 00].
> The line under "CDB:" shows the attempted SCSI command. In this case it
> was the request to read two data blocks from block address 0. It failed
> because at this address are two audio blocks which would be readable only
> by SCSI command READ CD.

Hmmm, I tried grepping "Illegal Request" "Illegal mode", "Sense key", but 
nothing turned up.
 
> > I usually only have downtime when doing a kernel upgrade... Perhaps the
> > box
> > needed some ... rest? :-)
> 
> If so then it would be no general problem of Linux. My /var/log/messages
> shows currently nearly ten times your uptime: [44669411.147860].

Yup. My suspect wouldn't be the OS, but perhaps the drive...? I haven't used 
it a lot, so it would be surprising, but possible.

> > Even though the noise is not a concern, perhaps I should throttle it a bit
> > for stability?
> 
> I regularly fear about the health of my drives when they go to full
> reading speed.
> (Especially my Pioneer BDR-S09 drive is willing to spin the medium so fast
> that currently sold "Verbatim" branded BD-RE media get cracks at the inner
> hole after about ten full-speed full-size readings. Because this drive
> does not obey SCSI read speed settings i had to invent a -read_speed mode
> named "soft_force" which causes xorriso to slow down the frequency of its
> read requests in order to enforce a lower speed.)

Oh, wow. 

I choose to throttle the write speed in my latest burn:

 xorriso -outdev /dev/sr0 -for-backup -blank as_needed -speed 4b --map ./
bildebackup-2023/ /Bilder -commit -eject all -outdev /dev/sr0 

However, to finish off my annual backups, I put in another 50 GB M-disc, and it 
seems to have failed in the very last minute:
xorriso : UPDATE : Writing:   23102208s   99.9%   fifo  99%  buf 100%    4.1xB 
xorriso : UPDATE : Writing:   23111136s  100.0%   fifo 100%  buf 100%    4.1xB 
libisofs: FATAL : Image is most likely damaged. Calculated/written tree end 
address mismatch.
libisofs: FATAL : Image is most likely damaged. Calculated/written image end 
address mismatch.
xorriso : FATAL : -abort_on 'FAILURE' encountered 'FATAL' during image writing
xorriso : NOTE : libburn has now been urged to cancel its operation
xorriso : UPDATE : Writing:   23112960s  100.0%   fifo  65%  buf 100%    0.8xB 
libburn : WARNING : Last session on media is still open.
xorriso : FAILURE : libburn indicates failure with writing.
xorriso : aborting : -abort_on 'FAILURE' encountered 'FATAL'

checking that, I only get 
libburn : WARNING : Last session on media is still open.
xorriso : FAILURE : Cannot read ISO image tree
xorriso : HINT : You might get a partial or altered ISO image tree by option -
error_behavior 'image_loading' 'best_effort' if -abort_on is set to be tolerant 
enough.
xorriso : aborting : -abort_on 'FAILURE' encountered 'FAILURE'

I can't find anything in the logs but the dmesg said:
[lø. des. 30 11:07:03 2023] ISO 9660 Extensions: RRIP_1991A
which is around then.

Kind regards,

Kjetil