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.

Docker Service failed to start unraid,docker log shows "fatal error: fault,[signal SIGSEGV: segmentation violation code=0x80 addr=0x0 pc=0xbdb940]"

Featured Replies

Hi, guys

 

I need some help, my unraid 6.9.2 shutdown itself some day, and i didn't know why. then i start it again, but docker can't start, I tried delete and recreate docker.img as this post described 

  , but it didn't work

 

I tried start docker in cli 

 

/usr/local/sbin/mount_image '/mnt/cache/docker/docker.img' /var/lib/docker 30

/etc/rc.d/rc.docker start

 

it still can't start,  /var/log/docker.log shows

 

unexpected fault address 0x0
fatal error: fault
[signal SIGSEGV: segmentation violation code=0x80 addr=0x0 pc=0xbdb940]

goroutine 1 [running, locked to thread]:
runtime.throw(0x14fefa8, 0x5)
	/usr/local/go/src/runtime/panic.go:774 +0x74 fp=0xc0001efe98 sp=0xc0001efe68 pc=0x430df4
runtime.sigpanic()
	/usr/local/go/src/runtime/signal_unix.go:401 +0x3e2 fp=0xc0001efec8 sp=0xc0001efe98 pc=0x4469e2
github.com/containerd/containerd/vendor/google.golang.org/grpc/health.init.0()
	/tmp/tmp.nEFLvHBBrz/src/github.com/containerd/containerd/vendor/google.golang.org/grpc/health/client.go:51 fp=0xc0001efed0 sp=0xc0001efec8 pc=0xbdb940
runtime.doInit(0x2974f20)
	/usr/local/go/src/runtime/proc.go:5228 +0x8c fp=0xc0001eff00 sp=0xc0001efed0 pc=0x43ef9c
runtime.doInit(0x296c620)
	/usr/local/go/src/runtime/proc.go:5223 +0x59 fp=0xc0001eff30 sp=0xc0001eff00 pc=0x43ef69
runtime.doInit(0x297d560)
	/usr/local/go/src/runtime/proc.go:5223 +0x59 fp=0xc0001eff60 sp=0xc0001eff30 pc=0x43ef69
runtime.main()
	/usr/local/go/src/runtime/proc.go:190 +0x1ca fp=0xc0001effe0 sp=0xc0001eff60 pc=0x43275a
runtime.goexit()
	/usr/local/go/src/runtime/asm_amd64.s:1357 +0x1 fp=0xc0001effe8 sp=0xc0001effe0 pc=0x461251
time="2022-08-12T21:24:39.410437223+08:00" level=error msg="containerd did not exit successfully" error="exit status 2" module=libcontainerd
failed to start containerd: timeout waiting for containerd to start

 

 

and when i disable and enable the docker, the syslog shows 

 

