nia

Hi. I recently swapped my laptop mSATA, so I took the old one, put it into a SATA adapter and added is as a cache drive. In the same operation, I moved the Docker file to the cache, and have the working directory ".appdata" there as well. Now I have hust realised, that the cache drive is displaying as "Unmountable" in the UI. Looking in the logs, it says "shfs/user: cache disk full". I don't know if the two are related, but I suspect they are. If I look at the Docker, it still works. If I browse from Windows to \\tower\cache I can see approx. 40GB data (of the 80), but it reports 80GB occupied - can't see the rest of the data. I don't understand that it reports unmountable, but can still be browsed to. I also don't understand how the docker can continue working if the cache is unmountable I'm probably missing the plot and how the cache is working, so my question is: How did this happen? What do I do now? How do I prevent it from happening again? Logs and selected screendumps attached (had to separate syslog1 out due to size constraints). tower-diagnostics-20160411-1801-after-stop-start.zip

For me, the issue disappeared - I think with 6.1.7 - maybe earlier . I can at least confirm that 6.1.7 does not have the issue here.

Just wanted to say [glow=red,2,300]THANK YOU![/glow] for this docker I have had a full ESXi Virtual Windows installation reserved only for uTorrent and the VPN client plus virus/malware scanners etc. - a quite heavy setup, sluggish and a lot of waiting time every time it was started. This one is Soooooo much easier, lighter and so far appears to just work. Brilliant stuff. Quick question: Is this guaranteed to only be active through the VPN - i.e. if the VPN connection drops or signon fails, then nothing is sent/received?

Yes - I removed and reinstalled, and all is good now. Just had to redo configuration of what to backup. Thanks.

Any suggestions how I get it running properly again? More documentation needed?

Black screen in the UI. Hi. I played around with an early version of the docker - left it for some months, and now I have installed the newest version. I got it working fine first time. Then after a day or two, my server got completely unresponsive. I can't say it's this Dockers fault, but the server is normally otherwise stable. Now - after a hard reset, parity check and a few restarts, I'm trying to get the docker started again. I can start it, but when I go to the WebUI, either directly from the docker icon or from a VNC-client, there is just a black box and a mouse cursor. How do I get the UI back? Log attached. Clipboard_Text.txt

Hi Squid. Thanks a lot - just seemed like a really high number at first glance. I'll stop worrying

Hi. I was looking at the bottom-left part of the dashboard page at: Dashboard/System Status/{Errors}/Network/eth0/Drops (Recieve) When choosing "Errors", I see under eth0 - Receive: Drops: 562039. All other numbers are at 0. What does it mean, and should I be concerned? Version 6.1.6 running 58 days. Diagnostics attached. tower-diagnostics-20160221-1601.zip

Or rather have whatever is running unRAID in the Office/near where gaming would happen. In my case my nice multipurpose (currently headless) server big(!) box hums away in the corner of the family shared office; which is also why apart from power consumption, noise and heat is also important..

I would be very interested in an analysis like mentioned below. Having prices here in Denmark of 1kWh @ 0.22£ or 0.34$ power consumption in a 24/365 scenario is most certainly a very important parameter. I have been on the fence with this for a while, postponing the replacement of Juniors rig (standing right next to the unRAID server) with either a new mobo/GPU or a virtual setup while pondering considerations like these. And as the server is standing right here in our home office, noise and heat is important too. So I will stay tuned for any analysis - particularly on power consumption - as a "wrong" decision could very well end up becoming quite expensive (almost doubling NAS's numbers could very quickly make the case for a separate power-off-able rig).

Thank you from me as well. Have just upgraded to 6.0.1, and by finding this it was a breeze to setup the backup :-)

@JimPhreak: No - sorry for being incorrect in stating "passthrough of the port" rather than "adding" - my mistake. @smdion: As my Supermicro board only has the one controller (as I understand/remember it), I would have nowhere to boot ESXi from if I passed the controller through, leaving me with no USB ports left... So I will have to wait for the issue to be hopefully solved soon. At least things appear to work regardless of the logging.

Not sure what you need apart from the previous screenshot. Tell me a bit more in detail how to find what you need, and I'll be happy to help!

Oh yes - look down to #81 in this topic

I passthrough the port, not the controller - see my config attached.

