May 27, 20188 yr I was moving some files around on my hard drives when all of a sudden I noticed none of my containers were running. I went into the Docker tab, but all I see is the error, "Docker Service failed to start". I tried restarting the service manually, even rebooted the server - service won't start. Upon reboot, a parity check has also kicked off, due to an unclean shutdown (I used the 'Reboot' button in the console as I normally do) Including my diagnostics file from after the reboot, when parity check kicked off...any help would be appreciated! proteus-diagnostics-20180526-2128.zip Edited May 30, 20188 yr by quinnjudge
May 27, 20188 yr Author Update: Fix Common Problems just alerted me: 1. Unable to write to cache - Drive mounted read-only or completely full (cache was nowhere near full prior to problems) 2. Call Traces found on your server - Your server has issued one or more call traces. This could be caused by a Kernel Issue, Bad Memory, etc. You should post your diagnostics and ask for assistance on the unRaid forums
May 27, 20188 yr Community Expert Cache pool is messed up, it's only using a device and it's corrupt, when it gets like this easiest way to fix it to backup the pool, recreate it and restore the data.
May 28, 20188 yr Author Thanks for the help so far, but it seems there may be deeper problems... After wiping/reformatting the cache pool, I am now unable to start the VM Manager, getting the error, "error : virNetSocketNewListenTCP:343 : Unable to resolve address '127.0.0.1' service '16509': Address family for hostname not supported". I am starting to wonder if there is something deeper that is causing issues...I guess I don't know if this is a completely random coincidence, or is somehow related to the original corruption of the cache pool... I have rebuilt the cache pool and recovered all of my docker containers. I have a (believed good) copy of all of the .img files for my VMs, and a backup of the libvirt.img file from a week ago. I am also attaching a new diagnostics file...any help with this is greatly appreciated! proteus-diagnostics-20180527-2158.zip
May 28, 20188 yr Community Expert Quote May 27 20:24:07 Proteus emhttpd: Starting services... May 27 20:24:07 Proteus emhttpd: shcmd (318): /usr/local/sbin/mount_image '/mnt/user/system/libvirt/libvirt.img' /etc/libvirt 1 May 27 20:24:07 Proteus kernel: BTRFS info (device loop2): disk space caching is enabled May 27 20:24:07 Proteus kernel: BTRFS info (device loop2): has skinny extents May 27 20:24:07 Proteus root: Resize '/etc/libvirt' of 'max' May 27 20:24:07 Proteus kernel: BTRFS info (device loop2): new size for /dev/loop2 is 1073741824 May 27 20:24:07 Proteus emhttpd: shcmd (320): /etc/rc.d/rc.libvirt start May 27 20:24:07 Proteus root: virtlockd is already running... I don't know what virtlockd is but try again after rebooting.
May 30, 20188 yr Author Looks like that fixed it, and everything is back up and running properly - thanks for your help!
Archived
This topic is now archived and is closed to further replies.