Automatic remount of safely removed USB 3.0 drive

Bug #792085 reported by Martin Wildam
566
This bug affects 153 people
Affects Status Importance Assigned to Milestone
linux (Fedora)
Fix Released
Undecided
linux (Ubuntu)
Fix Released
Medium
Joseph Salisbury
Trusty
Triaged
Medium
Joseph Salisbury
Xenial
Fix Released
Medium
Joseph Salisbury
Yakkety
Fix Released
Medium
Joseph Salisbury
linux (openSUSE)
Fix Released
Medium

Bug Description

Binary package hint: nautilus

When I choose "Safely remove drive" context menu entry for an external USB drive within a nautilus window or directly clicking on the desktop icon, after about 10 seconds the drive is automatically remounted and a Nautilus window showing the root folder opens.

I have noticed that similar already happened with a very old Ubuntu version - Bug #110589 and as that is so long time ago I thought it is better to open a new bug. Reason of the problem might even be completely different.

ProblemType: Bug
DistroRelease: Ubuntu 11.04
Package: nautilus 1:2.32.2.1-0ubuntu13
ProcVersionSignature: Ubuntu 2.6.38-8.42-generic-pae 2.6.38.2
Uname: Linux 2.6.38-8-generic-pae i686
Architecture: i386
Date: Thu Jun 2 23:40:08 2011
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release i386 (20110427.1)
ProcEnviron:
 LANGUAGE=en_US:en
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: nautilus
UpgradeStatus: No upgrade log present (probably fresh install)

break-fix: - 37be66767e3cae4fd16e064d8bb7f9f72bf5c045

Revision history for this message
Martin Wildam (mwildam) wrote :
Revision history for this message
Alex Colorado (alex-kiwikiwi) wrote :

Same behaviour for me. Although it only happens after the first time I select "Safely remove drive".
After the first automatic remount, the second time I choose "Safely remove drive" the usb external drive does not remount.

It happens for different types of USB drives and USB keys, so it's not related to a specific external drive.

Marco Sulla (xdq4gh24rq)
Changed in nautilus (Ubuntu):
status: New → Confirmed
Changed in usb-creator (Ubuntu):
status: New → Confirmed
Marco Sulla (xdq4gh24rq)
Changed in udev (Ubuntu):
status: New → Confirmed
Revision history for this message
Marco Sulla (xdq4gh24rq) wrote :

Daniel Richard G. from Bug #507309 : usb-creator has a strange quirk in that when it starts up, it (re)mounts all unmounted partitions on all connected USB drives---even those drives on which the "Safely remove drive" operation has been performed, but are still plugged into the USB bus. This is with icons and everything on the desktop; this is clearly some sort of interaction with udev, similar to what occurs when a USB drive is plugged in.

I am filing this report to request that this "mount everything" behavior be removed. It is inappropriate for usb-creator to do this, not least because it may then go on to perform destructive operations on some of these newly-mounted filesystems!

Revision history for this message
Mihai Capotă (mihaic) wrote :

I have the same problem, but only with two Western Digital USB 3 drives. The drives are My Book Essential 3 TB (WDBACW0030HBK) and My Passport Essential 500 GB (WDBACY5000ABK). I can reproduce the behavior on a laptop and a desktop, both running Ubuntu 10.10. All other drives remain unmounted.

Changed in nautilus (Ubuntu):
importance: Undecided → Low
Revision history for this message
Nikhil P Joseph (madfly8082-deactivatedaccount-deactivatedaccount) wrote :

does this happen in 11.10 also?

Revision history for this message
Daniel Richard G. (skunk) wrote :

In 11.10, I'm no longer seeing usb-creator remount previously-removed disks on startup.

I can't speak to the Nautilus behavior described in this bug, however, as I've never observed it myself.

Revision history for this message
Jan Sonntag (finaljason) wrote :

As you can read on https://bugzilla.gnome.org/show_bug.cgi?id=641873 the specified behaviour seems to appear only with some nvidea chipsets.
Could the bug be a driver issue?

Revision history for this message
Nikhil P Joseph (madfly8082-deactivatedaccount-deactivatedaccount) wrote :

if it is a driver issue, is there anyway we can roll back to the driver version in lucid?

Revision history for this message
torstenaf (afguy) wrote : Re: [Bug 792085] Re: Automatic remount of safely removed drive

The behavior has changed, but still exists.

After "ejecting" the device, it now disappears and does not
automatically re-appear as a device; however, in "My Computer"
location when I select "Safely remove device" it disappears and
automatically re-appears. Interesting, after re-appearing I cannot
click on and open the disk drive.

At the OS-level the USB devices automatically remount, but at the
interface level it partially disappears, re-appears in my computer
inaccessible.

TH

On Fri, Oct 14, 2011 at 8:33 PM, Nikhil P Joseph
<email address hidden> wrote:
> does this happen in 11.10 also?
>
> --
> You received this bug notification because you are subscribed to a
> duplicate bug report (608508).
> https://bugs.launchpad.net/bugs/792085
>
> Title:
>  Automatic remount of safely removed drive
>
> Status in “nautilus” package in Ubuntu:
>  Confirmed
> Status in “udev” package in Ubuntu:
>  Confirmed
> Status in “usb-creator” package in Ubuntu:
>  Confirmed
>
> Bug description:
>  Binary package hint: nautilus
>
>  When I choose "Safely remove drive" context menu entry for an external
>  USB drive within a nautilus window or directly clicking on the desktop
>  icon, after about 10 seconds the drive is automatically remounted and
>  a Nautilus window showing the root folder opens.
>
>  I have noticed that similar already happened with a very old Ubuntu
>  version - Bug #110589 and as that is so long time ago I thought it is
>  better to open a new bug. Reason of the problem might even be
>  completely different.
>
>  ProblemType: Bug
>  DistroRelease: Ubuntu 11.04
>  Package: nautilus 1:2.32.2.1-0ubuntu13
>  ProcVersionSignature: Ubuntu 2.6.38-8.42-generic-pae 2.6.38.2
>  Uname: Linux 2.6.38-8-generic-pae i686
>  Architecture: i386
>  Date: Thu Jun  2 23:40:08 2011
>  InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release i386 (20110427.1)
>  ProcEnviron:
>   LANGUAGE=en_US:en
>   LANG=en_US.UTF-8
>   SHELL=/bin/bash
>  SourcePackage: nautilus
>  UpgradeStatus: No upgrade log present (probably fresh install)
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/792085/+subscriptions
>

Revision history for this message
Jan Sonntag (finaljason) wrote : Re: Automatic remount of safely removed drive

@Nikhil:

the bug didn't appear in lucid (for me) and i recognized it for the first time in natty (but i don't know whether the bug appears in maverick too)

@torstenaf:

sounds interesting. Can you check your dmesg-log for entries like:

[ 968.188033] usb 1-8: new high speed USB device using ehci_hcd and address 6

and after reappearing (same bus):

[ 1005.992037] usb 2-8: new full speed USB device using ohci_hcd and address 4

If it's a driver issue there is definitively something wrong with the communication between ohci_hcd and ehci_hcd.

Revision history for this message
Nikhil P Joseph (madfly8082-deactivatedaccount-deactivatedaccount) wrote :

@Jan: I can confirm that. My laptop's still running lucid and i noticed it first in maverick when i tried it for a short time. my machine has the nvidia mcp51 chipset. however i am not sure if the problem affects nvidia chipsets alone, ive seen some people with intel machines also encountering this problem.

Revision history for this message
torstenaf (afguy) wrote : Re: [Bug 792085] Re: Automatic remount of safely removed drive

Here are the dmesg messages.

After plugging in USB device:
[29103.712213] usb 1-1: new high speed USB device number 3 using ehci_hcd
[29103.852384] scsi8 : usb-storage 1-1:1.0

After clicking the "Eject" icon on the file manager (no change from before):
[29103.712213] usb 1-1: new high speed USB device number 3 using ehci_hcd
[29103.852384] scsi8 : usb-storage 1-1:1.0

After opening "Computer", right clicking on the USB drive, and
clicking "Safely Remove Drive" (the icon disappears, then re-appears):
[29103.712213] usb 1-1: new high speed USB device number 3 using ehci_hcd
[29103.852384] scsi8 : usb-storage 1-1:1.0
[29167.356346] usb 1-1: USB disconnect, device number 3
[29167.728213] usb 3-1: new full speed USB device number 2 using ohci_hcd
[29167.929262] usb 3-1: not running at top speed; connect to a high speed hub
[29167.953587] scsi9 : usb-storage 3-1:1.0

TH

On Mon, Oct 17, 2011 at 5:22 PM, Jan Sonntag <email address hidden> wrote:
> @Nikhil:
>
> the bug didn't appear in lucid (for me) and i recognized it for the
> first time in natty (but i don't know whether the bug appears in
> maverick too)
>
> @torstenaf:
>
> sounds interesting. Can you check your dmesg-log for entries like:
>
> [  968.188033] usb 1-8: new high speed USB device using ehci_hcd and
> address 6
>
> and after reappearing (same bus):
>
> [ 1005.992037] usb 2-8: new full speed USB device using ohci_hcd and
> address 4
>
> If it's a driver issue there is definitively something wrong with the
> communication between ohci_hcd and ehci_hcd.
>
> --
> You received this bug notification because you are subscribed to a
> duplicate bug report (608508).
> https://bugs.launchpad.net/bugs/792085
>
> Title:
>  Automatic remount of safely removed drive
>
> Status in “nautilus” package in Ubuntu:
>  Confirmed
> Status in “udev” package in Ubuntu:
>  Confirmed
> Status in “usb-creator” package in Ubuntu:
>  Confirmed
>
> Bug description:
>  Binary package hint: nautilus
>
>  When I choose "Safely remove drive" context menu entry for an external
>  USB drive within a nautilus window or directly clicking on the desktop
>  icon, after about 10 seconds the drive is automatically remounted and
>  a Nautilus window showing the root folder opens.
>
>  I have noticed that similar already happened with a very old Ubuntu
>  version - Bug #110589 and as that is so long time ago I thought it is
>  better to open a new bug. Reason of the problem might even be
>  completely different.
>
>  ProblemType: Bug
>  DistroRelease: Ubuntu 11.04
>  Package: nautilus 1:2.32.2.1-0ubuntu13
>  ProcVersionSignature: Ubuntu 2.6.38-8.42-generic-pae 2.6.38.2
>  Uname: Linux 2.6.38-8-generic-pae i686
>  Architecture: i386
>  Date: Thu Jun  2 23:40:08 2011
>  InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release i386 (20110427.1)
>  ProcEnviron:
>   LANGUAGE=en_US:en
>   LANG=en_US.UTF-8
>   SHELL=/bin/bash
>  SourcePackage: nautilus
>  UpgradeStatus: No upgrade log present (probably fresh install)
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/792085/+subscriptions
>

Revision history for this message
Martin Wildam (mwildam) wrote : Re: Automatic remount of safely removed drive

Don't experience this any more on Oneiric with Intel graphic card and 11.10 (release) under unity (other desktops not yet tested).

Revision history for this message
Jan Sonntag (finaljason) wrote :

@Martin Wildam:

which chipset you are using?

I'm actually downloading Puppy Linux and test if the bug also appears there...

Revision history for this message
Martin Wildam (mwildam) wrote :

product: Mobile 4 Series Chipset Integrated Graphics Controller
vendor: Intel Corporation

Revision history for this message
Jan Sonntag (finaljason) wrote :

Hmpf!

Puppy's kernel is too old...

Has someone a newer (Gentoo, Open Suse or whatever) live cd to test if the bug only appears in Ubuntu?

Revision history for this message
Nikhil P Joseph (madfly8082-deactivatedaccount-deactivatedaccount) wrote :

Im assuming we need a distribution with kernel version>=2.6.35. that's the one which shipped with maverick.

Revision history for this message
Martin Wildam (mwildam) wrote : Re: [Bug 792085] Re: Automatic remount of safely removed drive

Hello,

tried with Fedora 15 Live CD on kernel 2.6.38.6-26 and did not
experience the problem there.
Ubuntu 11.10 with current kernel 3.0.0-12 also does not show the issue.

On Tue, Oct 18, 2011 at 17:33, Nikhil P Joseph
<email address hidden> wrote:
> Im assuming we need a distribution with kernel version>=2.6.35. that's
> the one which shipped with maverick.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/792085
>
> Title:
>  Automatic remount of safely removed drive
>
> Status in “nautilus” package in Ubuntu:
>  Confirmed
> Status in “udev” package in Ubuntu:
>  Confirmed
> Status in “usb-creator” package in Ubuntu:
>  Confirmed
>
> Bug description:
>  Binary package hint: nautilus
>
>  When I choose "Safely remove drive" context menu entry for an external
>  USB drive within a nautilus window or directly clicking on the desktop
>  icon, after about 10 seconds the drive is automatically remounted and
>  a Nautilus window showing the root folder opens.
>
>  I have noticed that similar already happened with a very old Ubuntu
>  version - Bug #110589 and as that is so long time ago I thought it is
>  better to open a new bug. Reason of the problem might even be
>  completely different.
>
>  ProblemType: Bug
>  DistroRelease: Ubuntu 11.04
>  Package: nautilus 1:2.32.2.1-0ubuntu13
>  ProcVersionSignature: Ubuntu 2.6.38-8.42-generic-pae 2.6.38.2
>  Uname: Linux 2.6.38-8-generic-pae i686
>  Architecture: i386
>  Date: Thu Jun  2 23:40:08 2011
>  InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release i386 (20110427.1)
>  ProcEnviron:
>   LANGUAGE=en_US:en
>   LANG=en_US.UTF-8
>   SHELL=/bin/bash
>  SourcePackage: nautilus
>  UpgradeStatus: No upgrade log present (probably fresh install)
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/792085/+subscriptions
>

--
Martin Wildam

http://www.google.com/profiles/mwildam

Revision history for this message
Matthias Niess (mniess) wrote : Re: Automatic remount of safely removed drive

The issue is still present for me with 3.0.0-12-generic and the nvidia chipset discussed above.

Peter Kennes (mgt2000)
Changed in nautilus (Ubuntu):
assignee: nobody → Peter Kennes (mgt2000)
Revision history for this message
Matt 6:27 (goffice) wrote :

