hal messing up cd fs type [SOLVED]

[pjv]

When I insert any (data) cdrom/cdr I get an error popup in gnome saying:

Code: Select all

mount: wrong fs type, bad option, bad superblock on /dev/hda,
missing codepage or other error
In some cases useful info is found in syslog - try
dmesg|tail or so 

I should however get a successful automount here. When I try to do it manually it works perfectly, so it isn't a problem with hardware, fstab, or any core drivers:

Code: Select all

mount -t auto /dev/hda /media/cd

This was working before I had put back a backup of the whole system. I already had some small problems with wrong permissions for system files and directories (such as .so files and things in /usr/share/). I'm guessing this has the same cause however I cannot pinpoint the problem. I'm pretty sure a real fresh hal doesn't have this problem. I already tried emerge -c and then reemerge of several things: hal, dbus, some of hal's deps.

The hald debug output has nothing that looks to be wrong, except maybe:

Code: Select all

[19045]: 15:15:02.782 [D] probe-storage.c:303: Doing open ("/dev/hda", O_RDONLY | O_NONBLOCK | O_EXCL)
[19045]: 15:15:02.785 [D] probe-storage.c:315: Open failed - Device Busy
[19045]: 15:15:02.885 [D] probe-storage.c:319: Attempting open w/ O_EXCL again
[19045]: 15:15:02.887 [D] probe-storage.c:333: PROBE HAS EXCLUSIVE LOCK ON CDROM
[19045]: 15:15:02.891 [D] probe-storage.c:375: media size = 736882688
[19045]: 15:15:02.892 [D] probe-storage.c:383: PROBE CLOSED LOCK ON CDROM
...
15:15:05.613 [I] hald.c:107: Added device to GDL; udi=/org/freedesktop/Hal/devices/volume_label_BACKUP28
[30165]: 15:15:06.780 [I] addon-storage.c:346: Checking whether device /dev/hda is locked on HAL
[30165]: 15:15:06.780 [I] addon-storage.c:354: ... device /dev/hda is not locked on HAL

On a higher level the problem clearly is hal is not doing "mount -t auto /dev/hda /media/cd" or "mount -t iso9660 /dev/hda /media/cd" itself. But why? Any thoughts without blaming me if some random system file has wrong permissions? Thx, pjv.

PS: Anyone know a good way to reemerge the whole system (reinstalling without erasing everything) while also repairing wrong permissions of files and dirs?[/code]

[baaann]

I had this problem both with cdrom and usb stick. I spent ages seaching and re-emerging/updating packages without success. It was only after giving up and thinking it was easier to live with it, that I recalled that when installing Gentoo fstab does not contain an entry for a usb stick, but my fstab did. So I commented out the entries for cdrom and usb stick and it worked as it should. The only thing I can think of causing this in my case, is a recent power outage that presumably left hal settings that should have been removed.

Not working

Code: Select all

# <fs>          	<mountpoint>    <type>  	<opts>      		<dump/pass>

# NOTE: If your BOOT partition is ReiserFS, add the notail option to opts.
/dev/hda1		/boot		ext2		defaults,noatime	1 2
/dev/hda5		/		reiserfs	noatime			0 1
/dev/hda2		none		swap		sw			0 0
/dev/cdroms/cdrom0	/mnt/cdrom	auto		noauto,ro,user		0 0
/dev/fd0		/mnt/floppy	auto		noauto,user		0 0
/dev/hda6		/home		reiserfs	noatime			0 2

# NOTE: The next line is critical for boot!
none			/proc		proc		defaults		0 0

# glibc 2.2 and above expects tmpfs to be mounted at /dev/shm for
# POSIX shared memory (shm_open, shm_unlink). 
# (tmpfs is a dynamically expandable/shrinkable ramdisk, and will
#  use almost no memory if not populated with files)
# Adding the following line to /etc/fstab should take care of this:

none			/dev/shm	tmpfs		defaults		0 0

/dev/sda1               /media/usbdisk          vfat    user,exec,noauto,utf8,noatime,sync,managed 0 0
/dev/hdd                /media/cdrom            auto    user,exec,noauto,managed 0 0

Working

Code: Select all

# <fs>          	<mountpoint>    <type>  	<opts>      		<dump/pass>

# NOTE: If your BOOT partition is ReiserFS, add the notail option to opts.
/dev/hda1		/boot		ext2		defaults,noatime	1 2
/dev/hda5		/		reiserfs	noatime			0 1
/dev/hda2		none		swap		sw			0 0
/dev/cdroms/cdrom0	/mnt/cdrom	auto		noauto,ro,user		0 0
/dev/fd0		/mnt/floppy	auto		noauto,user		0 0
/dev/hda6		/home		reiserfs	noatime			0 2

# NOTE: The next line is critical for boot!
none			/proc		proc		defaults		0 0

# glibc 2.2 and above expects tmpfs to be mounted at /dev/shm for
# POSIX shared memory (shm_open, shm_unlink). 
# (tmpfs is a dynamically expandable/shrinkable ramdisk, and will
#  use almost no memory if not populated with files)
# Adding the following line to /etc/fstab should take care of this:

none			/dev/shm	tmpfs		defaults		0 0

#/dev/sda1               /media/usbdisk          vfat    user,exec,noauto,utf8,noatime,sync,managed 0 0
#/dev/hdd                /media/cdrom            auto    user,exec,noauto,managed 0 0

[pjv]

Heh, that was quick. I was looking in the wrong direction.

The culprit is the "managed" option, that you had also and that I must have added when restoring the backup. Remove it (only that word) in your fstab and it's solved.

Thanks for the insight!

[xiber]

Posted something abit a go trying to find out why util-linux-2.13-r2 is nolonger patched to ignore "managed" in fstab.

http://forums.gentoo.org/viewtopic-t-65 ... ight-.html