USB-Hard drive A-DATA SH93 does not work.

Bug #554283 reported by veZuk
34
This bug affects 6 people
Affects Status Importance Assigned to Milestone
udev (Ubuntu)
Fix Released
Undecided
Unassigned

Bug Description

Good time of day.

I recently bought a USB hard drive ADATA SH93 640Gb (http://adata.com.tw/en/product_show.php?ProductNo=14210001), but no Karmic, nor Lucid did not want to work with him. One note - if you boot from the LiveCD Karmic (9.10) then it is visible and you can use it.

In addition, for example, ArchLinux, Ubuntu 8.04.1 on the same computer works fine with the disk.

I think that's something wrong with the kernel.

When I connect the hard drive is in /var/log/syslog appear such messages:

Apr 3 01:59:11 vezuk-etop kernel: [ 239.990039] usb 2-4: new high speed USB device using ehci_hcd and address 4
Apr 3 01:59:12 vezuk-etop kernel: [ 240.141636] usb 2-4: configuration #1 chosen from 1 choice
Apr 3 01:59:12 vezuk-etop kernel: [ 240.141842] scsi3 : SCSI emulation for USB Mass Storage devices
Apr 3 01:59:12 vezuk-etop kernel: [ 240.142020] usb-storage: device found at 4
Apr 3 01:59:12 vezuk-etop kernel: [ 240.142023] usb-storage: waiting for device to settle before scanning
Apr 3 01:59:17 vezuk-etop kernel: [ 245.140163] usb-storage: device scan complete
Apr 3 01:59:17 vezuk-etop kernel: [ 245.140801] scsi 3:0:0:0: Direct-Access A-DATA SH93 PQ: 0 ANSI: 0
Apr 3 01:59:17 vezuk-etop kernel: [ 245.146075] sd 3:0:0:0: Attached scsi generic sg3 type 0
Apr 3 01:59:17 vezuk-etop kernel: [ 245.148794] sd 3:0:0:0: [sdc] 1250263728 512-byte logical blocks: (640 GB/596 GiB)
Apr 3 01:59:17 vezuk-etop kernel: [ 245.149292] sd 3:0:0:0: [sdc] Write Protect is off
Apr 3 01:59:17 vezuk-etop kernel: [ 245.149296] sd 3:0:0:0: [sdc] Mode Sense: 03 00 00 00
Apr 3 01:59:17 vezuk-etop kernel: [ 245.149300] sd 3:0:0:0: [sdc] Assuming drive cache: write through
Apr 3 01:59:17 vezuk-etop kernel: [ 245.151198] sd 3:0:0:0: [sdc] Assuming drive cache: write through
Apr 3 01:59:17 vezuk-etop kernel: [ 245.151208] sdc: sdc1
Apr 3 01:59:17 vezuk-etop kernel: [ 245.177867] sd 3:0:0:0: [sdc] Assuming drive cache: write through
Apr 3 01:59:17 vezuk-etop kernel: [ 245.177875] sd 3:0:0:0: [sdc] Attached SCSI disk
Apr 3 01:59:30 vezuk-etop kernel: [ 258.972562] sd 3:0:0:0: [sdc] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
Apr 3 01:59:30 vezuk-etop kernel: [ 258.972570] sd 3:0:0:0: [sdc] Sense Key : Illegal Request [current]
Apr 3 01:59:30 vezuk-etop kernel: [ 258.972577] sd 3:0:0:0: [sdc] Add. Sense: Invalid command operation code
Apr 3 01:59:30 vezuk-etop kernel: [ 258.972585] sd 3:0:0:0: [sdc] CDB: Read(6): 08 00 08 00 08 00
Apr 3 01:59:30 vezuk-etop kernel: [ 258.972596] end_request: I/O error, dev sdc, sector 2048
Apr 3 01:59:30 vezuk-etop kernel: [ 258.972603] Buffer I/O error on device sdc1, logical block 0
Apr 3 01:59:30 vezuk-etop kernel: [ 258.973533] sd 3:0:0:0: [sdc] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
Apr 3 01:59:30 vezuk-etop kernel: [ 258.973541] sd 3:0:0:0: [sdc] Sense Key : Illegal Request [current]
Apr 3 01:59:30 vezuk-etop kernel: [ 258.973548] sd 3:0:0:0: [sdc] Add. Sense: Invalid command operation code
Apr 3 01:59:30 vezuk-etop kernel: [ 258.973554] sd 3:0:0:0: [sdc] CDB: Read(6): 08 00 08 00 08 00
Apr 3 01:59:30 vezuk-etop kernel: [ 258.973565] end_request: I/O error, dev sdc, sector 2048
Apr 3 01:59:30 vezuk-etop kernel: [ 258.973572] Buffer I/O error on device sdc1, logical block 0
Apr 3 01:59:30 vezuk-etop kernel: [ 258.974561] sd 3:0:0:0: [sdc] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
Apr 3 01:59:30 vezuk-etop kernel: [ 258.974567] sd 3:0:0:0: [sdc] Sense Key : Illegal Request [current]
Apr 3 01:59:30 vezuk-etop kernel: [ 258.974574] sd 3:0:0:0: [sdc] Add. Sense: Invalid command operation code
Apr 3 01:59:30 vezuk-etop kernel: [ 258.974580] sd 3:0:0:0: [sdc] CDB: Read(6): 08 00 08 00 08 00
Apr 3 01:59:30 vezuk-etop kernel: [ 258.974590] end_request: I/O error, dev sdc, sector 2048
Apr 3 01:59:30 vezuk-etop kernel: [ 258.974595] Buffer I/O error on device sdc1, logical block 0
Apr 3 01:59:30 vezuk-etop kernel: [ 258.975535] sd 3:0:0:0: [sdc] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
Apr 3 01:59:30 vezuk-etop kernel: [ 258.975543] sd 3:0:0:0: [sdc] Sense Key : Illegal Request [current]
Apr 3 01:59:30 vezuk-etop kernel: [ 258.975549] sd 3:0:0:0: [sdc] Add. Sense: Invalid command operation code
Apr 3 01:59:30 vezuk-etop kernel: [ 258.975556] sd 3:0:0:0: [sdc] CDB: Read(6): 08 00 08 00 08 00
Apr 3 01:59:30 vezuk-etop kernel: [ 258.975567] end_request: I/O error, dev sdc, sector 2048
Apr 3 01:59:30 vezuk-etop kernel: [ 258.975573] Buffer I/O error on device sdc1, logical block 0
Apr 3 01:59:30 vezuk-etop kernel: [ 258.976556] sd 3:0:0:0: [sdc] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
Apr 3 01:59:30 vezuk-etop kernel: [ 258.976562] sd 3:0:0:0: [sdc] Sense Key : Illegal Request [current]
Apr 3 01:59:30 vezuk-etop kernel: [ 258.976568] sd 3:0:0:0: [sdc] Add. Sense: Invalid command operation code
Apr 3 01:59:30 vezuk-etop kernel: [ 258.976574] sd 3:0:0:0: [sdc] CDB: Read(6): 08 00 08 00 08 00
Apr 3 01:59:30 vezuk-etop kernel: [ 258.976584] end_request: I/O error, dev sdc, sector 2048
Apr 3 01:59:30 vezuk-etop kernel: [ 258.976589] Buffer I/O error on device sdc1, logical block 0
Apr 3 01:59:30 vezuk-etop kernel: [ 258.977526] sd 3:0:0:0: [sdc] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
Apr 3 01:59:30 vezuk-etop kernel: [ 258.977533] sd 3:0:0:0: [sdc] Sense Key : Illegal Request [current]
Apr 3 01:59:30 vezuk-etop kernel: [ 258.977540] sd 3:0:0:0: [sdc] Add. Sense: Invalid command operation code
Apr 3 01:59:30 vezuk-etop kernel: [ 258.977547] sd 3:0:0:0: [sdc] CDB: Read(6): 08 00 08 00 08 00
Apr 3 01:59:30 vezuk-etop kernel: [ 258.977558] end_request: I/O error, dev sdc, sector 2048
Apr 3 01:59:30 vezuk-etop kernel: [ 258.977564] Buffer I/O error on device sdc1, logical block 0
Apr 3 01:59:30 vezuk-etop kernel: [ 258.978552] sd 3:0:0:0: [sdc] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
Apr 3 01:59:30 vezuk-etop kernel: [ 258.978558] sd 3:0:0:0: [sdc] Sense Key : Illegal Request [current]
Apr 3 01:59:30 vezuk-etop kernel: [ 258.978564] sd 3:0:0:0: [sdc] Add. Sense: Invalid command operation code
Apr 3 01:59:30 vezuk-etop kernel: [ 258.978570] sd 3:0:0:0: [sdc] CDB: Read(6): 08 00 08 00 08 00
Apr 3 01:59:30 vezuk-etop kernel: [ 258.978581] end_request: I/O error, dev sdc, sector 2048
Apr 3 01:59:30 vezuk-etop kernel: [ 258.978585] Buffer I/O error on device sdc1, logical block 0
Apr 3 01:59:30 vezuk-etop kernel: [ 258.979551] sd 3:0:0:0: [sdc] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
Apr 3 01:59:30 vezuk-etop kernel: [ 258.979557] sd 3:0:0:0: [sdc] Sense Key : Illegal Request [current]
Apr 3 01:59:30 vezuk-etop kernel: [ 258.979563] sd 3:0:0:0: [sdc] Add. Sense: Invalid command operation code
Apr 3 01:59:30 vezuk-etop kernel: [ 258.979568] sd 3:0:0:0: [sdc] CDB: Read(6): 08 00 08 00 08 00
Apr 3 01:59:30 vezuk-etop kernel: [ 258.979578] end_request: I/O error, dev sdc, sector 2048
Apr 3 01:59:30 vezuk-etop kernel: [ 258.979582] Buffer I/O error on device sdc1, logical block 0
Apr 3 01:59:30 vezuk-etop kernel: [ 258.980523] sd 3:0:0:0: [sdc] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
Apr 3 01:59:30 vezuk-etop kernel: [ 258.980529] sd 3:0:0:0: [sdc] Sense Key : Illegal Request [current]
Apr 3 01:59:30 vezuk-etop kernel: [ 258.980535] sd 3:0:0:0: [sdc] Add. Sense: Invalid command operation code
Apr 3 01:59:30 vezuk-etop kernel: [ 258.980541] sd 3:0:0:0: [sdc] CDB: Read(6): 08 00 08 00 08 00
Apr 3 01:59:30 vezuk-etop kernel: [ 258.980552] end_request: I/O error, dev sdc, sector 2048
Apr 3 01:59:30 vezuk-etop kernel: [ 258.980557] Buffer I/O error on device sdc1, logical block 0
Apr 3 01:59:30 vezuk-etop kernel: [ 258.981524] sd 3:0:0:0: [sdc] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
Apr 3 01:59:30 vezuk-etop kernel: [ 258.981534] sd 3:0:0:0: [sdc] Sense Key : Illegal Request [current]
Apr 3 01:59:30 vezuk-etop kernel: [ 258.981543] sd 3:0:0:0: [sdc] Add. Sense: Invalid command operation code
Apr 3 01:59:30 vezuk-etop kernel: [ 258.981553] sd 3:0:0:0: [sdc] CDB: Read(6): 08 00 08 00 08 00
Apr 3 01:59:30 vezuk-etop kernel: [ 258.981570] end_request: I/O error, dev sdc, sector 2048
Apr 3 01:59:30 vezuk-etop kernel: [ 258.981578] Buffer I/O error on device sdc1, logical block 0
Apr 3 01:59:30 vezuk-etop kernel: [ 258.982534] sd 3:0:0:0: [sdc] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
Apr 3 01:59:30 vezuk-etop kernel: [ 258.982540] sd 3:0:0:0: [sdc] Sense Key : Illegal Request [current]
Apr 3 01:59:30 vezuk-etop kernel: [ 258.982547] sd 3:0:0:0: [sdc] Add. Sense: Invalid command operation code
Apr 3 01:59:30 vezuk-etop kernel: [ 258.982554] sd 3:0:0:0: [sdc] CDB: Read(6): 08 00 08 38 08 00
Apr 3 01:59:30 vezuk-etop kernel: [ 258.982564] end_request: I/O error, dev sdc, sector 2104
Apr 3 01:59:30 vezuk-etop kernel: [ 258.983521] sd 3:0:0:0: [sdc] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
Apr 3 01:59:30 vezuk-etop kernel: [ 258.983527] sd 3:0:0:0: [sdc] Sense Key : Illegal Request [current]
Apr 3 01:59:30 vezuk-etop kernel: [ 258.983533] sd 3:0:0:0: [sdc] Add. Sense: Invalid command operation code
Apr 3 01:59:30 vezuk-etop kernel: [ 258.983540] sd 3:0:0:0: [sdc] CDB: Read(6): 08 00 08 00 08 00
Apr 3 01:59:30 vezuk-etop kernel: [ 258.983550] end_request: I/O error, dev sdc, sector 2048
Apr 3 01:59:30 vezuk-etop kernel: [ 258.984394] sd 3:0:0:0: [sdc] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
Apr 3 01:59:30 vezuk-etop kernel: [ 258.984400] sd 3:0:0:0: [sdc] Sense Key : Illegal Request [current]
Apr 3 01:59:30 vezuk-etop kernel: [ 258.984406] sd 3:0:0:0: [sdc] Add. Sense: Invalid command operation code
Apr 3 01:59:30 vezuk-etop kernel: [ 258.984412] sd 3:0:0:0: [sdc] CDB: Read(6): 08 00 08 00 08 00
Apr 3 01:59:30 vezuk-etop kernel: [ 258.984422] end_request: I/O error, dev sdc, sector 2048
Apr 3 01:59:42 vezuk-etop kernel: [ 270.146340] sd 3:0:0:0: [sdc] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
Apr 3 01:59:42 vezuk-etop kernel: [ 270.146349] sd 3:0:0:0: [sdc] Sense Key : Illegal Request [current]
Apr 3 01:59:42 vezuk-etop kernel: [ 270.146355] sd 3:0:0:0: [sdc] Add. Sense: Invalid command operation code
Apr 3 01:59:42 vezuk-etop kernel: [ 270.146363] sd 3:0:0:0: [sdc] CDB: Read(10): 28 00 4a 85 77 80 00 00 08 00
Apr 3 01:59:42 vezuk-etop kernel: [ 270.146377] end_request: I/O error, dev sdc, sector 1250260864
Apr 3 01:59:42 vezuk-etop kernel: [ 270.146383] __ratelimit: 3 callbacks suppressed
Apr 3 01:59:42 vezuk-etop kernel: [ 270.146388] Buffer I/O error on device sdc1, logical block 156282352
Apr 3 01:59:42 vezuk-etop kernel: [ 270.147328] sd 3:0:0:0: [sdc] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
Apr 3 01:59:42 vezuk-etop kernel: [ 270.147334] sd 3:0:0:0: [sdc] Sense Key : Illegal Request [current]
Apr 3 01:59:42 vezuk-etop kernel: [ 270.147339] sd 3:0:0:0: [sdc] Add. Sense: Invalid command operation code
Apr 3 01:59:42 vezuk-etop kernel: [ 270.147345] sd 3:0:0:0: [sdc] CDB: Read(6): 08 00 00 00 20 00
Apr 3 01:59:42 vezuk-etop kernel: [ 270.147355] end_request: I/O error, dev sdc, sector 0
Apr 3 01:59:42 vezuk-etop kernel: [ 270.147360] Buffer I/O error on device sdc, logical block 0
Apr 3 01:59:42 vezuk-etop kernel: [ 270.147365] Buffer I/O error on device sdc, logical block 1
Apr 3 01:59:42 vezuk-etop kernel: [ 270.147369] Buffer I/O error on device sdc, logical block 2
Apr 3 01:59:42 vezuk-etop kernel: [ 270.147373] Buffer I/O error on device sdc, logical block 3
Apr 3 01:59:53 vezuk-etop kernel: [ 281.309474] sd 3:0:0:0: [sdc] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
Apr 3 01:59:53 vezuk-etop kernel: [ 281.309483] sd 3:0:0:0: [sdc] Sense Key : Illegal Request [current]
Apr 3 01:59:53 vezuk-etop kernel: [ 281.309490] sd 3:0:0:0: [sdc] Add. Sense: Invalid command operation code
Apr 3 01:59:53 vezuk-etop kernel: [ 281.309497] sd 3:0:0:0: [sdc] CDB: Read(10): 28 00 4a 85 77 f0 00 00 08 00
Apr 3 01:59:53 vezuk-etop kernel: [ 281.309512] end_request: I/O error, dev sdc, sector 1250260976
Apr 3 01:59:53 vezuk-etop kernel: [ 281.309520] Buffer I/O error on device sdc1, logical block 156282366
Apr 3 01:59:53 vezuk-etop kernel: [ 281.310453] sd 3:0:0:0: [sdc] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
Apr 3 01:59:53 vezuk-etop kernel: [ 281.310459] sd 3:0:0:0: [sdc] Sense Key : Illegal Request [current]
Apr 3 01:59:53 vezuk-etop kernel: [ 281.310465] sd 3:0:0:0: [sdc] Add. Sense: Invalid command operation code
Apr 3 01:59:53 vezuk-etop kernel: [ 281.310472] sd 3:0:0:0: [sdc] CDB: Read(6): 08 00 08 00 08 00
Apr 3 01:59:53 vezuk-etop kernel: [ 281.310482] end_request: I/O error, dev sdc, sector 2048
Apr 3 01:59:53 vezuk-etop kernel: [ 281.310488] Buffer I/O error on device sdc1, logical block 0
Apr 3 01:59:53 vezuk-etop kernel: [ 281.311459] sd 3:0:0:0: [sdc] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
Apr 3 01:59:53 vezuk-etop kernel: [ 281.311465] sd 3:0:0:0: [sdc] Sense Key : Illegal Request [current]
Apr 3 01:59:53 vezuk-etop kernel: [ 281.311470] sd 3:0:0:0: [sdc] Add. Sense: Invalid command operation code
Apr 3 01:59:53 vezuk-etop kernel: [ 281.311477] sd 3:0:0:0: [sdc] CDB: Read(6): 08 00 08 08 08 00
Apr 3 01:59:53 vezuk-etop kernel: [ 281.311486] end_request: I/O error, dev sdc, sector 2056
Apr 3 01:59:53 vezuk-etop kernel: [ 281.311491] Buffer I/O error on device sdc1, logical block 1
...

The disc is not broken, electronics works as expected.

$ uname -a
Linux vezuk-etop 2.6.32-19-generic #28-Ubuntu SMP Thu Apr 1 10:39:41 UTC 2010 x86_64 GNU/Linux

I'm not the only one who has a problem (In Russian: http://old.nabble.com/USB-HDD-td27944884.html).

veZuk (vezukru)
description: updated
Revision history for this message
kuncy7 (kuncy7) wrote :

Hi!
I have a USB hard drive ADATA SH93 500Gb and identical problem. :(

Revision history for this message
Alex Maverick (maverickalex) wrote :
Download full text (4.1 KiB)

Hey guys!

Same here.

On the same hardware machine, with Arch and Ubuntu Rescue Remix 9.10 and Windows that usb hdd (ADATA SH93 500Gb ) operates perfetly!

Here is what appears in /var/log/syslog when I connect it to Ubuntu 10.04:

----------------------------------------------------------------------------------------------------------------
Mar 18 15:24:01 merlin kernel: [ 2466.656104] usb 1-5: new high speed
USB device using ehci_hcd and address 2
Mar 18 15:24:01 merlin kernel: [ 2466.789033] usb 1-5: configuration
#1 chosen from 1 choice
Mar 18 15:24:02 merlin kernel: [ 2467.558594] Initializing USB Mass
Storage driver...
Mar 18 15:24:02 merlin kernel: [ 2467.558719] scsi4 : SCSI emulation
for USB Mass Storage devices
Mar 18 15:24:02 merlin kernel: [ 2467.558801] usbcore: registered new
interface driver usb-storage
Mar 18 15:24:02 merlin kernel: [ 2467.558804] USB Mass Storage support
registered.
Mar 18 15:24:02 merlin kernel: [ 2467.558934] usb-storage: device found at 2
Mar 18 15:24:02 merlin kernel: [ 2467.558935] usb-storage: waiting for
device to settle before scanning
Mar 18 15:24:07 merlin kernel: [ 2472.556315] usb-storage: device scan complete
Mar 18 15:24:07 merlin kernel: [ 2472.556828] scsi 4:0:0:0:
Direct-Access A-DATA SH93 PQ: 0 ANSI: 0
Mar 18 15:24:07 merlin kernel: [ 2472.557549] sd 4:0:0:0: Attached
scsi generic sg2 type 0
Mar 18 15:24:07 merlin kernel: [ 2472.558176] sd 4:0:0:0: [sdb]
976773168 512-byte logical blocks: (500 GB/465 GiB)
Mar 18 15:24:07 merlin kernel: [ 2472.558673] sd 4:0:0:0: [sdb] Write
Protect is off
Mar 18 15:24:07 merlin kernel: [ 2472.558675] sd 4:0:0:0: [sdb] Mode
Sense: 03 00 00 00
Mar 18 15:24:07 merlin kernel: [ 2472.558678] sd 4:0:0:0: [sdb]
Assuming drive cache: write through
Mar 18 15:24:07 merlin kernel: [ 2472.559796] sd 4:0:0:0: [sdb]
Assuming drive cache: write through
Mar 18 15:24:08 merlin kernel: [ 2472.559799] sdb: sdb1 sdb2 sdb3 < sdb5 sdb6 >
Mar 18 15:24:08 merlin kernel: [ 2473.023042] sd 4:0:0:0: [sdb]
Assuming drive cache: write through
Mar 18 15:24:08 merlin kernel: [ 2473.023047] sd 4:0:0:0: [sdb]
Attached SCSI disk
Mar 18 15:24:22 merlin kernel: [ 2487.252293] sd 4:0:0:0: [sdb]
Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
Mar 18 15:24:22 merlin kernel: [ 2487.252299] sd 4:0:0:0: [sdb] Sense
Key : Illegal Request [current]
Mar 18 15:24:22 merlin kernel: [ 2487.252304] sd 4:0:0:0: [sdb] Add.
Sense: Invalid command operation code
Mar 18 15:24:22 merlin kernel: [ 2487.252309] sd 4:0:0:0: [sdb] CDB:
Read(6): 08 00 00 3f 08 00
Mar 18 15:24:22 merlin kernel: [ 2487.252315] end_request: I/O error,
dev sdb, sector 63
Mar 18 15:24:22 merlin kernel: [ 2487.252320] Buffer I/O error on
device sdb1, logical block 0
Mar 18 15:24:22 merlin kernel: [ 2487.252324] Buffer I/O error on
device sdb1, logical block 1
Mar 18 15:24:22 merlin kernel: [ 2487.253289] sd 4:0:0:0: [sdb]
Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
Mar 18 15:24:22 merlin kernel: [ 2487.253292] sd 4:0:0:0: [sdb] Sense
Key : Illegal Request [current]
Mar 18 15:24:22 merlin kernel: [ 2487.253296] sd 4:0:0:0: [sdb] Add.
Sense: Invalid command operation code
Mar 18 15:24:22 merlin kernel: [ 2487.25...

Read more...

Revision history for this message
kass (kass) wrote :

USB hard drive ADATA SH93 320Gb. Same problem.

Revision history for this message
Alex Maverick (maverickalex) wrote :

Hey guys, any news? So pity it is not working still...

Changed in linux (Ubuntu):
status: New → Confirmed
assignee: nobody → Canonical Kernel Team (canonical-kernel-team)
Revision history for this message
Alex Maverick (maverickalex) wrote :

Same stuff.

Revision history for this message
veZuk (vezukru) wrote :

В 10.04 бета 2 проблема всё ещё присутствиует.

Revision history for this message
veZuk (vezukru) wrote :

Oops...

In the 10.04 beta 2 problem still exists.

Revision history for this message
veZuk (vezukru) wrote :

It seems to me that the problem is not in kernel, may be in some of the modules. Or affect any option in some config files. Because I tried 9.04 with new kernel - HDD works fine. But at 10.04 with the old kernels exact same problem.

Revision history for this message
honiiwawa (krakaka) wrote :

I had the same problem.
Solved it by not using usb extensions.

Revision history for this message
Maksim Ivanyukhin (ivmaks) wrote :
Download full text (5.1 KiB)

[53006.029469] Buffer I/O error on device sdl1, logical block 488383936
[53017.206215] sd 16:0:0:0: [sdl] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
[53017.206224] sd 16:0:0:0: [sdl] Sense Key : Illegal Request [current]
[53017.206231] sd 16:0:0:0: [sdl] Add. Sense: Invalid command operation code
[53017.206239] sd 16:0:0:0: [sdl] CDB: Read(10): 28 00 3a 38 4b c1 00 00 02 00
[53017.206251] end_request: I/O error, dev sdl, sector 976767937
[53017.206259] Buffer I/O error on device sdl1, logical block 488383937
[53017.208197] sd 16:0:0:0: [sdl] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
[53017.208201] sd 16:0:0:0: [sdl] Sense Key : Illegal Request [current]
[53017.208206] sd 16:0:0:0: [sdl] Add. Sense: Invalid command operation code
[53017.208211] sd 16:0:0:0: [sdl] CDB: Read(6): 08 00 00 00 20 00
[53017.208219] end_request: I/O error, dev sdl, sector 0
[53017.208222] Buffer I/O error on device sdl, logical block 0
[53017.208227] Buffer I/O error on device sdl, logical block 1
[53017.208231] Buffer I/O error on device sdl, logical block 2
[53017.208234] Buffer I/O error on device sdl, logical block 3
[53028.384007] sd 16:0:0:0: [sdl] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
[53028.384017] sd 16:0:0:0: [sdl] Sense Key : Illegal Request [current]
[53028.384024] sd 16:0:0:0: [sdl] Add. Sense: Invalid command operation code
[53028.384031] sd 16:0:0:0: [sdl] CDB: Read(10): 28 00 3a 38 4b c3 00 00 04 00
[53028.384043] end_request: I/O error, dev sdl, sector 976767939
[53028.384051] Buffer I/O error on device sdl1, logical block 488383938
[53028.384057] Buffer I/O error on device sdl1, logical block 488383939
[53039.560801] sd 16:0:0:0: [sdl] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
[53039.560809] sd 16:0:0:0: [sdl] Sense Key : Illegal Request [current]
[53039.560816] sd 16:0:0:0: [sdl] Add. Sense: Invalid command operation code
[53039.560823] sd 16:0:0:0: [sdl] CDB: Read(10): 28 00 3a 38 4c 2f 00 00 08 00
[53039.560835] end_request: I/O error, dev sdl, sector 976768047
[53039.560843] Buffer I/O error on device sdl1, logical block 488383992
[53039.560849] Buffer I/O error on device sdl1, logical block 488383993
[53039.560853] Buffer I/O error on device sdl1, logical block 488383994
[53039.560857] Buffer I/O error on device sdl1, logical block 488383995
[53039.562792] sd 16:0:0:0: [sdl] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
[53039.562796] sd 16:0:0:0: [sdl] Sense Key : Illegal Request [current]
[53039.562801] sd 16:0:0:0: [sdl] Add. Sense: Invalid command operation code
[53039.562806] sd 16:0:0:0: [sdl] CDB: Read(6): 08 00 00 3f 08 00
[53039.562814] end_request: I/O error, dev sdl, sector 63
[53039.562819] Buffer I/O error on device sdl1, logical block 0
[53039.562823] Buffer I/O error on device sdl1, logical block 1
[53039.562827] Buffer I/O error on device sdl1, logical block 2
[53039.562831] Buffer I/O error on device sdl1, logical block 3
[53039.563785] sd 16:0:0:0: [sdl] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
[53039.563789] sd 16:0:0:0: [sdl] Sense Key : Illegal Request [current]
[53039.563794] sd 16:0:0:0: [sdl] Add. Sense: Invalid command operation code
[53039.563798] sd 16:0:0:0: [sdl] CDB: Read(6...

Read more...

Revision history for this message
bazi (bazidzem) wrote :

I have got the same thing with my HardDrive:
[ 254.824074] Initializing USB Mass Storage driver...
[ 254.824277] scsi4 : SCSI emulation for USB Mass Storage devices
[ 254.824411] usbcore: registered new interface driver usb-storage
[ 254.824415] USB Mass Storage support registered.
[ 254.828002] usb-storage: device found at 4
[ 254.828006] usb-storage: waiting for device to settle before scanning
[ 259.828475] usb-storage: device scan complete
[ 259.829226] scsi 4:0:0:0: Direct-Access SAMSUNG HM250HI PQ: 0 ANSI: 0
[ 259.829926] sd 4:0:0:0: Attached scsi generic sg2 type 0
[ 259.830804] sd 4:0:0:0: [sdb] 488397168 512-byte logical blocks: (250 GB/232 GiB)
[ 259.834398] sd 4:0:0:0: [sdb] Write Protect is off
[ 259.834404] sd 4:0:0:0: [sdb] Mode Sense: 03 00 00 00
[ 259.834408] sd 4:0:0:0: [sdb] Assuming drive cache: write through
[ 259.836894] sd 4:0:0:0: [sdb] Assuming drive cache: write through
[ 259.836903] sdb: sdb1
[ 259.870170] sd 4:0:0:0: [sdb] Assuming drive cache: write through
[ 259.870177] sd 4:0:0:0: [sdb] Attached SCSI disk
[ 273.669389] sd 4:0:0:0: [sdb] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
[ 273.669399] sd 4:0:0:0: [sdb] Sense Key : Illegal Request [current]
[ 273.669406] sd 4:0:0:0: [sdb] Add. Sense: Invalid command operation code
[ 273.669414] sd 4:0:0:0: [sdb] CDB: Read(6): 08 00 00 00 20 00
[ 273.669427] end_request: I/O error, dev sdb, sector 0
[ 273.669433] __ratelimit: 9 callbacks suppressed
[ 273.669438] Buffer I/O error on device sdb, logical block 0
[ 273.669447] Buffer I/O error on device sdb, logical block 1
[ 273.669452] Buffer I/O error on device sdb, logical block 2
[ 273.669456] Buffer I/O error on device sdb, logical block 3
[ 273.671005] sd 4:0:0:0: [sdb] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
[ 273.671013] sd 4:0:0:0: [sdb] Sense Key : Illegal Request [current]
[ 273.671020] sd 4:0:0:0: [sdb] Add. Sense: Invalid command operation code
[ 273.671028] sd 4:0:0:0: [sdb] CDB: Read(6): 08 00 00 00 08 00
[ 273.671040] end_request: I/O error, dev sdb, sector 0
[ 273.671046] Buffer I/O error on device sdb, logical block 0

Revision history for this message
bazi (bazidzem) wrote :

Like veZuk I think that this is not a kernel issue, as you can see on my log, HardDrive was correctly recognized "SAMSUNG HM250HI" even got mount id "sdb" but something went wrong with "Sense Key":
[ 273.669399] sd 4:0:0:0: [sdb] Sense Key : Illegal Request [current]

I would also like to add that under XP works fine, shame that under Ubuntu doesn't because I prefer Ubunty than XP

Revision history for this message
kass (kass) wrote :

Yes! It's works!
After, probably udev, update disk work fine! (lucid)

Revision history for this message
kass (kass) wrote :

Apr 20 21:46:10 wizzle kernel: [300789.640082] usb 1-2: new high speed USB device using ehci_hcd and address 10
Apr 20 21:46:10 wizzle kernel: [300789.773443] usb 1-2: configuration #1 chosen from 1 choice
Apr 20 21:46:10 wizzle kernel: [300789.776434] scsi8 : SCSI emulation for USB Mass Storage devices
Apr 20 21:46:10 wizzle kernel: [300789.776801] usb-storage: device found at 10
Apr 20 21:46:10 wizzle kernel: [300789.776806] usb-storage: waiting for device to settle before scanning
Apr 20 21:46:15 wizzle kernel: [300794.776540] usb-storage: device scan complete
Apr 20 21:46:15 wizzle kernel: [300794.777527] scsi 8:0:0:0: Direct-Access A-DATA SH93 PQ: 0 ANSI: 0
Apr 20 21:46:15 wizzle kernel: [300794.778784] sd 8:0:0:0: Attached scsi generic sg3 type 0
Apr 20 21:46:15 wizzle kernel: [300794.780284] sd 8:0:0:0: [sdc] 625142448 512-byte logical blocks: (320 GB/298 GiB)
Apr 20 21:46:15 wizzle kernel: [300794.780879] sd 8:0:0:0: [sdc] Write Protect is off
Apr 20 21:46:15 wizzle kernel: [300794.780886] sd 8:0:0:0: [sdc] Mode Sense: 03 00 00 00
Apr 20 21:46:15 wizzle kernel: [300794.780892] sd 8:0:0:0: [sdc] Assuming drive cache: write through
Apr 20 21:46:15 wizzle kernel: [300794.785623] sd 8:0:0:0: [sdc] Assuming drive cache: write through
Apr 20 21:46:15 wizzle kernel: [300794.785635] sdc: sdc1
Apr 20 21:46:15 wizzle kernel: [300794.829620] sd 8:0:0:0: [sdc] Assuming drive cache: write through
Apr 20 21:46:15 wizzle kernel: [300794.829631] sd 8:0:0:0: [sdc] Attached SCSI disk
Apr 20 21:46:17 wizzle ntfs-3g[7614]: Version 2010.3.6 external FUSE 28
Apr 20 21:46:17 wizzle ntfs-3g[7614]: Mounted /dev/sdc1 (Read-Write, label "kolibri", NTFS 3.1)

Revision history for this message
Alexus (alexus230zzz) wrote :

Та же проблема. В 9.10 вс

Revision history for this message
Alexus (alexus230zzz) wrote :
Download full text (5.6 KiB)

A-Data SH93 500GB

Ubuntu 9.10 - ok

Ubuntu 10.04 beta2:

kernel: [ 1639.736050] usb 1-4: new high speed USB device using ehci_hcd and address 7
kernel: [ 1639.869806] usb 1-4: configuration #1 chosen from 1 choice
kernel: [ 1639.870202] scsi4 : SCSI emulation for USB Mass Storage devices
kernel: [ 1639.870380] usb-storage: device found at 7
kernel: [ 1639.870382] usb-storage: waiting for device to settle before scanning
kernel: [ 1644.868295] usb-storage: device scan complete
kernel: [ 1644.868865] scsi 4:0:0:0: Direct-Access A-DATA SH93 PQ: 0 ANSI: 0
kernel: [ 1644.871549] sd 4:0:0:0: Attached scsi generic sg2 type 0
kernel: [ 1644.872433] sd 4:0:0:0: [sdb] 976773168 512-byte logical blocks: (500 GB/465 GiB)
kernel: [ 1644.872949] sd 4:0:0:0: [sdb] Write Protect is off
kernel: [ 1644.872953] sd 4:0:0:0: [sdb] Mode Sense: 03 00 00 00
kernel: [ 1644.872956] sd 4:0:0:0: [sdb] Assuming drive cache: write through
kernel: [ 1644.874453] sd 4:0:0:0: [sdb] Assuming drive cache: write through
kernel: [ 1644.874459] sdb: sdb1 sdb2 sdb3
kernel: [ 1644.898204] sd 4:0:0:0: [sdb] Assuming drive cache: write through
kernel: [ 1644.898211] sd 4:0:0:0: [sdb] Attached SCSI disk
kernel: [ 1659.440693] sd 4:0:0:0: [sdb] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
kernel: [ 1659.440701] sd 4:0:0:0: [sdb] Sense Key : Illegal Request [current]
kernel: [ 1659.440707] sd 4:0:0:0: [sdb] Add. Sense: Invalid command operation code
kernel: [ 1659.440713] sd 4:0:0:0: [sdb] CDB: Read(6): 08 00 00 3f 08 00
kernel: [ 1659.440722] end_request: I/O error, dev sdb, sector 63
kernel: [ 1659.440729] Buffer I/O error on device sdb1, logical block 0
kernel: [ 1659.440735] Buffer I/O error on device sdb1, logical block 1
kernel: [ 1659.440738] Buffer I/O error on device sdb1, logical block 2
kernel: [ 1659.440741] Buffer I/O error on device sdb1, logical block 3
kernel: [ 1659.441699] sd 4:0:0:0: [sdb] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
kernel: [ 1659.441705] sd 4:0:0:0: [sdb] Sense Key : Illegal Request [current]
kernel: [ 1659.441711] sd 4:0:0:0: [sdb] Add. Sense: Invalid command operation code
kernel: [ 1659.441717] sd 4:0:0:0: [sdb] CDB: Read(6): 08 00 00 3f 02 00
kernel: [ 1659.441725] end_request: I/O error, dev sdb, sector 63
kernel: [ 1659.441730] Buffer I/O error on device sdb1, logical block 0
kernel: [ 1659.442568] sd 4:0:0:0: [sdb] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
kernel: [ 1659.442574] sd 4:0:0:0: [sdb] Sense Key : Illegal Request [current]
kernel: [ 1659.442579] sd 4:0:0:0: [sdb] Add. Sense: Invalid command operation code
kernel: [ 1659.442584] sd 4:0:0:0: [sdb] CDB: Read(6): 08 00 00 41 02 00
kernel: [ 1659.442592] end_request: I/O error, dev sdb, sector 65
kernel: [ 1659.442596] Buffer I/O error on device sdb1, logical block 1
kernel: [ 1659.443569] sd 4:0:0:0: [sdb] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
kernel: [ 1659.443576] sd 4:0:0:0: [sdb] Sense Key : Illegal Request [current]
kernel: [ 1659.443581] sd 4:0:0:0: [sdb] Add. Sense: Invalid command operation code
kernel: [ 1659.443587] sd 4:0:0:0: [sdb] CDB: Read(6): 08 00 00 43 04 00
kernel: [ 1659.443594] end_request: I/O error, dev sdb, secto...

Read more...

Revision history for this message
bazi (bazidzem) wrote :

True mine is also working now after update (lucid).

Revision history for this message
P0w3r3d (anielkis) wrote :

hi, someone can tell me where was the error, and how it was fixed?? i have the same problem with other distribution..
Thanks

Revision history for this message
Pete Graner (pgraner) wrote :

This issue is confirmed fixed by server comments in the bug. Most likely a udev change.

Changed in linux (Ubuntu):
status: Confirmed → Fix Released
affects: linux (Ubuntu) → udev (Ubuntu)
Changed in udev (Ubuntu):
assignee: Canonical Kernel Team (canonical-kernel-team) → nobody
Revision history for this message
Tomas Bulajcsik (tomas-bulajcsik) wrote :

Hello,
I am new here, I have the same HDD, could install Lucid, but it cannot boot.
How should I fix it?

Thank you
Tomas

Revision history for this message
Tom Parkin (tom-parkin) wrote :

Without wanting to add unnecessary noise to a closed bug, I just wanted to note that I still see this issue with a Ubuntu 10.04.2 install, freshly updated on 18th March 2011.

I have udev 151-12.3 installed.

With udev running I see this bug. If I turn udev off[1] then I can mount my usb hdd OK.

So I think this issue is present in udev 151-12.3.

[1] /etc/init.d/udev stop

Revision history for this message
Tatsiana (tata-na) wrote :

Hello,

Last week I bouught ADATA SH93 500 GB.
I had the same problem: my thinkpad "Lenovo x100e" with WIN7 did not see ADATA SH93 but another PC with Win XP detected this device without any problem.
This problem was resolved. I downloaded and installed last x100e drivers/updates for WIN7 from "native" site lenovo.com and after this manipulation all is ok: ADATA SH93 is detected under win7. So my advice - to install last related WIN7 updates for your PC.

Hope this will help someone...

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.