Aug 12 22:20:42 Tower ool www[15785]: /usr/local/emhttp/plugins/dynamix/scripts/emcmd 'cmdStatus=Apply'
Aug 12 22:20:42 Tower emhttpd: Starting services...
Aug 12 22:20:42 Tower emhttpd: shcmd (207413): /etc/rc.d/rc.samba restart
Aug 12 22:20:42 Tower nmbd[18185]: [2022/08/12 22:20:42.860892,  0] ../../source3/nmbd/nmbd.c:59(terminate)
Aug 12 22:20:42 Tower nmbd[18185]:   Got SIGTERM: going down...
Aug 12 22:20:42 Tower winbindd[18195]: [2022/08/12 22:20:42.861044,  0] ../../source3/winbindd/winbindd.c:244(winbindd_sig_term_handler)
Aug 12 22:20:42 Tower winbindd[18195]:   Got sig[15] terminate (is_parent=1)
Aug 12 22:20:42 Tower winbindd[18197]: [2022/08/12 22:20:42.862534,  0] ../../source3/winbindd/winbindd.c:244(winbindd_sig_term_handler)
Aug 12 22:20:42 Tower winbindd[18197]:   Got sig[15] terminate (is_parent=0)
Aug 12 22:20:42 Tower winbindd[18438]: [2022/08/12 22:20:42.862570,  0] ../../source3/winbindd/winbindd.c:244(winbindd_sig_term_handler)
Aug 12 22:20:42 Tower winbindd[18438]:   Got sig[15] terminate (is_parent=0)
Aug 12 22:20:45 Tower root: Starting Samba:  /usr/sbin/smbd -D
Aug 12 22:20:45 Tower root:                  /usr/sbin/nmbd -D
Aug 12 22:20:45 Tower smbd[16215]: [2022/08/12 22:20:45.041217,  0] ../../lib/util/become_daemon.c:135(daemon_ready)
Aug 12 22:20:45 Tower smbd[16215]:   daemon_ready: daemon 'smbd' finished starting up and ready to serve connections
Aug 12 22:20:45 Tower root:                  /usr/sbin/wsdd
Aug 12 22:20:45 Tower nmbd[16220]: [2022/08/12 22:20:45.052352,  0] ../../lib/util/become_daemon.c:135(daemon_ready)
Aug 12 22:20:45 Tower nmbd[16220]:   daemon_ready: daemon 'nmbd' finished starting up and ready to serve connections
Aug 12 22:20:45 Tower root:                  /usr/sbin/winbindd -D
Aug 12 22:20:45 Tower winbindd[16230]: [2022/08/12 22:20:45.096774,  0] ../../source3/winbindd/winbindd_cache.c:3203(initialize_winbindd_cache)
Aug 12 22:20:45 Tower winbindd[16230]:   initialize_winbindd_cache: clearing cache and re-creating with version number 2
Aug 12 22:20:45 Tower winbindd[16230]: [2022/08/12 22:20:45.097398,  0] ../../lib/util/become_daemon.c:135(daemon_ready)
Aug 12 22:20:45 Tower winbindd[16230]:   daemon_ready: daemon 'winbindd' finished starting up and ready to serve connections
Aug 12 22:20:59 Tower ool www[16330]: /usr/local/emhttp/plugins/dynamix/scripts/emcmd 'cmdStatus=Apply'
Aug 12 22:20:59 Tower emhttpd: Starting services...
Aug 12 22:20:59 Tower emhttpd: shcmd (207454): /etc/rc.d/rc.samba restart
Aug 12 22:20:59 Tower nmbd[16220]: [2022/08/12 22:20:59.546873,  0] ../../source3/nmbd/nmbd.c:59(terminate)
Aug 12 22:20:59 Tower nmbd[16220]:   Got SIGTERM: going down...
Aug 12 22:20:59 Tower winbindd[16230]: [2022/08/12 22:20:59.546960,  0] ../../source3/winbindd/winbindd.c:244(winbindd_sig_term_handler)
Aug 12 22:20:59 Tower winbindd[16230]:   Got sig[15] terminate (is_parent=1)
Aug 12 22:20:59 Tower winbindd[16232]: [2022/08/12 22:20:59.546960,  0] ../../source3/winbindd/winbindd.c:244(winbindd_sig_term_handler)
Aug 12 22:20:59 Tower winbindd[16232]:   Got sig[15] terminate (is_parent=0)
Aug 12 22:21:01 Tower root: Starting Samba:  /usr/sbin/smbd -D
Aug 12 22:21:01 Tower root:                  /usr/sbin/nmbd -D
Aug 12 22:21:01 Tower smbd[16497]: [2022/08/12 22:21:01.728061,  0] ../../lib/util/become_daemon.c:135(daemon_ready)
Aug 12 22:21:01 Tower smbd[16497]:   daemon_ready: daemon 'smbd' finished starting up and ready to serve connections
Aug 12 22:21:01 Tower root:                  /usr/sbin/wsdd
Aug 12 22:21:01 Tower nmbd[16502]: [2022/08/12 22:21:01.739477,  0] ../../lib/util/become_daemon.c:135(daemon_ready)
Aug 12 22:21:01 Tower nmbd[16502]:   daemon_ready: daemon 'nmbd' finished starting up and ready to serve connections
Aug 12 22:21:01 Tower root:                  /usr/sbin/winbindd -D
Aug 12 22:21:01 Tower winbindd[16512]: [2022/08/12 22:21:01.780989,  0] ../../source3/winbindd/winbindd_cache.c:3203(initialize_winbindd_cache)
Aug 12 22:21:01 Tower winbindd[16512]:   initialize_winbindd_cache: clearing cache and re-creating with version number 2
Aug 12 22:21:01 Tower winbindd[16512]: [2022/08/12 22:21:01.781599,  0] ../../lib/util/become_daemon.c:135(daemon_ready)
Aug 12 22:21:01 Tower winbindd[16512]:   daemon_ready: daemon 'winbindd' finished starting up and ready to serve connections
Aug 12 22:21:01 Tower emhttpd: shcmd (207468): /usr/local/sbin/mount_image '/mnt/cache/docker/docker.img' /var/lib/docker 30
Aug 12 22:21:01 Tower kernel: BTRFS info (device loop3): using free space tree
Aug 12 22:21:01 Tower kernel: BTRFS info (device loop3): has skinny extents
Aug 12 22:21:01 Tower kernel: BTRFS info (device loop3): enabling ssd optimizations
Aug 12 22:21:02 Tower root: Resize '/var/lib/docker' of 'max'
Aug 12 22:21:02 Tower emhttpd: shcmd (207470): /etc/rc.d/rc.docker start
Aug 12 22:21:02 Tower root: starting dockerd ...
Aug 12 22:21:31 Tower emhttpd: shcmd (207472): umount /var/lib/docker

 

and  the diagnostics file is here, :( 

 

 

tower-diagnostics-20220812-2228.zip

  • Community Expert

Does it work if you boot in SAFE mode?

Also, have you run a memtest from the boot menu?  (If you boot via UEFI mode, you will need to temporarily switch to Legacy in order to run the test)

It would also be worthwhile to upgrade to 6.10.3 (as there's numerous bug fixes), along with purchasing a legit key instead of running a cracked version which probably has issues / viruses / etc

  • Author
10 hours ago, trurl said:

Does it work if you boot in SAFE mode?

thanks, i'll try

  • Author
10 hours ago, Squid said:

Also, have you run a memtest from the boot menu?  (If you boot via UEFI mode, you will need to temporarily switch to Legacy in order to run the test)

Thanks , i'll try to run a memtest, it's boot in Legacy mode, not UEFI

  • Author
8 hours ago, Squid said:

It would also be worthwhile to upgrade to 6.10.3 (as there's numerous bug fixes), along with purchasing a legit key instead of running a cracked version which probably has issues / viruses / etc

yeah, i believe it

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

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.