steve1977

Thanks again @gridrunner for the video and all the other helpful Unraid videos. I gave it another try with the very latest clover file and now all appears to work for me. Fingers crossed this stays stable for me. One Q - is it helpful and even possible to update Clover to later versions over the next weeks and months. Would I need an USB image again or could do this right out of the VM? Right now, my VM starts a xmas Clover screen upon bootup.

Unfortunately the disk failed again, while building new parity. Log attached. Any indication? Pointing to a cable issue again? tower-diagnostics-20180105-0135.zip

Unfortunately, my brand new parity disk (WD 10TB) keeps failing on me. I tried to run an extended SMART and believe that it completed without errors. I am not sure though as there may have been restarts or I may just reading things wrong. May I ask if someone skilled can have a look at my diagnostic log to see whether the extended SMART actually ran and completed? And whether anything suspicious in the log file why the disk failed? Thanks for your help! tower-diagnostics-20180104-0121.zip

Thanks, very clear. I posted in a separate thread regarding core allocations. Coming back to my other question: anyone else experiencing the issue that LE VM "freezes" frequently. I can still open the VM GUI, but can no longer move between the menus. It shows the Kodi GUI, but that's it and no action possible.

Is this just an issue for those with pass-through GPU or is the standard install broken now?

can someone confirm it’s still working? it somehow does not for me. i cannot log in and it shows password wrong (though it clearly isn’t). thoughts?

Thanks. So, my mistake may have been either (2) or (4). I had changed the default config folder from /mnt/cache/bla/bla to /mnt/cache/bla/bla/config. So, let me not do this and I'll wait after setting it up and watch the log. Only once I see "done" in the log, I will change the IP. Wish me luck :-)

Thanks for your reply and great to see this is still working. So, it must be me doing something wrong. Let me ask my questions one by one, so it will be easier for trouble-shooting: 1) Do I need to map the /import folder? The screenshot in the second post indicates that there is the need, but this is not mentioned elsewhere. 2) Do I need to map config to a dedicated config folder as shown in the screenshot of the second post (i.e., /mnt/cache/mbz/config). The default mapping in the docker template doesn't do it, so I would change this? 3) When doing a fresh install, do I still need to remove the content from /config and /data as indicated in the 18/05/2017 edit? Or is this just for legacy users? 4) When is the point of "after initialization" defined when I am supposed to add the local IP? Is this right after the docker is installed and up and running? Or is this after downloading the image (i.e., many hours later)? Once I hear back, I'll go ahead with another try and follow clearly the logic above. I will then post back any error message I may still have. Thanks!

Great to see this sticky and would love to get advice how to set up the right CPU and Ram assignment. My System: Cpu: Intel i7 7800X: 6C/12T @ 3.5ghz Motherboard: Asus Prime X299-A Ram: 32GB DDR 3 Graphiccards: GTX1050 (host), GTX1050 (VM1) I'd like to run: 1) Unraid with dockers (sabnzbd, radarr, sonarr), no transcoding/Plex 2) VM1: Win10 for gaming 3) VM2: MacOS for Photos 4) VM3: LE Kodi 5) Optional: VM4: Win10 for either gaming or general use (TBD) Would love to seek advice how to assign CPU and Ram. Currently, I have it set up as follows: Unraid: no assignment (not used 0/6, 12GB) VM1: 4/10, 5/11, 8GB VM2: 2/8, 3/9, 8GB VM3: 1/7, 4GB No VM4 setup yet I am wondering whether my VM1 would perform better if I were to assign an additional core to it? Also curious whether I can set VM3 set up more efficiently and whether helpful to assign additional ram to any of the VMs? If I were to set up VM4 as additional gaming VM (or all-purpose VM), how would I need to change my config? Thanks in advance and happy new year!

Thanks for your immediate reply. I wasn't aware. I don't need to assign any core to VMs? I.e., not ticking any box when setting up the docker? I also do have one gaming VM. I noticed very visible performance differences when assigning 1, 2 or 4 cores. Would not assigning any core make things more flexible and actually better than assigning just 2 cores (i.e., using maximum number of cores if available)? Let me focus on LE VM (without passthrough) then instead of docker, which indeeed may be easier for me. Fingers crossed the LE VM image for Unraid will eventually see some update. It feels abundant now.

