SOLVED: USB-Harddrive not detected anymore

[sheeva_user]

Hello,
my Sheevaplug has been running fine for nine months, 24/7. Always connected to it was a 2.5" Harddrive without power supply. This HD was always mounted as /dev/sda1. Since a few days, the HD is not detected anymore.

When switching the Sheeva on, the HD-LED lights for a few seconds, then turns off, while booting "/dev/sda1 was not detected". My first guess was, the HD was broken, but connected to any other computer it runs just fine. Also a 3.5" HD with external power is not detected by the Sheeva anymore.

A first google-search now lets me fear, the USB-connector of the Sheeva is broken. Has anybody any hints how to find the source of the problem?

Thank you very much for your help!

Ralf

[Confusticated]

Look up the pinout of the USB port and measure the 5v with a meter to see if it is correct.

[sheeva_user]

Thank you for the good hint. The voltage is constantly 4.96 V during the whole boot process. This should be enough, shouldn't it?

[Confusticated]

That looks good, so unlikely a PSU\USB power on switch problem.
My next step would be to do a 'lsusb' on the plug and see if it correctly detects the internal hub built into the Sheeva.
Post the output if you are not sure what you are looking for.

[sheeva_user]

Hub and HD are listed by lsusb:

Code:

Bus 001 Device 002: ID 04e8:1f06 Samsung Electronics Co., Ltd HX-MU064DA portable harddisk
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

Some lines of the syslog that might be interesting:

Code:

[   22.428428] NAND device: Manufacturer ID: 0xad, Chip ID: 0xdc (Hynix NAND 512MiB 3,3V 8-bit)
[   22.436949] Scanning device for bad blocks
[   22.530900] Bad eraseblock 3075 at 0x000018060000
[   22.535757] Bad eraseblock 3079 at 0x0000180e0000
[   22.540594] Bad eraseblock 3083 at 0x000018160000
[   22.545386] Bad eraseblock 3085 at 0x0000181a0000
[   22.552400] Bad eraseblock 3163 at 0x000018b60000
[   22.563699] Bad eraseblock 3388 at 0x00001a780000
[   22.568455] Bad eraseblock 3389 at 0x00001a7a0000
[   22.587260] Bad eraseblock 3871 at 0x00001e3e0000
[   22.598535] Creating 3 MTD partitions on "orion_nand":
...
[   22.931432] udev[44]: starting version 164

[   23.222777] usbcore: registered new interface driver usbfs

[   23.228924] usbcore: registered new interface driver hub

[   23.234954] usbcore: registered new device driver usb

[   23.263287] mmc0: mvsdio driver initialized, lacking card detect (fall back to polling)

[   23.285167] MV-643xx 10/100/1000 ethernet driver version 1.4

[   23.291160] mv643xx_eth smi: probed

[   23.297802] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver

[   23.310092] net eth0: port 0 with MAC address f0:ad:4e:00:66:91

[   23.319688] orion-ehci orion-ehci.0: Marvell Orion EHCI

[   23.327159] orion-ehci orion-ehci.0: new USB bus registered, assigned bus number 1

[   23.359913] mmc0: host does not support reading read-only switch. assuming write-enable.

[   23.368463] orion-ehci orion-ehci.0: irq 19, io mem 0xf1050000

[   23.374360] mmc0: new high speed SDHC card at address 8fe4

[   23.392336] orion-ehci orion-ehci.0: USB 2.0 started, EHCI 1.00

[   23.400503] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002

[   23.407368] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1

[   23.414635] usb usb1: Product: Marvell Orion EHCI

[   23.419364] usb usb1: Manufacturer: Linux 2.6.32-5-kirkwood ehci_hcd

[   23.425761] usb usb1: SerialNumber: orion-ehci.0

[   23.431717] mmcblk0: mmc0:8fe4 SD04G 3.69 GiB

[   23.436333]  mmcblk0:

[   23.439065] usb usb1: configuration #1 chosen from 1 choice

[   23.444973]  p1 p2 p3 <

[   23.447673] hub 1-0:1.0: USB hub found

[   23.451709]  p5 >

[   23.454536] hub 1-0:1.0: 1 port detected

Begin: Loading essential drivers ... done.

Begin: Running /scripts/init-premount ... done.

Begin: Mounting root file system ... Begin: Running /scripts/local-top ... done.

Begin: Running /scripts/local-premount ... done.

Begin: Running /scripts/local-bottom ... done.

done.

Begin: Running /scripts/init-bottom ... done.

[   23.771038] usb 1-1: new high speed USB device using orion-ehci and address 2


INIT: version 2.88 booting


[   23.922007] usb 1-1: New USB device found, idVendor=04e8, idProduct=1f06

