usb hdd not mounting (after it was dropped)

Questions about hardware,drivers and peripherals
Forum rules
Before you post please read how to get help
Post Reply
kkna9877
Level 1
Level 1
Posts: 2
Joined: Fri Aug 14, 2015 9:03 am

usb hdd not mounting (after it was dropped)

Post by kkna9877 » Sat Jan 13, 2018 6:56 am

I have Seagate usb hdd that was dropped about 8" (so I would not expect a failure). Details are below. Is there anything else I could try before extracting the disk and trying it with a different caddy?

Thanks
Tim

Code: Select all

inxi -Sr
System:    Host: TimLaptop Kernel: 3.13.0-24-generic x86_64 (64 bit) Desktop: Xfce 4.11.8 Distro: Linux Mint 17 Qiana

When I plug it in I get

Code: Select all

lsblk
NAME   MAJ:MIN RM   SIZE RO TYPE MOUNTPOINT
sda      8:0    0 931.5G  0 disk 
├─sda1   8:1    0   512M  0 part /boot/efi
├─sda2   8:2    0 923.1G  0 part /
└─sda3   8:3    0   7.9G  0 part [SWAP]
sdb      8:16   0 931.5G  0 disk 
so the disk is seen but without partitions

Code: Select all

lsblk /dev/sdb
NAME MAJ:MIN RM   SIZE RO TYPE MOUNTPOINT
sdb    8:16   0 931.5G  0 disk 
gparted hangs when the disk is connected (scanning) so I can't even re-partition it. I have tried to repartition using the Windows HP USB tool but that does not work either

tail /var/kern.log is

Code: Select all