I used to do that as well, but just upgraded both ESXi (from 5.5) and unRAID(from 5.0.4), and while I was at it thought I would just test the improved plop: PlopKexec. It is MUCH faster at booting! I just timed it (see my config in signature): Power on until finished reading kernel and starting "running text": 30 secs Power on until login prompt: 1 minute flat! So now I just boot using the plopKexec ISO never looking back again to the vmdk-method.

I have just upgraded, and unfortunately I also get these warnings Jul 19 17:16:14 Tower kernel: usb 1-1: reset high-speed USB device number 2 using ehci-pci Jul 19 17:16:14 Tower kernel: sd 4:0:0:0: [sdn] 3987456 512-byte logical blocks: (2.04 GB/1.90 GiB) Jul 19 17:16:59 Tower kernel: usb 1-1: reset high-speed USB device number 2 using ehci-pci Jul 19 17:16:59 Tower kernel: sd 4:0:0:0: [sdn] 3987456 512-byte logical blocks: (2.04 GB/1.90 GiB) Jul 19 17:17:40 Tower kernel: usb 1-1: reset high-speed USB device number 2 using ehci-pci Jul 19 17:17:40 Tower kernel: sd 4:0:0:0: [sdn] 3987456 512-byte logical blocks: (2.04 GB/1.90 GiB) My USB key is a Kingston DataTraveler 2.0 2GB

Quite a few of us in here are already using ESXi. How will this be different/better? Should we migrate, and will the options for Virtual machines, and the ease of managing be similar?

[glow=red,2,300]BINGO!!![/glow] That's the solution. It was there with root access configured. I removed it, and immediately had access. Thank You for pointing me in this direction. I'll close this thread with the solution. For reference - here are my responses to the other questions: It's fixed, and the same as it has always been. I'm also able to access the server from all my PC's. I am also able to access the Samba file shares from the PC that is failing through the IP address - just not using the server name. Nope. Not previously - but now I have - no change unfortunately. Yes. Yes. It lists the shares I used to have to \\tower as well as my 'emergency' shares that is addressing the server directly on IP \\192.168.1.99

Thanks for the reply. As already stated, I have rebooted (by now countless times). In combinations of many of the options below, including with completely disabled network cards and disabled services on all netcards. Also with other windows machines on the network turned off. No luck.

Hi. Sorry for another \\TOWER not found thread I have searched and tried most of the things I have found. I have just upgraded to 5.0.4 from 5.12beta (yes - that old). After this, I have the following problem. I can see \\tower from all but my own PC - including all shares. On my own PC, I can See the web interface through http://tower/Main See tower through ping See file shares through direct IP-addressing \\192.168.1.99 But I keep on not being able to access \\tower through Explorer or Directory Opus. I have added tower to hosts-file on my PC flushed DNS-cache deleted ARP-cache disabled all services on network cards on my machine changed workgroup for my machine and for the unRAID server renamed the unRAID server away from tower - in this case, I can get to the Samba share through the new name disabled Sabma services (and reenabled) confirmed that Tower is master browser (also seen from my PC) probably a few other things that I don't even remember All of the above with appropriate reboots underway and many in combinations One thing I haven't been able to figure out is a hint from somewhere on the net, that the cache on the samba server (unRAID) could be the culprit. In relation to that a wins.dat file is mentioned (I don't find it on my unRAID server). How would I go about clearing unRAIDs cache? I believe it's in the var/cache/samba folder, but what can I delete - and when? Any suggestions to how I get my ability to address the samba shares through \\tower again? Logfile attached if anyone can use that for diagnostics. Setup is in signature. syslog-NiA.zip

Beire - are you on ESXi 5.0, 5.1 or 5.5? I'm on 5.0.0 kernel build 469512.

Thanks. After one more reboot, I have managed to stay in touch with the server for more than 2-3 minutes - I left the computer and Client connected overnight, and it's still there. Right now I don't want toi touch ANYTHING until after Christmas eve - so I don't know if I'm just lucky, or the issue indeed has disappeared. I'll post back with my findings.

Thanks for the tip - sadly it didn't work. Anyone else?

I just upgraded my bios from version 1 to 2.0b, and I also got weird characters in the name - changing every time ESXi boots. I lose connection from vSphere Client after a few minutes every time I try to restart. And the address where it is disappears from the network, and can't even be ping'ed. So - I really can't do much. Sometimes I get a VM started, and it will keep running, but I can not at all administer the VM :-< I'm really in deep water here, so I hope someone can help/advise?