[OpenWrt-Devel] Lots of errors w/ sysupgrade on x86_64

Philip Prindeville philipp_subx at redfish-solutions.com
Sun May 31 21:07:10 EDT 2020


Filed a flyspray:

https://bugs.openwrt.org/index.php?do=details&task_id=3140


> On May 31, 2020, at 4:43 PM, Philip Prindeville <philipp_subx at redfish-solutions.com> wrote:
> 
> Had to set up console redirection to capture this, but this is what I’m seeing on a fairly recent build of master (about 2 weeks old):
> 
> root at OpenWrt:/# ifdown wan
> root at OpenWrt:/# 
> root at OpenWrt:/# 
> root at OpenWrt:/# sysupgrade /tmp/openwrt-r13360\+64-4661b05390-x86-64-generic-squashfs-combined-efi.img 
> Image metadata not found
> Reading partition table from bootdisk...
> cat: write error: Broken pipe
> Reading partition table from image...
> Saving config files...
> Commencing upgrade. Closing all shell sessions.
> Watchdog handover: fd=7
> - watchdog -
> killall: telnetd: no process killed
> killall: dropbear: no process kiSending TERM to remaining processes ... ntpd sh snmpd dhcpd ipset-dns collectd lldpd lldpd smartd named sleep ubusd askfirst urngd netifd rngd crond lighttpd sshd syslog-ng 
> Sending KILL to remaining processes ... 
> Switching to ramdisk...
> Performing system upgrade...
> Reading partition table from bootdisk...
> dd: warning: partial read (8192 bytes); suggest iflag=fullblock
> 0+63 records in
> 0+63 records out
> 1101824 bytes (1.1 MB, 1.1 MiB) copied, 0.00492347 s, 224 MB/s
> Reading partition table from image...
> Writing image to /dev/nvme0n1p1...
> cat: write error: Broken pipe
> 40959+0 records in
> 19+1 records out
> 20971008 bytes (21 MB, 20 MiB) copied, 0.0963313 s, 218 MB/s
> Writing image to /dev/nvme0n1p2...
> 462847+0 records in
> 225+1 records out
> 236977664 bytes (237 MB, 226 MiB) copied, 0.810288 s, 292 MB/s
> Writing new UUID to /dev/nvme0n1...
> 4+0 records in
> 4+0 records out
> cat: write error: Broken pipe
> 4 bytes copied, 0.00439713 s, 0.9 k[ 2308.927159] F2FS-fs (nvme0n1p1): Magic Mismatch, valid(0xf2f52010) - read(0x0)
> B/s
> [ 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
> Upgrading bootloader on /dev/nvme0n1...
> touch: /tmp/boot/grub/upgraded: No such file or directory
> Upgrade completed
> Rebooting system...
> umount: can't unmount /dev: Resource busy
> umount: can't unmount /tmp: Resource busy
> [ 2310.852582] ACPI Warning: \_SB.PCI0.BR2C._PRT: Return Package has no elements (empty) (20190816/nsprepkg-96)
> [ 2310.881404] ACPI Warning: \_SB.PCI0.BR2C._PRT: Return Package has no elements (empty) (20190816/nsprepkg-96)
> [ 2311.080235] reboot: Restarting system
> [ 2311.093088] reboot: machine restart
> 
> 
> That seems like a LOT of “Broken pipe” warnings.
> 
> Also, there’s no reason the image wouldn’t contain meta-data, so I’m not sure why I’m seeing that warning, either.
> 
> That said… the system seems to boot up okay with the new image in-place.
> 
> But it sure would be nice to not violate the Principle of Least Astonishment throwing all of these warnings.
> 
> Thanks
> 
> 
> _______________________________________________
> openwrt-devel mailing list
> openwrt-devel at lists.openwrt.org
> https://lists.openwrt.org/mailman/listinfo/openwrt-devel


_______________________________________________
openwrt-devel mailing list
openwrt-devel at lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel


More information about the openwrt-devel mailing list