© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
0e1f616
(Get the code!)
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:/
So the drive's firmware programmers were overly creative.
If it was ASCQ 0 or 2, then libburn would tolerate it:
6 28 00 NOT READY TO READY CHANGE, MEDIUM MAY HAVE CHANGED
6 28 02 FORMAT-LAYER MAY HAVE CHANGED
but the other ASCQs of ASC 28 were too obscure to me to be tolerable.
I now made a GNU xorriso tarball with a libburn which tolerates any Drive
event error with ASC 28 so that you can drill deeper into the drive behavior.
(I have to think whether this change is good as permanent solution. The list
of key 6 errors looks in part fatal like
6 29 00 POWER ON, RESET, OR BUS DEVICE RESET OCCURRED
6 3B 0F END OF MEDIUM REACHED
but in part retryable. My program change relies on the hope that all ASC 28
codes are harmless.)
-------
You will need the dependency packages of pseudo-package "build-essential"
https:/
then download
https:/
and copy it to a directory of your choice, e.g. to
/home/
Then build it by
cd /home/chris/xorriso
tar xzf xorriso-
cd xorriso-1.5.3
./configure --prefix=/usr && make
On a modern machine the "make" part should be done in half a minute.
Afterwards there should be an executable program
./xorriso/xorriso
You may use it in place by its relative address
./xorriso/xorriso -outdev /dev/sr0 -toc
or by its absolute address
/home/
Your Ubuntu xorriso will stay installed and your package manager cannot
get confused by the newly made xorriso. (It is quite large because it contains
own copies of libburn, libisofs, libisoburn, and libjte.)
-------
Have a nice day :)
Thomas