-
-
Notifications
You must be signed in to change notification settings - Fork 504
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-ramlog: No such file or directory #3509
Comments
Hi, many thanks for your report. As workaround you could try to create the file and reboot your system afterwards.
|
I can confirm that the workaround seems to be functioning, thanks. The file
|
well it's more |
I am logged on as user root and the message still remains (even after reboot). As previously stated it does not impair functionality I just wanted you to know in case something needs to be done about it. |
can you open |
Like this?
|
uhh looks like it's missing completely. Can you have a look to
|
As the error states the file is indeed not present:
|
ok you are missing quite some files. Seems something did goes wrong during update. I would recommend to clone the directory again |
Well this is a clean installation so i can't really do something about it or can I? Or do I have to build the image myself? |
What I meant was, that something during the update to DietPi v6.29.2 did not succeeded correctly as you are missing some data. So there are basically 2 ways. First one would be to clone the entire directory |
Okay thank you for the clarification. I have cloned the folder, since a fresh installation would not work due to the image update process being broken when using v6.14 image (this was a fresh install from today). With the cloned folder there are no more errors. Looks good to me as a workaround. |
Ok would it be possible to post your solution, how you cloned the directory. It might help others if they will hit similar |
I did this (be aware i have not extensively tested if everything works but as far as I have tested it does):
|
Just installed a new image. As soon as the
After restarting the installation works as expected. |
Thx for sharing the workaround. Regarding the initial issue, I guess @MichaIng would need to have a look. |
@Vec7or @Joulinar Very strange, especially since the update does not remove files from /boot/dietpi but only copies the ones from /DietPi/dietpi to /boot/dietpi. So even if this copy process would fail, the files would still be present. Even more, since the update is internally restarted, files are re-downloaded to /boot/dietpi actively. So this must have been failed at two stages... I'll run a test boot to see if I can replicate within VM. Own RPi device/server is started tomorrow, the ISP technician took 10 days longer to finally tomorrow enable our broad band internet.... |
@MichaIng btw have seen similar on our forum https://dietpi.com/phpbb/viewtopic.php?f=11&t=7607 as well as on the duplicate GitHub post #3513 All seems to run Strech |
Analysing the case on fresh NanoPi NEO (Stretch) image within systemd-nspawn container:
I'll create a debug branch to pause the update at certain stages and have a subshell for investigation... |
I see I need to get more and different SBC to be able test more in detail |
@Joulinar However back to topic, found the bug, a faulty patch from v6.16 to v6.17: 323454c |
@MichaIng |
Details:
Steps to reproduce:
Expected behaviour:
Actual behaviour:
Additional logs
is happeningExtra details:
Additional logs:
The text was updated successfully, but these errors were encountered: