External hard drive not detected with lsblk

sanuqe7 · 2024-05-26 18:41:34

Hi,
I've been using arch for some time now but I'm still not very good at it, so I'm sorry if I forgot something stupid. So I have an external HDD and when I plug it in the light lights up but if I run lsblk it doesn't show up. If i run lsusb immediately after plugging it in it shows up in that but if I wait a few seconds and run lsusb again it goes away. I've also already had problems with this drive when it refused to format and I got angry and unplugged it which was very stupid, so I think it is corrupted and gdisk had also confirmed that MBR is corrupted before the drive stopped showing up on lsblk all together.
this is the output of dmesg:

[23674.374874] usb 2-1: new SuperSpeed USB device number 13 using xhci_hcd
[23674.392333] usb 2-1: New USB device found, idVendor=1058, idProduct=2622, bcdDevice=10.23
[23674.392349] usb 2-1: New USB device strings: Mfr=2, Product=3, SerialNumber=1
[23674.392357] usb 2-1: Product: Elements SE 2622
[23674.392362] usb 2-1: Manufacturer: Western Digital
[23674.392367] usb 2-1: SerialNumber: 575858324538313438344341
[23674.394848] usb-storage 2-1:1.0: USB Mass Storage device detected
[23674.395358] scsi host1: usb-storage 2-1:1.0
[23675.422797] scsi 1:0:0:0: Direct-Access     WD       Elements SE 2622 1023 PQ: 0 ANSI: 6
[23675.423428] scsi 1:0:0:1: Enclosure         WD       SES Device       1023 PQ: 0 ANSI: 6
[23675.428331] ses 1:0:0:1: Attached Enclosure device
[23675.429739] sd 1:0:0:0: [sda] Spinning up disk...
[23675.430019] ses 1:0:0:1: Wrong diagnostic page; asked for 1 got 8
[23675.430021] ses 1:0:0:1: Failed to get diagnostic page 0x1
[23675.430023] ses 1:0:0:1: Failed to bind enclosure -19
[23676.434770] ..ready
[23714.061588] xhci_hcd 0000:00:14.0: Timeout while waiting for setup device command
[23719.394729] xhci_hcd 0000:00:14.0: Timeout while waiting for setup device command
[23719.601464] usb 2-1: device not accepting address 13, error -62
[23724.941476] xhci_hcd 0000:00:14.0: Timeout while waiting for setup device command
[23730.274893] xhci_hcd 0000:00:14.0: Timeout while waiting for setup device command
[23730.481471] usb 2-1: device not accepting address 13, error -62
[23735.821471] xhci_hcd 0000:00:14.0: Timeout while waiting for setup device command
[23741.154903] xhci_hcd 0000:00:14.0: Timeout while waiting for setup device command
[23741.361438] usb 2-1: device not accepting address 13, error -62
[23746.701521] xhci_hcd 0000:00:14.0: Timeout while waiting for setup device command
[23752.034548] xhci_hcd 0000:00:14.0: Timeout while waiting for setup device command
[23752.241488] usb 2-1: device not accepting address 13, error -62
[23752.256590] usb 2-1: USB disconnect, device number 13
[23752.256635] sd 1:0:0:0: [sda] 3906963456 512-byte logical blocks: (2.00 TB/1.82 TiB)
[23752.268160] sd 1:0:0:0: [sda] Write Protect is off
[23752.268170] sd 1:0:0:0: [sda] Mode Sense: 00 00 00 00
[23752.268185] sd 1:0:0:0: [sda] Asking for cache data failed
[23752.268189] sd 1:0:0:0: [sda] Assuming drive cache: write through
[23752.268738] sd 1:0:0:0: [sda] Attached SCSI disk
[23757.581490] xhci_hcd 0000:00:14.0: Timeout while waiting for setup device command
[23762.914843] xhci_hcd 0000:00:14.0: Timeout while waiting for setup device command
[23763.121416] usb 2-1: device not accepting address 14, error -62
[23768.461458] xhci_hcd 0000:00:14.0: Timeout while waiting for setup device command
[23773.794863] xhci_hcd 0000:00:14.0: Timeout while waiting for setup device command
[23774.001469] usb 2-1: device not accepting address 15, error -62
[23774.008232] usb usb2-port1: attempt power cycle
[23779.981510] xhci_hcd 0000:00:14.0: Timeout while waiting for setup device command
[23785.314863] xhci_hcd 0000:00:14.0: Timeout while waiting for setup device command
[23785.521461] usb 2-1: device not accepting address 16, error -62
[23790.861449] xhci_hcd 0000:00:14.0: Timeout while waiting for setup device command
[23796.194797] xhci_hcd 0000:00:14.0: Timeout while waiting for setup device command
[23796.401414] usb 2-1: device not accepting address 17, error -62
[23796.407974] usb usb2-port1: unable to enumerate USB device

