I can't mount my floppy drive anymore since one of the last online updates

[Werner Holtfreter]

Like bug 481184 I could never mount my floppy by the GUI, I could it mounting only by the terminal. Since one of the last online updates this did not work anymore:

werner@zuse:~$ sudo mount -v /dev/fd0 /mnt/
[sudo] password for werner:
mount: Es wurde kein Dateisystemtyp für /dev/fd0 angegeben
       Werde den Typ vfat versuchen #translation: Will try type vfat
/dev/fd0 on /mnt type vfat (rw)

It seems to be mounted, no message in the logs, but it is not mounted:

werner@zuse:~$ sudo umount /dev/fd0
umount: /dev/fd0 ist nicht eingehängt #translation: ...is not mounted

2010-04-02 I installed 3 online updates:

   devicekit-disks 007-2ubuntu5 -> 007-2ubuntu6
   tzdata 2010e-0ubuntu0.9.10 -> 2010g-0ubuntu0.9.10
   tzdata-java 2010e-0ubuntu0.9.10 -> 2010g-0ubuntu0.9.10

The first program seems to be relevant - and bingo, I can mount my floppy in a terminal.

But after the next reboot, mounting is impossible again.

Last but not least: It's not a hardware problem, I can mount after boot debian lenny.

ProblemType: Bug
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: werner 1867 F.... pulseaudio
                      werner 2206 F.... knotify4
CRDA: Error: [Errno 2] No such file or directory
Card0.Amixer.info:
 Card hw:0 'NVidia'/'HDA NVidia at 0xfe020000 irq 20'
   Mixer name : 'Realtek ALC662 rev1'
   Components : 'HDA:10ec0662,15650000,00100101'
   Controls : 33
   Simple ctrls : 17
Date: Sat Apr 3 18:15:54 2010
DistroRelease: Ubuntu 9.10
HibernationDevice: RESUME=UUID=90f31bbe-3110-43e5-8130-e81616136092
IwConfig:
 lo no wireless extensions.

 eth0 no wireless extensions.
Lsusb:
 Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
 Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
 Bus 003 Device 002: ID 05fe:0011 Chic Technology Corp. Browser Mouse
 Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: BIOSTAR Group GF7025-M2 TE
NonfreeKernelModules: nvidia
Package: linux-image-2.6.31-20-generic 2.6.31-20.58
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.31-20-generic root=UUID=f2fb4ee7-1c31-4840-9504-c7d1d765071a ro
ProcEnviron:
 LANG=de_DE.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-20.58-generic
RelatedPackageVersions:
 linux-backports-modules-2.6.31-20-generic N/A
 linux-firmware 1.26
RfKill:

SourcePackage: linux
Uname: Linux 2.6.31-20-generic x86_64
XsessionErrors:
 (gnome-settings-daemon:1881): GLib-CRITICAL **: g_propagate_error: assertion `src != NULL' failed
 (gnome-settings-daemon:1881): GLib-CRITICAL **: g_propagate_error: assertion `src != NULL' failed
 (nautilus:1916): Eel-CRITICAL **: eel_preferences_get_boolean: assertion `preferences_is_initialized ()' failed
 (polkit-gnome-authentication-agent-1:1954): GLib-CRITICAL **: g_once_init_leave: assertion `initialization_value != 0' failed
 (firefox:2115): GLib-WARNING **: g_set_prgname() called multiple times
dmi.bios.date: 07/18/2008
dmi.bios.vendor: Phoenix Technologies, LTD
dmi.bios.version: 6.00 PG
dmi.board.name: GF7025-M2 TE
dmi.board.vendor: BIOSTAR Group
dmi.board.version: Unknow
dmi.chassis.asset.tag: Unknow
dmi.chassis.type: 3
dmi.chassis.vendor: Unknow
dmi.chassis.version: Unknow
dmi.modalias: dmi:bvnPhoenixTechnologies,LTD:bvr6.00PG:bd07/18/2008:svnBIOSTARGroup:pnGF7025-M2TE:pvrUnknow:rvnBIOSTARGroup:rnGF7025-M2TE:rvrUnknow:cvnUnknow:ct3:cvrUnknow:
dmi.product.name: GF7025-M2 TE
dmi.product.version: Unknow
dmi.sys.vendor: BIOSTAR Group

[dino99 (9d9)]

i've got the same problem today but i cant say that problem is new as i rarely need to use floppy.

 First i've put a floppy disk inside the reader and Lucid does not detect that new situation.
So i've ran MountManager and change setting to allow user to mount/unmount /dev/fd0 ( admin by default, so that seem a feature not a bug)

After giving user the right of mount/unmount, everything goes well. So that's seem normal.

[Werner Holtfreter (holtfreter)]

