Syncing two UAS devices causes Ubuntu to hang

binhex
Posts: 18
Joined: Wed Jun 19, 2019 5:54 pm
languages_spoken: english
ODROIDs: N2
Has thanked: 4 times
Been thanked: 1 time
Contact:

Re: Syncing two UAS devices causes Ubuntu to hang

Unread post by binhex » Fri Aug 02, 2019 7:02 pm

@odroid, so if im reading the above tests so far you are saying you currently are not seeing any USB disconnection issues, right?, if so what would be your recommended settings for CoreELEC users who are seeing USB disconnection issues?, i see you are using the following:-

1. thicker usb cables - any make of cable you would recommend?
2. significantly beefier power supply over the standard 12v/2A - 15V/4A is this worth trying?, if so what make and model would you recommend?
3. additional parameters to boot.ini - do we simply add the following to the boot.ini for CoreELEC or is this tied in with the later kernel (see next comment) usb-xhci.tablesize=2
4. later kernel - im assuming this would be something CoreELEC dev's would need to tweak in their image, right? if so what kernel is the recommended for CoreELEC?

if you feel this is still too early in the testing process to conclude anything yet then thats cool, but i thought i would ask.

Note - i personally am NOT seeing USB disconnection issues but i know a number of members are, such as @rosenrot and @trex_daemon who are seeing USB tuner disconnections whilst running CoreELEC and feel it would be nice to include this group of people as well, i would think both of the people just mentioned would be up for testing anything you put forward.

User avatar
odroid
Site Admin
Posts: 32146
Joined: Fri Feb 22, 2013 11:14 pm
languages_spoken: English
ODROIDs: ODROID
Has thanked: 119 times
Been thanked: 297 times
Contact:

Re: Syncing two UAS devices causes Ubuntu to hang

Unread post by odroid » Fri Aug 02, 2019 8:52 pm

@binhex,

We will share what we changed in the Kernel source, boot.ini, bootblob and IRQ handler tweaks with team CoreELEC once we complete the test early next week.
And they can easily merge the changes.
But this improvements might not be directly effective to the DVT/ATSC tuners' stability and we need further analysis probably.

binhex
Posts: 18
Joined: Wed Jun 19, 2019 5:54 pm
languages_spoken: english
ODROIDs: N2
Has thanked: 4 times
Been thanked: 1 time
Contact:

Re: Syncing two UAS devices causes Ubuntu to hang

Unread post by binhex » Fri Aug 02, 2019 8:57 pm

odroid wrote:
Fri Aug 02, 2019 8:52 pm
@binhex,

We will share what we changed in the Kernel source, boot.ini, bootblob and IRQ handler tweaks with team CoreELEC once we complete the test early next week.
And they can easily merge the changes.
But this improvements might not be directly effective to the DVT/ATSC tuners and we need further analysis probably.
OK thanks for taking the time to respond, it's appreciated, just FYI i know the 'Sundtek DVB-S2 USB' are def problematic, as both of the mentioned users in my previous post have this adapter with disconnection issues, so it should be fairly easy to replicate once you get time to taking a look.

User avatar
odroid
Site Admin
Posts: 32146
Joined: Fri Feb 22, 2013 11:14 pm
languages_spoken: English
ODROIDs: ODROID
Has thanked: 119 times
Been thanked: 297 times
Contact:

Re: Syncing two UAS devices causes Ubuntu to hang

Unread post by odroid » Fri Aug 02, 2019 9:02 pm

Thank you letting me know the device name.
Unfortunately, there is no DVB services here in Korea. So it is very difficult to test it.
So we need to gather some kernel error/warning messages from the users to find a clue.

Jay4692
Posts: 16
Joined: Sat Jun 29, 2019 6:31 pm
languages_spoken: english, spanish
ODROIDs: N2
Has thanked: 6 times
Been thanked: 3 times
Contact:

Re: Syncing two UAS devices causes Ubuntu to hang

Unread post by Jay4692 » Sat Aug 03, 2019 12:54 am

Hello everyone,

I've been following this thread since I discovered this problem with my N2. My setup is form of two Toshiba 2.5" USB 3.0 external drives connected to the N2 through a powered USB 3.0 hub, both drives are formatted with EXT4 and the N2 is running the official Ubuntu 18.04 LTS minimal image. I use one of the drives for a NAS and the other one is for incremental backups, which are done every night using rsync and its option --link-dest. I used this setup with a Raspberry Pi 3b for a year and didn't have any problems.

I didn't mind the slow rate transfer between drives because the only time I needed to transfer files from one to the other was for backing up at night, so while I waited for a permanent fix for this issue what I did was in my backup script before the rsync command added to the first post temporal solution to limit the size of max_sectors_size to 16 (I did try multiple values, this one being with the most speed and reliability) and then after the rsync command and restored the max_sectors_size value to default, that way I could enjoy the fast transfer speed when using the NAS and have reliable USB transfers for the backing up process.
With this, backups have been done without any issues until this night, after I upgraded to the last boot.ini, which for some reason caused the backup and system to hang again.

I did make sure that I was running the latest version of boot.ini and kernel so to try and fix the problem again I setted the max_sectors_size to 8. That did work but the backup time has increased, with rate transfers at around 20 MB/s but as I said I don't mind the time it takes to backup to the other drive because it's done overnight, I just want not to think about if the backup process fails or not, but it would be nice to be able to use that USB 3.0 speed to restore my backup in case one of the drives fails :)

I just wanted to share my setup and experience with this problem to add more information and I hope to find a permanent solution to this problem.

erm67
Posts: 9
Joined: Sat Jun 22, 2019 10:53 pm
languages_spoken: english,german,italian
ODROIDs: N2
Has thanked: 0
Been thanked: 1 time
Contact:

Re: Syncing two UAS devices causes Ubuntu to hang

Unread post by erm67 » Sat Aug 03, 2019 5:22 pm

odroid wrote:
Tue Jul 30, 2019 3:51 pm
The latest kernel package is 4.9.185-43.
https://github.com/hardkernel/linux/releases

The latest bootini package for setting the sg_table size properly and assigning the USB IRQ handlers to a big A73 core.
https://github.com/mdrjr/n2_bootini/blo ... t.ini#L103
Thanks, I was having occasionally the problem in particular every time I run a btrfs scrub command; I am using a 4 HDD uas enclosure (Bus 002 Device 003: ID 152d:0567 JMicron Technology Corp. / JMicron USA Technology Corp. JMS567 SATA 6Gb/s bridge) this fixedthe crashes, it is a bit slow I think because I have not updated uboot and probably the binary blob since I am on holiday and only have ssh access to the box, but I will as soon as I came back home.

Code: Select all

erm67 ~ # cat /sys/kernel/debug/clk/clk81/clk_rate
166666664
I only have a question: the boot.ini uses elevator=none but I have 4 rotational disks in the enclosure and probably deadline or cfq will work better than none, the elevator is unrelated to the problem and I can change it to something else in the boot.ini right?

User avatar
odroid
Site Admin
Posts: 32146
Joined: Fri Feb 22, 2013 11:14 pm
languages_spoken: English
ODROIDs: ODROID
Has thanked: 119 times
Been thanked: 297 times
Contact:

Re: Syncing two UAS devices causes Ubuntu to hang

Unread post by odroid » Mon Aug 05, 2019 11:53 am

@erm67,
166Mhz is quite slow. It must be 222Mhz.
I think some boot code couldn't be updated properly by uncertain root causes.
We will release a new minimal image within two days for better test correlations.

@Jay4692,
Thank you sharing the test result.
Please try it again once we release a new OS image a couple of days later.
These users thanked the author odroid for the post:
Jay4692 (Mon Aug 05, 2019 5:21 pm)

nick793
Posts: 26
Joined: Mon Jun 24, 2019 9:35 pm
languages_spoken: english
ODROIDs: N2, GO
Has thanked: 0
Been thanked: 2 times
Contact:

Re: Syncing two UAS devices causes Ubuntu to hang

Unread post by nick793 » Mon Aug 05, 2019 11:12 pm

Just wanted to report that I had another fail last night but I'm unsure of root cause. Wasn't doing anything stressful to the system or any checksums but the system crashed regardless.

