Ok..   I know this has nothing to do with it..  But since I paid for unraid, I've had it lock up and a few other things.  Anyway, Here  is what's going on now. 

 

I had unraid ether crash or lockup or something about 15 minutes after putting in the paid key. It stopped responding on the computer I was using. I then went to the main computer with a monitor and keyboard. I already had the gui running since I'm still making sure everything is transferring and everything like it should. On the screen (computer running unraid) it was still on username for login. I couldn't do anything. I waited a few minutes and tried again. Still nothing..  So I unplugged it. Yes I made sure no activity lights was going.

 

Once I started it up, everything was good except that the dockers wasn't there..  I went to restart the server again (using the restart button) and it starts then goes to a black screen and is still running..  Monitor cuts off, but fans etc still going.. 

 

I waited again, then unplugged it again..  I started it back up and it was running fine. All the dockers etc was running like it should have been. Then it stopped responding again..  

 

Now, it still doesn't shut down, and the dockers are gone (with the error Docker Service failed to start. ) So now I'm stuck with just a broken OS..   Any Ideas on what I can do to repair this?  As I said in the beginning, it all started right after I put the paid key in. Before that It was running smoothly..  

 

Also, I'm running 6.4.0 

Please post your diagnostics: Tools -> Diagnostics

Sorry. I forgot to post this before...  I think the memory is bad..  I just had it come up with Call Traces Found.  I've had to restart it a few time since I posted this post..

whs-diagnostics-20180115-2137.zip

@johnnie.black

I have the same issue as @Meloccobut on top of that my VMs are no longer available after upgrading to 6.4 roughly 2hrs ago.

I noticed that my vdisk folder is no longer present & there has been no change after a reboot or power down & up.

 

unleyden-diagnostics-20180116-0251.zip

Edited January 16, 20188 yr by kleyden
remove quote box

@johnnie.black

I just noticed that my cache drive is not mounting after the 6.4 upgrade...which makes sense as to why my VMs are not available.

Any advice or questions would be appreciated.

Edited January 16, 20188 yr by kleyden
grammar correction

Sorry. I forgot to post this before...  I think the memory is bad..  I just had it come up with Call Traces Found.  I've had to restart it a few time since I posted this post..
whs-diagnostics-20180115-2137.zip

Is the docker still stopped since rebooting? It appears to be working on the diagnostics posted.

[mention=353]johnnie.black[/mention]
I just noticed that my cache drive is not mounting after the 6.4 upgrade...which makes sense as to why my VMs are not available.
Any advice or questions would be appreciated.

See here:

https://lime-technology.com/forums/topic/65494-unraid-os-version-640-stable-release-available/?do=findComment&comment=619388

It starts up some times and sometimes not..  It started up when I unplugged it and forced it to restart.  I tried to get a new dio. while it won't start but after 10 minutes of waiting, it never downloaded.. The dockers are also acting funny.. Krusader says it's running, but I have issues logging in. It sometimes starts to the main login screen, sometimes it doesn't start up at all, (see picture below). Plex does the same thing..  Sometimes it starts up, sometimes not.. It streams slow and transfers are very slow..  After thinking about it, I did upgrade the os a day before putting the key in..  Could I go back to 6.3.5? I backed up the flash card (wasn't sure the best way, so I just copied the flash card to a folder on my workstation). I don't know if that is the issue or not..  But I didn't have half the issues I'm having now...   Any Ideas?

Docker images shows write errors, these could be hardware related your not enough space on the device where the docker is:

 

Quote

Jan 15 21:35:22 WHS kernel: BTRFS info (device loop2): bdev /dev/loop2 errs: wr 675, rd 0, flush 0, corrupt 0, gen 0

 

It's also advisable to uninstall both the preclear and the S3 sleep plugin as they have known issues with v6.4

I had this happen to me today. It was a corrupt docker.img deleted it and recreated my templates and all is good.

Btrfs? That's the cache drive? I just took it out. I hope that fixes it. I noticed just before taking the cache drive out that it was full for some reason. Not sure why, before upgrading it only had 60gig in it.. But that's fine.. I'll see if that's the issue.. 

I've had to delete krusader and reinstall it a few times.. 

4 minutes ago, Melocco said:

Btrfs? That's the cache drive?

The docker image is always btrfs, but it can be stored on a xfs disk or cache device.

ok...  So what do I need to do? Do a parity check? All the drives show good and as far as preclear, if I take it out, how can I test the drive to see if there are any issues with it? I had heard that preclear kinda tests the drive by reading and writing multiple times..  Kinda a burn in..   Show I test the drive in windows instead?  Thanks for your help..  I really appreciate it.. 

10 minutes ago, Melocco said:

ok...  So what do I need to do?

 

