Re: [newbie] can't eject cd after burning
On Fri, Mar 21, 2003 at 11:11:30AM -0600, Tom Brinkman wrote: On Friday March 21 2003 08:33 am, Richard Urwin wrote: $ eject /dev/scd0# Came out, went back in again $ sudo umount -l /mnt/cdrom2 Password: $ eject /dev/scd0# Came out, stayed out Here again, I don't think it was the 'umount' that did the trick. Konqueror's hold on the device had probly expired by then. IME, even tho you had already closed Konqueror, it still takes some time to release. A CDr can't be mounted, since you can only mount filesystems. There ain't one on blank CDr's (or images like audio CD's) ;) After you burned it, and then checked with a file manager, supermount did mount it, and it was probly Konq that took it's sweet damn time lettin it go. While I grant that that sequence took thirty seconds or so, and things may have changed between the two ejects, that was a lot less time than I took fiddling with it last night. I don't know about GUI's, but all my CL solutions (biso, bacd, bdcd) contain 'eject'. ie, alias bdcd='cdrecord -v -eject speed=4 dev=0,0,0 -data' So the CDr is immediately ejected right after fixating is finished. Then to check the CD, I push the drawer back in and bring it up in a terminal and do a 'ls' on it, or use a file manager like Konqueror. Then I either wait a while, or if I'm impatient, use 'eject /dev/scd0' to retrieve it. 'man eject' says If the device is currently mounted, it is unmounted before ejecting. Maybe in your case it's havin trouble over riding Konq's hold? Doesn't happen to me, I suspect it could be permissions. What's your msec level? I run at msec 2 just so my system doesn't argue with me about what I wanna do ; To tell the truth, 'bout the only time my burner won't give up a CD is after doin 'md5sum /dev/scd0' to check the integrity of burned iso's. 'eject' always gets it for me tho ;) An update on the non-ejecting business. I don't have supermount enabled, so that can't be it. The other suggestions have not worked, either. BUT, after burning a few more CDs, it seems that I only have this problem when I use -overburn. So until I can eject after overburning, that's my story and I'm sticking to it! Todd Want to buy your Pack or Services from MandrakeSoft? Go to http://www.mandrakestore.com
Re: [newbie] can't eject cd after burning
On Friday March 21 2003 07:16 pm, Chris wrote: Hello Tom I don't know about GUI's, but all my CL solutions (biso, bacd, bdcd) contain 'eject'. ie, alias bdcd='cdrecord -v -eject speed=4 dev=0,0,0 -data' So the CDr is immediately ejected right after fixating is finished. Then to check the CD, I push the drawer back in and bring it up in a terminal and do a 'ls' on it, or use a file manager like Konqueror. Then I either wait a while, or if I'm impatient, use 'eject /dev/scd0' to retrieve it. Tom, that alias you showed me how to setup is working great, lots better using the CL than a gui, guess it takes me back to my MSDOS days. Question though, .mp3' would be burnt as data files correct? Yes With 'data' files like .mp3's (or .jpg's, .avi's, .mpg's, .mov's, etc.) I copy them to a directory and make sure I haven't exceeded the target CDr size (usually 700mb's). Then I create an image with 'mkcdimg /directory' (alias mkcdimg='mkisofs -r -o cd_image'). Then 'bdcd cd_image' puts the whole sh'bang on a CDr. No runs, no drips, no errors :) Also, this problem he's having with the cd not ejecting, I notice he keeps mentioning he has supermount enabled, maybe if he disabled it? I had problems with being able to copy multiple files from my cd's to the hd before I disabled it here, since then I've had no problems. Supermount is not the problem. It's just a convenient scapegoat for user or hardware deficiencies. -- Tom Brinkman Corpus Christi, Texas Want to buy your Pack or Services from MandrakeSoft? Go to http://www.mandrakestore.com
Re: [newbie] can't eject cd after burning
On Friday 21 Mar 2003 1:29 pm, Tom Brinkman wrote: On Thursday March 20 2003 05:16 pm, Richard Urwin wrote: I have just had exactly the same problem. Wrote a CDRW in GCombust, finished OK, wouldn't eject the CD. lsof reported that nothing on the cd was open. ie lsof|grep cdrom2 and lsof|grep scd0 both reported nothing. Seeing that nothing was open I unmounted it with umount -l /mnt/cdrom2 and that at least gave me my cd back. Everything appeared fairly sane I think. The jury is still out as to whether I can burn another CD following this one, and I'm no expert about what I might have broken with that unmount. I did have supermount enabled. CDr's are not mounted for burning. So 'umount' isn't part of the equation. I did open the CD in Konquerer immediately after the burn, just to make sure the data was there. This time through I closed GCombust first. (And closed konquerer before trying to eject, of course.) It's likely just coincidental that by the time you ran that command, whatever has holding on to the burner had released it. Next time try 'eject /dev/scd0' (or scd? depending on which ? your burner is). 'Course if you're burning as root (you shouldn't be) you'll need to run the eject command as root. $ eject /dev/scd0# Came out, went back in again $ sudo umount -l /mnt/cdrom2 Password: $ eject /dev/scd0# Came out, stayed out While I grant that that sequence took thirty seconds or so, and things may have changed between the two ejects, that was a lot less time than I took fiddling with it last night. It stands to reason that the burner must lock the drive closed while the burn is happening. I don't know how that happens. Even if it isn't a mount it might still have a similar effect on the top level mount/umount/eject functionality. Supermount has been vastly improved in 9.1. Specially if you use the premptable, low latency kernel found in contribs (2.4.21-0.16mm). OTOH, supermount isn't involved in this problem since CDr's are not mounted for burning anyway. The reason I'm doing this is to archive off my files so when I load 9.1, hopefully next week, I can nuke and pave, and this time get the partitions right so I don't have to do it next time. Not that a few backups now and then aren't a good thing ;-) -- Richard Urwin Want to buy your Pack or Services from MandrakeSoft? Go to http://www.mandrakestore.com
Re: [newbie] can't eject cd after burning
On Friday 21 Mar 2003 2:33 pm, Richard Urwin wrote: On Friday 21 Mar 2003 1:29 pm, Tom Brinkman wrote: On Thursday March 20 2003 05:16 pm, Richard Urwin wrote: I did open the CD in Konquerer immediately after the burn, just to make sure the data was there. This time through I closed GCombust first. (And closed konquerer before trying to eject, of course.) I experience this open/fast close from time to time after browsing cds. It is clear that you must make abosolutely certain that no Konqueror windows are open before you try to eject. I think it would also mean that you must not be browsing the directory in a shell, either. Still there appear to be times when that isn't enough. Sometimes it sorts itself out after a while, but if it gets stuck, I generally log out, then in again. It's likely just coincidental that by the time you ran that command, whatever has holding on to the burner had released it. Next time try 'eject /dev/scd0' (or scd? depending on which ? your burner is). 'Course if you're burning as root (you shouldn't be) you'll need to run the eject command as root. $ eject /dev/scd0# Came out, went back in again $ sudo umount -l /mnt/cdrom2 Password: $ eject /dev/scd0# Came out, stayed out While I grant that that sequence took thirty seconds or so, and things may have changed between the two ejects, that was a lot less time than I took fiddling with it last night. It stands to reason that the burner must lock the drive closed while the burn is happening. I don't know how that happens. Even if it isn't a mount it might still have a similar effect on the top level mount/umount/eject functionality. I don't burn from the command line. Both XCDRoast and K3b have a setting to eject on completion, and I always use that. Anne -- Registered Linux User No.293302 Want to buy your Pack or Services from MandrakeSoft? Go to http://www.mandrakestore.com
Re: [newbie] can't eject cd after burning
I've just gone through the process again. On Friday 21 Mar 2003 3:28 pm, Anne Wilson wrote: On Friday 21 Mar 2003 2:33 pm, Richard Urwin wrote: On Friday 21 Mar 2003 1:29 pm, Tom Brinkman wrote: On Thursday March 20 2003 05:16 pm, Richard Urwin wrote: I did open the CD in Konquerer immediately after the burn, just to make sure the data was there. This time through I closed GCombust first. (And closed konquerer before trying to eject, of course.) I experience this open/fast close from time to time after browsing cds. It is clear that you must make abosolutely certain that no Konqueror windows are open before you try to eject. I think it would also mean that you must not be browsing the directory in a shell, either. Still there appear to be times when that isn't enough. Sometimes it sorts itself out after a while, but if it gets stuck, I generally log out, then in again. This time I closed GCombust and ejected the CD before opening konquerer. Once from the button on the drive, once using eject. Both worked perfectly. Then I opened the CD using konquerer. No files. I then mounted the CD by hand (sudo mount /mnt/cdrom2.) The files appeared. Then I tried to eject the CD. No dice, the button is ignored and eject does the now-you-see-it-now-you-dont routine. I unmounted the CD by hand. The first time it refused device is busy. But it had only just retracted, and the drive was probably reading the index. I waited a second or two and the second umount worked. This time I got everything working without the -l flag to umount, so that is probably a red herring. My guess is that a standard umount will work, so long as you give it a while after a failed eject. Supermount was enabled at all times. Conclusion: Burning CDs can confuse supermount. Expect to mount/umount by hand. Wait for the drive to finish following a failed eject. I have finished my backups for now. I'll leave it to others to determine if ejecting and reinserting the disk after burning but before trying to read it reduces problems. It's likely just coincidental that by the time you ran that command, whatever has holding on to the burner had released it. Next time try 'eject /dev/scd0' (or scd? depending on which ? your burner is). 'Course if you're burning as root (you shouldn't be) you'll need to run the eject command as root. $ eject /dev/scd0# Came out, went back in again $ sudo umount -l /mnt/cdrom2 Password: $ eject /dev/scd0# Came out, stayed out While I grant that that sequence took thirty seconds or so, and things may have changed between the two ejects, that was a lot less time than I took fiddling with it last night. It stands to reason that the burner must lock the drive closed while the burn is happening. I don't know how that happens. Even if it isn't a mount it might still have a similar effect on the top level mount/umount/eject functionality. I don't burn from the command line. Both XCDRoast and K3b have a setting to eject on completion, and I always use that. GCombust is GUI, and was installed with MDK9.0 XCDRoast did not seem to be able to construct a CD, just to copy one. I may be wrong. Anne -- Richard Urwin Want to buy your Pack or Services from MandrakeSoft? Go to http://www.mandrakestore.com
Re: [newbie] can't eject cd after burning
On Friday 21 Mar 2003 3:53 pm, Richard Urwin wrote: I've just gone through the process again. On Friday 21 Mar 2003 3:28 pm, Anne Wilson wrote: On Friday 21 Mar 2003 2:33 pm, Richard Urwin wrote: On Friday 21 Mar 2003 1:29 pm, Tom Brinkman wrote: On Thursday March 20 2003 05:16 pm, Richard Urwin wrote: This time I closed GCombust and ejected the CD before opening konquerer. Wise, I think. Once from the button on the drive, once using eject. Both worked perfectly. Then I opened the CD using konquerer. No files. I then mounted the CD by hand (sudo mount /mnt/cdrom2.) The files appeared. Then I tried to eject the CD. No dice, the button is ignored and eject does the now-you-see-it-now-you-dont routine. I unmounted the CD by hand. The first time it refused device is busy. But it had only just retracted, and the drive was probably reading the index. I waited a second or two and the second umount worked. This time I got everything working without the -l flag to umount, so that is probably a red herring. My guess is that a standard umount will work, so long as you give it a while after a failed eject. Part of the problem is probably the longish spin-up spin-down time with modern faster drives. Supermount was enabled at all times. Conclusion: Burning CDs can confuse supermount. Expect to mount/umount by hand. Wait for the drive to finish following a failed eject. Which fits with my experience that it sometimes clears itself if left along. I have finished my backups for now. I'll leave it to others to determine if ejecting and reinserting the disk after burning but before trying to read it reduces problems. GCombust is GUI, and was installed with MDK9.0 OK - I haven't used it. XCDRoast did not seem to be able to construct a CD, just to copy one. I may be wrong. I use it all the time for backing up files. If you want to either post to list or direct to me, I will make some notes and give you a HOW-TO. Anne -- Registered Linux User No.293302 Want to buy your Pack or Services from MandrakeSoft? Go to http://www.mandrakestore.com
Re: [newbie] can't eject cd after burning
On Friday 21 Mar 2003 4:02 pm, Anne Wilson wrote: I use it all the time for backing up files. If you want to either post to list or direct to me, I will make some notes and give you a HOW-TO. Anne Ahh! Master Tracks. Now I see. How un-intuitive. -- Richard Urwin Want to buy your Pack or Services from MandrakeSoft? Go to http://www.mandrakestore.com
Re: [newbie] can't eject cd after burning
On Friday 21 Mar 2003 4:12 pm, Richard Urwin wrote: On Friday 21 Mar 2003 4:02 pm, Anne Wilson wrote: I use it all the time for backing up files. If you want to either post to list or direct to me, I will make some notes and give you a HOW-TO. Anne Ahh! Master Tracks. Now I see. How un-intuitive. 'Tis, a bit g That said, I find it very easy to use. I like the ability to add a directory, check the size of the burn, exclude inessentials for a later burn if it's too big, and so on. I have K3b installed, and it's pretty, but somehow I can't use it with the same ease. That's great, though, for tasks such as burning an iso, so there advantages in having both. Anne -- Registered Linux User No.293302 Want to buy your Pack or Services from MandrakeSoft? Go to http://www.mandrakestore.com
Re: [newbie] can't eject cd after burning
On Friday 21 Mar 2003 4:18 pm, Anne Wilson wrote: ... I find it very easy to use. I like the ability to add a directory, check the size of the burn, exclude inessentials for a later burn if it's too big, and so on. I have K3b installed, and it's pretty, but somehow I can't use it with the same ease. That's great, though, for tasks such as burning an iso, so there advantages in having both. Anne GCombust has a button that suggests which directories to remove to shrink the image down below the size of the CD while wasting the minimum amount of space. What would be useful is if you could mark those directories as not in the current image, but have them hang around until you did the next burn, so you don't forget which ones you've done, or more likely, haven't. -- Richard Urwin Want to buy your Pack or Services from MandrakeSoft? Go to http://www.mandrakestore.com
Re: [newbie] can't eject cd after burning
On Friday 21 Mar 2003 4:30 pm, Richard Urwin wrote: On Friday 21 Mar 2003 4:18 pm, Anne Wilson wrote: ... I find it very easy to use. I like the ability to add a directory, check the size of the burn, exclude inessentials for a later burn if it's too big, and so on. I have K3b installed, and it's pretty, but somehow I can't use it with the same ease. That's great, though, for tasks such as burning an iso, so there advantages in having both. Anne GCombust has a button that suggests which directories to remove to shrink the image down below the size of the CD while wasting the minimum amount of space. That sounds useful What would be useful is if you could mark those directories as not in the current image, but have them hang around until you did the next burn, so you don't forget which ones you've done, or more likely, haven't. Excluded files/subdirectories are clearly marked with a red arrow in the selection page, which can be returned to when you've finished. (Since it can eject at the end of the burn, you can just keep the program open.) I then note down those excluded ones, clear the list, and start by putting those at the head of the list. Anne -- Registered Linux User No.293302 Want to buy your Pack or Services from MandrakeSoft? Go to http://www.mandrakestore.com
Re: [newbie] can't eject cd after burning
On Friday 21 Mar 2003 4:33 pm, Anne Wilson wrote: On Friday 21 Mar 2003 4:30 pm, Richard Urwin wrote: On Friday 21 Mar 2003 4:18 pm, Anne Wilson wrote: ... I find it very easy to use. I like the ability to add a directory, check the size of the burn, exclude inessentials for a later burn if it's too big, and so on. I have K3b installed, and it's pretty, but somehow I can't use it with the same ease. That's great, though, for tasks such as burning an iso, so there advantages in having both. Anne GCombust has a button that suggests which directories to remove to shrink the image down below the size of the CD while wasting the minimum amount of space. That sounds useful What would be useful is if you could mark those directories as not in the current image, but have them hang around until you did the next burn, so you don't forget which ones you've done, or more likely, haven't. Excluded files/subdirectories are clearly marked with a red arrow in the selection page, which can be returned to when you've finished. (Since it can eject at the end of the burn, you can just keep the program open.) I then note down those excluded ones, clear the list, and start by putting those at the head of the list. Anne Almost perfect! But why not a clear all but excluded files button. GCombust can only delete them out of the image, and since they're automatically chosen I'd imagine that they'd be scattered throughout the image - so a lot of writing. It can save the current file list, but not the marked subset of it, or invert the selection. Either of those would have been enough. I suppose it's open source. If I wanted it badly enough I'd add it. -- Richard Urwin Want to buy your Pack or Services from MandrakeSoft? Go to http://www.mandrakestore.com
Re: [newbie] can't eject cd after burning
On Friday March 21 2003 08:33 am, Richard Urwin wrote: $ eject /dev/scd0# Came out, went back in again $ sudo umount -l /mnt/cdrom2 Password: $ eject /dev/scd0# Came out, stayed out Here again, I don't think it was the 'umount' that did the trick. Konqueror's hold on the device had probly expired by then. IME, even tho you had already closed Konqueror, it still takes some time to release. A CDr can't be mounted, since you can only mount filesystems. There ain't one on blank CDr's (or images like audio CD's) ;) After you burned it, and then checked with a file manager, supermount did mount it, and it was probly Konq that took it's sweet damn time lettin it go. While I grant that that sequence took thirty seconds or so, and things may have changed between the two ejects, that was a lot less time than I took fiddling with it last night. I don't know about GUI's, but all my CL solutions (biso, bacd, bdcd) contain 'eject'. ie, alias bdcd='cdrecord -v -eject speed=4 dev=0,0,0 -data' So the CDr is immediately ejected right after fixating is finished. Then to check the CD, I push the drawer back in and bring it up in a terminal and do a 'ls' on it, or use a file manager like Konqueror. Then I either wait a while, or if I'm impatient, use 'eject /dev/scd0' to retrieve it. 'man eject' says If the device is currently mounted, it is unmounted before ejecting. Maybe in your case it's havin trouble over riding Konq's hold? Doesn't happen to me, I suspect it could be permissions. What's your msec level? I run at msec 2 just so my system doesn't argue with me about what I wanna do ; To tell the truth, 'bout the only time my burner won't give up a CD is after doin 'md5sum /dev/scd0' to check the integrity of burned iso's. 'eject' always gets it for me tho ;) -- Tom Brinkman Corpus Christi, Texas Want to buy your Pack or Services from MandrakeSoft? Go to http://www.mandrakestore.com
Re: [newbie] can't eject cd after burning
On Friday 21 Mar 2003 5:11 pm, Tom Brinkman wrote: I don't know about GUI's, but all my CL solutions (biso, bacd, bdcd) contain 'eject'. ie, alias bdcd='cdrecord -v -eject speed=4 dev=0,0,0 -data' So the CDr is immediately ejected right after fixating is finished. Then to check the CD, I push the drawer back in and bring it up in a terminal and do a 'ls' on it, or use a file manager like Konqueror. Then I either wait a while, or if I'm impatient, use 'eject /dev/scd0' to retrieve it. 'man eject' says If the device is currently mounted, it is unmounted before ejecting. Maybe in your case it's havin trouble over riding Konq's hold? Doesn't happen to me, I suspect it could be permissions. What's your msec level? I run at msec 2 just so my system doesn't argue with me about what I wanna do ; To tell the truth, 'bout the only time my burner won't give up a CD is after doin 'md5sum /dev/scd0' to check the integrity of burned iso's. 'eject' always gets it for me tho ;) msec is 3. The eject option is probably the way to go. The disk is reinserted as a valid filesystem rather than suddenly turning into one. -- Richard Urwin Want to buy your Pack or Services from MandrakeSoft? Go to http://www.mandrakestore.com
Re: [newbie] can't eject cd after burning
On Friday 21 March 2003 10:53 am, Richard Urwin wrote: Supermount was enabled at all times. Conclusion: Burning CDs can confuse supermount. Expect to mount/umount by hand. Wait for the drive to finish following a failed eject. What is happining is the following cd is finished burning (but not mounted) supermount sees that a valid cd is in the drive, and then mounts it cd is now mounted. This is one of the main reasons that i do not use supermount. -- Alex / KC2IVL ft100 software for Linux http://www.qsl.net/kc2ivl Good judgment comes from experience, and a lot of that comes from bad judgment Want to buy your Pack or Services from MandrakeSoft? Go to http://www.mandrakestore.com
Re: [newbie] can't eject cd after burning
On Fri, 21 Mar 2003 13:05:22 -0500 A V Flinsch [EMAIL PROTECTED] wrote: What is happining is the following cd is finished burning (but not mounted) supermount sees that a valid cd is in the drive, and then mounts it cd is now mounted. This is one of the main reasons that i do not use supermount. This is not a global problem, though. I've always used supermount with Mandrake and never had a problem with locked trays (or anything else, for that matter). Miark Want to buy your Pack or Services from MandrakeSoft? Go to http://www.mandrakestore.com
Re: [newbie] can't eject cd after burning
On Tuesday 18 Mar 2003 10:29 pm, darklord wrote: On Tuesday 18 March 2003 11:06 am, Todd Slater wrote: Yeah, I've tried eject. I probably had some ROX-filer windows open but I can't say for sure. Todd Todd, have you tried lsof /dev/device (or /mnt/device) to see what still has a hold of it? Might help point the way. :-) I have just had exactly the same problem. Wrote a CDRW in GCombust, finished OK, wouldn't eject the CD. lsof reported that nothing on the cd was open. ie lsof|grep cdrom2 and lsof|grep scd0 both reported nothing. Seeing that nothing was open I unmounted it with umount -l /mnt/cdrom2 and that at least gave me my cd back. Everything appeared fairly sane I think. The jury is still out as to whether I can burn another CD following this one, and I'm no expert about what I might have broken with that unmount. I did have supermount enabled. (My drive is a Dyson 1622 (ages old!) and the Media is CMC badged as Memorex.) -- Richard Urwin Want to buy your Pack or Services from MandrakeSoft? Go to http://www.mandrakestore.com
Re: [newbie] can't eject cd after burning
have you tried: #cdrecord -reset bascule How do I turn the recorder off and on again? cdrdao says it has finished the burn successfully. Thanks, Todd -- One's never alone with a rubber duck. Want to buy your Pack or Services from MandrakeSoft? Go to http://www.mandrakestore.com
Re: [newbie] can't eject cd after burning
On Tuesday 18 March 2003 04:14, Todd Slater wrote: Using cdrdao, with the --eject flag, sometimes after burning the green light on the cd burner flashes, but I am unable to eject it. But sometimes it does eject. This is annoying because right now the only way I know to get the CD out is to reboot :(. The burner is an HP CD-Writer Plus. Todd Had something similar a while back. Turned out the writer never stopped writing/working because the CD-rw disc itself was bad. It happens a lot with too cheap discs. Good luck, HarM Want to buy your Pack or Services from MandrakeSoft? Go to http://www.mandrakestore.com
Re: [newbie] can't eject cd after burning
On some sites you can see quality tests of different CD-Rs. I found that TDK reflex, Sony or Verbatin CD-Rs are good. Also note that CD-Rewritables can only safely burnt at 4x speed, even if noticed otherwise (The Verbatin CDRWs say 24x, but my system always said 4x was the max when inserting such a disk, same with the Sony CDRWs but those also said max 4x on the cover :). If you get such a problem again you can also turn the recorder off and then on again to eject the CD by button. I doubt if the system recognises the drive again without reboot after doing that. You can at least try to start cdrdao after doing that. On 3/18/03 9:38 AM, H.J.Bathoorn [EMAIL PROTECTED] wrote: On Tuesday 18 March 2003 04:14, Todd Slater wrote: Using cdrdao, with the --eject flag, sometimes after burning the green light on the cd burner flashes, but I am unable to eject it. But sometimes it does eject. This is annoying because right now the only way I know to get the CD out is to reboot :(. The burner is an HP CD-Writer Plus. Todd Had something similar a while back. Turned out the writer never stopped writing/working because the CD-rw disc itself was bad. It happens a lot with too cheap discs. Good luck, HarM Want to buy your Pack or Services from MandrakeSoft? Go to http://www.mandrakestore.com Want to buy your Pack or Services from MandrakeSoft? Go to http://www.mandrakestore.com
Re: [newbie] can't eject cd after burning
On Monday 17 March 2003 10:14 pm, Todd Slater wrote: Using cdrdao, with the --eject flag, sometimes after burning the green light on the cd burner flashes, but I am unable to eject it. But sometimes it does eject. This is annoying because right now the only way I know to get the CD out is to reboot :(. The burner is an HP CD-Writer Plus. Todd have you tried eject /mnt/cdrom or whereever the cdrom is mounted, and at the time, do you have any file manager windows open? -- Linux counter number 167806 Want to buy your Pack or Services from MandrakeSoft? Go to http://www.mandrakestore.com
Re: [newbie] can't eject cd after burning
How about if you type the following at the command line? eject /mnt/cdrom or if that doesn't work how about umount /mnt/cdrom eject /mnt/cdrom I tried that and still no go. After burning it seems it's not mounted. I tried mounting it and couldn't--unknown filesystem and none specified. It's known as cdrom2. Todd Can you take a look at the processes running while your're burning and afterward? Does some process still have control of the device? -- Anthony Abby http://www.comicsnsuch | Comic Community News http://www.aplusdata.com | System Consultation Web Development Want to buy your Pack or Services from MandrakeSoft? Go to http://www.mandrakestore.com
Re: [newbie] can't eject cd after burning
On Monday March 17 2003 11:31 pm, Todd Slater wrote: or if that doesn't work how about umount /mnt/cdrom eject /mnt/cdrom I tried that and still no go. After burning it seems it's not mounted. I tried mounting it and couldn't--unknown filesystem and none specified. It's known as cdrom2. Todd CDr's aren't mounted for burning, so umount isn't the problem. Maybe cdrdao is. Dunno, I always use cdrecord. Every once in a while my Plextor doesn't wanna give up a CD. Try, eject /dev/scd0That always worksforme ;) -- Tom Brinkman Corpus Christi, Texas Want to buy your Pack or Services from MandrakeSoft? Go to http://www.mandrakestore.com
Re: [newbie] can't eject cd after burning
On Tuesday March 18 2003 05:00 am, Leendert wrote: On some sites you can see quality tests of different CD-Rs. I found that TDK reflex, Sony or Verbatin CD-Rs are good. The problem with this advice is that CDr's are rarely manufactured by the 'brand' name they're sold under. I had one 50 spindle of TDK's that were about 1/2 Ritek's, the other 1/2 made by CMC Magnetics. Every spindle of Verbatim's I've had were CMC Magnetics. Ritek and CMC are OK, but Taiyo Yuden's are better. Fuji Film CDr's are made by Taiyo Yuden. Office Max near me sells their own brand which are actually CMC's, the same CDR's as the Verbatim's they sell, but at almost half the price. The problem with them is the coated side (label side) isn't as durable as the name brand CDr's. It's the coated side that is actually the side where recording is done. If you put a blank CDr in your burner, and type tom$ cdrecord -atip dev=0,0,0 Cdrecord 2.0 (i586-mandrake-linux-gnu) Copyright (C) 1995-2002 Jörg Schilling scsidev: '0,0,0' scsibus: 0 target: 0 lun: 0 Linux sg driver version: 3.1.24 Using libscg version 'schily-0.7' Device type: Removable CD-ROM Version: 0 Response Format: 1 Vendor_info: 'PLEXTOR ' Identifikation : 'CD-R PX-W8432T' Revision : '1.09' Device seems to be: Generic mmc CD-RW. Using generic SCSI-3/mmc CD-R driver (mmc_cdr). Driver flags : MMC SWABAUDIO Supported modes: TAO PACKET SAO SAO/R96P SAO/R96R RAW/R16 RAW/R96P RAW/R96R ATIP info from disk: Indicated writing power: 4 Is not unrestricted Is not erasable Disk sub type: Medium Type A, low Beta category (A-) (2) ATIP start of lead in: -12508 (97:15/17) ATIP start of lead out: 359845 (79:59/70) Disk type:Short strategy type (Phthalocyanine or similar) Manuf. index: 22 Manufacturer: Ritek Co. That was from a Maxell brand 700 mb CDr. Just about all the CDr's sold are made by Ritek, CMC, or Ty-U. IME, Ritek = good, CMC = better Taiyo Yuden = best. -- Tom Brinkman Corpus Christi, Texas Want to buy your Pack or Services from MandrakeSoft? Go to http://www.mandrakestore.com
Re: [newbie] can't eject cd after burning
On Tuesday 18 March 2003 11:06 am, Todd Slater wrote: Yeah, I've tried eject. I probably had some ROX-filer windows open but I can't say for sure. Todd Todd, have you tried lsof /dev/device (or /mnt/device) to see what still has a hold of it? Might help point the way. :-) Want to buy your Pack or Services from MandrakeSoft? Go to http://www.mandrakestore.com
[newbie] can't eject cd after burning
Using cdrdao, with the --eject flag, sometimes after burning the green light on the cd burner flashes, but I am unable to eject it. But sometimes it does eject. This is annoying because right now the only way I know to get the CD out is to reboot :(. The burner is an HP CD-Writer Plus. Todd Want to buy your Pack or Services from MandrakeSoft? Go to http://www.mandrakestore.com
Re: [newbie] can't eject cd after burning
Todd Slater said: Using cdrdao, with the --eject flag, sometimes after burning the green light on the cd burner flashes, but I am unable to eject it. But sometimes it does eject. This is annoying because right now the only way I know to get the CD out is to reboot :(. The burner is an HP CD-Writer Plus. Todd How about if you type the following at the command line? eject /mnt/cdrom or if that doesn't work how about umount /mnt/cdrom eject /mnt/cdrom -- Anthony Abby http://www.comicsnsuch | Comic Community News http://www.aplusdata.com | System Consultation Web Development Want to buy your Pack or Services from MandrakeSoft? Go to http://www.mandrakestore.com
Re: [newbie] can't eject cd after burning
On Mon, 17 Mar 2003 22:28:27 -0500 (EST) Anthony Abby [EMAIL PROTECTED] wrote: Todd Slater said: Using cdrdao, with the --eject flag, sometimes after burning the green light on the cd burner flashes, but I am unable to eject it. But sometimes it does eject. This is annoying because right now the only way I know to get the CD out is to reboot :(. The burner is an HP CD-Writer Plus. Todd How about if you type the following at the command line? eject /mnt/cdrom or if that doesn't work how about umount /mnt/cdrom eject /mnt/cdrom I tried that and still no go. After burning it seems it's not mounted. I tried mounting it and couldn't--unknown filesystem and none specified. It's known as cdrom2. Todd Want to buy your Pack or Services from MandrakeSoft? Go to http://www.mandrakestore.com