This was on 4.9.185-43 and an older boot.ini (didn't update for some reason). I just updated after the failure to 4.9.185-44 and a new boot.ini with xhci-tablesize=2. Also updated to latest Ubuntu minimal through apt upgrade.

I'm running a resync on my RAID1 arrays now and bringing all databases/applications back up and will report back if anything dies on the new kernel/boot.ini/image

User avatar
odroid
Site Admin
Posts: 32146
Joined: Fri Feb 22, 2013 11:14 pm
languages_spoken: English
ODROIDs: ODROID
Has thanked: 119 times
Been thanked: 297 times
Contact:

Re: Syncing two UAS devices causes Ubuntu to hang

Unread post by odroid » Tue Aug 06, 2019 9:00 am

We've tested the stressing four SSDs in parallel over 100 hours and there was no issue.
We will release a new minimal image tomorrow to have the exactly same test conditions with many users.
Once we release it, we will post a news on this thread too.

We will also start another test with the RAID configuration with four SSDs tomorrow.

joshua.yang
Posts: 243
Joined: Fri Sep 22, 2017 5:54 pm
languages_spoken: Korean, English
ODROIDs: XU4, XU4Q + Cloudshell2, H2, N2
Has thanked: 2 times
Been thanked: 24 times
Contact:

Re: Syncing two UAS devices causes Ubuntu to hang

Unread post by joshua.yang » Tue Aug 06, 2019 3:21 pm

elatllat wrote:
Fri Aug 02, 2019 5:52 pm
I'd guess something like this was used;

Code: Select all

mdadm --create /dev/md/test /dev/sda /dev/sdb /dev/sdc /dev/sdd --level=5 --raid-devices=4
mkfs.ext4 /dev/md/test
mount /dev/md/test /media/test
Hi.

I've tested with 4 Samsung 860 EVO 250G SSD which are connected using our SATA to USB 3.0 bridge board.
20190806_150857.jpg
20190806_150857.jpg (554.38 KiB) Viewed 1462 times
Set RAID 5 up with that commands, and waited a few minutes for its re-sync process to be done.

Then I tested its performance using iozone 3, 3 times.

This is the results.

Code: Select all

root@odroid:/media/test# fstrim / && sudo iozone -e -I -a -s 100M -r 4k -r 16384k -i 0 -i 1 -i 2
	Iozone: Performance Test of File I/O
	        Version $Revision: 3.429 $
		Compiled for 64 bit mode.
		Build: linux

	Contributors:William Norcott, Don Capps, Isom Crawford, Kirby Collins
	             Al Slater, Scott Rhine, Mike Wisner, Ken Goss
	             Steve Landherr, Brad Smith, Mark Kelly, Dr. Alain CYR,
	             Randy Dunlap, Mark Montague, Dan Million, Gavin Brebner,
	             Jean-Marc Zucconi, Jeff Blomberg, Benny Halevy, Dave Boone,
	             Erik Habbinga, Kris Strecker, Walter Wong, Joshua Root,
	             Fabrice Bacchella, Zhenghua Xue, Qin Li, Darren Sawyer,
	             Vangel Bojaxhi, Ben England, Vikentsi Lapa.

	Run began: Tue Aug  6 02:48:13 2019

	Include fsync in write timing
	O_DIRECT feature enabled
	Auto Mode
	File size set to 102400 kB
	Record Size 4 kB
	Record Size 16384 kB
	Command line used: iozone -e -I -a -s 100M -r 4k -r 16384k -i 0 -i 1 -i 2
	Output is in kBytes/sec
	Time Resolution = 0.000001 seconds.
	Processor cache size set to 1024 kBytes.
	Processor cache line size set to 32 bytes.
	File stride size set to 17 * record size.
                                                              random    random     bkwd    record    stride
              kB  reclen    write  rewrite    read    reread    read     write     read   rewrite      read   fwrite frewrite    fread  freread
          102400       4    13855    16542    38757    38894    23710    10524
          102400   16384   138675   157488   263920   267069   265558   146516

iozone test complete.
root@odroid:/media/test# fstrim / && sudo iozone -e -I -a -s 100M -r 4k -r 16384k -i 0 -i 1 -i 2
	Iozone: Performance Test of File I/O
	        Version $Revision: 3.429 $
		Compiled for 64 bit mode.
		Build: linux

	Contributors:William Norcott, Don Capps, Isom Crawford, Kirby Collins
	             Al Slater, Scott Rhine, Mike Wisner, Ken Goss
	             Steve Landherr, Brad Smith, Mark Kelly, Dr. Alain CYR,
	             Randy Dunlap, Mark Montague, Dan Million, Gavin Brebner,
	             Jean-Marc Zucconi, Jeff Blomberg, Benny Halevy, Dave Boone,
	             Erik Habbinga, Kris Strecker, Walter Wong, Joshua Root,
	             Fabrice Bacchella, Zhenghua Xue, Qin Li, Darren Sawyer,
	             Vangel Bojaxhi, Ben England, Vikentsi Lapa.

	Run began: Tue Aug  6 02:48:52 2019

	Include fsync in write timing
	O_DIRECT feature enabled
	Auto Mode
	File size set to 102400 kB
	Record Size 4 kB
	Record Size 16384 kB
	Command line used: iozone -e -I -a -s 100M -r 4k -r 16384k -i 0 -i 1 -i 2
	Output is in kBytes/sec
	Time Resolution = 0.000001 seconds.
	Processor cache size set to 1024 kBytes.
	Processor cache line size set to 32 bytes.
	File stride size set to 17 * record size.
                                                              random    random     bkwd    record    stride
              kB  reclen    write  rewrite    read    reread    read     write     read   rewrite      read   fwrite frewrite    fread  freread
          102400       4    13927    17057    38896    38936    23379    10683
          102400   16384   140834   143291   263919   267054   267153   138834

iozone test complete.
root@odroid:/media/test# fstrim / && sudo iozone -e -I -a -s 100M -r 4k -r 16384k -i 0 -i 1 -i 2
	Iozone: Performance Test of File I/O
	        Version $Revision: 3.429 $
		Compiled for 64 bit mode.
		Build: linux

	Contributors:William Norcott, Don Capps, Isom Crawford, Kirby Collins
	             Al Slater, Scott Rhine, Mike Wisner, Ken Goss
	             Steve Landherr, Brad Smith, Mark Kelly, Dr. Alain CYR,
	             Randy Dunlap, Mark Montague, Dan Million, Gavin Brebner,
	             Jean-Marc Zucconi, Jeff Blomberg, Benny Halevy, Dave Boone,
	             Erik Habbinga, Kris Strecker, Walter Wong, Joshua Root,
	             Fabrice Bacchella, Zhenghua Xue, Qin Li, Darren Sawyer,
	             Vangel Bojaxhi, Ben England, Vikentsi Lapa.

	Run began: Tue Aug  6 02:49:41 2019

	Include fsync in write timing
	O_DIRECT feature enabled
	Auto Mode
	File size set to 102400 kB
	Record Size 4 kB
	Record Size 16384 kB
	Command line used: iozone -e -I -a -s 100M -r 4k -r 16384k -i 0 -i 1 -i 2
	Output is in kBytes/sec
	Time Resolution = 0.000001 seconds.
	Processor cache size set to 1024 kBytes.
	Processor cache line size set to 32 bytes.
	File stride size set to 17 * record size.
                                                              random    random     bkwd    record    stride
              kB  reclen    write  rewrite    read    reread    read     write     read   rewrite      read   fwrite frewrite    fread  freread
          102400       4    13933    17365    39921    41170    24403    10761
          102400   16384   141815   139035   264118   267817   266864   148101

iozone test complete.
sg_tablesize is 2.

Now I will do some test with that software RAIDed array.
I'm about to write a script that performs a loop for doing generating/reading/deleting using a huge 100GB dummy file.
Also, I will use the new released minimal image.

Any suggestions welcome. :)

xabolcs
Posts: 54
Joined: Fri Jun 22, 2018 6:37 pm
languages_spoken: english
ODROIDs: N2
Has thanked: 69 times
Been thanked: 1 time
Contact:

Re: Syncing two UAS devices causes Ubuntu to hang

Unread post by xabolcs » Tue Aug 06, 2019 3:39 pm

f3write and f3read from the f3 package will be your friend!

Read their help to generate exact amount of semi-random data!

You could also try other filesystems too.
I was able to crash easily doing f3read & f3write tests on a btrfs filesystem on a RAID10 (made from 2 drives, with far 2 layout).

elatllat
Posts: 1502
Joined: Tue Sep 01, 2015 8:54 am
languages_spoken: english
ODROIDs: XU4, N1, N2
Has thanked: 21 times
Been thanked: 45 times
Contact:

Re: Syncing two UAS devices causes Ubuntu to hang

Unread post by elatllat » Tue Aug 06, 2019 3:48 pm

