I run two Dell GX270 x86 systems. Both are running kernel 3.5.7. On the system running udev-171-r9, floppies work as expected. On the system running udev-197-r3, floppies won't mount. Mount reports no errors, but the directory in which the drive was mounted appears empty. Umount reports the drive as not mounted, according to mtab. It is not in /proc/ Reproducible: Always Actual Results: > mount -v /media/floppy mount: you didn't specify a filesystem type for /dev/fd0 I will try type vfat /dev/fd0 on /media/floppy type vfat (rw,noexec,nosuid,nodev,sync,user=rick) > mount rootfs on / type rootfs (rw) /dev/root on / type ext3 (rw,noatime,commit=0) proc on /proc type proc (rw,relatime) tmpfs on /run type tmpfs (rw,nosuid,nodev,relatime,mode=755) udev on /dev type devtmpfs (rw,nosuid,relatime,size=10240k,nr_inodes=112889,mode=755) devpts on /dev/pts type devpts (rw,relatime,mode=600) tmpfs on /dev/shm type tmpfs (rw,relatime) sysfs on /sys type sysfs (rw,nosuid,nodev,noexec,relatime) cgroup_root on /sys/fs/cgroup type tmpfs (rw,nosuid,nodev,noexec,relatime,size=10240k,mode=755) openrc on /sys/fs/cgroup/openrc type cgroup (rw,nosuid,nodev,noexec,relatime,release_agent=/lib/rc/sh/cgroup-release-agent.sh,name=openrc) cpu on /sys/fs/cgroup/cpu type cgroup (rw,nosuid,nodev,noexec,relatime,cpu) devices on /sys/fs/cgroup/devices type cgroup (rw,nosuid,nodev,noexec,relatime,devices) binfmt_misc on /proc/sys/fs/binfmt_misc type binfmt_misc (rw,noexec,nosuid,nodev) > cat /proc/mounts rootfs / rootfs rw 0 0 /dev/root / ext3 rw,noatime,errors=continue,commit=5,barrier=1,data=ordered 0 0 proc /proc proc rw,relatime 0 0 tmpfs /run tmpfs rw,nosuid,nodev,relatime,mode=755 0 0 udev /dev devtmpfs rw,nosuid,relatime,size=10240k,nr_inodes=112889,mode=755 0 0 devpts /dev/pts devpts rw,relatime,mode=600 0 0 tmpfs /dev/shm tmpfs rw,relatime 0 0 sysfs /sys sysfs rw,nosuid,nodev,noexec,relatime 0 0 cgroup_root /sys/fs/cgroup tmpfs rw,nosuid,nodev,noexec,relatime,size=10240k,mode=755 0 0 openrc /sys/fs/cgroup/openrc cgroup rw,nosuid,nodev,noexec,relatime,release_agent=/lib/rc/sh/cgroup-release-agent.sh,name=openrc 0 0 cpu /sys/fs/cgroup/cpu cgroup rw,nosuid,nodev,noexec,relatime,cpu 0 0 devices /sys/fs/cgroup/devices cgroup rw,nosuid,nodev,noexec,relatime,devices 0 0 binfmt_misc /proc/sys/fs/binfmt_misc binfmt_misc rw,nosuid,nodev,noexec,relatime 0 0 > umount /media/floppy umount: /media/floppy is not mounted (according to mtab) > there is a forum post thread on this at http://forums.gentoo.org/viewtopic-p-7229662.html#7229662
If it doesn't appear in /proc/mounts, I don't think it is a udev issue. Also, mounting floppies works fine for me in my qemu VM with udev-197-r4. What version of util-linux are you using?
In fact, so long as /dev/fd0 exists and has the correct type, udev has done its job.
Do you have sys-fs/udisks installed, is the daemon running by any chance? Or daemons, depending on if you have :0 or :2 SLOT installed or both? Are you trying this with a desktop running that would use udisks? Does dmesg print anything intresting while trying to mount it?
I'm running util-linux-2.21.2 and udisks-1.0.4-r2, latest stable for x86. The udisks daemon seems to be running: > ps aux | grep udisks root 3072 0.0 0.3 24216 3424 ? Sl 10:56 0:00 /usr/libexec/udisks-daemon root 3079 0.0 0.0 5520 784 ? S 10:56 0:00 udisks-daemon: not polling any devices rick 3430 0.0 0.0 4500 788 pts/0 S+ 11:09 0:00 grep --color=never udisks I'm trying to mount from an xfce desktop. Nothing appears in the dmesg after a mount attempt. fd0 seems to exist: > ls -l /dev/fd* lrwxrwxrwx 1 root root 13 Jan 24 10:55 /dev/fd -> /proc/self/fd/ brw-rw---- 1 root floppy 2, 0 Jan 24 10:55 /dev/fd0 what am I doing wrong here?
Apparently udisks is indeed the problem. After a fresh boot, without starting a desktop, the udisks daemon is not running, and floppies are fully functional. Starting XFCE starts the udisks daemon. If the floppy is mounted, it vanishes from mtab, and cannot be accessed. Stopping XFCE leaves the udisks daemon running, and floppies dysfunctional. Behaviour is identical on systems running udev-197-r3 and udev-171-r9. Both run udisks-1.0.4-r2 and linux-3.5.7. Any suggestions for a workaround?
Found an upstream udisks bug that seems relevant.
*** This bug has been marked as a duplicate of bug 338185 ***
