-
-
Notifications
You must be signed in to change notification settings - Fork 502
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
DietPi Failing to Update #3048
Comments
@tenryou-17 Hmm something with the package file lists is damaged.
|
@MichaIng
|
@tenryou-17 |
Ha! My bad. There was no output for the first line. Here is the output for the second line:
|
@tenryou-17 Do you have a backup where we could recover the missing list files? But those warnings did not make the upgrade fail, but:
Could be fixed by: And the sources file error could be tried to be solved by cleaning everything and redownloading them:
What I am thinking about why these files are missing or broken. Perhaps some SDcard corruption. Could you paste: |
So no output to paste for the first three lines. Here is the output for
And here is the output for
And here is the output for
I don't have a backup, but my setup is fairly simple. It would be trivial to reflash the SD card with the latest DietPi image. I have found that every couple of months I run into this problem where it won't update. I just end up reflashing the card and think nothing of it, because my setup is really simple. However, now I think it is a pattern which is why I reported it. |
About update issues. Yeah this is all on APT level currently and there are several possibilities why APT can fail. However in your case something either touched those .list files which should nothing do else of APT/DPkg, or some disk I/O corrupted them. And for disk I/O errors again there are a bunch of possible reasons, including voltage issues (unstable/insufficient power supply) or simply bad quality or old dying SDcard. However your Okay as above, please do:
|
I think the
may have been the straw that broke the camels back. The apt upgrade failed again. I tried to reboot the Pi to try again, but alas it does not boot. Unfortunately, I didn't save the output on my first run. Before I reformat my card and do a fresh install, is there anything I can get off the SD card? A log file or something that may be useful? Thanks for your help! |
@tenryou-17 The downside or RAM log is that there are no system logs available after power off. You could check To have better control about file system errors:
And of course you could even move the whole system to a USB drive. Since RPi3 you cannot only move the root fs to some USB drive, but it can boot from there, after programming it (can be done via dietpi-config as well). From RPi3+ on this programming is not even required anymore. |
So in my haste to get my system up and running after work, I totally forgot to check I have never heard about Your points about safeguarding against file system errors are excellent. Thank you so much. Going forward I will make it a point to keep checking Thanks very much for your support @MichaIng. I appreciate the time you've taken to craft such informative responses. The community appreciates you <3 |
@tenryou-17 Important for this to work is that in Important as well to know is that RPi kernel/bootloader has an integrated fsck. It runs before the init system (systemd) has been loaded and can be forced for every boot by adding |
Details:
Steps to reproduce:
Expected behaviour:
Actual behaviour:
Extra details:
Additional logs:
The text was updated successfully, but these errors were encountered: