[Top][All Lists]

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

Re: [Bug-xorriso] To Thomas Schmitt: how to go on, xorriso is installed

From: Thomas Schmitt
Subject: Re: [Bug-xorriso] To Thomas Schmitt: how to go on, xorriso is installed
Date: Wed, 10 Apr 2019 10:13:45 +0200


Adalbert Hanßen wrote:
> Media product: 97m24s16f/79m59s74f , Sony Corporation
> Media status : is blank

This is not totally unplausible, because the write error came early and
there is some asynchronicity because of the drive buffer. So it can be
that no actual writing happened.

With write SAO this would be somewhat astounding. But with TAO it would
be plausible.

> Now the first one written labelled Verbatim:
> Then after some period, the CD is mounted and now it shows the content in
> Thunar!

This indicates that the first blocks of the CD are readable. The Linux
kernel can read the superblock and the directory tree.
But i doubt that the all the data file contents are readable.
I expect i/o errors when you try to open some of the offered files.

> libburn : SORRY : Cannot open busy device '/dev/sr0' : Device or resource

By default you will have to umount the drive before xorriso is willing
to access it. (This lock shall not only prevent mounted ISOs from being
altered, but also prevent collisions between burn programs on the same

There is xorriso command
  -osirrox o_excl_off
which circumvents the lock. But one should use it only if umounting is
not an option or if it is unknown which process has the CD drive in use.

> $ umount /dev/sr0
> $ xorriso -outdev /dev/sr0 -list_profiles out -toc
> ...
> libburn : SORRY : Timeout exceed (30000 ms). Retry canceled.

The drive has a hard time with its own produce.

> Media status : is written , is closed
> Media summary: 1 session, 116943 data blocks,  228m data,     0 free

This looks like SAO. A large session is already reserved.

So you could retry with Xfburn "Schreibmodus" TAO/Track-at-once in order
to make sure that the drive fails with both write types.

(On the other hand, written by SAO, the other CD should not be blank
 any more. And the drive should really not accept the first WRITE command
 if the SAO reservation did fail. Quite a riddle ...)

> This one took much longer to complete. But this medium is really wrecked, I
> thought the other one too!
> Tomorrow I'll try to write onto the SONY disk with the T400 laptop.

I am not sure whether the Sony medium is really still burnable.
Be not disappointed if it fails there too.

But burn tests with a yet untouched CDs would be very interesting for
the question whether your media are bad on more than one drive.

> Probably we also need xorriso there too - right?

We could need it for examining the media after burning.
(It can also be used for burning with MD5 checksums for all data files
 and the overall ISO filesystem. xorriso can later checkread the medium
 and verify the checksums.)

> I also have an external USB CD/DVD drive which I could alos test.

The more the better. At least for the riddle what component is to blame.

Have a nice day :)


reply via email to

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