Bug 338912 - External USB HDD disk does not spin down on "Safely remove" action, is only unmounted
Summary: External USB HDD disk does not spin down on "Safely remove" action, is only ...
Status: RESOLVED DUPLICATE of bug 270808
Alias: None
Product: solid
Classification: Frameworks and Libraries
Component: libsolid-udisks2 (show other bugs)
Version: 4.13.2
Platform: Ubuntu Linux
: NOR normal
Target Milestone: ---
Assignee: Dolphin Bug Assignee
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-09-08 18:08 UTC by Vincas Dargis
Modified: 2014-11-18 22:20 UTC (History)
3 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Vincas Dargis 2014-09-08 18:08:02 UTC
Exteran USB HDD is not pwoered down on "Safely remove" action

When clicking "Safely remove" icon near mounted drive, that disk is unmounted, but is not powered down. I can feel it virating (spinning), and unpluging it makes... bad sounds.

Reproducible: Always

Steps to Reproduce:
1. Attach external drive
2. Mount it as suggested, open Dolphin.
3. Open mounted drive's context menu, click  "Safely remove..."

Actual Results:  
Drive is unmounted, but not powerd down (drie is still spinning).

Expected Results:  
Drive sould be powered down.

I'm using Kubuntu 14.04.1 amd64. 

There is no such problem in Xubuntu 14.04 and Ubuntu 14.04. I've tried all tree variants in clean LiveCDs. Kubuntu (Dolphin/KDE/?) is one of them that does not spin down my exteran drive.

At first this problem was the same in Ubuntu I've used earier, bug mentioned here:
https://bugs.launchpad.net/gentoo/+source/nautilus/+bug/1067876 . But looks like only Kubuntu/KDE has this problem left, at least with my drive:

Bus 002 Device 008: ID 152d:2329 JMicron Technology Corp. / JMicron USA Technology Corp. JM20329 SATA Bridge
Device Descriptor:
  bLength                18
  bDescriptorType         1
  bcdUSB               2.00
  bDeviceClass            0 (Defined at Interface level)
  bDeviceSubClass         0 
  bDeviceProtocol         0 
  bMaxPacketSize0        64
  idVendor           0x152d JMicron Technology Corp. / JMicron USA Technology Corp.
  idProduct          0x2329 JM20329 SATA Bridge
  bcdDevice            1.00
  iManufacturer           1 JMicron
  iProduct                2 USB to ATA/ATAPI bridge
  iSerial                 5 100317B20030
  bNumConfigurations      1
  Configuration Descriptor:
    bLength                 9
    bDescriptorType         2
    wTotalLength           32
    bNumInterfaces          1
    bConfigurationValue     1
    iConfiguration          4 USB Mass Storage
    bmAttributes         0xc0
      Self Powered
    MaxPower                2mA
    Interface Descriptor:
      bLength                 9
      bDescriptorType         4
      bInterfaceNumber        0
      bAlternateSetting       0
      bNumEndpoints           2
      bInterfaceClass         8 Mass Storage
      bInterfaceSubClass      6 SCSI
      bInterfaceProtocol     80 Bulk-Only
      iInterface              6 MSC Bulk-Only Transfer
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x81  EP 1 IN
        bmAttributes            2
          Transfer Type            Bulk
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0200  1x 512 bytes
        bInterval               0
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x02  EP 2 OUT
        bmAttributes            2
          Transfer Type            Bulk
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0200  1x 512 bytes
        bInterval               0
Device Qualifier (for other device speed):
  bLength                10
  bDescriptorType         6
  bcdUSB               2.00
  bDeviceClass            0 (Defined at Interface level)
  bDeviceSubClass         0 
  bDeviceProtocol         0 
  bMaxPacketSize0        64
  bNumConfigurations      1
Device Status:     0x0001
  Self Powered
Comment 1 Vincas Dargis 2014-09-08 18:10:00 UTC
It does spin down if I use "sudo udisks --detach /dev/sdX" after unmounting.
Comment 2 Emmanuel Pescosta 2014-09-09 07:31:53 UTC
Thanks for the very detailed bug report!

Dolphin uses Solid for mounting/unmounting storage devices, so I'll reassign it to Solid.
Comment 3 Christoph Feck 2014-09-09 10:41:24 UTC

*** This bug has been marked as a duplicate of bug 270808 ***
Comment 4 jonoei97 2014-09-18 05:46:15 UTC
I do quite a bit of work with an external hard drive, so I am quite disappointed that the duplicated bug has marked this as a won't fix. This means that I will have to always unmount and use udisks to detach the external hard drive.

Actually, this bug has made me hesitant to recommend KDE to other users, since I do not want to be responsible for anything that may cause a malfunction in other users' external drives. Even if it does not cause a malfunction, I do not want to cause other users to worry, especially if they come from a Windows environment.

To any KDE developer reading this, I humbly ask him or her to implement this feature, even if it is just disabled by default. I would truly appreciate it. Thank you.
Comment 5 Frank Reininghaus 2014-11-18 22:20:04 UTC
(In reply to jonoei97 from comment #4)
> To any KDE developer reading this, I humbly ask him or her to implement this
> feature, even if it is just disabled by default. I would truly appreciate
> it. Thank you.

If you read all comments in bug 270808, you will see that a fix has already been developed by the people working on Solid (this is the library which is responsible for interacting with devices). They just decided not to apply the fix because they felt that it needs more testing to reduce the risk of regressions, and nobody volunteered to test it.

It seems that you would appreciate to see this fix in the next version of Solid, so it would be great if you could get in touch with the developers (just add a comment in bug 270808 or e-mail them) and ask them what you can do to help with testing. I'm pretty sure that many KDE users will be grateful! Thanks for your help.