btrfs should be left out of this test (it's to unstable especially on a diverged 4.9).
some work should be done on balancing speed and stability but I'm guessing any lingering stability issues are due to a broken upgrade.
so maybe the best thing to do would be to ask everyone to test from a fresh IMG,
and only if someone can reproduce an issue from the fresh IMG should HK do further pure stability testing.
These users thanked the author elatllat for the post:
xabolcs (Tue Aug 06, 2019 3:59 pm)

User avatar
odroid
Site Admin
Posts: 32146
Joined: Fri Feb 22, 2013 11:14 pm
languages_spoken: English
ODROIDs: ODROID
Has thanked: 119 times
Been thanked: 297 times
Contact:

Re: Syncing two UAS devices causes Ubuntu to hang

Unread post by odroid » Tue Aug 06, 2019 3:52 pm

The fresh new Ubuntu 18.04.3 minimal image has been released.
https://wiki.odroid.com/odroid-n2/os_im ... u/20190806

And I have to agree that BTRFS test must be isolated since the recent Kernel 4.9.187 still seems to have the stability/compatibility problem with BTRFS.
Once the Kernel 5.3 has some improved the S922X clock configuration for higher CPU/USB performance, let's test it again.
Until that, we have to use EXT4 probably.
These users thanked the author odroid for the post (total 3):
xabolcs (Tue Aug 06, 2019 3:59 pm) • Jay4692 (Tue Aug 06, 2019 10:07 pm) • elatllat (Wed Aug 07, 2019 12:58 am)

joshua.yang
Posts: 243
Joined: Fri Sep 22, 2017 5:54 pm
languages_spoken: Korean, English
ODROIDs: XU4, XU4Q + Cloudshell2, H2, N2
Has thanked: 2 times
Been thanked: 24 times
Contact:

Re: Syncing two UAS devices causes Ubuntu to hang

Unread post by joshua.yang » Tue Aug 06, 2019 5:21 pm

xabolcs wrote:
Tue Aug 06, 2019 3:39 pm
f3write and f3read from the f3 package will be your friend!

Read their help to generate exact amount of semi-random data!

You could also try other filesystems too.
I was able to crash easily doing f3read & f3write tests on a btrfs filesystem on a RAID10 (made from 2 drives, with far 2 layout).
TIL, f3 package looks a great validation tool. :shock:

Any idea of how I utilize this for a long-term test script?

Or, it is enough for doing a loop of f3write / f3read / removing dump files commands?

Here is my first execution of f3write command for the mount point of S/W RAIDed array.
스크린샷 2019-08-06 오후 5.19.42.png
스크린샷 2019-08-06 오후 5.19.42.png (351.33 KiB) Viewed 1410 times

Andrew Sayers
Posts: 32
Joined: Fri May 17, 2019 5:06 pm
languages_spoken: english
ODROIDs: N2
Has thanked: 6 times
Been thanked: 3 times
Contact:

Re: Syncing two UAS devices causes Ubuntu to hang

Unread post by Andrew Sayers » Tue Aug 06, 2019 6:34 pm

odroid wrote:
Tue Aug 06, 2019 3:52 pm
The fresh new Ubuntu 18.04.3 minimal image has been released.
https://wiki.odroid.com/odroid-n2/os_im ... u/20190806
This sounds like great news, and a good time to update the first post, but I've allowed myself to get sidetracked from this thread lately. I couldn't see answers to these questions above, but sorry if I've missed something:

How does this affect the previous workarounds (max_sectors_kb and tablesize)? Are they redundant? Harmful? Worth testing with and without?

Do existing users need to format and reinstall the new image, or is a normal apt-get update && apt-get upgrade enough? Do we need to apt-get dist-upgrade?

How strongly do you recommend users upgrade right now? For example, if this month is as busy as last month, I'll only have time for one format+reinstall. Should I do it now to avoid data loss, or wait and see whether this week's tests show up something else?

Finally, is there a simple explanation for the problem and/or solution? Is there a specific pull request somewhere that we can see?

I'll update the first post with answers. Good work once again!

joshua.yang
Posts: 243
Joined: Fri Sep 22, 2017 5:54 pm
languages_spoken: Korean, English
ODROIDs: XU4, XU4Q + Cloudshell2, H2, N2
Has thanked: 2 times
Been thanked: 24 times
Contact:

Re: Syncing two UAS devices causes Ubuntu to hang

Unread post by joshua.yang » Tue Aug 06, 2019 6:34 pm

I've just started an infinite test using f3 tools. :)

xabolcs
Posts: 54
Joined: Fri Jun 22, 2018 6:37 pm
languages_spoken: english
ODROIDs: N2
Has thanked: 69 times
Been thanked: 1 time
Contact:

Re: Syncing two UAS devices causes Ubuntu to hang

Unread post by xabolcs » Tue Aug 06, 2019 8:27 pm

joshua.yang wrote:
Tue Aug 06, 2019 5:21 pm
Or, it is enough for doing a loop of f3write / f3read / removing dump files commands?
f3write & f3read in a true loop will be enough, as f3write removes all dump files from the directory automatically

Code: Select all

root@odroid:~# f3write /mnt/mdp/h2w/
F3 write 7.0
Copyright (C) 2010 Digirati Internet LTDA.
This is free software; see the source for copying conditions.

Removing old file 1.h2w ...
Removing old file 2.h2w ...
Removing old file 3.h2w ...
Free space: 97.81 GB
Creating file 1.h2w ... OK!                           
Creating file 2.h2w ... OK!   
.
.
.

Jay4692
Posts: 16
Joined: Sat Jun 29, 2019 6:31 pm
languages_spoken: english, spanish
ODROIDs: N2
Has thanked: 6 times
Been thanked: 3 times
Contact:

Re: Syncing two UAS devices causes Ubuntu to hang

Unread post by Jay4692 » Tue Aug 06, 2019 10:07 pm

Hello again,

I tried the new image with a fresh install, before moving all my config and stuff I did try to run the rsync command to test tonight's backup, which includes a 4 Gb .7z file with the image of my current running SD card. It did fail, so I also try to attach both drives directly to the N2 with the same results.

So in my use case the new image doesn't improve nothing, rsync fails after a while as before, but I don't understand why Odroid can stress 4 SSDs for over 100 hours without any problems and I have problems after just a couple of minutes in my setup The only difference between what Odroid uses its eMMC, while I use a regular SanDisk SD card, and the drives.

I will continue to set max_sectors_kb to 8 before trying to copy between drives, which is the only solution that currently works for me.

elatllat
Posts: 1502
Joined: Tue Sep 01, 2015 8:54 am
languages_spoken: english
ODROIDs: XU4, N1, N2
Has thanked: 21 times
Been thanked: 45 times
Contact:

Re: Syncing two UAS devices causes Ubuntu to hang

Unread post by elatllat » Wed Aug 07, 2019 12:45 am

Jay4692 wrote:
Tue Aug 06, 2019 10:07 pm
Hello again,

I tried the new image with a fresh install... It did fail...
What was the exact failure message? (rsync and dmesg)
and what are the exact commands for minimal steps to reproduce? (just rsync a 4GB file to ext4, no RAID or Btrfs?)

Jay4692
Posts: 16
Joined: Sat Jun 29, 2019 6:31 pm
languages_spoken: english, spanish
ODROIDs: N2
Has thanked: 6 times
Been thanked: 3 times
Contact:

Re: Syncing two UAS devices causes Ubuntu to hang

Unread post by Jay4692 » Wed Aug 07, 2019 3:33 am

elatllat wrote:
Wed Aug 07, 2019 12:45 am
Jay4692 wrote:
Tue Aug 06, 2019 10:07 pm
Hello again,

I tried the new image with a fresh install... It did fail...
What was the exact failure message? (rsync and dmesg)
and what are the exact commands for minimal steps to reproduce? (just rsync a 4GB file to ext4, no RAID or Btrfs?)
The message that shows is this one:

Code: Select all

sending incremental file list
./
Descargas/
Documentos/Odroid/
Documentos/Odroid/odroid-n2-backup_06-08-19.7z
  4,622,522,321 100%   24.64MB/s    0:02:58 (xfr#1, ir-chk=1004/1049)
rsync: read errors mapping "/mnt/toshibaNAS/Documentos/Odroid/odroid-n2-backup_06-08-19.7z": Input/output error (5)
file has vanished: "/mnt/toshibaNAS/Documentos/Odroid/odroid-n2-backup_06-08-19.img"
rsync: write failed on "/mnt/toshibaBAK/2019-08-06/Documentos/Odroid/odroid-n2-backup_06-08-19.7z": Read-only file system (30)
rsync error: error in file IO (code 11) at receiver.c(393) [receiver=3.1.2]
ls: reading directory '/mnt/toshibaBAK/': Input/output error
ls: reading directory '/mnt/toshibaBAK/': Input/output error
ls: reading directory '/mnt/toshibaBAK/': Input/output error
ls: reading directory '/mnt/toshibaBAK/': Input/output error
ls: reading directory '/mnt/toshibaBAK/': Input/output error
ls: reading directory '/mnt/toshibaBAK/': Input/output error
ls: reading directory '/mnt/toshibaBAK/': Input/output error
ls: reading directory '/mnt/toshibaBAK/': Input/output error
ls: reading directory '/mnt/toshibaBAK/': Input/output error
ls: reading directory '/mnt/toshibaBAK/': Input/output error
ls: reading directory '/mnt/toshibaBAK/': Input/output error
ls: reading directory '/mnt/toshibaBAK/': Input/output error
ls: reading directory '/mnt/toshibaBAK/': Input/output error
ls: reading directory '/mnt/toshibaBAK/': Input/output error
ls: reading directory '/mnt/toshibaBAK/': Input/output error
ls: reading directory '/mnt/toshibaBAK/': Input/output error
ls: reading directory '/mnt/toshibaBAK/': Input/output error
ls: reading directory '/mnt/toshibaBAK/': Input/output error
ls: reading directory '/mnt/toshibaBAK/': Input/output error
ls: reading directory '/mnt/toshibaBAK/': Input/output error
ls: reading directory '/mnt/toshibaBAK/': Input/output error
ls: reading directory '/mnt/toshibaBAK/': Input/output error
ls: reading directory '/mnt/toshibaBAK/': Input/output error
ls: reading directory '/mnt/toshibaBAK/': Input/output error
ls: reading directory '/mnt/toshibaBAK/': Input/output error
ls: reading directory '/mnt/toshibaBAK/': Input/output error
ls: reading directory '/mnt/toshibaBAK/': Input/output error
ls: reading directory '/mnt/toshibaBAK/': Input/output error
ls: reading directory '/mnt/toshibaBAK/': Input/output error
ls: reading directory '/mnt/toshibaBAK/': Input/output error
ls: reading directory '/mnt/toshibaBAK/': Input/output error
ls: reading directory '/mnt/toshibaBAK/': Input/output error
touch: cannot touch '/mnt/toshibaBAK//2019-08-06/.complete': Read-only file system

Code: Select all

[  822.008240] xhci-hcd xhci-hcd.0.auto: xHCI host not responding to stop endpoint command.
[  822.008250] xhci-hcd xhci-hcd.0.auto: Assuming host is dying, halting host.
[  822.024274] xhci-hcd xhci-hcd.0.auto: Host not halted after 16000 microseconds.
[  822.024284] xhci-hcd xhci-hcd.0.auto: Non-responsive xHCI host is not halting.
[  822.024291] xhci-hcd xhci-hcd.0.auto: Completing active URBs anyway.
[  822.024426] xhci-hcd xhci-hcd.0.auto: HC died; cleaning up
[  822.024440] hub 2-1.3:1.0: hub_ext_port_status failed (err = -108)
[  822.024455] usb 2-1.3-port1: cannot reset (err = -108)
[  822.024465] usb 2-1.3-port1: cannot reset (err = -108)
[  822.024473] usb 2-1.3-port1: cannot reset (err = -108)
[  822.024481] usb 2-1.3-port1: cannot reset (err = -108)
[  822.024489] usb 2-1.3-port1: cannot reset (err = -108)
[  822.024493] usb 2-1.3-port1: Cannot enable. Maybe the USB cable is bad?
[  822.024504] usb 2-1.3-port1: cannot disable (err = -108)
[  822.024517] hub 2-1.3:1.0: hub_ext_port_status failed (err = -108)
[  822.024526] usb 2-1.3-port1: cannot reset (err = -108)
[  822.024535] usb 2-1.3-port1: cannot reset (err = -108)
[  822.024543] usb 2-1.3-port1: cannot reset (err = -108)
[  822.024551] usb 2-1.3-port1: cannot reset (err = -108)
[  822.024559] usb 2-1.3-port1: cannot reset (err = -108)
[  822.024562] usb 2-1.3-port1: Cannot enable. Maybe the USB cable is bad?
[  822.024571] usb 2-1.3-port1: cannot disable (err = -108)
[  822.024584] hub 2-1.3:1.0: hub_ext_port_status failed (err = -108)
[  822.024593] usb 2-1.3-port1: cannot reset (err = -108)
[  822.024601] usb 2-1.3-port1: cannot reset (err = -108)
[  822.024609] usb 2-1.3-port1: cannot reset (err = -108)
[  822.024617] usb 2-1.3-port1: cannot reset (err = -108)
[  822.024625] usb 2-1.3-port1: cannot reset (err = -108)
[  822.024628] usb 2-1.3-port1: Cannot enable. Maybe the USB cable is bad?
[  822.024637] usb 2-1.3-port1: cannot disable (err = -108)
[  822.024650] hub 2-1.3:1.0: hub_ext_port_status failed (err = -108)
[  822.024659] usb 2-1.3-port1: cannot reset (err = -108)
[  822.024667] usb 2-1.3-port1: cannot reset (err = -108)
[  822.024675] usb 2-1.3-port1: cannot reset (err = -108)
[  822.024683] usb 2-1.3-port1: cannot reset (err = -108)
[  822.024691] usb 2-1.3-port1: cannot reset (err = -108)
[  822.024694] usb 2-1.3-port1: Cannot enable. Maybe the USB cable is bad?
[  822.024703] usb 2-1.3-port1: cannot disable (err = -108)
[  822.024712] usb 2-1.3-port1: cannot disable (err = -108)
[  822.024785] hub 2-1.3:1.0: hub_ext_port_status failed (err = -108)
[  822.216198] xhci-hcd xhci-hcd.0.auto: xHCI host not responding to stop endpoint command.
[  822.216206] xhci-hcd xhci-hcd.0.auto: Assuming host is dying, halting host.
[  822.216309] xhci-hcd xhci-hcd.0.auto: HC died; cleaning up
[  822.222793] usb 1-1: USB disconnect, device number 2
[  822.222806] usb 1-1.3: USB disconnect, device number 3
[  822.226875] usb 2-1: USB disconnect, device number 2
[  822.226887] usb 2-1.3: USB disconnect, device number 3
[  822.226895] usb 2-1.3.1: USB disconnect, device number 4
[  822.228332] blk_update_request: I/O error, dev sda, sector 1675460360
[  822.229419] blk_update_request: I/O error, dev sda, sector 1675460392
[  822.236085] blk_update_request: I/O error, dev sda, sector 1675460424
[  822.243226] blk_update_request: I/O error, dev sda, sector 1675460456
[  822.249947] blk_update_request: I/O error, dev sda, sector 1675460504
[  822.256521] blk_update_request: I/O error, dev sda, sector 1675460568
[  822.262535] EXT4-fs warning (device sda1): ext4_end_bio:313: I/O error -5 writing to inode 141820178 (offset 2852126720 size 8388608 starting block 209432576)
[  822.262543] Buffer I/O error on device sda1, logical block 209432064
[  822.268967] Buffer I/O error on device sda1, logical block 209432065
[  822.275377] Buffer I/O error on device sda1, logical block 209432066
[  822.281785] Buffer I/O error on device sda1, logical block 209432067
[  822.288394] Buffer I/O error on device sda1, logical block 209432068
[  822.294856] Buffer I/O error on device sda1, logical block 209432069
[  822.301273] Buffer I/O error on device sda1, logical block 209432070
[  822.307863] Buffer I/O error on device sda1, logical block 209432071
[  822.314295] Buffer I/O error on device sda1, logical block 209432072
[  822.320876] Buffer I/O error on device sda1, logical block 209432073
[  822.327685] blk_update_request: I/O error, dev sda, sector 1675460608
[  822.333941] blk_update_request: I/O error, dev sda, sector 2927903888
[  822.340562] blk_update_request: I/O error, dev sda, sector 1675460624
[  822.347118] blk_update_request: I/O error, dev sda, sector 2927903904
[  822.356404] EXT4-fs warning (device sda1): ext4_end_bio:313: I/O error -5 writing to inode 141820178 (offset 2852126720 size 8388608 starting block 209432832)
[  822.358516] EXT4-fs warning (device sda1): ext4_end_bio:313: I/O error -5 writing to inode 141820178 (offset 2860515328 size 2101248 starting block 209433088)
[  822.360183] EXT4-fs warning (device sda1): ext4_end_bio:313: I/O error -5 writing to inode 141820178 (offset 2860515328 size 3149824 starting block 209433344)
[  822.362300] EXT4-fs warning (device sda1): ext4_end_bio:313: I/O error -5 writing to inode 141820178 (offset 2860515328 size 4198400 starting block 209433600)
[  822.363823] EXT4-fs warning (device sda1): ext4_end_bio:313: I/O error -5 writing to inode 141820178 (offset 2860515328 size 5246976 starting block 209433856)
[  822.365784] EXT4-fs warning (device sda1): ext4_end_bio:313: I/O error -5 writing to inode 141820178 (offset 2860515328 size 6295552 starting block 209434112)
[  822.367129] EXT4-fs warning (device sda1): ext4_end_bio:313: I/O error -5 writing to inode 141820178 (offset 2860515328 size 7344128 starting block 209434368)
[  822.368336] sd 1:0:0:0: [sdb] tag#0 FAILED Result: hostbyte=DID_ERROR driverbyte=DRIVER_OK
[  822.368345] sd 1:0:0:0: [sdb] tag#0 CDB: Read(16) 88 00 00 00 00 00 03 31 25 d8 00 00 00 20 00 00
[  822.369597] EXT4-fs warning (device sda1): ext4_end_bio:313: I/O error -5 writing to inode 141820178 (offset 2860515328 size 8388608 starting block 209434624)
[  822.374415] EXT4-fs warning (device sda1): ext4_end_bio:313: I/O error -5 writing to inode 141820178 (offset 2860515328 size 8388608 starting block 209434880)
[  822.386330] JBD2: Detected IO errors while flushing file data on sda1-8
[  822.386346] Aborting journal on device sda1-8.
[  822.386408] Buffer I/O error on dev sda1, logical block 365985792, lost sync page write
[  822.393541] Buffer I/O error on dev sda1, logical block 0, lost sync page write
[  822.400932] EXT4-fs error (device sda1): ext4_journal_check_start:56: Detected aborted journal
[  822.401279] JBD2: Error -5 detected when updating journal superblock for sda1-8.
[  822.401310] JBD2: Detected IO errors while flushing file data on sda1-8
[  822.417261] EXT4-fs (sda1): Remounting filesystem read-only
[  822.424304] EXT4-fs (sda1): previous I/O error to superblock detected
[  822.429664] Buffer I/O error on dev sda1, logical block 0, lost sync page write
[  822.437005] EXT4-fs (sda1): ext4_writepages: jbd2_start: 9223372036854775807 pages, ino 141820178; err -30
[  822.446956] Buffer I/O error on dev sda1, logical block 209190914, lost async page write
[  822.452278] sd 1:0:0:0: [sdb] tag#0 FAILED Result: hostbyte=DID_ERROR driverbyte=DRIVER_OK
[  822.452289] sd 1:0:0:0: [sdb] tag#0 CDB: Read(16) 88 00 00 00 00 00 03 31 25 f8 00 00 00 08 00 00
[  822.455463] Buffer I/O error on dev sda1, logical block 209190915, lost async page write
[  822.463472] Buffer I/O error on dev sda1, logical block 209190916, lost async page write
[  822.471590] Buffer I/O error on dev sda1, logical block 209190917, lost async page write
[  822.494842] sd 0:0:0:0: [sda] Synchronizing SCSI cache
[  822.501092] sd 0:0:0:0: [sda] Synchronize Cache(10) failed: Result: hostbyte=DID_NO_CONNECT driverbyte=DRIVER_OK
[  822.525089] usb 2-1.3.2: USB disconnect, device number 5
[  822.591421] sd 1:0:0:0: [sdb] Synchronizing SCSI cache
[  822.591481] sd 1:0:0:0: [sdb] Synchronize Cache(10) failed: Result: hostbyte=DID_NO_CONNECT driverbyte=DRIVER_OK
[  829.578844] EXT4-fs error (device sdb1): ext4_find_entry:1454: inode #72876298: comm rsync: reading directory lblock 0
[  829.835096] EXT4-fs warning: 4 callbacks suppressed
[  829.835101] EXT4-fs warning (device sda1): htree_dirblock_to_tree:976: inode #2: lblock 0: comm ls: error -5 reading directory block
[  829.836508] EXT4-fs warning (device sda1): htree_dirblock_to_tree:976: inode #2: lblock 0: comm ls: error -5 reading directory block
[  829.855713] EXT4-fs warning (device sda1): htree_dirblock_to_tree:976: inode #2: lblock 0: comm ls: error -5 reading directory block
[  829.871589] EXT4-fs warning (device sda1): htree_dirblock_to_tree:976: inode #2: lblock 0: comm ls: error -5 reading directory block
[  829.888001] EXT4-fs warning (device sda1): htree_dirblock_to_tree:976: inode #2: lblock 0: comm ls: error -5 reading directory block
[  829.899945] EXT4-fs warning (device sda1): htree_dirblock_to_tree:976: inode #2: lblock 0: comm ls: error -5 reading directory block
[  829.911932] EXT4-fs warning (device sda1): htree_dirblock_to_tree:976: inode #2: lblock 0: comm ls: error -5 reading directory block
[  829.923371] EXT4-fs warning (device sda1): htree_dirblock_to_tree:976: inode #2: lblock 0: comm ls: error -5 reading directory block
[  829.933981] EXT4-fs warning (device sda1): htree_dirblock_to_tree:976: inode #2: lblock 0: comm ls: error -5 reading directory block
[  829.947003] EXT4-fs warning (device sda1): htree_dirblock_to_tree:976: inode #2: lblock 0: comm ls: error -5 reading directory block
[  830.177998] EXT4-fs error (device sda1): ext4_find_entry:1454: inode #141819905: comm touch: reading directory lblock 0
But doing more testing something weird happened to me. I did try on my current OS image (the one I've been running since I got the N2) to run the backup command without touching the max_sectors_size_kb file, and it succeded for 3 times in a row, so what I did to ensure everything was fine was to uncompress the 7z file to rsync the 4gb 7z archive and a 28 Gb img archive, again to make sure everything was running fine. This time I got and error again (same as in the clean image) so I don't know what to think about.

Anyway, the rsync command that I use is this one:

Code: Select all

rsync -av --progress --link-dest ${LASTDAYPATH} ${DATADIR} ${TODAYPATH}
It only transfers archives with different timestamp or new, so today I know it has to backup that 4Gb 7z file, and if I keep it, the 28 Gb img file. I don't have any RAID, just two mounted EXT4 drives. The only thing that seems stable to me is set max_sectors_size_kb to 8

elatllat
Posts: 1502
Joined: Tue Sep 01, 2015 8:54 am
languages_spoken: english
ODROIDs: XU4, N1, N2
Has thanked: 21 times
Been thanked: 45 times
Contact:

Re: Syncing two UAS devices causes Ubuntu to hang

Unread post by elatllat » Wed Aug 07, 2019 4:52 am

Jay4692 wrote:
Wed Aug 07, 2019 3:33 am
...

Code: Select all

[  822.008250] xhci-hcd xhci-hcd.0.auto: Assuming host is dying, halting host.
...
So the same as Nighti.
Jay4692 wrote:
Wed Aug 07, 2019 3:33 am
...The only thing that seems stable to me is set max_sectors_size_kb to 8...
I think you mean

Code: Select all

echo 8 > /sys/class/block/sda/queue/max_sectors_kb
Any interesting mkfs.ext4 options or just the default?

(Edit; see Nighti's comment below)
Last edited by elatllat on Wed Aug 07, 2019 5:11 am, edited 2 times in total.

User avatar
Nighti
Posts: 39
Joined: Tue Sep 13, 2016 11:59 am
languages_spoken: english
ODROIDs: XU4, N2
Has thanked: 1 time
Been thanked: 3 times
Contact:

Re: Syncing two UAS devices causes Ubuntu to hang

Unread post by Nighti » Wed Aug 07, 2019 5:02 am

@Jay4692: Please run this commands and post it here.

Code: Select all

cat /sys/kernel/debug/aml_clkmsr/clkmsr | grep clk81
cat /proc/cmdline
dmesg | grep sg_tablesize
My issue is resolved with the most recent kernel/boot.ini and USB3.0
These users thanked the author Nighti for the post:
elatllat (Wed Aug 07, 2019 5:03 am)

Jay4692
Posts: 16
Joined: Sat Jun 29, 2019 6:31 pm
languages_spoken: english, spanish
ODROIDs: N2
Has thanked: 6 times
Been thanked: 3 times
Contact:

Re: Syncing two UAS devices causes Ubuntu to hang

Unread post by Jay4692 » Wed Aug 07, 2019 5:46 am

elatllat wrote:
Wed Aug 07, 2019 4:52 am
Jay4692 wrote:
Wed Aug 07, 2019 3:33 am
...

Code: Select all

[  822.008250] xhci-hcd xhci-hcd.0.auto: Assuming host is dying, halting host.
...
So the same as Nighti.
Jay4692 wrote:
Wed Aug 07, 2019 3:33 am
...The only thing that seems stable to me is set max_sectors_size_kb to 8...
I think you mean

Code: Select all

echo 8 > /sys/class/block/sda/queue/max_sectors_kb
Any interesting mkfs.ext4 options or just the default?

(Edit; see Nighti's comment below)
Yes, I did meant echo 8 > /sys/class/block/sda/queue/max_sectors_kb, I got confused, sorry about that. It's strange that just less than a month ago I could use 16 value, but with recent updates I have to reduce it to 8.

No, I didn't use any options, just default.
Nighti wrote:
Wed Aug 07, 2019 5:02 am
@Jay4692: Please run this commands and post it here.

Code: Select all

cat /sys/kernel/debug/aml_clkmsr/clkmsr | grep clk81
cat /proc/cmdline
dmesg | grep sg_tablesize
My issue is resolved with the most recent kernel/boot.ini and USB3.0
Here are the results:

Code: Select all

cat /sys/kernel/debug/aml_clkmsr/clkmsr | grep clk81
[ 7][ 222000000]clk81

Code: Select all

cat /proc/cmdline
root=UUID=e139ce78-9841-40fe-8823-96a304a09859 rootwait rw console=ttyS0,115200n8  no_console_suspend fsck.repair=yes net.ifnames=0 elevator=noop hdmimode=1080p60hz cvbsmode=576cvbs max_freq_a53=1896 max_freq_a73=1800 maxcpus=6 voutmode=hdmi  disablehpd=false cvbscable=0 overscan=100  monitor_onoff=false usb-xhci.tablesize=2 logo=osd0,loaded

Code: Select all

dmesg | grep sg_tablesize
[    4.775573] usb: xhci: determined sg_tablesize: 2
[    4.846903] usb: xhci: determined sg_tablesize: 2
Other thing I noticed, when the rsync completed correctly the speed was stable at around 40 MB/s, but in the run that rsync crashed it was going from 20 MB/s to 50 MB/s in incremental steps of speed, then again from 50 MB/s to 20 MB/s again in decremental steps and just before the crash the speed bump up to 200 MB/s (maybe because it already lost target drive so transfer speed went crazy...)

Happy to see that other problems are resolved with recent updates, makes me not to lose hope.

Thanks everyone.

User avatar
Nighti
Posts: 39
Joined: Tue Sep 13, 2016 11:59 am
languages_spoken: english
ODROIDs: XU4, N2
Has thanked: 1 time
Been thanked: 3 times
Contact:

Re: Syncing two UAS devices causes Ubuntu to hang

Unread post by Nighti » Wed Aug 07, 2019 5:53 am

Looks good to me. Please also make sure to reset max_sectors_kb to default value.
Please also post this commands:
# lsusb
# lsusb -t
Is the drive self powered or external?

Jay4692
Posts: 16
Joined: Sat Jun 29, 2019 6:31 pm
languages_spoken: english, spanish
ODROIDs: N2
Has thanked: 6 times
Been thanked: 3 times
Contact:

Re: Syncing two UAS devices causes Ubuntu to hang

Unread post by Jay4692 » Wed Aug 07, 2019 6:09 am

Nighti wrote:
Wed Aug 07, 2019 5:53 am
Looks good to me. Please also make sure to reset max_sectors_kb to default value.
Please also post this commands:
# lsusb
# lsusb -t
Is the drive self powered or external?
Yes, I set default value to max_sectors_kb everytime rsync ends. (In my case the first time I started to change the value in this file was 1024, so I set to 8 before rsync and when it ends I set it back to 1024)

Here are the results:

Code: Select all

lsusb
Bus 002 Device 005: ID 0480:0900 Toshiba America Inc
Bus 002 Device 004: ID 0480:a202 Toshiba America Inc Canvio Basics HDD
Bus 002 Device 003: ID 2109:0813 VIA Labs, Inc.
Bus 002 Device 002: ID 05e3:0620 Genesys Logic, Inc.
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 003: ID 2109:2813 VIA Labs, Inc.
Bus 001 Device 002: ID 05e3:0610 Genesys Logic, Inc. 4-port hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

Code: Select all

lsusb -t
/:  Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci-hcd/1p, 5000M
    |__ Port 1: Dev 2, If 0, Class=Hub, Driver=hub/4p, 5000M
        |__ Port 3: Dev 3, If 0, Class=Hub, Driver=hub/4p, 5000M
            |__ Port 1: Dev 4, If 0, Class=Mass Storage, Driver=usb-storage, 5000M
            |__ Port 2: Dev 5, If 0, Class=Mass Storage, Driver=usb-storage, 5000M
/:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci-hcd/2p, 480M
    |__ Port 1: Dev 2, If 0, Class=Hub, Driver=hub/4p, 480M
        |__ Port 3: Dev 3, If 0, Class=Hub, Driver=hub/4p, 480M
They are self powered, but they are connected to a powered USB 3.0 hub, RaspberryPi 3 couldn't supply enough voltage to both drives and when N2 arrived didn't have any reason not to use it, but as I said rsync fails even when drives are attached directly to the N2.

User avatar
Nighti
Posts: 39
Joined: Tue Sep 13, 2016 11:59 am
languages_spoken: english
ODROIDs: XU4, N2
Has thanked: 1 time
Been thanked: 3 times
Contact:

Re: Syncing two UAS devices causes Ubuntu to hang

Unread post by Nighti » Wed Aug 07, 2019 6:15 am

Maybe try not to touch max_sectors_kb at all. Reboot and keep original values.

Jay4692
Posts: 16
Joined: Sat Jun 29, 2019 6:31 pm
languages_spoken: english, spanish
ODROIDs: N2
Has thanked: 6 times
Been thanked: 3 times
Contact:

Re: Syncing two UAS devices causes Ubuntu to hang

Unread post by Jay4692 » Wed Aug 07, 2019 7:06 am

I did try not touching max_sectors_kb after a reboot, same result, rsync crashs. Also I did set the backup drive to be accessed the same way as my NAS drive and tried to simply copy a big file from one to the other through Windows Explorer with the same result.

It's getting late here, so I'm going to call it a night and tomorrow I will try some different variations with my current OS and the new fresh image, see if I can find a pattern, I will post if I find something interesting.

Thanks for the help.

elatllat
Posts: 1502
Joined: Tue Sep 01, 2015 8:54 am
languages_spoken: english
ODROIDs: XU4, N1, N2
Has thanked: 21 times
Been thanked: 45 times
Contact:

Re: Syncing two UAS devices causes Ubuntu to hang

Unread post by elatllat » Wed Aug 07, 2019 11:01 am

I was not able to reproduce any issues using rsync on the latest image,
but on the off chance it's related I did notice plugging in the USB cable to quickly results in never ending dmesg errors;

Code: Select all

[  548.874161] usb 2-1.1: reset SuperSpeed USB device number 4 using xhci-hcd
[  548.894627] sd 0:0:0:0: [sda] tag#0 FAILED Result: hostbyte=DID_ERROR driverbyte=DRIVER_OK
[  548.894636] sd 0:0:0:0: [sda] tag#0 CDB: Read(10) 28 00 00 00 03 00 00 00 90 00
[  548.894640] blk_update_request: I/O error, dev sda, sector 768
[  549.050099] usb 2-1.1: reset SuperSpeed USB device number 4 using xhci-hcd
BTRFS crashed it after 32KB but we can ignore that.

I assume the buggy USB is due to the closed source binaries here.
Maybe AmLogic can be convinced to open source them :lol:

User avatar
Nighti
Posts: 39
Joined: Tue Sep 13, 2016 11:59 am
languages_spoken: english
ODROIDs: XU4, N2
Has thanked: 1 time
Been thanked: 3 times
Contact:

Re: Syncing two UAS devices causes Ubuntu to hang

Unread post by Nighti » Wed Aug 07, 2019 11:30 am

My fileserver system is also running with 4 x USB3.0 disks stable for one week now. No I/O errors to report.

User avatar
odroid
Site Admin
Posts: 32146
Joined: Fri Feb 22, 2013 11:14 pm
languages_spoken: English
ODROIDs: ODROID
Has thanked: 119 times
Been thanked: 297 times
Contact:

Re: Syncing two UAS devices causes Ubuntu to hang

Unread post by odroid » Wed Aug 07, 2019 11:49 am

@Jay4692,
Can you please try other thick and short USB 3.0 cables?
When we used some low quality cables, the eye-diagram USB 3.0 signal integrity test was failed and it caused random XHCI transfer errors.
USB3_eye_diagram.png
USB3_eye_diagram.png (99.65 KiB) Viewed 1229 times

joshua.yang
Posts: 243
Joined: Fri Sep 22, 2017 5:54 pm
languages_spoken: Korean, English
ODROIDs: XU4, XU4Q + Cloudshell2, H2, N2
Has thanked: 2 times
Been thanked: 24 times
Contact:

Re: Syncing two UAS devices causes Ubuntu to hang

Unread post by joshua.yang » Wed Aug 07, 2019 11:58 am

xabolcs wrote:
Tue Aug 06, 2019 8:27 pm
f3write & f3read in a true loop will be enough, as f3write removes all dump files from the directory automatically

Code: Select all

root@odroid:~# f3write /mnt/mdp/h2w/
F3 write 7.0
Copyright (C) 2010 Digirati Internet LTDA.
This is free software; see the source for copying conditions.

Removing old file 1.h2w ...
Removing old file 2.h2w ...
Removing old file 3.h2w ...
Free space: 97.81 GB
Creating file 1.h2w ... OK!                           
Creating file 2.h2w ... OK!   
.
.
.
Okay, I checked that f3write command removes old existing dump files.
Wrote a script that doing a loop for fwrite / fread. And it logs the loop counts and their outputs to a log file.

It looks stable so far. Here are the current results.

Code: Select all

root@odroid:~/scripts/load test# grep -iE "speed|count" f3_test.log
===== Loop count: 1 =====
Average writing speed: 98.94 MB/s
Average reading speed: 174.75 MB/s
===== Loop count: 2 =====
Average writing speed: 96.59 MB/s
Average reading speed: 174.87 MB/s
===== Loop count: 3 =====
Average writing speed: 97.07 MB/s
Average reading speed: 175.31 MB/s
===== Loop count: 4 =====
Average writing speed: 96.97 MB/s
Average reading speed: 175.21 MB/s
===== Loop count: 5 =====
Average writing speed: 96.52 MB/s
Average reading speed: 175.36 MB/s
===== Loop count: 6 =====

nick793
Posts: 26
Joined: Mon Jun 24, 2019 9:35 pm
languages_spoken: english
ODROIDs: N2, GO
Has thanked: 0
Been thanked: 2 times
Contact:

Re: Syncing two UAS devices causes Ubuntu to hang

Unread post by nick793 » Wed Aug 07, 2019 10:21 pm

I don't know why, but I was able to move 1TB of files from one drive local to the N2 to an NFS share over a few hours - no problems.

However, if I attempt to run a checksum on anything I crash my USB in minutes.

Jay4692
Posts: 16
Joined: Sat Jun 29, 2019 6:31 pm
languages_spoken: english, spanish
ODROIDs: N2
Has thanked: 6 times
Been thanked: 3 times
Contact:

Re: Syncing two UAS devices causes Ubuntu to hang

Unread post by Jay4692 » Wed Aug 07, 2019 11:39 pm

Some updates.

I'm trying with a fresh os (latest version posted here), this are the only things I did to the OS:

1 - Create user and add it to sudo group.
2 - Change password of root user.
3 - Login in created user.

Then I did two tests, the first would be to rsync an archive without mounting any drive with etc/fstab (just default /media/usbn) and the second one mounting both drives by uuid. First test, without mounting the drives in etc/fstab, gave me max transfer speeds of 3.91 Mb/s (more than 30 minutes to transfer a 4 Gb file), didn't have enough patience to end transfer, but not usable anyways, even if its stable. Then I mounted the drives in etc/fstab as follows and rebooted:

Code: Select all

UUID=uuid_of_drive /mnt/toshibaNAS ext4 defaults 0 0
UUID=uuid_of_drive /mnt/toshibaBAK ext4 defaults 0 0
Tried the same test with rsync, speeds where normal USB 3.0 ( aprox 80 Mb/s) but after just 10 seconds drives hang up and rsync fails to complete. So I'm just curious, how do you mount the drives to a particular folder? Any options to consider in fstab, or created folder inside /media or /mnt? Maybe my problems are related to this, just guessing.

EDIT: I did some more testing, mounting the drives in fstab with option sync give me max speeds of 3.91 Mb/s, when I did change it for async the transfer speeds where normal for USB 3.0 but wasn't stable.

Code: Select all

UUID=uuid_of_drive /mnt/toshibaBAK ext4 auto,async 0 0
UUID=uuid_of_drive /mnt/toshibaNAS ext4 auto,async 0 0
odroid wrote:
Wed Aug 07, 2019 11:49 am
@Jay4692,
Can you please try other thick and short USB 3.0 cables?
When we used some low quality cables, the eye-diagram USB 3.0 signal integrity test was failed and it caused random XHCI transfer errors.
USB3_eye_diagram.png
At the moment I don't have any other microUSB 3.0 cables, I only have the ones that came with the drives. I will try as a last resource, but I didn't have any reasons to blame the cables, because in my desktop computer attaching both drives to the back USB 3.0 motherboard ports and copying huge loads of data with these original cables didn't gave me any problems.

EDIT 2: After reading some similar problems in a RockPro64 github I just bought two new microUSB 3.0 thick 0.5 meters cables and a new 12V 2A power supply, I bought my Odroid from odroid.co.uk and it came with a 12v 1.5A power supply, maybe all this is related to bad cables and defective power supply after all. I will try tomorrow with this new hardware, see if it helps with the problem.

alvarow
Posts: 33
Joined: Wed Apr 10, 2019 10:44 pm
languages_spoken: english
ODROIDs: N2
Has thanked: 14 times
Been thanked: 1 time
Contact:

Re: Syncing two UAS devices causes Ubuntu to hang

Unread post by alvarow » Thu Aug 08, 2019 9:51 am

Hi ... I'd like to add that I've been getting reboots on my N2 ... I can reproduce it fairly easily but I don't think it has to do with two UAS devices ...

In my scenario, I have a 10TB WD Elements (so a powered USB3.0 drive) connected to a 4GB N2, booting off eMMC and I am using the power adapter, not the USB charging port to power the N2.

I wanted to use the device to backup my NAS over the ethernet port... I tried over NFS, SMB2 and rsyncd (on the NAS)... the USB drive is formatted as XFS and sometimes I get a couple of minutes of transfers in, and sometimes just a few seconds and the N2 reboots.

I managed to save some dmesg output, that happens before the reboot. There is no slow downs or lock ups... it simply reboots.

I tried to slow the transfer speed by using rsync with --bwlimit=25000 and it still crashes. Seems with I use --bwlimit=5000 it works (so far about 2 hours).

Tell what you want me to do to help, or if you think this is not related, I'll start a new thread.

PS - fully updated and rebooted. Attached dmesg output from 4.9.184-37, I rather not crash it again, but I'll do it if needed.

thanks!
Attachments
dmesg-n2-4.9.184-37.log.gz
(44.63 KiB) Downloaded 11 times

User avatar
odroid
Site Admin
Posts: 32146
Joined: Fri Feb 22, 2013 11:14 pm
languages_spoken: English
ODROIDs: ODROID
Has thanked: 119 times
Been thanked: 297 times
Contact:

Re: Syncing two UAS devices causes Ubuntu to hang

Unread post by odroid » Thu Aug 08, 2019 10:00 am

@alvarow,
Thank you for the log file.
But please flash the latest image to have a exactly same test condition since some users reported the boot blobs and other tweaks couldn't be updated by uncertain reasons.

@Jay4692,
Once you receive new cables, please share the test result again.

alvarow
Posts: 33
Joined: Wed Apr 10, 2019 10:44 pm
languages_spoken: english
ODROIDs: N2
Has thanked: 14 times
Been thanked: 1 time
Contact:

Re: Syncing two UAS devices causes Ubuntu to hang

Unread post by alvarow » Thu Aug 08, 2019 10:37 am

Oh no :-( I spent time tweaking it, getting nginx migrated from my previous SBC, etc... I'll do it though.

I just got this as well (on yesterday's kernel)
Does this mean anything to you guys?

Code: Select all

[   38.893292] ------------[ cut here ]------------
[   38.893319] WARNING: CPU: 1 PID: 0 at cgroup_get+0xcc/0xf0
[   38.893323] Modules linked in: xfs rpcsec_gss_krb5 nfsv4 ipt_MASQUERADE tun nf_nat_masquerade_ipv4 iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nfs nf_nat_ipv4 nf_nat nf_conntrack fscache cpufreq_ondemand cpufreq_powersave cpufreq_userspace cpufreq_conservative squashfs ip6table_filter ip6_tables iptable_filter rtc_pcf8563 ir_lirc_codec lirc_dev i2c_meson_master meson_ir sch_fq_codel amvdec_vp9 amvdec_vc1 amvdec_real amvdec_mmpeg4 amvdec_mpeg4 amvdec_mpeg12 amvdec_mmjpeg amvdec_mjpeg amvdec_h265 amvdec_h264mvc amvdec_mh264 amvdec_h264 amvdec_avs stream_input decoder_common firmware media_clock nfsd auth_rpcgss nfs_acl lockd grace sunrpc ip_tables x_tables ipv6

[   38.893489] CPU: 1 PID: 0 Comm: swapper/1 Not tainted 4.9.187-52 #1
[   38.893493] Hardware name: Hardkernel ODROID-N2 (DT)
[   38.893498] task: ffffffc0ca9daa00 task.stack: ffffffc0ca9e8000
[   38.893507] PC is at cgroup_get+0xcc/0xf0
[   38.893516] LR is at cgroup_sk_alloc+0x48/0xb0
[   38.893532] ------------[ cut here ]------------
[   38.893544] WARNING: CPU: 1 PID: 0 at vmalloc_to_page+0xd8/0xe8
[   38.893546] Modules linked in: xfs rpcsec_gss_krb5 nfsv4 ipt_MASQUERADE tun nf_nat_masquerade_ipv4 iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nfs nf_nat_ipv4 nf_nat nf_conntrack fscache cpufreq_ondemand cpufreq_powersave cpufreq_userspace cpufreq_conservative squashfs ip6table_filter ip6_tables iptable_filter rtc_pcf8563 ir_lirc_codec lirc_dev i2c_meson_master meson_ir sch_fq_codel amvdec_vp9 amvdec_vc1 amvdec_real amvdec_mmpeg4 amvdec_mpeg4 amvdec_mpeg12 amvdec_mmjpeg amvdec_mjpeg amvdec_h265 amvdec_h264mvc amvdec_mh264 amvdec_h264 amvdec_avs stream_input decoder_common firmware media_clock nfsd auth_rpcgss nfs_acl lockd grace sunrpc ip_tables x_tables ipv6

[   38.893683] CPU: 1 PID: 0 Comm: swapper/1 Not tainted 4.9.187-52 #1
[   38.893686] Hardware name: Hardkernel ODROID-N2 (DT)
[   38.893691] task: ffffffc0ca9daa00 task.stack: ffffffc0ca9e8000
[   38.893699] PC is at vmalloc_to_page+0xd8/0xe8
[   38.893707] LR is at __show_regs+0xb0/0x3b0
[   38.893714] pc : [<ffffff80092020a0>] lr : [<ffffff80090860e0>] pstate: 800003c5
[   38.893717] sp : ffffffc0cf32c5f0
Attachments
dmesg-n2-4.9.187-52.log.gz
(22.41 KiB) Downloaded 8 times

elatllat
Posts: 1502
Joined: Tue Sep 01, 2015 8:54 am
languages_spoken: english
ODROIDs: XU4, N1, N2
Has thanked: 21 times
Been thanked: 45 times
Contact:

Re: Syncing two UAS devices causes Ubuntu to hang

Unread post by elatllat » Thu Aug 08, 2019 11:48 am

alvarow wrote:
Thu Aug 08, 2019 10:37 am
Oh no :-( I spent time tweaking it...
an install script is worth more than a backup so

Code: Select all

history > install.sh
then edit into a runnable state.

Try a test on eMMC/sdCard (loopback FS optionaly) to see if the reboots are USB related. (I did notice them with 4.9 btrfs but not with 5.3 and assumed they were not USB related but did not test XFS)

alvarow
Posts: 33
Joined: Wed Apr 10, 2019 10:44 pm
languages_spoken: english
ODROIDs: N2
Has thanked: 14 times
Been thanked: 1 time
Contact:

Re: Syncing two UAS devices causes Ubuntu to hang

Unread post by alvarow » Fri Aug 09, 2019 12:27 am

I'll take an image of the eMMC and then restore it back :-) this is Linux, if I update the kernel, it is updated, I don't see the point in re-imaging just to get new packages, but I'll humor you guys.

eMMC is ext4, as is the image from Hard Kernel.

thanks!

alvarow
Posts: 33
Joined: Wed Apr 10, 2019 10:44 pm
languages_spoken: english
ODROIDs: N2
Has thanked: 14 times
Been thanked: 1 time
Contact:

Re: Syncing two UAS devices causes Ubuntu to hang

Unread post by alvarow » Fri Aug 09, 2019 12:32 am

So I logged back into the Odroid this morning, yesterday I left `screen` running rsync with the latest kernel, and it was able to sync everything, no reboot. I did get several kernel traces on `dmesg`, but no reboots at full gigabit speed. I am busy at work, I'll report back with results as soon as I have time to toy with it again, but I expect the same behavior.

thanks for the help so far!

Jay4692
Posts: 16
Joined: Sat Jun 29, 2019 6:31 pm
languages_spoken: english, spanish
ODROIDs: N2
Has thanked: 6 times
Been thanked: 3 times
Contact:

Re: Syncing two UAS devices causes Ubuntu to hang

Unread post by Jay4692 » Fri Aug 09, 2019 2:52 am

Hi,

I tried to rsync some big files with the new power supply and cables for the drives and for me it still fails with the new image. I also tested to do the same rsync in my laptop with Ubuntu 18.04 and it got better speeds (110 MB/s to 120 MB/s compared to the 30MB/s to 70MB/s in the N2) and it did complete a transfer of 36 Gb without any problems over the hub, where on the N2 it crashes after around a minute of transfer.
For the records I did try different combinations, always with the new image:

- The two drives attached to the hub.
- Two drives directly attached to the N2. (To test if there was an issue with the hub itself)
- One drive on the hub, one drive on the N2 (to reduce undervoltage issues)

I did also try a fresh image of Armbian with the same results. At this point I don't know what else to try, there is no hardware issue on the drives, cables or hub, because they work without any problems and faster on my desktop and laptop, so maybe the only solution for me is continue to set max_sectors_size to 8 and live with USB 2.0 transfer speeds between drives as now I'm well over the return period of the store I bought the N2 from.
These users thanked the author Jay4692 for the post (total 2):
alvarow (Fri Aug 09, 2019 5:21 am) • rooted (Tue Aug 13, 2019 12:24 pm)

alvarow
Posts: 33
Joined: Wed Apr 10, 2019 10:44 pm
languages_spoken: english
ODROIDs: N2
Has thanked: 14 times
Been thanked: 1 time
Contact:

Re: Syncing two UAS devices causes Ubuntu to hang

Unread post by alvarow » Fri Aug 09, 2019 5:22 am

I haven't re-imaged mine yet... but I have been hammering it with transfers, I get CPU cut here traces on fresh reboots without doing anything... but it no longer crashes. Was this some instrumentation added to Aug 6th kernel release? or that's something harmful going on?

nick793
Posts: 26
Joined: Mon Jun 24, 2019 9:35 pm
languages_spoken: english
ODROIDs: N2, GO
Has thanked: 0
Been thanked: 2 times
Contact:

Re: Syncing two UAS devices causes Ubuntu to hang

Unread post by nick793 » Fri Aug 09, 2019 7:36 am

odroid wrote:
Wed Aug 07, 2019 11:49 am
@Jay4692,
Can you please try other thick and short USB 3.0 cables?
When we used some low quality cables, the eye-diagram USB 3.0 signal integrity test was failed and it caused random XHCI transfer errors.
USB3_eye_diagram.png
I'm sorry to say this, but this points squarely at a hardware issue with the N2. I've used three HDD enclosures with the USB cables they shipped with reliably on my Pi 3B+/Pi 4/Windows laptop. When I use them on the N2 I run into all the errors I described in my previous replies. If the eye is not good and the same cable/drive is used on multiple devices without issue that indicates the N2 has a signal integrity problem or perhaps a noisy power supply.

As for my tests, I moved 1TB multiple times from the N2 (RAID1 with 2 disks) to my Pi 4 (RAID5 with 3 disks). No errors during the transfer or reboots. Now that I have my data in a safe spot I'll try and crash the N2 by running checksums on the old data and report back. This is still the most reliable way for me to break the USB.

elatllat
Posts: 1502
Joined: Tue Sep 01, 2015 8:54 am
languages_spoken: english
ODROIDs: XU4, N1, N2
Has thanked: 21 times
Been thanked: 45 times
Contact:

Re: Syncing two UAS devices causes Ubuntu to hang

Unread post by elatllat » Fri Aug 09, 2019 7:44 am

nick793 wrote:
Fri Aug 09, 2019 7:36 am
...points squarely at a hardware issue...
maybe but so far only 1 user had a USB crash with the new img.

Jay4692
Posts: 16
Joined: Sat Jun 29, 2019 6:31 pm
languages_spoken: english, spanish
ODROIDs: N2
Has thanked: 6 times
Been thanked: 3 times
Contact:

Re: Syncing two UAS devices causes Ubuntu to hang

Unread post by Jay4692 » Fri Aug 09, 2019 7:47 am

nick793 wrote:
Fri Aug 09, 2019 7:36 am
odroid wrote:
Wed Aug 07, 2019 11:49 am
@Jay4692,
Can you please try other thick and short USB 3.0 cables?
When we used some low quality cables, the eye-diagram USB 3.0 signal integrity test was failed and it caused random XHCI transfer errors.
USB3_eye_diagram.png
I'm sorry to say this, but this points squarely at a hardware issue with the N2. I've used three HDD enclosures with the USB cables they shipped with reliably on my Pi 3B+/Pi 4/Windows laptop. When I use them on the N2 I run into all the errors I described in my previous replies. If the eye is not good and the same cable/drive is used on multiple devices without issue that indicates the N2 has a signal integrity problem or perhaps a noisy power supply.
...
As I said, for me it's still the same, crashes while trying to rsync files between drives, even with a powered USB 3.0 hub (drives don't receive any power until I plugin the 36W power supply to the hub) so it's strange that it's related to power supply issues, as far as I know. And it happens the same to me, same drives, same hub and same cables works reliable in my laptop and desktop even with more speed than I can achieve (before crashes) on the N2.

I don't have another SBC with USB 3.0 to test, and if is not a hardware problem with the N2, the only difference I see with Odroid or other people is that I use an SD Card, instead of the eMMC module, who knows

User avatar
Nighti
Posts: 39
Joined: Tue Sep 13, 2016 11:59 am
languages_spoken: english
ODROIDs: XU4, N2
Has thanked: 1 time
Been thanked: 3 times
Contact:

Re: Syncing two UAS devices causes Ubuntu to hang

Unread post by Nighti » Fri Aug 09, 2019 7:53 am

I can rule out the SD card. Mine is also running on SD card.
These users thanked the author Nighti for the post:
Jay4692 (Fri Aug 09, 2019 7:54 am)

Jay4692
Posts: 16
Joined: Sat Jun 29, 2019 6:31 pm
languages_spoken: english, spanish
ODROIDs: N2
Has thanked: 6 times
Been thanked: 3 times
Contact:

Re: Syncing two UAS devices causes Ubuntu to hang

Unread post by Jay4692 » Fri Aug 09, 2019 7:55 am

Nighti wrote:
Fri Aug 09, 2019 7:53 am
I can rule out the SD card. Mine is also running on SD card.
That leaves me without any ideas.

Thanks for the info

qcasey1
Posts: 24
Joined: Thu Apr 18, 2019 7:29 am
languages_spoken: english
ODROIDs: XU4, N2
Location: California
Has thanked: 5 times
Been thanked: 0
Contact:

Re: Syncing two UAS devices causes Ubuntu to hang

Unread post by qcasey1 » Fri Aug 09, 2019 9:25 am

Jay4692 wrote:
Fri Aug 09, 2019 2:52 am
I also tested to do the same rsync in my laptop with Ubuntu 18.04 and it got better speeds (110 MB/s to 120 MB/s compared to the 30MB/s to 70MB/s in the N2) and it did complete a transfer of 36 Gb without any problems over the hub, where on the N2 it crashes after around a minute of transfer.
Similar thing here. I'm on the new image, EMMC, no crashes yet but the same drive / cable that gets 110+MB/s on my laptop is at a max of 40MB/s on the N2. This new image I'm at least getting 38-40 instead of the peak 30 from the previous. Not sure if that's a coincidence or not

elatllat
Posts: 1502
Joined: Tue Sep 01, 2015 8:54 am
languages_spoken: english
ODROIDs: XU4, N1, N2
Has thanked: 21 times
Been thanked: 45 times
Contact:

Re: Syncing two UAS devices causes Ubuntu to hang

Unread post by elatllat » Fri Aug 09, 2019 10:55 am

So as the new img has fixed USB crashing for everyone except Jay4692, maybe Jay4692 can give us a sample script to crash a fresh img, or test the 5.3 kernel.

nick793
Posts: 26
Joined: Mon Jun 24, 2019 9:35 pm
languages_spoken: english
ODROIDs: N2, GO
Has thanked: 0
Been thanked: 2 times
Contact:

Re: Syncing two UAS devices causes Ubuntu to hang

Unread post by nick793 » Fri Aug 09, 2019 8:16 pm

elatllat wrote:
Fri Aug 09, 2019 7:44 am
nick793 wrote:
Fri Aug 09, 2019 7:36 am
...points squarely at a hardware issue...
maybe but so far only 1 user had a USB crash with the new img.
I would test but I'm leaving for a week and can't knock my system offline during that time. I did use apt upgrade to get up to the latest image but I realize there are flaws with that approach. That being said, I was able to knock my system offline by verifying torrents with Transmission and to my knowledge that just runs a ton of small checksums on the files.
qcasey1 wrote:
Fri Aug 09, 2019 9:25 am
Jay4692 wrote:
Fri Aug 09, 2019 2:52 am
I also tested to do the same rsync in my laptop with Ubuntu 18.04 and it got better speeds (110 MB/s to 120 MB/s compared to the 30MB/s to 70MB/s in the N2) and it did complete a transfer of 36 Gb without any problems over the hub, where on the N2 it crashes after around a minute of transfer.
Similar thing here. I'm on the new image, EMMC, no crashes yet but the same drive / cable that gets 110+MB/s on my laptop is at a max of 40MB/s on the N2. This new image I'm at least getting 38-40 instead of the peak 30 from the previous. Not sure if that's a coincidence or not
While I hope it's just a software issue, the fact that the speeds are capped so low on the N2 suggests either buggy software (which is what we're all trying to identify with this thread), a signal integrity issue with the USB 3.0 controller, or a noisy power supply. If the power supply is too noisy and the filtering on the power input to the USB controller is not enough to compensate, then that would also be a potential signal integrity issue. If HK themselves are seeing eye issues depending on the cable that's a bad sign. I realize the cheap cables are usually crap and will cause problems, but I don't have the tools to measure the eye diagram of every device I plug in to make sure it's the cable and not the N2. For myself personally, I use the cables the device came with which tend to be thicker than usual. I also use a 12V/2A power supply from Ameridroid but I don't know how noisy it is.

Edit: I should amend this statement. Edited above to indicate it could also be a power supply problem as well since we all have different power supplies.
Last edited by nick793 on Sat Aug 10, 2019 12:06 am, edited 1 time in total.

qcasey1
Posts: 24
Joined: Thu Apr 18, 2019 7:29 am
languages_spoken: english
ODROIDs: XU4, N2
Location: California
Has thanked: 5 times
Been thanked: 0
Contact:

Re: Syncing two UAS devices causes Ubuntu to hang

Unread post by qcasey1 » Fri Aug 09, 2019 11:45 pm

That would be a shame, no USB3 ports would really kill this board for me. At this point I'd even take only 1 or 2 ports at USB3 speeds like the pi 4. Better than none

Post Reply

Return to “Issues”

Who is online

Users browsing this forum: shanti and 2 guests