I'm having the same issue in the Unity launcher. External hard drive connected via USB. When I right-click the drive in the launcher and then select 'safely remove', it spins down the drive for about 5 seconds, then remounts. Did not experience this in Lucid. Currently using 11.10 and kernel 3.0.0-14-generic.

Peter Kennes (mgt2000)
Changed in nautilus (Ubuntu):
assignee: Peter Kennes (mgt2000) → nobody
Revision history for this message
vasja pupkin (klient1982) wrote :

same problem Ubuntu 10.10

Revision history for this message
Matt 6:27 (goffice) wrote :

I just discovered that when I first 'safely remove' it remounts as noted in post #20 above, but once external HD activity ceases (after the remount), I can use "safely remove" a second time and it spins down and stays off.

Revision history for this message
Dennis Fehr (cy-raid) wrote :

This also affects me.. I really wish this would get fixed, it's been around for quite some time and it's so annoying. I wonder how many other people it affects, and they just don't voice their opinion..

Revision history for this message
pelm (pelle-ekh) wrote :

For me too on Ubuntu 12.04, fresh install (yesterday daily ISO). As described, first time when i securely removes a USB drive with the rightclick option in Unity launcher it automatically remount in a few seconds. The second time i try to securely remove the drive it works. In Lucid it was no problem.

Revision history for this message
Matthias Niess (mniess) wrote :

This only happens on certain nvidia chipsets and only with newer kernels (the nautilus-version doesn't really matter).

Changed in nautilus (Ubuntu):
status: Confirmed → Invalid
Changed in usb-creator (Ubuntu):
status: Confirmed → Invalid
Revision history for this message
pelm (pelle-ekh) wrote :

Is there some workaround for this issue? It's a really big issue which users not knowing it can lose data when unplug the device too soon.

Revision history for this message
Martin Wildam (mwildam) wrote :

I don't have an nvidia chipset and it happened to me also - however does not occur any more on Precise released version with latest updates.

Revision history for this message
sojourner (itsmealso2) wrote :

hitting eject instead of safely remove works for me

Revision history for this message
Martin Wildam (mwildam) wrote :

Tried again (as a while passed by and I am currently on 12.04): Still same issue.

Clicking eject in Nautilus seems to remove the device correctly, but disk usage analyzer for example still sees it - so that does not completely unmount the drive/device!

I consider this a critical issue as I am not always able to eject and in the next seconds find the correct plug - otherwise it is already remounted when I unplug it.

Revision history for this message
Marius B. Kotsbak (mariusko) wrote :

Are any of you able to test a 12.10 live CD of the latest beta or daily image?

Revision history for this message
Rod Zazubek (zazubek) wrote :

This problem has not gone away with
Linux Mint 14 (Ubuntu 12.10) on my
pc with the nvidia chipset.
In fact, it is now worse because
Safely Remove Drive has been removed.
See launchpad #1067876.
So to safely remove my portable hard drive
I now need the following 4 commands:
> udisks --unmount /dev/sdb1
> udisks --detach /dev/sdb
wait for remount
> udisks --unmount /dev/sdb1
> udisks --detach /dev/sdb
Replace sdb with whatever your drive is using.
Add more udisks --unmount commands if you have
multiple partitions mounted.

Revision history for this message
Chris (fabricator4) wrote :

Confirmed for both 12.04 and 12.10, ASRock N68-VS3 FX motherboard, NVidia chipset.

When you click "Safely remove" on the launcher icon and then wait for buffers to be flushed, device remounts. The remount is done as a USB 1.x device as the speed is very slow on transfer (about 1MiB / minute). In the log (attached) it appears to think that the device is plugged into a slow speed hub.

     *-usb:0
          description: USB controller
          product: MCP61 USB 1.1 Controller
          vendor: NVIDIA Corporation
          physical id: 2
          bus info: pci@0000:00:02.0
          version: a3
          width: 32 bits
          clock: 66MHz
          capabilities: pm ohci bus_master cap_list
          configuration: driver=ohci_hcd latency=0 maxlatency=1 mingnt=3
          resources: irq:23 memory:effff000-efffffff

Revision history for this message
Walter Ribeiro (wribeirojr) wrote :

At the first time pen drive is "safely removed", it is automatically remounted immediately.
If I repeat the operation, automatic remount don't occur.

Ubuntu 13.04 - HP Pavilion dv6000

Revision history for this message
Nithin C (nithin-aneesh) wrote :

The automatic remount occurs in Ubuntu 13.04 beta 1

no longer affects: nautilus
Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in ubuntu:
status: New → Confirmed
Nithin C (nithin-aneesh)
affects: nautilus → ubuntu
Changed in nautilus (Ubuntu):
status: Invalid → Confirmed
Revision history for this message
Peter Eijlander (peter-eijlander) wrote :

After seeing this in some older version of Ubuntu this issue never reoccurred with whatever USB stick or -drive I have. I currently use Ubuntu 12.04LTS_64bit. I have no USB3 hardware.

Revision history for this message
chris blake (cblake-r) wrote :

12.04 ASUS 64 bit.
This only happens on usb 3.0 port, the 2.0 ports work as expected

Revision history for this message
soroosh sardari (soroosh-sardari) wrote :

I'm using 12.04 on Asus u41.
This damn problem exists for safely remove of USB hard disks but USB falsh has no probelm.

Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in ubuntu:
status: New → Confirmed
Revision history for this message
beni (benicchio) wrote :

I can confirm the bug. And it started after the upgrade to 13.04 - 64bit on a Dell XPS-8500. It was not happening on 12.10.
Only affects USB 3.0 ports (2.0 safely removes ok).
The only way to unmount a USB hard drive in my case is clicking on the arrow icon on Nautilus window. If I click on Safely Remove, both on Nautilus or on launcher icon, the drive is re-mounted.

Revision history for this message
jcsjcs (jcsjcs) wrote :

I would like to confirm what beni wrote on 2013-05-04.

I've just installed 13.04 on a zenbook with only USB 3.0 ports. "Safely Removing" USB harddisks or memory results in immediate re-mounting. Only clicking on the arrow in a Nautilus (or unmounting in a terminal "umount /media/...") will allow me to safely remove my disk.

My previous computer with 12.04 did not have USB 3.0 ports and I didn't experience this problem.

Revision history for this message
Martin Wildam (mwildam) wrote : Re: [Bug 792085] Re: Automatic remount of safely removed drive

On Sun, May 26, 2013 at 4:16 PM, jcsjcs <email address hidden> wrote:
> My previous computer with 12.04 did not have USB 3.0 ports and I didn't
> experience this problem.

I have experienced the problem on 12.04 in the beginning, but went
away with some kernel update (currently running 3.5.0-30-generic which
works fine), so this might be the reason why you didn't experience it
on 12.04.

Best regards, Martin.

Revision history for this message
Norbert (nrbrtx) wrote : Re: Automatic remount of safely removed drive

I got this behaviour with one of my flashed under Ubuntu 12.04.

Revision history for this message
HousieMousie2 (housiemousie2) wrote :

My laptop is an older machine:
00:04.0 USB controller: NVIDIA Corporation MCP79 OHCI USB 1.1 Controller (rev b1)
00:04.1 USB controller: NVIDIA Corporation MCP79 EHCI USB 2.0 Controller (rev b1)
00:06.0 USB controller: NVIDIA Corporation MCP79 OHCI USB 1.1 Controller (rev b1)
00:06.1 USB controller: NVIDIA Corporation MCP79 EHCI USB 2.0 Controller (rev b1)

This bug affects me.

The USB/External drive remounts almost immediately after Safely Remove, but will properly unmount and stay unmounted after the second Safely Remove.

Revision history for this message
miusang (858690042-5) wrote :

The same bug for me in Ubuntu 12.04.

Only eSATA port works. The other USB ports don't work at all.

The laptop I just bought last year meet the bug but the old PC in my home doesn't come across the bug.
After my time-consuming reflection, I suspect that the reason may be due to the problem in nautilus dealing with USB 2.0 and USB 3.0 port.

The nautilus doesn't deal well with USB 3.0 but deal well with USB 2.0.

Revision history for this message
Sabine (sabse) wrote :

Same bug with Ubuntu 13.04

Yesterday I updated from ubuntu 12.10 to 13.04 using the software updater.
Now when I plug-in my external hdd it automounts again in seconds after I hit 'safely remove'. It does not stay unmounted even after multiple times hitting 'safely remove' I can only remove it when I either do ' sudo eject /media/...' or 'sudo umount /media/....'

I hadn't had this problem with 12.10. It doesn't make a difference if I use the Usb 2.0 or 3.0 port on my computer.

In addition a Usb pen drive that was working perfectly before is not working at all anymore and not even listed
when I do 'sudo fdisk -l'

My computer does have a Nvidia Graphics card and I use gnome not unity

no longer affects: ubuntu
no longer affects: usb-creator (Ubuntu)
Changed in udev (Ubuntu):
importance: Undecided → Medium
Revision history for this message
Matthias Niess (mniess) wrote :

This problem is still present in 13.10 and trusty. As long as you use the affected nvidia chipset on the motherboard. I upgraded the computer I have with this motherboard just to see if the bug is still there. I won't be upgrading it anymore. So I can't give any more feedback and hereby unsubscribe from this bug.

Revision history for this message
Eero (eero+launchpad) wrote :

It's not just Nvidia chipsets. I'm having this issue with Intel chipset in 12.04.

$ lspci
00:00.0 Host bridge: Intel Corporation 2nd Generation Core Processor Family DRAM Controller (rev 09)
00:02.0 VGA compatible controller: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller (rev 09)
00:16.0 Communication controller: Intel Corporation 6 Series/C200 Series Chipset Family MEI Controller #1 (rev 04)
00:16.3 Serial controller: Intel Corporation 6 Series/C200 Series Chipset Family KT Controller (rev 04)
00:19.0 Ethernet controller: Intel Corporation 82579LM Gigabit Network Connection (rev 04)
00:1a.0 USB controller: Intel Corporation 6 Series/C200 Series Chipset Family USB Enhanced Host Controller #2 (rev 04)
00:1b.0 Audio device: Intel Corporation 6 Series/C200 Series Chipset Family High Definition Audio Controller (rev 04)
00:1c.0 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 1 (rev b4)
00:1c.1 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 2 (rev b4)
00:1c.3 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 4 (rev b4)
00:1c.4 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 5 (rev b4)
00:1c.6 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 7 (rev b4)
00:1d.0 USB controller: Intel Corporation 6 Series/C200 Series Chipset Family USB Enhanced Host Controller #1 (rev 04)
00:1f.0 ISA bridge: Intel Corporation QM67 Express Chipset Family LPC Controller (rev 04)
00:1f.2 SATA controller: Intel Corporation 6 Series/C200 Series Chipset Family 6 port SATA AHCI Controller (rev 04)
00:1f.3 SMBus: Intel Corporation 6 Series/C200 Series Chipset Family SMBus Controller (rev 04)
03:00.0 Network controller: Intel Corporation Centrino Advanced-N 6205 [Taylor Peak] (rev 34)
0d:00.0 System peripheral: Ricoh Co Ltd MMC/SD Host Controller (rev 07)
0e:00.0 USB controller: NEC Corporation uPD720200 USB 3.0 Host Controller (rev 04)

$ lsusb
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 002 Device 009: ID 0bdb:1911 Ericsson Business Mobile Networks BV
Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 001 Device 003: ID 147e:2016 Upek Biometric Touchchip/Touchstrip Fingerprint Sensor
Bus 001 Device 004: ID 04f2:b217 Chicony Electronics Co., Ltd

Revision history for this message
Raj Rao (coytar) wrote :

This is quite annoying! I'm using 13.10 and I just tried to safely remove a Samsung 1TB external drive (USB3.0 device plugged into USB3.0 port) but it kept remounting. I tried it this way as well:

sudo udisks --unmount /dev/sde1
sudo udisks --detach /dev/sde1

and that also remounted except it took a few seconds longer.

Here is my USB hardware info:
$ lspci | grep USB
00:1a.0 USB controller: Intel Corporation C600/X79 series chipset USB2 Enhanced Host Controller #2 (rev 05)
00:1d.0 USB controller: Intel Corporation C600/X79 series chipset USB2 Enhanced Host Controller #1 (rev 05)
06:00.0 USB controller: ASMedia Technology Inc. ASM1042 SuperSpeed USB Host Controller
07:00.0 USB controller: ASMedia Technology Inc. ASM1042 SuperSpeed USB Host Controller
08:00.0 USB controller: ASMedia Technology Inc. ASM1042 SuperSpeed USB Host Controller

Revision history for this message
Abhirav Kumar (akabhirav) wrote :

This bug affects all the Ubuntu versions from 10.10 to 13.10 and also maybe 14.04 till now.
How ever I had the problem in 13.04 and 13.10 only on usb 3.0 and not 2.0.
Please solve the problem soon
This bug should atleast be of medium importance and please assign someone to it soon

Ubuntu 13.10

Revision history for this message
Nick Sharp (njsharp) wrote :

I have this problem on 12.04 with a new Seagate 3TB usb3 external drive ON A USB3 interface. Will test later on 14.04; waiting for final release at present.

For me, safe removal never works (drive always returns) unlike others above, who find it does work second time.

I reduced the problem a little by:

System Settings/Details/Removable Media/Never prompt or start programs on media insertion (TICK)

and dconf-editor:

org.gnome.desktop.media-handling
automount (UNtick)
automount-oepn (UNtick)
automount-never (TICK)

Of course, then I have to open disk utility and mount drives by hand and open the mount point by hand. No big deal.

Interestingly, the problem does not occur if the drive is connected via a USB2 interface, but that rather spoils the point of having a USB3-capable drive! In fact, it dropped the read time to about 1/5th but made almost no difference to the write time, so if your use of the drive is primarily to archive files, it seems: connect via USB2 interface is quite a good idea for now!

I suspect that the issue is related to the USB3 interface, both in the drive and the PC.

A Seagate ST2000DM001 (2Tb USB interface) external drive CONNECTED ON A USB3 INTERFACE DOES behave correctly on SAFE REMOVAL and does NOT reappear in the list in disk utility.

(probably off topic) It is interesting to note that on my drive (Seagate STNV3000300) the interface at the disk enclosure is a PAIR of connectors side by side, not a simple mini or micro USB peripheral interface.

Nick Sharp

Revision history for this message
Don Dennis (metastableb) wrote :

I have the bug on ubuntu 14.04 with my Seagate 1TB Backup plus extrnal hard disk. I had the same problem with ubuntu 13.10 .
The drive automatically remounted after safely removal/ eject in a few seconds.
This behaviour was only with the USB 3 ports of my laptop. Connectd to the USB 2 ports, the harddsik spun down and powered off as it should have.

I even tried using udisks to do the same but the result was the same.

Hope this bug is assigned to someone soon. It has been almost an year for me without a fix.

Revision history for this message
Allan Bogh (ajbogh) wrote :

I have this problem as well with 14.04. The eject button in Nautilus works as I can see the device unmount from /media/username/DeviceName, then it immediately remounts. There are no errors with using "sudo umount /media/username/DeviceName", however the device will also remount.

I've also gotten the error "Cannot eject drive in use: Device /dev/sdg1 is mounted" until I close all Nautilus windows and reopen one, but this may not be related.

Device specs:

- USB 64G (PNY)
- Fat32 format
- 1 Primary partition
- Bootable
- Created with Startup Disk Creator

Revision history for this message
Ronnie Burgos (lavero.burgos) wrote :

I have the same bug. running Ubuntu 14.04 x64, have tried several kernels including the latest 3.14.7 and 3.15 and the bug persists.
i have attached a 3tb HGST formatted with NTFS to my Asus Chromebox to one of its four usb 3.0 ports (no 2.0 here my bad), so no NVIDIA graphis, just intel ones.

is there a temporary fix for this?, anyone? its been many years and nada??? gee this sucks

Revision history for this message
jcsjcs (jcsjcs) wrote :

The only "fix" I know is to open a terminal and to manually unmount the drive:

sudo umount /media/<path_to_your_media>

Revision history for this message
John Trappett (john-trappett) wrote :

The bug is also present here on my USB 3.0 port... USB 2.0 ports are not affected.

Hardware: HP 15-d015tu Notebook PC (http://h10025.www1.hp.com/ewfrf/wc/document?cc=au&lc=en&docname=c04220494)
OS: Ubuntu 14.04

Happy to provide feedback to any developer who wishes to try and solve this long-standing bug.

Revision history for this message
dafreez (dafreez-gmail) wrote :

Same here with two usb-3 drives (usb-2 pendrives not affected). Safely remove not only remounts but also shows al my mouhnted drives previously unlocked form launcher. I can unmount the usb-drives though and then turn them off. Not sure how safe this is??

Revision history for this message
Simon P. (simpre) wrote :

I got the same problem with Ubuntu 14.04, only my USB 3.0 port is affected.

Revision history for this message
zzarko (zzarko-gmail) wrote :

Same problem on 14.04 64bit. Found somewhere this workaround:

gvfs-mount --eject "file:///media/volume_name"

and it works. df -h shows no drive mounted, but Unity launcher isn't aware of that. Still, safe to remove. I didn't had this problem in my previous 12.04/13.10 installations on the same machine.

Revision history for this message
John Trappett (john-trappett) wrote :

That workaround doesn't work for me. There is some activity on the drive light, however, it remains on with the motor running. The only thing that works for me is to close the notebook lid, wait for it to suspend, remove the drive, then open the lid again.

Revision history for this message
jcsjcs (jcsjcs) wrote :

For me a simple

umount /media/<username>/<drive>

does the trick. The drive won't get remounted and is save to remove after the command completes.

Revision history for this message
A J V Prasad (ajvprasad) wrote :

I am experiencing the same issue when I plugged my seagate backup plus in USB 3.0 port and not issue if plugged in usb 2.0. OS: Scientific Linux, kernel 2.6.32 .

And other important observation is the issue is same in windows 7.

Other important observation which may be helpful to trouble shooters is that I experience this issue after I compiled and used the usbreset (usbreset.c) program from
http://unix.stackexchange.com/questions/7051/how-to-re-mount-a-usb-stick-after-unmounting-from-nautilus-without-disconnecting

( I used this program on USB 3.0 port only )

Before that there is no such issue.

My mother board is GIGABYTE 970A-DS3P

From my observations I infer the issue is related with USB controllers/firmware which might have been set right by vendors through some control on chipsets/mother boards which is being reset with usbreset mentioned above or by something else by users and going in to trouble.

Hope these observations lead to solution.
( I already used the work-around : umount before googling the issue and is working fine ).

Revision history for this message
A J V Prasad (ajvprasad) wrote :

I am correcting some typos in my earlier post.

I am experiencing the same issue when I plugged my seagate backup plus in USB 3.0 port and there is no issue if plugged in usb 2.0. OS: Scientific Linux, kernel 2.6.32 .

And other important observation is the issue is same in windows 7.

Other important observation which may be helpful to trouble shooters is that I experience this issue after I compiled and used the usbreset (usbreset.c) program from

I am experiencing the same issue when I plugged my seagate backup plus in USB 3.0 port and not issue if plugged in usb 2.0. OS: Scientific Linux, kernel 2.6.32 .

And other important observation is the issue is same in windows 7.

Other important observation which may be helpful to trouble shooters is that I experience this issue after I compiled and used the usbreset (usbreset.c) program from

http://askubuntu.com/questions/645/how-do-you-reset-a-usb-device-from-the-command-line

( I used this program on USB 3.0 port only )

Before that there is no such issue.

My mother board is GIGABYTE 970A-DS3P

From my observations I infer the issue is related with USB controllers/firmware which might have been set right by vendors through some control on chipsets/mother boards which is being reset with usbreset mentioned above or by something else by users and going in to trouble.

Hope these observations lead to solution.
( I already used the work-around : umount before googling the issue and is working fine ).

( I used this program on USB 3.0 port only )

Before that there is no such issue.

My mother board is GIGABYTE 970A-DS3P

From my observations I infer the issue is related with USB controllers/firmware which might have been set right by vendors through some control on chipsets/mother boards which is being reset with usbreset mentioned above or by something else by users and going in to trouble.

Hope these observations lead to solution.
( I already used the work-around : umount before googling the issue and is working fine ).

Revision history for this message
Peter Kennes (mgt2000) wrote :

I don't have this problem any more with any of my external hard disks :)
Linux kernel version: 3.13.0-36-generic

I didn't use my hard disks for a while so probably there were no problem in some previous kernel versions.

Revision history for this message
A J V Prasad (ajvprasad) wrote :

Dear Peter,

Can you use the usbreset program which is mentioned in my earlier post ? So that You can confirm that recent kernels have fixed the issue.

Thanks

Revision history for this message
Peter Kennes (mgt2000) wrote :

Unfortunately no :( at list not today!

Revision history for this message
Rudolfs Caune (djbacons) wrote :

Still having this problem with one externam HDD (USB). I have 3 of them and two flash drives. All of them unmounts correctly, but one HDD automatically re-mounts back. So i'm forced to just unplug it. :(
Interesting thing is that i have this problem with same HDD on other Ubuntu pcs. 12.04 and 14.04. So this must be something with the HDD, but what?!

Revision history for this message
apinunt (apinunt) wrote :

Experiencing the same problem with 3 Seagate 3TB USB3 drives on a Samsung Gamer Notebook.
3 years and this problem is only assigned a Medium Importance?

Revision history for this message
Graham Mitchell (graham-grahammitchell) wrote :

Still having this problem.

$ uname -a
Linux foo 3.13.0-27-generic #50-Ubuntu SMP Thu May 15 18:06:16 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux
$ cat /etc/lsb-release
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=14.04
DISTRIB_CODENAME=trusty
DISTRIB_DESCRIPTION="Ubuntu 14.04.1 LTS"

Revision history for this message
anw (antoine-spam) wrote :

same here on thunar with xubuntu 14.04 (fresh install) with inateck sata to usb3 docking station...

$ uname -a
Linux ins 3.13.0-39-generic #66-Ubuntu SMP Tue Oct 28 13:30:27 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux

anw@ins:~$ cat /etc/lsb-release
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=14.04
DISTRIB_CODENAME=trusty
DISTRIB_DESCRIPTION="Ubuntu 14.04.1 LTS"

Revision history for this message
Abhirav Kumar (akabhirav) wrote :

This bug has bugged me since ubuntu 11.04 (when I started using Ubuntu) till 14.04 (even though LTS still has this problem) and still there is no one that solves the problem.

As of today I have installed all the update of and using Ubuntu 14.04.1 LTS

When I safely remove my external HDD in a 3.0 USB port it turns off for a second and then restarts and is mounted again.
The same does not happen when I plug my HDD to a 2.0 USB port.

As I have mentioned above, I have lost valuable data because of this bug, please fix it. I will help anyway I can.

Revision history for this message
Fenyvesi Attila (fattila2) wrote :

I am having this bug on Xubuntu 14.10 (Thunar 1.6.3) when trying to unmount a USB 3.0 Seagate 1TB HDD from a USB 3.0 port. I also experience one second off and remounting after that.
I don't have this bug when using USB 2.0 pendrive in USB 3.0 port.

dmesg | grep USB

#after plugged in a USB 2.0 port
[ 1955.357740] usb 1-1.2: new high-speed USB device number 8 using ehci-pci
[ 1955.512198] usb 1-1.2: New USB device found, idVendor=0bc2, idProduct=a013
[ 1955.512205] usb 1-1.2: New USB device strings: Mfr=2, Product=3, SerialNumber=1

#unmounting with Thunar, the device starts spinning again but cannot be seen in /dev/sd*
[ 2109.543249] usb 1-1.2: USB disconnect, device number 8

#after plugged in a USB 3.0 port
[ 2335.126791] usb 4-4: new SuperSpeed USB device number 12 using xhci_hcd
[ 2335.143475] usb 4-4: New USB device found, idVendor=0bc2, idProduct=a013
[ 2335.143482] usb 4-4: New USB device strings: Mfr=2, Product=3, SerialNumber=1

#unmounting with Thunar, the device starts spinning again and Thunar opens the remounted media
[ 2439.351726] usb 4-4: USB disconnect, device number 12
[ 2439.739404] usb 4-4: new SuperSpeed USB device number 13 using xhci_hcd
[ 2439.756138] usb 4-4: New USB device found, idVendor=0bc2, idProduct=a013
[ 2439.756146] usb 4-4: New USB device strings: Mfr=2, Product=3, SerialNumber=1

USB 2.0 pendrive
#automount in USB 3.0 port
[ 3045.472256] usb 3-4: new high-speed USB device number 3 using xhci_hcd
[ 3045.601106] usb 3-4: New USB device found, idVendor=08ec, idProduct=2038
[ 3045.601115] usb 3-4: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 3045.601698] usb-storage 3-4:1.0: USB Mass Storage device detected
#/dev contents
ata@ata-HP-ProBook-6470b:~$ ls /dev/sdb*
/dev/sdb /dev/sdb1

#Thunar gives this error message when unmounting: "Error opening /sys/devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.2/remove: No such file or directory."
#Nothing new in dmesg
#/dev contents
ata@ata-HP-ProBook-6470b:~$ ls /dev/sdb*
/dev/sdb

Revision history for this message
Fenyvesi Attila (fattila2) wrote :

I found two workarounds.

Workaround 1)
On Xubuntu 14.10 using Thunar 1.6.3 file manager I managed to stop the automatic remount of unmounted USB 3.0 drives using USB 3.0 ports.
In Thunar: Edit -> Preferences -> Advanced -> "Configure the management of removable drives and media." -> "Storage" tab:
I unchecked the "Mount removable drives when hot-plugged" option.
With this setting, after unmounting the USB 3.0 device in Thunar, 'dmesg | grep USB' has these new lines:
[ 1902.911399] usb 4-3: USB disconnect, device number 7
[ 1903.395819] usb 4-3: new SuperSpeed USB device number 8 using xhci_hcd
[ 1903.412365] usb 4-3: New USB device found, idVendor=174c, idProduct=55aa
[ 1903.412379] usb 4-3: New USB device strings: Mfr=2, Product=3, SerialNumber=1
[ 1903.413049] usb-storage 4-3:1.0: USB Mass Storage device detected
The USB 3.0 external HDD stops for a second and starts spinning after that (like before unchecking the mentioned preference), the device can be seen in /dev/ but is not mounted. As a side-effect of this, thunar doesn't automount drives plugged in.

Workaround 2)
Instead of using the eject buttons, right-click -> "Unmount" each partition of the device in the file manager (I tested this with Thunar).

