I guess we need an error message that is pointing us in some direction.
OMV Webgui not working
-
- OMV 5.x
- MarcS
-
-
journalctl -xb
And the output of this?
I have managed to run journalctl -xb and transfer the file.
Maybe someone can detect the issue in here.
Thank you so much!
-
Those logs have time stamps 30.06 and 01.07. Are those current ones and the clock on the RPi is not set correctly?
-
-
I will check
-
I confirm the date command shows Thu Jun 30 18:43
-
-
-
Yes, you are right. Thanks for the pointer.
Will try to switch Kernels.
-
I might also try to rebuild the system. Does anyone know where the config files of Snapraid and Mergerfs are located in OMV?
-
Kernel 5.10.103-v71+ will just not boot for me.
Does anyone know how I can switch Kernels?
I have the following folders on the boot drive
/boot [has Kernel5.10 files]
/boot.bak [has a Kernel 5.9.0-0.bpo]
/backup/boot [has config files and vmlinuz files, all related to 5.10.0-0.bpo.xx]
-
-
Kernel 5.10.103-v71+
That is the armhf kernel.
To boot the arm64, edit the config.txt on the sd card to have a line with arm64=1
-
Now I end up with Kernel 5.10.103-v8+
but also in emergency Mode
-
ok. I managed to boot into a clean system but there is still a problem with the fstab.
Although I am commenting out a mount point that keeps creating issues, OMV re-generates the fstab with the problem mount point.
Where can I stop this ?
-
-
Is this mergerfs? I think you can disable fstab in the plugin. Then systemd will be used instead.
-
Unfortunately that flag only exists in OMV6.
But I think mergerFS is definitely my problem together with OMV's Fstab generation.
The list of devices in MergerFS shows one drive twice and when I try to see Filesystems in OMV-GUI nothing shows up (although I can see all files on the command line).
Participate now!
Don’t have an account yet? Register yourself now and be a part of our community!