skybob22

Sorry if it takes a while to reply. I just made an account, so the number of posts I can make per day appears to be limited to 1. I did some additional testing and tried flashing several different images including some older versions: Couldn't boot at all (same error UUID does not exist): Armbian_22.05.3_Nanopi-r4s_focal_current_5.15.48.img.xz Armbian_22.02.1_Nanopi-r4s_focal_current_5.15.25.img.xz Armbian_22.05.3_Nanopi-r4s_jammy_current_5.15.48.img.xz Armbian_22.05.3_Nanopi-r4s_bullseye_current_5.15.48.img.xz Armbian_22.02.1_Nanopi-r4s_bullseye_current_5.15.25.img.xz Armbian_21.08.1_Nanopi-r4s_hirsute_edge_5.13.12.img.xz Armbian_22.02.1_Nanopi-r4s_jammy_edge_5.16.11.img Booted but would no longer boot after apt update/upgrade: Armbian_21.08.1_Nanopi-r4s_focal_current_5.10.60.img.xz Armbian_21.08.1_Nanopi-r4s_buster_current_5.10.60.img.xz Armbian_21.08.1_Nanopi-r4s_bullseye_current_5.10.60.img.xz I also have tried 3 different SD cards. So I doubt that is the cause, unless all 3 are somehow bad. All the ones that don't work appear to be 5.10.* I'm not sure if the newer ones come bundled with the newer version of the package that breaks it? Woops, sorry about that. When I read the title I didn't realize it was referring to the same problem I wish I had found it easier because it would have saved me a lot of time installing packages a couple at a time until I found the one that broke it... I also came to the same conclusion that updating linux-image-current-rockchip64 to version 22.*.* or newer breaks it. I tried three different 32GB SanDisk Ultra SD cards and none of the newer images will boot (including Armbian_22.05.3_Nanopi-r4s_jammy_current_5.15.48.img.xz and Armbian_22.05.3_Nanopi-r4s_bullseye_current_5.15.48.img.xz) I was using Rufus, but I also downloaded and tried the same version of USBimager 1.0.8 to eliminate that variable and still had the same problem I don't know if there might be some problem with my board? That seems unlikely since the older images still work... But given that the images work on the board you tested and aren't working on mine I'm not sure what would cause that.

I'm trying to load Armbian onto a NanoPi R4S, but an running into problems where it won't start with certain versions, and running apt update breaks it on other versions. I've hooked up the serial interface so I can see what's going on during boot, so there are pastebin links to the logs. Fresh Image (Jammy/Focal): Trying to use Jammy or Focal I cannot the the board to boot at all with a completely fresh image. The error message complains that the UUID for the main partition does not exist Log: https://pastebin.com/gQeyhVf5 Fresh image (Bullseye/Buster), post account creation: Bullseye and Buster will initially boot, but sometimes will not boot properly if doing a soft-reboot (ie. sudo reboot now), requiring a hard power-cycle to boot (which is a bit annoying since the board won't be in the easiest place to get to). At this stage I haven't done anything except the initial prompt to change the root password It has the same error message that UUID does not exist Log: https://pastebin.com/cnNbZVFT Post apt update/upgrade (Bullseye/Buster): With both Bullseye and Buster, I run apt update and apt upgrade since it's generally a good idea to keep packages up-to-date for security. I didn't change any other files or do anything else except run the update However in both, after running apt upgrade it is no longer able to boot no mater how many times I power cycle it. Also complains UUID does not exist Log: https://pastebin.com/pqyxBrvS After apt update was complete, but before power cycling/rebooting it I did check the UUIDs of the partitions using blkid and also checked /boot/armbianEnv.txt to check if either had changed. But the UUID's still matched what they were previously so it doesn't seem that anything got changed or corrupted In all the cases where it won't boot it seems to be complaining that the UUID for the rootfs doesn't exist. And I'm not sure how to fix it