Having problems with External Hard Drives on my Laptop

InsidiousMind · 2015-04-04 16:20:01

Ever since using linux i've always had the same problem. Whenever i connect a hard-drive, it keeps disconnecting/ spitting input-ouptut errors.
I thought it was because of the hard-drive failing, which turned out to be the problem with my last two, but i'm using another one (Seagate MomentusXT 500GB) and i'm getting the same problem.
I had just reformatted this hard drive from NTFS to Ext4 using Gparted, so maybe that's the problem? I'm really kind of lost.

I mount my HDD like this:
sudo mount /dev/sdd1 /mnt/usb

and unmount like this:
sudo umount /mnt/usb

It connects initially, and i'm able to put stuff onto it. I was able to put a whole TV series on it successfully, but when i tried copying my music onto it it failed and alot of the music didn't copy, giving me these errors:

ile system
cp: cannot create directory ‘/mnt/usb/music/Clawfinger’: Read-only file system
cp: cannot create directory ‘/mnt/usb/music/Cake’: Read-only file system
cp: cannot create directory ‘/mnt/usb/music/The Glitch Mob - Discography’: Read-only file system
cp: cannot create directory ‘/mnt/usb/music/Bastille - Bad Blood (The Extended Cut)’: Read-only file system
cp: cannot create directory ‘/mnt/usb/music/ARCTIC MONKEYS - DISCOGRAPHY (2005-13) [CHANNEL NEO]’: Read-only file system
cp: cannot create directory ‘/mnt/usb/music/NIRVANA DISCOGRAPHY @320Kbps CbR Mp3 [TuGAZx]’: Read-only file system
cp: cannot create directory ‘/mnt/usb/music/The Doors - STUDIO DISCOGRAPHY’: Read-only file system
cp: cannot create directory ‘/mnt/usb/music/Tiesto - Red Lights (2014.Dance)’: Read-only file system
cp: cannot create directory ‘/mnt/usb/music/Tiesto - A Town Called Paradise (Deluxe Edition) 2014 320kbps CBR MP3 [VX]’: Read-only file system
cp: cannot create directory ‘/mnt/usb/music/Daft Punk - Discography - 1994-2013’: Read-only file system
cp: cannot create directory ‘/mnt/usb/music/Pink_Floyd_Greatest_Hits’: Read-only file system
cp: cannot create directory ‘/mnt/usb/music/Calvin Harris - Discography - 2007-2013’: Read-only file system
cp: cannot create directory ‘/mnt/usb/music/Weezer [Discography]’: Read-only file system
cp: cannot create directory ‘/mnt/usb/music/MGMT’: Read-only file system
cp: cannot create directory ‘/mnt/usb/music/Blackmill’: Read-only file system
cp: cannot create directory ‘/mnt/usb/music/Avicii - Discography’: Read-only file system
cp: cannot create directory ‘/mnt/usb/music/Zedd’: Read-only file system
cp: preserving times for ‘/mnt/usb/music’: Read-only file system

I can then unmount and mount the HDD again, and try again, but i keep getting the same problem.

Here's my dmesg:

