HITACHI 500g usb hd not recognized

skid vicious · 2012-02-04 16:37:09

greetings #bangers.

i incorrectly assumed with my recent (1st) #! install that all my usb goodies were working since i was able to effortlessly plug and play an 8g thumb drive. however, it seems there is some distinction (size?) between that and my external usb drive. i ran a few searches on the forum and found similar troubles but not exact.

i know somebody else had trouble with 'permissions' but my problem is that the drive is not even seen. but for the record, the power light comes on and i can hear the whir of promise in the thing but that is where my good fortune ends.

i.m running the latest stable version of #! on a lenovo thinkpad SL410. i had this problem once before with debian squeeze and eventually had to resort to a re-install of the OS, which always feels like a cop-out to me. i would like to bring my kung fu up to a level where i can solve my problems with a scalpel as opposed to a sledge hammer. can anybody offer me some suggestions here...?

here are some outputs with the device plugged in:

zello@crunchbang:/etc$ lsusb
Bus 008 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 007 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 006 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 003 Device 002: ID 04b4:0060 Cypress Semiconductor Corp.
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 002 Device 002: ID 17ef:4810 Lenovo Integrated Webcam [R5U877]
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 003: ID 4971:1012 SimpleTech
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

xaos52 · 2012-02-04 16:46:19

The device probably is detected, but not automounted.
Try this:
unplug the device if it is plugged in
plug it in again
wait a couple seconds
run this command in a terminal window, and post the output on the forum:

dmesg|tail -n 80

Last edited by xaos52 (2012-02-04 16:46:51)

skid vicious · 2012-02-04 17:06:46

thanks xaos52 for the quick response. here.s that info:

zello@crunchbang:/dev$ dmesg|tail -n 80
[ 5360.641599] iwlwifi 0000:05:00.0: Error sending REPLY_RXON: enqueue_hcmd failed: -5
[ 5360.641603] iwlwifi 0000:05:00.0: Error clearing ASSOC_MSK on BSS (-5)
[ 5360.641607] wlan0: deauthenticating from e0:46:9a:c6:f0:e7 by local choice (reason=3)
[ 5360.641624] iwlwifi 0000:05:00.0: Not sending command - RF KILL
[ 5360.641628] iwlwifi 0000:05:00.0: Error sending REPLY_ADD_STA: enqueue_hcmd failed: -5
[ 5360.641633] ieee80211 phy0: failed to remove key (1, ff:ff:ff:ff:ff:ff) from hardware (-5)
[ 5360.641638] iwlwifi 0000:05:00.0: Not sending command - RF KILL
[ 5360.641642] iwlwifi 0000:05:00.0: Error sending REPLY_ADD_STA: enqueue_hcmd failed: -5
[ 5360.641646] ieee80211 phy0: failed to remove key (2, ff:ff:ff:ff:ff:ff) from hardware (-5)
[ 5360.641663] iwlwifi 0000:05:00.0: Not sending command - RF KILL
[ 5360.641667] iwlwifi 0000:05:00.0: Error sending REPLY_ADD_STA: enqueue_hcmd failed: -5
[ 5360.641671] ieee80211 phy0: failed to remove key (0, e0:46:9a:c6:f0:e7) from hardware (-5)
[ 5360.641676] iwlwifi 0000:05:00.0: Not sending command - RF KILL
[ 5360.641680] iwlwifi 0000:05:00.0: Error sending REPLY_REMOVE_STA: enqueue_hcmd failed: -5
[ 5360.641684] iwlwifi 0000:05:00.0: Error removing station e0:46:9a:c6:f0:e7
[ 5360.641692] iwlwifi 0000:05:00.0: Not sending command - RF KILL
[ 5360.641696] iwlwifi 0000:05:00.0: Error sending REPLY_RXON: enqueue_hcmd failed: -5
[ 5360.641700] iwlwifi 0000:05:00.0: Error clearing ASSOC_MSK on BSS (-5)
[ 5360.641764] iwlwifi 0000:05:00.0: Not sending command - RF KILL
[ 5360.641799] iwlwifi 0000:05:00.0: Error sending REPLY_LEDS_CMD: enqueue_hcmd failed: -5
[ 5360.641805] iwlwifi 0000:05:00.0: Not sending c

skid vicious · 2012-02-04 17:11:19

whoops. is there some off site spot i should post these long readouts? here.s what appears to be the relevant info. you.re right, it does actuall "see" the drive...:

