For the second time within about 4 weeks my cubietruck is not coming up anymore after a sudo apt upgrade and reboot.
Is there something systematically breaking?
I think it is the initramfstools that is breaking it?
Now, I have no radio, alarm-clock and I cannot turn on my coffee-maker over the internet and I will probably have to spend a day etching a new SD card etc.
I bought a new SD card last time this happened since I figured ist would be related to that, now I think it is a software thing.
I use the cubietruck headless over ssh and have no real video output, just audio.
I also need to do some cumbersome operations to get it out of the box, it is in from which it is controlling all sorts of remote controls for receivers, projectors etc. So it is almost easier to etch a new card, but I am afraid I will find myself with the same problem in a few weeks again.
Is it now trying to boot from ramfs rather than the SD-card?
Any suggestions on what I could do in a more "minimally invasive" way to get it back to work? Any updates I should hold back in the future to keep this from happening?
You can post now and register later.
If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.
Question
matrzh
For the second time within about 4 weeks my cubietruck is not coming up anymore after a sudo apt upgrade and reboot.
Is there something systematically breaking?
I think it is the initramfstools that is breaking it?
Now, I have no radio, alarm-clock and I cannot turn on my coffee-maker over the internet
and I will probably have to spend a day etching a new SD card etc.
I bought a new SD card last time this happened since I figured ist would be related to that, now I think it is a software thing.
I use the cubietruck headless over ssh and have no real video output, just audio.
I also need to do some cumbersome operations to get it out of the box, it is in from which it is controlling all sorts of remote controls for receivers, projectors etc. So it is almost easier to etch a new card, but I am afraid I will find myself with the same problem in a few weeks again.
I used the following image
Armbian_21.05.1_Cubietruck_buster_current_5.10.34_xfce_desktop.img
The latest upgrade did the following:
The following packages will be upgraded:
code firefox-esr libgssapi-krb5-2 libjavascriptcoregtk-4.0-18 libk5crypto3 libkrb5-3 libkrb5support0 libnss-myhostname libpam-systemd libsystemd0 libudev1 libwebkit2gtk-4.0-37 linux-u-boot-cubietruck-current systemd systemd-sysv
udev
In particular:
Processing triggers for initramfs-tools (0.133+deb10u1) ...
update-initramfs: Generating /boot/initrd.img-5.10.43-sunxi
update-initramfs: Converting to u-boot format
Is it now trying to boot from ramfs rather than the SD-card?
Any suggestions on what I could do in a more "minimally invasive" way to get it back to work? Any updates I should hold back in the future to keep this from happening?
Link to comment
Share on other sites
9 answers to this question
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.