Hello,
i find that my scheduled daily omv-regen backup was done last time on May 27th. Every 'omv-regen backup' try (scheduled or manually) is leading to system restart. On May 27th. (few hours after last backup) my system was updating. Also in GUI OMV is not listed my system disk's parameters like before. Did someone can check my log for errors, please?
The last activity before restart:
The only way omv-regen backup could cause a reboot is if you have the option set to update the system and if that update is causing an error. That has nothing to do with omv-regen but with system updates. If you run omv-upgrade you will probably have the same result.
Regarding the logs you have published, I only see updates, but no errors, except for a missing firmware and a series of folder reading errors at the end that I don't understand what they mean, I don't know what Armbian is doing with those folders. Someone else will have to help with that.
I don't see anything that would cause reboots except that this is an unreliable 32-bit system. You can see the omv-regen logs in /var/log/omv-regen.log.1, 2, 3...
Maybe you should check the status of that system disk, it may be failing.
Thanks for answer.
Option "update the system" is not set.
omv-upgrade is not causing system reset. Is still working.
Strange thing is OMV not showing info about sd card, but info can be read from:
omv-regen regenera also is not able to show/read info from sdcard? Is it error or normal situation when I'am running regenera with old system disk?
Anyway i will try to change my sd card in few days.
Option "update the system" is not set.
There is nothing in omv-regen backup that can cause a reboot, the only thing the script does is collect system information and store it in the backup. You can see it here. https://github.com/xhente/omv-…/omv-regen.sh#L1425-L1534
Did you look at the omv-regen log?
omv-regen regenera also is not able to show/read info from sdcard? Is it error or normal situation when I'am running regenera with old system disk?
If the script cannot detect the file system it simply warns you. That np means that that file system has some problem.
Strange thing is OMV not showing info about sd card, but info can be read from:
Do you have the openmediavault-sharerootfs plugin installed? Otherwise OMV will not show that file system.
I've exchanged sd card, installed new armbian, omv and omv-regen. And after successfully 'omv-regen regenera' problem is back.
Exactly the same.
Trying command from this line (#1497 )and found that this is causing freeze of system and 'hard' reset:
systemctl list-unit-files | tee "${CarpetaRegen}${ORB[Systemctl]}"
After that omv is not working in my case. Freeze and reset.
Trying command from this line (#1497 )and found that this is causing freeze of system and 'hard' reset:
systemctl list-unit-files | tee "${CarpetaRegen}${ORB[Systemctl]}"
I have no idea what could be the reason for the systemctl list-unit-files command to cause a system reboot.
I encountered similar issues as shown in the screenshot here:
For context:
I created a backup with omv-regen and it was successful.
Next I removed / purged OMV from my machine (Raspberry pi 4).
Then I re-installed OMV following the usual instructions in the guide here.
After the OMV installation and rebooting the pi, I ran sudo omv-regen and tried to regenera / restore from my backup, and I saw the same errors as seen above.
What went wrong here? 
The notice about the system hard drive is only a warning. omv-regen is not able to read the serial number of that hard drive, which I assume is an SD card or a pendrive. So it's just a warning, but it doesn't prevent regeneration from being executed.
What is preventing the regeneration is that you have made some configuration on that system. You can only run omv-regen on a clean system. No configuration should be done in the GUI. The documentation is clear about this.
omv-regen 7.0.20 is in the repository. The disk check has been replaced with a warning.
Since I am not always able to detect serial numbers on hard drives and this seems to cause confusion I have removed it.
Thanks for the reply. So when I uninstalled / purged OMV from my machine, and then reinstalled it - I expected it to completely remove any configuration I had, but it actually didn't.
So when I started the newly installed OMV, my admin password, users, groups, drives, filesystems, SMB shares etc. were all still there. Is this expected behaviour?
Worth noting that all plugins were removed and my email notifications needed to be set again though.
So for now, I'm ok because it somehow preserved most of what I wanted to restore anyway. But out of curiosity, could this be why it showed the configuration error message?
Yes, that is expected.
omv-regen only makes sense if you are setting up a new, clean system. Otherwise the configurations that are already in the system could be in bad condition and you will not achieve anything, only make it worse.
Installing OMV from scratch costs between 10 or 20 minutes. You can install it on a pendrive and keep your original system disk disconnected. In fact, that's what I recommend doing, so you can always go back if something doesn't go as you expect.
Don’t have an account yet? Register yourself now and be a part of our community!