[ 7196.982872] usb 1-2: USB disconnect, device number 3
[ 7231.248059] usb 1-2: new high-speed USB device number 4 using ehci_hcd
[ 7231.382564] usb 1-2: New USB device found, idVendor=4971, idProduct=1012
[ 7231.382570] usb 1-2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 7231.382574] usb 1-2: Product: Touro Mobile Pro
[ 7231.382577] usb 1-2: Manufacturer: Hitachi GST
[ 7231.382580] usb 1-2: SerialNumber: 02100110711000001041
[ 7231.388695] scsi7 : uas
[ 7235.350400] scsi 7:0:0:0: Direct-Access Hitachi Touro Mobile Pro A0D0 PQ: 0 ANSI: 4
[ 7242.016055] scsi 7:0:0:0: uas_eh_abort_handler tag 0
[ 7242.016062] scsi 7:0:0:0: uas_eh_device_reset_handler tag 0
[ 7242.016066] scsi 7:0:0:0: uas_eh_target_reset_handler tag 0
[ 7242.016070] scsi 7:0:0:0: uas_eh_bus_reset_handler tag 0
[ 7242.128060] usb 1-2: reset high-speed USB device number 4 using ehci_hcd
[ 7242.261884] scsi 7:0:0:0: Device offlined - not ready after error recovery
[ 7242.261916] scsi 7:0:0:0: rejecting I/O to offline device
[ 7242.261925] scsi 7:0:0:0: rejecting I/O to offline device
[ 7242.263277] scsi 7:0:0:1: Enclosure Hitachi SES A0D0 PQ: 0 ANSI: 4
[ 7242.263497] scsi 7:0:0:2: uas_sense_old: urb length 26 disagrees with IU sense data length 510, using 18 bytes of sense data
[ 7242.265196] sd 7:0:0:0: Attached scsi generic sg2 type 0
[ 7242.265374] ses 7:0:0:1: Attached Enclosure device
[ 7242.266042] ses 7:0:0:1: Attached scsi generic sg3 type 13
[ 7273.056058] sd 7:0:0:0: uas_eh_abort_handler tag 0
[ 7273.056065] sd 7:0:0:0: uas_eh_device_reset_handler tag 0
[ 7273.056069] sd 7:0:0:0: uas_eh_target_reset_handler tag 0
[ 7273.056073] sd 7:0:0:0: uas_eh_bus_reset_handler tag 0
[ 7273.168060] usb 1-2: reset high-speed USB device number 4 using ehci_hcd
[ 7273.301869] sd 7:0:0:0: Device offlined - not ready after error recovery
[ 7273.301903] sd 7:0:0:0: rejecting I/O to offline device
[ 7273.301913] sd 7:0:0:0: rejecting I/O to offline device
[ 7273.301919] sd 7:0:0:0: rejecting I/O to offline device
[ 7273.301924] sd 7:0:0:0: [sdb] READ CAPACITY failed
[ 7273.301927] sd 7:0:0:0: [sdb] Result: hostbyte=DID_NO_CONNECT driverbyte=DRIVER_OK

xaos52 · 2012-02-04 17:14:22

Cant be. I asked for 80 lines, and only got 21 or so...
Seems like you are flooded with iwlwifi error messages. Is your wireless working?
Can you post the output of

dmesg|grep sd

after inserting the USB drive.
Oh, and please post between [ code ] tags.

xaos52 · 2012-02-04 17:24:09

Are you trying to mount an USB-3 device?
The system detects tne new drive, but can not handle it because it has USB-1/2 interfaces only?

skid vicious · 2012-02-04 17:33:09

ok. i just left the central office where i was, now at a different wifi spot. yeah, i was having connectivity issues.
here is the code:

