Just updated to 142 via dietpi-update (After a backup) and now unit will not boot. Gets me blue/red solid lights but apparently no kernel is loading. Anyone else? Any tips? I did a backup but saw the prompt about them not being compatible… unsure where to go from here.
I’ve not experienced this during my tests on the C2’s with v142 update, but lets check few things:
PSU used?
SD card / EMMC used?
Plug the SD/EMMC into PC, open the /boot partition and take a screenshot of the files. If you have a Linux system, also check the 2nd partition and list kernel version (eg: ls -lha /lib/modules)
Also, can you remember which DietPi image version you wrote to the SD/EMMC card originally? (eg: DietPi_v123_OdroidC2…img)
EDIT: Also, can you remember where you stored the dietpi-backup? default is /mnt/dietpi-backup. If its on SD/EMMC, I can get it restored for you. You’ll need to read the SD/EMMC to image file, zip (with password) and upload somewhere, then email me link + pw and i’ll take a look.
Thanks for the support! I use the PSU from Ameridroid and eMMC from them, too.
I was able to get it to boot by doing the following:
Copied all /boot files from a previous install (v140, and v139 was first image I used on this device) and replacing the /boot files on the eMMC that were there after the 142 update.
dietpi still prompts me for an update but it is running OK for now. I have tried the update a few more times since but always had to restore the /boot files from the previous version to get it to boot at all…
Screenshot of /boot after 142 update (that doesn’t work) is attached. I tried to attach another file but have to do in another post.
this is the /boot from v140 (I think) that does work. I had this on a sdcard from first install and it works fine booting by itself or copying the /boot files to the eMMC that was updated to 142. Hope this is clear…
This may be unrelated, but my external HDD (/mnt/usb_1) becomes unmounted relatively often, usually under heavy use, requiring a ssh login and “mount -a”. I will post a second topic, but felt that it might be relevant…
also just want you to know i’m going to kick you and the team a small donation for your efforts with this project and commitment to FOSS tech. Thx mate
Could be a drive failure, insufficient power (1x750mah drive should be fine for 2A PSU, are you using any other USB devices?) power instability issue or usb <> sata controller failure.
When the drive unexpectedly dismounts, might be worth checking dmesg for any errors listed on the drive:
dmesg | grep sda
this is the /boot from v140 (I think) that does work. I had this on a sdcard from first install and it works fine booting by itself or copying the /boot files to the eMMC that was updated to 142. Hope this is clear…
Make a backup of the /boot folder on the EMMC.
Once done, copy all files on the working SDcard /boot to the EMMC, excluding:
The drive is brand new so I’m guessing it is lack of power… I have a USB DAC and a Zwave controller also plugged in, so that must be it. Would getting a 3A PSU help? If so, where might I get a good on for the C2?
I copied the old boot files except /dietpi folder and dietpi.txt and it booted fine. Still prompted me for an update, so did update, completed, sent reboot command via ssh and it is has not rebooted. Manually unplugged and replugged the C2 and still no boot, just solid blue/rd lights.
After this, I copied the files from the old SD card install over again (except /dietpi and dietpi.txt) which allowed it to boot and it does not prompt me for an update now.
Thanks for help.
Question - I am scared to update now… Do you think I have to do this everytime I update? Any insight into what happened?
A 5v/2A PSU Should be enough for the C2 and 1x USB drive + USB peripherals. As long as the PSU provides a stable 5v (usually the official PSU’s supplied with RPi/Odroid are), I dont believe that PSU is the issue here.
Regardless, if you can please paste the results of the below command, this will list current USB mA usage/requirements for connected devices:
lsusb -v
I copied the old boot files except /dietpi folder and dietpi.txt and it booted fine. Still prompted me for an update, so did update, completed, sent reboot command via ssh and it is has not rebooted. Manually unplugged and replugged the C2 and still no boot, just solid blue/rd lights.
Ok, so something in the patch is causing the issue. During the patch, DietPi will upgrade apt, this may pull in a new kernel from Meverics Repo. Can you remember when running dietpi-update, if you seen any on-screen text that mentions a kernel update?
Ideally, I’d like to get a exact copy of your failed boot EMMC/SD to run some tests, this will help us find the cause. Would you be comfortable reading the SD/EMMC (in the state of failure to boot) to an image file with win32diskimager (or similar), compress it with zip, then upload to a hosting site (eg: dropbox/mega etc)?
If not, let me know and i’ll give steps required.
Question - I am scared to update now… Do you think I have to do this everytime I update? Any insight into what happened?
A failed boot after dietpi-update is unexpected and unacceptable in our eyes. Ideally, with your help, we would like to run some tests on your current installation and find the cause.