Bugzilla – Bug 461786
system cannot mount any additional file systems
Last modified: 2009-02-04 10:48:16 UTC
If I connect an USB stick, USD disk drive, Firewire disk, ... the automounter fails. Note: A new device file is created, linked with a proper name, but not mounted. After attempting to mount manually, the mount command hangs forever. Inspection of the process table shows that there are two hanging mount processes: mount -t binfmt_misc none /proc/sys/fs/binfmt_misc If one of them is killed, the system works OK. But how can I get rid of the superfluous mount? The problem does not appear on all my computers. Perhaps it is caused by a leftover from a previous Linux installation?
Which desktop do you have (KDE3, KDE4, Gnome,...)?
The machine runs kde4init, but the window manager is /opt/kde3/bin/kdm. The problem (partially) disappeared when I disabled the starting of jexec in /etc/rc*.d . Now can mount everything, even cryptofiles via the /dev/loop* devices. But here I cannot unmount them again: ukd@iridium:~> mount $HOME/ext Passwort: ukd@iridium:~> umount $HOME/ext umount: /home/ukd/ext mount und fstab stimmen nicht überein ukd@iridium:~> I have to force an umount as a superuser: iridium:/home/ukd # umount /home/ukd/ext ioctl: LOOP_CLR_FD: Kein passendes Gerät bzw. keine passende Adresse gefunden In spite of the error message "no matching device or address found", the umount succeeds. Here is the appropriate line of my /etc/fstab: /media/usbdisk/.c /home/ukd/ext ext3 \ loop=/dev/loop0,encryption=twofish256,noatime,user,acl,user_xattr,noauto,rw 0 0 Of course, I am not sure that this problem is related to the former one.
Isn't it same as bug#463582?
it is *** This bug has been marked as a duplicate of bug 463582 ***