rb2k
-
Posts
3 -
Joined
-
Last visited
Content Type
Profiles
Forums
Downloads
Store
Gallery
Bug Reports
Documentation
Landing
Report Comments posted by rb2k
-
-
I upgraded from RC5 to RC6.
Neither the docker service nor VMs are starting up.Docker service complains about /mnt/user/system/docker/docker.img
VMs complain about /mnt/user/system/libvirt/libvirt.img
Seems like the symlink is deadroot@server:/mnt/user# ls -lash /mnt/user/system 0 lrwxrwxrwx 4 nobody users 47 Mar 14 2021 /mnt/user/system -> /mnt/applications/system
This is the content.
root@TheSilence:/mnt/applications# ls -lash /mnt/applications/ total 24G 16K drwxrwxrwx 1 nobody users 98 Jul 17 2022 ./ 0 drwxr-xr-x 9 root root 180 May 19 14:14 ../ 0 drwxrwxrwx 1 nobody users 442 Apr 23 09:00 appdata/ 0 drwx--x--x 1 1000 users 14 Nov 25 2020 docker/ 0 drwxrwxrwx 1 nobody users 38 Jan 14 19:21 domains/ 24G -rw-r--r-- 1 root root 24G Mar 14 2021 hassio.qcow2 0 drwxrwxrwx 1 nobody users 264 Jan 14 19:17 isos/ 0 drwxrwxrwx 1 nobody users 124 Jun 21 2022 sync/
And it's on a mount:Quoteroot@server:/mnt/applications# mount | grep applications
/dev/sdd1 on /mnt/applications type btrfs (rw,noatime,ssd,discard=async,space_cache=v2,subvolid=5,subvol=/)
Unraid OS version 6.12.0-rc6 available
-
-
-
-
-
in Prereleases
Posted · Edited by rb2k
I found something over here on /mnt/disk1. A bit confused since it's a regular XFS drive and not my SSD where this used to be?
/dev/md1p1 is on /mnt/disk1 type xfs (rw,noatime,nouuid,attr2,inode64,logbufs=8,logbsize=32k,noquota)
root@server:/# ls -lash /mnt/disk1/system/docker/ total 51G 0 drwxrwxrwx 2 root root 24 Mar 14 2021 ./ 0 drwxrwxrwx 4 nobody users 47 Mar 14 2021 ../ 51G -rw-rw-rw- 1 nobody users 50G May 19 14:10 docker.img root@TheSilence:/mnt/applications# ls -lash /mnt/disk1/system/libvirt/ total 1.1G 0 drwxrwxrwx 2 root root 33 Mar 14 2021 ./ 0 drwxrwxrwx 4 nobody users 47 Mar 14 2021 ../ 1.1G -rw-rw-rw- 1 nobody users 1.0G May 19 14:09 libvirt.img
EDIT: "cp -R /mnt/disk1/system /mnt/applications/" fixed it.
I had to manually start the docker and VM service, but they're up and running now.
I am not 100% sure if I had some non standard setup somehow previously, but I do recall trying to move things to SSDs at some point. Maybe that caused the issue.