Thanks for the log. Unfortunately the config change switching the console= positions doesn't appear to have done anything, so your console=tty1 is still last in the kernel command line, hence most of the initramfs output is missing. However, that doesn't matter much in this case as the basic failure is still clear from the log; under kernel rev 1011 it's failing to mount your rootfs:
... [ 0.499808] VFS: Cannot open root device "LABEL=writable" or unknown-block(0,0): error -6 [ 0.501568] Please append a correct "root=" boot option; here are the available partitions: [ 0.503467] List of all bdev filesystems: [ 0.503553] mmc0: new high speed SDXC card at address 5048 [ 0.504435] ext3 [ 0.505402] ext2 [ 0.506422] ext4 [ 0.507347] squashfs [ 0.508242] vfat [ 0.509151] [ 0.510958] Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0) [ 2.014089] CPU: 3 UID: 0 PID: 1 Comm: swapper/0 Not tainted 7.0.0-1011-raspi #11-Ubuntu PREEMPT(lazy> [ 2.023485] Hardware name: Raspberry Pi Zero 2 W Rev 1.0 (DT) ... After the kernel panic, the system reboots and you're back to the working set of assets. So, in your case at least, the question becomes "why is it failing to mount the rootfs"? This could be a kernel issue, or a dracut issue (the system that generates the initramfs), but it's not a piboot-try issue. Given this bug is now the consolidation of the various piboot-try reports, I think adding a kernel issue here would just confuse things further, so I've opened a separate bug (LP: #2157789) against linux- raspi with the relevant log (screenlog.0.v2) attached and subscribed you (irihapeti) to that issue. If you want to try repeating the experiment with the console= portions switched to provide the initramfs (dracut) output as well, I'd recommend attaching that to LP: #2157789 as that may help the kernel team figure out what's going on. Anyway, thanks very much for the log output -- good to see piboot-try doing what it's meant to in at least one case (though I definitely need to improve that warning message!) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2155094 Title: RPi 3B, Zero 2W, 4B: New boot assets in /boot/firmware/new failed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/2155094/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
