General Help & Advice > Hardware Compatibility

External SATA-USB hard drive keeps disconnecting

(1/4) > >>

haughtonomous:
I have this wierd problem that I don't understand. I have been using an external SATA hard drive in a USB caddy for backups. It's been fine for years. Recently it started not auto-mounting when I plugged it in, and making a funny sort of repetitive 'restarting' noise, sounding as if the head was sticking somewhere. Not always, but enough to be annoying. I thought it had gone west and I bought a brand new replacement, with a new caddy too, but that has the same problem so it looks like it isn't either drive nor the caddies themselves. The system log shows the drive mounting and then being disconnected - the log extract is below. Can anyone throw some light on what is gong wrong?

Linux Mint 18.3, Kernel 4.15.0-106-generic #107~16.04.1-Ubuntu SMP Thu Jun 4 15:40:05 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux

Gigabyte board, 8GB memory, USB2 ports.

The log extract (this repeats endlessly until the drive is physically disconnected, with the device number incrementing each time):

Jun 28 17:09:59 study kernel: [ 505.967378] usb 2-1.1: new high-speed USB device number 26 using ehci-pci
Jun 28 17:09:59 study kernel: [ 506.080235] usb 2-1.1: New USB device found, idVendor=152d, idProduct=2329
Jun 28 17:09:59 study kernel: [ 506.080237] usb 2-1.1: New USB device strings: Mfr=1, Product=2, SerialNumber=5
Jun 28 17:09:59 study kernel: [ 506.080238] usb 2-1.1: Product: USB to ATA/ATAPI Bridge
Jun 28 17:09:59 study kernel: [ 506.080238] usb 2-1.1: Manufacturer: JMicron
Jun 28 17:09:59 study kernel: [ 506.080239] usb 2-1.1: SerialNumber: D61A3188123F
Jun 28 17:09:59 study kernel: [ 506.080791] usb-storage 2-1.1:1.0: USB Mass Storage device detected
Jun 28 17:09:59 study kernel: [ 506.080935] usb-storage 2-1.1:1.0: Quirks match for vid 152d pid 2329: 8020
Jun 28 17:09:59 study kernel: [ 506.081123] scsi host5: usb-storage 2-1.1:1.0
Jun 28 17:09:59 study mtp-probe: checking bus 2, device 26: "/sys/devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.1"
Jun 28 17:09:59 study mtp-probe: bus: 2, device: 26 was not an MTP device
Jun 28 17:10:00 study kernel: [ 507.108047] scsi 5:0:0:0: Direct-Access WDC WD50 00BPVT-00HXZT1 PQ: 0 ANSI: 2 CCS
Jun 28 17:10:00 study kernel: [ 507.108667] sd 5:0:0:0: Attached scsi generic sg7 type 0
Jun 28 17:10:00 study kernel: [ 507.109767] sd 5:0:0:0: [sdg] 976773168 512-byte logical blocks: (500 GB/466 GiB)
Jun 28 17:10:00 study kernel: [ 507.111955] sd 5:0:0:0: [sdg] Write Protect is off
Jun 28 17:10:00 study kernel: [ 507.111957] sd 5:0:0:0: [sdg] Mode Sense: 34 00 00 00
Jun 28 17:10:00 study kernel: [ 507.112987] sd 5:0:0:0: [sdg] Write cache: disabled, read cache: enabled, doesn't support DPO or FUA
Jun 28 17:10:00 study kernel: [ 507.152508] sd 5:0:0:0: [sdg] Attached SCSI disk
Jun 28 17:10:01 study kernel: [ 508.024133] usb 2-1.1: USB disconnect, device number 26
Jun 28 17:10:01 study kernel: [ 508.028261] scsi 5:0:0:0: rejecting I/O to offline device
Jun 28 17:10:01 study kernel: [ 508.028266] scsi 5:0:0:0: [sdg] killing request
Jun 28 17:10:01 study kernel: [ 508.028283] scsi 5:0:0:0: [sdg] FAILED Result: hostbyte=DID_NO_CONNECT driverbyte=DRIVER_OK
Jun 28 17:10:01 study kernel: [ 508.028286] scsi 5:0:0:0: [sdg] CDB: Read(10) 28 00 00 00 10 00 00 00 08 00
Jun 28 17:10:01 study kernel: [ 508.028287] print_req_error: I/O error, dev sdg, sector 4096
Jun 28 17:10:01 study kernel: [ 508.028356] Buffer I/O error on dev sdg, logical block 512, async page read
Jun 28 17:10:01 study systemd-udevd[3586]: inotify_add_watch(9, /dev/sdg, 10) failed: No such file or directory
Jun 28 17:10:03 study colord-sane: io/hpmud/pp.c 627: unable to read device-id ret=-1

