JonathanM

I'm guessing this is probably the issue. https://forums.unraid.net/topic/46802-faq-for-unraid-v6/?do=findComment&comment=819173 If not, you would be better to start your own thread instead of posting into someone else's already solved thread.

That made me cringe. The load you are putting on the bearings doing that could exceed what the drive is rated to handle. It's just not a good idea to move a running disk drive, it's pretty easy to induce errors. Paper towel cardboard tube makes a decent way to somewhat isolate what you are listening to.

Replace it. You could possibly rearrange how the drives are getting power, as in make sure you are using all the leads possible directly from the PSU, eliminate as many splitters as you can.

AFAIK, privoxy is web only, so if you want to route torrent traffic through the vpn you will need to either follow the directions to send the whole container through by using the vpn container as the network for the torrent container, or set up the torrent client with its own vpn login. spaceinvader one has a video on youtube about sending one container through another for exactly what you are talking about.

Quote the section that you are having issues with.

https://wiki.unraid.net/Troubleshooting#Re-enable_the_drive

Formatting while the drive is outside the array won't do anything, whatever is being emulated by the rest of the disks will be written back to the drive when you put it back in.

When a drive fails, if parity is accurate at the point it drops, then the only indication will be the red x and the notifications. The data slot should still contain all the data as emulated by parity. Navigating to /mnt/diskX will still work, and all the files on the drive will be there and readable. The disk itself isn't being accessed, the data is being generated by all the other drives that are still working.

Sure, but it's a matter of manually moving the data off the emulated missing drive to another destination.

Yes. If you only have 1 parity drive, you can only have 1 missing drive. Any further failures will result in complete data loss from all missing data drives, including the first failure.

Parity will rebuild whatever is emulated in the missing disk slot onto a drive you put back in to the slot. If you rebuild parity without that slot, all data that was there will be gone.

So the drive was empty?

It's an arbitrary word. You could mount the host folders to a folder inside krusader called "rabbits" and when you looked in krusader your mapped content would be in the /rabbits folder.

Try the disk speed test and see how they look. https://lime-technology.com/forums/topic/70636-beta-diskspeed-hard-drive-benchmarking-unraid-6/

Perhaps setting up a VM with a linux server would work, you could attach a second vdisk to it and share that from the VM. I don't know of a way to directly accomplish what you are asking from the Unraid GUI.

Should work normally, as in how you typically reverse proxy sites, not how lsio makes it work. As long as you can successfully access the site through an IP and port, like http://192.168.1.5:8080, then you just plug that address in to your nginx config. If you CAN'T get to the site locally, then you will need to fix that first, typically by adding the appropriate port to the delugevpn container. I reverse proxy sites through swag from a VM, from a second Unraid server, and local containers, all with no issues. If none of this makes any sense, then you are going to need to take a crash course in how to configure nginx. It's not that hard, but there are differences in how lsio does things that make it so you need to know a little more about how it's working.

Did you verify that nomachine was working properly when the VM's were running with VNC?

Use nomachine instead. DP to HDMI converters are fairly cheap.

Make sure your boot USB is in a 2.0 port with a black insert.

Many USB adapters modify the addressing of drives. It's one of the reasons why USB is not recommended for array drives. It's generally ok for unassigned devices as long as you don't expect to use the drive directly with SATA interchangeably.

Can you attach the drive directly to a SATA connection and try again?

Are you sure the drive you are trying to access was one of the data drives? Do you have a list of the drives as they were in the array before?

There doesn't appear to be any attempt to attach the disk in question, and the array is stopped. Recreate the issue then collect the diagnostics and post them.

That's probably a little long of an interval. The consensus is once a month. A parity check with zero errors is the way to know with some certainty that a drive failure can be rebuilt accurately. If you aren't going to do parity checks more often, at least do long smart tests on all your drives, that way at least drive failures have a chance of being caught before multiples sneak up on you and preclude the possibility of rebuilding successfully.

Attach the diagnostics zip file to your next post.