In that case I would restart to check if rootfs is now mounted correctly.
And how can I do this excactly?
In that case I would restart to check if rootfs is now mounted correctly.
And how can I do this excactly?
And how can I do this excactly?
Run
sudo reboot
When the system reboots check if you can access the GUI. If rootfs is still in read-only mode, try to remount it as raulfg3 said:
sudo mount -o remount,rw /
Run
sudo reboot
When the system reboots check if you can access the GUI. If rootfs is still in read-only mode, try to remount it as raulfg3 said:
sudo mount -o remount,rw /
After the reboot I am able to go to the login screen from GUI but I am not able to login, still the same error message. Even after the remount command (sudo mount -o remount,rw /) it didnt work.
- It is not a cache problem. Have you already tried Ctrl+shift+R
- rootfs is not full. You have now removed those foreign devices.
- rootfs is not mounted read-only. Did you execute the command I gave you? The one from raulfg3 had a typographical error.
It is not a user blocking issue. You have already tried omv-firstaid.
...
At this moment it doesn't occur to me what else it could be...
Display More- It is not a cache problem. Have you already tried Ctrl+shift+R
- rootfs is not full. You have now removed those foreign devices.
- rootfs is not mounted read-only. Did you execute the command I gave you? The one from raulfg3 had a typographical error.
It is not a user blocking issue. You have already tried omv-firstaid.
...
At this moment it doesn't occur to me what else it could be...
Yes I have entered the command sudo mount -o remount,rw / with success but it didnt fix the issue. I am confused…
Have you installed anything on the host at any time?
What is the output of:
sudo systemctl list-unit-files --type service --all
Several pages will appear, you can go forward and back with RePag and AvPag
What is the output of:
sudo systemctl list-unit-files --type service --all
Several pages will appear, you can go forward and back with RePag and AvPag
I hope this will help:
I had to put on my glasses to read those images Next time it is better to publish in text format, copy and paste. And more comfortable for you too.
At first glance I see two things:
1. You have active apparmor. I'm not sure if it could influence access to the GUI, in any case you should follow the instructions here. RE: docker not working since omv-upgrade
2. You have pihole installed on the host, or at least a pihole-FTL service appears. This is so? pihole could affect OMV.
I don't think I see anything else that might be relevant. Maybe someone can see something else.
Display MoreI had to put on my glasses to read those images
Next time it is better to publish in text format, copy and paste. And more comfortable for you too.
At first glance I see two things:
1. You have active apparmor. I'm not sure if it could influence access to the GUI, in any case you should follow the instructions here. RE: docker not working since omv-upgrade
2. You have pihole installed on the host, or at least a pihole-FTL service appears. This is so? pihole could affect OMV.
I had to use screenshot, soo many words are not allowed 😅
1. I will try the instruction now.
2. The Backup I have used is 2 days old and pihole has worked the whole time.
2. The Backup I have used is 2 days old and pihole has worked the whole time.
I found some reference on google that says that pihole could affect the web GUI (on another OMV-like system). I would try just stopping that service and testing if the GUI works.
systemctl stop pihole-FTL.service
If the GUI doesn't work just start that service again.
systemctl start pihole-FTL.service
1. You have active apparmor. I'm not sure if it could influence access to the GUI, in any case you should follow the instructions here. RE: docker not working since omv-upgrade
I have the apparmor deactivated but it still dont work...
Don’t have an account yet? Register yourself now and be a part of our community!