2 hours ago, johnnie.black said:

It's also advisable to uninstall both the preclear and the S3 sleep plugin as they have known issues with v6.4

 

Also, check that the docker image is in a device with available space, and best to delete and recreate it to avoid any issues.

6 minutes ago, RichardU said:

Yikes. Just updated to 6.4. No VMs or Dockers. I fixed the VM problem by editing it and specifying the location. For dockers, I deleted docker.img removed preclear and rebooted. Still get: "Docker service failed to start."

 

Here's my diagnostics. Any help would be appreciated.

 

Richard

ubernet-diagnostics-20180116-1535.zip

 

I don't see any attempt on the log to start the docker service, since the image is currently on an UD device, can you test after creating a new image on your cache device?

Upgraded to 6.4. No dockers or VM. All I had to do was edit the VM file to re-enter the location. And change Settings / Dockers to re-enter the location.

 

Cheers,

 

Richard

 

Getting the same issue. Any help would be appreciated.

 

Here's my logs: 

unraid-diagnostics-20180119-1221.zip

Looks like the docker.img is corrupted.  Easiest to delete it and recreate it then re-add your apps via the apps tab, previous apps.

 

Other problems.  Disk 1 has a ton of read errors   Personally, I'd replace it with 32 reallocated sectors, and 8 more waiting currently to be reallocated.

 

I've replaced my cache drive and I'm still having issues. The kernel error is still happening. I am just having to unplug mine every day or so.

 

I'm just going to wait until the next update. I didn't have any issues until updating and putting in the full key.. 

 

I'm sure it's something crazy on my end, but I don't know what else to do.. 

On 1/19/2018 at 12:31 PM, Squid said:

Looks like the docker.img is corrupted.  Easiest to delete it and recreate it then re-add your apps via the apps tab, previous apps.

 

Other problems.  Disk 1 has a ton of read errors   Personally, I'd replace it with 32 reallocated sectors, and 8 more waiting currently to be reallocated.

 

Thank you, that helped fix some of the issues (delete docker.img) and rebuild.

 

The only issue I'm having is my letsencrypt image is not working anymore. Does this have something to do with the new reverse proxy setup?

 

Here's my log for when attempting to start the letsencrypt container. 

 

Jan 22 12:37:22 Unraid kernel: docker0: port 6(veth91dec58) entered blocking state
Jan 22 12:37:22 Unraid kernel: docker0: port 6(veth91dec58) entered disabled state
Jan 22 12:37:22 Unraid kernel: device veth91dec58 entered promiscuous mode
Jan 22 12:37:22 Unraid kernel: IPv6: ADDRCONF(NETDEV_UP): veth91dec58: link is not ready
Jan 22 12:37:22 Unraid kernel: docker0: port 6(veth91dec58) entered blocking state
Jan 22 12:37:22 Unraid kernel: docker0: port 6(veth91dec58) entered forwarding state
Jan 22 12:37:22 Unraid kernel: docker0: port 6(veth91dec58) entered disabled state
Jan 22 12:37:22 Unraid kernel: docker0: port 6(veth91dec58) entered disabled state
Jan 22 12:37:22 Unraid kernel: device veth91dec58 left promiscuous mode
Jan 22 12:37:22 Unraid kernel: docker0: port 6(veth91dec58) entered disabled state
Jan 22 12:37:29 Unraid kernel: kvm: disabled by bios

 

Probably because you're reusing the ports which unRaid now uses if SSL is enabled.  Check the 6.4.0 thread / let's encrypt thread

aliens-diagnostics-20180321-1553.zipaliens-diagnostics-20180321-1553.zipaliens-diagnostics-20180321-1553.zipI had some random issues with docker last night, where it would not start any container , today I upgraded to 6.5 and I have same message as all of you "Docker Service Fail to Start"

 

My Disk all look good 

 

Here is diagnostic file 

 

Any help appreciated 

aliens-diagnostics-20180321-1553.zip

syslog.txt

Edited March 21, 20188 yr by cableshark

Ok

 

My issue got resolved,   by increasing Docker Virtual disk image size from 20 to 30GB

 

Settings "Docker" ---   

"Enable Docker :  click no,

 

and Apply settings.

 

Then you will see docker "image size " by increasing docker image size from 20 to 30GB,  screen shot attached where you increase size 

 

Edited March 21, 20188 yr by cableshark

1 hour ago, cableshark said:

My issue got resolved,   by increasing Docker Virtual disk image size from 20 to 30GB

 

This is probably only temporary until it fills up again. 20GB would likely be plenty if you had things setup correctly.

 

You need to figure out why it is filling up. See "Docker Image Filling Up" in the Docker FAQ:

 

https://lime-technology.com/forums/topic/57181-real-docker-faq/