Jan 13 10:22:50 TimLaptop kernel: [   55.090012] usb-storage 1-4.1:1.0: USB Mass Storage device detected
Jan 13 10:22:50 TimLaptop kernel: [   55.090334] scsi2 : usb-storage 1-4.1:1.0
Jan 13 10:22:50 TimLaptop kernel: [   55.090460] usbcore: registered new interface driver usb-storage
Jan 13 10:22:51 TimLaptop kernel: [   56.090235] scsi 2:0:0:0: Direct-Access     Seagate  Expansion        0502 PQ: 0 ANSI: 6
Jan 13 10:22:51 TimLaptop kernel: [   56.090823] sd 2:0:0:0: Attached scsi generic sg1 type 0
Jan 13 10:22:51 TimLaptop kernel: [   56.099044] sd 2:0:0:0: [sdb] Spinning up disk...
Jan 13 10:24:28 TimLaptop kernel: [   57.102213] ....................................................................................................not responding...
Jan 13 10:24:28 TimLaptop kernel: [  156.579333] sd 2:0:0:0: [sdb] 1953525167 512-byte logical blocks: (1.00 TB/931 GiB)
Jan 13 10:24:35 TimLaptop kernel: [  163.511428] sd 2:0:0:0: [sdb] Test WP failed, assume Write Enabled
Jan 13 10:24:42 TimLaptop kernel: [  170.467446] sd 2:0:0:0: [sdb] Asking for cache data failed
Jan 13 10:24:42 TimLaptop kernel: [  170.467455] sd 2:0:0:0: [sdb] Assuming drive cache: write through
Jan 13 10:24:42 TimLaptop kernel: [  170.468829] sd 2:0:0:0: [sdb] Spinning up disk...
Jan 13 10:26:11 TimLaptop kernel: [  258.932881] JFS: nTxBlock = 8192, nTxLock = 65536
Jan 13 10:26:11 TimLaptop kernel: [  259.036899] SGI XFS with ACLs, security attributes, realtime, large block/inode numbers, no debug enabled
Jan 13 10:26:23 TimLaptop kernel: [  171.471086] ....................................................................................................not responding...
Jan 13 10:26:30 TimLaptop kernel: [  277.906429] sd 2:0:0:0: [sdb] Test WP failed, assume Write Enabled
Jan 13 10:26:36 TimLaptop kernel: [  284.862149] sd 2:0:0:0: [sdb] Asking for cache data failed
Jan 13 10:26:36 TimLaptop kernel: [  284.862157] sd 2:0:0:0: [sdb] Assuming drive cache: write through
Jan 13 10:29:53 TimLaptop kernel: [  481.651477] INFO: task kworker/u8:3:143 blocked for more than 120 seconds.
Jan 13 10:29:53 TimLaptop kernel: [  481.651486]       Not tainted 3.13.0-24-generic #46-Ubuntu
Jan 13 10:29:53 TimLaptop kernel: [  481.651488] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
Jan 13 10:29:53 TimLaptop kernel: [  481.651491] kworker/u8:3    D ffff88023fc94440     0   143      2 0x00000000
Jan 13 10:29:53 TimLaptop kernel: [  481.651503] Workqueue: events_unbound async_run_entry_fn
Jan 13 10:29:53 TimLaptop kernel: [  481.651506]  ffff88022e0f7a38 0000000000000002 ffff88022e0f8000 ffff88022e0f7fd8
Jan 13 10:29:53 TimLaptop kernel: [  481.651512]  0000000000014440 0000000000014440 ffff88022e0f8000 ffff88023fc94cd8
Jan 13 10:29:53 TimLaptop kernel: [  481.651517]  ffff88023ffaa4e8 ffff88022e0f7ac0 0000000000000002 ffffffff8114df10
Jan 13 10:29:53 TimLaptop kernel: [  481.651522] Call Trace:
Jan 13 10:29:53 TimLaptop kernel: [  481.651532]  [<ffffffff8114df10>] ? wait_on_page_read+0x60/0x60
Jan 13 10:29:53 TimLaptop kernel: [  481.651538]  [<ffffffff8171a1ad>] io_schedule+0x9d/0x140
Jan 13 10:29:53 TimLaptop kernel: [  481.651543]  [<ffffffff8114df1e>] sleep_on_page+0xe/0x20
Jan 13 10:29:53 TimLaptop kernel: [  481.651547]  [<ffffffff8171a738>] __wait_on_bit_lock+0x48/0xb0
Jan 13 10:29:53 TimLaptop kernel: [  481.651553]  [<ffffffff811f23a0>] ? blkdev_write_begin+0x30/0x30
Jan 13 10:29:53 TimLaptop kernel: [  481.651558]  [<ffffffff8114e02a>] __lock_page+0x6a/0x70
Jan 13 10:29:53 TimLaptop kernel: [  481.651563]  [<ffffffff810aaed0>] ? autoremove_wake_function+0x40/0x40
Jan 13 10:29:53 TimLaptop kernel: [  481.651568]  [<ffffffff811f23b8>] ? blkdev_readpage+0x18/0x20
Jan 13 10:29:53 TimLaptop kernel: [  481.651573]  [<ffffffff8114ee40>] do_read_cache_page+0x100/0x1a0
Jan 13 10:29:53 TimLaptop kernel: [  481.651578]  [<ffffffff8114ef19>] read_cache_page+0x19/0x30
Jan 13 10:29:53 TimLaptop kernel: [  481.651584]  [<ffffffff8134386d>] read_dev_sector+0x2d/0x90
Jan 13 10:29:53 TimLaptop kernel: [  481.651588]  [<ffffffff813445f0>] ? check_partition+0x240/0x240
Jan 13 10:29:53 TimLaptop kernel: [  481.651593]  [<ffffffff81344660>] adfspart_check_ICS+0x70/0x280
Jan 13 10:29:53 TimLaptop kernel: [  481.651599]  [<ffffffff81368bd9>] ? snprintf+0x39/0x40
Jan 13 10:29:53 TimLaptop kernel: [  481.651604]  [<ffffffff813445f0>] ? check_partition+0x240/0x240
Jan 13 10:29:53 TimLaptop kernel: [  481.651609]  [<ffffffff813444b8>] check_partition+0x108/0x240
Jan 13 10:29:53 TimLaptop kernel: [  481.651613]  [<ffffffff813440e4>] rescan_partitions+0xb4/0x2c0
Jan 13 10:29:53 TimLaptop kernel: [  481.651618]  [<ffffffff811f3714>] __blkdev_get+0x384/0x4c0
Jan 13 10:29:53 TimLaptop kernel: [  481.651622]  [<ffffffff811f3a15>] blkdev_get+0x1c5/0x340
Jan 13 10:29:53 TimLaptop kernel: [  481.651627]  [<ffffffff811d34f0>] ? unlock_new_inode+0x50/0x70
Jan 13 10:29:53 TimLaptop kernel: [  481.651632]  [<ffffffff811f2263>] ? bdget+0x133/0x150
Jan 13 10:29:53 TimLaptop kernel: [  481.651637]  [<ffffffff81341981>] add_disk+0x3a1/0x4b0
Jan 13 10:29:53 TimLaptop kernel: [  481.651642]  [<ffffffff8149b9b4>] ? __pm_runtime_use_autosuspend+0x54/0xa0
Jan 13 10:29:53 TimLaptop kernel: [  481.651649]  [<ffffffff814eb345>] sd_probe_async+0x135/0x200
Jan 13 10:29:53 TimLaptop kernel: [  481.651653]  [<ffffffff81091517>] async_run_entry_fn+0x37/0x130
Jan 13 10:29:53 TimLaptop kernel: [  481.651659]  [<ffffffff810838a2>] process_one_work+0x182/0x450
Jan 13 10:29:53 TimLaptop kernel: [  481.651664]  [<ffffffff81084641>] worker_thread+0x121/0x410
Jan 13 10:29:53 TimLaptop kernel: [  481.651668]  [<ffffffff81084520>] ? rescuer_thread+0x3e0/0x3e0
Jan 13 10:29:53 TimLaptop kernel: [  481.651673]  [<ffffffff8108b312>] kthread+0xd2/0xf0
Jan 13 10:29:53 TimLaptop kernel: [  481.651678]  [<ffffffff8108b240>] ? kthread_create_on_node+0x1d0/0x1d0
Jan 13 10:29:53 TimLaptop kernel: [  481.651683]  [<ffffffff8172637c>] ret_from_fork+0x7c/0xb0
Jan 13 10:29:53 TimLaptop kernel: [  481.651687]  [<ffffffff8108b240>] ? kthread_create_on_node+0x1d0/0x1d0

Mute Ant
Level 13
Level 13
Posts: 4926
Joined: Tue Sep 03, 2013 7:45 pm

Re: usb hdd not mounting (after it was dropped)

Post by Mute Ant » Sat Jan 13, 2018 12:55 pm

"Dropped about eight inches" But it's the landing that does the damage.

Drops 8 inches and stops in 1/8 inch on a carpet -----> 64gn -----> Good chance of survival.

Drops 8 inches and stops in 1/80 inch on a desktop ------> 640gn -----> Candidate for the bits-box.

With /dev/sdb visible, the electronics appears to have survived, but there's no sign of any medium for it to read.
2018-10-23 Rock on Tommy productions presents the Librarian Chorus in Here Comes the Bride...
Ook ook ook ook: Ook ook ook ook: Ook ook ook ook ook: Ook ook ook ook.

Neil Edmond
Level 5
Level 5
Posts: 886
Joined: Thu Dec 26, 2013 10:19 am
Location: N.E. AR USA

Re: usb hdd not mounting (after it was dropped)

Post by Neil Edmond » Sat Jan 13, 2018 2:53 pm

Was this disk powered up and operating when dropped? If so, that would almost certainly damage it.

Post Reply

Return to “Hardware Support”