Floppy disk problem

[Keith]

Yes, yes; I know!  I ought to join the 20th Century.  But apart from the obvious advantage of floppy disks (impossible to lose, unlike USB sticks) they are rather mechanical and subject to all that entails.  Anyway; I have some files that I want to recover. 
I am confident that there is no mechanical problem because:

• I have checked it's physical installation (honestly!).
• All four desktops on which I have installed Ubuntu have non-working floppy drives that were functional in XP before the installation.

I attach the output from the sudo lshw -C disk command that lists the DVD and HDD but no floppy, so it is clearly not being recognised – unless there is another command for listing it. 
I am running Ubuntu V12.
Any ideas?  (Actually, I haven't yet checked that there is power on the power leads)

[SeZo]

The kernel drivers might not be running:

Code: [Select]

sudo modprobe floppy

Then try with disk inserted

[Keith]

Done that.  Then when I right-clicked on Floppy Drive in Nautilus, there was a 'click' from the drive, but no listing.
I have since discovered some udisks commands and I attach the outputs from those which might help.

[SeZo]

Try adding your username in the floppy group:

Code: [Select]

sudo adduser $USER floppy

[Mark Greaves (PCNetSpec)]

DON'T DO THAT

[Mark Greaves (PCNetSpec)]

My mistake .. it's "usermod" that needs the -aG (a for append) option 

It seems udisks 1.x is broken in Ubuntu, try:

Code: [Select]

udisks --mount /dev/fd0

after addding yourself to the floppy group and rebooting.

Quite why 12.04 is still using udisks 1.x is beyond me .. pretty much all other distros are now using udisks 2.x

--

[Keith]

The adduser command had no effect:
keith@desktop-1:~$ sudo adduser $USER floppy
[sudo] password for keith:
Adding user `keith' to group `floppy' ...
Adding user keith to group floppy
Done.

...but the udisks command:
keith@desktop-1:~$ udisks --mount /dev/fd0
Mounted /org/freedesktop/UDisks/devices/fd0 at /media/floppy0

produced the attached warning that I had once before.  But still no response in Nautilus.

[EDIT] Ah! didn't reboot.......

[Keith]

Sadly, still no response in Nautilus.
Can I upgrade to udisks 2.x?

[Mark Greaves (PCNetSpec)]

2 secs I think I've found a solution .. but first, what's the output from:

Code: [Select]

groups

[Keith]

keith@desktop-1:~$ groups
keith adm cdrom floppy sudo dip plugdev lpadmin sambashare

[Mark Greaves (PCNetSpec)]

Try this ..

Open /lib/udev/rules.d/80-udisks.rules for editing:

Code: [Select]

sudo gedit /lib/udev/rules.d/80-udisks.rules

Find the section that reads:-

Code: [Select]

# PC floppy drives
#
KERNEL=="fd*", ENV{ID_DRIVE_FLOPPY}="1"

# USB floppy drives
#
SUBSYSTEMS=="usb", ATTRS{bInterfaceClass}=="08", ATTRS{bInterfaceSubClass}=="04", ENV{ID_DRIVE_FLOPPY}="1"

And change the two 1's to 0's .. so it reads:-

Code: [Select]

# PC floppy drives
#
KERNEL=="fd*", ENV{ID_DRIVE_FLOPPY}="0"

# USB floppy drives
#
SUBSYSTEMS=="usb", ATTRS{bInterfaceClass}=="08", ATTRS{bInterfaceSubClass}=="04", ENV{ID_DRIVE_FLOPPY}="0"

SAVE the file

Now restart udev by running:

Code: [Select]

sudo invoke-rc.d udev restart

or

Code: [Select]

sudo service udev restart

(or reboot)

Does the floppy work now ?


Source:
http://www.securitybeacon.com/?p=1110

--

[Keith]

Ran the commands but nothing, then rebooted and Voila!  The floppy works!  (on read, anyway)
I shall try the same trick on my second desktop and let you know the result.

Thank you so much.

[Mark Greaves (PCNetSpec)]

Great

Does that mean you CAN'T write to the floppy .. or just that you haven't tried it yet ?

[EDIT]

I'm wondering if it would be best to create a custom udev rule with a higher number, such as 81-floppy.rules and make the changes in there .. so any updates that revert 80-udisks.rules to it original state won't stop the floppy drive from working.

Or you could just do the above again if the floppy ever stops working.

--

[Keith]

Well - almost great. 
I can't eject the disk safely, only "unmount", which crashes Nautilus.
If I try just inserting another disk, it doesn't recognise it.
I can copy a file to it, but there's no way of exiting without crashing Nautilus, and the file is not there when I restart.
I can at least recover my old files, which was the object of the exercise, but it would be nice to get it working properly - or am I being too demanding?

Sorry: I don't understand your final words - could you elaborate?

[Mark Greaves (PCNetSpec)]

OK .. another option seems to be to DOWNgrade udisks.

Can you post the output from:

Code: [Select]

uname -a