Hi,
sorry for your drive.
But good for Linux burn programs that MS-Windows does not know something
essential about drive error messages which we Linuxers don't know.
> the srange this is that if you use the Disks program in utilities.
That's probably a message from the kernel via systemd and
Hi Thomas.
sorry that it has taken a while to get back to you.
the drive failed completely, would not read or write.
i have perchased another drive, and that is workig ok.
the srange this is that if you use the Disks program in utilities. it
shows the drive as read only. this is what got me
Hi,
well, at least we got over the strange error code.
> libburn : SORRY : Timeout exceed (3 ms). Retry canceled.
> libburn : SORRY : Command: READ DISC INFORMATION #63,[2 04 00] : 51 00
> 00 00 00 00 00 00 22 00 : dxfer_len= 34
The command READ DISC INFORMATION was retried 63 times. The
Correction:
The single command READ DISC INFORMATION probably did not timeout, but was
repeated
with intermediate waiting until 30 seconds had elapsed. So the drive probably
reacts swiftly but
always says that it is not yet ready.
--
You received this bug notification because you are a member
Hi Thomas.
did the alteration to spc.c and ran make. ububnu is still seeing the
drive as read only. see the output below.
chris@chris-A320M-S2H-V2:~/xorriso/xorriso-1.5.3$ ./xorriso/xorriso
-outdev /dev/sr0 -toc
GNU xorriso 1.5.3 : RockRidge filesystem manipulator, libburnia
project.
libburn :
Thanks for getting back to me.
I have not done this before, but will have a go and let you know.
Regards
Chris
On Thu, 24 Sep 2020, 17:20 Thomas Schmitt, <1896...@bugs.launchpad.net>
wrote:
> Hi,
>
> > libburn : SORRY : Asynchronous SCSI error on waiting after START UNIT
> > (+ LOAD) [6 28 81]
Hi,
> libburn : SORRY : Asynchronous SCSI error on waiting after START UNIT
> (+ LOAD) [6 28 81] Drive event. Unknown ASCQ with drive event ASC 28.
Grr. A higher level intervened.
In line 198 of file
~/xorriso/xorriso-1.5.3/libburn/spc.c
there is
if (key == 0x6 &&
Hi Thomas.
have followed your instructions. still no good.
this is the terminal readout.
chris@chris-A320M-S2H-V2:~/xorriso/xorriso-1.5.3$ ./xorriso/xorriso
-outdev /dev/sr0 -toc
GNU xorriso 1.5.3 : RockRidge filesystem manipulator, libburnia
project.
libburn : SORRY : Asynchronous SCSI error on
Thanks Thomas.
Will give it a go later today.
Regards
Chris
On Thu, 24 Sep 2020, 11:30 Thomas Schmitt, <1896...@bugs.launchpad.net>
wrote:
> Hi,
>
> > Sense Key 6 "Drive event", ASC 28 ASCQ 81.
>
> This SCSI error reply is not listed in SCSI specs SPC or MMC or in the
> summary of T10 committee
The line with the absolute address was meant to be:
/home/chris/xorriso/xorriso-1.5.3/xorriso/xorriso -outdev /dev/sr0
-toc
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1896804
Title:
CD/DVD
Hi,
> Sense Key 6 "Drive event", ASC 28 ASCQ 81.
This SCSI error reply is not listed in SCSI specs SPC or MMC or in the
summary of T10 committee
https://www.t10.org/lists/asc-num.htm#ASC_28
So the drive's firmware programmers were overly creative.
If it was ASCQ 0 or 2, then libburn would
Hi Thomas.
this is the output from running "xorriso -outdev /dev/sr0 -toc"
xorriso 1.5.2 : RockRidge filesystem manipulator, libburnia project.
libburn : SORRY : Asynchronous SCSI error on waiting after START UNIT
(+ LOAD): See MMC specs: Sense Key 6 "Drive event", ASC 28 ASCQ 81.
xorriso :
I forgot to ask for putting in the desired medium before performing
xorriso -outdev /dev/sr0 -toc
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1896804
Title:
CD/DVD drive detected as read only,
Hi,
i understand from the category "brasero package" that you inspect the drive
by Brasero.
Which burn backend is it using (cdrecord, wodim, libburn ) ?
What kind of medium did you try (CD-R, DVD+R, DVD-R, DVD+RW, BD-R, ...) ?
Which task of Brasero do you want to perform (Audio project, Data
14 matches
Mail list logo
