You are not logged in.
Hi!
I'm using Archlinux on a Dell Inspiron N5110.
I'm having problems with my external HDD. It works flawlessly, but when I have to reboot the system, it stops working. I have to unplug and plug it again to be able to mount it.
It wouldn't be a major problem if I wasn't using my laptop as a plex server. Today doing a system upgrade via ssh I had to reboot it because docker couldn't create bridged networks with a new installed kernel not applied yet, and after the reboot, the drive is gone.
I can't see it in 'lsblk' neither 'lsusb -t'.
The obvious solution is wait until coming home and do the replug, but it's annoying, and I feel that it should just work.
I don't know if it's related to the use of a USB 3.0 port. I'll try at home if a 2.0 port do the same.
Some outputs:
$ uname -r
4.20.7-arch1-1-ARCH
$ lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
sda 8:0 0 111.8G 0 disk
├─sda1 8:1 0 200M 0 part /boot
├─sda2 8:2 0 55G 0 part /
├─sda3 8:3 0 55G 0 part
└─sda4 8:4 0 1.5G 0 part [SWAP]
sdb 8:16 0 931.5G 0 disk
└─sdb1 8:17 0 931.5G 0 part /data
$ lsusb -t
/: Bus 04.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/2p, 5000M
/: Bus 03.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/2p, 480M
|__ Port 1: Dev 2, If 0, Class=Hub, Driver=hub/8p, 480M
|__ Port 2: Dev 3, If 0, Class=Human Interface Device, Driver=usbhid, 1.5M
|__ Port 2: Dev 3, If 1, Class=Human Interface Device, Driver=usbhid, 1.5M
/: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/2p, 480M
/: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/2p, 480M
|__ Port 1: Dev 2, If 0, Class=Hub, Driver=hub/6p, 480M
|__ Port 4: Dev 3, If 0, Class=Wireless, Driver=btusb, 12M
|__ Port 4: Dev 3, If 1, Class=Wireless, Driver=btusb, 12M
|__ Port 5: Dev 4, If 0, Class=Video, Driver=uvcvideo, 480M
|__ Port 5: Dev 4, If 1, Class=Video, Driver=uvcvideo, 480MNote: /dev/sdb is the internal drive. The usb one appears as /dev/sdc when it's working
I hope someone knows why is this happening. I'll be glad to post other logs that you could find useful. ![]()
Last edited by alomsimoy (2019-02-12 14:48:38)
Offline
Probably its happening because of a bug in device or USB controller firmware ![]()
Does the same happen if you shutdown and power up again? Maybe cold reboot would help, some PCs implement it quite faithfully by actually power-cycling the whole machine. Add reboot=cold to kernel parameters, reboot, check with cat /proc/cmdline if it has been applied and then reset again to see if the disk works right this time.
Offline