Preparing for a Prototype


Grench

Forum Addict!
Joined
Oct 3, 2008
Messages
6,623
root@MarbleSD:/home/grench/Desktop#
Post automatically merged:

And if you can boot into an OS from the left SD Card slot, doing an fsck on /dev/mmcblk0p1 and /dev/mmcblk0p2 would be great.
If the eMMC has issues, these I/O errors should appear there as well.

If fsck doesn't report any errors, the the eMMC should be fine.
Booted from left SD slot.
fdisk-l shows from pretty wild stuff dealing with multiple ramdisks.
fsck /dev/mmcblk0p1 shows the device as mounted - should it be mounted at all since I am booted from the SD card slot?

root@MarbleSD:/home/grench/Desktop# fdisk -l
Disk /dev/ram0: 16 MiB, 16777216 bytes, 32768 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes


Disk /dev/ram1: 16 MiB, 16777216 bytes, 32768 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes


Disk /dev/ram2: 16 MiB, 16777216 bytes, 32768 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes


Disk /dev/ram3: 16 MiB, 16777216 bytes, 32768 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes


Disk /dev/ram4: 16 MiB, 16777216 bytes, 32768 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes


Disk /dev/ram5: 16 MiB, 16777216 bytes, 32768 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes


Disk /dev/ram6: 16 MiB, 16777216 bytes, 32768 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes


Disk /dev/ram7: 16 MiB, 16777216 bytes, 32768 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes


Disk /dev/ram8: 16 MiB, 16777216 bytes, 32768 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes


Disk /dev/ram9: 16 MiB, 16777216 bytes, 32768 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes


Disk /dev/ram10: 16 MiB, 16777216 bytes, 32768 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes


Disk /dev/ram11: 16 MiB, 16777216 bytes, 32768 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes


Disk /dev/ram12: 16 MiB, 16777216 bytes, 32768 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes


Disk /dev/ram13: 16 MiB, 16777216 bytes, 32768 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes


Disk /dev/ram14: 16 MiB, 16777216 bytes, 32768 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes


Disk /dev/ram15: 16 MiB, 16777216 bytes, 32768 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes


Disk /dev/mmcblk3: 59.6 GiB, 64021856256 bytes, 125042688 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0xf23ef208

Device Boot Start End Sectors Size Id Type
/dev/mmcblk3p1 * 2048 526335 524288 256M 83 Linux
/dev/mmcblk3p2 526336 16777215 16250880 7.8G 83 Linux


Disk /dev/mmcblk0: 29.1 GiB, 31268536320 bytes, 61071360 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0x5bdc0a86

Device Boot Start End Sectors Size Id Type
/dev/mmcblk0p1 * 2048 526335 524288 256M 83 Linux
/dev/mmcblk0p2 526336 61071359 60545024 28.9G 83 Linux
root@MarbleSD:/home/grench/Desktop# fsck /dev/mmcblk0p1
fsck from util-linux 2.33.1
e2fsck 1.44.5 (15-Dec-2018)
/dev/mmcblk0p1 is mounted.
e2fsck: Cannot continue, aborting.

Here are the exciting umount commands and the results of the fsck on both eMMC partitions:

Note - I connected the SD card booted Pyra to my home network and copied/pasted the results of everything in the spoiler tags in this message into a post here to merge in.

root@MarbleSD:/home/grench/Desktop# umount /dev/mmcblk0p1
root@MarbleSD:/home/grench/Desktop# umount /dev/mmcblk0p2
root@MarbleSD:/home/grench/Desktop# fsck /dev/mmcblk0p1
fsck from util-linux 2.33.1
e2fsck 1.44.5 (15-Dec-2018)
boot has gone 7303 days without being checked, check forced.
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information
boot: 265/65536 files (93.2% non-contiguous), 37176/262144 blocks
root@MarbleSD:/home/grench/Desktop# fsck /dev/mmcblk0p2
fsck from util-linux 2.33.1
Info: Segments per section = 1
Info: Sections per zone = 1
Info: sector size = 512
Info: total sectors = 60545024 (29563 MB)
Info: MKFS version
"Linux version 4.19.60-letux-lpae-pyra-nobat (pyra@debian-buster) (gcc version 8.3.0 (Debian 8.3.0-2)) #1 SMP PREEMPT Tue Dec 17 01:00:43 CET 2019"
Info: FSCK version
from "Linux version 4.19.60-letux-lpae-pyra-nobat (pyra@debian-buster) (gcc version 8.3.0 (Debian 8.3.0-2)) #1 SMP PREEMPT Tue Dec 17 01:00:43 CET 2019"
to "Linux version 4.19.88-letux-lpae (pyra@debian-buster) (gcc version 8.3.0 (Debian 8.3.0-2)) #1 SMP PREEMPT Fri Dec 13 20:15:40 CET 2019"
Info: superblock features = 0 :
Info: superblock encrypt level = 0, salt = 00000000000000000000000000000000
Info: total FS sectors = 60545024 (29563 MB)
Info: CKPT version = 6029e7fc
Info: checkpoint state = 55 : crc fsck compacted_summary unmount

[FSCK] Unreachable nat entries [Ok..] [0x0]
[FSCK] SIT valid block bitmap checking [Ok..]
[FSCK] Hard link checking for regular file [Ok..] [0xb]
[FSCK] valid_block_count matching with CP [Ok..] [0xdec7b]
[FSCK] valid_node_count matcing with CP (de lookup) [Ok..] [0x2bfc7]
[FSCK] valid_node_count matcing with CP (nat lookup) [Ok..] [0x2bfc7]
[FSCK] valid_inode_count matched with CP [Ok..] [0x2bedc]
[FSCK] free segment_count matched with CP [Ok..] [0x3218]
[FSCK] next block offset is free [Ok..]
[FSCK] fixing SIT types
[FSCK] other corrupted bugs [Ok..]
Info: Write valid nat_bits in checkpoint

Done.
root@MarbleSD:/home/grench/Desktop#
 
Last edited:
  • Like
Reactions: rSl

Grench

Forum Addict!
Joined
Oct 3, 2008
Messages
6,623
Alright - up and running now with both the eMMC and via a card in the left SD card slot.

Issue: SD card partitioned out by the SD card OS writer inefficiently.

SD OS card has two partitions. According to fdisk -l for sizes and blkid /dev/mmcblk3p1(2) for reporting the formats:
/dev/mmcblk3p1 is ext4 and 256M
/dev/mmcblk3p2 is f2fs and 7.8G
The card is 64GB. Without using Gparted - or parted for that matter - does anyone have a good way to extend/expand/stretch that f2fs partition to the rest of the card?

Why is it f2fs anyway instead of keeping the OS on a simplified all ext4 model?

Rebooted into the eMMC to see what the OS loaded to it has. According to fdisk -l for sizes and blkid for reporting the formats:
/dev/mmcblk0p1 is ext2 and 256M
/dev/mmcblk0p2 is f2fs and 28.9G

So - ext2 on the eMMC Vs ext4 on the SD image for the boot partition. Another difference between the eMMC installer OS and the SD card bootable OS. At least the eMMC installer partitions to match the card.

So, any linux partitioning genius want to help me with the command to expand out that f2fs partition on the SD image?
Post automatically merged:

Differences between the eMMC image and the SD card image.
eMMC boot is ext2. SD boot is ext4.
eMMC OS does NOT result in a left shoulder shift button or the brightness button working for me - apparently isn't launching funkey monkey right?
eMMC OS battery statistics get double lined and out of whack. They seem to be functioning on the SD card OS.
eMMC running on my desktop is starting to flake out as I type this. I'll load up the minicom log.
eMMC shutdown onscreen menu is now full of nothing but squares/boxes again.
eMMC shutdown failed again.
# minicom


Welcome to minicom 2.7

OPTIONS: I18n
Compiled on Apr 22 2017, 09:14:19.
Port /dev/ttyUSB0, 17:20:28

Press CTRL-A Z for help on special keys


