magostinelli Posted May 14, 2021 Posted May 14, 2021 Hello, i did an update of the system (apt dist-upgrade), and after the system doesn't start anymore. I use internal MMC, so I tryed to use last Armbian buster (Armbian_21.02.3_Helios64_buster_current_5.10.21.img) from sd card and it works. I mounted the MMC, fsck and finally chrooted into it and did an apt update and dist-upgrade, I atach the console log, the system hangs on Starting Kernel. helios64_20210514.txt
barnumbirr Posted May 14, 2021 Posted May 14, 2021 Can you try to boot from the SD card again, mount the eMMC and edit the /boot/armbianEnv.txt to increase verbosity (defaults to 1 which means less verbose, maximum value is 7). Please then post the logs.
magostinelli Posted May 14, 2021 Author Posted May 14, 2021 2 hours ago, barnumbirr said: Can you try to boot from the SD card again, mount the eMMC and edit the /boot/armbianEnv.txt to increase verbosity (defaults to 1 which means less verbose, maximum value is 7). Please then post the logs. I found the errors! The /boot/armbianEnv.txt was corrupted, I replaced the file using that one from sd card, and then changed the UUID of the roor partition.
barnumbirr Posted May 17, 2021 Posted May 17, 2021 Nicely done. Corruption of the armbianEnv.txt file is one of the remaining nagging issues on the Helios64. I suspect it is linked to the system instability but I've not been able to pinpoint the exact issue so far.
Werner Posted May 18, 2021 Posted May 18, 2021 On 5/14/2021 at 3:40 PM, magostinelli said: The /boot/armbianEnv.txt was corrupted Can you elaborate? Does the file become empty or unreadable?
Polarisgeek Posted May 18, 2021 Posted May 18, 2021 When I had it happen to me during an update it added/rewrote some text and added gibberish(special characters). I was able to edit it to match some of the examples and put in my UUID and it booted right up. I unfortunately don't have any screen shots or anything to show.
magostinelli Posted May 21, 2021 Author Posted May 21, 2021 In my case, the file has some configuration for logrotate, and at the end it has some special characters.
Recommended Posts