Why might this keep happening?
Without logs, it is impossible to know. Are you rebooting between? Is the media your OS is installed on old? You definitely should not need to keep doing this.
Without logs, it is impossible to know
Fair comment. If it happens again, what logs do I need? The contents of the red box dialogue or more than that?
Are you rebooting between?
Between what exactly? My NAS is NOT on 24/7 if that's what you mean. In each case, I fired it up, checked for updates and tried applying those showing from the GUI. I usually reboot AFTER a successful upgrade although it's not always required.
Is the media your OS is installed on old?
No. It's a little-used 120GB SSD.
You definitely should not need to keep doing this.
Yes, I thought it was unusual.
I am having this same problem also for 8.0.7 and 8.0.8 updates
I reboot once a day.
Using a newish SD card for OS.
Kernel: Linux 6.17.13+deb13-amd64
Is the package cloud-init installed on your system?
# dpkg -l | grep cloud-initNo, the package cloud-init is not installed on my system.
what logs do I need? The contents of the red box dialogue or more than that?
red box -yes. any logs that might be helpful like term.log and history.log from /var/log/apt/.
Between what exactly? My NAS is NOT on 24/7 if that's what you mean. In each case, I fired it up, checked for updates and tried applying those showing from the GUI. I usually reboot AFTER a successful upgrade although it's not always required.
Since I didn't know what you were doing, I had to ask generally. I was curious if you were rebooting between the dpkg problems. Now, I know your system is not on all of them time and that answers more questions. Do you happen to have the writecache plugin installed and still configured to use system memory? I recommend changing that if you do.
red box -yes. any logs that might be helpful like term.log and history.log from /var/log/apt/.
Noted. I will gather those things if I have a recurrence.
Since I didn't know what you were doing, I had to ask generally. I was curious if you were rebooting between the dpkg problems. Now, I know your system is not on all of them time and that answers more questions.
You're quite right. You couldn't know how I use my system.
Do you happen to have the writecache plugin installed and still configured to use system memory? I recommend changing that if you do.
I do have it installed, yes. I thought it was needed for ANY form of solid state storage but something I read yesterday suggested it was just USB sticks and SD cards rather than SSDs. I unticked the box to use system memory and used a share instead. Or, am I better off disabling it completely?
Thanks for all your help. I'm very grateful 
I thought it was needed for ANY form of solid state storage but something I read yesterday suggested it was just USB sticks and SD cards rather than SSDs.
It helps any write-limited storage. Probably not needed on good ssds and nvme though. I still use it on my system with nvme.
I unticked the box to use system memory and used a share instead. Or, am I better off disabling it completely?
Using a share means that you don't lose anything if the system crashes/shuts down improperly. Shouldn't hurt anything to use it. Up to you if you think you need to limit writes to your drive.
Thanks a million for the extra details. It seems reasonable to leave it as it is now that I made the change you suggested. If it's good enough for you, it's good enough for me.
I may be experiencing the same problem, and can help with more info
See attached and ask me what you need. I have not rebooted, and would like to avoid that.
The error came up on the initial upgrade ("OMV-Upgrade-to-8081-ERROR-1.png") where I captured that screenshot. I also captured the notification ("OMV-Upgrade-to-8081-ERROR-1.txt").
Then, without reboot, I simply repeated the install and got the following result: "OMV-Upgrade-to-8081-ERROR-2.png". After that second attempt I got "OMV-Upgrade-to-8081-ERROR-3.png".
I also attached dmesg output for today ("OMV-Upgrade-to-8081-ERROR-4-dmesg-20260129.txt")
Hope this helps.
Cheers.
You can ignore the systemd-sysv-generator warnings. These warnings need to be fixed by upstream Debian.
Please run omv-engined -d -f in a root shell and check if there are reported any errors.
You can ignore the systemd-sysv-generator warnings. These warnings need to be fixed by upstream Debian.
Please run omv-engined -d -f in a root shell and check if there are reported any errors.
Running now ... how long should it run ? I am getting a lot of
SIGCHLD received ...
Child (pid=1869626) terminated with exit code 0
Child process forked (pid=1869636)You can stop it (CTRL-C). After that run monit restart omv-engined.
You can stop it (CTRL-C). After that run monit restart omv-engined.
Ok. Done that. Next ... ?
Ok. Done that. Next ... ?
Nothing. That was just to validate that omv-engined has no problems.
Looking at your post again, I don't really see where the problem lies. Your attached logs only show unimportant warnings that can be ignored and an error message from omv-engined that we have just checked without any problems. When an OMV package is installed, omv-engined is restarted at the end, which can lead to the log output you attached.
Ok. Thank you.
I upgraded from 8.0.8 to 8.0.9 without any errors today.
I had taken the advice to change my Write-cache plugin to Not to write to memory, but instead write to a workspace folder.
Thank you ryecoaaron.
I upgraded from 8.0.8 to 8.0.9 without any errors today.
I had taken the advice to change my Write-cache plugin to Not to write to memory, but instead write to a workspace folder.
Thank you ryecoaaron.
This echoes my experience. The upgrade from 8.0.8 to 8.0.9 is the first update that worked for me without having to do 'dpkg --configure -a' first since I upgraded from OMV 7. I'm really hoping it will work as normal from now.
Thanks from me too.
The problem is back again. This time it is persistent. I applied the suggested two commands in above posts from "votdev".
All my screenshots are attached.
What shall I try now ?
Cheers.
Don’t have an account yet? Register yourself now and be a part of our community!