Also I notice that it is reported as /dev/sdg, but my internal drives are /dev/sda and /dev/sdb. Should this not be /dev/sdc? is that significant?

Keith:
Hello haughtonomous - and welcome to the Forum.

Although Mint 20 is the latest version, Mint 18 is still supported, so that can't be your problem.
I'm a bit (= very) out of my depth on this one, but you might find some ideas here: https://unix.stackexchange.com/questions/136812/prevent-usb-storage-from-using-different-device-on-reset and others might respond with better advice.

Keith

[EDIT] ...and this might offer some guidance on MTP (Micro$oft, apparently!) https://en.wikipedia.org/wiki/Media_Transfer_Protocol

haughtonomous:
Keith, thank you for the response. I'm like you, out of my depth on this sort of thing. That article has a log extract that looks remarkably like mine, so it looks like I am suffering from a USB Disconnect action instead of a USB Reset action, but I am puzzled as to why this is occurring. This is the Mint automount at work when I plug in the external drive and according to the log the drive remains connected:


--- Quote ---[sdg] Attached SCSI disk
--- End quote ---

for a little under one second, until this is logged:


--- Quote ---usb 2-1.1: USB disconnect, device number 26
--- End quote ---

What could be causing that to be happening? Is it possible that a kernel update (I have been installing every new kernel update as they are available via the Update Manager tool) has caused this? Could it be that the latest kernel no longer works with my hardware (which is now a good few years old) and I should be reverting to increasingly earlier kernels, until the problem stops?

Rich J:

--- Quote from: haughtonomous on June 29, 2020, 10:28:24 pm ---Keith, thank you for the response. I'm like you, out of my depth on this sort of thing. That article has a log extract that looks remarkably like mine, so it looks like I am suffering from a USB Disconnect action instead of a USB Reset action, but I am puzzled as to why this is occurring. This is the Mint automount at work when I plug in the external drive and according to the log the drive remains connected:


--- Quote ---[sdg] Attached SCSI disk
--- End quote ---

for a little under one second, until this is logged:


--- Quote ---usb 2-1.1: USB disconnect, device number 26
--- End quote ---

What could be causing that to be happening? Is it possible that a kernel update (I have been installing every new kernel update as they are available via the Update Manager tool) has caused this? Could it be that the latest kernel no longer works with my hardware (which is now a good few years old) and I should be reverting to increasingly earlier kernels, until the problem stops?

--- End quote ---

Hi haughtonomous, and a belated welcome from me!

This is very often a good move in cases where a previously working distro suddenly 'plays up' possibly due to a conflict with the new kernel.  If you revert to a known working kernel, (often the one before) and the problem disappears, then the issue is resolved immediately.  It's then a matter of waiting until the conflicting software 'catches up' or a patch is found and then the new kernel can be utilised.  It is rarely a problem to wait a while for this to happen, other than for a security threat - very rare in Linux.

Hope this helps,

Rich
 

Keith:
Rich,

If it's been a bug in Mint, then perhaps Mint 20 has indeed "caught up".  If so, then creating a Live USB of Mint 20 might show if that's been the problem.  What do you think?

Keith

Navigation

[0] Message Index

[#] Next page

Go to full version