Red Hat Bugzilla – Bug 141867
weirdness with usb dvd burner after burning disks
Last modified: 2015-01-04 17:13:38 EST
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.3)
Description of problem:
I wasn't sure whether to file this under cdrtools, dvdrtools or kernel
(since it's related to all of them). Basically, I have an external
usb2 dvd burner, and I use a script that basically calls mkisofs and
cdrecord to burn the disk (I've tried by hand, too). The dvd burner
shows up as /dev/scd0 (/media/cdrecorder1) and I am able to
successfully burn disks (I've verified this). However, once I've
burnt a disk, /dev/scd0 becomes unusable. Sometimes this means I just
can't mount anything (always comes up as "bad superblock"), or
sometimes /dev/scd0 just disappears, such that if I power the burner
off/on, it's re-detected as /dev/scd1, even though /dev/scd0 doesn't
exist (and it still won't mount disks).
I've tried this with the UP kernel, too, and get the same errors (with
the addition that the system will hang during shutdown/reboot
somewhere near the very end of things).
Rebooting solves the problem until I burn another disk.
Version-Release number of selected component (if applicable):
I believe that this is somehow related to a previous bug that I had
open at https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=123876 --
that bug went away, eventually, although I still had trouble burning
disks with SMP kernels (cdrecord couldn't figure out how to enable
burnfree, and no matter how slow I burned, I'd get buffer underruns).
An update has been released for Fedora Core 3 (kernel-2.6.12-1.1372_FC3) which
may contain a fix for your problem. Please update to this new kernel, and
report whether or not it fixes your problem.
If you have updated to Fedora Core 4 since this bug was opened, and the problem
still occurs with the latest updates for that release, please change the version
field of this bug to 'fc4'.
sorry, don't have my usb burner anymore. had to install it internally so I
could actually use it. Hopefully someone else can verify this.
I'll close this out for now. If someone else has the same problem, typically
they file a new bug anyway.