[   23.928756] usb 1-1: New USB device strings: Mfr=1, Product=11, SerialNumber=3

[   23.936031] usb 1-1: Product: Samsung S2 Portable

[   23.940755] usb 1-1: Manufacturer: JMicron

[   23.944887] usb 1-1: SerialNumber: 00000011E093105007C0

[   23.952326] usb 1-1: configuration #1 chosen from 1 choice

Using makefile-style concurrent boot in runlevel S.

Starting the hotplug events dispatcher: udevd[   24.256823] udev[147]: starting version 164

.

Synthesizing the initial hotplug events...done.

Waiting for /dev to be fully populated...[   24.697132] scsi_mod: Unknown symbol blk_get_queue

[   24.708031] scsi_mod: Unknown symbol blk_put_queue

done.

Activating swap...[   24.923214] Adding 220152k swap on /dev/mmcblk0p5.  Priority:-1 extents:1 across:220152k SS

done.

Checking root file system...fsck from util-linux-ng 2.17.2

e2fsck 1.41.12 (17-May-2010)

/dev/mmcblk0p2: clean, 61432/429408 files, 405705/857344 blocks

done.

Cleaning up ifupdown....

[   25.247184] loop: module loaded

Loading kernel modules...done.

Setting up networking....

Activating lvm and md swap...done.

Checking file systems...fsck from util-linux-ng 2.17.2

e2fsck 1.41.12 (17-May-2010)

/dev/mmcblk0p1: clean, 19/110160 files, 28665/220160 blocks

done.

Mounting local filesystems...mount: special device /dev/sda1 does not exist

failed.

[Confusticated]

Looking at your syslog, that is not a configuration I am familiar with.
This does not look like a HDD failure to me, are you sure nothing has changed since the device partition 'disappeared', do you have automatic updates enabled ?
What does 'fdisk -l' show (does /dev/sdc1 exist) ?
Run 'dmesg -c' with the drive disconnected to clear the kernel message buffer, then connect the drive and run 'dmesg' to display any new entries.

[sheeva_user]

Thank you for your patience Confusticated! 

I put Debian on a SD-Card, following the tutorial at cyrius.com and occasionally have installed suggested updates.
 fdisk -l doesn't show /dev/sda1:

Code:

Disk /dev/mmcblk0: 3965 MB, 3965190144 bytes
4 heads, 16 sectors/track, 121008 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00086191

        Device Boot      Start         End      Blocks   Id  System
/dev/mmcblk0p1   *          33        6912      220160   83  Linux
Partition 1 does not end on cylinder boundary.
/dev/mmcblk0p2            6913      114080     3429376   83  Linux
Partition 2 does not end on cylinder boundary.
/dev/mmcblk0p3          114112      120992      220161    5  Extended
Partition 3 does not end on cylinder boundary.
/dev/mmcblk0p5          114113      120992      220160   82  Linux swap / Solaris

dmesg after pluging in the HD says:

Code:

[  108.571017] usb 1-1: new high speed USB device using orion-ehci and address 3
[  108.722030] usb 1-1: New USB device found, idVendor=04e8, idProduct=1f06
[  108.728764] usb 1-1: New USB device strings: Mfr=1, Product=11, SerialNumber=3
[  108.736036] usb 1-1: Product: Samsung S2 Portable
[  108.740761] usb 1-1: Manufacturer: JMicron
[  108.744893] usb 1-1: SerialNumber: 00000011E093105007C0
[  108.752704] usb 1-1: configuration #1 chosen from 1 choice
[  108.781960] scsi_mod: Unknown symbol blk_get_queue
[  108.792911] scsi_mod: Unknown symbol blk_put_queue

[sheeva_user]

Confusticated! Your question for updates put me on a good track!
 
I tried a flash-kernel and reboot and:

Code:

Disk /dev/sda: 640.1 GB, 640135028736 bytes
255 heads, 63 sectors/track, 77825 cylinders

Thank you so much! :-)

[Confusticated]

scsi_mod: Unknown symbol blk_get_queue

Here is your problem (don't believe I missed it in your earlier post), I bet that an update has taken place and broken things.
I suggest you try another update, and make sure that you keep your kernel in sync with the disto, which you will need to perform by hand as 'apt-get upgrade' doesn't know to use 'mkimage' on the kernel and copy the resulting uImage into place.


EDIT: Hehe you got there before me, the forum bounced my post cos you had already solved it & posted yourself !
I need to learn to type faster, happy plugging!

[aleandro]

Open a shell and execute:

flash-kernel

Do a reboot and see if it helps.

[sheeva_user]

Thanks Aleandro!
I did this and it worked!

Is there a way to set this topic solved?

Happy Plugging!