Just us an update:
I deleted the array and tried to mount the drives individually.
It still throws the same error as above.
Where is my fault here?
You can see the excerpt of the syslog at the moment of the reboot above. It is just empty...
I absolutely expect that. I still do not understand why it does look like something like this happens.
Maybe someone has another idea where and how to do research?
Anyone else has suggestions or knows what is happening when I press the mount button?
I do not understand how it can happen, that the root Filesystem seems to get unmounted.
Or is there a possibility to see pending changes and what they look like?
Reacted with to ryecoaaron’s post in the thread OMV 5.x Mounting through Web Interface throws error and lets OMV reboot.Reaction (Post)Try the proxmox kernel (tab to install it in omv-extras) to see if it helps. And is there anything in /var/log/watchdog/?
Thanks for your suggestions.
The watchdog log directory is empty and I trying the proxmox kernel now. I will update this answer afterwards.
One thing I think I saw: It looks like OMV is unmounting the "/" (root) partition, when trying to mount a new…
Yes, but unfortunately I cannot see what exactly.
5.7.0-0.bpo.2-amd64 #1 SMP Debian 5.7.10-1~bpo10+1 (2020-07-30) x86_64
This is the kernel I use.
I had the same error before, several times. Usually using salt to fix fstab solved the issue. This time…
After the reboot when I apply the pending config changes, the watchdog sends me following mail:
Message from watchdog:
The system will be rebooted because of error 2 = 'No such file or directory'
And this is the syslog (between 19:32 and 19:34):
I think something on the OS side fails. This is a reproducable behaviour. I have an Intel 1155 Sockt board with a Xeon on it. It works since several months and is reliable over month, except I do what is described above. I even could reproduce it on…
Posted the thread OMV 5.x Mounting through Web Interface throws error and lets OMV reboot.ThreadHi community,
I just added a new software raid and waited till it got completely synced. Afterwards I created an ext4 filesystem. As soon as this has been finished I wanted to mount the filesystem. This gave me an error in the web interface (502 - bad…
One of my drives disappeared suddenly although it is healthy and usable.
I found it to be sda now. After deleting and formatting it, every try to mount immediately lets OMV die.
I had this in the past and fixed it through a new installation.