OMV on Raspberry and SD Card full!
-
- OMV 5.x
- Yield79
-
-
Usually when this happens it is because you have configured docker containers directly on the OMV disk. Install WinSCP to see your folders and where you have the problem.
https://openmediavault.readthe…/newuserguide.html#winscp
You will have to make a copy of your container config folder and change it disk, if this is the real problem.
Take a look here and see how you should do it so it doesn't happen again.
-
Or a rsync job that failed the destination
-
-
Here is described how to find out what is filling your root fs
-
So, the problem could be due to the fact that, sometimes due to power cuts, when restarting the Raspberry fails to mount the USB disks and I am forced to restart the containers.
In these cases, the doker apps, I guess, are going to write to the SD instead of USB disks.
I connected via WinSCP, but I don't understand what I can delete ...
Here is described how to find out what is filling your root fs
now I read this topic well and I will try to follow the directions.
in the meantime, thanks for the support
-
Tell us more about your docker setup. Did you move the docker files off the sd-card?
If you changed it, how did you do it and where did you place it..
Do you use the USB-disk for anything else than docker? In that case (disk not mounted on reboot), I would be more concerned about /srv/dev-disk-by-... folders being filled with data which should not go there.
Eigther way, you will only find the files, if you unmount the USB-disk when checking used space.
-
-
Tell us more about your docker setup. Did you move the docker files off the sd-card?
Eigther way, you will only find the files, if you unmount the USB-disk when checking used space.
Docker Storage has the same folder as you
But when i use a docker compose on Portainer, i use usb disks. example:
Code
Alles anzeigenversion: "2.1" services: jellyfin: image: linuxserver/jellyfin container_name: jellyfin ........ volumes: - /srv/dev-disk-by-id-usb-WDC_WD10_EARS-00Y5B1_152D00539000-0-0-part2/jellyfin_svr:/config - /srv/dev-disk-by-id-usb-WDC_WD10_EARS-00Y5B1_152D00539000-0-0-part2/jellyfin_svr:/data/tvshows - /srv/dev-disk-by-id-usb-WDC_WD10_EARS-00Y5B1_152D00539000-0-0-part2/jellyfin_svr:/data/movies - /srv/dev-disk-by-id-usb-WDC_WD10_EARS-00Y5B1_152D00539000-0-0-part2/jellyfin_svr:/opt/vc/lib #optional - /srv/dev-disk-by-id-usb-WDC_WD10_EARS-00Y5B1_152D00539000-0-0-part2:/NAS/Volume_1 - /srv/dev-disk-by-id-usb-WDC_WD20_EFRX-68AX9N0_152D00539000-0-1-part2:/NAS/Volume_2 - /srv/dev-disk-by-label-HDD3:/NAS/Volume_3 .........
Zitat
In that case (disk not mounted on reboot), I would be more concerned about /srv/dev-disk-by-... folders being filled with data which should not go there.I think this is the problem
-
I think you should check your volume paths. Make sure they are well defined and pointed at the disks.
On the other hand, if you read the guide I mentioned in post # 2 of this thread, you will see that the var/lib/docker folder is preferably on another disk.
-
To find the data on your disk:
- stop all services in omv except ssh
- go to the command line by ssh
- become root and be careful from now on
- stop the docker daemon (will stop all containers too) systemctl stop docker
- unmount you disks
- mount
- cd /srv
- du -xud1
post the outpur of the last three commands
-
-
-
Do it like this:
- Stop the docker daemon (and all containers with it) systemctl stop docker
- rsync -aHv /var/lib/docker /srv/dev-disk-by-id-usb-WDC_WD10_EARS-00Y5B1_152D00539000-0-0-part2/omv/docker
Copy all old docker contents to new location keeping permissions and possible hard links and be verbose about what it is doing - change the docker location in the OMV UI
- Restart the docker daemon in the OMV UI (will restart containers as well)
- Check if all your containers are running as expected
- remove /var/lib/docker
-
Do it like this:
- Stop the docker daemon (and all containers with it) systemctl stop docker
- rsync -aHv /var/lib/docker /srv/dev-disk-by-id-usb-WDC_WD10_EARS-00Y5B1_152D00539000-0-0-part2/omv/docker
Copy all old docker contents to new location keeping permissions and possible hard links and be verbose about what it is doing - change the docker location in the OMV UI
- Restart the docker daemon in the OMV UI (will restart containers as well)
- Check if all your containers are running as expected
- remove /var/lib/docker
Just a remark:
Between 3 and 4, don't forget to "Save"
Although, I also think it's better to:Before #3
1st, uninstall docker
After #3
install docker with the path changed and saved.
-
-
-
-
sudo mv /var/lib/docker /var/lib/docker.backup
to be save, you can set a symlink
ln -s /srv/dev-disk-by-id-usb-WDC_WD10_EARS-00Y5B1_152D00539000-0-0-part2/omv/docker /var/lib/docker
-
-
done. I restart the whole system and check.
-
-
So the links are not pointing to the correct docker directory. Check this again.
-
-
therefore, in omv the path of the docker is
/ srv / dev-disk-by-id-usb-WDC_WD10_EARS-00Y5B1_152D00539000-0-0-part2 / omv / docker / dockerroot
I added / dockerroot to all the previous steps.
if I click on the simlink via winscp, it takes me correctly to the path indicated above
I stop the docker service and try to rerun???
sudo rsync -aHv /var/lib/docker.backup /srv/dev-disk-by-id-usb-WDC_WD10_EARS-00Y5B1_152D00539000-0-0-part2/omv/docker/dockerroot
-
Jetzt mitmachen!
Sie haben noch kein Benutzerkonto auf unserer Seite? Registrieren Sie sich kostenlos und nehmen Sie an unserer Community teil!