Re: Burning and mounting written BDs

[Kjetil Kjernsmo]

On torsdag 28. desember 2023 23:39:59 CET Thomas Schmitt wrote:
> Hi,
> 
> Kjetil Kjernsmo wrote:
> > OK, I had a single 25 GB M-disc left, so I just started writing to that,
> > fingers crossed!
> 
> I meanwhile made up a theory about the failure to mount which you report
> in the first mail of this thread:
> If you did not eject and reload the medium between burning and mount
> attempt, then you fell victim to a known problem with burning on Linux.

Uh-oh. Indeed, I didn't.


> The change of medium state and readable size does not get known to the
> kernel automatically and there are no means to tell the kernel to
> re-assess the medium. The only way to force re-assessment is to eject and
> reload.

OK!

So, meanwhile, I wrote the 25GB M-disc that I had, and that looked fine. check 
reading logs is attached, that looked fine too and isn't too big. 


> With xorriso you may eject by appending the following commands to the
> xorriso burn run:
> 
>   -commit -eject all -outdev /dev/sr0
> 
> This will burn, eject, load again, and wait until the drive reports to
> be ready. (Linux does not wait properly any more since march 2008.)

OK, so I did this on the new disc, but it still fails to mount:

root@robin:/dev# xorriso  -commit -eject all -outdev /dev/sr0
xorriso 1.5.4 : RockRidge filesystem manipulator, libburnia project.

xorriso : WARNING : -commit: No image modifications pending
Drive current: -outdev '/dev/sr0'
Media current: BD-R sequential recording
Media status : is written , is appendable
Media summary: 1 session, 12060064 data blocks, 23.0g data,  311m free
root@robin:/dev#   osirrox -indev /dev/sr0 -mount indev auto auto /mnt/test/
xorriso 1.5.4 : RockRidge filesystem manipulator, libburnia project.

xorriso : NOTE : Loading ISO image tree from LBA 0
xorriso : UPDATE :      80 nodes read in 1 seconds
xorriso : UPDATE :     480 nodes read in 2 seconds
xorriso : UPDATE :    5050 nodes read in 3 seconds
xorriso : UPDATE :   12350 nodes read in 4 seconds
xorriso : UPDATE :   16937 nodes read in 5 seconds
Drive current: -indev '/dev/sr0'
Drive access : shared:readonly
Media current: BD-R sequential recording
Media status : is written , is appendable
Media summary: 1 session, 12060064 data blocks, 23.0g data,  311m free
Volume id    : 'ISOIMAGE'
Volume id    : 'ISOIMAGE'
Mount command: mount -t iso9660 -o nodev,noexec,nosuid,ro,sbsector=0 '/dev/
sr0' '/mnt/test/'
mount: /mnt/test: wrong fs type, bad option, bad superblock on /dev/sr0, 
missing codepage or helper program, or other error.
       dmesg(1) may have more information after failed mount system call.
xorriso : FAILURE : -mount : mount command failed with exit value 32
xorriso : aborting : -abort_on 'FAILURE' encountered 'FAILURE'

> > Alright, OK! I have previously used this [drive] successfully even with
> > 100 GB M-Disc
> 
> But did you checkread all data content afterwards ?

No, I have to admit that I didn't... I wrote it with k3b, saw no errors, 
opened a few files to see if that was OK, and put them in my in-laws basement 
for offsite backup :-)


> If my above theory is correct, then the readability problem with higher
> block addresses might not be new.

Yeah, I should bring some back and check them one day.


> Have a nice day :)

Likewise!

Kind regards,

Kjetil

xorriso25_log
Description: Text document