-
-
Notifications
You must be signed in to change notification settings - Fork 498
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-upgrade 6.25.3 -> 6.32.2: dietpi-ramdisk: No such file or directory #3812
Comments
System is running ok, reboots ok etc. just concern that Ram is no-longer used and SD card being used instead (eventually leading to failure/corruption/performance degrade of SD). Please comment if dietpi-ramdisk is now obsolete and what replaced it if so. thanks for all your support :) |
Hi, many thanks for your report. If I'm not mistaken this can be ignored. Isn't it @MichaIng maybe similar to this?? #3532 (comment) |
Many thanks for your report. First of all: Yes And yes, we had this update issue one or two times before, which occurred because the updater somehow did not kill itself (more precisely, its parent script) as intended and But just to be very sure, do you still have the updater log in terminal, or the related log file:
Ah yes all makes sense, the v6.25-only bug where I moved the output split for log file into a pipe, but the pipe input processes looses control over the parent shell, hence cannot kill it anymore. Learning never ends 😄. |
Thanks for the timely and informative post! The situation is exactly as you describe and the installer did complete successfully. I'll paste the log FYI in any case. thanks again.
Details as previously shared. The log: Logfile attached. Click to expand!
|
Okay, great, everything is fine then. Luckily there are not much systems on v6.25 anymore, since a reliable fix on a 6.25 system prior to the update is not reliably possible. We could hack something inside via MOTD but not everyone has it enabled. |
Details:
Steps to reproduce:
(6.25.3 -> 6.32.2)
Expected behaviour:
Actual behaviour:
Extra details:
Additional logs:
The text was updated successfully, but these errors were encountered: