Hello All,

I'm have an issue getting unraid to start.  It seemed to start when I tried to refresh a docker.  It now won't let me start any dockers.    My shares and VM's are ok but all my dockers won't start.  Here is a paste from my log...  I was have network issues as well and suspect my nic teaming has contriubuted to this so I have disabled it.   My UNRAID is 192.168.0.241.

 

Any help would be appreciated.    Thanks

 

 

an 29 15:44:48 Tower kernel: do_IRQ+0x46/0xd0
Jan 29 15:44:48 Tower kernel: common_interrupt+0xf/0xf
Jan 29 15:44:48 Tower kernel: </IRQ>
Jan 29 15:44:48 Tower kernel: RIP: 0010:vmx_handle_external_intr+0x6c/0x6d [kvm_intel]
Jan 29 15:44:48 Tower kernel: Code: 0f b7 50 06 8b 48 08 0f b7 00 48 c1 e2 10 48 c1 e1 20 48 09 ca 48 09 d0 48 89 e2 48 83 e4 f0 6a 18 52 9c 6a 10 e8 34 c4 6a e1 <c3> 48 8d 97 80 5a 00 00 f0 80 a7 a0 5a 00 00 fe b9 08 00 00 00 31
Jan 29 15:44:48 Tower kernel: RSP: 0018:ffffc90003883d48 EFLAGS: 00000082 ORIG_RAX: ffffffffffffffde
Jan 29 15:44:48 Tower kernel: RAX: ffffffff81800228 RBX: 0000000000000000 RCX: ffffffff00000000
Jan 29 15:44:48 Tower kernel: RDX: ffffc90003883d48 RSI: 0000000000000000 RDI: ffff88849db50000
Jan 29 15:44:48 Tower kernel: RBP: ffff88849db50000 R08: ffffff169d05eb02 R09: 0000000000000000
Jan 29 15:44:48 Tower kernel: R10: 0000000000000000 R11: 0000000000000000 R12: 0000000000000000
Jan 29 15:44:48 Tower kernel: R13: ffffc900038da5e0 R14: 0000000000000000 R15: 0000000000000000
Jan 29 15:44:48 Tower kernel: ? irq_entries_start+0x8/0x660
Jan 29 15:44:48 Tower kernel: ? vmx_get_exit_info+0x55/0x55 [kvm_intel]
Jan 29 15:44:48 Tower kernel: ? kvm_arch_vcpu_ioctl_run+0x1059/0x1367 [kvm]
Jan 29 15:44:48 Tower kernel: ? kvm_send_userspace_msi+0x5d/0x77 [kvm]
Jan 29 15:44:48 Tower kernel: ? kvm_vcpu_ioctl+0x17b/0x4b1 [kvm]
Jan 29 15:44:48 Tower kernel: ? __seccomp_filter+0x39/0x1ed
Jan 29 15:44:48 Tower kernel: ? vfs_ioctl+0x19/0x26
Jan 29 15:44:48 Tower kernel: ? do_vfs_ioctl+0x533/0x55d
Jan 29 15:44:48 Tower kernel: ? ksys_ioctl+0x37/0x56
Jan 29 15:44:48 Tower kernel: ? __x64_sys_ioctl+0x11/0x14
Jan 29 15:44:48 Tower kernel: ? do_syscall_64+0x57/0xf2
Jan 29 15:44:48 Tower kernel: ? entry_SYSCALL_64_after_hwframe+0x44/0xa9
Jan 29 15:44:48 Tower kernel: handlers:
Jan 29 15:44:48 Tower kernel: [<0000000051508708>] usb_hcd_irq
Jan 29 15:44:48 Tower kernel: Disabling IRQ #16
Jan 29 15:45:17 Tower webGUI: Successful login user root from 192.168.0.227
Jan 29 15:45:51 Tower ntpd[1660]: kernel reports TIME_ERROR: 0x41: Clock Unsynchronized
Jan 29 15:46:07 Tower nginx: 2021/01/29 15:46:07 [error] 4979#4979: *1693 upstream timed out (110: Connection timed out) while reading response header from upstream, client: 127.0.0.1, server: , request: "POST /plugins/community.applications/include/exec.php HTTP/1.1", upstream: "fastcgi://unix:/var/run/php5-fpm.sock", host: "localhost", referrer: "http://localhost/Apps"
Jan 29 15:50:02 Tower nginx: 2021/01/29 15:50:02 [error] 4979#4979: *3304 upstream timed out (110: Connection timed out) while reading response header from upstream, client: 192.168.0.227, server: , request: "GET /plugins/dynamix.docker.manager/include/DockerContainers.php HTTP/1.1", upstream: "fastcgi://unix:/var/run/php5-fpm.sock", host: "192.168.0.241", referrer: "http://192.168.0.241/Docker"
Jan 29 15:51:00 Tower root: Fix Common Problems Version 2020.12.27
Jan 29 15:51:00 Tower root: Fix Common Problems: Error: Default docker appdata location is not a cache-only share ** Ignored
Jan 29 15:51:01 Tower root: Fix Common Problems: Error: Plugin fix.common.problems.plg is not up to date
Jan 29 15:51:02 Tower root: Fix Common Problems: Warning: Plugin unassigned.devices.plg is not up to date
Jan 29 15:51:02 Tower root: Fix Common Problems: Warning: Plugin unassigned.devices-plus.plg is not up to date

 

 

I just re-read what I wrote above and did not word it very well...  I mucked it up when I tried to delete a docker image and the install it.  I was getting an error saying it was already there and it was not showing in the GUI....  Hope that helps.

Reboot and please post the diagnostics: Tools -> Diagnostics after if still issues.