marshy919

Members
  • Content count

    36
  • Joined

  • Last visited

Community Reputation

0 Neutral

About marshy919

  • Rank
    Advanced Member
  1. Unsure what to do here. I have to access my Unifi Cloud Key controller. Located at: https://10.9.1.110:8443/ It just loads nothing, on anything coming from this Unraid server. Tried Linux, Win10, Mac VM. Just doesn't load. Other PC and phones etc work 100%. I moved house, nothing else has been done (besides changing the DNS settings to the new ISP address). Any input would be greatly appreciated, Thanks! Edit: All docker Local IP and Unraid Server IP are working from within. It's just everything that manages my network is impossible to connect to from this PC...
  2. Cache drive and downloading

    I use a Samsung 256gb 950 pro ssd for my downloaders to save into. So the actual docker is on my cache, but it all gets saved (temporarily) to a unassigned disk (so that it doesn't affect parity). I have it unpack as it downloads individual parts, so the CPU hit isn't as great. Works wonders for me Sent from my SM-G935F using Tapatalk
  3. unRAID OS version 6.4.0-rc9f available

    Nah didn't work. Tried different pc with different browser too. Sent from my SM-G935F using Tapatalk
  4. unRAID OS version 6.4.0-rc9f available

    The temp reading on my NVME card through PCIE is now correct, thankyou. I swapped to the "grey" UI theme today - works well so far. However, noticed that down the bottom left corner it says "Array Started•Starting services...:
  5. unRAID OS version 6.4.0-rc7a available

    Same issue as darksurf. Rebooting while server seemed to eliminate the problem for me though. Sent from my SM-G935F using Tapatalk
  6. VM crashing

    Wierd, restarted the PC and unraid wouldn't boot anymore. Just a blinking dash on a black screen. Had to reset BIOS, enable vt-d and set boot priority again to just get it to boot. Doing this, somehow fixed the above issue, at least for now. If it does it again ill post logs.
  7. VM crashing

    Only just started doing this today. Can work fine for a few hours, then just crash instantly. Has happened twice, the first time I just used Controlr to run the VM again. This time I tried Controlr, but it failed. I checked the Unraid UI, and it gave me an error restarting the VM. internal error: qemu unexpectedly closed the monitor: 2017-08-26T09:28:36.485755Z qemu-system-x86_64: -chardev pty,id=charserial0: char device redirected to /dev/pts/0 (label charserial0)
  8. Wiped all data?

    Oh thanks, I thought I did something wrong. So I can just re-add the parity drive?
  9. Wiped all data?

    Feeeew, all the data is there still. I just needed to not mount the parity drive. Now I can see all the disk usage, etc etc. Can someone please explain what to do from here? I don't want to break anything! I just need to add back my parity drive and sync that. Add an unassigned device to an SSD.
  10. Wiped all data?

    So this is surely my fault... A couple things happened. I had a new SSD to install, and I was going to do so as an unassigned device (for temp download location). While I was at it, I saw an error on drive 22. I've never used this slot, although I think I may have mounted my existing cache drive there once when first building the server. Anyway, the error was something like "disk missing, files are emulated" - along those lines. So I googled that error, and came across something showing that you can fix this by tools > new config. A quick read of that showed what to do (i think)... I selected to keep my cache and parity drives (cause they are correct with no errors atm). I then see that all my data drives are unassigned. I select all the data drives to be selected again. So currently the parity drive, cache and data drives are all selected. When I started the array, it done a parity check but showed all my data drives as unmountable (I'd need to format them again). I cancelled the parity check after about 30 seconds, checked my drives with Krusader and it was saying they are empty. I then stopped the array and started to panic. Clearly I've done something wrong, unsure what exactly... How do I go about getting this data back? Fortunately I had nothing super important, just media, but a fair bit of it... Thanks
  11. Look up cpu pinning. Any decent thread will explain it all in detail. Sent from my SM-G955F using Tapatalk
  12. RC7 & Ryzen 1600: Arch Linux with EFI boot

    Post your vm xml Sent from my SM-G955F using Tapatalk
  13. Can't boot OS in VM

    Yeah installing with seabios was the only way for me too. Could you maybe add this info to the vm create page or have the template automatically choose seabios when making an Ubuntu/debian etc build? Sent from my SM-G955F using Tapatalk
  14. Plugin list takes a long time to load

    I've had the same issue recently. Loading plugin page was definitely faster on previous rc. I noticed that clicking off plugins to docker, and then back to it made it load faster. Same exact issue with calculating disk usage for shares. Sent from my SM-G955F using Tapatalk
  15. append isolcpus rc7 issues

    Hmm, I think I understand what you are saying. You mean because cAdvisor isn't limited to any cores that's why it is showing the above? Because I have extra parameters for cAdvisor. --cpuset-cpus=0,6 It used to look like this: This is my Krusader docker viewed through cAdvisor. Allowed Cores 0 1 2 3 4 5 6 7 8 9 10 11 Thanks for those commands. cat /sys/devices/system/cpu/isolated = 1-5, 7-11. Perfect cat /proc/$$/status|tail -6 = cpu_allowed_list is 0,6 So it looks like it is working... The reason I isolate CPU is I try to game on my VM. When you get 15 second lockups every minute due to a docker unpacking a 5GB file, its very annoying. Only when nothing is happening at all my DPC latency is okay (500ish), but even the parity check absolutely kills it now. Without changing anything, any activity on the server absolutely kills my VMs DPC latency The driver that is killing it now is wdf1000.sys. Essentially I had previously used cores 0,6 to run all of my unraid server and dockers. Core 3 for emulatorpin. Every other core for VMs (and it worked...) Without changing any of this, DPC latency is through the roof and now cAdvisor is showing that is isn't working. But commands in putty are?
Copyright © 2005-2017 Lime Technology, Inc. unRAID® is a registered trademark of Lime Technology, Inc.