Mageia forum

I now have, what I presume to be, a "ghost" of a USB drive (may have been my phone) that I had plugged in since upgrade/install of Mageia #3 (see other post in the forum regarding problems).

In Dolphin it shows up in the Devices portion on the L-hand side as "0 B Removable Media", When I click on the entry I get the following error message:

An error occurred while accessing '0 B Removable Media', the system responded: The requested operation has failed: Error mounting /dev/fd0 at /run/media/myles/disk: Command-line `mount -t "auto" -o "uhelper=udisks2,nodev,nosuid" "/dev/fd0" "/run/media/myles/disk"' exited with non-zero exit status 32: mount: /dev/fd0 is not a valid block device

.

What does this mean, and how do I get rid of it?

This is a problem that I have seen as well. ANYTHING that you plug in these days might cause such a problem because a lot of devices are coming with USB storage capabilities. In my case I finally discovered it was an HP printer with empty sockets for various types of flash memory. Now I simply don't worry about it anymore when I see it because I know what it is and just ignore it. But it can change the order in which your hard drives get designated. That is why it is super important to make sure you identify hard drives only by UUID or, better yet, LABELS. Other than that it is just a matter of starting with a bare machine and plugging and unpluggin devices to see which one(s) are trying to add USB storage.

Does any of you two have a floppy drive or a card reader connected all the time?
Shouldn't be any ghost drive, dolphin just shows what is currently attached.

You may want to check viewtopic.php?f=8&t=4904

doktor5000, my bad once again,should have searched the forums and found that thread.
Yes I do have a physical floppy drive installed in my system. Is this something new in Mageia #3 that this has caused this to show up, didn't in Mageia #2?
Or do I just ignore it?

Yep, probably some change in the lower layers, seems udisk2: https://bugs.launchpad.net/ubuntu/+sour ... ug/1054414

Seems it should already be fixed for KDE 4.10.2: https://bbs.archlinux.org/viewtopic.php ... 0#p1230570