network IO issue with Ubuntu 20.04 on RPI4

Sat Jul 3 15:29:10 UTC 2021

Hi Colin,

Errors like below.  I tried with another, new, USB stick.  I am planning 
on trying another brand too. I also tried using an SSD (but that one 
seemed to get pretty warm)..  and am not sure, but the SSD made the RPI 
crash pretty often (wonder if that's a power (shortage) issue, since the 
SSD probably uses more power than a USB stick ?

here are some errors I see when trying to copy data off the USB stick:

Ron

/var/log/kern.log.1:Jun 23 11:04:24 seismo kernel: [682577.174599] 
EXT4-fs error (device sda1) in ext4_da_write_end:3213: IO failure
/var/log/kern.log.1:Jun 23 11:04:29 seismo kernel: [682582.102163] 
EXT4-fs error (device sda1): ext4_journal_check_start:61: Detected 
aborted journal
/var/log/kern.log.1:Jun 23 11:08:00 seismo kernel: [ 1.075156] 
bcm2708_fb: probe of soc:fb failed with error -2
/var/log/kern.log.1:Jun 24 17:27:25 seismo kernel: [ 1.082231] 
bcm2708_fb: probe of soc:fb failed with error -2
/var/log/syslog.1:Jul  2 09:47:50 seismo kernel: [67572.665930] 
ieee80211 phy1: rt2x00usb_vendor_request: Error - Vendor Request 0x07 
failed for offset 0x1700 with error -71
/var/log/syslog.1:Jul  2 09:47:50 seismo kernel: [67573.184012] sd 
0:0:0:0: [sda] tag#0 FAILED Result: hostbyte=DID_ERROR driverbyte=DRIVER_OK
/var/log/syslog.1:Jul  2 09:47:50 seismo kernel: [67573.184048] 
blk_update_request: I/O error, dev sda, sector 29879250 op 0x1:(WRITE) 
flags 0x800 phys_seg 2 prio class 0
/var/log/syslog.1:Jul  2 09:47:50 seismo kernel: [67573.307997] sd 
0:0:0:0: [sda] tag#0 FAILED Result: hostbyte=DID_ERROR driverbyte=DRIVER_OK
/var/log/syslog.1:Jul  2 09:47:50 seismo kernel: [67573.308033] 
blk_update_request: I/O error, dev sda, sector 29622306 op 0x1:(WRITE) 
flags 0x800 phys_seg 1 prio class 0
/var/log/syslog.1:Jul  2 09:47:50 seismo kernel: [67573.318950] Buffer 
I/O error on dev sda1, logical block 3702784, lost sync page write
/var/log/syslog.1:Jul  2 09:47:50 seismo kernel: [67573.326939] JBD2: 
Error -5 detected when updating journal superblock for sda1-8.
/var/log/syslog.1:Jul  2 09:47:50 seismo kernel: [67573.340483] 
blk_update_request: I/O error, dev sda, sector 60088192 op 0x0:(READ) 
flags 0x80700 phys_seg 1 prio class 0
/var/log/syslog.1:Jul  2 09:47:50 seismo kernel: [67573.357663] 
blk_update_request: I/O error, dev sda, sector 60088192 op 0x0:(READ) 
flags 0x0 phys_seg 1 prio class 0
/var/log/syslog.1:Jul  2 09:47:50 seismo kernel: [67573.368301] Buffer 
I/O error on dev sda, logical block 7511024, async page read
/var/log/syslog.1:Jul  2 09:47:50 seismo multipathd[1602]: uevent 
trigger error
/var/log/syslog.1:Jul  2 09:47:52 seismo kernel: [67574.717553] 
blk_update_request: I/O error, dev sda, sector 34 op 0x1:(WRITE) flags 
0x800 phys_seg 1 prio class 0
/var/log/syslog.1:Jul  2 09:47:52 seismo kernel: [67574.727954] Buffer 
I/O error on dev sda1, logical block 0, lost sync page write
/var/log/syslog.1:Jul  2 09:47:52 seismo kernel: [67574.735440] EXT4-fs 
(sda1): I/O error while writing superblock
/var/log/syslog.1:Jul  2 09:47:52 seismo kernel: [67574.741426] EXT4-fs 
error (device sda1): ext4_journal_check_start:61: Detected aborted journal

On 7/3/21 7:33 AM, Colin Law wrote:
> What are the IO errors?
>
> Colin
>
> On Fri, 2 Jul 2021, 23:07 R C, <cjvijf at gmail.com 
> <mailto:cjvijf at gmail.com>> wrote:
>
>     Hello,
>
>
>     I am running Ubuntu 20.04 on an RPI4, for data collection
>
>
>     I am using a USB connected wifi dongle with long range antenna,  a
>     USB
>     connection to an AD board, and a USB stick (formatted ext4) for
>     storing
>     captured data from the AD board
>
>
>     When I try to scp data off the USB stick to somewhere else, another
>     machine, the RPI gets really slow, I do see some IO errors in
>     syslog and
>     at times the RPI even 'freezes'.
>
>     When I boot the same hardware with an SD card that has centos 7
>     installed it seems to work (not lightning fast, but consistently
>     works).
>
>     (Centos 7 is 32bit btw.)
>
>
>
>     Ubuntu 20.04 is 64bit (which I want to keep using because the data
>     logger seems to work more stable/reliable when it comes to
>     capturing data)
>
>
>     Any ideas what might be causing this?  or where to start looking?
>
>
>     thanks,
>
>
>     Ron
>
>
>     -- 
>     ubuntu-users mailing list
>     ubuntu-users at lists.ubuntu.com <mailto:ubuntu-users at lists.ubuntu.com>
>     Modify settings or unsubscribe at:
>     https://lists.ubuntu.com/mailman/listinfo/ubuntu-users
>     <https://lists.ubuntu.com/mailman/listinfo/ubuntu-users>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.ubuntu.com/archives/ubuntu-users/attachments/20210703/5c603377/attachment.html>