October 13, 20187 yr My server (latest) was unresponsive today. Hard reset and it's back up, but docker page shows "Docker Service failed to start". I've restarted twice, sa.e result. What kind of diagnostician I look at to see why docker wont start. Looking at the syslog, I see this relative to the Docker load: Oct 12 23:23:52 HunterNAS emhttpd: Starting services... Oct 12 23:23:52 HunterNAS emhttpd: shcmd (127): /usr/local/sbin/mount_image '/mnt/cache/docker.img' /var/lib/docker 20 Oct 12 23:23:52 HunterNAS kernel: BTRFS: device fsid 46e4fe78-0324-4c24-9923-aa27b03dba05 devid 1 transid 81137 /dev/loop2 Oct 12 23:23:52 HunterNAS kernel: BTRFS info (device loop2): disk space caching is enabled Oct 12 23:23:52 HunterNAS kernel: BTRFS info (device loop2): has skinny extents Oct 12 23:23:52 HunterNAS kernel: BTRFS error (device loop2): bad tree block start 0 458047488 Oct 12 23:23:52 HunterNAS kernel: BTRFS error (device loop2): bad tree block start 0 458047488 Oct 12 23:23:52 HunterNAS kernel: BTRFS warning (device loop2): failed to read tree root Oct 12 23:23:52 HunterNAS root: mount: /var/lib/docker: wrong fs type, bad option, bad superblock on /dev/loop2, missing codepage or helper program, or other error. Oct 12 23:23:52 HunterNAS kernel: BTRFS error (device loop2): open_ctree failed Oct 12 23:23:52 HunterNAS root: mount error But I don't see any disk errors on the Cache drive. The appdata share is live and I can access files. The log file directory on the cache drive is empty. Not sure where the docker log file is stored? Diagnostics attached - thanks in advance! hunternas-diagnostics-20181012-2329.zip Edited October 13, 20187 yr by jeffreywhunter
October 16, 20187 yr Author On 10/13/2018 at 1:31 AM, johnnie.black said: Delete and recreate docker image. I did the following 1. Settings - Docker - Advanced View - Enable Docker: No - Delete The Image File Check Box - Apply - Enable The Service - Apply Then I went to do this: 2. Apps Tab, Previous Apps Section - Check off all your previously installed apps and install them via the button. However, its missing the Plex Media Server App? And when I went to the docker page, I'm again, seeing the "Docker Service failed to start." error. Thanks in advance...
October 17, 20187 yr Author 5 hours ago, johnnie.black said: Please post new diags. Apologies, should have included... hunternas-diagnostics-20181017-0701.zip
October 17, 20187 yr Community Expert Sylog is filled with these: Oct 17 07:01:43 HunterNAS emhttpd: error: put_config_idx, 609: Invalid argument (22): fopen: /boot/config/shares/home\ movies.cfg Oct 17 07:01:43 HunterNAS emhttpd: Starting services... Oct 17 07:01:44 HunterNAS emhttpd: error: put_config_idx, 609: Invalid argument (22): fopen: /boot/config/shares/home\ movies.cfg Oct 17 07:01:44 HunterNAS emhttpd: Starting services... Oct 17 07:01:45 HunterNAS emhttpd: error: put_config_idx, 609: Invalid argument (22): fopen: /boot/config/shares/home\ movies.cfg Oct 17 07:01:45 HunterNAS emhttpd: Starting services... Which I don't know what it means, possibly an issue with the flash drive or the movies share settings, you can try deleting movies.cfg and recreate the config.
October 19, 20187 yr Author On 10/17/2018 at 8:58 AM, johnnie.black said: Sylog is filled with these: Oct 17 07:01:43 HunterNAS emhttpd: error: put_config_idx, 609: Invalid argument (22): fopen: /boot/config/shares/home\ movies.cfg Oct 17 07:01:43 HunterNAS emhttpd: Starting services... Oct 17 07:01:44 HunterNAS emhttpd: error: put_config_idx, 609: Invalid argument (22): fopen: /boot/config/shares/home\ movies.cfg Oct 17 07:01:44 HunterNAS emhttpd: Starting services... Oct 17 07:01:45 HunterNAS emhttpd: error: put_config_idx, 609: Invalid argument (22): fopen: /boot/config/shares/home\ movies.cfg Oct 17 07:01:45 HunterNAS emhttpd: Starting services... Which I don't know what it means, possibly an issue with the flash drive or the movies share settings, you can try deleting movies.cfg and recreate the config. I've never actually deleted a share I wanted to keep. This the proper approach? 1. Document the disks connected to the share. 2. Uncheck the disks from the share. 3. Delete the share. 4. Check the appropriate disks. Try to recreate the docker?
October 20, 20187 yr Community Expert I didn't say to delete the share, delete the share cfg file on your flashdrive, or rename it, for example to "home movies.bak", Unraid will recreate the cfg at array start, though with default settings, so you might want to look at the current settings before deleting to change them back if needed.
October 20, 20187 yr Author 8 hours ago, johnnie.black said: I didn't say to delete the share, delete the share cfg file on your flashdrive, or rename it, for example to "home movies.bak", Unraid will recreate the cfg at array start, though with default settings, so you might want to look at the current settings before deleting to change them back if needed. Interesting. If the array is online, its recreates the movies.cfg file immediately. And it creates it blank (i.e. no settings). 14 hours ago, johnnie.black said: I didn't say to delete the share, delete the share cfg file on your flashdrive, or rename it, for example to "home movies.bak", Unraid will recreate the cfg at array start, though with default settings, so you might want to look at the current settings before deleting to change them back if needed. Turns out the problem was with a share I setup. Not sure how this started failing, as its been this way for over a year, but I had a share setup with /home movies. In the path it looks like \mnt\user\home/ movies. It appears that it was having problems using that path. Changed to /homemovies and \mnet\user\homemovies and its working fine.
Archived
This topic is now archived and is closed to further replies.