USB HDD Problems

I’m using an external USB SSD as my main storage (mounted at /media/ext_storage ), and I keep having issues writing to the external drive (Buffer I/O error).

I’ve tested the drive and external enclosure with other computers (this was used with an x86 libreelec box) and have no problems. My only problem is using the drive with the Odroid N2 under core elec.

This is the output of dmesg coming during the error:
235837.535164@3] usb 2-1.4: USB disconnect, device number 3
[235837.535320@5] blk_update_request: I/O error, dev sda, sector 1475229920
[235837.535330@5] EXT4-fs warning (device sda2): ext4_end_bio:313: I/O error -5 writing to inode 46006410 (offset 24211456 size 364544 starting block 184403829)
[235837.535334@5] Buffer I/O error on device sda2, logical block 184352535
[235837.535345@5] Buffer I/O error on device sda2, logical block 184352536
[235837.535347@5] Buffer I/O error on device sda2, logical block 184352537
[235837.535349@5] Buffer I/O error on device sda2, logical block 184352538
[235837.535352@5] Buffer I/O error on device sda2, logical block 184352539
[235837.535354@5] Buffer I/O error on device sda2, logical block 184352540
[235837.535356@5] Buffer I/O error on device sda2, logical block 184352541
[235837.535357@5] Buffer I/O error on device sda2, logical block 184352542
[235837.535359@5] Buffer I/O error on device sda2, logical block 184352543
[235837.535361@5] Buffer I/O error on device sda2, logical block 184352544
[235837.535630@0] blk_update_request: I/O error, dev sda, sector 1475380296
[235837.535642@0] EXT4-fs warning (device sda2): ext4_end_bio:313: I/O error -5 writing to inode 46006410 (offset 25706496 size 405504 starting block 184422636)
[235837.535872@1] blk_update_request: I/O error, dev sda, sector 812691672
[235837.535878@1] EXT4-fs warning (device sda2): ext4_end_bio:313: I/O error -5 writing to inode 46006342 (offset 0 size 4096 starting block 101586460)
[235837.538388@2] JBD2: Detected IO errors while flushing file data on sda2-8
[235837.538397@2] blk_update_request: I/O error, dev sda, sector 936038776
[235837.538443@2] Aborting journal on device sda2-8.
[235837.538450@2] blk_update_request: I/O error, dev sda, sector 936001576
[235837.538453@2] Buffer I/O error on dev sda2, logical block 116948992, lost sync page write
[235837.538456@2] JBD2: Error -5 detected when updating journal superblock for sda2-8.
[235837.538490@2] EXT4-fs error (device sda2) in __ext4_new_inode:914: Journal has aborted
[235837.538502@2] blk_update_request: I/O error, dev sda, sector 409640
[235837.538504@2] Buffer I/O error on dev sda2, logical block 0, lost sync page write

Do you use 9.0.3 build on N2?
As I remember it was fixed already in nightly builds…
You can try to update to nightly to check if problem fixed and after update to next stable as it will be ready.

1 Like

I use two external USB3 drives (4TB, 1x 3.5" self-powered, 1x 2.5" USB-powered) with N2-nightlies since weeks and have no problems.

1 Like

I’m using 9.0.3. I’ll try the nightlies

You can try already 9.2.0 stable

I did three different things, and now it’s fixed. The first was the upgrade to 9.2.0, but I still had issues.

Next, I realized that the SSD was way hotter than it was when running on my previous libreelec system (x86, not odroid), so I changed enclosures.

At the same time, I was having terrible wifi performance, so I switched from using the USB2 AC wifi key I had to a TP-Link travel router connected via ethernet that handles the wifi bridge.

The last two fixed the problem. Later on, I’m going to try moving back to the old SSD enclosure to see if the heat was the only problem.

I bought a Lacie 4to 2.5 inch hard drive formatted in NTFS.
It does not work on the N2. It connects and disconnects automatically every 2 or 3 seconds.
Please hepl me.
Thank you

Does it work on other devices (like a PC)? Does it come with a “double” USB cable? It’s possible that the N2’s USB port can’t provide enough power to this particular drive.

1 Like

Had this behaviour until I got a decent external case with 12v supply. It will kill the HDD eventually if it is allowed to continue.

Shoog