[22951.444217] usb 1-1: reset high-speed USB device number 19 using xhci_hcd
[22966.616452] usb 1-1: device descriptor read/64, error -110
[22981.892003] usb 1-1: device descriptor read/64, error -110
[22982.155518] usb 1-1: reset high-speed USB device number 19 using xhci_hcd
[22997.327767] usb 1-1: device descriptor read/64, error -110
[23012.603571] usb 1-1: device descriptor read/64, error -110
[23012.867002] usb 1-1: reset high-speed USB device number 19 using xhci_hcd
[23017.881048] xhci_hcd 0000:00:14.0: Command completion event does not match command
[23017.881078] xhci_hcd 0000:00:14.0: Timeout while waiting for setup device command
[23023.098593] xhci_hcd 0000:00:14.0: Timeout while waiting for setup device command
[23023.302055] usb 1-1: device not accepting address 19, error -62
[23023.462289] usb 1-1: reset high-speed USB device number 19 using xhci_hcd
[23028.476297] xhci_hcd 0000:00:14.0: Command completion event does not match command
[23028.476314] xhci_hcd 0000:00:14.0: Timeout while waiting for setup device command
[23033.693797] xhci_hcd 0000:00:14.0: Timeout while waiting for setup device command
[23033.897336] usb 1-1: device not accepting address 19, error -62
[23033.897435] usb 1-1: USB disconnect, device number 19
[23033.903973] sd 10:0:0:0: [sdd] UNKNOWN Result: hostbyte=0x01 driverbyte=0x00
[23033.903976] sd 10:0:0:0: [sdd] CDB: 
[23033.903977] cdb[0]=0x2a: 2a 00 03 90 e5 10 00 00 f0 00
[23033.903982] blk_update_request: I/O error, dev sdd, sector 59827472
[23033.903985] EXT4-fs warning (device sdd1): ext4_end_bio:317: I/O error -5 writing to inode 16777759 (offset 0 size 8388608 starting block 7478464)
[23033.903987] buffer_io_error: 4990 callbacks suppressed
[23033.903988] Buffer I/O error on device sdd1, logical block 7478178
[23033.903990] Buffer I/O error on device sdd1, logical block 7478179
[23033.903991] Buffer I/O error on device sdd1, logical block 7478180
[23033.903992] Buffer I/O error on device sdd1, logical block 7478181
[23033.903993] Buffer I/O error on device sdd1, logical block 7478182
[23033.903994] Buffer I/O error on device sdd1, logical block 7478183
[23033.903995] Buffer I/O error on device sdd1, logical block 7478184
[23033.903996] Buffer I/O error on device sdd1, logical block 7478185
[23033.903997] Buffer I/O error on device sdd1, logical block 7478186
[23033.903998] Buffer I/O error on device sdd1, logical block 7478187
[23033.904015] EXT4-fs warning (device sdd1): ext4_end_bio:317: I/O error -5 writing to inode 16777759 (offset 0 size 8388608 starting block 7478524)
[23033.904027] EXT4-fs warning (device sdd1): ext4_end_bio:317: I/O error -5 writing to inode 16777759 (offset 0 size 8388608 starting block 7478554)
[23033.904050] EXT4-fs warning (device sdd1): ext4_end_bio:317: I/O error -5 writing to inode 16777759 (offset 0 size 8388608 starting block 7478584)
[23033.904066] EXT4-fs warning (device sdd1): ext4_end_bio:317: I/O error -5 writing to inode 16777759 (offset 0 size 8388608 starting block 7478614)
[23033.904080] EXT4-fs warning (device sdd1): ext4_end_bio:317: I/O error -5 writing to inode 16777759 (offset 0 size 8388608 starting block 7478644)
[23033.904095] EXT4-fs warning (device sdd1): ext4_end_bio:317: I/O error -5 writing to inode 16777759 (offset 0 size 8388608 starting block 7478674)
[23033.904110] EXT4-fs warning (device sdd1): ext4_end_bio:317: I/O error -5 writing to inode 16777759 (offset 0 size 8388608 starting block 7478704)
[23033.904124] EXT4-fs warning (device sdd1): ext4_end_bio:317: I/O error -5 writing to inode 16777759 (offset 0 size 8388608 starting block 7478734)
[23033.904139] EXT4-fs warning (device sdd1): ext4_end_bio:317: I/O error -5 writing to inode 16777759 (offset 0 size 8388608 starting block 7478764)
[23033.905630] sd 10:0:0:0: [sdd] UNKNOWN Result: hostbyte=0x01 driverbyte=0x00
[23033.905632] sd 10:0:0:0: [sdd] CDB: 
[23033.905633] cdb[0]=0x2a: 2a 00 03 90 e6 00 00 00 f0 00
[23033.905639] blk_update_request: I/O error, dev sdd, sector 59827712
[23033.906165] Aborting journal on device sdd1-8.
[23033.906176] JBD2: Error -5 detected when updating journal superblock for sdd1-8.
[23033.906270] EXT4-fs (sdd1): Delayed block allocation failed for inode 16777761 at logical offset 0 with max blocks 2048 with error 30
[23033.906272] EXT4-fs (sdd1): This should not happen!! Data will be lost

