I have been having some strange results trying to burn CDs under CentOS. I don't think they are hardware related because I have had some success, in fact most of this usually works.
I use k3b for most of my CD and DVD writing - it seems to work fairly well (well, except for wrecking my installation a few weeks ago when it crashed my installation and I had to reinstall to get it back, but that's old news).
Yesterday, of my work desktop (32-bit), I tried to burn a CD with k3b. The system hung as soon as I clicked on the start button in the burn menu. I did not want another case of wrecked system, so I rebooted (no other way to interrupt it) and all went well, except that I didn't even try to burn the CD. (I used my other, backup desktop, and it worked fine over there - hmm....)
Then, last night, on my home desktop (64-bit), which is usually solid as a rock, no problems whatsoever (I said "usually"), I had similar problems, though not quite as bad. I was trying to erase some CD-RWs, and I kept getting errors, both from k3b and cdrecord, claiming that they could not lock the drive for exclusive access (because another process was accessing the device). This is really annoying because I've tried this one several CD-RWs, and they all get the same error. Since k3b doesn't include a facility to add data to an already written CD or DVD unless there's a specific project for it (which I don't have 'cuz the CDs were written under Window$ or with projects I didn't keep).
Any ideas/suggestions?
Thanks.
mhr
On Wed, 2008-12-31 at 10:27 -0800, MHR wrote:
I have been having some strange results trying to burn CDs under CentOS. I don't think they are hardware related because I have had some success, in fact most of this usually works.
I use k3b for most of my CD and DVD writing - it seems to work fairly well (well, except for wrecking my installation a few weeks ago when it crashed my installation and I had to reinstall to get it back, but that's old news).
Yesterday, of my work desktop (32-bit), I tried to burn a CD with k3b. The system hung as soon as I clicked on the start button in the burn menu. I did not want another case of wrecked system, so I rebooted (no other way to interrupt it) and all went well, except that I didn't even try to burn the CD. (I used my other, backup desktop, and it worked fine over there - hmm....)
Then, last night, on my home desktop (64-bit), which is usually solid as a rock, no problems whatsoever (I said "usually"), I had similar problems, though not quite as bad. I was trying to erase some CD-RWs, and I kept getting errors, both from k3b and cdrecord, claiming that they could not lock the drive for exclusive access (because another process was accessing the device). This is really annoying because I've tried this one several CD-RWs, and they all get the same error. Since k3b doesn't include a facility to add data to an already written CD or DVD unless there's a specific project for it (which I don't have 'cuz the CDs were written under Window$ or with projects I didn't keep).
Any ideas/suggestions?
As to the "in use" part, I'll make a SWAG (Scientific Wild-Ass Guess).
With a normal desktop, when you insert a CD/DVD that has something recognizable on it, an "automount" occurs that gives you access to the thing from your desktop. I know notthing about the k3*, so I don't know if the following is possible.
Is it possible that it is mounted as another user? If it is mounted at all, does k3* allow you to erase, write, etc? I would think that it would need to be un-mounted for that to occur.
That's all I can think of. Can you right-click on the icon and see what the system thinks about it? What does a mount command show?
Thanks.
mhr
<snip>
Sorry I have nothing more knowledgeable. I always use the cdr tools for my stuff.
HTH
On Wed, Dec 31, 2008 at 10:37 AM, William L. Maltby CentOS4Bill@triad.rr.com wrote:
As to the "in use" part, I'll make a SWAG (Scientific Wild-Ass Guess).
With a normal desktop, when you insert a CD/DVD that has something recognizable on it, an "automount" occurs that gives you access to the thing from your desktop. I know notthing about the k3*, so I don't know if the following is possible.
Is it possible that it is mounted as another user? If it is mounted at all, does k3* allow you to erase, write, etc? I would think that it would need to be un-mounted for that to occur.
Actually, I did think of that. I tried running the cdrecord erase command with sudo (as root) and it made no difference - still couldn't "lock" the device.
Should I unmount the disk and then try the erase command? That seems kind of odd, but I'll try it tonight anyway....
Thanks.
mhr
On Wed, 2008-12-31 at 11:09 -0800, MHR wrote:
On Wed, Dec 31, 2008 at 10:37 AM, William L. Maltby CentOS4Bill@triad.rr.com wrote:
As to the "in use" part, I'll make a SWAG (Scientific Wild-Ass Guess).
With a normal desktop, when you insert a CD/DVD that has something recognizable on it, an "automount" occurs that gives you access to the thing from your desktop. I know notthing about the k3*, so I don't know if the following is possible.
Is it possible that it is mounted as another user? If it is mounted at all, does k3* allow you to erase, write, etc? I would think that it would need to be un-mounted for that to occur.
Actually, I did think of that. I tried running the cdrecord erase command with sudo (as root) and it made no difference - still couldn't "lock" the device.
Should I unmount the disk and then try the erase command? That seems kind of odd, but I'll try it tonight anyway....
Yes. AFAIK, no mounted FS can be easily (I'm not sure about impossible) "reformatted" or "erased" (both are effectively removing the file system). One of the nice things an OS does (or should do) if prevent destruction of "active" file systems. If mounted, it is active. Try the umount and then working on it. BTW, for DVD if IIRC, you _might_ need to "format". Unsure of that though. I know a "virgin" needs formatting.
Maybe the desktop ICON can be right-clicked and cause an unmount without ejecting and making the icon disappear? If so, then that would let you continue to operate on it via the desktop tools.
I've not tried that, but it _seems_ it should work. I mean, if the desktop can recognize a "blank" media and allow you to format, burn, etc., even though there is no file system there, it should not (IMO) remove the icon just because it is unmounted. Once unmounted, the media is not "active" and could (s/b IMO) be treated just like a blank media.
Thanks.
mhr
<snip sig stuff>
MHR wrote:
I have been having some strange results trying to burn CDs under CentOS. I don't think they are hardware related because I have had some success, in fact most of this usually works.
I use k3b with little problem. I do have to tell it to use TAO and to go at 8x. If I let it go auto, it would hang on me. I suspect it was not getting the 'right' hardware info and doing the wrong thing.
I use k3b for most of my CD and DVD writing - it seems to work fairly well (well, except for wrecking my installation a few weeks ago when it crashed my installation and I had to reinstall to get it back, but that's old news).
Yesterday, of my work desktop (32-bit), I tried to burn a CD with k3b. The system hung as soon as I clicked on the start button in the burn menu. I did not want another case of wrecked system, so I rebooted (no other way to interrupt it) and all went well, except that I didn't even try to burn the CD. (I used my other, backup desktop, and it worked fine over there - hmm....)
Then, last night, on my home desktop (64-bit), which is usually solid as a rock, no problems whatsoever (I said "usually"), I had similar problems, though not quite as bad. I was trying to erase some CD-RWs, and I kept getting errors, both from k3b and cdrecord, claiming that they could not lock the drive for exclusive access (because another process was accessing the device). This is really annoying because I've tried this one several CD-RWs, and they all get the same error. Since k3b doesn't include a facility to add data to an already written CD or DVD unless there's a specific project for it (which I don't have 'cuz the CDs were written under Window$ or with projects I didn't keep).
Any ideas/suggestions?
Thanks.
mhr _______________________________________________ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
On Wed, Dec 31, 2008 at 11:09 AM, Robert Moskowitz rgm@htt-consult.com wrote:
MHR wrote:
I have been having some strange results trying to burn CDs under CentOS. I don't think they are hardware related because I have had some success, in fact most of this usually works.
I use k3b with little problem. I do have to tell it to use TAO and to go at 8x. If I let it go auto, it would hang on me. I suspect it was not getting the 'right' hardware info and doing the wrong thing.
A big aha! I forgot all about that (TAO). I usually click the circular dual arrow button (which tells k3b to go and get the actual speeds available so it will then use the right/fastest one).
Thanks!
mhr
On Wed, Dec 31, 2008 at 1:27 PM, MHR mhullrich@gmail.com wrote:
I have been having some strange results trying to burn CDs under CentOS. I don't think they are hardware related because I have had some success, in fact most of this usually works.
I use k3b for most of my CD and DVD writing - it seems to work fairly well (well, except for wrecking my installation a few weeks ago when it crashed my installation and I had to reinstall to get it back, but that's old news).
I use k3b to burn CD-R and CD-RW media on my CentOS 5.2 (32 bit) box. Does not have a DVD burner, so I can't speak to burning DVD media with k3b. I do not see those issues. However, when I began having a variety of problems with this box, about 2 weeks ago, one of the symptoms was that k3b did not see media in the drive. There were also other symptoms, unrelated to k3b. Following my own advice, which I'd given to someone on the list, I opened the box and pushed down on all the connectors, RAM, etc. Poof..... All of the symptoms have gone away, and stayed away, with the exception of the 4 Diagnostic Lights on the motherboard are Yellow, undocumented, but apparently means mobo is damaged. Bottom line is I suggest that you open the box, and push down on all the connectors, RAM, etc. GL & Happy New Year!
MHR wrote: *snip*
Any ideas/suggestions?
I always just use the cli tool, and I always do the actual burn as root.
To make a CD/DVD image I use -
mkisofs -J -l -r -o foo.iso /path/to/some/directory
To burn - which I do as root - I insert the media, wait a few seconds, then -
cdrecord -dev=/dev/scd0 -speed=n -dao -pad -v foo.iso
For data CDs if I pick a speed below 24x it does 24x anyway - not sure why, didn't with my old burner (ATAPI) but does with my SATA burner.
With DVDs - I specify 4x. When burning AVI files to play on my DVD player (which supports divx on iso9660) if I burn at 8x - half the time the DVD player reports bad disk, but burn at 4x and it always works (DVD-R media)
Don't let the screensaver pop on during a burn - I've had that ruin burns. Also burn as root. When I try burning as a non privileged user, it often fails. You can set the suid bit on cdrecord and burn as standard user, but that gets undone next yum update (I suppose you could write a suid wrapper script and throw it in /usr/local/bin ...)
For audio CDs - last time I burned an audio CD was so long ago I don't remember, but I recall needing to make a TOC file and I think I used a different executable than cdrecord.
Also - if running BitTorrent - shut it off. I've had burns ruined because BitTorrent was running. That may have been because I don't have a dedicated disk for the CD/DVD images, so the disk arm moving to read and send torrent bits may have been too slow to keep the burner buffer happily filled.
On Wed, Dec 31, 2008 at 1:27 PM, MHR mhullrich@gmail.com wrote:
I have been having some strange results trying to burn >CDs under CentOS. I don't think they are hardware related >because I have had some success, in fact most of this usually works.
I use k3b for most of my CD and DVD writing - it seems to work fairly well (well, except for wrecking my installation a few
I do have an issue with k3b (CentOS 5.2, 32 bit), but nothing grave. I cannot erase CD-RW media with k3b, most or all of the time. I ran into that last night. Went to M$ Windows and I was able to erase the 2 CD-RW media, without any problem. Then, I tried to burn the files (which are M$ Windows files) to the CD-RW media. No go and I wasted about 20-30 minutes, while it was in a loop or stalled on M$ Windows. Then, I went back to CentOS and I was able to burn the files, without any problems. :-) Not sure what is causing the issues. Nothing grave, such as borked your box recently.
On Sat, Jan 03, 2009 at 04:21:55PM -0500, Lanny Marcus wrote:
On Wed, Dec 31, 2008 at 1:27 PM, MHR mhullrich@gmail.com wrote:
I have been having some strange results trying to burn >CDs under CentOS. I don't think they are hardware related >because I have had some success, in fact most of this usually works.
I use k3b for most of my CD and DVD writing - it seems to work fairly well (well, except for wrecking my installation a few
I do have an issue with k3b (CentOS 5.2, 32 bit), but nothing grave. I cannot erase CD-RW media with k3b, most or all of the time. I ran into that last night. Went to M$ Windows and I was able to erase the 2 CD-RW media, without any problem. Then, I tried to burn the files (which are M$ Windows files) to the CD-RW media. No go and I wasted about 20-30 minutes, while it was in a loop or stalled on M$ Windows. Then, I went back to CentOS and I was able to burn the files, without any problems. :-) Not sure what is causing the issues. Nothing grave, such as borked your box recently.
My experience has been that SOMETIMES K3B will attempt to erase a RW volume and fail because the volume is currently mounted. I think that K3B should automagically unmount it, but I've seen it not do so. So, if erasing it fails, manually unmount it then try again.
On Sat, Jan 3, 2009 at 4:30 PM, fred smith fredex@fcshome.stoneham.ma.us wrote:
On Sat, Jan 03, 2009 at 04:21:55PM -0500, Lanny Marcus wrote:
<snip>
I do have an issue with k3b (CentOS 5.2, 32 bit), but nothing grave. I cannot erase CD-RW media with k3b, most or all of the time. I ran into that last night. Went to M$ Windows and I was able to erase the 2 CD-RW media, without any problem. Then, I tried to burn the files (which are M$ Windows files) to the CD-RW media. No go and I wasted about 20-30 minutes, while it was in a loop or stalled on M$ Windows. Then, I went back to CentOS and I was able to burn the files, without any problems. :-) Not sure what is causing the issues. Nothing grave, such as borked your box recently.
My experience has been that SOMETIMES K3B will attempt to erase a RW volume and fail because the volume is currently mounted. I think that K3B should automagically unmount it, but I've seen it not do so. So, if erasing it fails, manually unmount it then try again.
Fred: Thank you. The next time it happens, I will try to unmount. Lann
On Saturday 03 January 2009 21:21:55 Lanny Marcus wrote:
On Wed, Dec 31, 2008 at 1:27 PM, MHR mhullrich@gmail.com wrote:
I have been having some strange results trying to burn >CDs under CentOS. I don't think they are hardware related >because I have had some success, in fact most of this usually works.
I use k3b for most of my CD and DVD writing - it seems to work fairly well (well, except for wrecking my installation a few
I do have an issue with k3b (CentOS 5.2, 32 bit), but nothing grave. I cannot erase CD-RW media with k3b, most or all of the time. I ran into that last night. Went to M$ Windows and I was able to erase the 2 CD-RW media, without any problem. Then, I tried to burn the files (which are M$ Windows files) to the CD-RW media. No go and I wasted about 20-30 minutes, while it was in a loop or stalled on M$ Windows. Then, I went back to CentOS and I was able to burn the files, without any problems. :-) Not sure what is causing the issues. Nothing grave, such as borked your box recently.
I struggled with this, trying as many ways as I could think of, and eventually thought it must be impossible. Then a couple of days ago I desperately needed a CD, and I'd run out of blanks. I put a CD-RW into the drive on a box where I hadn't used k3b before. K3b opened up with a tip-of-the-day - and miracle of miracles, it asked if I knew that I didn't need to erase the CD-RW as k3b could do it on the fly. I'd nothing to lose, so I asked it to burn the iso. It asked if I wanted it to blank the disc and use it. I got a clean, verified burn, and used the CD-RW to do an install!
Anne
On Sat, Jan 3, 2009 at 5:04 PM, Anne Wilson cannewilson@googlemail.com wrote:
On Saturday 03 January 2009 21:21:55 Lanny Marcus wrote:
<snip>
I do have an issue with k3b (CentOS 5.2, 32 bit), but nothing grave. I cannot erase CD-RW media with k3b, most or all of the time. I ran into that last night. Went to M$ Windows and I was able to erase the 2 CD-RW media, without any problem. Then, I tried to burn the files (which are M$ Windows files) to the CD-RW media. No go and I wasted about 20-30 minutes, while it was in a loop or stalled on M$ Windows. Then, I went back to CentOS and I was able to burn the files, without any problems. :-) Not sure what is causing the issues. Nothing grave, such as borked your box recently.
I struggled with this, trying as many ways as I could think of, and eventually thought it must be impossible. Then a couple of days ago I desperately needed a CD, and I'd run out of blanks. I put a CD-RW into the drive on a box where I hadn't used k3b before. K3b opened up with a tip-of-the-day - and miracle of miracles, it asked if I knew that I didn't need to erase the CD-RW as k3b could do it on the fly. I'd nothing to lose, so I asked it to burn the iso. It asked if I wanted it to blank the disc and use it. I got a clean, verified burn, and used the CD-RW to do an install!
Anne: Cool. Thanks. I will try that, the next time I use a CD-RW that has previously been used. I tried "Tools > Erase CD-RW" and it got stuck. Maybe it will just work, if I let it erase the media automatically, without me asking.... Lanny
On Saturday 03 January 2009 22:22:52 Lanny Marcus wrote:
On Sat, Jan 3, 2009 at 5:04 PM, Anne Wilson cannewilson@googlemail.com
wrote:
On Saturday 03 January 2009 21:21:55 Lanny Marcus wrote:
<snip>
I do have an issue with k3b (CentOS 5.2, 32 bit), but nothing grave. I cannot erase CD-RW media with k3b, most or all of the time. I ran into that last night. Went to M$ Windows and I was able to erase the 2 CD-RW media, without any problem. Then, I tried to burn the files (which are M$ Windows files) to the CD-RW media. No go and I wasted about 20-30 minutes, while it was in a loop or stalled on M$ Windows. Then, I went back to CentOS and I was able to burn the files, without any problems. :-) Not sure what is causing the issues. Nothing grave, such as borked your box recently.
I struggled with this, trying as many ways as I could think of, and eventually thought it must be impossible. Then a couple of days ago I desperately needed a CD, and I'd run out of blanks. I put a CD-RW into the drive on a box where I hadn't used k3b before. K3b opened up with a tip-of-the-day - and miracle of miracles, it asked if I knew that I didn't need to erase the CD-RW as k3b could do it on the fly. I'd nothing to lose, so I asked it to burn the iso. It asked if I wanted it to blank the disc and use it. I got a clean, verified burn, and used the CD-RW to do an install!
Anne: Cool. Thanks. I will try that, the next time I use a CD-RW that has previously been used. I tried "Tools > Erase CD-RW" and it got stuck.
That's what I found. If you find it works the same way as I saw, we should file a bug report.
Maybe it will just work, if I let it erase the media automatically, without me asking....
If you have a spare disk you might do a test burn, while it's on your mind? Let us know what happens.
Anne
On Sun, Jan 4, 2009 at 3:25 AM, Anne Wilson cannewilson@googlemail.com wrote:
On Saturday 03 January 2009 22:22:52 Lanny Marcus wrote:
I do have an issue with k3b (CentOS 5.2, 32 bit), but nothing grave. I cannot erase CD-RW media with k3b, most or all of the time. I ran into
<snip>
I struggled with this, trying as many ways as I could think of, and eventually thought it must be impossible. Then a couple of days ago I desperately needed a CD, and I'd run out of blanks. I put a CD-RW into the drive on a box where I hadn't used k3b before. K3b opened up with a tip-of-the-day - and miracle of miracles, it asked if I knew that I didn't need to erase the CD-RW as k3b could do it on the fly. I'd nothing to lose, so I asked it to burn the iso. It asked if I wanted it to blank the disc and use it. I got a clean, verified burn, and used the CD-RW to do an install!
<snip>
That's what I found. If you find it works the same way as I saw, we should file a bug report.
<snip>
If you have a spare disk you might do a test burn, while it's on your mind? Let us know what happens.
Anne: This seems OT and probably a bug report or a support request, on CentOS or at Upstream would be appropriate? This morning, I took two (2) CD-RW media, one Imation and one Verbatim, and I tried this. Each of them had four (4) photos on them, a few MB of stuff. No Joy here. I get different results than you do. When I hoped it would automatically erase the CD-RW, as it did for you, before writing new data, I got this Error: The disk is either empty or is not appendable".
When I tried Tools > Erase CD-RW (I tried Erase Fast, Complete and Last Session and got the same results), I got, "The Erasing process failed. Do you want to see the debugging output?". Below is that file. Should a bug or support request be filed about K3b? If so, where? Will you do that? I suspect that K3b a very widely used application. I was logged in as a normal user, not root. TIA, Lanny
System ----------------------- K3b Version: 0.12.17
KDE Version: 3.5.4-16.el5.centos CentOS QT Version: 3.3.6 Kernel: 2.6.18-92.1.22.el5 Devices ----------------------- SONY CD-RW CRX216E PD03 (/dev/hdd, ) at [CD-R; CD-RW; CD-ROM] [CD-ROM; CD-R; CD-RW] [SAO; TAO; RAW; SAO/R96P; SAO/R96R; RAW/R16; RAW/R96P; RAW/R96R]
HL-DT-ST DVD-ROM GDR8163B 0D20 (/dev/hdc, ) at [CD-ROM; DVD-ROM] [DVD-ROM; CD-ROM] [None] Used versions ----------------------- cdrecord: 2.1
cdrecord command: ----------------------- /usr/bin/cdrecord -v gracetime=2 dev=/dev/hdd speed=4 -tao driveropts=burnfree -eject -overburn blank=fast -force
cdrecord ----------------------- /usr/bin/cdrecord: Cannot allocate memory. WARNING: Cannot do mlockall(2).
/usr/bin/cdrecord: WARNING: This causes a high risk for buffer underruns. /usr/bin/cdrecord: Operation not permitted. WARNING: Cannot set RR-scheduler /usr/bin/cdrecord: Permission denied. WARNING: Cannot set priority using setpriority(). /usr/bin/cdrecord: WARNING: This causes a high risk for buffer underruns. scsidev: '/dev/hdd' devname: '/dev/hdd' scsibus: -2 target: -2 lun: -2 Error trying to open /dev/hdd exclusively ... retrying in 1 second. Error trying to open /dev/hdd exclusively ... retrying in 1 second. Error trying to open /dev/hdd exclusively ... retrying in 1 second. Error trying to open /dev/hdd exclusively ... retrying in 1 second. Error trying to open /dev/hdd exclusively ... retrying in 1 second. Error trying to open /dev/hdd exclusively ... retrying in 1 second. Error trying to open /dev/hdd exclusively ... retrying in 1 second. Error trying to open /dev/hdd exclusively ... retrying in 1 second. Error trying to open /dev/hdd exclusively ... retrying in 1 second. Error trying to open /dev/hdd exclusively ... retrying in 1 second. /usr/bin/cdrecord: Device or resource busy. Cannot open '/dev/hdd'. Cannot open SCSI driver. /usr/bin/cdrecord: For possible targets try 'cdrecord -scanbus'. Make sure you are root. /usr/bin/cdrecord: For possible transport specifiers try 'cdrecord dev=help'. Cdrecord-Clone 2.01 (cpu-pc-linux-gnu) Copyright (C) 1995-2004 Jörg Schilling Note: This version is an unofficial (modified) version with DVD support Note: and therefore may have bugs that are not present in the original. Note: Please send bug reports or support requests to http://bugzilla.redhat.com/bugzilla Note: The author of cdrecord should not be bothered with problems in this version. TOC Type: 1 = CD-ROM
Lanny Marcus wrote:
On Sun, Jan 4, 2009 at 3:25 AM, Anne Wilson cannewilson@googlemail.com wrote:
On Saturday 03 January 2009 22:22:52 Lanny Marcus wrote:
I do have an issue with k3b (CentOS 5.2, 32 bit), but nothing grave. I cannot erase CD-RW media with k3b, most or all of the time. I ran into
<snip> >>> I struggled with this, trying as many ways as I could think of, and >>> eventually thought it must be impossible. Then a couple of days ago I >>> desperately needed a CD, and I'd run out of blanks. I put a CD-RW into >>> the drive on a box where I hadn't used k3b before. K3b opened up with a >>> tip-of-the-day - and miracle of miracles, it asked if I knew that I >>> didn't need to erase the CD-RW as k3b could do it on the fly. I'd >>> nothing to lose, so I asked it to burn the iso. It asked if I wanted it >>> to blank the disc and use it. I got a clean, verified burn, and used the >>> CD-RW to do an install! <snip> > That's what I found. If you find it works the same way as I saw, we should > file a bug report. <snip> > If you have a spare disk you might do a test burn, while it's on your mind? > Let us know what happens.
Anne: This seems OT and probably a bug report or a support request, on CentOS or at Upstream would be appropriate? This morning, I took two (2) CD-RW media, one Imation and one Verbatim, and I tried this. Each of them had four (4) photos on them, a few MB of stuff. No Joy here. I get different results than you do. When I hoped it would automatically erase the CD-RW, as it did for you, before writing new data, I got this Error: The disk is either empty or is not appendable".
When I tried Tools > Erase CD-RW (I tried Erase Fast, Complete and Last Session and got the same results), I got, "The Erasing process failed. Do you want to see the debugging output?". Below is that file. Should a bug or support request be filed about K3b? If so, where? Will you do that? I suspect that K3b a very widely used application. I was logged in as a normal user, not root. TIA, Lanny
System
K3b Version: 0.12.17
KDE Version: 3.5.4-16.el5.centos CentOS QT Version: 3.3.6 Kernel: 2.6.18-92.1.22.el5 Devices
SONY CD-RW CRX216E PD03 (/dev/hdd, ) at [CD-R; CD-RW; CD-ROM] [CD-ROM; CD-R; CD-RW] [SAO; TAO; RAW; SAO/R96P; SAO/R96R; RAW/R16; RAW/R96P; RAW/R96R]
HL-DT-ST DVD-ROM GDR8163B 0D20 (/dev/hdc, ) at [CD-ROM; DVD-ROM] [DVD-ROM; CD-ROM] [None] Used versions
cdrecord: 2.1
cdrecord command:
/usr/bin/cdrecord -v gracetime=2 dev=/dev/hdd speed=4 -tao driveropts=burnfree -eject -overburn blank=fast -force
cdrecord
/usr/bin/cdrecord: Cannot allocate memory. WARNING: Cannot do mlockall(2).
/usr/bin/cdrecord: WARNING: This causes a high risk for buffer underruns. /usr/bin/cdrecord: Operation not permitted. WARNING: Cannot set RR-scheduler /usr/bin/cdrecord: Permission denied. WARNING: Cannot set priority using setpriority(). /usr/bin/cdrecord: WARNING: This causes a high risk for buffer underruns. scsidev: '/dev/hdd' devname: '/dev/hdd' scsibus: -2 target: -2 lun: -2 Error trying to open /dev/hdd exclusively ... retrying in 1 second. Error trying to open /dev/hdd exclusively ... retrying in 1 second. Error trying to open /dev/hdd exclusively ... retrying in 1 second. Error trying to open /dev/hdd exclusively ... retrying in 1 second. Error trying to open /dev/hdd exclusively ... retrying in 1 second. Error trying to open /dev/hdd exclusively ... retrying in 1 second. Error trying to open /dev/hdd exclusively ... retrying in 1 second. Error trying to open /dev/hdd exclusively ... retrying in 1 second. Error trying to open /dev/hdd exclusively ... retrying in 1 second. Error trying to open /dev/hdd exclusively ... retrying in 1 second. /usr/bin/cdrecord: Device or resource busy. Cannot open '/dev/hdd'. Cannot open SCSI driver. /usr/bin/cdrecord: For possible targets try 'cdrecord -scanbus'. Make sure you are root. /usr/bin/cdrecord: For possible transport specifiers try 'cdrecord dev=help'. Cdrecord-Clone 2.01 (cpu-pc-linux-gnu) Copyright (C) 1995-2004 Jörg Schilling Note: This version is an unofficial (modified) version with DVD support Note: and therefore may have bugs that are not present in the original. Note: Please send bug reports or support requests to http://bugzilla.redhat.com/bugzilla Note: The author of cdrecord should not be bothered with problems in this version. TOC Type: 1 = CD-ROM
I've seen this as well. I believe it happens because KDE (I guess GNOME would do the same) detects the disc, mounts it and opens a konqueror (fileviewer) window to graphically show the top-level directory. If that happens, k3b cannot open the device exclusively (that's what the error message says) and therefore cannot erase it.
The workaround is to a) wait until the fileviewer window comes up, b) close theat window c) unmount the disc (right-click on desktop icon) d) make sure it's no longer mounted, by saying "mount" in a shell window and inspecting the output carefully e) only then start k3b.
works for me.
HTH,
Kay
On Sun, Jan 4, 2009 at 7:57 AM, Kay Diederichs kay.diederichs@uni-konstanz.de wrote:
Lanny Marcus wrote:
On Sun, Jan 4, 2009 at 3:25 AM, Anne Wilson cannewilson@googlemail.com wrote:
On Saturday 03 January 2009 22:22:52 Lanny Marcus wrote:
I do have an issue with k3b (CentOS 5.2, 32 bit), but nothing grave. I cannot erase CD-RW media with k3b, most or all of the time. I ran into
<snip>
That's what I found. If you find it works the same way as I saw, we should file a bug report.
<snip>
I've seen this as well. I believe it happens because >KDE (I guess GNOME would do the same) detects the disc, mounts it and >opens a konqueror
Yes. I use GNOME. KDE is also installed, but it is very rare that I use KDE> <snip>
The workaround is to a) wait until the fileviewer window comes up, b) close theat window c) unmount the disc (right-click on desktop icon) d) make sure it's no longer mounted, by saying "mount" in a shell window and inspecting the output carefully e) only then start k3b. works for me.
Fred Smith mentioned unmounting the drive. I will try that and see if that works for me.
On Sunday 04 January 2009 11:50:55 Lanny Marcus wrote:
On Sun, Jan 4, 2009 at 3:25 AM, Anne Wilson cannewilson@googlemail.com
wrote:
On Saturday 03 January 2009 22:22:52 Lanny Marcus wrote:
I do have an issue with k3b (CentOS 5.2, 32 bit), but nothing grave. I cannot erase CD-RW media with k3b, most or all of the time. I ran into
<snip>
I struggled with this, trying as many ways as I could think of, and eventually thought it must be impossible. Then a couple of days ago I desperately needed a CD, and I'd run out of blanks. I put a CD-RW into the drive on a box where I hadn't used k3b before. K3b opened up with a tip-of-the-day - and miracle of miracles, it asked if I knew that I didn't need to erase the CD-RW as k3b could do it on the fly. I'd nothing to lose, so I asked it to burn the iso. It asked if I wanted it to blank the disc and use it. I got a clean, verified burn, and used the CD-RW to do an install!
<snip>
That's what I found. If you find it works the same way as I saw, we should file a bug report.
<snip>
If you have a spare disk you might do a test burn, while it's on your mind? Let us know what happens.
Anne: This seems OT and probably a bug report or a support request, on CentOS or at Upstream would be appropriate?
Before you can file a bug report that is likely to help get anything sorted, you have to be able to define the problem. At the moment I don't think you have done so.
This morning, I took two (2) CD-RW media, one Imation and one Verbatim, and I tried this. Each of them had four (4) photos on them, a few MB of stuff. No Joy here. I get different results than you do. When I hoped it would automatically erase the CD-RW, as it did for you, before writing new data, I got this Error: The disk is either empty or is not appendable".
When I tried Tools > Erase CD-RW (I tried Erase Fast, Complete and Last Session and got the same results), I got, "The Erasing process failed. Do you want to see the debugging output?". Below is that file. Should a bug or support request be filed about K3b? If so, where? Will you do that? I suspect that K3b a very widely used application. I was logged in as a normal user, not root. TIA, Lanny
System
K3b Version: 0.12.17
KDE Version: 3.5.4-16.el5.centos CentOS QT Version: 3.3.6 Kernel: 2.6.18-92.1.22.el5 Devices
SONY CD-RW CRX216E PD03 (/dev/hdd, ) at [CD-R; CD-RW; CD-ROM] [CD-ROM; CD-R; CD-RW] [SAO; TAO; RAW; SAO/R96P; SAO/R96R; RAW/R16; RAW/R96P; RAW/R96R]
HL-DT-ST DVD-ROM GDR8163B 0D20 (/dev/hdc, ) at [CD-ROM; DVD-ROM] [DVD-ROM; CD-ROM] [None] Used versions
cdrecord: 2.1
cdrecord command:
/usr/bin/cdrecord -v gracetime=2 dev=/dev/hdd speed=4 -tao driveropts=burnfree -eject -overburn blank=fast -force
cdrecord
/usr/bin/cdrecord: Cannot allocate memory. WARNING: Cannot do mlockall(2).
/usr/bin/cdrecord: WARNING: This causes a high risk for buffer underruns. /usr/bin/cdrecord: Operation not permitted. WARNING: Cannot set RR-scheduler /usr/bin/cdrecord: Permission denied. WARNING: Cannot set priority using setpriority(). /usr/bin/cdrecord: WARNING: This causes a high risk for buffer underruns. scsidev: '/dev/hdd' devname: '/dev/hdd' scsibus: -2 target: -2 lun: -2 Error trying to open /dev/hdd exclusively ... retrying in 1 second. Error trying to open /dev/hdd exclusively ... retrying in 1 second. Error trying to open /dev/hdd exclusively ... retrying in 1 second. Error trying to open /dev/hdd exclusively ... retrying in 1 second. Error trying to open /dev/hdd exclusively ... retrying in 1 second. Error trying to open /dev/hdd exclusively ... retrying in 1 second. Error trying to open /dev/hdd exclusively ... retrying in 1 second. Error trying to open /dev/hdd exclusively ... retrying in 1 second. Error trying to open /dev/hdd exclusively ... retrying in 1 second. Error trying to open /dev/hdd exclusively ... retrying in 1 second. /usr/bin/cdrecord: Device or resource busy. Cannot open '/dev/hdd'.
I agree with Kay that this implies that the drive is mounted. You MUST make sure that it isn't before using k3b.
Cannot open SCSI driver. /usr/bin/cdrecord: For possible targets try 'cdrecord -scanbus'. Make sure you are root. /usr/bin/cdrecord: For possible transport specifiers try 'cdrecord dev=help'. Cdrecord-Clone 2.01 (cpu-pc-linux-gnu) Copyright (C) 1995-2004 Jörg Schilling Note: This version is an unofficial (modified) version with DVD support Note: and therefore may have bugs that are not present in the original. Note: Please send bug reports or support requests to http://bugzilla.redhat.com/bugzilla Note: The author of cdrecord should not be bothered with problems in this version. TOC Type: 1 = CD-ROM
When and if you get this to the point when you can make a good report, that output tells you to do it at http://bugzilla.redhat.com/bugzilla. You might find it helpful to search bugzilla to see what has already been said about this.
Anne
On Sun, Jan 4, 2009 at 8:31 AM, Anne Wilson cannewilson@googlemail.com wrote:
On Sunday 04 January 2009 11:50:55 Lanny Marcus wrote:
On Saturday 03 January 2009 22:22:52 Lanny Marcus wrote:
I do have an issue with k3b (CentOS 5.2, 32 bit), but nothing grave. I cannot erase CD-RW media with k3b, most or all of the time. I ran
<snip>
I struggled with this, trying as many ways as I could think of, and eventually thought it must be impossible. Then a couple of days ago I desperately needed a CD, and I'd run out of blanks. I put a CD-RW into the drive on a box where I hadn't used k3b before. K3b opened up with a tip-of-the-day - and miracle of miracles, it asked if I knew that I didn't need to erase the CD-RW as k3b could do it on the fly. I'd nothing to lose, so I asked it to burn the iso. It asked if I wanted it to blank the disc and use it. I got a clean, verified burn, and used the CD-RW to do an install!
From reading that, I think that you did not unmount the media, before
that. Am I correct? If so, that does not work for me. I have tried this, logged in as a regular user and also logged in as root. Same results, so it is not a permissions problem.
Before you can file a bug report that is likely to help get anything sorted, you have to be able to define the problem. At the moment I don't think you have done so.
Correct. I believe Fred Smith is correct that the drive needs to be unmounted. I am going to try to do that and see what happens.
I agree with Kay that this implies that the drive is mounted. You MUST make sure that it isn't before using k3b.
OK. I will try to unmount /dev/hdd, before I launch K3b for the next attempt(s).
On Sunday 04 January 2009 14:23:55 Lanny Marcus wrote:
On Sun, Jan 4, 2009 at 8:31 AM, Anne Wilson cannewilson@googlemail.com
wrote:
On Sunday 04 January 2009 11:50:55 Lanny Marcus wrote:
On Saturday 03 January 2009 22:22:52 Lanny Marcus wrote:
> I do have an issue with k3b (CentOS 5.2, 32 bit), but nothing > grave. I cannot erase CD-RW media with k3b, most or all of the > time. I ran
<snip>
I struggled with this, trying as many ways as I could think of, and eventually thought it must be impossible. Then a couple of days ago I desperately needed a CD, and I'd run out of blanks. I put a CD-RW into the drive on a box where I hadn't used k3b before. K3b opened up with a tip-of-the-day - and miracle of miracles, it asked if I knew that I didn't need to erase the CD-RW as k3b could do it on the fly. I'd nothing to lose, so I asked it to burn the iso. It asked if I wanted it to blank the disc and use it. I got a clean, verified burn, and used the CD-RW to do an install!
From reading that, I think that you did not unmount the media, before
that. Am I correct?
No. Perhaps I did not make it clear. I did not allow the disk to be mounted. The tip opened up when k3b recognised the disk, which has nothing to do with mounting. If you can't avoid mounting the disk, then you must umount it before attempting to use it with k3b.
Anne
On Sun, Jan 4, 2009 at 9:46 AM, Anne Wilson cannewilson@googlemail.com wrote:
>> I do have an issue with k3b (CentOS 5.2, 32 >bit), but nothing >> >> >> >> grave. I cannot erase >CD-RW media with k3b, most or all of the
> I struggled with this, trying as many ways as I >could think of, and > eventually thought it must be impossible. > Then a couple of days > ago I desperately needed a CD, and I'd run >out of blanks. I put a > CD-RW into the drive on a box where I hadn't >used k3b before. K3b > opened up with a tip-of-the-day - and miracle >of miracles, it asked > if I knew that I didn't need to erase the >CD-RW as k3b could do it > on the fly. I'd nothing to lose, so I asked it to >burn the iso. It > asked if I wanted it to blank the disc and use >it. I got a clean, > verified burn, and used the CD-RW to do an >install!
<snip>
No. Perhaps I did not make it clear. I did not allow the >disk to be mounted. The tip opened up when k3b recognised the disk, which >has nothing to do with mounting. If you can't avoid mounting the disk, then you >must umount it before attempting to use it with k3b.
OK. I've made some tests and if you believe that anything I ran into warrants a bug or support request against K3b, on CentOS.org and/or RedHat.com please tell me.
I opened a terminal window, "su -" and then "umount /dev/hdd" and then I exited from the shell.
(a) I can use the drop down menu, "Tools" > "Erase CD-RW", without any problem.
(b) I can write new files to the CD-RW. I did not get a message, asking me if I wanted it to erase the CD-RW media. It did *not* erase the existing files on the CD-RW media, before writing the new files. It added the new files, as if the CD-RW were a multi session disk.
(c) In the K3b list of files in my home directory (/home/lanny) it showed files that had been deleted previously.
On Sunday 04 January 2009 16:19:46 Lanny Marcus wrote:
On Sun, Jan 4, 2009 at 9:46 AM, Anne Wilson cannewilson@googlemail.com
wrote:
> >> I do have an issue with k3b (CentOS 5.2, 32 >bit), but nothing > >> >> >> >> >> grave. I cannot erase >CD-RW media with k3b, most > >> or all of the > > > > I struggled with this, trying as many ways as I >could think of, > > and eventually thought it must be impossible. > Then a couple of > > days ago I desperately needed a CD, and I'd run >out of blanks. > > I put a CD-RW into the drive on a box where I hadn't >used k3b > > before. K3b opened up with a tip-of-the-day - and miracle >of > > miracles, it asked if I knew that I didn't need to erase the > > >CD-RW as k3b could do it on the fly. I'd nothing to lose, so I > > asked it to >burn the iso. It asked if I wanted it to blank the > > disc and use >it. I got a clean, verified burn, and used the > > CD-RW to do an >install!
<snip>
No. Perhaps I did not make it clear. I did not allow the >disk to be mounted. The tip opened up when k3b recognised the disk, which >has nothing to do with mounting. If you can't avoid mounting the disk, then you >must umount it before attempting to use it with k3b.
OK. I've made some tests and if you believe that anything I ran into warrants a bug or support request against K3b, on CentOS.org and/or RedHat.com please tell me.
I opened a terminal window, "su -" and then "umount /dev/hdd" and then I exited from the shell.
(a) I can use the drop down menu, "Tools" > "Erase CD-RW", without any problem.
That seems to prove that it's simply a mount problem.
(b) I can write new files to the CD-RW. I did not get a message, asking me if I wanted it to erase the CD-RW media. It did *not* erase the existing files on the CD-RW media, before writing the new files. It added the new files, as if the CD-RW were a multi session disk.
Probably you only get that message when it needs a whole disk, like burning an iso (bootable).
(c) In the K3b list of files in my home directory (/home/lanny) it showed files that had been deleted previously.
Not sure what you mean there, but maybe it's relelvant that any files in your wastebin are still actually there in your home directory? I've never seen anything that makes me suspect a problem with this - never seen files that I believed to be deleted.
You need to know if anyone else has seen this problem, before reporting it.
Anne
On Sun, Jan 4, 2009 at 11:57 AM, Anne Wilson cannewilson@googlemail.com wrote:
>> >> I do have an issue with k3b (CentOS 5.2, 32 >bit), but nothing >> >> >> >> >> >> grave. I cannot erase >CD-RW media with k3b, most >> >> or all of the > > I struggled with this, trying as many ways as I >could think of, >> > and eventually thought it must be impossible. > Then a couple of >> > days ago I desperately needed a CD, and I'd run >out of blanks. >> > I put a CD-RW into the drive on a box where I hadn't >used k3b >> > before. K3b opened up with a tip-of-the-day - and miracle >of >> > miracles, it asked if I knew that I didn't need to erase the >> > >CD-RW as k3b could do it on the fly. I'd nothing to lose, so I >> > asked it to >burn the iso. It asked if I wanted it to blank the >> > disc and use >it. I got a clean, verified burn, and used the >> > CD-RW to do an >install!
<snip> OK. I've made some tests and if you believe that anything I ran into warrants a bug or support request against K3b, on CentOS.org and/or RedHat.com please tell me.
I opened a terminal window, "su -" and then "umount /dev/hdd" and then I exited from the shell.
(a) I can use the drop down menu, "Tools" > "Erase CD-RW", without any problem.
That seems to prove that it's simply a mount problem.
Yes.
(b) I can write new files to the CD-RW. I did not get a message, asking me if I wanted it to erase the CD-RW media. It did *not* erase the existing files on the CD-RW media, before writing the new files. It added the new files, as if the CD-RW were a multi session disk.
Probably you only get that message when it needs a whole disk, like burning an iso (bootable).
I wonder why it did not erase the four (4) photos I had on the CD-RW media, before it wrote the two (2) files I wanted it to write? There are now six (6) files on the CD-RW media. No problem, it was only a test, but I assumed, incorrectly, as usual when I assume, that it would erase the CD-RW, before writing the files I wanted it to write to the CD-RW.
(c) In the K3b list of files in my home directory (/home/lanny) it showed files that had been deleted previously.
Not sure what you mean there, but maybe it's relelvant that any files in your wastebin are still actually there in your home directory? I've never seen anything that makes me suspect a problem with this - never seen files that I believed to be deleted.
When you use K3b to create a Data disc (CD-R, CD-RW, etc) it shows a list of files to choose from. In this case, I previously had two (2) files in my home directory and when I used K3b to make the tests this morning, they were shown. However, if I look at my home directory, they are not shown, even if I tell Nautilus to show Hidden files.
You need to know if anyone else has seen this problem, before reporting it.
That last one is trivial. If you think it is OK (or even "normal") that it did not offer to erase the CD-RW media before writing the new files, or, that it did not erase the old files, I will not report it. Maybe that behavior is what the program is expected to do.
On Sunday 04 January 2009 18:30:40 Lanny Marcus wrote:
On Sun, Jan 4, 2009 at 11:57 AM, Anne Wilson cannewilson@googlemail.com
wrote:
> >> >> I do have an issue with k3b (CentOS 5.2, 32 >bit), but > >> >> nothing > >> >> > >> >> >> >> >> >> grave. I cannot erase >CD-RW media with k3b, > >> >> >> >> >> >> most > >> >> > >> >> or all of the >> > >> > I struggled with this, trying as many ways as I >could think >> > of, >> > > >> > and eventually thought it must be impossible. > Then a couple > >> > of days ago I desperately needed a CD, and I'd run >out of > >> > blanks. I put a CD-RW into the drive on a box where I hadn't > >> > >used k3b before. K3b opened up with a tip-of-the-day - and > >> > miracle >of miracles, it asked if I knew that I didn't need > >> > to erase the > >> > > >> > >CD-RW as k3b could do it on the fly. I'd nothing to lose, so > >> > > I > >> > > >> > asked it to >burn the iso. It asked if I wanted it to blank > >> > the disc and use >it. I got a clean, verified burn, and used > >> > the CD-RW to do an >install!
<snip> OK. I've made some tests and if you believe that anything I ran into warrants a bug or support request against K3b, on CentOS.org and/or RedHat.com please tell me.
I opened a terminal window, "su -" and then "umount /dev/hdd" and then I exited from the shell.
(a) I can use the drop down menu, "Tools" > "Erase CD-RW", without any problem.
That seems to prove that it's simply a mount problem.
Yes.
(b) I can write new files to the CD-RW. I did not get a message, asking me if I wanted it to erase the CD-RW media. It did *not* erase the existing files on the CD-RW media, before writing the new files. It added the new files, as if the CD-RW were a multi session disk.
Probably you only get that message when it needs a whole disk, like burning an iso (bootable).
I wonder why it did not erase the four (4) photos I had on the CD-RW media, before it wrote the two (2) files I wanted it to write? There are now six (6) files on the CD-RW media. No problem, it was only a test, but I assumed, incorrectly, as usual when I assume, that it would erase the CD-RW, before writing the files I wanted it to write to the CD-RW.
(c) In the K3b list of files in my home directory (/home/lanny) it showed files that had been deleted previously.
Not sure what you mean there, but maybe it's relelvant that any files in your wastebin are still actually there in your home directory? I've never seen anything that makes me suspect a problem with this - never seen files that I believed to be deleted.
When you use K3b to create a Data disc (CD-R, CD-RW, etc) it shows a list of files to choose from. In this case, I previously had two (2) files in my home directory and when I used K3b to make the tests this morning, they were shown. However, if I look at my home directory, they are not shown, even if I tell Nautilus to show Hidden files.
You need to know if anyone else has seen this problem, before reporting it.
That last one is trivial. If you think it is OK (or even "normal") that it did not offer to erase the CD-RW media before writing the new files, or, that it did not erase the old files, I will not report it. Maybe that behavior is what the program is expected to do.
I think it *is* expected behaviour. After all, you don't want it to erase anything without warning. I think you had a disk that is not finalized (do CD-RW disks finalize? I don't know) therefore it could append the file. There was nothing in what you were doing to make it suspect that it shouldn't do so.
I'm not an expert in these matters, but it seems to me that that is what has happened, and is quite normal. Now if you have an iso downloaded anywhere you might try burning an image, and see if that asks you about deleting. I'll bet it does.
Anne
On Sun, Jan 4, 2009 at 1:47 PM, Anne Wilson cannewilson@googlemail.com wrote:
On Sunday 04 January 2009 18:30:40 Lanny Marcus wrote:
On Sun, Jan 4, 2009 at 11:57 AM, Anne Wilson cannewilson@googlemail.com
wrote:
>> >> >> I do have an issue with k3b (CentOS 5.2, 32 >bit), but >> >> >> nothing >> >> >> >> >> >> >> grave. I cannot erase >CD-RW media with k3b, >> >> >> >> >> >> >> most >> >> >> or all of the > >> > > >> > I struggled with this, trying as many ways as I >could think >> >> > and eventually thought it must be impossible. > Then a couple >> >> > of days ago I desperately needed a CD, and I'd run >out of >> >> > blanks. I put a CD-RW into the drive on a box where I hadn't >> >> > >used k3b before. K3b opened up with a tip-of-the-day - and >> >> > miracle >of miracles, it asked if I knew that I didn't need >> >> > to erase the
I think it *is* expected behaviour. After all, you don't want it to erase anything without warning. I think you had a disk that is not finalized (do CD-RW disks finalize? I don't know) therefore it could append the file. There was nothing in what you were doing to make it suspect that it shouldn't do so.
Yes. Normally, one is asked, before data are deleted. I am not sure whether or not CD-RW media finalize (there's another word for that?). I think so, because they seem to have something done to them, after the data are written to the media.
I'm not an expert in these matters, but it seems to me that that is what has happened, and is quite normal. Now if you have an iso downloaded anywhere you might try burning an image, and see if that asks you about deleting. I'll bet it does.
I'll Download an .iso and see if I am asked whether or not I want to erase the media before writing the .iso to it.
On Sun, Jan 04, 2009 at 11:19:46AM -0500, Lanny Marcus wrote:
On Sun, Jan 4, 2009 at 9:46 AM, Anne Wilson cannewilson@googlemail.com wrote:
> >> I do have an issue with k3b (CentOS 5.2, 32 >bit), but nothing >> >> >> >> grave. I cannot erase >CD-RW media with k3b, most or all of the
> > I struggled with this, trying as many ways as I >could think of, and > > eventually thought it must be impossible. > Then a couple of days > > ago I desperately needed a CD, and I'd run >out of blanks. I put a > > CD-RW into the drive on a box where I hadn't >used k3b before. K3b > > opened up with a tip-of-the-day - and miracle >of miracles, it asked > > if I knew that I didn't need to erase the >CD-RW as k3b could do it > > on the fly. I'd nothing to lose, so I asked it to >burn the iso. It > > asked if I wanted it to blank the disc and use >it. I got a clean, > > verified burn, and used the CD-RW to do an >install!
<snip> > No. Perhaps I did not make it clear. I did not allow the >disk to be mounted. > The tip opened up when k3b recognised the disk, which >has nothing to do with > mounting. If you can't avoid mounting the disk, then you >must umount it > before attempting to use it with k3b.
OK. I've made some tests and if you believe that anything I ran into warrants a bug or support request against K3b, on CentOS.org and/or RedHat.com please tell me.
I opened a terminal window, "su -" and then "umount /dev/hdd" and then I exited from the shell.
(a) I can use the drop down menu, "Tools" > "Erase CD-RW", without any problem.
(b) I can write new files to the CD-RW. I did not get a message, asking me if I wanted it to erase the CD-RW media. It did *not* erase
There is an option in K3B to automatically erase RW media when it finds one in its drive. You have to set that option or else it defaults to not erasing it (and not asking you).
On the Settings menu, Configure K3B, Writing, Advanced, is a checkbox labeled "Automatically erase CD-RWs and DVD-RWs". If that's not checked it won't automatically erase it, and if it IS checked, it will ask you first.
On Sun, Jan 4, 2009 at 3:14 PM, fred smith fredex@fcshome.stoneham.ma.us wrote: <snip>
There is an option in K3B to automatically erase RW media when it finds one in its drive. You have to set that option or else it defaults to not erasing it (and not asking you).
On the Settings menu, Configure K3B, Writing, Advanced, is a checkbox labeled "Automatically erase CD-RWs and DVD-RWs". If that's not checked it won't automatically erase it, and if it IS checked, it will ask you first.
Thank you. I now have that box checked.
Lanny Marcus wrote:
OK. I've made some tests and if you believe that anything I ran into warrants a bug or support request against K3b, on CentOS.org and/or RedHat.com please tell me.
redhat probably. We saw similar issue(s) in fedora awhile back, and patched k3b to auto-demount media (using gnome-mount)... rhel's k3b builds probably ought to do something similar.
-- Rex
On Sun, Jan 4, 2009 at 3:37 PM, Rex Dieter rdieter@math.unl.edu wrote:
Lanny Marcus wrote:
OK. I've made some tests and if you believe that anything I ran into warrants a bug or support request against K3b, on CentOS.org and/or RedHat.com please tell me.
redhat probably. We saw similar issue(s) in fedora awhile back, and patched >k3b to auto-demount media (using gnome-mount)... rhel's k3b builds probably >ought to do something similar.
What is the procedure for reporting? Seems like within the past few weeks there was something about how to do this. First report to CentOS Bugzilla and then report to RedHat Bugzilla and cross reference them?
On Sun, Jan 04, 2009 at 04:05:02PM -0500, Lanny Marcus wrote:
On Sun, Jan 4, 2009 at 3:37 PM, Rex Dieter rdieter@math.unl.edu wrote:
Lanny Marcus wrote:
OK. I've made some tests and if you believe that anything I ran into warrants a bug or support request against K3b, on CentOS.org and/or RedHat.com please tell me.
redhat probably. We saw similar issue(s) in fedora awhile back, and patched >k3b to auto-demount media (using gnome-mount)... rhel's k3b builds probably >ought to do something similar.
What is the procedure for reporting? Seems like within the past few weeks there was something about how to do this. First report to CentOS Bugzilla and then report to RedHat Bugzilla and cross reference them?
Lanny, AFAIK, you would go to bugzilla.redhat.com or perhaps the Centos bugzilla (if not at bugzilla.centos.org, then the centos.org web site would contain a pointer to it).
If you're reporting a bug in Centos, I'd think it should go to the Centos bugzilla who will then (eventually???) forward it to redhat. However it may be worth looking at redhat's bugzilla to see if they already have it. If so you could just add your voice to the throng.
On Sun, Jan 4, 2009 at 6:25 PM, fred smith fredex@fcshome.stoneham.ma.us wrote:
On Sun, Jan 04, 2009 at 04:05:02PM -0500, Lanny Marcus wrote:
On Sun, Jan 4, 2009 at 3:37 PM, Rex Dieter rdieter@math.unl.edu wrote:
Lanny Marcus wrote:
OK. I've made some tests and if you believe that anything I ran into warrants a bug or support request against K3b, on CentOS.org and/or RedHat.com please tell me.
redhat probably. We saw similar issue(s) in fedora awhile back, and patched >k3b to auto-demount media (using gnome-mount)... rhel's k3b builds probably >ought to do something similar.
What is the procedure for reporting? Seems like within the past few weeks there was something about how to do this. First report to CentOS Bugzilla and then report to RedHat Bugzilla and cross reference them?
Lanny, AFAIK, you would go to bugzilla.redhat.com or perhaps the Centos bugzilla (if not at bugzilla.centos.org, then the centos.org web site would contain a pointer to it).
If you're reporting a bug in Centos, I'd think it should go to the Centos bugzilla who will then (eventually???) forward it to redhat. However it may be worth looking at redhat's bugzilla to see if they already have it. If so you could just add your voice to the throng.
Good idea. I will try to find it on Redhat's Bugzilla, before I post it. Thanks! Probably it is in RHEL and we got it from them....
On Sun, Jan 04, 2009 at 09:23:55AM -0500, Lanny Marcus wrote:
On Sun, Jan 4, 2009 at 8:31 AM, Anne Wilson cannewilson@googlemail.com wrote:
On Sunday 04 January 2009 11:50:55 Lanny Marcus wrote:
On Saturday 03 January 2009 22:22:52 Lanny Marcus wrote:
> I do have an issue with k3b (CentOS 5.2, 32 bit), but nothing grave. > I cannot erase CD-RW media with k3b, most or all of the time. I ran
<snip> >> >> > I struggled with this, trying as many ways as I could think of, and >> >> > eventually thought it must be impossible. Then a couple of days ago I >> >> > desperately needed a CD, and I'd run out of blanks. I put a CD-RW >> >> > into the drive on a box where I hadn't used k3b before. K3b opened up >> >> > with a tip-of-the-day - and miracle of miracles, it asked if I knew >> >> > that I didn't need to erase the CD-RW as k3b could do it on the fly. >> >> > I'd nothing to lose, so I asked it to burn the iso. It asked if I >> >> > wanted it to blank the disc and use it. I got a clean, verified burn, >> >> > and used the CD-RW to do an install!
From reading that, I think that you did not unmount the media, before
that. Am I correct? If so, that does not work for me. I have tried this, logged in as a regular user and also logged in as root. Same results, so it is not a permissions problem.
Before you can file a bug report that is likely to help get anything sorted, you have to be able to define the problem. At the moment I don't think you have done so.
Correct. I believe Fred Smith is correct that the drive needs to be unmounted. I am going to try to do that and see what happens.
I agree with Kay that this implies that the drive is mounted. You MUST make sure that it isn't before using k3b.
OK. I will try to unmount /dev/hdd, before I launch K3b for the next attempt(s).
I firmly remember that at times in the past K3B would automaticlaly unmount the CD when it was about to erase or otherwise write to it, but on my current system (centos 5) it does not. I've not really investigated to find out why (though I certainly should).
On Wed, Dec 31, 2008 at 1:27 PM, MHR mhullrich@gmail.com wrote:
I have been having some strange results trying to burn CDs under CentOS. I don't think they are hardware related because I have had some success, in fact most of this usually works.
I use k3b for most of my CD and DVD writing - it seems to work fairly well (well, except for wrecking my installation a few weeks ago when it crashed my installation and I had to reinstall to get it back, but that's old news).
<snip> A follow on to my previous replies about K3b. Yesterday, I purchased an LG DVD Burner for my Daughter's box. This morning I installed it and I tested it with K3b on CentOS 5 (32 bit). No problem writing a DVD with it. Since your problem is on your box at work and no problem on the other box you tested there, or, on your desktop at home, I wonder if there is some glitch in the drive in that box and that it is a HW issue. Or, some glitch with K3b on that box. If you are brave enough to uninstall K3b and then install it again, maybe the problem will go away. Do you have another DVD Burner at work you can install in that box, to see if you get the same results? My experience is that K3b is pretty solid. Also, maybe there is a problem with the EIDE cable to that drive? Have you checked to see that the connectors are seated properly?
-
Anne Wilson -
fred smith -
Kay Diederichs -
Lanny Marcus -
MHR -
Michael A. Peters -
Rex Dieter -
Robert Moskowitz -
William L. Maltby