matteo

Can confirm I'm also seeing this. I'm able to recover by installing the 23.02.2 linux-image-current-meson64 and linux-dtb-current-meson64 packages from /var/cache/apt/archives.
 
From what I can tell it's installing the modules for 6.1.50 in  /lib/modules but is somehow still booting 6.1.11
 
/boot/uImage isn't getting updated
$ strings /boot/uImage | grep "Linux version" Linux version 6.1.11-meson64 (root@29682b33de96) (aarch64-linux-gnu-gcc (GNU Toolchain for the A-profile Architecture 8.3-2019.03 (arm-rel-8.36)) 8.3.0, GNU ld (GNU Toolchain for the A-profile Architecture 8.3-2019.03 (arm-rel-8.36)) 2.32.0.20190321) #23.02.2 SMP PREEMPT Linux version 6.1.11-meson64 (root@29682b33de96) (aarch64-linux-gnu-gcc (GNU Toolchain for the A-profile Architecture 8.3-2019.03 (arm-rel-8.36)) 8.3.0, GNU ld (GNU Toolchain for the A-profile Architecture 8.3-2019.03 (arm-rel-8.36)) 2.32.0.20190321) #23.02.2 SMP PREEMPT Sat Feb 18 00:07:55 UTC 2023  
 
I can confirm that running the following command manually gets the device back into a working state
$ mkimage -A arm64 -O linux -T kernel -C none -a 0x1080000 -e 0x1080000 -n Linux -d /boot/vmlinuz-6.1.50-current-meson64 /boot/uImage  

Hi Igor and wildcat_paris,
 
Many thanks for pointing this out to me. I read over the documentation last night, but glossed over that section because I didn't think of my unit as bricked. Sorry for the foolish question, but thank you again for the help, and for all the hard work you've put into this project!
 
Best,
Matteo

wildcat_paris,
 
Thanks again for your assistance, I appreciate it. I was able to get the system back up and running after following the rescue procedure. I noticed that I'm now using the legacy kernel (3.14.67), rather than vanilla (4.5.5). Is that expected behavior, or did I choose the wrong set of files? I first tried the cubox_4.5 debs, and then afterward the cubox_5.10 debs. In any case, I might leave things the way they are, as everything seems a tad more responsive with the legacy kernel. 
 
Also, I still have the missing file messages at boot, but it doesn't seem to affect anything. Perhaps this was always being displayed, but I never noticed because this is a headless server. I assume it's nothing to worry about?
 
Lastly, I'm fairly certain that I used aptitude for previous upgrades, but I'm not positive. In any case, I'll stick with apt-get for this system from now on.
 
Best,
Matteo

Hello,
 
I updated my Vanilla Jessie headless install yesterday (aptitude safe-upgrade), but the system never came back online after reboot. The screen flashes the SolidRun logo and a few lines of text, and then the LED turns off and the screen goes blank:
 
 
It doesn't seem like the system boots, and it definitely doesn't connect to my home network via Ethernet. Is there a way to rescue this install?
 
Thanks in advance,
Matteo