Screenshots available at https://www.dropbox.com/sh/iax2x6by866nbtq/AADd3ljfdAn2ljqkZrJg0Spda?dl=0

Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in thunar (Ubuntu):
status: New → Confirmed
Revision history for this message
Ciprian (ciprian420) wrote :

The bug is still here on 14.04

Revision history for this message
jong (agitato816) wrote :

exactly same here 14.04 !!!!
ubuntu 64 bit 14.04

Linux umi 3.13.0-45-generic #74-Ubuntu SMP Tue Jan 13 19:36:28 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux

plz fix it

Revision history for this message
Robert B (robertb-macau) wrote :

This bug affects me too, on 14.04 (kernel 3.13.0-46).

However, the curious thing is that it only affects me with the new Transcend StoreJet 25H3 external HDD (USB 3.0) that I got recently. Before that I was using a Seagate external HDD (also USB 3.0) which I was able to safely remove (either using Nautilus or from the command line with udisks --detach). This seems to suggest that the drive itself is responsible for this behaviour.

The Transcend drive has a hardware button which on Windows is supposed to do a quick reconnect for a detached device, or a one-touch backup when connected. On Linux this button seems not to have any effect, but the fact that the drive can go from detached state back to attached state by its own action could possibly be the reason we're seeing this strange behaviour. Perhaps it's not a bug but a feature...

Revision history for this message
Dhanar Adi Dewandaru (dhanar-adi-dewandaru) wrote :

I have written my finding which might be relevant this bug: http://dhanar10.blogspot.com/2015/03/usb-hdd-gets-mounted-again-after-safely.html

It is on Debian 8 "Jessie" though, but it should be close to Ubuntu 14.04+ right?

