bug-xorriso
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Burning and mounting written BDs


From: Thomas Schmitt
Subject: Re: Burning and mounting written BDs
Date: Fri, 29 Dec 2023 08:57:17 +0100

Hi,

Kjetil Kjernsmo wrote:
> 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.

Yeah. That's how a good checkread log should look like.
(Maximum speed was 12x = ~ 54 MB/s. Isn't that terribly loud ?
If so, you may curb speed by xorriso command -read_speed "6" before the
-check_media command.)


I wrote:
> > With xorriso you may eject by appending the following commands to the
> > xorriso burn run:

> root@robin:/dev# xorriso  -commit -eject all -outdev /dev/sr0
> xorriso : WARNING : -commit: No image modifications pending

I actually meant that these commands would perform the eject-load cycle
at the end of a burn run. But of course it does not harm to perform
such a cycle later.


> root@robin:/dev#   osirrox -indev /dev/sr0 -mount indev auto auto /mnt/test/
> ...
> 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.

This is unexpected.
What does the system log say about the reason for this failure ?


Have a nice day :)

Thomas




reply via email to

[Prev in Thread] Current Thread [Next in Thread]