[23033.906276] EXT4-fs error (device sdd1) in ext4_writepages:2395: Journal has aborted
[23033.906793] EXT4-fs (sdd1): previous I/O error to superblock detected
[23033.906801] EXT4-fs error (device sdd1): ext4_journal_check_start:56: Detected aborted journal
[23033.906802] EXT4-fs (sdd1): Remounting filesystem read-only
[23033.906803] EXT4-fs (sdd1): previous I/O error to superblock detected
[23033.906808] EXT4-fs (sdd1): ext4_writepages: jbd2_start: 9223372036854775807 pages, ino 16777762; err -30
[23033.907641] EXT4-fs error (device sdd1): ext4_find_entry:1289: inode #16515073: comm cp: reading directory lblock 0
[23033.907644] EXT4-fs (sdd1): previous I/O error to superblock detected
[23033.907690] EXT4-fs error (device sdd1): ext4_find_entry:1289: inode #16515073: comm cp: reading directory lblock 0
[23033.907692] EXT4-fs (sdd1): previous I/O error to superblock detected
[23033.907736] EXT4-fs error (device sdd1): ext4_find_entry:1289: inode #16515073: comm cp: reading directory lblock 0
[23033.907738] EXT4-fs (sdd1): previous I/O error to superblock detected
[23033.907771] EXT4-fs error (device sdd1): ext4_find_entry:1289: inode #16515073: comm cp: reading directory lblock 0
[23033.907773] EXT4-fs (sdd1): previous I/O error to superblock detected
[23033.907805] EXT4-fs error (device sdd1): ext4_find_entry:1289: inode #16515073: comm cp: reading directory lblock 0
[23033.907845] EXT4-fs error (device sdd1): ext4_find_entry:1289: inode #16515073: comm cp: reading directory lblock 0
[23033.907886] EXT4-fs error (device sdd1): ext4_find_entry:1289: inode #16515073: comm cp: reading directory lblock 0
[23033.907919] EXT4-fs error (device sdd1): ext4_find_entry:1289: inode #16515073: comm cp: reading directory lblock 0
[23033.907947] EXT4-fs error (device sdd1): ext4_find_entry:1289: inode #16515073: comm cp: reading directory lblock 0
[23034.490498] xhci_hcd 0000:00:14.0: xHCI xhci_drop_endpoint called with disabled ep ffff880225074480
[23034.490502] xhci_hcd 0000:00:14.0: xHCI xhci_drop_endpoint called with disabled ep ffff8802250744c8
[23220.391199] usb 1-1: new high-speed USB device number 54 using xhci_hcd
[23235.563509] usb 1-1: device descriptor read/64, error -110
[23250.839126] usb 1-1: device descriptor read/64, error -110
[23251.102653] usb 1-1: new high-speed USB device number 55 using xhci_hcd
[23266.274917] usb 1-1: device descriptor read/64, error -110
[23281.550616] usb 1-1: device descriptor read/64, error -110
[23281.814174] usb 1-1: new high-speed USB device number 56 using xhci_hcd
[23286.831502] xhci_hcd 0000:00:14.0: Command completion event does not match command
[23286.831579] xhci_hcd 0000:00:14.0: Timeout while waiting for setup device command
[23292.049048] xhci_hcd 0000:00:14.0: Timeout while waiting for setup device command
[23292.252556] usb 1-1: device not accepting address 56, error -62
[23292.412732] usb 1-1: new high-speed USB device number 57 using xhci_hcd
[23297.426714] xhci_hcd 0000:00:14.0: Command completion event does not match command
[23297.426728] xhci_hcd 0000:00:14.0: Timeout while waiting for setup device command
[23302.644273] xhci_hcd 0000:00:14.0: Timeout while waiting for setup device command
[23302.847753] usb 1-1: device not accepting address 57, error -62
[23302.847781] usb usb1-port1: unable to enumerate USB device