zello@crunchbang:~$ dmesg|grep sd
[    0.854280] sdhci: Secure Digital Host Controller Interface driver
[    0.854283] sdhci: Copyright(c) Pierre Ossman
[    0.854494] sdhci-pci 0000:02:00.0: SDHCI controller found [197b:2382] (rev 0)
[    0.854516] sdhci-pci 0000:02:00.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16
[    0.854555] sdhci-pci 0000:02:00.0: setting latency timer to 64
[    0.956353] sdhci-pci 0000:02:00.2: SDHCI controller found [197b:2381] (rev 0)
[    0.956366] sdhci-pci 0000:02:00.2: PCI INT A -> GSI 16 (level, low) -> IRQ 16
[    0.956372] sdhci-pci 0000:02:00.2: Refusing to bind to secondary interface.
[    0.956379] sdhci-pci 0000:02:00.2: PCI INT A disabled
[    2.405837] sd 0:0:0:0: [sda] 625142448 512-byte logical blocks: (320 GB/298 GiB)
[    2.405876] sd 0:0:0:0: [sda] Write Protect is off
[    2.405878] sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00
[    2.405895] sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[    2.457318]  sda: sda1 sda2 < sda5 sda6 sda7 sda8 sda9 >
[    2.457828] sd 0:0:0:0: [sda] Attached SCSI disk
[    2.461991] sd 0:0:0:0: Attached scsi generic sg0 type 0
[    3.248208] EXT4-fs (sda1): mounted filesystem with ordered data mode. Opts: (null)
[    7.164140] Adding 5761020k swap on /dev/sda7.  Priority:-1 extents:1 across:5761020k 
[    7.168844] EXT4-fs (sda1): re-mounted. Opts: (null)
[    7.653483] EXT4-fs (sda1): re-mounted. Opts: errors=remount-ro
[    8.939702] EXT4-fs (sda9): mounted filesystem with ordered data mode. Opts: (null)
[    9.012550] EXT4-fs (sda8): mounted filesystem with ordered data mode. Opts: (null)
[    9.081052] EXT4-fs (sda5): mounted filesystem with ordered data mode. Opts: (null)
[    9.179718] EXT4-fs (sda6): mounted filesystem with ordered data mode. Opts: (null)
[  295.081066] sd 6:0:0:0: Attached scsi generic sg2 type 0
[  326.048047] sd 6:0:0:0: uas_eh_abort_handler tag 0
[  326.048054] sd 6:0:0:0: uas_eh_device_reset_handler tag 0
[  326.048058] sd 6:0:0:0: uas_eh_target_reset_handler tag 0
[  326.048062] sd 6:0:0:0: uas_eh_bus_reset_handler tag 0
[  326.293819] sd 6:0:0:0: Device offlined - not ready after error recovery
[  326.293851] sd 6:0:0:0: rejecting I/O to offline device
[  326.293860] sd 6:0:0:0: rejecting I/O to offline device
[  326.293867] sd 6:0:0:0: rejecting I/O to offline device
[  326.293872] sd 6:0:0:0: [sdb] READ CAPACITY failed
[  326.293875] sd 6:0:0:0: [sdb]  Result: hostbyte=DID_NO_CONNECT driverbyte=DRIVER_OK
[  326.293880] sd 6:0:0:0: [sdb] Sense not available.
[  326.293886] sd 6:0:0:0: rejecting I/O to offline device
[  326.293891] sd 6:0:0:0: [sdb] Write Protect is off
[  326.293895] sd 6:0:0:0: [sdb] Mode Sense: 00 00 00 00
[  326.293901] sd 6:0:0:0: rejecting I/O to offline device
[  326.293905] sd 6:0:0:0: [sdb] Asking for cache data failed
[  326.293909] sd 6:0:0:0: [sdb] Assuming drive cache: write through
[  326.294618] sd 6:0:0:0: [sdb] Attached SCSI disk

skid vicious · 2012-02-04 17:35:43

and yes, the hitachi touros is 3.0 but for what it.s worth, debian squeeze was able to work with it, excepting that one glitch...

xaos52 · 2012-02-04 17:54:05

Seems like this bug:
https://bugs.launchpad.net/ubuntu/+sour … bug/901215
Solution (or rather workaround) is to blacklist 'uas'
Let me know if you do not know how to do that.
hth

Last edited by xaos52 (2012-02-04 17:56:12)

skid vicious · 2012-02-04 18:18:03

ok. it.s not often that i giggle like a schoolgirl in public but here i am at my favorite chinese place with wifi, with "problem solved" written all over my face! thanks a million!

big_smile

i guess i never thought to use the term 'bug' in my search string. is that how you found this workaround?

xaos52 · 2012-02-04 18:55:07

No, searched on 'hitachi touros +linux'.

Enjoy the Chinese food smile

CrunchBang Linux

SEARCH

#1 2012-02-04 16:37:09

HITACHI 500g usb hd not recognized

#2 2012-02-04 16:46:19

Re: HITACHI 500g usb hd not recognized

#3 2012-02-04 17:06:46

Re: HITACHI 500g usb hd not recognized

#4 2012-02-04 17:11:19

Re: HITACHI 500g usb hd not recognized

#5 2012-02-04 17:14:22

Re: HITACHI 500g usb hd not recognized

#6 2012-02-04 17:24:09

Re: HITACHI 500g usb hd not recognized

#7 2012-02-04 17:33:09

Re: HITACHI 500g usb hd not recognized

#8 2012-02-04 17:35:43

Re: HITACHI 500g usb hd not recognized

#9 2012-02-04 17:54:05

Re: HITACHI 500g usb hd not recognized

#10 2012-02-04 18:18:03

Re: HITACHI 500g usb hd not recognized

#11 2012-02-04 18:55:07

Re: HITACHI 500g usb hd not recognized

Board footer