Jerry Jyrer

Quick scan, it looks like the same. Solution / root cause?

Totally agreed. I posted here and similar topics for the same issue but so far no real solutions. Many suggestions were around under voltage being supplied. I personally doubt if that is the root cause. Armbian software/driver itself? Not too sure I tried the stock one from FriendlyElec, the result is the same. Is it the upstream Linux? Possible but no verification. I have just tried after recent apt update and upgrade. The same problem is still reproducible.

Yes, exactly what I finally solved my problem. Same to you Jim, I initially thought and be advised by many that it was the power problem but at the end what solved was to connect one with an USB 2.0 port.

Half correct sir. I fixed the power things. The problem wasn't. What really did the trick was to connect one hard drive with an usb extension (usb 2.0). The extension has no external power supply whatsoever. If any of my cabel is bad, adding additional one result worse. But in fact, it did the trick. I successfully rsync 1.7TB as expected. Now, I'm going to just connect my original usb-c adapter --- the one that all of us said it's the problem -- instead of the DC power adapter 5V 8A powering via GPIO pin 4 (+) and 6(GDN). I'm about 80% sure it wouldn't have any problem. What would it be really a problem to connect 2 USB 3.0 gen 1 external hard drives to Nanopi M4 and doing their full capacity reading/writing. Driver, board, or kernel issues? Thought?

It looks like I might find the problems. I connected my Toshiba external hard drive (2TB) with another usb 2.0 extension cable. Basically, instead of contect it as usb 3.0, I made it as usb 2.0. My WD Mybook 8TB is connecting to the board directly as usb 3.0 Copying now going >1GB of data and still continue on going. dmesg shows some errors and warnning about resetting the speed though but the rsync is still good and continue: kern :info : [Dec12 19:26] usb 3-1.1.1: reset high-speed USB device number 4 using xhci-hcd kern :warn : [ +0.138467] usb 3-1.1.1: ep 0x81 - rounding interval to 16 microframes, ep desc says 20 microframes kern :warn : [ +0.000055] usb 3-1.1.1: ep 0x2 - rounding interval to 16 microframes, ep desc says 20 microframes kern :warn : [ +6.776374] xhci-hcd xhci-hcd.6.auto: WARN Event TRB for slot 5 ep 2 with no TDs queued? kern :info : [ +31.102096] usb 3-1.1.1: reset high-speed USB device number 4 using xhci-hcd kern :warn : [ +0.133845] usb 3-1.1.1: ep 0x81 - rounding interval to 16 microframes, ep desc says 20 microframes kern :warn : [ +0.000056] usb 3-1.1.1: ep 0x2 - rounding interval to 16 microframes, ep desc says 20 microframes kern :warn : [Dec12 19:27] xhci-hcd xhci-hcd.6.auto: WARN Event TRB for slot 5 ep 2 with no TDs queued? kern :warn : [ +4.933371] xhci-hcd xhci-hcd.6.auto: WARN Event TRB for slot 5 ep 2 with no TDs queued? kern :warn : [ +35.645125] xhci-hcd xhci-hcd.6.auto: WARN Event TRB for slot 5 ep 2 with no TDs queued? kern :info : [Dec12 19:28] usb 3-1.1.1: reset high-speed USB device number 4 using xhci-hcd kern :warn : [ +0.138459] usb 3-1.1.1: ep 0x81 - rounding interval to 16 microframes, ep desc says 20 microframes kern :warn : [ +0.000057] usb 3-1.1.1: ep 0x2 - rounding interval to 16 microframes, ep desc says 20 microframes kern :warn : [ +17.781779] xhci-hcd xhci-hcd.6.auto: WARN Event TRB for slot 5 ep 2 with no TDs queued? kern :warn : [ +4.944248] xhci-hcd xhci-hcd.6.auto: WARN Event TRB for slot 5 ep 2 with no TDs queued? kern :info : [Dec12 19:29] usb 3-1.1.1: reset high-speed USB device number 4 using xhci-hcd kern :warn : [ +0.134115] usb 3-1.1.1: ep 0x81 - rounding interval to 16 microframes, ep desc says 20 microframes kern :warn : [ +0.000055] usb 3-1.1.1: ep 0x2 - rounding interval to 16 microframes, ep desc says 20 microframes kern :info : [ +36.858678] usb 3-1.1.1: reset high-speed USB device number 4 using xhci-hcd kern :warn : [ +0.133971] usb 3-1.1.1: ep 0x81 - rounding interval to 16 microframes, ep desc says 20 microframes kern :warn : [ +0.000056] usb 3-1.1.1: ep 0x2 - rounding interval to 16 microframes, ep desc says 20 microframes kern :warn : [Dec12 19:30] xhci-hcd xhci-hcd.6.auto: WARN Event TRB for slot 5 ep 2 with no TDs queued? kern :warn : [ +9.477617] xhci-hcd xhci-hcd.6.auto: WARN Event TRB for slot 5 ep 2 with no TDs queued? kern :warn : [ +6.977276] xhci-hcd xhci-hcd.6.auto: WARN Event TRB for slot 5 ep 2 with no TDs queued? kern :warn : [Dec12 19:31] xhci-hcd xhci-hcd.6.auto: WARN Event TRB for slot 5 ep 2 with no TDs queued? kern :info : [ +37.592164] usb 3-1.1.1: reset high-speed USB device number 4 using xhci-hcd kern :warn : [ +0.134474] usb 3-1.1.1: ep 0x81 - rounding interval to 16 microframes, ep desc says 20 microframes kern :warn : [ +0.000068] usb 3-1.1.1: ep 0x2 - rounding interval to 16 microframes, ep desc says 20 microframes

