Fedora 17 warning: USB devices are not unmounted correctly

 There is currently a nasty bug in Fedora 17 related to USB devices. If you copy some data to your USB flash drive/harddisk and try to eject it (either in Nautilus or using Gnome Shell tray icon), there is no indicator of progress saying whether you need to wait until all the data are written or whether you can already remove the drive. Instead you’ll get the notion that you can remove the drive immediately. But if you do this, your data might be corrupted (in case some of them haven’t been transferred yet).

There are two possible workarounds for this:

1. (easier) After you eject the device using Nautilus or Gnome Shell dialog, run a terminal and write sync. Wait until that finishes and only after that unplug the device from the computer.

2. (harder) Don’t use Nautilus or Gnome Shell to eject the device, but use umount in terminal instead. You have to be root to do this. The mount point is in /run/media/.

As you can see, none of these approaches is suitable for inexperienced users. I’ll try to make sure we won’t release Fedora 17 Final with this bug included. Until that time, please be aware of this so that you don’t lose your data.

EDIT: Follow-up post: Fedora 17: Your data on USB devices are now safe(r)

Flattr this

6 thoughts on “Fedora 17 warning: USB devices are not unmounted correctly

  1. If this gets through anything can… a typical example of developer-centric approach as opposed to user-centric one. The current solution is a nasty hack? Let’s remove it. There is currently no replacement and it is going to effect a lot of users? Whatever. We might provide a clean solution one day. Until then you’re doomed.

    1. The result of living on the bleeding edge of Linux I suppose, but I agree that this isn’t an ideal solution. I think four of my six flash drives lack a LED, so this would affect me unless I go to the terminal to sync.

  2. A more preffered method of unmounting the disk would be udisks, since it’s the same system used to mount the disk.

    udisks –unmount /dev/sdb1

  3. Just read the original bug report – “wait for flashing led” was a suggested workaround \o/

    1. Even if you flash drive had a LED diod (all of mine don’t have any), I wouldn’t recommend it, unless you don’t care much about that particular data.

Leave a Reply (Markdown syntax supported)

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s