Hi, while making a google poll about the spectrum of sense bytes reported by cdrecord, i found some occurences of "Sense Bytes: 72".
This german bug report describes a similar incident with CD-R: http://forums.gentoo.org/viewtopic-t-795543-view-previous.html?sid=363061ca5d441369d0e3d4e34d1cc55f The submitter reports to have repaired it by connecting the drive to a different SATA port on the mainboard. This one got solved by moving and re-plugging hard disks and optical drives: http://forums.fedoraforum.org/showthread.php?p=983661 Similar ones with no final remedy: http://forums.linuxmint.com/viewtopic.php?f=47&t=51139&p=294233 http://ubuntuforums.org/showthread.php?t=1411580 https://bugs.launchpad.net/ubuntu/+source/cdrkit/+bug/432929 There are lots of misleading rumors: This one comes to the conclusion that cdrecord succeeds where wodim fails: https://bugzilla.redhat.com/show_bug.cgi?format=multiple&id=546437 see first follow-up comment So far for success-failure statistics. It is reported that switching from disk image file to writing on-the-fly helped https://bbs.archlinux.org/viewtopic.php?id=60892 Quite implausible unless the image file emerges on a different disk than the input data get read from. Other remedies are: add user to group "optical", setup k3B properly, convert sound files to .wav ... maybe we should add lunar phases or subterrestrial water radiations to the list. ------------------------------------------------ Elsewise google finds me only format codes 0x70 and 0xF0 with cdrecord. Both differ only by the VALID bit, which indicates the standard conformance of bytes 3 to 6. Have a nice day :) Thomas -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected] Archive: http://lists.debian.org/[email protected]
