pwn4fun

@wrotruck@joecool169@ra1k_0 You need to enable "Host access to custom networks". Settings - Docker - Enable Docker "NO" - "Apply" - click on advanced view - Host access to custom networks "Enabled" - "Apply" - Enable Docker "YES" - "Apply". This should solve the 502 bad gateway issue.

Tried using the console command. rm -r /mnt/user/DeleteMePlease/hydra2/logs/* To no avail, as this crashed the server. After that was... rm -r /mnt/user/DeleteMePlease/hydra2/* Also crashed the server. Finally rm -r /mnt/user/DeleteMePlease/* No idea why but the last one worked while all the others caused the system to hang. If anybody knows why I would love to learn why that would happen.

Solution (not ideal) but it worked for me. As I had no backup at the time and could not afford to lose any data. Remove 1 drive from the raid card and plug it into the motherboard. Rebuild array. Repeat steps 1-2 until all drives are plugged into the motherboard and the final rebuild is finished. Swap into new system with a raid card in JBOD mode.

For anybody else with this problem. Whitelist your server in any adblock software. Update to the latest stable release of unRAID. Make sure no containers or VMs are misbehaving and eating ram.

Hello Everyone, I have a slight problem with a folder that is locked. It is an old appdata folder for "hydra2". Long story short, I removed the docker and used "Cleanup Appdata" after the removal was finished. It seemed to be taking a very long time so I let it run for a while, (2 days). At this point it said it was finished but when browsing to the appdata folder it was still there. Everything inside the folder deleted except for the "logs" folder. Trying to delete this folder crashed file explorer on my Win 10 machine. Next I tried the "binhex-krusader" container that also crashed. Can not open the folder or delete it, as any system attempting it hangs almost immediately. Folder is located in its own share with nothing else in it. Size of folder is determined to be about 9.20 GB. Any help on how to delete would be appreciated.

Upgraded to version 6.6.6 and the problem persists. Unsure of the next steps to take.

Just upgraded server to new machine. The web GUI is very slow to load, and sometimes get a "504 gateway time-out (nginx)" error. Reset fixes it for a bit but always happens after a while. Any advice would be appreciated. unraid-diagnostics-20181205-0153.zip

Recently decided to upgrade server but have an issue with my current setup. Currently running each drive through a raid card without JBOD support. Not a problem (I thought) Ill just run each drive in a raid 0 by itself. Works but now that I'm looking to upgrade I realize what a mistake that was. Is there anyway to build a new machine and use the same drives without data loss?

What is the workaround?

Here is diagnostics. tower-diagnostics-20170320-2117.zip

All 4 things are are in order but still no luck. I have no clue why i am getting issues.

I am new to UnRAID and am receiving the following error message when trying to launch a VM with a dedicated GPU. internal error: process exited while connecting to monitor: 2017-03-20T02:22:24.702355Z qemu-system-x86_64: -device vfio-pci,host=0b:00.0,id=hostdev0,bus=pci.0,addr=0x5: vfio: failed to set iommu for container: Operation not permitted 2017-03-20T02:22:24.702398Z qemu-system-x86_64: -device vfio-pci,host=0b:00.0,id=hostdev0,bus=pci.0,addr=0x5: vfio: failed to setup container for group 20 2017-03-20T02:22:24.702405Z qemu-system-x86_64: -device vfio-pci,host=0b:00.0,id=hostdev0,bus=pci.0,addr=0x5: vfio: failed to get group 20 2017-03-20T02:22:24.702421Z qemu-system-x86_64: -device vfio-pci,host=0b:00.0,id=hostdev0,bus=pci.0,addr=0x5: Device initialization failed The VM boots fine with the VNC option checked. My system specs are as follows. Model: Custom M/B: - CPU: Intel® Xeon® CPU E5530 @ 2.40GHz HVM: Enabled IOMMU: Enabled Cache: 128 kB, 128 kB, 1024 kB, 1024 kB, 8192 kB, 8192 kB Memory: 18 GB (max. installable capacity 384 GB) Network: bond0: fault-tolerance (active-backup), mtu 1500 eth0: 1000 Mb/s, full duplex, mtu 1500 eth1: not connected eth2: not connected eth3: not connected Kernel: Linux 4.9.10-unRAID x86_64 OpenSSL: 1.0.2k