keeps showing disks that aren 't connected any more

[teo1978]

I have a usb stick that got corrupted by usb-creator (which errored while erasing it). Obviously, no matter how corrupt the content of the usb stick, Disks must allow me to at least format it as long as the hardware is fine.

I first opened Disks, and it showed TWO items related to the usb stick:
- Toshiba TransMemory (without any /dev/something)
- Generic USB Mass Storage ( /dev/sdb).

The "Format" option was greyed out for both.

I unplugged the drive. Then I restarted Disks, and it still shows "Toshiba TransMemory", though the stick is not even plugged in.

ProblemType: Bug
DistroRelease: Ubuntu 15.04
Package: udisks2 2.1.5-1
ProcVersionSignature: Ubuntu 3.19.0-32.37-generic 3.19.8-ckt7
Uname: Linux 3.19.0-32-generic x86_64
ApportVersion: 2.17.2-0ubuntu1.7
Architecture: amd64
CurrentDesktop: Unity
CustomUdevRuleFiles: 60-vboxdrv.rules 40-brother-libsane-type1.rules 51-android.rules
Date: Sat Nov 14 19:21:12 2015
InstallationDate: Installed on 2013-10-11 (764 days ago)
InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
MachineType: Acer Aspire V3-571G
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-32-generic.efi.signed root=UUID=5830b30e-69e8-4bb4-8a2b-bc2b43c7414a ro quiet splash vt.handoff=7
SourcePackage: udisks2
UpgradeStatus: Upgraded to vivid on 2015-08-15 (90 days ago)
dmi.bios.date: 10/15/2012
dmi.bios.vendor: Acer
dmi.bios.version: V2.07
dmi.board.asset.tag: Type2 - Board Asset Tag
dmi.board.name: VA50_HC_CR
dmi.board.vendor: Acer
dmi.board.version: Type2 - Board Version
dmi.chassis.type: 10
dmi.chassis.vendor: Acer
dmi.chassis.version: V2.07
dmi.modalias: dmi:bvnAcer:bvrV2.07:bd10/15/2012:svnAcer:pnAspireV3-571G:pvrV2.07:rvnAcer:rnVA50_HC_CR:rvrType2-BoardVersion:cvnAcer:ct10:cvrV2.07:
dmi.product.name: Aspire V3-571G
dmi.product.version: V2.07
dmi.sys.vendor: Acer

[Phillip Susi (psusi)]

Please attach your /var/log/syslog after this happens.

[teo1978 (teo8976)]

Sorry but now I have fixed the USB stick and it would be too much work to reproduce the issue again.

Note: when you report a bug using ubuntu-bug, some files are attached automatically. I guess the package is who decides which files are to be attached, because the set of files differs depending on what package the bug is reported against.

So I suggest you to change whatever setting in the package so that /var/log/syslog is attached automatically the next time.

[Phillip Susi (psusi)]

Then the bug remains incomplete since we don't have enough information to go on.

You say you fixed it. How? That might help understand what was wrong in the first place.

[Juan Ignacio Saitua (jisaitua)]

There's an unresolved bug already reported in mainstream about this issue: https://bugs.freedesktop.org/show_bug.cgi?id=79184

I'm facing the same problem so I will gladly provide you with additional information if required.

[teo1978 (teo8976)]

> You say you fixed it. How? That might help understand what was wrong in the first place.

I just reformatted it from a Windows machine (so no, this won't help much)...