Re: Fedora screwing up cdrom (Gnome, or nautilus, won't unmount cdrom)

From: H. S. (h_55_am_at_linuxmail.org)
Date: 11/12/03 

Date: Tue, 11 Nov 2003 22:27:05 -0500

Ohmster wrote:
> "H. S." <h_55_am@linuxmail.org> wrote in
> news:GITrb.1631$xI2.112476@news20.bellglobal.com:
>
>
>>I am using Fedora Core 1 running gnome. I have noticed that Gnome is not
>>ejecting my cdroms. It does if I eject it soon after I put it in, but if
>>I try after some time it just plain refuses to give back my CDROM!
>>umount doesn't work (no, I am NOT in /mnt/cdrom), eject doesn't work,
>>and neither does "umount -f".
>>
>>Anybody know what is going on? I hate having to reboot everytime I want
>>my disc back!
>
>
> I had a similar problem with redhat and my cdrom. The system was slowing to a
> crawl and the cd would not work. Checking /var/log/messages showed the cd
> constantly being accessed and getting error messages. I fixed it by taking
> the automount out of /etc/fstab so that the cdrom entry looks like this now:
>
> /dev/cdrom /mnt/cdrom iso9660 user,ro,mode=444,noauto 0 0
>
> Not sure if this is your problem but if you check the messages file and you
> get it filled with scssi crap, you will know it.
>

Mine fstab has:
/dev/cdrom /mnt/cdrom udf,iso9660 noauto,owner,kudzu,ro 0 0

and my system log has entries (leading date and machine are truncated to
shorten the length):
ACPI: RSDP (v000 ASUS ) @ 0x000f75a0
ACPI: RSDT (v001 ASUS <P4B> 0x42302e31 MSFT 0x31313031) @ 0x0fffc000
ACPI: FADT (v001 ASUS <P4B> 0x42302e31 MSFT 0x31313031) @ 0x0fffc100
ACPI: BOOT (v001 ASUS <P4B> 0x42302e31 MSFT 0x31313031) @ 0x0fffc040
ACPI: MADT (v001 ASUS <P4B> 0x42302e31 MSFT 0x31313031) @ 0x0fffc080
ACPI: DSDT (v001 ASUS <P4B> 0x00001000 MSFT 0x0100000b) @ 0x00000000
Kernel command line: ro root=LABEL=/ hdd=ide-scsi rhgb

->HS 

-- 
(Remove all underscores from my email address to get the correct one. 
Apologies for the inconvenience, but this is to reduce spam.)

Relevant Pages