[ 572.489627] bq24296_usb_detect: r8=84 ADAP PWRGOOD r9=01 HOT
[ 573.832186] systemd-journald[1337]: Failed to rotate /var/log/journal/2ea02fr
[ 573.845626] systemd-journald[1337]: Failed to rotate /var/log/journal/2ea02fr
[ 573.860642] systemd-journald[1337]: Failed to write entry (21 items, 619 bytr
[ 573.872967] systemd-journald[1337]: Failed to rotate /var/log/journal/2ea02fr
[ 573.886373] systemd-journald[1337]: Failed to rotate /var/log/journal/2ea02fr
[ 573.910229] systemd-journald[1337]: Failed to write entry (21 items, 601 bytr
[ 573.922796] systemd-journald[1337]: Failed to rotate /var/log/journal/2ea02fr
[ 573.936679] systemd-journald[1337]: Failed to rotate /var/log/journal/2ea02fr
[ 573.952221] systemd-journald[1337]: Failed to write entry (21 items, 619 bytr
[ 573.966144] systemd-journald[1337]: Failed to rotate /var/log/journal/2ea02fr
[ 574.569603] bq24296_usb_detect: r8=8c ADAP INDPM PWRGOOD r9=01 HOT
[ 576.499306] bq2729x_chg_irq_func
[ 576.502725] bq2729x_irq_work_func: di = ed3f5440
[ 576.510632] bq24296_usb_detect: r8=8c ADAP INDPM PWRGOOD r9=81 WDOG HOT
[ 576.520720] bq2729x_irq_work_func: r8=8c r9=81
[ 579.780979] bq24296_usb_detect: r8=84 ADAP PWRGOOD r9=81 WDOG HOT
[ 579.800179] systemd-journald[1337]: Failed to rotate /var/log/journal/2ea02fr
[ 579.824418] systemd-journald[1337]: Failed to rotate /var/log/journal/2ea02fr
[ 579.843225] systemd-journald[1337]: Failed to write entry (9 items, 267 byter
[ 579.888486] systemd-journald[1337]: Failed to rotate /var/log/journal/2ea02fr
[ 579.907786] systemd-journald[1337]: Failed to rotate /var/log/journal/2ea02fr
[ 579.930511] systemd-journald[1337]: Failed to write entry (21 items, 619 bytr
[ 579.944949] systemd-journald[1337]: Failed to rotate /var/log/journal/2ea02fr
[ 579.966457] systemd-journald[1337]: Failed to rotate /var/log/journal/2ea02fr
[ 579.995171] systemd-journald[1337]: Failed to write entry (21 items, 601 bytr
[ 580.031041] systemd-journald[1337]: Failed to rotate /var/log/journal/2ea02fr
[ 582.889503] bq24296_usb_detect: r8=8c ADAP INDPM PWRGOOD r9=81 WDOG HOT
[ 585.830260] systemd-journald[1337]: Failed to rotate /var/log/journal/2ea02fr
[ 585.845116] systemd-journald[1337]: Failed to rotate /var/log/journal/2ea02fr
[ 585.861179] systemd-journald[1337]: Failed to write entry (21 items, 619 bytr
[ 585.874801] systemd-journald[1337]: Failed to rotate /var/log/journal/2ea02fr
[ 585.888942] systemd-journald[1337]: Failed to rotate /var/log/journal/2ea02fr
[ 585.904230] systemd-journald[1337]: Failed to write entry (21 items, 601 bytr
[ 585.917213] systemd-journald[1337]: Failed to rotate /var/log/journal/2ea02fr
[ 585.931652] systemd-journald[1337]: Failed to rotate /var/log/journal/2ea02fr
[ 585.946858] systemd-journald[1337]: Failed to write entry (21 items, 619 bytr
[ 585.958001] systemd-journald[1337]: Failed to rotate /var/log/journal/2ea02fr
[ 590.170049] bq24296_usb_detect: r8=84 ADAP PWRGOOD r9=81 WDOG HOT
[ 591.835268] systemd-journald[1337]: Failed to rotate /var/log/journal/2ea02fr
[ 591.849447] systemd-journald[1337]: Failed to rotate /var/log/journal/2ea02fr
[ 591.865812] systemd-journald[1337]: Failed to write entry (21 items, 619 bytr
[ 591.880766] systemd-journald[1337]: Failed to rotate /var/log/journal/2ea02fr
[ 591.894257] systemd-journald[1337]: Failed to rotate /var/log/journal/2ea02fr
[ 591.910791] systemd-journald[1337]: Failed to write entry (21 items, 601 bytr
[ 591.924891] systemd-journald[1337]: Failed to rotate /var/log/journal/2ea02fr
[ 591.938684] systemd-journald[1337]: Failed to rotate /var/log/journal/2ea02fr
[ 591.954748] systemd-journald[1337]: Failed to write entry (21 items, 619 bytr
[ 591.969510] systemd-journald[1337]: Failed to rotate /var/log/journal/2ea02fr
[ 593.289472] bq24296_usb_detect: r8=8c ADAP INDPM PWRGOOD r9=81 WDOG HOT
[ 597.830669] systemd-journald[1337]: Failed to rotate /var/log/journal/2ea02fr
[ 597.843912] systemd-journald[1337]: Failed to rotate /var/log/journal/2ea02fr
[ 597.857964] systemd-journald[1337]: Failed to write entry (21 items, 619 bytr
[ 597.869327] systemd-journald[1337]: Failed to rotate /var/log/journal/2ea02fr
[ 597.882421] systemd-journald[1337]: Failed to rotate /var/log/journal/2ea02fr
[ 597.896360] systemd-journald[1337]: Failed to write entry (21 items, 601 bytr
[ 597.907703] systemd-journald[1337]: Failed to rotate /var/log/journal/2ea02fr
[ 597.920827] systemd-journald[1337]: Failed to rotate /var/log/journal/2ea02fr
[ 597.935058] systemd-journald[1337]: Failed to write entry (21 items, 619 bytr
[ 597.946625] systemd-journald[1337]: Failed to rotate /var/log/journal/2ea02fr
[ 598.490007] bq24296_usb_detect: r8=84 ADAP PWRGOOD r9=81 WDOG HOT
[ 600.569645] bq24296_usb_detect: r8=8c ADAP INDPM PWRGOOD r9=81 WDOG HOT
[ 603.830302] systemd-journald[1337]: Failed to rotate /var/log/journal/2ea02fr
[ 603.843353] systemd-journald[1337]: Failed to rotate /var/log/journal/2ea02fr
[ 603.857255] systemd-journald[1337]: Failed to write entry (21 items, 619 bytr
[ 603.868291] systemd-journald[1337]: Failed to rotate /var/log/journal/2ea02fr
[ 603.881339] systemd-journald[1337]: Failed to rotate /var/log/journal/2ea02fr
[ 603.895018] systemd-journald[1337]: Failed to write entry (21 items, 601 bytr
[ 603.906003] systemd-journald[1337]: Failed to rotate /var/log/journal/2ea02fr
[ 603.919035] systemd-journald[1337]: Failed to rotate /var/log/journal/2ea02fr
[ 603.932730] systemd-journald[1337]: Failed to write entry (21 items, 619 bytr
[ 603.943719] systemd-journald[1337]: Failed to rotate /var/log/journal/2ea02fr
[ 606.810065] bq24296_usb_detect: r8=84 ADAP PWRGOOD r9=81 WDOG HOT
[ 609.830455] systemd-journald[1337]: Failed to rotate /var/log/journal/2ea02fr
[ 609.843514] systemd-journald[1337]: Failed to rotate /var/log/journal/2ea02fr
[ 609.857529] systemd-journald[1337]: Failed to write entry (21 items, 619 bytr
[ 609.868584] systemd-journald[1337]: Failed to rotate /var/log/journal/2ea02fr
[ 609.881694] systemd-journald[1337]: Failed to rotate /var/log/journal/2ea02fr
[ 609.895428] systemd-journald[1337]: Failed to write entry (21 items, 600 bytr
[ 609.906412] systemd-journald[1337]: Failed to rotate /var/log/journal/2ea02fr
[ 609.919443] systemd-journald[1337]: Failed to rotate /var/log/journal/2ea02fr
[ 609.929328] bq24296_usb_detect: r8=8c ADAP INDPM PWRGOOD r9=81 WDOG HOT
[ 609.933161] systemd-journald[1337]: Failed to write entry (21 items, 619 bytr
[ 609.950320] systemd-journald[1337]: Failed to rotate /var/log/journal/2ea02fr
[ 615.129594] bq24296_usb_detect: r8=84 ADAP PWRGOOD r9=81 WDOG HOT
[ 615.139820] systemd-journald[1337]: Failed to rotate /var/log/journal/2ea02fr
[ 615.155713] systemd-journald[1337]: Failed to rotate /var/log/journal/2ea02fr
[ 615.180190] systemd-journald[1337]: Failed to write entry (9 items, 267 byter
[ 615.835191] systemd-journald[1337]: Failed to rotate /var/log/journal/2ea02fr
[ 615.859269] systemd-journald[1337]: Failed to rotate /var/log/journal/2ea02fr
[ 615.882321] systemd-journald[1337]: Failed to write entry (21 items, 619 bytr
[ 615.903763] systemd-journald[1337]: Failed to rotate /var/log/journal/2ea02fr
[ 615.921950] systemd-journald[1337]: Failed to rotate /var/log/journal/2ea02fr
[ 615.945227] systemd-journald[1337]: Failed to write entry (21 items, 601 bytr
[ 615.968830] systemd-journald[1337]: Failed to rotate /var/log/journal/2ea02fr
[ 617.209364] bq24296_usb_detect: r8=8c ADAP INDPM PWRGOOD r9=81 WDOG HOT
[ 621.830202] systemd-journald[1337]: Failed to rotate /var/log/journal/2ea02fr
[ 621.843399] systemd-journald[1337]: Failed to rotate /var/log/journal/2ea02fr
[ 621.857306] systemd-journald[1337]: Failed to write entry (21 items, 619 bytr
[ 621.868363] systemd-journald[1337]: Failed to rotate /var/log/journal/2ea02fr
[ 621.881415] systemd-journald[1337]: Failed to rotate /var/log/journal/2ea02fr
[ 621.895197] systemd-journald[1337]: Failed to write entry (21 items, 601 bytr
[ 621.906224] systemd-journald[1337]: Failed to rotate /var/log/journal/2ea02fr
[ 621.919281] systemd-journald[1337]: Failed to rotate /var/log/journal/2ea02fr
[ 621.932967] systemd-journald[1337]: Failed to write entry (21 items, 619 bytr
[ 621.943949] systemd-journald[1337]: Failed to rotate /var/log/journal/2ea02fr
[ 625.529760] bq24296_usb_detect: r8=84 ADAP PWRGOOD r9=81 WDOG HOT
[ 627.609211] bq24296_usb_detect: r8=8c ADAP INDPM PWRGOOD r9=81 WDOG HOT
[ 627.620458] systemd-journald[1337]: Failed to rotate /var/log/journal/2ea02fr
[ 627.636007] systemd-journald[1337]: Failed to rotate /var/log/journal/2ea02fr
[ 627.652690] systemd-journald[1337]: Failed to write entry (9 items, 273 byter
[ 627.830640] systemd-journald[1337]: Failed to rotate /var/log/journal/2ea02fr
[ 627.845732] systemd-journald[1337]: Failed to rotate /var/log/journal/2ea02fr
[ 627.861970] systemd-journald[1337]: Failed to write entry (21 items, 619 bytr
[ 627.874688] systemd-journald[1337]: Failed to rotate /var/log/journal/2ea02fr
[ 627.890539] systemd-journald[1337]: Failed to rotate /var/log/journal/2ea02fr
[ 627.906948] systemd-journald[1337]: Failed to write entry (21 items, 600 bytr
[ 627.920040] systemd-journald[1337]: Failed to rotate /var/log/journal/2ea02fr
[ 633.835378] systemd-journald[1337]: Failed to rotate /var/log/journal/2ea02fr
[ 633.849399] systemd-journald[1337]: Failed to rotate /var/log/journal/2ea02fr
[ 633.850658] bq24296_usb_detect: r8=84 ADAP PWRGOOD r9=81 WDOG HOT
[ 633.865933] systemd-journald[1337]: Failed to write entry (21 items, 619 bytr
[ 633.895839] systemd-journald[1337]: Failed to rotate /var/log/journal/2ea02fr
[ 633.915219] systemd-journald[1337]: Failed to rotate /var/log/journal/2ea02fr
[ 633.943174] systemd-journald[1337]: Failed to write entry (9 items, 267 byter
[ 633.962832] systemd-journald[1337]: Failed to rotate /var/log/journal/2ea02fr
[ 633.976928] systemd-journald[1337]: Failed to rotate /var/log/journal/2ea02fr
[ 633.993014] systemd-journald[1337]: Failed to write entry (21 items, 601 bytr
[ 634.007676] systemd-journald[1337]: Failed to rotate /var/log/journal/2ea02fr
[ 635.929554] bq24296_usb_detect: r8=8c ADAP INDPM PWRGOOD r9=81 WDOG HOT
[ 639.830347] systemd-journald[1337]: Failed to rotate /var/log/journal/2ea02fr
[ 639.843433] systemd-journald[1337]: Failed to rotate /var/log/journal/2ea02fr
[ 639.857302] systemd-journald[1337]: Failed to write entry (21 items, 619 bytr
[ 639.868356] systemd-journald[1337]: Failed to rotate /var/log/journal/2ea02fr
[ 639.881399] systemd-journald[1337]: Failed to rotate /var/log/journal/2ea02fr
[ 639.895082] systemd-journald[1337]: Failed to write entry (21 items, 601 bytr
[ 639.906107] systemd-journald[1337]: Failed to rotate /var/log/journal/2ea02fr
[ 639.919123] systemd-journald[1337]: Failed to rotate /var/log/journal/2ea02fr
[ 639.932800] systemd-journald[1337]: Failed to write entry (21 items, 619 bytr
[ 639.943772] systemd-journald[1337]: Failed to rotate /var/log/journal/2ea02fr
[ 642.170021] bq24296_usb_detect: r8=84 ADAP PWRGOOD r9=81 WDOG HOT
[ 644.249571] bq24296_usb_detect: r8=8c ADAP INDPM PWRGOOD r9=81 WDOG HOT
[ 645.830271] systemd-journald[1337]: Failed to rotate /var/log/journal/2ea02fr
[ 645.843314] systemd-journald[1337]: Failed to rotate /var/log/journal/2ea02fr
[ 645.857276] systemd-journald[1337]: Failed to write entry (21 items, 619 bytr
[ 645.868313] systemd-journald[1337]: Failed to rotate /var/log/journal/2ea02fr
[ 645.881356] systemd-journald[1337]: Failed to rotate /var/log/journal/2ea02fr
[ 645.895027] systemd-journald[1337]: Failed to write entry (21 items, 600 bytr
[ 645.906017] systemd-journald[1337]: Failed to rotate /var/log/journal/2ea02fr
[ 645.919011] systemd-journald[1337]: Failed to rotate /var/log/journal/2ea02fr
[ 645.932749] systemd-journald[1337]: Failed to write entry (21 items, 619 bytr
[ 645.943758] systemd-journald[1337]: Failed to rotate /var/log/journal/2ea02fr
[ 650.490072] bq24296_usb_detect: r8=84 ADAP PWRGOOD r9=81 WDOG HOT
[ 651.837264] systemd-journald[1337]: Failed to rotate /var/log/journal/2ea02fr
[ 651.851009] systemd-journald[1337]: Failed to rotate /var/log/journal/2ea02fr
[ 651.875756] systemd-journald[1337]: Failed to write entry (21 items, 619 bytr
[ 651.890346] systemd-journald[1337]: Failed to rotate /var/log/journal/2ea02fr
[ 651.904011] systemd-journald[1337]: Failed to rotate /var/log/journal/2ea02fr
[ 651.922444] systemd-journald[1337]: Failed to write entry (21 items, 601 bytr
[ 651.936924] systemd-journald[1337]: Failed to rotate /var/log/journal/2ea02fr
[ 651.951387] systemd-journald[1337]: Failed to rotate /var/log/journal/2ea02fr
[ 651.969624] systemd-journald[1337]: Failed to write entry (21 items, 619 bytr
[ 651.990784] systemd-journald[1337]: Failed to rotate /var/log/journal/2ea02fr
[ 652.569591] bq24296_usb_detect: r8=8c ADAP INDPM PWRGOOD r9=81 WDOG HOT
[ 657.832383] systemd-journald[1337]: Failed to rotate /var/log/journal/2ea02fr
[ 657.846685] systemd-journald[1337]: Failed to rotate /var/log/journal/2ea02fr
[ 657.864593] systemd-journald[1337]: Failed to write entry (21 items, 619 bytr
[ 657.882188] systemd-journald[1337]: Failed to rotate /var/log/journal/2ea02fr
[ 657.900682] systemd-journald[1337]: Failed to rotate /var/log/journal/2ea02fr
[ 657.921314] systemd-journald[1337]: Failed to write entry (21 items, 601 bytr
[ 657.939159] systemd-journald[1337]: Failed to rotate /var/log/journal/2ea02fr
[ 657.954617] systemd-journald[1337]: Failed to rotate /var/log/journal/2ea02fr
[ 657.972170] systemd-journald[1337]: Failed to write entry (21 items, 619 bytr
[ 657.988726] systemd-journald[1337]: Failed to rotate /var/log/journal/2ea02fr
[ 658.809656] bq24296_usb_detect: r8=84 ADAP PWRGOOD r9=81 WDOG HOT
[ 660.889203] bq24296_usb_detect: r8=8c ADAP INDPM PWRGOOD r9=81 WDOG HOT
[ 663.830203] systemd-journald[1337]: Failed to rotate /var/log/journal/2ea02fr
[ 663.843416] systemd-journald[1337]: Failed to rotate /var/log/journal/2ea02fr
[ 663.857278] systemd-journald[1337]: Failed to write entry (21 items, 619 bytr
[ 663.868304] systemd-journald[1337]: Failed to rotate /var/log/journal/2ea02fr
[ 663.881370] systemd-journald[1337]: Failed to rotate /var/log/journal/2ea02fr
[ 663.895068] systemd-journald[1337]: Failed to write entry (21 items, 601 bytr
[ 663.906087] systemd-journald[1337]: Failed to rotate /var/log/journal/2ea02fr
[ 663.919125] systemd-journald[1337]: Failed to rotate /var/log/journal/2ea02fr
[ 663.932965] systemd-journald[1337]: Failed to write entry (21 items, 619 bytr
[ 663.943959] systemd-journald[1337]: Failed to rotate /var/log/journal/2ea02fr
[ 667.129653] bq24296_usb_detect: r8=84 ADAP PWRGOOD r9=81 WDOG HOT
[ 669.209409] bq24296_usb_detect: r8=8c ADAP INDPM PWRGOOD r9=81 WDOG HOT
[ 669.219113] systemd-journald[1337]: Failed to rotate /var/log/journal/2ea02fr
[ 669.235091] systemd-journald[1337]: Failed to rotate /var/log/journal/2ea02fr
[ 669.251975] systemd-journald[1337]: Failed to write entry (9 items, 273 byter
[ 669.830292] systemd-journald[1337]: Failed to rotate /var/log/journal/2ea02fr
[ 669.844688] systemd-journald[1337]: Failed to rotate /var/log/journal/2ea02fr
[ 669.860102] systemd-journald[1337]: Failed to write entry (21 items, 619 bytr
[ 669.872536] systemd-journald[1337]: Failed to rotate /var/log/journal/2ea02fr
[ 669.886880] systemd-journald[1337]: Failed to rotate /var/log/journal/2ea02fr
[ 669.903058] systemd-journald[1337]: Failed to write entry (21 items, 600 bytr
[ 669.915701] systemd-journald[1337]: Failed to rotate /var/log/journal/2ea02fr
[ 675.450085] bq24296_usb_detect: r8=84 ADAP PWRGOOD r9=81 WDOG HOT
[ 675.459770] systemd-journald[1337]: Failed to rotate /var/log/journal/2ea02fr
[ 675.473966] systemd-journald[1337]: Failed to rotate /var/log/journal/2ea02fr
[ 675.491716] systemd-journald[1337]: Failed to write entry (9 items, 267 byter
[ 675.835271] systemd-journald[1337]: Failed to rotate /var/log/journal/2ea02fr
[ 675.849361] systemd-journald[1337]: Failed to rotate /var/log/journal/2ea02fr
[ 675.865961] systemd-journald[1337]: Failed to write entry (21 items, 619 bytr
[ 675.880428] systemd-journald[1337]: Failed to rotate /var/log/journal/2ea02fr
[ 675.894004] systemd-journald[1337]: Failed to rotate /var/log/journal/2ea02fr
[ 675.910311] systemd-journald[1337]: Failed to write entry (21 items, 601 bytr
[ 675.924467] systemd-journald[1337]: Failed to rotate /var/log/journal/2ea02fr
[ 677.529648] bq24296_usb_detect: r8=8c ADAP INDPM PWRGOOD r9=81 WDOG HOT
[ 679.065597] wlcore: down
[ 679.086339] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
[ 681.830163] systemd-journald[1337]: Failed to rotate /var/log/journal/2ea02fr
[ 681.843478] systemd-journald[1337]: Failed to rotate /var/log/journal/2ea02fr
[ 681.857213] systemd-journald[1337]: Failed to write entry (21 items, 619 bytr
[ 681.868273] systemd-journald[1337]: Failed to rotate /var/log/journal/2ea02fr
[ 681.881304] systemd-journald[1337]: Failed to rotate /var/log/journal/2ea02fr
[ 681.894960] systemd-journald[1337]: Failed to write entry (21 items, 601 bytr
[ 681.905971] systemd-journald[1337]: Failed to rotate /var/log/journal/2ea02fr
[ 681.919027] systemd-journald[1337]: Failed to rotate /var/log/journal/2ea02fr
[ 681.932778] systemd-journald[1337]: Failed to write entry (21 items, 619 bytr
[ 681.943777] systemd-journald[1337]: Failed to rotate /var/log/journal/2ea02fr
[ 683.770030] bq24296_usb_detect: r8=84 ADAP PWRGOOD r9=81 WDOG HOT
[ 685.849644] bq24296_usb_detect: r8=8c ADAP INDPM PWRGOOD r9=81 WDOG HOT
[ 687.830209] systemd-journald[1337]: Failed to rotate /var/log/journal/2ea02fr
[ 687.843279] systemd-journald[1337]: Failed to rotate /var/log/journal/2ea02fr
[ 687.857306] systemd-journald[1337]: Failed to write entry (21 items, 619 bytr
[ 687.868356] systemd-journald[1337]: Failed to rotate /var/log/journal/2ea02fr
[ 687.881430] systemd-journald[1337]: Failed to rotate /var/log/journal/2ea02fr
[ 687.895127] systemd-journald[1337]: Failed to write entry (21 items, 600 bytr
[ 687.906141] systemd-journald[1337]: Failed to rotate /var/log/journal/2ea02fr
[ 687.919188] systemd-journald[1337]: Failed to rotate /var/log/journal/2ea02fr
[ 687.932841] systemd-journald[1337]: Failed to write entry (21 items, 619 bytr
[ 687.943840] systemd-journald[1337]: Failed to rotate /var/log/journal/2ea02fr
[ 692.090239] bq24296_usb_detect: r8=84 ADAP PWRGOOD r9=81 WDOG HOT
[ 693.832510] systemd-journald[1337]: Failed to rotate /var/log/journal/2ea02fr
[ 693.847339] systemd-journald[1337]: Failed to rotate /var/log/journal/2ea02fr
[ 693.863463] systemd-journald[1337]: Failed to write entry (21 items, 619 bytr
[ 693.875823] systemd-journald[1337]: Failed to rotate /var/log/journal/2ea02fr
[ 693.890516] systemd-journald[1337]: Failed to rotate /var/log/journal/2ea02fr
[ 693.904732] systemd-journald[1337]: Failed to write entry (21 items, 600 bytr
[ 693.917486] systemd-journald[1337]: Failed to rotate /var/log/journal/2ea02fr
[ 693.930623] systemd-journald[1337]: Failed to rotate /var/log/journal/2ea02fr
[ 693.962697] systemd-journald[1337]: Failed to write entry (21 items, 619 bytr
[ 693.978543] systemd-journald[1337]: Failed to rotate /var/log/journal/2ea02fr
[ 694.169250] bq24296_usb_detect: r8=8c ADAP INDPM PWRGOOD r9=81 WDOG HOT
[ 699.832337] systemd-journald[1337]: Failed to rotate /var/log/journal/2ea02fr
[ 699.845791] systemd-journald[1337]: Failed to rotate /var/log/journal/2ea02fr
[ 699.860808] systemd-journald[1337]: Failed to write entry (21 items, 619 bytr
[ 699.873033] systemd-journald[1337]: Failed to rotate /var/log/journal/2ea02fr
[ 699.886319] systemd-journald[1337]: Failed to rotate /var/log/journal/2ea02fr
[ 699.900960] systemd-journald[1337]: Failed to write entry (21 items, 601 bytr
[ 699.913236] systemd-journald[1337]: Failed to rotate /var/log/journal/2ea02fr
[ 699.926491] systemd-journald[1337]: Failed to rotate /var/log/journal/2ea02fr
[ 699.941123] systemd-journald[1337]: Failed to write entry (21 items, 619 bytr
[ 699.953399] systemd-journald[1337]: Failed to rotate /var/log/journal/2ea02fr
[ 700.409601] bq24296_usb_detect: r8=84 ADAP PWRGOOD r9=81 WDOG HOT
[ 702.489260] bq24296_usb_detect: r8=8c ADAP INDPM PWRGOOD r9=81 WDOG HOT
[ 705.830267] systemd-journald[1337]: Failed to rotate /var/log/journal/2ea02fr
[ 705.843454] systemd-journald[1337]: Failed to rotate /var/log/journal/2ea02fr
[ 705.857312] systemd-journald[1337]: Failed to write entry (21 items, 619 bytr
[ 705.868363] systemd-journald[1337]: Failed to rotate /var/log/journal/2ea02fr
[ 705.881439] systemd-journald[1337]: Failed to rotate /var/log/journal/2ea02fr
[ 705.895113] systemd-journald[1337]: Failed to write entry (21 items, 601 bytr
[ 705.906182] systemd-journald[1337]: Failed to rotate /var/log/journal/2ea02fr
[ 705.919186] systemd-journald[1337]: Failed to rotate /var/log/journal/2ea02fr
[ 705.932857] systemd-journald[1337]: Failed to write entry (21 items, 619 bytr
[ 705.943859] systemd-journald[1337]: Failed to rotate /var/log/journal/2ea02fr
[ 708.729691] bq24296_usb_detect: r8=84 ADAP PWRGOOD r9=81 WDOG HOT
[ 711.830672] systemd-journald[1337]: Failed to rotate /var/log/journal/2ea02fr
[ 711.845946] systemd-journald[1337]: Failed to rotate /var/log/journal/2ea02fr
[ 711.849165] bq24296_usb_detect: r8=8c ADAP INDPM PWRGOOD r9=81 WDOG HOT
[ 711.859757] systemd-journald[1337]: Failed to write entry (21 items, 619 bytr
[ 711.878266] systemd-journald[1337]: Failed to rotate /var/log/journal/2ea02fr
[ 711.893076] systemd-journald[1337]: Failed to rotate /var/log/journal/2ea02fr
[ 711.910318] systemd-journald[1337]: Failed to write entry (9 items, 273 byter
[ 711.921354] systemd-journald[1337]: Failed to rotate /var/log/journal/2ea02fr
[ 711.934398] systemd-journald[1337]: Failed to rotate /var/log/journal/2ea02fr
[ 711.948112] systemd-journald[1337]: Failed to write entry (21 items, 600 bytr
[ 711.959185] systemd-journald[1337]: Failed to rotate /var/log/journal/2ea02fr
[ 717.049755] bq24296_usb_detect: r8=84 ADAP PWRGOOD r9=81 WDOG HOT
[ 717.059799] systemd-journald[1337]: Failed to rotate /var/log/journal/2ea02fr
[ 717.073956] systemd-journald[1337]: Failed to rotate /var/log/journal/2ea02fr
[ 717.100755] systemd-journald[1337]: Failed to write entry (9 items, 267 byter
[ 717.837549] systemd-journald[1337]: Failed to rotate /var/log/journal/2ea02fr
[ 717.859642] systemd-journald[1337]: Failed to rotate /var/log/journal/2ea02fr
[ 717.884452] systemd-journald[1337]: Failed to write entry (21 items, 619 bytr
[ 717.916138] systemd-journald[1337]: Failed to rotate /var/log/journal/2ea02fr
[ 717.935088] systemd-journald[1337]: Failed to rotate /var/log/journal/2ea02fr
[ 717.954300] systemd-journald[1337]: Failed to write entry (21 items, 619 bytr
[ 717.969157] systemd-journald[1337]: Failed to rotate /var/log/journal/2ea02fr
[ 719.129241] bq24296_usb_detect: r8=8c ADAP INDPM PWRGOOD r9=81 WDOG HOT
[ 722.498274] systemd-journald[1337]: Failed to rotate /var/log/journal/2ea02fr
[ 722.512140] systemd-journald[1337]: Failed to rotate /var/log/journal/2ea02fr
[ 722.526769] systemd-journald[1337]: Failed to write entry (28 items, 915 bytr
[ 722.538208] systemd-journald[1337]: Failed to rotate /var/log/journal/2ea02fr
[ 722.551302] systemd-journald[1337]: Failed to rotate /var/log/journal/2ea02fr
[ 722.565906] systemd-journald[1337]: Failed to write entry (28 items, 885 bytr
[ 722.578106] systemd-journald[1337]: Failed to rotate /var/log/journal/2ea02fr
[ 722.591468] systemd-journald[1337]: Failed to rotate /var/log/journal/2ea02fr
[ 722.606375] systemd-journald[1337]: Failed to write entry (28 items, 915 bytr
[ 722.617572] systemd-journald[1337]: Failed to rotate /var/log/journal/2ea02fr
[ 725.371837] bq24296_usb_detect: r8=84 ADAP PWRGOOD r9=81 WDOG HOT
[ 727.459206] bq24296_usb_detect: r8=8c ADAP INDPM PWRGOOD r9=81 WDOG HOT
[ 729.830340] systemd-journald[1337]: Failed to rotate /var/log/journal/2ea02fr
[ 729.843686] systemd-journald[1337]: Failed to rotate /var/log/journal/2ea02fr
[ 729.857869] systemd-journald[1337]: Failed to write entry (21 items, 619 bytr
[ 729.869251] systemd-journald[1337]: Failed to rotate /var/log/journal/2ea02fr
[ 729.882585] systemd-journald[1337]: Failed to rotate /var/log/journal/2ea02fr
[ 729.896576] systemd-journald[1337]: Failed to write entry (21 items, 600 bytr
[ 729.907831] systemd-journald[1337]: Failed to rotate /var/log/journal/2ea02fr
[ 729.921172] systemd-journald[1337]: Failed to rotate /var/log/journal/2ea02fr
[ 729.935163] systemd-journald[1337]: Failed to write entry (21 items, 619 bytr
[ 729.946363] systemd-journald[1337]: Failed to rotate /var/log/journal/2ea02fr
[ 733.689670] bq24296_usb_detect: r8=84 ADAP PWRGOOD r9=81 WDOG HOT
[ 735.769640] bq24296_usb_detect: r8=8c ADAP INDPM PWRGOOD r9=81 WDOG HOT
[ 735.777155] systemd-journald[1337]: Failed to rotate /var/log/journal/2ea02fr
[ 735.809086] systemd-journald[1337]: Failed to rotate /var/log/journal/2ea02fr
[ 735.825224] systemd-journald[1337]: Failed to write entry (9 items, 273 byter
[ 735.838612] systemd-journald[1337]: Failed to rotate /var/log/journal/2ea02fr
[ 735.852357] systemd-journald[1337]: Failed to rotate /var/log/journal/2ea02fr
[ 735.867159] systemd-journald[1337]: Failed to write entry (21 items, 619 bytr
[ 735.879253] systemd-journald[1337]: Failed to rotate /var/log/journal/2ea02fr
[ 735.892946] systemd-journald[1337]: Failed to rotate /var/log/journal/2ea02fr
[ 735.907722] systemd-journald[1337]: Failed to write entry (21 items, 601 bytr
[ 735.919826] systemd-journald[1337]: Failed to rotate /var/log/journal/2ea02fr
[ 741.835265] systemd-journald[1337]: Failed to rotate /var/log/journal/2ea02fr
[ 741.856280] systemd-journald[1337]: Failed to rotate /var/log/journal/2ea02fr
[ 741.882985] systemd-journald[1337]: Failed to write entry (21 items, 619 bytr
[ 741.905450] systemd-journald[1337]: Failed to rotate /var/log/journal/2ea02fr
[ 741.924503] systemd-journald[1337]: Failed to rotate /var/log/journal/2ea02fr
[ 741.946746] systemd-journald[1337]: Failed to write entry (21 items, 601 bytr
[ 741.970017] systemd-journald[1337]: Failed to rotate /var/log/journal/2ea02fr
[ 741.985483] systemd-journald[1337]: Failed to rotate /var/log/journal/2ea02fr
[ 742.003321] systemd-journald[1337]: Failed to write entry (21 items, 619 bytr
[ 742.009735] bq24296_usb_detect: r8=84 ADAP PWRGOOD r9=81 WDOG HOT
[ 742.017290] systemd-journald[1337]: Failed to rotate /var/log/journal/2ea02fr
[ 744.089242] bq24296_usb_detect: r8=8c ADAP INDPM PWRGOOD r9=81 WDOG HOT
[ 747.830266] systemd-journald[1337]: Failed to rotate /var/log/journal/2ea02fr
[ 747.843612] systemd-journald[1337]: Failed to rotate /var/log/journal/2ea02fr
[ 747.857922] systemd-journald[1337]: Failed to write entry (21 items, 619 bytr
[ 747.869261] systemd-journald[1337]: Failed to rotate /var/log/journal/2ea02fr
[ 747.882574] systemd-journald[1337]: Failed to rotate /var/log/journal/2ea02fr
[ 747.896535] systemd-journald[1337]: Failed to write entry (21 items, 601 bytr
[ 747.907803] systemd-journald[1337]: Failed to rotate /var/log/journal/2ea02fr
[ 747.921134] systemd-journald[1337]: Failed to rotate /var/log/journal/2ea02fr
[ 747.935129] systemd-journald[1337]: Failed to write entry (21 items, 619 bytr
[ 747.953427] systemd-journald[1337]: Failed to rotate /var/log/journal/2ea02fr
[ 750.329627] bq24296_usb_detect: r8=84 ADAP PWRGOOD r9=81 WDOG HOT
[ 752.489269] bq24296_usb_detect: r8=8c ADAP INDPM PWRGOOD r9=81 WDOG HOT
[ 753.830345] systemd-journald[1337]: Failed to rotate /var/log/journal/2ea02fr
[ 753.850874] systemd-journald[1337]: Failed to rotate /var/log/journal/2ea02fr
[ 753.872228] systemd-journald[1337]: Failed to write entry (21 items, 619 bytr
[ 753.890738] systemd-journald[1337]: Failed to rotate /var/log/journal/2ea02fr
[ 753.911284] systemd-journald[1337]: Failed to rotate /var/log/journal/2ea02fr
[ 753.932327] systemd-journald[1337]: Failed to write entry (21 items, 600 bytr
[ 753.950740] systemd-journald[1337]: Failed to rotate /var/log/journal/2ea02fr
[ 753.971261] systemd-journald[1337]: Failed to rotate /var/log/journal/2ea02fr
[ 753.992323] systemd-journald[1337]: Failed to write entry (21 items, 619 bytr
[ 754.010652] systemd-journald[1337]: Failed to rotate /var/log/journal/2ea02fr
[ 756.649697] bq24296_usb_detect: r8=84 ADAP PWRGOOD r9=81 WDOG HOT
[ 759.615072] systemd-journald[1337]: Failed to rotate /var/log/journal/2ea02fr
[ 759.637664] systemd-journald[1337]: Failed to rotate /var/log/journal/2ea02fr
[ 759.660710] systemd-journald[1337]: Failed to write entry (24 items, 669 bytr
[ 759.680687] systemd-journald[1337]: Failed to rotate /var/log/journal/2ea02fr
[ 759.702757] systemd-journald[1337]: Failed to rotate /var/log/journal/2ea02fr
[ 759.725559] systemd-journald[1337]: Failed to write entry (23 items, 629 bytr
[ 759.745469] systemd-journald[1337]: Failed to rotate /var/log/journal/2ea02fr
[ 759.766980] systemd-journald[1337]: Failed to rotate /var/log/journal/2ea02fr
[ 759.788186] systemd-journald[1337]: Failed to write entry (23 items, 688 bytr
[ 759.806590] systemd-journald[1337]: Failed to rotate /var/log/journal/2ea02fr
[ 759.849195] bq24296_usb_detect: r8=8c ADAP INDPM PWRGOOD r9=81 WDOG HOT
[ 765.049705] bq24296_usb_detect: r8=84 ADAP PWRGOOD r9=81 WDOG HOT
[ 765.109892] systemd-journald[1337]: Failed to rotate /var/log/journal/2ea02fr
[ 765.169584] systemd-journald[1337]: Failed to rotate /var/log/journal/2ea02fr
[ 765.233403] systemd-journald[1337]: Failed to write entry (9 items, 267 byter
[ 765.837749] systemd-journald[1337]: Failed to rotate /var/log/journal/2ea02fr
[ 765.897542] systemd-journald[1337]: Failed to rotate /var/log/journal/2ea02fr
[ 765.959698] systemd-journald[1337]: Failed to write entry (21 items, 619 bytr
[ 766.019325] systemd-journald[1337]: Failed to rotate /var/log/journal/2ea02fr
[ 766.089336] systemd-journald[1337]: Failed to rotate /var/log/journal/2ea02fr
[ 766.172107] systemd-journald[1337]: Failed to write entry (21 items, 619 bytr
[ 766.244126] systemd-journald[1337]: Failed to rotate /var/log/journal/2ea02fr

Theory: When the unit is booted from the SD card, the eMMC is getting mounted as well as a file system. Is there -any- chance that the OS running from the SD card is making any accidental writes to the eMMC? Why? The eMMC was working fine today until I ran the unit on the SD card. Now it is freeking out when booted from the eMMC.
 
Last edited:

levi

Still fresh, damnit!
Joined
Oct 6, 2008
Messages
13,198
Location
Somewhere off the coast of the EU
I personally blame the automounters. Sure they allow you just to plug in a card and read the data off it, but writing back it it is more dangerous. If you have to mount it youself you're more inclined to remember to unmount it before removing it I find.

Granted, an unprepared mount requires superuser priviledges, but if you have a card you regularly plug in you can add it to your fstab once and give it user priviledges to allow it to be user mountable and unmountable.
 
  • Like
Reactions: rSl

Grench

Forum Addict!
Joined
Oct 3, 2008
Messages
6,623
Returned to running off of the SD card OS. I wanted to run another set of fsck checks against the eMMC. Maybe some interesting results?

grench@MarbleSD:~/Desktop$ sudo su
[sudo] password for grench:
root@MarbleSD:/home/grench/Desktop# umount /dev/mmcblk0p1
root@MarbleSD:/home/grench/Desktop# umount /dev/mmcblk0p2
root@MarbleSD:/home/grench/Desktop# fsck /dev/mmcblk0p1
fsck from util-linux 2.33.1
e2fsck 1.44.5 (15-Dec-2018)
boot was not cleanly unmounted, check forced.
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information
boot: 265/65536 files (93.2% non-contiguous), 37176/262144 blocks
root@MarbleSD:/home/grench/Desktop# fsck /dev/mmcblk0p2
fsck from util-linux 2.33.1
Info: Segments per section = 1
Info: Sections per zone = 1
Info: sector size = 512
Info: total sectors = 60545024 (29563 MB)
Info: MKFS version
"Linux version 4.19.60-letux-lpae-pyra-nobat (pyra@debian-buster) (gcc version 8.3.0 (Debian 8.3.0-2)) #1 SMP PREEMPT Tue Dec 17 01:00:43 CET 2019"
Info: FSCK version
from "Linux version 4.19.88-letux-lpae (pyra@debian-buster) (gcc version 8.3.0 (Debian 8.3.0-2)) #1 SMP PREEMPT Fri Dec 13 20:15:40 CET 2019"
to "Linux version 4.19.88-letux-lpae (pyra@debian-buster) (gcc version 8.3.0 (Debian 8.3.0-2)) #1 SMP PREEMPT Fri Dec 13 20:15:40 CET 2019"
Info: superblock features = 0 :
Info: superblock encrypt level = 0, salt = 00000000000000000000000000000000
Info: total FS sectors = 60545024 (29563 MB)
Info: CKPT version = 6029e826
Info: checkpoint state = 55 : crc fsck compacted_summary unmount

[FSCK] Unreachable nat entries [Ok..] [0x0]
[FSCK] SIT valid block bitmap checking [Ok..]
[FSCK] Hard link checking for regular file [Ok..] [0xb]
[FSCK] valid_block_count matching with CP [Ok..] [0xdfcf9]
[FSCK] valid_node_count matcing with CP (de lookup) [Ok..] [0x2bffe]
[FSCK] valid_node_count matcing with CP (nat lookup) [Ok..] [0x2bffe]
[FSCK] valid_inode_count matched with CP [Ok..] [0x2bf0f]
[FSCK] free segment_count matched with CP [Ok..] [0x320e]
[FSCK] next block offset is free [Ok..]
[FSCK] fixing SIT types
[FSCK] other corrupted bugs [Ok..]

Done.
root@MarbleSD:/home/grench/Desktop#

I'm going to run with the SD card OS for now with the eMMC partitions umounted so I can have a chance to spend some time actually fiddling with the device instead of the OS or the partitions. But, either my eMMC is freeking out again OR the SD OS makes edits to the eMMC OS. Not sure which.

I would like to expand that partition out at some point from 8GB to the remainder of the 64GB card. Right now I have 4.1GB free.
 
Last edited:

Silent-Hunter

Hardcore Member
Joined
May 29, 2010
Messages
3,258
Is `sync` a root only command? I run it as non-root all the time on my systems. But they all use Debian 10.
 

Grench

Forum Addict!
Joined
Oct 3, 2008
Messages
6,623
Is `sync` a root only command? I run it as non-root all the time on my systems. But they all use Debian 10.
The answer to that is, "It depends". To my understanding, opening a user terminal with normal user permissions and typing 'sync' -should- flush the write cache of data for user initiated writes to user mounted devices. If at any point the system - with root rights - would have or could have touched anything on the device, a user level sync may actually prove to be inadequate to bring a mounted device to a stable state. In the case of the writes that I'm doing above, sync 100% has to be done at a root prompt as the dd command that filled the cache was (has to be) done at a root prompt.
 

aTc

Very Active Member
Joined
Apr 25, 2009
Messages
189
f2fs is used instead of ext4 because it should behave better on flash based media.

Use a disk image writing tool to dump the .img onto an sd card instead of dd , there are lots of them, rpi uses the same method to make their sd cards ( https://www.raspberrypi.org/documentation/installation/installing-images/README.md )
I use gnome-disks myself, or ddrescue on the command line (ddrescue shows progress)

The bootable pyraos only creates an 8gb partition because otherwise it would take forever to write it to the card, and it can't know how big the card is it's going to be written to in advance.
I quickly created the .img based stuff so people could create bootable sd cards more easily, the 'real' method is to use the pyra-install.sh script , but that's a lot harder to use.
Eventually it should resize the partition in the initramfs on first boot, like the rpi does, but since there are loads of other problems to take care of first, that's a slightly lower priority.
 

Silent-Hunter

Hardcore Member
Joined
May 29, 2010
Messages
3,258
I think in order for f2fs to be a benefit you have to know all sorts of things about the specific flash chip you're using it on. I could be wrong though.
 
  • Like
Reactions: rSl

EvilDragon

Administrator
Staff member
Joined
Mar 4, 2003
Messages
29,597
Age
43
Location
Ingolstadt
Frankly, write caching is one of the best and worst existing Linux user experiences that there still is. Yes, it speeds up the entire system in the background - great. It also misleads and -lies- to the end user, which to me is a cardinal sin of any OS. Maybe we should have a big fat RED widget in the system tray that says something to the effect of, "2.5 GB writes cached! Press here to sync!" instead of the user having to open a root/admin prompt and typing a command?
We don't want the end user to use elevated privileges for day in/out activities, right? So why can't we finish syncing the write cache without opening a root terminal?
Well, this is standard Linux stuff. Usually, you unmount the device before you unplug it, and it won't unmount while it's not yet synced.
It's possible to disable the cache for external mounted devices, but that slows things down by factor 10.

There's no real need to sync manually using a root terminal - Linux syncs automatically, when you unmount (which can be done via the file manager), and it also syncs after a certain time regularly.

Theory: When the unit is booted from the SD card, the eMMC is getting mounted as well as a file system. Is there -any- chance that the OS running from the SD card is making any accidental writes to the eMMC? Why? The eMMC was working fine today until I ran the unit on the SD card. Now it is freeking out when booted from the eMMC.
Hm, that could be a reason. I've never done this myself, no idea if aTc or others have tried that yet.
 

Djoga'Ro

moonstruck
Joined
Apr 3, 2016
Messages
1,620
Doing this on the 64GB Samsung EVO microSD card that I'm going to use as an OS SD card.
Used fdisk /dev/sdj to blow away the existing partitions.
# dd if=/dev/zero of=/dev/sdj bs=1M; sync
That has been running a good five minutes or more at 85M/sec (This is a fast SDXC card). You sure that command stops at 1M or does it start 1M -in-?
Not on its own, no, and no, since you didn't give an offset, it starts at the very beginning.
# dd if=/dev/zero of=/dev/sdj bs=1M; sync
^C20977+0 records in
20977+0 records out
21995978752 bytes (22 GB, 20 GiB) copied, 263.509 s, 83.5 MB/s
I Ctrl+C interrupted it - it's gone far enough.

Just to be 'safe' I'm going to let this run for 5 mins more.
# dd if=/dev/zero of=/dev/sdj; sync
^C29916913+0 records in
29916913+0 records out
15317459456 bytes (15 GB, 14 GiB) copied, 168.435 s, 90.9 MB/s

Now that I've done that and ctrl+c'd out, I submitted a # sync and am waiting for the card to settle out. That might take a while - my workstation has 48GB RAM and can cache a crazy write buffer.
You've zeroed the first 22GB of the card once and the first 15 GB a second time.
But I don't get, why ED asked to zero the device at all, since you where then dd-ing an device image to the card without planning to use an offset and the device image should contain all the partition information, which then of course gets written, too.
You didn't specify a count= value, just a block size. I'm not sure what dd does if you don't specify both to be honest, and I'm not sure why the total size differs, but I always use it with a count= and a bs= and it works for me in that situation.
Yes, dd reads chunkwise and writes chunkwise, bs gives the size of chunks to use and in the output they call the chunks records. I think you can specify differing bs for input and output. To specify a total size ypu can give a count of blocks/chunks/records, or - iirc - you can give an actual total size instead. If you don't specify a limit (and even if you do), it stops, when it reaches the end of the input or output "channel'/device/file - whichever comes first.

I understand and agree with all that - that isn't my gripe. My gripe is in how the OS reports completion of a copy/paste or ordered write. It reports completion of the read as completion of the entire action. Drag and drop a few GB of files onto a mounted USB drive or SD card (same thing more ore less) and the OS reads the files, says it's done, shows no device activity - and may not for up to an hour or more post the read. From a user perspective it is 'done'. From a reality perspective, it has done the read but not the write - and there is no indication on screen that this action is still pending. The only report to the user is that the copy is complete - which it isn't until the OS decides it is bored and writes the files to the target in the background or a sync is forced - and sync is a root only command.

Frankly, write caching is one of the best and worst existing Linux user experiences that there still is. Yes, it speeds up the entire system in the background - great. It also misleads and -lies- to the end user, which to me is a cardinal sin of any OS. Maybe we should have a big fat RED widget in the system tray that says something to the effect of, "2.5 GB writes cached! Press here to sync!" instead of the user having to open a root/admin prompt and typing a command?

We don't want the end user to use elevated privileges for day in/out activities, right? So why can't we finish syncing the write cache without opening a root terminal?

*steps down off the soapbox*

Battery at 84%. Time to set things back up for minicom and booting off of the freshly departitioned, dd zero'd and imaged microSDXC card's first boot.
I don't know the guts by heart, but as I understand it, it's the device driver or even the device itself (?), which does the lazy writing, so to the commands you use to issue a write the deed is done, when they report it is. When a filesystem was mounted, the fs or the mount programm (?) knows to issue a sync, and else it's up to you. But I'm glad you go through this that publicly, makes me myself aware of it, too. :) (I so far always used some tools in Windows to write images to mem-sticks, that do the finishing up.)
The answer to that is, "It depends". To my understanding, opening a user terminal with normal user permissions and typing 'sync' -should- flush the write cache of data for user initiated writes to user mounted devices. If at any point the system - with root rights - would have or could have touched anything on the device, a user level sync may actually prove to be inadequate to bring a mounted device to a stable state. In the case of the writes that I'm doing above, sync 100% has to be done at a root prompt as the dd command that filled the cache was (has to be) done at a root prompt.
You sure. When there is a parameter-less command, I can use without root privilege, I wouldn't expect that fact to change based on temporal context. ?
 

aTc

Very Active Member
Joined
Apr 25, 2009
Messages
189
It shouldn't touch anything other than the partition it booted from.

When you get to the desktop it will probe for removable disks and mount them, (like when you insert an sd card in another slot, or attach a usb device), and it just mounts whatever is on the emmc as part of that, it doesn't get written to by anything.

The syncing can take quite a while when you've written lots of data to an sd card (it usually completes in a few seconds, while it takes 10 minutes to actually write everything).
I did get annoyed enough at one point to quickly write a sync program that show how much data it still has to flush.
 

docbroke

Banned
Joined
Feb 21, 2019
Messages
480
Age
39
Location
India
it is safe to use sync after copying data to removable media, so that we don't remove media before write is complete. Same thing happens in windows, only name is different, it says something like "your device is safe to remove" once that sync is complete.
On most media read is quicker than write. So copy dialog disappears and terminal is freed for other tasks while write continues in background.
 
  • Like
Reactions: rSl

EvilDragon

Administrator
Staff member
Joined
Mar 4, 2003
Messages
29,597
Age
43
Location
Ingolstadt
it is safe to use sync after copying data to removable media, so that we don't remove media before write is complete. Same thing happens in windows, only name is different, it says something like "your device is safe to remove" once that sync is complete.
On most media read is quicker than write. So copy dialog disappears and terminal is freed for other tasks while write continues in background.
I think Windows still has the cache disabled as default so it runs slower but more user friendly.
 

Grench

Forum Addict!
Joined
Oct 3, 2008
Messages
6,623
You sure. When there is a parameter-less command, I can use without root privilege, I wouldn't expect that fact to change based on temporal context. ?
Yes, sync can be used by any user account. However, it appears to be specific to that user's unwritten data unless you're root - then it writes all user's data.

Get out a SD card - something in the range of 32GB or more.
Open up a folder using a normal user account. Start copying 10GB or so of files to it.
While that is running open a folder under the root user. Start copying another 10GB or so to another folder on the same card.

When both say 'done', run sync from the normal user. Let it complete.
Then run the sync command from the root user. It then runs for about as long. If the user sync were 'universal', then what is it doing?

From what I can tell:
The sync command submitted by the normal user -only- syncs that user's writes.
The sync command submitted by root syncs all open writes from all users to all devices.
The umount or right click unmount perform the sync command as if the user was root - system level - which makes sense as the device is about to get unmounted.

But, if you're fiddling around in multiple user accounts on the same box (with or without elevation) and need to settle the media without unmounting it, make sure you run that sync from root.

I run my backups to HDDs. I have noticed this same behavior with them. If I want to power down the workstation - and leave the backup or near-line drive in the sata dock, root sync is key to happiness on the next use. Failure to do so can result in lost data and sadness and having to re-synchronize multiple terabytes over multiple disks.

Enough with sync for now, though. We're all here because we're interested in the Pyra and I happen to have one that I'm fiddling around with.
 

Grench

Forum Addict!
Joined
Oct 3, 2008
Messages
6,623
Hm, that could be a reason. I've never done this myself, no idea if aTc or others have tried that yet.
It shouldn't touch anything other than the partition it booted from.

When you get to the desktop it will probe for removable disks and mount them, (like when you insert an sd card in another slot, or attach a usb device), and it just mounts whatever is on the emmc as part of that, it doesn't get written to by anything.
My direct experience was:
Loaded the OS flash to eMMC. Booted from it. It worked 100% over ~4 reboots.
Created an OS card for the SD slot. Booted from it. It worked 100% over ~3 reboots.
Removed the card from the SD slot.
Booted from the eMMC. OS is now 'rotten'. Things that worked now don't, etc.
The only 'change' that I can point to is having booted from the SD card.

There are a lot of differences between the OS image used in the eMMC OS and the SD card OS. Boot is ext2 vs ext4. Whether the left shoulder shift works or not during the Welcome script. Likely more, but I'm not planning to reflash the eMMC again tonight. I need a break from that, so I'm sticking with the left SD slot booting for now.

There are clearly differences between the two, though. From my poking around, the SD boot feels like the superior version. Which one would be seen as the 'more current' one? Is there a path/plan to get them back in sync?

**********************************
New topic: USB charging ports oddities.
OS used: SD card
'Smart' USB 3.1 hub with a 2.5A charging port capable of negotiated voltage/current.
'Dumb' USB 2.0 hub with a 2A charging port.
USB volt/amp measurement device put in between to test draw.

microUSB charging/serial port plugged into either charger, draws 0.45A
microUSB 3.0 wide port plugged in with cable (fat 3.0 or narrow 2.0) to either charger, draws ~1.7A (a bit variable)

If the microUSB charging/serial port is plugged in and drawing 0.45A and a device (OTG hub, card reader, etc) is plugged into the mciroUSB 3.0 wide port, charging through the charging/serial port stops and current draw on the charging/serial port drops to 0.00A AND the device on the microUSB 3.0 port is inactive.

If the mciroUSB charging/serial port is empty and an OTG device is plugged into the USB 3.0 wide port, then the OTG hub, card reader, etc gets power, works as normal and devices show up in the file system (good).

I haven't figured out a configuration where I can get the charging/serial narrow USB to draw more than 0.45A. Isn't this one supposed to be our main charging port?

Charging through the microUSB 3.0 wide port seems to work quite well using fat 3.0 or narrow 2.0 cables.

Right now it seems that I can either supply power to the Pyra OR use the USB 3.0 OTG functionality while draining the battery.

The reverse case works fine. I can supply power via the USB 3.0 wide port and use the serial communications from the charging/serial port without issue.

How I envisioned it working:
Hub is powered via a 3.5A wall plug.
USB charging/serial port draws main power (up to 2+A) from a charging port (no data) on my hub.
Hub USB 3.0 host port plugs into the USB 3.0 wide connector on the Pyra.
Both plugs in use simultaneously. One draws power, the other hosts the USB 3.0 hub allowing keyboard, data devices, ethernet, etc.

Is this a known issue?
 

wdt

Member
Joined
Feb 16, 2009
Messages
114
FWIW, from experience with SBC's putty is a much nicer remote terminal, but
you may get lost in the extreme amount of configuration if needed (not usually)
A saved config can be started with double click
This (pyra) is almost certainly using open firmware, a dtb somewhere in /boot
Maybe the emmc needs to be slowed down slightly? a slightly lower frequency?
Or, less likely, is the voltage right? There is a 6-12 line stanza for every device
Without a compile environment, hacking dtb->dts->dtb is rather painful,
except for the simplest things
--remembering more --
There can be issues with drive current and more esoterically slew
Some rk3399 had to have 8ma drive rather than 4ma, partly a factor of trace geometry
 
Last edited:

EvilDragon

Administrator
Staff member
Joined
Mar 4, 2003
Messages
29,597
Age
43
Location
Ingolstadt
AND we did find the issue (or more specifically: aTc did ;))

@ToastBucket It's your U-Boot version :)

The U-Boot is fairly new and it seems it doesn't have all patches from Nikolaus' U-Boot in there.

The lower left shoulder button is the "force-to-boot from internal SD Card button".
Once the U-Boot has loaded though, this function needs to be disabled. Nikolaus' U-Boot does that.
The ToastBuckets' U-Boot doesn't do that now.

So that means:
Whenever you press the left shoulder button, it switches from the eMMC to the internal Micro SD Card. Once you let go of the shoulder button, the eMMC is immediately back - but you can imagine this leads to a corrupted filesystem!
This also explains why the left shoulder button wasn't working for Shift anymore...

I think the image I used to originally flash the units was NOT yet using ToastBuckets U-Boot, which is the reason this happened after a reflash.

aTc is currently packaging up a new installation image which will fix that problem :)
 

ToastBucket

Very Active Member
Joined
Oct 12, 2010
Messages
330
Location
Seattle
So that means:
Whenever you press the left shoulder button, it switches from the eMMC to the internal Micro SD Card. Once you let go of the shoulder button, the eMMC is immediately back - but you can imagine this leads to a corrupted filesystem!
This also explains why the left shoulder button wasn't working for Shift anymore...
That explains it :). I just kind of blindly copied this functionality from the old UBoot with only mild testing. I’ll have to do some more testing and repairs here. Good to have some units out in the wild to help us find these issues :)
 
Top