OMV7: reboots every time I try to change configuration

perhaps the fast way to recover is to do a new fresh install.

depending how you install first time is more or less easy to be online in minutes.

@ondras also experiencing the same thing OMV 7 installed on Debian Bookworm ODroid HC4.

Do you have docker by chance on your system?

I have the same problem after clean install of OMV7.

Odroid HC4, Debian 12 clean install via petitboot, openmediavault via install script.

Apply changes in WebUI, CLI stuff like restarting a service (networking, workbench etc.) results in a sudden reboot. No useful information in logs when watching journalctl.

No problems with Debian 11 + OMV6.

ondras did you find a solution?

Edit: This seems to be a common problem: Can't apply changes after new install of OMV

Quote from grittywheel

I have the same problem after clean install of OMV7.

Odroid HC4, Debian 12 clean install via petitboot, openmediavault via install script.

Apply changes in WebUI, CLI stuff like restarting a service (networking, workbench etc.) results in a sudden reboot. No useful information in logs when watching journalctl.

No problems with Debian 11 + OMV6.

ondras did you find a solution?

Edit: This seems to be a common problem: Can't apply changes after new install of OMV

Display More

Are you using docker with your install?

Hi.

I also have restarts on odroid HC2 device.

Thread

After last update omv-regen backups failed, system restarts and omv don't show info about system disk SD.

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:




OS: Armbian (24.5.1) armv7l --- Host: Hardkernel ODROID XU4 --- Kernel: 6.6.31-current-odroidxu4 --- Shell:…

Slavek

Jun 2nd 2024

Quote from MikeSmith

Are you using docker with your install?

No, the system is practically unusable, so I never got to setting stuff up.

Quote from ryecoaaron

I added docker and two big containers to my odroid hc4 test. Made random changes all over the web interface. Still can't get the system to reboot. Even the following command didn't do it:

root@odroidhc4:~# omv-salt deploy run chrony collectd fstab hosts hostname monit nginx phpfpm systemd-networkd watchdog

Did you setup OMV via petitboot (Debian12) and the omv install script?

Quote from ryecoaaron

Nope. I removed petitboot (part of the armbian instructions) and installed Armbian Debian 12 (https://wiki.omv-extras.org/do…:armbian_bookworm_install). Then used the install script.

I tried to the same, but unfortunately the current image at https://www.armbian.com/odroid-hc4/ is an automated build and not suitable for the omv install according the guide you're linking to. Either I have to wait for a proper image or else I have to learn how to build an image myself.

It's in the guide under the "Not supported" section.

Quote

WARNING!

You are using a automated build meant only for developers to provide constructive feedback to improve build system, OS settings or UX.

If this does not apply to you, STOP NOW! Especially don't use this image for production since things might not work as expected or at all. They may break anytime with next upgrade.

I get this warning when booting the Armbian Bookworm from the Odroid HC4 page.

Quote from grittywheel

I tried to the same, but unfortunately the current image at https://www.armbian.com/odroid-hc4/ is an automated build and not suitable for the omv install according the guide you're linking to. Either I have to wait for a proper image or else I have to learn how to build an image myself.

That's very strange, not saying you're wrong but I use: https://www.armbian.com/odroid-xu4/ and have OMV working.

I followed: https://wiki.omv-extras.org/do…:armbian_bookworm_install

• • wget -O - https://github.com/OpenMediaVault-Plugin-Developers/installScript/raw/master/preinstall | sudo bash
  • wget -O - https://github.com/OpenMediaVault-Plugin-Developers/installScript/raw/master/install | sudo bash

And it worked.

Strange that hc4 wouldn't work considering it's newer hardware.

What makes you say that the hc4 build is not suitable for the OMV install according to the guide? I've read it and didn't notice anything.

I got OMV7 to work without restarts (so far) and I think petitboot (w/ Debian 12) is the culprit.

So future readers here is a guide:

1) Remove petitboot from Odroid HC4 (instructions)

2) Download and write Armbian Bookworm minimal image to SD-card and install

3) Install OMV using not only the install script but also the preinstall script as explained in this guide

ryecoaaron I understand that Armbian for HC4 is not officially supported by the Armbian team, but only by community. The reason why I hesitated using the Armbian Bookwork image available on armbian.com/odroid-hc4 is that the image is apparently an automated build and therefore issues the warning upon boot as I described earlier - also in the guide "Not supported" section the warnings are very clear about not using automated builds.

What I did was I learned how to use the Armbian build framework and build my own stable image for Odroid HC4. This took some time because of all sorts of issues for me (too few loop devices on Ubuntu 22.04, Armbian mirror problems with bookworm at the moment etc.)

Anyway, I guess I could've used your solution but this was also a great learning experience for me.

Thank you for your help and your work on the install script!

MikeSmith See above

Same here exactly as described by ondras. It was running perfectly for months but during a move the SD card was damaged, and I just reinstalled it on Debian 12 from Petitboot and OMV using the Github script. I was able to set the Dashboard and to mount the file system but trying to apply any other setting reboot the HC4 without applying the configuration. I will prefer to avoid the Armbian fix. No obvious error message in the log just some things probably unrelated as in the Kernel log "spi-nor spi1.0: unrecognized JEDEC id bytes: 0b 40 18 0b 40 18" that just indicat a non-identified memory chips. Any idea?