[Docker failed to start on on reboot]

I tried upgrading but failed to be able to reboot afterwards.  Was getting kernel panic errors.  I just redid my usb stick and its back. Thanks

[Docker failed to start on on reboot]

Checked out ok.  Started up the system and array again.  Same log messages.  No docker. 

 

C:\>chkdsk /f D:
The type of the file system is FAT32.
Volume UNRAID created 7/20/2017 8:38 AM
Volume Serial Number is 272C-EBE2
Windows is verifying files and folders...
File and folder verification is complete.
Windows has checked the file system and found no probl
   15,122,992 KB total disk space.
          200 KB in 3 hidden files.
          176 KB in 22 folders.
      185,720 KB in 127 files.
   14,936,888 KB are available.

        8,192 bytes in each allocation unit.
    1,890,374 total allocation units on disk.
    1,867,111 allocation units available on disk.
 

[Docker failed to start on on reboot]

1 hour ago, Squid said:

Delete docker.img and recreate https://forums.unraid.net/topic/57181-docker-faq/#comment-564309

 

I gave that a shot a few times and no luck.  Docker will not start and same log.

[Docker failed to start on on reboot]

tower-diagnostics-20200130-1441.zip

 

Hello, so I stopped the array and did a clean shutdown.  When booted up docker failed to start.  The logs show

 

Jan 30 06:36:05 Tower emhttpd: shcmd (416): /etc/rc.d/rc.docker start
Jan 30 06:36:05 Tower root: starting dockerd ...
Jan 30 06:36:06 Tower kernel: SQUASHFS error: Unable to read fragment cache entry [846f5c]
Jan 30 06:36:06 Tower kernel: SQUASHFS error: Unable to read page, block 846f5c, size 1f0d4
Jan 30 06:36:06 Tower kernel: SQUASHFS error: Unable to read fragment cache entry [846f5c]
Jan 30 06:36:06 Tower kernel: SQUASHFS error: Unable to read page, block 846f5c, size 1f0d4
Jan 30 06:36:06 Tower kernel: SQUASHFS error: Unable to read fragment cache entry [846f5c]
Jan 30 06:36:06 Tower kernel: SQUASHFS error: Unable to read page, block 846f5c, size 1f0d4
Jan 30 06:36:06 Tower kernel: SQUASHFS error: Unable to read fragment cache entry [846f5c]
Jan 30 06:36:06 Tower kernel: SQUASHFS error: Unable to read page, block 846f

[Troubleshooting Win 10 VM pausing]

24 minutes ago, Squid said:

Just to get it out of the way, is the Windows VM set to sleep / hibernate in its power management?

It was set to sleep.  I changed it to never.  Assume that would cause it as well.

[Troubleshooting Win 10 VM pausing]

Hello,

 

I am having issues with a Windows 10 VM pausing on me and the solutions I have read were all related to disk being full.  I am using cache prefer and it is showing plenty of room, however I did read about allocation issues and the suggestion is to balance.  I did that.  My VM is still pausing. 

 

I am trying to rule out any cache setup issues on the pausing VM issue.

 

Thanks

 

 

 

 

tower-diagnostics-20200115-1421.zip