USB drive disappears after formatting; gives error; no longer mountable

Bug #1471266 reported by Christopher Barrington-Leigh
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
usb-creator (Ubuntu)
New
Undecided
Unassigned

Bug Description

When formatting a 4.1GB iriver USB key, usb-creator-gtk gave me the following error:

org.freedesktop.DBus.Python.GLib.Error: Traceback (most recent call last):
  File "/usr/lib/python3/dist-packages/dbus/service.py", line 707, in _message_cb
    retval = candidate_method(self, *args, **keywords)
  File "/usr/share/usb-creator/usb-creator-helper", line 287, in Format
    partition = table.call_create_partition_sync(0, size, '0x0c', '', no_options, None)
GLib.Error: udisks-error-quark: GDBus.Error:org.freedesktop.UDisks2.Error.Failed: Error wiping newly created partition /dev/sdc1: Command-line `wipefs -a "/dev/sdc1"' exited with non-zero exit status 1: wipefs: error: /dev/sdc1: probing initialization failed: No such file or directory
 (0)

Subsequently, I could not mount the drive. If I pulled it out and put it back in, it would show up in usb-creator-gtk, but it would not let me install anything on it. The disk didn't show up on the desktop and I could not mount or access it.

I solved this by reformatting the disk with the Disks utility instead. After that, it showed up fine in usb-creator-gtk and I could install an OS on it.

ProblemType: Bug
DistroRelease: Ubuntu 15.04
Package: usb-creator-gtk 0.2.67ubuntu0.1
ProcVersionSignature: Ubuntu 3.19.0-21.21-generic 3.19.8
Uname: Linux 3.19.0-21-generic x86_64
ApportVersion: 2.17.2-0ubuntu1.1
Architecture: amd64
CurrentDesktop: Unity
Date: Fri Jul 3 10:09:55 2015
EcryptfsInUse: Yes
InstallationDate: Installed on 2015-03-28 (96 days ago)
InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Beta amd64 (20150325)
SourcePackage: usb-creator
UDisksDump: Error: [Errno 2] No such file or directory: 'udisks'
UpgradeStatus: No upgrade log present (probably fresh install)

Revision history for this message
Christopher Barrington-Leigh (cpbl) wrote :
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.