Skip to content
View in the app

A better way to browse. Learn more.

Unraid

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

VMs/Containers missing following xfs_repair

Featured Replies

After a migration to a new server, I had to run xfs_repair to see my shares which had disappeared.

 

Once I did that, the shares returned (hooray) - but all my Docker images and VMs have disappeared. I think this is due to them living on the cache drives (BTRFS).. But whatever the reason, I'm stuck and can't get my VMs etc to show up. Attached the diagnostics.

 

Thanks

 

 

unraid-2-diagnostics-20191015-1028.zip

  • Community Expert

Both loop devices are mounting correctly but appear empty:
 

Filesystem      Size  Used Avail Use% Mounted on
/dev/loop2       20G   17M   20G   1% /var/lib/docker
/dev/loop3      1.0G   17M  905M   2% /etc/libvirt

Possibly another copy exists on the array.

  • Author
14 minutes ago, johnnie.black said:

Both loop devices are mounting correctly but appear empty:
 


Filesystem      Size  Used Avail Use% Mounted on
/dev/loop2       20G   17M   20G   1% /var/lib/docker
/dev/loop3      1.0G   17M  905M   2% /etc/libvirt

Possibly another copy exists on the array.

Cool  - and thanks for the quick reply - but just to clarify - what am I looking for a duplicate copy of? I can see for example that there is a copy of docker.img on both the /mnt/cache and /mnt/user, but to be fair I am quite in the dark when it comes to the innards of Unraid :/

  • Community Expert

/mnt/cache and /mnt/user will be the same, try typing:

 

find /mnt -name libvirt.img

I recommend always using disk paths for those files to avoid this, /mnt/cache or /mnt/diskX, instead of /mnt/user

  • Author

For example:

 

root@unraid-2:~# find /mnt -name docker.img
/mnt/user/system/docker/docker.img
/mnt/user0/system/docker/docker.img
/mnt/cache/system/docker/docker.img
/mnt/disk1/system/docker/docker.img

 

With this in mind I went to the Docker settings, changed the location of appdata and docker.img to the 'cache' variant, but no dice - still no containers showing up when re-enabling Docker.

 

Do I need to do some other reconfig?

 

Thanks again

 

  • Community Expert
1 hour ago, jmbrnt said:

IFor example:

 

root@unraid-2:~# find /mnt -name docker.img
/mnt/user/system/docker/docker.img
/mnt/user0/system/docker/docker.img
/mnt/cache/system/docker/docker.img
/mnt/disk1/system/docker/docker.img

 

With this in mind I went to the Docker settings, changed the location of appdata and docker.img to the 'cache' variant, but no dice - still no containers showing up when re-enabling Docker.

 

Do I need to do some other reconfig?

 

Thanks again

 

For this purpose ignore the /mnt/user* variants as they are just different views of the files on the physical disks being seen via the User Share layer in Unraid.  I think the 'cache' variant of the file takes precedence at the User Share level.   If /mnt/cache is not working then try the /mnt/disk1 path in case that is the one that contains your docker images.  

Edited by itimpi

  • Community Expert
8 minutes ago, itimpi said:

I think the 'cache' variant of the file takes precedence at the User Share level.

Correct, you need to point to /mnt/disk1, though it might be a good idea to then move them to cache.

  • Author
35 minutes ago, johnnie.black said:

Correct, you need to point to /mnt/disk1, though it might be a good idea to then move them to cache.

OK - I thought they were on the cache... I'm still not sure why anything changed though, was all working before I fixed the xfs.

 

I'll give it a shot moving to /mnt/disk1 and see..

  • Community Expert
2 minutes ago, jmbrnt said:

I'm still not sure why anything changed though

If it was disk1 that failed mount, and since they were set to use /mnt/user, new images would have been created, and after the fs on disk1 was fixed the ones on cache take precedence, so they remain the ones in use.

  • Author
1 minute ago, johnnie.black said:

If it was disk1 that failed mount, and since they were set to use /mnt/user, new images would have been created, and after the fs on disk1 was fixed the ones on cache take precedence, so they remain the ones in use.

I just changed it to point at /mnt/disk1, and Docker is all go again.

 

Should I just wipe the cache out and re-add it, copy the stuff from /mnt/disk1 back to the cache? The logic here is I did set it to /mnt/cache and still didn't work.

  • Community Expert

Delete docker.img on cache, stop docker service, run the mover, set docker path to /mnt/cache/system/docker.img, re-enable docker service.

  • Author
14 minutes ago, johnnie.black said:

Delete docker.img on cache, stop docker service, run the mover, set docker path to /mnt/cache/system/docker.img, re-enable docker service.

You beaut, that seems to have solved it.

 

Thanks very much.

Archived

This topic is now archived and is closed to further replies.

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.