USB SATA harddisc registered, but not accessable

gargamel · 09-29-2007, 07:48 PM

Hi,

after spending several hours reading virtually every post regarding USB disks I didn't seem to find anything really covering my problem. So I hope for some hints how to track things down and to identify what the problems is actually caused by.

I just bought a Fujitsu-Siemens Storagebird XL-E external USB 2.0 harddisc. When I connect the device, it appears in the list of USB devices:

Code:

# lsusb
Bus 1 Device 10: ID 0766:0012 Jess-Link Products Co., Ltd

The output of dmesg is:

Code:

usb 1-5.2: new high speed USB device using ehci_hcd and address 10
usb 1-5.2: configuration #1 chosen from 1 choice
scsi6 : SCSI emulation for USB Mass Storage devices
usb-storage: device found at 10
usb-storage: waiting for device to settle before scanning
kobject_add failed for usb_storage with -EEXIST, don't try to register things with the same name in the same directory.
 [<c03e86f7>] kobject_shadow_add+0x117/0x1a0
 [<c013fba4>] mod_sysfs_setup+0x24/0xb0
 [<c0141458>] sys_init_module+0x1648/0x1940
 [<c0102ae8>] syscall_call+0x7/0xb
 =======================
scsi 6:0:0:0: Direct-Access     Ext Hard  Disk                 PQ: 0 ANSI: 4
sdb: Spinning up disk.......................................................................................................not responding...
sdb : READ CAPACITY failed.
sdb : status=1, message=00, host=0, driver=08
sd: Current: sense key=0x2
    ASC=0x4 ASCQ=0x0
sdb: test WP failed, assume Write Enabled
sdb: assuming drive cache: write through
sd 6:0:0:0: Attached scsi disk sdb
sd 6:0:0:0: Attached scsi generic sg1 type 0
usb-storage: device scan complete
kobject_add failed for usb_storage with -EEXIST, don't try to register things with the same name in the same directory.
 [<c03e86f7>] kobject_shadow_add+0x117/0x1a0
 [<c013fba4>] mod_sysfs_setup+0x24/0xb0
 [<c0141458>] sys_init_module+0x1648/0x1940
 [<c0102ae8>] syscall_call+0x7/0xb
 =======================
EXT4-fs: unable to read superblock
FAT: unable to read boot sector

Other than USB sticks and my other external USB harddrives, the storagebird isn't mounted, and it doesn't appear in the KDE system tray (/media/disk etc.).

However, other than my external USB harddiscs from Trekstor, the Fujitsu-Siemens Storagebird is not an USB hub. Not sure, if this has anything to do with my problem.

BTW, the disk doesn't appear in the MS Windows XP file explorer as a removable drive, also! When I connect it to my Windows system, I hear the bell ringing informing me of the new device. But then nothing happens.

I'd be grateful for any clue, what's wrong here. Could it be that the device is defunct? Or do I need additional kernel modules? How can I find out, what's actually wrong?

Thanks a lot in advance,

gargamel

onebuck · 09-29-2007, 08:55 PM

Hi,

Which kernel?

duryodhan · 09-29-2007, 11:57 PM

The device is defunct!!

ok , you could try twiddling with the wire. Try connecting it to a USB jack at the back of your comp and not the one on the front.

I think that the problem is with power, your HDD isn't probably getting enough power (are you able to hear the sound of the read pin dropping and then the disc spinning again and then a small click etc. etc.)

some cases come with 2 USB wires ( so that you can get power from 2 ports ) , if thats the case connect both. Try changing the case. Some cases come with facility of external DC power , try that ...

basically , I believe it is a H/W issue.

Is it a 3.5 inch or 2.5 inch HDD ?If it is the former you could remove it from the case and connect it directly to a computer and test ..

best is .. if you are still covered by warranty just replace the damn thing

gargamel · 09-30-2007, 05:57 AM

Quote:

Originally Posted by duryodhan

The device is defunct!!

ok , you could try twiddling with the wire. Try connecting it to a USB jack at the back of your comp and not the one on the front.

I think that the problem is with power, your HDD isn't probably getting enough power (are you able to hear the sound of the read pin dropping and then the disc spinning again and then a small click etc. etc.)

some cases come with 2 USB wires ( so that you can get power from 2 ports ) , if thats the case connect both. Try changing the case. Some cases come with facility of external DC power , try that ...

basically , I believe it is a H/W issue.

Is it a 3.5 inch or 2.5 inch HDD ?If it is the former you could remove it from the case and connect it directly to a computer and test ..

best is .. if you are still covered by warranty just replace the damn thing

Thanks for both your answers. I run the 2.6.21.5 stock kernel of Slackware 12.0, not sure if it's the modularized or the everything-compiled-in version. The device is completely new 3.5" USB 2.0 drive with an external power supply. According to the specs it should be able to work with a USB 2.0 connection only, but the signal LED is green only when the external supply is connected. I've tried all 6 USB jacks of my computer, although only one of the two on the front is USB 2.0 (the rest is USB 1.1). I have never heard any noise from within the box, and the LED was never flashing, which it should do, according to the manual, when there is data transferred.

That's why I also suspect that it is a hardware problem. I'll replace it, as you suggest.

That brings up my next question: Although it costs a bit more, I am thinking of replacing it with a LAN (instead of USB) device.

Good or bad idea, what would you think?

Thanks for your good advice!

gargamel

duryodhan · 09-30-2007, 08:57 AM

I would stick with USB ... if what you want is a portable storage solution.

If you want a storage solution then a NAS is a much better bet .

USB is much more portable, standardised and support is pretty much defacto. Why mess with that?

Also, normal ethernet is only 100MBps (gigabit is well, gigabit!) , whereas USB 2.0 is 480 MBps.

I don't know where you are and how good you are with H/W, but what I have generally found to be cheaper over at my place is to buy a 2.5" laptop HDD and a case and fix them up together. YMMV.

onebuck · 09-30-2007, 10:48 AM

Hi,

You could check to see if the external drive functions on another system to confirm the issue is indeed a hardware failure. If the drive is at fault then take it back. It could be a USB issue for the MB. That is why I suggest another machine to test on.

Do a 'uname -r' to see th exact kernel in use. The error shown in your dmesg output is just due to the driver already in the kernel.

gargamel · 09-30-2007, 12:12 PM

Thanks again. I've tried the device now on three machines:
- main machine (tower) with AMD Athlon, one USB 2.0 and five USB 1.1 ports running Slackware 12.0 and OpenSuSE 10.2
- my old Toshiba Satellite laptop, with only one USB 1.1 port, also running Slack 12
- my 2 years old corporate laptop, running MS Windows XP, with three USB 2.0 ports

The Slackware systems both run kernel 2.6.21.5-smp (although smp support is useless on them).

While on the Slackware and SuSE Linux systems I can see that the device identifies itself, but the harddisc is not spinning up.

On the MS Windows laptop, the bell rings, telling me that some new device has been found. But nothing else happens.

So it's not working on three machines with totally different hardware, running the finest two Linux brands and one 'alternative' system. ;-) If the device is defunct or not: It's not working in my environment, so I'll return it.

Thanks also for the advice to stick with USB.

Best regards

gargamel

gargamel · 10-04-2007, 09:52 AM

Just to let you know, your guess was absolutely right: The harddisc was defunct. I had it replaced, the new device works like a charm.

So this issue is SOLVED. 8-)

Thanks,

gargamel