Thanks, dino99,

   devkit-disks --mount /dev/fd0

is a good work around.

Strange, a simple "mount" don't work but a more complex program works.

[Jeremy Foshee (jeremyfoshee)]

Hi Werner,

If you could also please test the latest upstream kernel available that would be great. It will allow additional upstream developers to examine the issue. Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Once you've tested the upstream kernel, please remove the 'needs-upstream-testing' tag. This can be done by clicking on the yellow pencil icon next to the tag located at the bottom of the bug description and deleting the 'needs-upstream-testing' text. Please let us know your results.

Thanks in advance.

    [This is an automated message. Apologies if it has reached you inappropriately; please just reply to this message indicating so.]

[Werner Holtfreter (holtfreter)]

Hallo Jeremy,

OK, I will try to do that. A question before:

Should I collect and post the system information with
  "ubuntu-bug -p linux"
again?
--
Werner

[Jeremy Foshee (jeremyfoshee)]

Hi Werner,
    If you are able, that would be helpful. At the very least I need to see if there is different behavior.

Thanks!

~JFo

[Werner Holtfreter (holtfreter)]

Hello Jeremy,

today I tested with the current upstream kernel 2.6.34-999-generic. The result is exact the same like 2.6.31-20-generic:

mount with nautilus did not work and
mount in a terminal did not work, only
devkit-disks --mount /dev/fd0 works.

Unfortunately I could not collect system information with "ubuntu-bug -p linux". See the error message:

hook /usr/share/apport/package-hooks//source_linux.py crashed:
Traceback (most recent call last):
  File "/usr/lib/python2.6/dist-packages/apport/report.py", line 637, in add_hooks_info
    symb['add_info'](self, ui)
  File "/usr/share/apport/package-hooks//source_linux.py", line 31, in add_info
    report['UnreportableReason'] = _('The running kernel is not an Ubuntu kernel')
NameError: global name '_' is not defined

Let me know if I can do more for you.

Werner

[Werner Holtfreter (holtfreter)]

I upgraded from Ubuntu 9.10 to 10.4: The bug exist not anymore.

Greetings, Werner

[Werner Holtfreter (holtfreter)]

The bug is back!

Today I'm needed the floppy after some weeks, but one of the online updates for Ubuntu 10.4 between 2010-06-20 to 2010-07-06 destroyed the floppy functionality again.

My Ubuntu 10.4 full backup from 2010-06-20 works fine. I made a list with all updates in the meantime with the command "apt-get -s upgrade". See attachment "updates.txt"

[Werner Holtfreter (holtfreter)]

In the meantime I work with Ubuntu 10.4. Today I could see and reproduce this steps:

1. Boot the system.

2. I don't make a graphical login, only a console login.

3. sudo mount /dev/fd0 /mnt # I can work on disk

4. Graphical login (gnome)

5. After step 4, the fd0 is not mounted any more! Remount is impossible.

[beroal (beroal)]

This bug also exists in Arch Linux. Try to load "Xorg" server with "xterm" only, then mount a floppy disk.

[beroal (beroal)]

Mounting "/dev/fd0u1440" instead of "/dev/fd0" seems working. (I assume you have a 1.44 MB diskette.) Maybe this is a bug of the kernel module "floppy". Also try KDE or Awesome instead of Gnome.

[Sergey Svishchev (svs)]

Bug 618953 suggests that udisks 1.0.1-1ubuntu1 is the problem, and your list of updates has

"Inst udisks [1.0.1-1build1] (1.0.1-1ubuntu1 Ubuntu:10.04/lucid-updates)"

[Werner Holtfreter (holtfreter)]

The bug is still alive in Ubuntu10.10! Thanks to Roman Beslik, his work around
| Mounting "/dev/fd0u1440" instead of "/dev/fd0"
is working fine.

[Werner Holtfreter (holtfreter)]

The best way to work around this bug I found in a forum:

Modify in /lib/udev/rules.d/80-udisks.rules the line 175
from
KERNEL=="fd*", ENV{ID_DRIVE_FLOPPY}="1"
to
KERNEL=="fd*", ENV{ID_DRIVE_FLOPPY}="0"

After this, all mount methods are working. I don't understand the background, but I hope it is helpfully, for users and for debuggers.

[beroal (beroal)]

There is no file "/dev/fd0u1440" in the Linux kernel version 2.6.39 . Changing "/lib/udev/rules.d/80-udisks.rules" does not work for me.

[Brad Figg (brad-figg)]

This bug was filed against a series that is no longer supported and so is being marked as Won't Fix. If this issue still exists in a supported series, please file a new bug.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.

[Werner Holtfreter (holtfreter)]

I have re-reported the bug.

https://bugs.launchpad.net/bugs/811108

Subscriber are welcome.