I can reliably reproduce the "cannot eject volume" part of this bug with one of
my two USB drives, and can not reproduce it with the other. Connecting both at
once in either order does not affect this.
Upon right-clicking on the icon for /media/brick (the affected disk) and
choosing Eject, the icon vanishes, a "Cannot eject volume" dialog appears, the
icon reappears and a Nautilus window for the disk is opened. grepping the
output of `lsof` for either "sdb" or "brick" yields nothing, and `pumount brick`
works as expected.
Output of dmesg upon plugging in the affected disk:
[140855.488000] usb 4-4.1: new high speed USB device using ehci_hcd and address
23
[140855.580000] usb 4-4.1: configuration #1 chosen from 1 choice
[140855.692000] scsi16 : SCSI emulation for USB Mass Storage devices
[140855.708000] usb-storage: device found at 23
[140855.708000] usb-storage: waiting for device to settle before scanning
[140860.708000] usb-storage: device scan complete
[140860.708000] scsi 16:0:0:0: Direct-Access HDT72252 5DLAT80 V44O
PQ: 0 ANSI: 2
[140860.712000] SCSI device sdb: 488397168 512-byte hdwr sectors (250059 MB)
[140860.712000] sdb: Write Protect is off
[140860.712000] sdb: Mode Sense: 53 00 00 08
[140860.712000] sdb: assuming drive cache: write through
[140860.716000] SCSI device sdb: 488397168 512-byte hdwr sectors (250059 MB)
[140860.716000] sdb: Write Protect is off
[140860.716000] sdb: Mode Sense: 53 00 00 08
[140860.716000] sdb: assuming drive cache: write through
[140860.716000] sdb: sdb1
[140860.732000] sd 16:0:0:0: Attached scsi disk sdb
[140860.732000] sd 16:0:0:0: Attached scsi generic sg2 type 0
[140861.632000] kjournald starting. Commit interval 5 seconds
[140861.632000] EXT3-fs warning: maximal mount count reached, running e2fsck is
recommended
[140861.632000] EXT3 FS on sdb1, internal journal
[140861.632000] EXT3-fs: mounted filesystem with ordered data mode.
Output of `sudo lsusb -vd 059f:0651`:
Bus 004 Device 023: ID 059f:0651 LaCie, Ltd
Device Descriptor:
bLength 18
bDescriptorType 1
bcdUSB 2.00
bDeviceClass 0 (Defined at Interface level)
bDeviceSubClass 0
bDeviceProtocol 0
bMaxPacketSize0 64
idVendor 0x059f LaCie, Ltd
idProduct 0x0651
bcdDevice 0.00
iManufacturer 1 LaCie
iProduct 2 LaCie Hard Drive USB
iSerial 3 10000E000C690A5A
bNumConfigurations 1
Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength 32
bNumInterfaces 1
bConfigurationValue 1
iConfiguration 0
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 (Zip)
iInterface 0
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
dmesg output for the unaffected disk:
[141312.856000] usb 4-4.2: new high speed USB device using ehci_hcd and address
24
[141312.996000] usb 4-4.2: configuration #2 chosen from 1 choice
[141312.996000] scsi17 : SCSI emulation for USB Mass Storage devices
[141313.000000] usb-storage: device found at 24
[141313.000000] usb-storage: waiting for device to settle before scanning
[141318.000000] usb-storage: device scan complete
[141318.484000] scsi 17:0:0:0: Direct-Access TOSHIBA MK4004GAH JC00
PQ: 0 ANSI: 0 CCS
[141318.484000] SCSI device sdb: 78126048 512-byte hdwr sectors (40001 MB)
[141318.488000] sdb: Write Protect is off
[141318.488000] sdb: Mode Sense: 00 4a 00 00
[141318.488000] sdb: assuming drive cache: write through
[141318.488000] SCSI device sdb: 78126048 512-byte hdwr sectors (40001 MB)
[141318.488000] sdb: Write Protect is off
[141318.488000] sdb: Mode Sense: 00 4a 00 00
[141318.488000] sdb: assuming drive cache: write through
[141318.488000] sdb: sdb1
[141318.836000] sd 17:0:0:0: Attached scsi disk sdb
[141318.836000] sd 17:0:0:0: Attached scsi generic sg2 type 0
...and corresponding lsusb output:
Bus 004 Device 024: ID 1006:3003 iRiver, Ltd.
Device Descriptor:
bLength 18
bDescriptorType 1
bcdUSB 2.00
bDeviceClass 0 (Defined at Interface level)
bDeviceSubClass 0
bDeviceProtocol 0
bMaxPacketSize0 64
idVendor 0x1006 iRiver, Ltd.
idProduct 0x3003
bcdDevice 1.00
iManufacturer 73 iRiver
iProduct 80 iRiver H300 Series
iSerial 99 0123456789AB
bNumConfigurations 1
Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength 39
bNumInterfaces 1
bConfigurationValue 2
iConfiguration 0
bmAttributes 0xc0
Self Powered
MaxPower 98mA
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 0
bNumEndpoints 3
bInterfaceClass 8 Mass Storage
bInterfaceSubClass 6 SCSI
bInterfaceProtocol 80 Bulk (Zip)
iInterface 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x82 EP 2 IN
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0200 1x 512 bytes
bInterval 1
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x01 EP 1 OUT
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0200 1x 512 bytes
bInterval 1
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x83 EP 3 IN
bmAttributes 3
Transfer Type Interrupt
Synch Type None
Usage Type Data
wMaxPacketSize 0x0002 1x 2 bytes
bInterval 9
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
--
Optical drive tray ejects when ejecting USB removable hard disc drive
https://bugs.launchpad.net/bugs/109224
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