I hope this bug can be resolved soon since it has been open for so long and it is affecting Debian, Ubuntu, and other derivatives also.

Revision history for this message
In , Luis-medina-1 (luis-medina-1) wrote :

Created attachment 627090
Output of systemd-journalctl

Powering usb drive ("Safely Remove Drive") isn't working, the HDD gets reattached again.

Revision history for this message
In , Luis-medina-1 (luis-medina-1) wrote :
Revision history for this message
Luis Medina (luis-medina) wrote :

Same issue here:

medina:~ # uname -a
Linux medina 3.16.7-7-desktop #1 SMP PREEMPT Wed Dec 17 18:00:44 UTC 2014 (762f27a) x86_64 x86_64 x86_64 GNU/Linux
medina:~ # cat /etc/os-release
NAME=openSUSE
VERSION="13.2 (Harlequin)"
VERSION_ID="13.2"
PRETTY_NAME="openSUSE 13.2 (Harlequin) (x86_64)"
ID=opensuse
ANSI_COLOR="0;32"
CPE_NAME="cpe:/o:opensuse:opensuse:13.2"
BUG_REPORT_URL="https://bugs.opensuse.org"
HOME_URL="https://opensuse.org/"
ID_LIKE="suse"
medina:~ # lspci
00:00.0 Host bridge: Intel Corporation Broadwell-U Host Bridge -OPI (rev 09)
00:02.0 VGA compatible controller: Intel Corporation Broadwell-U Integrated Graphics (rev 09)
00:03.0 Audio device: Intel Corporation Broadwell-U Audio Controller (rev 09)
00:14.0 USB controller: Intel Corporation Wildcat Point-LP USB xHCI Controller (rev 03)
00:16.0 Communication controller: Intel Corporation Wildcat Point-LP MEI Controller #1 (rev 03)
00:1b.0 Audio device: Intel Corporation Wildcat Point-LP High Definition Audio Controller (rev 03)
00:1c.0 PCI bridge: Intel Corporation Wildcat Point-LP PCI Express Root Port #1 (rev e3)
00:1c.2 PCI bridge: Intel Corporation Wildcat Point-LP PCI Express Root Port #3 (rev e3)
00:1c.3 PCI bridge: Intel Corporation Wildcat Point-LP PCI Express Root Port #4 (rev e3)
00:1c.4 PCI bridge: Intel Corporation Wildcat Point-LP PCI Express Root Port #5 (rev e3)
00:1d.0 USB controller: Intel Corporation Wildcat Point-LP USB EHCI Controller (rev 03)
00:1f.0 ISA bridge: Intel Corporation Wildcat Point-LP LPC Controller (rev 03)
00:1f.2 SATA controller: Intel Corporation Wildcat Point-LP SATA Controller [AHCI Mode] (rev 03)
00:1f.3 SMBus: Intel Corporation Wildcat Point-LP SMBus Controller (rev 03)
02:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 10)
03:00.0 Network controller: Intel Corporation Wireless 7265 (rev 59)
04:00.0 3D controller: NVIDIA Corporation GM108M [GeForce 830M] (rev a2)
medina:~ # lsusb
Bus 001 Device 004: ID 0bda:5754 Realtek Semiconductor Corp.
Bus 001 Device 002: ID 8087:8001 Intel Corp.
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 003 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 002 Device 002: ID 046d:c534 Logitech, Inc.
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

Revision history for this message
Christian Poveda (christianpoved4) wrote :

I'm on ubuntu 14.10 with kernel 3.16 and on debian jessie with kernel 4.0 and stills happens with an Adata external hdd

Revision history for this message
Mika Huurre (mika-huurre) wrote :
Download full text (8.1 KiB)

Ubuntu 15.04, same thing (with HP and Trancend external USB3 hdd both).

ubuntu@hauki:~$ uname -a
Linux hauki 3.19.0-18-generic #18-Ubuntu SMP Tue May 19 18:31:35 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux
ubuntu@hauki:~$ cat /etc/os-release
NAME="Ubuntu"
VERSION="15.04 (Vivid Vervet)"
ID=ubuntu
ID_LIKE=debian
PRETTY_NAME="Ubuntu 15.04"
VERSION_ID="15.04"
HOME_URL="http://www.ubuntu.com/"
SUPPORT_URL="http://help.ubuntu.com/"
BUG_REPORT_URL="http://bugs.launchpad.net/ubuntu/"

ubuntu@hauki:~$ lspci
00:00.0 Host bridge: Intel Corporation 4th Gen Core Processor DRAM Controller (rev 06)
00:01.0 PCI bridge: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor PCI Express x16 Controller (rev 06)
00:14.0 USB controller: Intel Corporation 8 Series/C220 Series Chipset Family USB xHCI (rev 05)
00:16.0 Communication controller: Intel Corporation 8 Series/C220 Series Chipset Family MEI Controller #1 (rev 04)
00:1a.0 USB controller: Intel Corporation 8 Series/C220 Series Chipset Family USB EHCI #2 (rev 05)
00:1b.0 Audio device: Intel Corporation 8 Series/C220 Series Chipset High Definition Audio Controller (rev 05)
00:1c.0 PCI bridge: Intel Corporation 8 Series/C220 Series Chipset Family PCI Express Root Port #1 (rev d5)
00:1c.4 PCI bridge: Intel Corporation 8 Series/C220 Series Chipset Family PCI Express Root Port #5 (rev d5)
00:1d.0 USB controller: Intel Corporation 8 Series/C220 Series Chipset Family USB EHCI #1 (rev 05)
00:1f.0 ISA bridge: Intel Corporation B85 Express LPC Controller (rev 05)
00:1f.2 SATA controller: Intel Corporation 8 Series/C220 Series Chipset Family 6-port SATA Controller 1 [AHCI mode] (rev 05)
00:1f.3 SMBus: Intel Corporation 8 Series/C220 Series Chipset Family SMBus Controller (rev 05)
01:00.0 VGA compatible controller: NVIDIA Corporation GM107 [GeForce GTX 750] (rev a2)
01:00.1 Audio device: NVIDIA Corporation Device 0fbc (rev a1)
03:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 0c)

ubuntu@hauki:~$ lsusb
Bus 004 Device 002: ID 8087:8000 Intel Corp.
Bus 004 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 003 Device 002: ID 8087:8008 Intel Corp.
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 019: ID 03f0:1840 Hewlett-Packard
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 008: ID 05e3:0745 Genesys Logic, Inc.
Bus 001 Device 004: ID 046d:c408 Logitech, Inc. Marble Mouse (4-button)
Bus 001 Device 002: ID 04b4:6560 Cypress Semiconductor Corp. CY7C65640 USB-2.0 "TetraHub"
Bus 001 Device 005: ID 0bda:0151 Realtek Semiconductor Corp. Mass Storage Device (Multicard Reader)
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

/var/log/syslog when trying to eject external hdd with sidepane Eject-'button' and it pops back:

1) Nautilus/Ejecting HP (in sidepane):
May 24 19:19:47 hauki udisksd[1887]: Cleaning up mount point /media/ubuntu/HP500GB1 (device 8:129 is not mounted)
May 24 19:19:47 hauki systemd[1]: Unit media-ubuntu-HP500GB1.mount entered failed state.
May 24 19:19:47 hauki systemd[1]: Found device TOSHIBA_MQ01ABD050 HP500GB.
May 24 19:19:47 hauki ntfs-3g[9889]: Unmou...

Read more...

Revision history for this message
Abhirav Kumar (akabhirav) wrote :

well this bug is sill not fixed in upstream kernel I had Linux 4.0 installed for about a month still had the same problem now I am on Ubuntu 15.04 and I am having the same problem.
Things like this generally don't look good on famous systems also there is a concern for our external drives condition getting deteriorated.
Linux community is one of the biggest developer communities in the verse please do something.

Revision history for this message
In , Tiwai-r (tiwai-r) wrote :

Does "Eject" also behave same? It should really detach without re-probe.
If "Eject" works, it's the answer -- why there are two distinct entries.

