I just updated my Odroid N2 to the latest beta version, 8.24.1, but encountered a boot issue. During the initial boot process, an error message related to EXT4-fs appeared, leading me to suspect a corrupted SD card.
To address this, I opted for a clean install, downloading the most recent image from the official website. Initially, the system booted successfully and began the automatic update process. However, it failed to reboot afterward, displaying the same EXT4-fs error as before.
I have attached a photo that captures the error message in more detail.
Here’s how I managed to restore my system to a functional state:
I performed a clean installation but this time, I disconnected the Ethernet cable to prevent the system from accessing the internet and automatically updating. Then, I used the DietPi restore utility to revert to a previous backup I had saved.
Now my system is functioning properly and I’m on version 8.24.1 but it’s asking me if i want to update the following packages : armbian-firmware libtiff6 linux-dtb-current-meson64 linux-image-current-meson64
linux-u-boot-odroidn2-current
Which was what i had updated earlier and borked my system
I see the same symptoms updating DietPi on an Odroid N2+. The update of the OS appears to go OK, but things seems to go bad at the end of the apt update.
Storage is a properly-set-up-for-boot USB SSD. The same failure occurs for a fresh install (downloaded image today) on a different HDD. Both the SSD and HDD are readable when mounted on a working Linux system.
Maybe something with latest kernel package. As we don’t develop this kernel, it would be needed to test with plain Armbian to see if it’s similar with latest kernel builds.
I’ve tried installing a saved old image that worked earlier, but it wants to automatically update to the latest (broken!) version. How can I safely suppress that automatic update?
Could you please specify which are the kernel package on hold? I put on hold this packages (armbian-firmware linux-dtb-current-meson64 linux-image-current-meson64, linux-u-boot-odroidn2-current), but Odroid N2+ still doesn’t boot after updating the rest of the packages.
Now the Odroid N2+ boots ok. I now for sure that one of these packages have problems. I think is the linux-u-boot-odroidn2-current/bookworm 23.11.1 arm64 [upgradable from: 23.8.1].
I will test one by one and get back to you.
So I found out that for me only this package ruins the boot of Odroid N2+!!!
linux-image-current-meson64
On my N2+ Armbian 23.11.1 and Dietpi 8.24 function without issue when run from an SD card.
My goal is to get Dietpi running from SSD only (no SD). Modifying /boot/boot.cmd (and compiling to boot.scr with mkimage) on the SSD allows the system to boot and the OS to partially start up but then fail – for both Armbian and Dietpi.
Looks like latest kernel version has some challenges. Best is to test with plain Armbian and if it behaves same, have it reported directly to Armbian. Just one remark, if you go to report to Armbian, don’t do any comments or similar about DietPi. We don’t have best relationship. Therefore it is needed to use original Armbian and their debugging tools
Yesterday, I attempted to update meson64, assuming any issues would have been resolved by now. Unfortunately, the update resulted in my system failing to boot.
Since then, I’ve tried multiple fresh installations using different USB sticks with the following images:
I initially tried using USB sticks, as that’s what I’ve been using for the past few years, but the same errors persist. When I switched to an SD card, the system booted successfully even with the meson64 update.
I’ve also tried installing other OSes, such as CoreELEC, on these USB drives, and they worked fine. It seems the issue is specific to booting DietPi from USB and HDD.
Any suggestions on what might be causing these errors or how to fix them would be greatly appreciated.
