Can't eject a previously mounted CD?
Hi Vojtech,
I suspect this problem has something to do with my nForce2 motherboard. When I mount a CD, unmount it, and try to eject it from my drive, the drive flashes the red 'busy / locked' light and refuses to let me eject it. I'm using the AMD / nVidia IDE kernel support and the obvious conclusion is that it's failing to release the device or something. Is this true?
I suspect the fix would be a one liner.
Signature · 1 line
Joshua Kwan
Quoted 6 lines · Joshua Kwan
I suspect this problem has something to do with my nForce2 motherboard. When I mount a CD, unmount it, and try to eject it from my drive, the drive flashes the red 'busy / locked' light and refuses to let me eject it. I'm using the AMD / nVidia IDE kernel support and the obvious conclusion is that it's failing to release the device or something. Is this true?
No. :) There isn't anything in that driver that'd be called upon mount or unmount, it just sets the timings on boottime or when hdparm is called.
Quoted 1 line
I suspect the fix would be a one liner.
If you're using SUSE 9.0 ...
kill suseplugger
... perhaps?
Signature · 2 lines
Vojtech Pavlik SuSE Labs, SuSE CR
Quoted 1 line · Vojtech Pavlik
If you're using SUSE 9.0 ...
No, Debian.
The reason I said it was something to do with my motherboard is that I've not experienced this before, even on another motherboard with the original nForce.
Traditionally (as in Windows), the only thing that would keep the CD from being ejected is an ongoing recording session. Of course, in Linux, it just has to be mounted, and that's normal behavior. Just that the drive doesn't want to eject my CD even after unmounting it. Does that mean that this is a userspace problem?
Signature · 1 line
Joshua Kwan
Quoted 11 lines · Joshua Kwan
Quoted 1 line · Vojtech Pavlik
If you're using SUSE 9.0 ...
No, Debian.
The reason I said it was something to do with my motherboard is that I've not experienced this before, even on another motherboard with the original nForce.
Quoted 6 lines
Traditionally (as in Windows), the only thing that would keep the CD from being ejected is an ongoing recording session. Of course, in Linux, it just has to be mounted, and that's normal behavior. Just that the drive doesn't want to eject my CD even after unmounting it. Does that mean that this is a userspace problem?
What does fuser -kv /mnt/cdrom claim?
Signature · 4 lines
There is no such thing as obsolete hardware. Merely hardware that other people don't want. (The Second Rule of Hardware Acquisition) Sam Flory <[email protected]>
Quoted 1 line · Samuel Flory
What does fuser -kv
/mnt/cdromclaim?
It's /cdrom here. I tried it on both /cdrom and /dev/cdrom after unmounting it, and the output was blank.
While mounted, here was the output:
USER PID ACCESS COMMAND
/cdrom root kernel mount /cdrom
No automatic removal. Please use umount /cdrom
I guess that doesn't say much though...
Signature · 1 line
Joshua Kwan
I've had 2.6.0-mm1 not able to allow the button on the cdrom eject the cd. the command eject however, does work. No errors are reported relating to why the eject button on the cdrom doesn't eject the cd.
Quoted 16 lines · Joshua Kwan
Quoted 1 line · Samuel Flory
What does fuser -kv
/mnt/cdromclaim?It's /cdrom here. I tried it on both /cdrom and
/dev/cdromafter unmounting it, and the output was blank.While mounted, here was the output:
USER PID ACCESS COMMAND
/cdrom root kernel mount /cdrom
No automatic removal. Please use umount /cdromI guess that doesn't say much though...
Quoted 2 lines · Ed Sweetman
I've had 2.6.0-mm1 not able to allow the button on the cdrom eject the cd. the command eject however, does work. No errors are reported relating to why the eject button on the cdrom doesn't eject the cd.
This happens to me too, running 2.6.0-mm1. Even a music CD gets stuck and can only be ejected with the "eject" command. eject, after ejecting sucessfully the CD outputs this:
# eject eject: unable to eject, last error: Invalid argument #
Regards,
Nuno Silva
Quoted 29 lines
Quoted 9 lines · Joshua Kwan
Quoted 1 line · Samuel Flory
What does fuser -kv
/mnt/cdromclaim?It's /cdrom here. I tried it on both /cdrom and
/dev/cdromafter unmounting it, and the output was blank.Quoted 8 lines
While mounted, here was the output:
USER PID ACCESS COMMAND
/cdrom root kernel mount /cdrom
No automatic removal. Please use umount /cdromI guess that doesn't say much though...
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Quoted 7 lines · Nuno Silva
This happens to me too, running 2.6.0-mm1. Even a music CD gets stuck and can only be ejected with the "eject" command. eject, after ejecting sucessfully the CD outputs this:
# eject eject: unable to eject, last error: Invalid argument #
Exactly! This must be a -mm problem then... Andrew?
Signature · 1 line
Joshua Kwan
Quoted 8 lines · Joshua Kwan
Quoted 1 line · Samuel Flory
What does fuser -kv
/mnt/cdromclaim?It's /cdrom here. I tried it on both /cdrom and
/dev/cdromafter unmounting it, and the output was blank.
Quoted 8 lines
While mounted, here was the output:
USER PID ACCESS COMMAND
/cdrom root kernel mount /cdrom
No automatic removal. Please use umount /cdromI guess that doesn't say much though...
It does seem to imply that the cdrom is still mounted, or that
something thinks it's still mounted.
Quoted 17 lines · Samuel Flory
Quoted 15 lines · Joshua Kwan
Quoted 1 line · Samuel Flory
What does fuser -kv
/mnt/cdromclaim?It's /cdrom here. I tried it on both /cdrom and
/dev/cdromafter unmounting it, and the output was blank.While mounted, here was the output:
USER PID ACCESS COMMAND
/cdrom root kernel mount /cdrom
No automatic removal. Please use umount /cdrom
Quoted 5 lines
Quoted 2 lines
I guess that doesn't say much though...
It does seem to imply that the cdrom is still mounted, or that
something thinks it's still mounted.
I dont believe this unable to eject problem has anything to do with anything thinking it's mounted.
famd upon load seems to cause this error.end_request: I/O error, dev hdc, sector 0
That's my cdrom. Perhaps the kernel has a bug in the code dealing with an access to the cdrom where no media is mounted and/or loaded. Either way, this is at boot and seems to be a kernel bug initiated by FAM. At least the version distributed with debian-unstable. I dont use gnome (i do have some gnome programs installed to test on) and the error message was reported soon after the loading of FAM.
Does everyone who has this problem by chance have it occuring on an atapi cd recorder. As of 2.6.0-mm1 my cd recorder is being labeled read only by the ide-cd driver. Meaning, no matter if i set the readonly flag in hdparm to 0, cdrecord and others will refuse to write to the drive because it's being told it's read only. I do not have fam loaded at the time of this testing. Are there new ide-cd arguments required to use atapi cd writers in native mode?
Quoted 35 lines · Ed Sweetman
Quoted 18 lines · Samuel Flory
Quoted 16 lines · Joshua Kwan
Quoted 1 line · Samuel Flory
What does fuser -kv
/mnt/cdromclaim?It's /cdrom here. I tried it on both /cdrom and
/dev/cdromafter unmounting it, and the output was blank.While mounted, here was the output:
USER PID ACCESS COMMAND
/cdrom root kernel mount /cdrom
No automatic removal. Please use umount /cdromQuoted 5 lines
Quoted 2 lines
I guess that doesn't say much though...
It does seem to imply that the cdrom is still mounted, or that
something thinks it's still mounted.I dont believe this unable to eject problem has anything to do with anything thinking it's mounted.
famd upon load seems to cause this error.
end_request: I/O error, dev hdc, sector 0That's my cdrom. Perhaps the kernel has a bug in the code dealing with an access to the cdrom where no media is mounted and/or loaded. Either way, this is at boot and seems to be a kernel bug initiated by FAM. At least the version distributed with debian-unstable. I dont use gnome (i do have some gnome programs installed to test on) and the error message was reported soon after the loading of FAM.