(Maybe there aren't on GNOME... It exists on XFCE4, at least.)

Revision history for this message
In , Luis-medina-1 (luis-medina-1) wrote :

The "Eject" button works (Gnome) but it only unmount the partition and does not actually deactivate the disk.

If the disk is connected to an usb 2.0 port "Safely Remove Drive" works, turning off the disk.

Revision history for this message
In , Tiwai-r (tiwai-r) wrote :

Oliver, this seems like a regression with xhci (with respect to ehci). Is there a known fix / workaround?

I also remember that one of my USB disks behaves like this.

Revision history for this message
In , Luis-medina-1 (luis-medina-1) wrote :

(In reply to Takashi Iwai from comment #4)
> Oliver, this seems like a regression with xhci (with respect to ehci). Is
> there a known fix / workaround?
>
> I also remember that one of my USB disks behaves like this.

One workaround is to attach the HDD to an USB 2.0 port.

Revision history for this message
In , Oneukum (oneukum) wrote :

What does the eject command on a terminal do?

Revision history for this message
In , Luis-medina-1 (luis-medina-1) wrote :
Download full text (7.0 KiB)

(In reply to Oliver Neukum from comment #6)
> What does the eject command on a terminal do?

Hi Oliver,

The eject command just unmount the partitions.

medina:~ # eject /dev/sdb

systemd-journalctl log:

Jun 30 13:12:50 medina.novell.com udisksd[2047]: Cleaning up mount point /run/media/luis/LUIS (device 8:17 is not mounted)
Jun 30 13:12:50 medina.novell.com ntfs-3g[4472]: Unmounting /dev/sdb1 (LUIS)
Jun 30 13:12:50 medina.novell.com udisksd[2047]: Cleaning up mount point /run/media/luis/ALBERTO (device 8:18 is not mounted)

However, if detach the hdd it gets remounted in my USB 3.0 port.

medina:~ # udisksctl power-off -b /dev/sdb

systemd-journalctl log:

Jun 30 13:13:01 medina.novell.com udisksd[2047]: Powering off /dev/sdb - successfully sent SCSI command START STOP UNIT
Jun 30 13:13:01 medina.novell.com kernel: sd 7:0:0:0: [sdb] Synchronizing SCSI cache
Jun 30 13:13:01 medina.novell.com udisksd[2047]: Powered off /dev/sdb - successfully wrote to sysfs path /sys/devices/pci0000:00/0000:00:14.0/usb3/3-1/remove
Jun 30 13:13:01 medina.novell.com kernel: sd 7:0:0:0: [sdb]
Jun 30 13:13:01 medina.novell.com kernel: Result: hostbyte=DID_ERROR driverbyte=DRIVER_OK
Jun 30 13:13:01 medina.novell.com kernel: usb 3-1: USB disconnect, device number 5
Jun 30 13:13:01 medina.novell.com kernel: usb 3-1: new SuperSpeed USB device number 6 using xhci_hcd
Jun 30 13:13:01 medina.novell.com kernel: usb 3-1: New USB device found, idVendor=0bc2, idProduct=2321
Jun 30 13:13:01 medina.novell.com kernel: usb 3-1: New USB device strings: Mfr=2, Product=3, SerialNumber=1
Jun 30 13:13:01 medina.novell.com kernel: usb 3-1: Product: Expansion
Jun 30 13:13:01 medina.novell.com kernel: usb 3-1: Manufacturer: Seagate
Jun 30 13:13:01 medina.novell.com kernel: usb 3-1: SerialNumber: NA4BQHLX
Jun 30 13:13:01 medina.novell.com kernel: scsi8 : uas
Jun 30 13:13:01 medina.novell.com kernel: scsi 8:0:0:0: Direct-Access Seagate Expansion 0502 PQ: 0 ANSI: 6
Jun 30 13:13:01 medina.novell.com kernel: sd 8:0:0:0: Attached scsi generic sg1 type 0
Jun 30 13:13:01 medina.novell.com kernel: sd 8:0:0:0: [sdb] 3907029167 512-byte logical blocks: (2.00 TB/1.81 TiB)
Jun 30 13:13:01 medina.novell.com kernel: sd 8:0:0:0: [sdb] 4096-byte physical blocks
Jun 30 13:13:01 medina.novell.com kernel: sd 8:0:0:0: [sdb] Write Protect is off
Jun 30 13:13:01 medina.novell.com kernel: sd 8:0:0:0: [sdb] Mode Sense: 4f 00 00 00
Jun 30 13:13:01 medina.novell.com kernel: sd 8:0:0:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
Jun 30 13:13:01 medina.novell.com mtp-probe[4516]: checking bus 3, device 6: "/sys/devices/pci0000:00/0000:00:14.0/usb3/3-1"
Jun 30 13:13:01 medina.novell.com mtp-probe[4516]: bus: 3, device: 6 was not an MTP device
Jun 30 13:13:03 medina.novell.com kernel: sdb: sdb1 sdb2 sdb3
Jun 30 13:13:03 medina.novell.com kernel: sd 8:0:0:0: [sdb] Attached SCSI disk
Jun 30 13:13:03 medina.novell.com kernel: hfsplus: write access to a journaled filesystem is not supported, use the force option at your own risk, mounting read-only.
Jun 30 13:13:03 medina.novell.com udisksd[2047]: Mounted /dev/sdb2 at /run/media/luis/ALBERTO on behalf of uid 1000
Jun 30 13...

Read more...

Revision history for this message
In , Luis-medina-1 (luis-medina-1) wrote :

*** Bug 859374 has been marked as a duplicate of this bug. ***

Revision history for this message
In , Oneukum (oneukum) wrote :

This is currently handled upstream. The patches are not yet ready. Something is wrong with the port state machine.

Revision history for this message
In , Jslaby-h (jslaby-h) wrote :

It's perhaps ready now :).

Revision history for this message
In , Oneukum (oneukum) wrote :

(In reply to Jiri Slaby from comment #12)
> It's perhaps ready now :).

Indeed. Please test KOTD.

Revision history for this message
In , Luis-medina-1 (luis-medina-1) wrote :
Download full text (5.0 KiB)

Same results with 4.2.rc6-1.1.g4a2cf4a

medina:~ # eject /dev/sdb

systemd-journalctl log:

Aug 13 10:45:10 medina.novell.com udisksd[1953]: Cleaning up mount point /run/media/luis/LUIS (device 8:17 is not mounted)
Aug 13 10:45:10 medina.novell.com ntfs-3g[3278]: Unmounting /dev/sdb1 (LUIS)
Aug 13 10:45:10 medina.novell.com udisksd[1953]: Cleaning up mount point /run/media/luis/ALBERTO (device 8:18 is not mounted)

medina:~ # udisksctl power-off -b /dev/sdb

systemd-journalctl log:

Aug 13 10:45:21 medina.novell.com bluetoothd[997]: Endpoint unregistered: sender=:1.28 path=/MediaEndpoint/A2DPSource
Aug 13 10:45:21 medina.novell.com bluetoothd[997]: Endpoint unregistered: sender=:1.28 path=/MediaEndpoint/A2DPSink
Aug 13 10:45:21 medina.novell.com systemd[1321]: pam_unix(systemd-user:session): session closed for user gdm
Aug 13 10:45:22 medina.novell.com udisksd[1953]: Powering off /dev/sdb - successfully sent SCSI command START STOP UNIT
Aug 13 10:45:22 medina.novell.com kernel: sd 6:0:0:0: [sdb] Synchronizing SCSI cache
Aug 13 10:45:23 medina.novell.com kernel: sd 6:0:0:0: [sdb] Synchronize Cache(10) failed: Result: hostbyte=DID_ERROR driverbyte=DRIVER_OK
Aug 13 10:45:23 medina.novell.com udisksd[1953]: Powered off /dev/sdb - successfully wrote to sysfs path /sys/devices/pci0000:00/0000:00:14.0/usb3/3-1/remove
Aug 13 10:45:23 medina.novell.com kernel: usb 3-1: USB disconnect, device number 4
Aug 13 10:45:23 medina.novell.com kernel: usb 3-1: new SuperSpeed USB device number 5 using xhci_hcd
Aug 13 10:45:23 medina.novell.com kernel: usb 3-1: New USB device found, idVendor=0bc2, idProduct=2321
Aug 13 10:45:23 medina.novell.com kernel: usb 3-1: New USB device strings: Mfr=2, Product=3, SerialNumber=1
Aug 13 10:45:23 medina.novell.com kernel: usb 3-1: Product: Expansion
Aug 13 10:45:23 medina.novell.com kernel: usb 3-1: Manufacturer: Seagate
Aug 13 10:45:23 medina.novell.com kernel: usb 3-1: SerialNumber: NA4BQHLX
Aug 13 10:45:23 medina.novell.com kernel: scsi host7: uas
Aug 13 10:45:23 medina.novell.com kernel: scsi 7:0:0:0: Direct-Access Seagate Expansion 0502 PQ: 0 ANSI: 6
Aug 13 10:45:23 medina.novell.com kernel: sd 7:0:0:0: Attached scsi generic sg1 type 0
Aug 13 10:45:23 medina.novell.com kernel: sd 7:0:0:0: [sdb] 3907029167 512-byte logical blocks: (2.00 TB/1.81 TiB)
Aug 13 10:45:23 medina.novell.com kernel: sd 7:0:0:0: [sdb] 4096-byte physical blocks
Aug 13 10:45:23 medina.novell.com kernel: sd 7:0:0:0: [sdb] Write Protect is off
Aug 13 10:45:23 medina.novell.com kernel: sd 7:0:0:0: [sdb] Mode Sense: 4f 00 00 00
Aug 13 10:45:23 medina.novell.com kernel: sd 7:0:0:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
Aug 13 10:45:23 medina.novell.com mtp-probe[3392]: checking bus 3, device 5: "/sys/devices/pci0000:00/0000:00:14.0/usb3/3-1"
Aug 13 10:45:23 medina.novell.com mtp-probe[3392]: bus: 3, device: 5 was not an MTP device
Aug 13 10:45:25 medina.novell.com kernel: sdb: sdb1 sdb2 sdb3
Aug 13 10:45:25 medina.novell.com kernel: sd 7:0:0:0: [sdb] Attached SCSI disk
Aug 13 10:45:25 medina.novell.com kernel: iwlwifi 0000:03:00.0: request for firmware file 'iwlwifi-7265D-11.ucode' failed.
Aug 13 10:45:25...

Read more...

Revision history for this message
In , Oneukum (oneukum) wrote :

Ok, then this is not the port status issue.
Please activate dynamic debugging of xhci
echo "modules xhci_hcd +p" > /sys/kernel/debug/dynamic_debug/control
and retest.

Revision history for this message
In , Luis-medina-1 (luis-medina-1) wrote :

Created attachment 646177
systemd-journalctl output

Oliver,

Started "systemd-journalctl -f" and then the following commands and/or actions where ejecuted:

{1.- Activate dynamic debugging of xhci}

  medina:~ # date; echo "modules xhci_hcd +p" > /sys/kernel/debug/dynamic_debug/control
  Thu Sep 3 14:35:29 CDT 2015
  -bash: echo: write error: Invalid argument
  medina:~ # date; echo "module xhci_hcd +p" > /sys/kernel/debug/dynamic_debug/control
  Thu Sep 3 14:35:37 CDT 2015

{2.- Inserted HDD}

{3.- Eject HDD}

  medina:~ # date; eject /dev/sdb
  Thu Sep 3 14:36:17 CDT 2015

{4.- PowerOff HDD (with automatic remouting)}

  medina:~ # date; udisksctl power-off -b /dev/sdb
  Thu Sep 3 14:36:29 CDT 2015

{5.- Disable dynamic debugging of xhci}

  medina:~ # date; echo "module xhci_hcd -p" > /sys/kernel/debug/dynamic_debug/control
  Thu Sep 3 14:36:56 CDT 2015

Revision history for this message
In , Oneukum (oneukum) wrote :

Could you please redo and split the logs when you do something?

Revision history for this message
In , Luis-medina-1 (luis-medina-1) wrote :

Created attachment 646529
systemd-journalctl divided by action

Sure,

I attached a tar.gz with three files:

01-insertHDD.log, inserting the HDD...

02-ejectHDD.log, execution of the command "eject /dev/sdb"

03-powerOffHDD.log, powering off and automatic remounting, command "udisksctl power-off -b /dev/sdb"

medina:~ # date; eject /dev/sdb
Tue Sep 8 09:44:07 CDT 2015
medina:~ # date; udisksctl power-off -b /dev/sdb
Tue Sep 8 09:44:33 CDT 2015

Revision history for this message
In , Oneukum (oneukum) wrote :

Inconclusive. Something crashes the drive. Possibly LPM is too much for your device. Please try this kernel disabling it:

https://build.opensuse.org/project/monitor?project=home%3Aoneukum%3Abnc922634_disableLPM

Revision history for this message
Romano Giannetti (romano-giannetti) wrote :

FYI --- using command line to eject the disk/partiton do work, see http://askubuntu.com/questions/422481/prevent-usb-drives-from-auto-remounting-after-remove

On the other hand, I see surprising that this bug is marked Medium. For non-tech-savy users, can ends in unclean disconnect and even data-loss. Should be marked as Critical.

Revision history for this message
Chaim Golenberg (jutko-hapa-nu) wrote :

I have same problem with Transcend 500G USB3 drive.

The problems exists only when I plug it into USB3 port, when I plug it to USB2 port (on the same laptop, I have two types of USBs), "Safely remove dirve" work well.

Revision history for this message
In , Jean-Christophe (jean-christophe-redhat-bugs) wrote :

Description of problem:

When ejecting a drive, from the GUI (Gnome, XFCE, ...) or using udiskctl, I believe udev is responsible of spinning it down.

Some disks spins down but spins up again immediately, forcing the user to do a hot unplug.

How reproducible:

Steps to Reproduce:
1. Plug in an external USB disk
2. Then eject it or do type udisksctl power-off -b /dev/sdx

Actual results:

Some disk models would spin back up, while others will properly shutdown.

Expected results:

All disks should spin down.

Additional info:

All my disks are USB 3.
I have 2 Toshiba external hard drive (500 Mo and 1 To) that do spin down correctly.
I have 1 Seagate Slim hard drive of 500 Mo that also shuts down correctly.

But, another Seagate Slim drive of 1To does spin back up.

Also, strangely, all of these disks do spin back up when they are plugged and ejected from behind an USB 3 hub.

Revision history for this message
Hitechcomputergeek (hitechcomputergeek) wrote :

This happens for me with a Transcend USB3.0 1TB drive. (I checked, and it has the latest firmware, too.) I agree with Romano Giannetti that this should be marked Critical - I can still unmount my main btrfs partition first, which should sync any writes to the disk, but I really don't know how bad it is for the drive's health to then just yank the drive out.

Revision history for this message
陈伟琪 (gameboy709494-d) wrote :
Revision history for this message
陈伟琪 (gameboy709494-d) wrote :

I forgot adding my computer information, sorry:

Master Board: MSI B85i
I7-4790K/8G RAM/1T ST1000DX001-1CM162 DISK.

Revision history for this message
In , Oneukum (oneukum) wrote :

Ping?

Revision history for this message
Almas (almasd) wrote :

Same here 14.04 on Samsung Chronos 7 series notebook with intel chipset and i5 cpu.

Revision history for this message
In , Jean-Christophe (jean-christophe-redhat-bugs) wrote :

A lot of reports on the Ubuntu side for a similar issue: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/792085

The culprit has not been identified yet, apparently.

Revision history for this message
In , Zbigniew (zbigniew-redhat-bugs) wrote :

Based on the comments it appears to be drive/chipset specific and maybe some driver issue. Reassigning to the kernel.

Revision history for this message
In , James (james-redhat-bugs) wrote :

I find this on my enclosures with Asmedia and Norelsys bridges. The JMicron one seems to power down properly.

Revision history for this message
Koopee (koopee1234) wrote :

Same in Archlinux: https://bbs.archlinux.org/viewtopic.php?id=184796
The link does not contain much new information, though.

Revision history for this message
Koopee (koopee1234) wrote :

I changed the topic to address usb 3.0 drives only. At least I do not have any problems in safe removal of USB2 drives.

summary: - Automatic remount of safely removed drive
+ Automatic remount of safely removed usb 3.0 drive
Revision history for this message
Cheng LI (licheng-nwpu2007) wrote :

Same problem here to unmount Seagate 2TB external HDD from USB 3.0 port on 14.04.

Revision history for this message
Kev Bowring (flocculant) wrote :

For the record - this affects in thunar for 16.04.

Revision history for this message
In , Jean-Christophe (jean-christophe-redhat-bugs) wrote :

James, how did you get this info? lsusb,lshw et hdparm do not seem to provide it.

Revision history for this message
Jean-Christophe Baptiste (jc-baptiste) wrote :

I described there : https://bugzilla.redhat.com/show_bug.cgi?id=1278944 or there : https://bugs.freedesktop.org/show_bug.cgi?id=71802

I don't think it is related only to USB 3 or Nautilus. It is a larger udisk or kernel issue with some micro-controllers...

Revision history for this message
C de-Avillez (hggdh2) wrote :

moving wrong assignment in Nautilus to thunar, per Flocculant's request on -bugs.

Changed in nautilus:
importance: Unknown → Undecided
status: Unknown → New
Revision history for this message
C de-Avillez (hggdh2) wrote :
Revision history for this message
EAB (adair-boder) wrote :

Ubuntu 16.04 here and I have this issue with USB 3.0 external HDD.

Revision history for this message
Compu (hotwheels14901) wrote :

i have this issue in 14.04.4 but only when my external hdd is using usb 3.0, if i plug it into a 2.0 only port i dont have this issue

Revision history for this message
Compu (hotwheels14901) wrote :

my drive is a WD My Passport 083A 1TB

Revision history for this message
In , Jean-Christophe (jean-christophe-redhat-bugs) wrote :

Version: 23 → 24

Revision history for this message
In , James (james-redhat-bugs) wrote :

(In reply to Jean-Christophe Baptiste from comment #4)
> James, how did you get this info? lsusb,lshw et hdparm do not seem to
> provide it.

Sorry for the very late reply. Sometimes the info identifying the bridge chip is in dmesg. Otherwise I look up the USB numeric IDs on Google. This is for generic enclosures only. In my experience, the bridge on the 'complete' big-brand drives have their firmwares and device IDs modified for hide the chip's origin.

Revision history for this message
Petrus Adamus (dohnp5a1) wrote :

The problem is still there in Ubuntu 16.04 on ASUS N750JV-T4148 for my ADATA NH13 HDD 2.5" 1000GB.

Revision history for this message
In , Wolfgang (wolfgang-redhat-bugs) wrote :

I see this behaviour as well on fully patched Fedora 24 with
kernel-4.6.4-301.fc24.x86_64

I have a LaCie 9223 1TB with USB ID 059f:1070. According to a google search this device uses a ASMedia 1053.
According to smartctl the HDD is a
Device Model: ST1000LM035-1RK172

If connected to USB 3 port on a
Gigabyte B85M-HD3 with
00:14.0 8086:8c31 USB controller: Intel Corporation 8 Series/C220 Series Chipset Family USB xHCI (rev 04)
or a
ASUS Z170-P D3 onboard USB port

the drive powers down using "safely remove drive"...
Aug 9 10:56:16 pcwb ntfs-3g[11727]: Unmounting /dev/sdb1 (LaCie-1TB)
Aug 9 10:56:16 pcwb udisksd[1491]: Unmounted /dev/sdb1 on behalf of uid 1000
Aug 9 10:56:16 pcwb udisksd[1491]: Successfully sent SCSI command SYNCHRONIZE CACHE to /dev/sdb
Aug 9 10:56:17 pcwb udisksd[1491]: Successfully sent SCSI command START STOP UNIT to /dev/sdb
Aug 9 10:56:17 pcwb systemd-udevd: inotify_add_watch(9, /dev/sdb1, 10) failed: No such file or directory
Aug 9 10:56:17 pcwb kernel: sd 6:0:0:0: [sdb] Synchronizing SCSI cache
Aug 9 10:56:17 pcwb kernel: sd 6:0:0:0: [sdb] Synchronize Cache(10) failed: Result: hostbyte=DID_ERROR driverbyte=DRIVER_OK
Aug 9 10:56:17 pcwb udisksd[1491]: Powered off /dev/sdb - successfully wrote to sysfs path /sys/devices/pci0000:00/0000:00:14.0/usb4/4
-1/remove
Aug 9 10:56:17 pcwb kernel: usb 4-1: USB disconnect, device number 21

and immediately reappears...
Aug 9 10:56:17 pcwb kernel: usb 4-1: new SuperSpeed USB device number 22 using xhci_hcd
Aug 9 10:56:17 pcwb kernel: usb 4-1: New USB device found, idVendor=059f, idProduct=1070
Aug 9 10:56:17 pcwb kernel: usb 4-1: New USB device strings: Mfr=2, Product=3, SerialNumber=1
Aug 9 10:56:17 pcwb kernel: usb 4-1: Product: Porsche Mobile for Mac
Aug 9 10:56:17 pcwb kernel: usb 4-1: Manufacturer: LaCie

Revision history for this message
Koopee (koopee1234) wrote :

Updated to Ubuntu 16.04 and the issue persists. How the importance of this issue could be raised? USB 2 works fine, USB3 does not.

Revision history for this message
Norbert (nrbrtx) wrote : Re: [Bug 792085] Re: Automatic remount of safely removed usb 3.0 drive

I think we should inform udisks developer - David Zeuthen.

Dear David!
Please read linked bug report carefully (especially comment 79
<https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/792085/comments/79>
with blog post
<http://dhanar10.blogspot.com/2015/03/usb-hdd-gets-mounted-again-after-safely.html>).
It seems that problem came from udisks.
Modern Fedora and RedHat are affected too
<https://bugzilla.redhat.com/show_bug.cgi?id=1278944>.
Arch is affected by this bug see forum
<https://bbs.archlinux.org/viewtopic.php?id=184796>.

It may cause data loss!
Please investigate, confirm and fix this bug!

With best regards,
Norbert.

On Fri, Aug 26, 2016 at 12:07 PM, Koopee <email address hidden> wrote:

> Updated to Ubuntu 16.04 and the issue persists. How the importance of
> this issue could be raised? USB 2 works fine, USB3 does not.
>
> --
> You received this bug notification because you are subscribed to a
> duplicate bug report (1194608).
> https://bugs.launchpad.net/bugs/792085
>
> Title:
> Automatic remount of safely removed usb 3.0 drive
>
> Status in Nautilus:
> New
> Status in thunar:
> Unknown
> Status in nautilus package in Ubuntu:
> Confirmed
> Status in thunar package in Ubuntu:
> Confirmed
> Status in udev package in Ubuntu:
> Confirmed
>
> Bug description:
> Binary package hint: nautilus
>
> When I choose "Safely remove drive" context menu entry for an external
> USB drive within a nautilus window or directly clicking on the desktop
> icon, after about 10 seconds the drive is automatically remounted and
> a Nautilus window showing the root folder opens.
>
> I have noticed that similar already happened with a very old Ubuntu
> version - Bug #110589 and as that is so long time ago I thought it is
> better to open a new bug. Reason of the problem might even be
> completely different.
>
> ProblemType: Bug
> DistroRelease: Ubuntu 11.04
> Package: nautilus 1:2.32.2.1-0ubuntu13
> ProcVersionSignature: Ubuntu 2.6.38-8.42-generic-pae 2.6.38.2
> Uname: Linux 2.6.38-8-generic-pae i686
> Architecture: i386
> Date: Thu Jun 2 23:40:08 2011
> InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release i386
> (20110427.1)
> ProcEnviron:
> LANGUAGE=en_US:en
> LANG=en_US.UTF-8
> SHELL=/bin/bash
> SourcePackage: nautilus
> UpgradeStatus: No upgrade log present (probably fresh install)
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/nautilus/+bug/792085/+subscriptions
>

Revision history for this message
Norbert (nrbrtx) wrote :

OK, David. I'm sorry.

On Fri, Aug 26, 2016 at 12:59 PM, David Zeuthen <email address hidden> wrote:

> I have not worked on udisks since 2013. Please remove me from the Cc.
> Thanks.
>
> On Fri, Aug 26, 2016 at 5:53 AM Nrbrtx <email address hidden> wrote:
>
>> I think we should inform udisks developer - David Zeuthen.
>>
>> Dear David!
>> Please read linked bug report carefully (especially comment 79
>> <https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/792085/comments/79>
>> with blog post
>> <http://dhanar10.blogspot.com/2015/03/usb-hdd-gets-mounted-again-after-safely.html>).
>> It seems that problem came from udisks.
>> Modern Fedora and RedHat are affected too
>> <https://bugzilla.redhat.com/show_bug.cgi?id=1278944>.
>> Arch is affected by this bug see forum
>> <https://bbs.archlinux.org/viewtopic.php?id=184796>.
>>
>> It may cause data loss!
>> Please investigate, confirm and fix this bug!
>>
>> With best regards,
>> Norbert.
>>
>> On Fri, Aug 26, 2016 at 12:07 PM, Koopee <email address hidden>
>> wrote:
>>
>>> Updated to Ubuntu 16.04 and the issue persists. How the importance of
>>> this issue could be raised? USB 2 works fine, USB3 does not.
>>>
>>> --
>>> You received this bug notification because you are subscribed to a
>>> duplicate bug report (1194608).
>>> https://bugs.launchpad.net/bugs/792085
>>>
>>> Title:
>>> Automatic remount of safely removed usb 3.0 drive
>>>
>>> Status in Nautilus:
>>> New
>>> Status in thunar:
>>> Unknown
>>> Status in nautilus package in Ubuntu:
>>> Confirmed
>>> Status in thunar package in Ubuntu:
>>> Confirmed
>>> Status in udev package in Ubuntu:
>>> Confirmed
>>>
>>> Bug description:
>>> Binary package hint: nautilus
>>>
>>> When I choose "Safely remove drive" context menu entry for an external
>>> USB drive within a nautilus window or directly clicking on the desktop
>>> icon, after about 10 seconds the drive is automatically remounted and
>>> a Nautilus window showing the root folder opens.
>>>
>>> I have noticed that similar already happened with a very old Ubuntu
>>> version - Bug #110589 and as that is so long time ago I thought it is
>>> better to open a new bug. Reason of the problem might even be
>>> completely different.
>>>
>>> ProblemType: Bug
>>> DistroRelease: Ubuntu 11.04
>>> Package: nautilus 1:2.32.2.1-0ubuntu13
>>> ProcVersionSignature: Ubuntu 2.6.38-8.42-generic-pae 2.6.38.2
>>> Uname: Linux 2.6.38-8-generic-pae i686
>>> Architecture: i386
>>> Date: Thu Jun 2 23:40:08 2011
>>> InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release i386
>>> (20110427.1)
>>> ProcEnviron:
>>> LANGUAGE=en_US:en
>>> LANG=en_US.UTF-8
>>> SHELL=/bin/bash
>>> SourcePackage: nautilus
>>> UpgradeStatus: No upgrade log present (probably fresh install)
>>>
>>> To manage notifications about this bug go to:
>>> https://bugs.launchpad.net/nautilus/+bug/792085/+subscriptions
>>>
>>
>>

Revision history for this message
Norbert (nrbrtx) wrote :

Dear udisks developers (Martin Pitt, Tom Yan, Simon McVittie, Kylie
McClain, Mike Frysinger, Mathieu Trudel-Lapierre, Peter Hatina, Phillip
Susi)!

Please read this bug report carefully (especially comment 79
<https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/792085/comments/79>
with blog post
<http://dhanar10.blogspot.com/2015/03/usb-hdd-gets-mounted-again-after-safely.html>
).
It seems that problem came from udisks.
Modern Fedora and RedHat are affected too
<https://bugzilla.redhat.com/show_bug.cgi?id=1278944>.
Arch is affected by this bug (see forum
<https://bbs.archlinux.org/viewtopic.php?id=184796>).

It may cause data loss!
Please investigate, confirm and fix this bug!

On Fri, Aug 26, 2016 at 12:07 PM, Koopee <email address hidden> wrote:

> Updated to Ubuntu 16.04 and the issue persists. How the importance of
> this issue could be raised? USB 2 works fine, USB3 does not.
>
> --
> You received this bug notification because you are subscribed to a
> duplicate bug report (1194608).
> https://bugs.launchpad.net/bugs/792085
>
> Title:
> Automatic remount of safely removed usb 3.0 drive
>
> Status in Nautilus:
> New
> Status in thunar:
> Unknown
> Status in nautilus package in Ubuntu:
> Confirmed
> Status in thunar package in Ubuntu:
> Confirmed
> Status in udev package in Ubuntu:
> Confirmed
>
> Bug description:
> Binary package hint: nautilus
>
> When I choose "Safely remove drive" context menu entry for an external
> USB drive within a nautilus window or directly clicking on the desktop
> icon, after about 10 seconds the drive is automatically remounted and
> a Nautilus window showing the root folder opens.
>
> I have noticed that similar already happened with a very old Ubuntu
> version - Bug #110589 and as that is so long time ago I thought it is
> better to open a new bug. Reason of the problem might even be
> completely different.
>
> ProblemType: Bug
> DistroRelease: Ubuntu 11.04
> Package: nautilus 1:2.32.2.1-0ubuntu13
> ProcVersionSignature: Ubuntu 2.6.38-8.42-generic-pae 2.6.38.2
> Uname: Linux 2.6.38-8-generic-pae i686
> Architecture: i386
> Date: Thu Jun 2 23:40:08 2011
> InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release i386
> (20110427.1)
> ProcEnviron:
> LANGUAGE=en_US:en
> LANG=en_US.UTF-8
> SHELL=/bin/bash
> SourcePackage: nautilus
> UpgradeStatus: No upgrade log present (probably fresh install)
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/nautilus/+bug/792085/+subscriptions
>

Revision history for this message
Eero (eero+launchpad) wrote :

How this bug can exist for over 5 years with a low priority, when there's a real possibility of data loss?

Revision history for this message
JK (ogni11) wrote :

Definitely not Nautilus related. The same occurs if you run “Disks” utility, select a USB 3 disk and then “Power off” from the menu near the top-right corner. To securely remove a USB 3 disk I unmount it first then run “Disks” utility, select it and then press “Standby Now” from the same menu. No problems so far. Could this be a temporary solution until this is fixed?

Revision history for this message
Simon McVittie (smcv) wrote :

> Dear udisks developers (Martin Pitt, Tom Yan, Simon McVittie, Kylie McClain, Mike Frysinger, Mathieu Trudel-Lapierre, Peter Hatina, Phillip Susi)!

No, this is not appropriate. It is ridiculous to assume that anyone who has ever contributed to a project is a maintainer for that project, responsible for that project, or responsible for fixing your favourite bug (even if it is common and serious). If that was how it worked, nobody rational would ever contribute anything.

If you want to pay someone to be responsible for fixing your favourite bug, various companies offer support contracts. Otherwise, those who do the work (in this case neither you nor me) set their own priorities.

Revision history for this message
In , Laura (laura-redhat-bugs) wrote :

*********** MASS BUG UPDATE **************

We apologize for the inconvenience. There is a large number of bugs to go through and several of them have gone stale. Due to this, we are doing a mass bug update across all of the Fedora 24 kernel bugs.

Fedora 24 has now been rebased to 4.7.4-200.fc24. Please test this kernel update (or newer) and let us know if you issue has been resolved or if it is still present with the newer kernel.

If you have moved on to Fedora 25, and are still experiencing this issue, please change the version to Fedora 25.

If you experience different issues, please open a new bug report for those.

Revision history for this message
In , Jean-Christophe (jean-christophe-redhat-bugs) wrote :

The bug is still here with latest kernel version.

Revision history for this message
In , James (james-redhat-bugs) wrote :

(In reply to Jean-Christophe Baptiste from comment #9)
> The bug is still here with latest kernel version.

Confirmed.

Revision history for this message
In , Oneukum (oneukum) wrote :

Upstream has provided a fix:

commit 91ff70db0c49d22fac1b249bd16949978406c271
Author: Mathias Nyman <email address hidden>
Date: Mon Aug 29 14:45:17 2016 +0300

    usb: hub: Fix auto-remount of safely removed or ejected USB-3 devices

    USB-3 does not have any link state that will avoid negotiating a connection
    with a plugged-in cable but will signal the host when the cable is
    unplugged.

    For USB-3 we used to first set the link to Disabled, then to RxDdetect to
    be able to detect cable connects or disconnects. But in RxDetect the connected
    device is detected again and eventually enabled.

    Instead set the link into U3 and disable remote wakeups for the device.
    This is what Windows does, and what Alan Stern suggested.

Revision history for this message
In , Oneukum (oneukum) wrote :

fix added to kernel trees

Revision history for this message
msj (mallikarjunasj) wrote :

For USB 3.0 Disks, Across Ubuntu Distros..... This surely needs to have more priority.

Unless this is fixed, We noobs might simply give up on Ubuntu/Linux altogether.

My Machine: Ubuntu 14.04 LTS, NVidia Chipset, Asus X552C

Device: Seagate BackupPlus 1 TB USB POwered Ext Hard disk Issue: Ext HDD keeps spinning(I place the palm below Ext HDD & feel the spinning is still On), Light keeps glowing, Nautilus Left Side Panel shows the disk is till mounted.

mount will list all mounted disks.. I used & found Seagate HDD is mounted as /dev/sdb1 I installed udisks using apt-get & ran these 2 commands in terminal. udisks --unmount /dev/sdb1 udisks --detach /dev/sdb

Caution***not udisks --detach /dev/sdb1, It is /dev/sdb

Now, the Nautilus Left Side Panel doesn't show the mounted icon for the Ext HDD, but the spinning is still on.

I tried sudo umount -f /dev/sdb1

I get the error, umount2: Invalid argument umount: /dev/sdb1: not mounted

My Problem is I've already lost 2 different 1 TB HDD's while working on Ubuntu. Data Retrieval costs are upwards of $3.5 per GB in Bangalore (200 INR per GB at SP Road....)

Does anyone have a solution..... Note: I've had the Ext HDD attached to the laptop from past 7 days & spinning is still On.

I'm at end of my wits & can't afford to loose the data in this HDD.

Changed in opensuse:
importance: Unknown → Medium
status: Unknown → Fix Released
Revision history for this message
god (humper) wrote :

I think it would be much better to just switch to systemd-mount for all removable media - see https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1627546 for details.

Revision history for this message
Norbert (nrbrtx) wrote :

Dear Ubuntu developers!

Please apply SUSE's patch on kernels in Ubuntu 12.04 LTS, 14.04 LTS, 16.04 LTS, 16.10 - http://kernel.suse.com/cgit/kernel-source/commit/?id=43e64619bd7eeb1f3d287e8faffc16ed3c1f2a2b .

tags: added: precise trusty xenial
tags: removed: i386
Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in linux (Ubuntu):
status: New → Confirmed
Brad Figg (brad-figg)
affects: linux-meta (Ubuntu) → linux (Ubuntu)
Changed in linux (Ubuntu):
status: New → Confirmed
Changed in thunar (Ubuntu):
importance: Undecided → Medium
Changed in linux (Ubuntu):
importance: Undecided → Medium
Changed in nautilus (Ubuntu):
importance: Low → Medium
Revision history for this message
In , Swamp-a (swamp-a) wrote :

openSUSE-SU-2016:2583-1: An update that solves four vulnerabilities and has 21 fixes is now available.

Category: security (important)
Bug References: 1000287,1000304,1000907,1001462,1001486,1004418,1004462,1005101,799133,881008,909994,911687,922634,963655,972460,978094,979681,987703,991247,991665,993890,993891,996664,999600,999932
CVE References: CVE-2016-5195,CVE-2016-7039,CVE-2016-7425,CVE-2016-8658
Sources used:
openSUSE Leap 42.1 (src): drbd-8.4.6-10.1, hdjmod-1.28-26.1, ipset-6.25.1-7.1, kernel-debug-4.1.34-33.1, kernel-default-4.1.34-33.1, kernel-docs-4.1.34-33.3, kernel-ec2-4.1.34-33.1, kernel-obs-build-4.1.34-33.1, kernel-obs-qa-4.1.34-33.1, kernel-obs-qa-xen-4.1.34-33.1, kernel-pae-4.1.34-33.1, kernel-pv-4.1.34-33.1, kernel-source-4.1.34-33.1, kernel-syms-4.1.34-33.1, kernel-vanilla-4.1.34-33.1, kernel-xen-4.1.34-33.1, lttng-modules-2.7.0-4.1, pcfclock-0.44-268.1, vhba-kmp-20140928-7.1

Revision history for this message
In , Bwiedemann (bwiedemann) wrote :

This is an autogenerated message for OBS integration:
This bug (922634) was mentioned in
https://build.opensuse.org/request/show/437000 13.2 / kernel-source

Revision history for this message
In , Swamp-a (swamp-a) wrote :

openSUSE-SU-2016:2625-1: An update that solves 12 vulnerabilities and has 19 fixes is now available.

Category: security (important)
Bug References: 1000287,1001486,1003077,1003925,1003931,1004045,1004418,1004462,881008,909994,911687,922634,951155,960689,978094,980371,986570,989152,991247,991608,991665,993890,993891,994296,994520,994748,994752,994759,996664,999600,999932
CVE References: CVE-2015-7513,CVE-2015-8956,CVE-2016-0823,CVE-2016-1237,CVE-2016-5195,CVE-2016-5696,CVE-2016-6327,CVE-2016-6480,CVE-2016-6828,CVE-2016-7117,CVE-2016-7425,CVE-2016-8658
Sources used:
openSUSE 13.2 (src): bbswitch-0.8-3.22.1, cloop-2.639-14.22.1, crash-7.0.8-22.1, hdjmod-1.28-18.23.1, ipset-6.23-22.1, kernel-debug-3.16.7-45.1, kernel-default-3.16.7-45.1, kernel-desktop-3.16.7-45.1, kernel-docs-3.16.7-45.2, kernel-ec2-3.16.7-45.1, kernel-obs-build-3.16.7-45.1, kernel-obs-qa-3.16.7-45.1, kernel-obs-qa-xen-3.16.7-45.1, kernel-pae-3.16.7-45.1, kernel-source-3.16.7-45.1, kernel-syms-3.16.7-45.1, kernel-vanilla-3.16.7-45.1, kernel-xen-3.16.7-45.1, pcfclock-0.44-260.22.1, vhba-kmp-20140629-2.22.1, virtualbox-5.0.28-54.2, xen-4.4.4_05-51.2, xtables-addons-2.6-24.1

summary: - Automatic remount of safely removed usb 3.0 drive
+ Automatic remount of safely removed USB 3.0 drive
Revision history for this message
In , Swamp-a (swamp-a) wrote :

SUSE-SU-2016:2912-1: An update that solves 11 vulnerabilities and has 111 fixes is now available.

Category: security (important)
Bug References: 1000189,1000287,1000304,1000776,1001419,1001486,1002165,1003079,1003153,1003400,1003568,1003866,1003925,1003964,1004252,1004462,1004517,1004520,1005666,1006691,1007615,1007886,744692,772786,789311,857397,860441,865545,866130,868923,874131,876463,898675,904489,909994,911687,915183,921338,921784,922064,922634,924381,924384,930399,931454,934067,937086,937888,940545,941420,946309,955446,956514,959463,961257,962846,966864,967640,970943,971975,971989,974406,974620,975596,975772,976195,977687,978094,979451,979928,982783,983619,984194,984419,984779,984992,985562,986445,987192,987333,987542,987565,987621,987805,988440,988617,988715,989152,989953,990245,991247,991608,991665,992244,992555,992591,992593,992712,993392,993841,993890,993891,994296,994438,994520,994748,995153,995968,996664,997059,997299,997708,997896,998689,998795,998825,999577,999584,999600,999779,999907,999932
CVE References: CVE-2015-8956,CVE-2016-5696,CVE-2016-6130,CVE-2016-6327,CVE-2016-6480,CVE-2016-6828,CVE-2016-7042,CVE-2016-7097,CVE-2016-7425,CVE-2016-8658,CVE-2016-8666
Sources used:
SUSE Linux Enterprise Workstation Extension 12-SP1 (src): kernel-default-3.12.67-60.64.18.1
SUSE Linux Enterprise Software Development Kit 12-SP1 (src): kernel-docs-3.12.67-60.64.18.3, kernel-obs-build-3.12.67-60.64.18.1
SUSE Linux Enterprise Server 12-SP1 (src): kernel-default-3.12.67-60.64.18.1, kernel-source-3.12.67-60.64.18.1, kernel-syms-3.12.67-60.64.18.1, kernel-xen-3.12.67-60.64.18.1
SUSE Linux Enterprise Module for Public Cloud 12 (src): kernel-ec2-3.12.67-60.64.18.1
SUSE Linux Enterprise Live Patching 12 (src): kgraft-patch-SLE12-SP1_Update_9-1-6.3
SUSE Linux Enterprise Desktop 12-SP1 (src): kernel-default-3.12.67-60.64.18.1, kernel-source-3.12.67-60.64.18.1, kernel-syms-3.12.67-60.64.18.1, kernel-xen-3.12.67-60.64.18.1

Revision history for this message
Norbert (nrbrtx) wrote :

Dear Ubuntu developers!

Please apply SUSE's patch on kernels in Ubuntu 12.04 LTS, 14.04 LTS, 16.04 LTS, 16.10 - http://kernel.suse.com/cgit/kernel-source/commit/?id=43e64619bd7eeb1f3d287e8faffc16ed3c1f2a2b .

Why it is so difficult?
Why you ignore this serious bug?

Many users have USB 3.0 on their computers for at least seven years.
Switching to OpenSUSE from Ubuntu is not good option.

Revision history for this message
In , Jean-Christophe (jean-christophe-redhat-bugs) wrote :

Still in Fedora 25.

Revision history for this message
In , Swamp-a (swamp-a) wrote :

SUSE-SU-2016:2976-1: An update that solves 13 vulnerabilities and has 87 fixes is now available.

Category: security (important)
Bug References: 1000189,1001419,1002165,1003077,1003344,1003568,1003677,1003866,1003925,1004517,1004520,1005857,1005896,1005903,1006917,1006919,1007944,763198,771065,799133,803320,839104,843236,860441,863873,865783,871728,907611,908458,908684,909077,909350,909484,909618,909994,911687,915183,920016,922634,922947,928138,929141,934760,951392,956514,960689,963655,967716,968010,968014,971975,971989,973203,974620,976867,977687,979514,979595,979681,980371,982218,982783,983535,983619,984102,984194,984992,985206,986337,986362,986365,986445,987565,988440,989152,989261,989764,989779,991608,991665,991923,992566,993127,993890,993891,994296,994436,994618,994759,994926,995968,996329,996664,997708,998399,998689,999584,999600,999907,999932
CVE References: CVE-2013-4312,CVE-2015-7513,CVE-2015-8956,CVE-2016-0823,CVE-2016-3841,CVE-2016-4998,CVE-2016-5696,CVE-2016-6480,CVE-2016-6828,CVE-2016-7042,CVE-2016-7097,CVE-2016-7117,CVE-2016-7425
Sources used:
SUSE Linux Enterprise Software Development Kit 11-SP4 (src): kernel-docs-3.0.101-88.3
SUSE Linux Enterprise Server 11-SP4 (src): kernel-bigmem-3.0.101-88.1, kernel-default-3.0.101-88.1, kernel-ec2-3.0.101-88.1, kernel-pae-3.0.101-88.1, kernel-ppc64-3.0.101-88.1, kernel-source-3.0.101-88.1, kernel-syms-3.0.101-88.1, kernel-trace-3.0.101-88.1, kernel-xen-3.0.101-88.1
SUSE Linux Enterprise Server 11-EXTRA (src): kernel-default-3.0.101-88.1, kernel-pae-3.0.101-88.1, kernel-ppc64-3.0.101-88.1, kernel-trace-3.0.101-88.1, kernel-xen-3.0.101-88.1
SUSE Linux Enterprise Debuginfo 11-SP4 (src): kernel-bigmem-3.0.101-88.1, kernel-default-3.0.101-88.1, kernel-ec2-3.0.101-88.1, kernel-pae-3.0.101-88.1, kernel-ppc64-3.0.101-88.1, kernel-trace-3.0.101-88.1, kernel-xen-3.0.101-88.1

Revision history for this message
In , Swamp-a (swamp-a) wrote :

openSUSE-SU-2016:3021-1: An update that solves 12 vulnerabilities and has 118 fixes is now available.

Category: security (important)
Bug References: 1000189,1000287,1000304,1000776,1001419,1001486,1002165,1003079,1003153,1003400,1003568,1003866,1003925,1004252,1004418,1004462,1004517,1004520,1005666,1006691,1007615,1007886,744692,772786,789311,799133,857397,860441,865545,866130,868923,874131,875631,876145,876463,898675,904489,909994,911687,915183,921338,921784,922064,922634,924381,924384,930399,931454,934067,937086,937888,940545,941420,946309,954986,955446,956514,959463,961257,962846,963655,963767,966864,967640,970943,971975,971989,974406,974620,975596,975772,976195,977687,978094,979451,979681,979928,982783,983619,984194,984419,984779,984992,985562,986445,987192,987333,987542,987565,987621,987805,988440,988617,988715,989152,989953,990245,991247,991608,991665,992244,992555,992591,992593,992712,993392,993841,993890,993891,994296,994438,994520,994748,994758,995153,995968,996664,997059,997299,997708,997896,998689,998795,998825,999577,999584,999600,999779,999907,999932
CVE References: CVE-2013-5634,CVE-2015-8956,CVE-2016-2069,CVE-2016-5696,CVE-2016-6130,CVE-2016-6327,CVE-2016-6480,CVE-2016-6828,CVE-2016-7042,CVE-2016-7097,CVE-2016-7425,CVE-2016-8658
Sources used:
openSUSE 13.1 (src): cloop-2.639-11.36.1, crash-7.0.2-2.36.1, hdjmod-1.28-16.36.1, ipset-6.21.1-2.40.1, iscsitarget-1.4.20.3-13.36.1, kernel-debug-3.12.67-58.1, kernel-default-3.12.67-58.1, kernel-desktop-3.12.67-58.1, kernel-docs-3.12.67-58.2, kernel-ec2-3.12.67-58.1, kernel-pae-3.12.67-58.1, kernel-source-3.12.67-58.1, kernel-syms-3.12.67-58.1, kernel-trace-3.12.67-58.1, kernel-vanilla-3.12.67-58.1, kernel-xen-3.12.67-58.1, ndiswrapper-1.58-37.1, openvswitch-1.11.0-0.43.1, pcfclock-0.44-258.37.1, vhba-kmp-20130607-2.36.1, virtualbox-4.2.36-2.68.1, xen-4.3.4_10-69.1, xtables-addons-2.3-2.35.1

Revision history for this message
Norbert (nrbrtx) wrote :

Dear Ubuntu developers!

Please apply SUSE's patch on kernels in Ubuntu 12.04 LTS, 14.04 LTS, 16.04 LTS, 16.10 - http://kernel.suse.com/cgit/kernel-source/commit/?id=43e64619bd7eeb1f3d287e8faffc16ed3c1f2a2b .

Revision history for this message
In , Swamp-a (swamp-a) wrote :

SUSE-SU-2016:3304-1: An update that solves 13 vulnerabilities and has 118 fixes is now available.

Category: security (important)
Bug References: 1000189,1000287,1000304,1000776,1001419,1001486,1002165,1003079,1003153,1003400,1003568,1003925,1004252,1004418,1004462,1004517,1004520,1005666,1006691,1007615,1007886,744692,789311,857397,860441,865545,866130,868923,874131,875631,876145,876463,898675,904489,909994,911687,915183,921338,921784,922064,922634,924381,924384,930399,934067,937086,937888,941420,946309,955446,956514,959463,961257,962846,963655,963767,966864,967640,970943,971975,971989,974406,974620,975596,975772,976195,977687,978094,979451,979681,979928,980371,981597,982783,983619,984194,984419,984779,984992,985562,986362,986365,986445,987192,987333,987542,987565,987621,987805,988440,988617,988715,989152,989953,990058,990245,991247,991608,991665,991667,992244,992555,992568,992591,992593,992712,993392,993841,993890,993891,994167,994296,994438,994520,994758,995153,995968,996664,997059,997299,997708,997896,998689,998795,998825,999577,999584,999600,999779,999907,999932
CVE References: CVE-2015-8956,CVE-2016-2069,CVE-2016-4998,CVE-2016-5195,CVE-2016-5696,CVE-2016-6130,CVE-2016-6327,CVE-2016-6480,CVE-2016-6828,CVE-2016-7042,CVE-2016-7097,CVE-2016-7425,CVE-2016-8658
Sources used:
SUSE Linux Enterprise Real Time Extension 12-SP1 (src): kernel-compute-3.12.67-60.27.1, kernel-compute_debug-3.12.67-60.27.1, kernel-rt-3.12.67-60.27.1, kernel-rt_debug-3.12.67-60.27.1, kernel-source-rt-3.12.67-60.27.1, kernel-syms-rt-3.12.67-60.27.1

no longer affects: nautilus (Ubuntu Xenial)
no longer affects: nautilus (Ubuntu Yakkety)
no longer affects: thunar (Ubuntu Xenial)
no longer affects: thunar (Ubuntu Yakkety)
no longer affects: udev (Ubuntu Xenial)
no longer affects: udev (Ubuntu Yakkety)
Changed in linux (Ubuntu Xenial):
assignee: nobody → Joseph Salisbury (jsalisbury)
importance: Undecided → Medium
status: New → In Progress
Changed in linux (Ubuntu Yakkety):
assignee: nobody → Joseph Salisbury (jsalisbury)
importance: Undecided → Medium
status: New → In Progress
Changed in linux (Ubuntu):
assignee: nobody → Joseph Salisbury (jsalisbury)
status: Confirmed → In Progress
Revision history for this message
Joseph Salisbury (jsalisbury) wrote :

I built a test kernel for Xenial and Yakkety with the following commit:
37be66767e3c usb: hub: Fix auto-remount of safely removed or ejected USB-3 devices

The test kernels can be downloaded from:
Xenial: http://kernel.ubuntu.com/~jsalisbury/lp792085/xenial
Yakkety: http://kernel.ubuntu.com/~jsalisbury/lp792085/yakkety

Can someone affected by this bug test the kernels and see if they resolve this bug? Precise and Trusty require some backporting, so I'll review to see if any prereq commits are also needed for commit 37be66767e3c to apply.

Also, this commit was cc'd to upstream stable, so all supported upstream stable kernels should get it.

Revision history for this message
Kev Bowring (flocculant) wrote :

@jsalisbury

I've downloaded the patched kernels for both Xenial and Yakkety.

For both I tested copying to drive and ejecting. Also tested just mounting and ejecting.

In both it worked as expected - no re-mounting of the drive after ejecting.

Thanks.

Revision history for this message
Joseph Salisbury (jsalisbury) wrote :

@flocculant, thanks for testing! I can submit and SRU request for both Xenial and Yakkety.

Can anyone confirm that this bug does in fact affect Precise and/or Trusty?

Revision history for this message
Norbert (nrbrtx) wrote :

@jsalisbury
I can't find my USB3 flash (as in comment #44) which reappears after removal.
But you can search this thread - Precise is mentioned 19 times; Trusty - 29 times.

So bug still exists in Precise and Trusty.

Revision history for this message
In , Laura (laura-redhat-bugs) wrote :

*********** MASS BUG UPDATE **************
We apologize for the inconvenience. There is a large number of bugs to go through and several of them have gone stale. Due to this, we are doing a mass bug update across all of the Fedora 25 kernel bugs.

Fedora 25 has now been rebased to 4.9.3-200.fc25. Please test this kernel update (or newer) and let us know if you issue has been resolved or if it is still present with the newer kernel.

If you have moved on to Fedora 26, and are still experiencing this issue, please change the version to Fedora 26.

If you experience different issues, please open a new bug report for those.

Revision history for this message
In , Swamp-a (swamp-a) wrote :

SUSE-SU-2017:0181-1: An update that solves 13 vulnerabilities and has 127 fixes is now available.

Category: security (important)
Bug References: 1000118,1000189,1000287,1000304,1000433,1000776,1001169,1001171,1001310,1001462,1001486,1001888,1002322,1002770,1002786,1003068,1003566,1003581,1003606,1003813,1003866,1003964,1004048,1004052,1004252,1004365,1004517,1005169,1005327,1005545,1005666,1005745,1005895,1005917,1005921,1005923,1005925,1005929,1006103,1006175,1006267,1006528,1006576,1006804,1006809,1006827,1006915,1006918,1007197,1007615,1007653,1007955,1008557,1008979,1009062,1009969,1010040,1010158,1010444,1010478,1010507,1010665,1010690,1010970,1011176,1011250,1011913,1012060,1012094,1012452,1012767,1012829,1012992,1013001,1013479,1013531,1013700,1014120,1014392,1014701,1014710,1015212,1015359,1015367,1015416,799133,914939,922634,963609,963655,963904,964462,966170,966172,966186,966191,966316,966318,966325,966471,969474,969475,969476,969477,969756,971975,971989,972993,974313,974842,974843,978907,979378,979681,981825,983087,983152,983318,985850,986255,986987,987641,987703,987805,988524,988715,990384,992555,993739,993841,993891,994881,995278,997059,997639,997807,998054,998689,999907,999932
CVE References: CVE-2015-1350,CVE-2015-8964,CVE-2016-7039,CVE-2016-7042,CVE-2016-7425,CVE-2016-7913,CVE-2016-7917,CVE-2016-8645,CVE-2016-8666,CVE-2016-9083,CVE-2016-9084,CVE-2016-9793,CVE-2016-9919
Sources used:
SUSE Linux Enterprise Workstation Extension 12-SP2 (src): kernel-default-4.4.38-93.1
SUSE Linux Enterprise Software Development Kit 12-SP2 (src): kernel-docs-4.4.38-93.3, kernel-obs-build-4.4.38-93.1
SUSE Linux Enterprise Server for Raspberry Pi 12-SP2 (src): kernel-default-4.4.38-93.1, kernel-source-4.4.38-93.1, kernel-syms-4.4.38-93.1
SUSE Linux Enterprise Server 12-SP2 (src): kernel-default-4.4.38-93.1, kernel-source-4.4.38-93.1, kernel-syms-4.4.38-93.1
SUSE Linux Enterprise Live Patching 12 (src): kgraft-patch-SLE12-SP2_Update_4-1-2.1
SUSE Linux Enterprise High Availability 12-SP2 (src): kernel-default-4.4.38-93.1
SUSE Linux Enterprise Desktop 12-SP2 (src): kernel-default-4.4.38-93.1, kernel-source-4.4.38-93.1, kernel-syms-4.4.38-93.1

Revision history for this message
In , Wolfgang (wolfgang-redhat-bugs) wrote :

Just tested it again with my
LaCie 9223 1TB with USB ID 059f:1070 on USB3 xhci ports of an ASUS Z-170 board and a HP EliteBook 820 G1.

It works now as expected on:
F24: 4.8.16-200.fc24.x86_64
F25: 4.9.3-200.fc25.x86_64

Drive shuts down and disconnects from USB port after selecting "safely remove drive" on MATE desktop and it does not spin up again.

I also tested an older LaCie USB 2.0 drive and it still works as well.

Changed in thunar:
importance: Unknown → Medium
status: Unknown → Invalid
Revision history for this message
Myk Dowling (politas) wrote :

Six and a half years. This still hasn't been resolved. You have a patch that works. Please, please, apply it! This has been giving me grief for far too long!

Revision history for this message
In , Laura (laura-redhat-bugs) wrote :

Thank you for letting us know. I'm going to close this bug. If the problem shows up again, please reopen.

tags: added: kernel-bug-break-fix
Changed in linux (Ubuntu Yakkety):
status: In Progress → Fix Committed
description: updated
Changed in linux (Ubuntu Xenial):
status: In Progress → Fix Committed
Changed in linux (Ubuntu Precise):
importance: Undecided → Medium
status: New → In Progress
Changed in linux (Ubuntu Trusty):
importance: Undecided → Medium
status: New → In Progress
assignee: nobody → Joseph Salisbury (jsalisbury)
Changed in linux (Ubuntu Precise):
assignee: nobody → Joseph Salisbury (jsalisbury)
Revision history for this message
SURAJIT BHAKTA (surajit697) wrote :

Is this fix available in the latest upates? (of xenial) or is it not ready yet?

Revision history for this message
Guilherme Tavares da Silva (guitsilva) wrote :

At least for me, the problem was solved after this week's update (Xenial, 4.4.0-62-generic).

Revision history for this message
Donk (donk) wrote :

With the linux-hwe kernel (4.8.0-37.39~16.04.1, xenial) from the "kernel PPA", my two USB3 drive are successfully ejected and they stay poweroff.

Revision history for this message
Martin Wildam (mwildam) wrote : Re: [Bug 792085] Re: Automatic remount of safely removed USB 3.0 drive

I can also confirm fix after upgrading from something older to
4.4.0-63-generic. Thanks to everybody who was involved bringing the
solution!

Best wishes, Martin.

Revision history for this message
Simon P. (simpre) wrote :

Today kernel update to 4.8.0-39-generic fixed this issue for me on 16.04.2 Finally, thanks!

Revision history for this message
Gobinath (slgobinath) wrote :

Kernel update to 4.4.0-64-generic fixed the problem here.
Thanks!

Changed in linux (Ubuntu Xenial):
status: Fix Committed → Fix Released
Changed in linux (Ubuntu Yakkety):
status: Fix Committed → Fix Released
no longer affects: linux (Ubuntu Precise)
Revision history for this message
Myk Dowling (politas) wrote :

Confirm fixed in Xenial

Revision history for this message
In , Swamp-a (swamp-a) wrote :

SUSE-SU-2017:1102-1: An update that solves 27 vulnerabilities and has 114 fixes is now available.

Category: security (important)
Bug References: 1003077,1003344,1003568,1003677,1003813,1003866,1003925,1004517,1004520,1005857,1005877,1005896,1005903,1006917,1006919,1007615,1007944,1008557,1008645,1008831,1008833,1008893,1009875,1010150,1010175,1010201,1010467,1010501,1010507,1010711,1010716,1011685,1011820,1012411,1012422,1012832,1012851,1012917,1013018,1013038,1013042,1013070,1013531,1013533,1013542,1013604,1014410,1014454,1014746,1015561,1015752,1015760,1015796,1015803,1015817,1015828,1015844,1015848,1015878,1015932,1016320,1016505,1016520,1016668,1016688,1016824,1016831,1017686,1017710,1019148,1019165,1019348,1019783,1020214,1021258,748806,763198,771065,786036,790588,795297,799133,800999,803320,821612,824171,851603,853052,860441,863873,865783,871728,901809,907611,908458,908684,909077,909350,909484,909491,909618,913387,914939,919382,922634,924708,925065,928138,929141,953233,956514,960689,961589,962846,963655,967716,968010,969340,973203,973691,979681,984194,986337,987333,987576,989152,989680,989764,989896,990245,992566,992991,993739,993832,995968,996541,996557,997401,998689,999101,999907
CVE References: CVE-2004-0230,CVE-2012-6704,CVE-2013-6368,CVE-2015-1350,CVE-2015-8956,CVE-2015-8962,CVE-2015-8964,CVE-2016-10088,CVE-2016-3841,CVE-2016-5696,CVE-2016-7042,CVE-2016-7097,CVE-2016-7117,CVE-2016-7910,CVE-2016-7911,CVE-2016-7916,CVE-2016-8399,CVE-2016-8632,CVE-2016-8633,CVE-2016-8646,CVE-2016-9555,CVE-2016-9576,CVE-2016-9685,CVE-2016-9756,CVE-2016-9793,CVE-2016-9794,CVE-2017-5551
Sources used:
SUSE Linux Enterprise Real Time Extension 11-SP4 (src): kernel-rt-3.0.101.rt130-68.1, kernel-rt_trace-3.0.101.rt130-68.1, kernel-source-rt-3.0.101.rt130-68.1, kernel-syms-rt-3.0.101.rt130-68.1
SUSE Linux Enterprise Debuginfo 11-SP4 (src): kernel-rt-3.0.101.rt130-68.1, kernel-rt_debug-3.0.101.rt130-68.1, kernel-rt_trace-3.0.101.rt130-68.1

Revision history for this message
In , Eric (eric-redhat-bugs) wrote :

Same issue on fedora 25 on XPS 15 9560. Running kernel 4.8.6-300.fc25.x86_64

Disk: seagate 1TEAPF-500 (4TB drive)

Other usb drives spin down as expected.

Revision history for this message
In , Eric (eric-redhat-bugs) wrote :

(In reply to Eric M from comment #15)
> Same issue on fedora 25 on XPS 15 9560. Running kernel 4.8.6-300.fc25.x86_64
>
> Disk: seagate 1TEAPF-500 (4TB drive)
>
> Other usb drives spin down as expected.

kernel 4.10.x resolves the issue for me.

Changed in fedora:
importance: Unknown → Undecided
status: Unknown → Fix Released
Mathew Hodson (mhodson)
Changed in linux (Ubuntu):
status: In Progress → Fix Released
affects: opensuse → linux (openSUSE)
Mathew Hodson (mhodson)
affects: fedora → linux (Fedora)
no longer affects: udev (Ubuntu Trusty)
no longer affects: udev (Ubuntu Precise)
no longer affects: udev (Ubuntu)
no longer affects: thunar (Ubuntu Trusty)
no longer affects: thunar (Ubuntu Precise)
no longer affects: thunar (Ubuntu)
no longer affects: nautilus (Ubuntu Trusty)
no longer affects: nautilus (Ubuntu Precise)
no longer affects: nautilus (Ubuntu)
Mathew Hodson (mhodson)
affects: thunar → ubuntu-translations
Changed in ubuntu-translations:
importance: Medium → Undecided
status: Invalid → New
no longer affects: ubuntu-translations
affects: nautilus → ubuntu-translations
no longer affects: ubuntu-translations
Mathew Hodson (mhodson)
Changed in linux (Ubuntu Trusty):
status: In Progress → Triaged
Brad Figg (brad-figg)
tags: added: cscc
Norbert (nrbrtx)
tags: removed: natty precise trusty
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.