Anyone know how to fix this?

wtx · 2015-04-04 16:41:00

Is your disk controller USB 3.x or USB 2.0?
You may try to disable xhci_hcd module in your system and use ehci_hcd driver and of course check with fsck sdd1 partition.

ewaller · 2015-04-04 17:00:41

There is a whole lot of bad going on there.

There are problems both drive errors and USB errors. I don't believe it.
I have a hunch the drive is starving for power.
USB devices are supposed to function all the way down to 4.25V. Not all do.
USB ports are supposed to be able to deliver 4.25V at the end of the cable at 500mA. Not all do.
USB 2.0 devices are not supposed to draw more than 100mA unless they negotiate for more. Some violate that.
USB 2.0 devices are never supposed to draw more than 500mA. Some violate that. Especially disk drives.

My guess is that your drive is drawing excess current and the voltage drop through the port and cable are dropping you below 4.25; or at least below the voltage that your drive goes "Tango Uniform"[1]. Does your drive have the option for external power? If so try it. Following up on wtx's comment; USB 3.0 is capable of delivering more power. Also, some drives have used a cable that violates just about every aspect of the USB specification: A "Y" cable that plugs into two host ports to provide more power to the guest. I despise this solution with every fiber of my electrical engineering existence; never-the-less, you might try one.

edit: [1] Teats Up.

Last edited by ewaller (2015-04-04 17:02:04)

InsidiousMind · 2015-04-18 16:58:41

It seems that the Drive only works with certain USB cables, which leads me to believe ewaller was correct.

It only works with one specfic USB cable and uses xhci_hcd module for my USB2.0 device plugged into my USB2.0 port. if I switch the controller on the drive to USB3.0 it doesn't work, if i switch the USB cable it also doesn't work.
I do have an external power option on my HDD, but having another cable to connect to my wall is just ridiculous. Also, I only have 2 USB ports on my system, on seperate sides of the machine. A cable which uses both of those up for power makes me want to cringe.
Kind of odd. I used to have a SSD, which worked much better with Linux and this computer, but it was old and ran out of writes. I guess i'll just have to live with this until I get another SSD *sigh*.

R00KIE · 2015-04-18 20:52:52

Just want to add something else to what ewaller said, although we are not seeing the whole picture here (full dmesg output) another guess would be that your drive(1) needs some quirk to operate without problems.

We see a device reset and then some I/O errors, these errors might be caused by the device reset. I would try disabling UAS(2) and see if you still have problems. If disabling UAS solves the problem then you should report this upstream so the proper quirk can be added to the kernel, otherwise ewaller hit the nail on the head.

(1) Not the disk drive itself but the bridge chip inside the enclosure.
(2) You say the drive is USB3 so I assume the kernel will try to use UAS. You can disable it by passing some options to the usb-storage module, create /etc/modprobe.d/usb-storage.conf and put this inside:

options usb-storage quirks=vid:pid:u

where vid and pid are the vendor and product ids you get on the output of lsusb.

Arch Linux

#1 2015-04-04 16:20:01

Having problems with External Hard Drives on my Laptop

#2 2015-04-04 16:41:00

Re: Having problems with External Hard Drives on my Laptop

#3 2015-04-04 17:00:41

Re: Having problems with External Hard Drives on my Laptop

#4 2015-04-18 16:58:41

Re: Having problems with External Hard Drives on my Laptop

#5 2015-04-18 20:52:52

Re: Having problems with External Hard Drives on my Laptop

Board footer