Hi,
the first message about lack of permissions is common and should be
harmless. The failure happens possibly with the attempt to get 16 MiB
of memory via call mmap(2). But it is not obvious why this only succeeds
if you are superuser.
So this might too be a red herring and the actual reason for
Hi,
> Is there a way to place a DVD burner into simulation mode as with CD
> recording so as to test the commands without wasting the disc?
Not with DVD+R and DVD+R DL, i fear.
Only DVD-R and unformatted DVD-RW can simulate.
> nodao.log
Now that's a short one.
It can hardly be that growisofs
... and there is a copy+paste error with
{{{
GET CONFIGURATION
46 01 00 00 00 00 00 00 08 00
From drive: 8b
00 00 00 9c 00 00 00 00
From drive: 8b
00 00 00 9c 00 00 00 00
8 ms
}}}
Of course, the drive replied only once.
--
You received this bug notification because you are a
Urm. The last stement should have been:
"... i will probably _not_ get to doing it soon."
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to dvd+rw-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1757030
Title:
Lite-On DS8A1H Slimline
Hi,
attached is a patch which enables SCSI logging to stderr in dvd+rw-tools.
It is based on dvd+rw-tools-7.1.tar.gz (MD5 8acb3c885c87f6838704a0025e435871).
There is no run-time control for this feature yet. Define or undefine
macro Libburnish_scsi_log_to_stderR and run "make" to enable or
Hi,
> With -tao option, xorrecord has no trouble at all.
I am out of ideas, for now.
> Is there an easy way to dump the raw commands before the one that
failed?
I am not aware whether the Linux kernel has a logging facility for
ioctl(SG_IO). That's the system call by which we perform the SCSI
Hi,
this time the layer break position was not set by growisofs.
Now i wonder what is the difference between the commands sent by growisofs
and libburn underneath xorriso.
Looking at the source code of growisofs it seems that no command RESERVE
TRACK is sent for DVD+R DL. libburn sends it if it
Hi,
the problem looks like it is triggered by growisofs' habit to explicitely
set the layer break position. See its message
/dev/dvdrw: splitting layers at 2009552 blocks
and its error message
4115562496/8231090176 (50.0%) @0.0x, remaining 16:15 RBU 100.0% UBU 100.0%
:-[ WRITE@LBA=1ea9d0h
Hi,
the initial error report of 2009 is probably due to a hardware problem
in the computers bus controller, or the cabling, or the drive's bus
controller.
> BraseroWodim stderr: CDB: 2A 00 00 01 6C 7E 00 00 1F 00
> ...
> BraseroWodim stderr: Sense Key: 0x0 No Additional Sense, Segment 11
> ...
>
Hi,
congrats to the success.
I have to stress, though, that cdrskin and xorriso are not forks of cdrecord
or growisofs, but applications of libburn, an independent implementation
of an SCSI/MMC driver in userspace.
In the end it depends on what the drive's firmware makes out of the SCSI
Hi,
yes, DVD-R and DVD+RW are treated quite differently by the drives.
The former is a sequential multi-session medium, the latter is a
random-access read-write medium. Firmware procedures inside the drive
differ. The laser used is the same, afaik. But the dye on the media is
quite surely not
Hi,
this looks like a bad relationship between drive and medium.
OPC (Optimum Power Calibration) is preparation stage of burning were the
drive makes experiments about the laser settings. The media have an
especially reserved data area for that.
Those experiments did not yield a satisfying
Hi,
did you already try -speed=1 in order to get the lowest possible speed ?
-
The growisofs function to set the speed
set_speed_B6h
in
https://sources.debian.net/src/dvd%2Brw-tools/7.1-11.1/growisofs_mmc.cpp/#L1090
is
Hi,
growisofs wrote:
> :-[ WRITE@LBA=10h failed with SK=5h/INVALID ADDRESS FOR WRITE]: Invalid
> argument
LBA=10h means that the second WRITE command yielded a failure message
from the drive. The accusation is strange.
I have seen this only with cdrecord yet, when the Linux kernel reported
Hi,
> growisofs
> ...
> :-[ WRITE@LBA=220h failed with SK=3h/WRITE ERROR]: Input/output error
Regrettably it does not tell the additional info numbers ASC and ASCQ.
But SK=3 means that the drive cannot write to the medium because of
unexpected problems. I.e. not because the DVD would not be
Hi,
i am somewhat confused. The fix is part of Debian's packaging
https://sources.debian.net/src/dvd%2Brw-tools/7.1-11/debian/patches/10-blue-ray-bug713016.patch/
(It is theoretically well understood and clearly correct.)
So why can't it stay in Ubuntu ?
--
You received this bug notification
Hi,
it is quite sure that you do not suffer from this old bug.
Please file a new bug. Tell what you did with which program,
which drive, which kind of media. Tell what error messages
you get when you try to read the discs.
Please notify me by mail to scdbac...@gmx.net about the
new bug report
Hi,
i got the growisofs log of K3b in a mail of 1.3 MB
From: Federico Tello Gentile 1113...@bugs.launchpad.net
which does not show up here.
The growisofs run failed with:
:-[ WRITE@LBA=b47400h failed with SK=5h/END OF USER AREA ENCOUNTERED ON THIS
TRACK]: Input/output error
This is a
Hi,
It is not that simple.
The same burn that failed with growisofs here
https://bugs.launchpad.net/ubuntu/utopic/+source/dvd+rw-tools/+bug/1113679/comments/13
finishes correctly with cdrecord.
[...] they all burn
flawlessly at 4X (1 GB/s). K3B using growisofs (besides never burning
Public bug reported:
Hi,
firstly: thanks for taking care of
https://bugs.launchpad.net/ubuntu/+source/dvd+rw-tools/+bug/1113679
Secondly: I hate to say it now, but i think a Debian user
just complained about the problem's little brother:
http://forums.debian.net/viewtopic.php?f=10t=120566
Hi,
are you really sure that the medium is DVD-R DL and not DVD+R DL.
DVD-R DL is said to be incapable of multi-session at all. I never
bought one. So i cannot tell what my drives would offer to do with
them.
I would be interested in seeing the output of
dvd+rw-mediainfo /dev/sr0
The
So you do not have a miracle burner which can do multi-session on DVD-R
DL. :))
Well, if i were the maintainer of dvd+rw-tools in Ubuntu, i would flatly disable
the 4 GB check or replace the error message and exit() by a loud warning
message.
(I would also fix
Dani, your problem is not related to this old Brasero bug.
You experience problems between drive and medium after
Brasero, libburn, and the drive all accepted the medium
as suitable for writing. The drive performed two WRITE
commands before it complained about the outcome of the
third one.
This narrows the set to: DVD-R, DVD-RW, DVD+R, DVD+RW.
(DVD-RAM and DVD+R DL have significantly different sizes.)
You should try a different brand of media. Best a different
type. E.g. try DVD+R if the failing ones are DVD-R.
If all reachable kinds of DVD fail, then consider to exchange
the
Hi,
something to the effect that beyond the first 2 KB the disk is not
empty
Original message texts may help to find out what's wrong.
Currently it looks like the burn programs get no error
indication from the drive, despite it does not burn the
medium properly.
Probably you used my libburn
Hi,
since the problem will soon be old enough to go to school,
i propose to fix a bug in the libburn plugin of Brasero
which is to see at
https://git.gnome.org/browse/brasero/tree/plugins/libburnia/burn-libburn.c#n558
This line obviously gets a number out of brasero's state:
Hi,
the drive tells libburn that the medium is not a DVD-RW
but a DVD+R. xorriso forwards this info:
Media current: DVD+R
Media status : is written , is closed
The perception of media type stems from 00 1b in the reply
to the GET CONFIGURATION command
GET CONFIGURATION
46 00 00 00 00 00
Another workaround is to format the BD-R before use by growisofs,
or to use growisofs option
-use-the-force-luke=spare:none
Whatever, is it so hard for Ubuntu to fix its dvd+rw-tools package ?
Like Fedora did ?
--
You received this bug notification because you are a member of Desktop
Hi,
the same problem is reported by
https://bugs.launchpad.net/ubuntu/+source/dvd+rw-tools/+bug/1113679
I proposed a remedy there:
--
--- growisofs_mmc_orig.cpp 2013-06-14 19:53:51.0 +0200
+++ growisofs_mmc.cpp
Hi,
Frank Griffin reports in
http://lists.alioth.debian.org/pipermail/debburn-devel/2013-June/000928.html
that my proposed change in growisofs_mmc.cpp indeed silences
the error message at the end of growisofs BD-R writing.
Have a nice day :)
Thomas
--
You received this bug notification
Hi,
after re-reading this diagnosis of the problem by the
author of growisofs
http://lists.debian.org/cdwrite/2008/07/msg00092.html
i developed a theory.
For details see
http://lists.alioth.debian.org/pipermail/debburn-devel/2013-June/000924.html
I do not want to use up a blank BD-R for
Hi,
i am the developer of libburn, which would probably be in charge
for burning underneath Brasero in younger Ubuntu versions.
(One can learn from Brasero logs, whether libburn is used as
burn backend. Search for Libburn.)
There was a bug when the application asked for minimum speed
and the
Hi,
To my own experience, the code which governs creation and burning of
ISO images on-the-fly is separate from the code that governs burning
of pre-produced image files from hard disk.
(I am developer of libburn and libisofs, not a user of Brasero.
But i once had reason to find out how Brasero
Hi,
thank you for flying xorriso.
The growisofs bug is indeed well known. It was announced several
years ago to become fixed in the next release. Regrettably that
release never happened. Currently growisofs seems unmaintained.
Much of its knowledge was pulled into libburn, though, which
Hi,
So I was in good luck that I only had to wait 2 days for the fix :-)
I guess the fix for your problem was available since a while.
But if you had installed it, you had gotten the bug that was fixed here.
So your luck is a very wise one which knows how long to wait. Congrats.
Have a nice
Hi,
As source I used the downloaded ISO of PartedMagic from 2012_11_30.
I simply opened this with Brasero to start burning on a DVD-RW,
which first had to be erased.
The bug that was fixed here did not affect burning of prepared
ISO images, but only composition of ISO images from hard disk
Hi,
I was using a CD-RW, not DVD-RW, 650 MB, 4x
I'm not sure, if -format would concern here?
Not with xorriso, and not desirable for your purpose.
Now I tried again with just updated 3.4.1-0ubuntu1.1:
Burning took ~ 10 min. at 4x -- successful
Some bugs were fixed in the meantime. The bug
Hi,
i am glad to see that this time not the libburn plugin is
to blame. :))
Telling from the log, i would say that burning via libburn
succeeded:
Burning from 0 to 355990
TAO pre-track 01 : get_nwa(0)=1, d=0 , demand=729067520 , cap=736966656
[... no visible error messages ...]
Aync CLOSE
Hi,
there was a brasero bug fixed in the course of
https://bugs.launchpad.net/ubuntu/+source/brasero/+bug/780117
which began by a different problem but collected several
reports about unmountable CD and DVD.
It hit data burning on-the-fly but not burning of pre-produced
ISO images or of CD
Hi,
some technical comments to Nico Zanferrari's notes:
(I always use a fresh standard live 32 bit USB key with the same DVD-RW)
[...]
- the unreadable coasters produced from other Ubuntu versions are seen as
blank disk from standard brasero 12.10, and can be easily blanked with it.
This is
Hi,
this problem could be caused by the Brasero bug
that was found in the course of
https://bugs.launchpad.net/ubuntu/+source/brasero/+bug/780117
Have a nice day :)
Thomas
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to brasero in
Hi,
for completeness: One of the two Debian patches replaces
the theory of SAO-versus-TAO.
It turned out that the function, which transmits the
libisofs image data to the burn software, dropped every
second data block. (Actually the first block of each pair
of blocks.)
Hi,
Paul Menzel wrote:
The way to solve this error, is that people provide the necessary log
files from Brasero and to improve the things Thomas Schmitt and George
Danchev have found out to be incorrect [1].
Well, actually we [George and me] do not have any good idea left what
goes wrong
Hi,
Austin Dempewolff wrote:
I'm not sure if my problem was exactly the same bug (Brasero was producing
coasters
without any errors,
That seems to be the much more often occuring problem, although it is
not the original cause of this bug report thread.
but I was burning ISOs, not data
Hi,
i wrote:
cdrskin -tao padsize=300k -v dev=/dev/sr0 blank=as_needed -eject image.iso
Austin Dempewolff wrote:
Done, worked great. Stdout attached.
I assume you tested full readability afterwards.
That cdrskin command is supposed to do quite the same with libburn
as Brasero does. One
Hi,
i am the upstream programmer of libisofs and libburn but not
directly involved in Brasero.
Andrea Amoroso wrote in #63:
still the mp3 cds I burnt are full of the mp3 i chose, with some
of them unreadable and others readable but with many lags
It is not clear to me whether libisofs was
46 matches
Mail list logo