[FS#3140] sysupgrade spews lost of errors on x86_64

[OpenWrt Bugs]

THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY.

The following task has a new comment added:

FS#3140 - sysupgrade spews lost of errors on x86_64
User who did this - Yousong Zhou (yousong)

----------
I just checked with the code.  The errors and warnings are disturbing but should be mostly fine with regard to integrity and functionality of the system.

The following was caused by command "cat xx | dd count=x ..".  It can also be zcat if the image is suffixed with .gz

cat: write error: Broken pipe


The following lines were likely caused by "mount /dev/xx /tmp/boot".  It's mount probe function debug output.  With combined-efi image, the boot partition will be formated as fat (or vfat).  The mount will succeed.

[ 2308.945667] F2FS-fs (nvme0n1p1): Can't find valid F2FS filesystem in 1th superblock
[ 2308.963141] F2FS-fs (nvme0n1p1): Magic Mismatch, valid(0xf2f52010) - read(0x6020601)
[ 2308.980487] F2FS-fs (nvme0n1p1): Can't find valid F2FS filesystem in 2th superblock


The following is a minor flaw that the filepath is wrong, but it should not cause bad consequence.

touch: /tmp/boot/grub/upgraded: No such file or directory



The following one I cannot reproduce.  But likely it's also expected as ptgen the tool we compile and use for partition table generation does not write backup (alt.) header at end of the disk.


May 31 16:43:17 OpenWrt kernel: [    3.753680] GPT:Primary header thinks Alt. header is not at the end of the disk.

----------

More information can be found at the following URL:
https://bugs.openwrt.org/index.php?do=details&task_id=3140#comment8953

You are receiving this message because you have requested it from the Flyspray bugtracking system.  If you did not expect this message or don't want to receive mails in future, you can change your notification settings at the URL shown above.