I am hesitating between trying to get the docker or the LE VM to work. Is @Squid's recommendation still unchanged to go with a VM? My issue with the VM is that it has not been seeing recent update for the LE headless image and that it freezes when running for some time. While I don't mind the RAM overhead, I do mind that I need to assign a CPU core. Curious why you didn't mention this?

Not sure this counts as getting it to run Can anyone confirm that this still works as of now with a fresh install? Maybe it just works for those who have set it up a few months ago, but something got changed within MBZ? I am trying for a month now, but fail to set it up. I tried all kind of settings left and right, but there appears to be some issue or I am still doing something wrong.

Any thoughts on above? This seems to be a bug in Unraid?

Thanks @EdgarWallace. This is indeed very clear and I should be able to build the docker from the screenshot above. Big thanks! Shouldn't it be possible to update Minimserver from within the docker? Will this break things?

Thanks for sharing. For whatever reasons, Simon didn't appreciate this solution and hinted it may stop working? Anyhow, I like it and may be a good solution for me as well. Can you share a bit more how you have done it. The four steps above read easy, but not clear to me where to do what. Thanks!

I would still love to see this working. Tried many times, but somehow don't get this to work. Can someone help me with a step by step what I'd need to do here. There are some work-arounds mentioned (deleting folders, adding IP, etc.) that are not clear to me when I need to do it. Also, not fully clear whether I still need to map the import folder and how exactly to map the config folder (as default in docker template or change?). Thanks for your help and merry xmas :-)

Has there been any update? Would love to run MiniM in a docker. Thanks!

This is a weird issue. My Win10 Pro VM is up and running well (OVMF). Somehow, the time is always off and it shows different times. Even if I change it back, it will eventually go back to the wrong time. Anyone else experiencing this and any idea?

hDig some more digging and it may not be easily possible. There is a "dirty fix" described here, but this will require me to always execute a bat file when ending the RDC session. https://www.tenforums.com/network-sharing/16159-disable-login-screen-after-remote-desktop-session.html And below basically says it is not possible with Windows, but potentially with a server version of it? https://social.msdn.microsoft.com/Forums/en-US/64735fb1-b438-4d97-a501-f64fcf7c5af0/login-again-after-remote-desktop-session?forum=embeddedwindowscomponents Any more creative or new ideas how to tackle this?

I have a Windows 10 Pro VM, which I access using RDC from notebooks at home. When I close RDC, the screen logs. This prevents me from using Gamestream. I cannot use Gamestream with RDC active and I also cannot use it after closing RDC. Any idea how I can prevent RDC to log the screen? Windows is set up to automatically log on at startup. Things work well with Teamviewer as Gamestream allows me to use Gamestream, while Teamviewer is active. However, I dislike Teamviewer and it has problems with my GPU drivers. Even if this could be fixed, it feels a lot slower compared to RDC. Any idea what could be done?

Any other idea how to solve this issue? I have a permanently mapped VHDX and frequently reboot my Windows VM. I hope there is some more convenient way to fix this?

I succeeded to get this working with VHDX. However, I am facing quite a severe issue. I have set up a script to mount the VHDX upon startup. Unfortunately, this requires me to remember to unmount the VHDX before restarting my Windows VM. Otherwise, the VHDX cannot be started again. I found another thread with another community member facing the same issue: Any thoughts?

Thanks for your note. I keep on having these issues related to "cabling" since starting to use Unraid some years back. I could consider changing the PSU or buy an UPS if you think that this may be a potential source of the issue? If so, any suggestions on an UPS? I have a 850W Corsair PSU, so would need to be able to support this.

Thanks. Let me do this. I did the quick SMART before, which showed no errors. I didn't succeed the extended one to complete, but this may be a cabling issue. Let me give it another try and report back.

Unfortunately, my parity disk disabled. Tried to rebuild, but yet again disabled. Any thoughts from the log whether this is a disk or cable issue. The disk is just a few weeks old, so hope that this is not already a warranty case. Log attached. Thanks for your help! tower-diagnostics-20171219-2200.zip