A normal cp creates the same problem also: $ sudo cp -Rf /mnt/Photos-Videos/* /media/WDMyBook/Photos-Videos/ $dmesg -xH shows

I got a normal DC power adapter 5V 8A powering via GPIO pin 4 (+) and 6(GDN). The USB Voltmeter reports 5.2V to 5.0V. The same problem occured. I really doubt that it's about under-votage nor power supply to the board. Is it possible this is a bad board? Can anyone try to rsync between two connected USB hard drives -- says successfully sync ~1TB of data on Nanopi M4?

I followed something like this for my NanoPi M4.

No. something like: $ sudo rsync -avh --progress /mnt/Photos-Videos /media/WDMyBook/

I'm pretty sure that's not the case.

Got another 5V 4A Board only: 5.13V Hard drives connected : 4.97 Same problem. Is it really the under-voltage problem still or something else might be covering this?

tried, it doesn't help. Got a USB voltmeter. Board Only: ~4.9V One hard drive connected: ~4.8V two hard drives connected: ~4.77V Rsync, staying around 4.77V but the same problem occured with both of them lost connections. Results were similar either using 5V 3A adapter or 5V 4A one. I was wondering if this is really about under volate and amp supplying, can I get a 5V 8A (or higher) with a barrel to USB converter -- e.g. https://www.amazon.com/JacobsParts-Barrel-Female-Connector-Adapter/dp/B00QHL2PTA https://www.amazon.com/ALITOVE-Converter-Transformer-5-5x2-1mm-100V-240V/dp/B078RZBL8X

Just a quick update, I've just received a brandnew USB-C 5V 4A. Same problem, no success. I'm waiting for an USB voltmeter to be sure if it's about under voltage or something else. dmesg similar to before kern :warn : [ +0.192987] xhci-hcd xhci-hcd.6.auto: xHCI host not responding to stop endpoint command. kern :warn : [ +0.000020] xhci-hcd xhci-hcd.6.auto: Assuming host is dying, halting host. kern :err : [ +0.013582] xhci-hcd xhci-hcd.6.auto: HC died; cleaning up kern :err : [ +0.000051] hub 4-1:1.0: hub_port_status failed (err = -22) kern :err : [ +0.000019] usb 4-1-port2: cannot reset (err = -22) kern :info : [ +0.000050] usb 3-1: USB disconnect, device number 2 kern :info : [ +0.000068] usb 4-1.2: USB disconnect, device number 3 kern :info : [ +0.001052] usb 4-1: USB disconnect, device number 2

Thank you Seasalt. Much appreciated. It was a little too late but lucky enough that all it was just some spark. I stopped before much drama happening. All things seem to be working okay. : ) Thanks NicoD. I'll get it to test things out. Thanks for the info. I would try my best to power the board with usb-c before going to the pin route. I have ordered the DashCharger 5V 4A. I'll get usb volt-meter and test things out. I initially thought that 5V 3A I have is good enough. That's the max spec for USB-C at 5V I believe. : (. Anyone success on rsync between USB hard drives attaching to the board with 3A/4A adapter?

Newbie question, is there a tool to do it at the software level or something that I need to plug a voltmeter to port 1 and 4 of one of the USB ports? http://pinouts.ru/Slots/USB_pinout.shtml

Right, 3.5 ones have their owned power supplies. They are 8TB MyBook. 2.5 one is powered via USB. It is a Tohisba one.

Nope., I used various usb power adapters and cables that I have. I didn't get the original power adapter and cable from FriendlyArm. I mainly tested connecting with one 2.5" and one 3.5". I also tested connecting both 3.5" once or twice. The results remain the same. Thanks,. will do. I wondered if anyone experiencing the same as I'm having with good cable and power adapter -- recommendation?

One of my suspects is the power adapter in which I'd like to get a confirmation from anyone with M4 with the FriendlyArm 5V 4A or DashCharger. Do you have problems connecting 2 USB hard drives and rsync between them. My situation's both drive got disconnected after <10 minutes of rsyncing at max. Separately, does this one come with a cable if I order it separately? Or any recommendation for a good power adapter juicing the M4. https://www.friendlyarm.com/index.php?route=product/product&amp;product_id=238

Anyone successfully connect 2 USB HDDs and rsycn between them? I haven't been able to. Both hard drives got disconnected. Board: Nanopi M4 4GB OS: Armbian Bionic/Stretch, FriendlyArM Bionic. All the same result. Power: USB-C 5V 3A / 2.1A / 2.4A. All the same result. rootsf: on SD, HDD. all the same result. Let me know what your setup is to get this successful. Ref: ref:

Related to It looks like the problem's related to the USB autosuspend. Googling "xHCI host not responding to stop endpoint command." seems to say so. I've been trying to disable the USB autosuspend but no success. I followed all possible ways described in https://unix.stackexchange.com/questions/91027/how-to-disable-usb-autosuspend-on-kernel-3-7-10-or-above and https://www.kernel.org/doc/Documentation/usb/power-management.txt but $ cat /sys/module/usbcore/parameters/autosuspend always returns 2 Board: NanoPi M4, 4GB with Armbian_5.65_Nanopim4_Debian_stretch_default_4.4.162.7z

I'll dig a bit more but so far here is what looks like to be the problem: [ 1008.854862] xhci-hcd xhci-hcd.6.auto: xHCI host not responding to stop endpoint command. [ 1008.854871] xhci-hcd xhci-hcd.6.auto: Assuming host is dying, halting host. [ 1008.854943] xhci-hcd xhci-hcd.6.auto: xHCI host not responding to stop endpoint command. [ 1008.854958] xhci-hcd xhci-hcd.6.auto: Assuming host is dying, halting host. [ 1008.868355] xhci-hcd xhci-hcd.6.auto: HC died; cleaning up [ 1008.868414] xhci-hcd xhci-hcd.6.auto: HC died; cleaning up [ 1008.868420] usb 3-1: USB disconnect, device number 2 [ 1008.868928] usb 4-1: USB disconnect, device number 2 [ 1008.868934] usb 4-1.3: USB disconnect, device number 3 [ 1008.875798] sd 0:0:0:0: [sda] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x01 driverbyte=0x00 [ 1008.875808] sd 0:0:0:0: [sda] tag#0 CDB: opcode=0x8a 8a 00 00 00 00 00 00 c5 88 00 00 00 00 f0 00 00 [ 1008.875812] blk_update_request: I/O error, dev sda, sector 12945408 [ 1008.875898] sd 0:0:0:0: [sda] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x01 driverbyte=0x00 [ 1008.875903] sd 0:0:0:0: [sda] tag#0 CDB: opcode=0x8a 8a 00 00 00 00 00 00 c5 88 f0 00 00 00 f0 00 00 [ 1008.875907] blk_update_request: I/O error, dev sda, sector 12945648 [ 1008.883757] EXT4-fs warning (device sda1): ext4_end_bio:330: I/O error -5 writing to inode 40435820 (offset 0 size 53248 starting block 323676765) [ 1008.883767] Buffer I/O error on device sda1, logical block 323676496 [ 1008.883774] Buffer I/O error on device sda1, logical block 323676497 [ 1008.883778] Buffer I/O error on device sda1, logical block 323676498 [ 1008.883783] Buffer I/O error on device sda1, logical block 323676499 [ 1008.883786] Buffer I/O error on device sda1, logical block 323676500 [ 1008.883790] Buffer I/O error on device sda1, logical block 323676501 [ 1008.883793] Buffer I/O error on device sda1, logical block 323676502 [ 1008.883796] Buffer I/O error on device sda1, logical block 323676503 [ 1008.883800] Buffer I/O error on device sda1, logical block 323676504 [ 1008.883803] Buffer I/O error on device sda1, logical block 323676505 [ 1008.883852] EXT4-fs warning (device sda1): ext4_end_bio:330: I/O error -5 writing to inode 40438764 (offset 0 size 413696 starting block 323676866) [ 1008.883975] EXT4-fs warning (device sda1): ext4_end_bio:330: I/O error -5 writing to inode 40501734 (offset 16777216 size 4980736 starting block 1618432) [ 1008.884650] EXT4-fs warning (device sda1): ext4_end_bio:330: I/O error -5 writing to inode 40501734 (offset 16777216 size 4980736 starting block 1618688) [ 1008.885322] EXT4-fs warning (device sda1): ext4_end_bio:330: I/O error -5 writing to inode 40501734 (offset 16777216 size 4980736 starting block 1618944) [ 1008.885887] EXT4-fs warning (device sda1): ext4_end_bio:330: I/O error -5 writing to inode 40501734 (offset 16777216 size 4980736 starting block 1619200) [ 1008.886444] EXT4-fs warning (device sda1): ext4_end_bio:330: I/O error -5 writing to inode 40501734 (offset 16777216 size 4980736 starting block 1619392) [ 1008.886944] EXT4-fs warning (device sda1): ext4_end_bio:330: I/O error -5 writing to inode 40501734 (offset 21757952 size 1572864 starting block 1619648) [ 1008.887502] EXT4-fs warning (device sda1): ext4_end_bio:330: I/O error -5 writing to inode 40501734 (offset 21757952 size 1572864 starting block 1619776) [ 1008.887797] EXT4-fs warning (device sda1): ext4_end_bio:330: I/O error -5 writing to inode 40501734 (offset 23330816 size 1310720 starting block 1620032) [ 1008.890389] JBD2: Detected IO errors while flushing file data on sda1-8 [ 1008.890521] Aborting journal on device sda1-8. [ 1008.890657] JBD2: Error -5 detected when updating journal superblock for sda1-8. [ 1008.890829] JBD2: Detected IO errors while flushing file data on sda1-8 [ 1008.901805] sd 1:0:0:0: [sdb] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x07 driverbyte=0x00 [ 1008.901819] sd 1:0:0:0: [sdb] tag#0 CDB: opcode=0x28 28 00 39 1d dd f0 00 00 f0 00 [ 1008.901825] blk_update_request: I/O error, dev sdb, sector 958258672 [ 1008.922339] usb 4-1.4: USB disconnect, device number 4 [ 1008.925822] sd 1:0:0:0: [sdb] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x01 driverbyte=0x00 [ 1008.925841] sd 1:0:0:0: [sdb] tag#0 CDB: opcode=0x28 28 00 39 1d de e0 00 00 10 00 [ 1008.925848] blk_update_request: I/O error, dev sdb, sector 958258912 [ 1008.925987] sd 1:0:0:0: [sdb] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x01 driverbyte=0x00 [ 1008.925995] sd 1:0:0:0: [sdb] tag#0 CDB: opcode=0x28 28 00 39 1d de f0 00 00 f0 00 [ 1008.926001] blk_update_request: I/O error, dev sdb, sector 958258928 [ 1008.927276] EXT4-fs error (device sda1): ext4_journal_check_start:56: Detected aborted journal [ 1008.928055] EXT4-fs (sda1): Remounting filesystem read-only [ 1008.928544] bdi-block not registered

Just back from the holiday. I tested the media. Both hard drives are healthy. I tested to mount /mnt/toshiba. Same problem. rsync just quited and after that no files seem to be mounted. A hard restart (pulling of power) was required. Here is $sudo armbianmonitor -u Just after the restarted with the Toshiba unattached. http://ix.io/1uz5 Any help would be appreciated. Thanks, Jerry

Yep. nand-to-sata-install works pretty good.

Thank you. Yes I'll be aware. Currently, all is pure data. Yes, the media test is still on going. I'll test out /mnt/toshiba mount point once the test finished. My book is ext4. Toshiba is NTFS. Both of them are connected to USB 3.0 ports. There 4 of them on NanoPi M4. I tried all of them and got the result.

$ sudo mount /dev/sdb1 /mnt $ sudo mkdir -p /MyBackup $ sudo rsync -avh --progress /mnt/ /MyBackup/ Well as for the reason, (1) testing and (2) mainly, 3-2-1 backup. Another observation, $ sudo smartctl -x /dev/sda1 showing: SMART support is: Unavailable - device lacks SMART capability. pretty weird. I'm running $armbianmonitor -c "$HOME" to test my new 8TB MyBook now. It will take awhile but so far so good. I believe it's finishing writing >1TB; 7TB to go.