Any help would be much appreciated and sorry in advance if I just made a stupid mistake.
ps. my system is fully up to date and restarted
THANK YOU IN ADVANCED!

Last edited by sanuqe7 (2024-05-26 19:07:16)

ewaller · 2024-05-26 21:09:14

The state of drive corruption won't (asserted without proof) impact the visibility of the device on the USB bus. That it is falling off the bus leads me to believe the problem has to do with the drive drawing more power than that which was negotiated when the USB connection was established. Check your journal and look for entries around the time the drive falls off the bus. The logs you provided seem to have 40 second time gap.

Is this a spinning drive? The log seems to indicate it is. It is common for the drive to draw a great deal of current when the spindle motor starts from a stall.

seth · 2024-05-26 21:23:48

That's not a problem w/ the partition table - the device doesn't respond properly.
Do you have the same problem w/ the LTS kernel?
Have you tried other USB ports? Does the drive use a Y-cable?
Does the disk work when attaching it to some other computer?

Edit: F5…

Last edited by seth (2024-05-26 21:24:20)

ewaller · 2024-05-26 21:33:27

sanuqe7, Seth and seem to be on the same page here. The question about a 'Y' cable has to do with drive power. A 'Y' cable allows the use of two ports to suck power from the host.

sanuqe7 · 2024-05-27 04:03:58

Hi,
I've checked the logs again but there is nothing different, when I plug the HDD in it starts spinning (I can feel it) and than it says ready on the logs and the drive keeps on spinning indefinitely although it still isn't detected. I've not checked yet with the LTS I can do that in the afternoon but I have tried all ports in my laptop and they all work with other usb-s. I do not use a Y-cable I think it is just usb-A to some Western Digital proprietary connector. I've tried using the disk in another computer running windows but there it is detected as a damaged drive.

Last edited by sanuqe7 (2024-05-27 04:05:24)

seth · 2024-05-27 06:48:36

If the LTS kernel doesn't help (there's https://bbs.archlinux.org/viewtopic.php … 1#p2173651 but that doesn't really fit your provided logs, however drives might respond weirdly to "bad" commands) and this is a notebook make sure to test the behavior on external power supply and see whether there're USB features in the UEFI settings (afair lenovo ha some "eternal on usb" thing that allows for charging during S3 etc. and also end up putting more power on the selected port) - also remove all external usb devices that are not strictly necesary for operation.

This is mostly relevant for forementioned Y-cables, but might have impact here: attach the cable to the host first and the disk afterwards intead of plugging the wired disk into the host.
Also pay attention to the drive orientation - eg. operating it upside down would not be helpful either but also sometimes found vertical orientation can demand more spinning power.

Ultimately you can buy usb hubs w/ external power supply (if this is a power supply issue and the drive isn't maybe just dying)

If you need to fix the MBR w/o just formating the device you could try to boot grml on the other (windows) system where the disk apparently shows up and use it to fix it there.
I'd be surprised if that has any impact on the device responding on the system where it's currently not responding.

sanuqe7 · 2024-05-27 16:42:00

Hi, I've tried the LTS kernel but it still doesn't work. I've also asked a computer guy I know for an opinion and he said that it's probably hardware damage, so if no one has any other ideas I think I'll just see if the warranty is still in order and get another one.
Thanks everyone for help, I was honestly blown away by the response time so thank you seth and ewaller a lot!

seth · 2024-05-27 16:49:19

seth wrote:

If you need to fix the MBR w/o just formating the device you could try to boot grml on the other (windows) system where the disk apparently shows up and use it to fix it there.

but if the drive no longer shows up on that system either, the controller might have been fried.

sanuqe7 · 2024-05-27 17:47:12

Yeah I forgot to mention the drive only shows up on windows under device management and not under disk management and also it is still under warranty and I don't really have any important data on it, but thanks anyways!

Arch Linux

#1 2024-05-26 18:41:34

External hard drive not detected with lsblk

#2 2024-05-26 21:09:14

Re: External hard drive not detected with lsblk

#3 2024-05-26 21:23:48

Re: External hard drive not detected with lsblk

#4 2024-05-26 21:33:27

Re: External hard drive not detected with lsblk

#5 2024-05-27 04:03:58

Re: External hard drive not detected with lsblk

#6 2024-05-27 06:48:36

Re: External hard drive not detected with lsblk

#7 2024-05-27 16:42:00

Re: External hard drive not detected with lsblk

#8 2024-05-27 16:49:19

Re: External hard drive not detected with lsblk

#9 2024-05-27 17:47:12

Re: External hard drive not detected with lsblk

Board footer