JonathanM

Why? Do you want to ensure that they can't run simultaneously? I don't see a good reason to go through the extra hassle vs. just setting up 2 VM's.

I suspect the docker settings aren't actually the OP's issue. It sounds to me like the appdata got lost / corrupted in the handling of the 1TB/120GB SSD cache pool.

Direct quote from the link. "Plex does not support the use of ISO, IMG, Video_TS, BDMV, or other “disk image” formats. If you wish to use those with Plex, you should convert them to a compatible format." "adding a scanner" whatever that means, is not going to change the fact that plex can't use .iso

I'm fairly sure it will bail out and allow you to remove it. I can't remember where I saw that, and I haven't personally tested it. Fairly easy to test if you wanted to risk invalidating parity for the sake of demonstration. Add a not precleared drive in a hot swap bay, let the clear process start, turn off the power to that specific bay and see what happens.

Wait, what? So if you edit an existing script, it will be affected? I'm guessing what you are saying is that until you open and save an existing script, the update doesn't change anything. Would it break things if instead of silently stripping the offending characters, remap the characters in the display to some visible character? What I'm getting at is instead of silently fixing the issue, make it obvious where the characters are, like maybe blink the space? That way if the unprintable is in a spot where it will break the script, the user can just delete it, if it's intentional you can still use the web editor without stripping them?

BTW, I'm pretty sure unraid trial only requires internet to start the array. As long as you keep the array started you don't need internet.

Also, what was your intent with pairing up a 1TB SSD with a 120GB SSD in the cache pool? If you haven't manually adjusted things, that will end up with 120GB of useable space, basically ignoring the capacity of the 1TB, and a free space display in the GUI that is seriously wrong.

Exactly.

Correct. Your license is good indefinitely. You only get one automatic transfer to a different flash drive per year, but should you have an issue before the year is up, you can email limetech and they will take care of you. The license key file is tied to the physical drive, as long as you keep that key file, it's registered. Doesn't matter what you do to the rest of the files on the drive, format it, whatever, as long as you put the same key file back in the config folder, it's fine. That may not have been the best move long term, physically larger drives seem to last longer. It would have been better to get a cable to mount the USB inside the case and attach to the motherboard's IDC header. Something like this or similar. https://www.newegg.com/startech-usbmbadapt-usb-a-female-to-usb-motherboard-4-pin-header/p/N82E16812200294

Quick question. How feasible would it be to set up another machine at a different IP with read only access to that same 350TB?

Simple solution. User Scripts plugin, schedule this script to taste, once an hour or whatever. #!/bin/bash docker restart binhex-nzbget Symptoms solved, no interaction required. The root CAUSE is still there, but I haven't seen any bad effects running this.

The real fix is running the 2.0 docker with the 2.0 windows front end. See here for some help. *(disclaimer. I don't use the windows client, I use linux desktop machines. The following information is what I obtained with 2 minutes of googling and reading) https://forum.deluge-torrent.org/viewtopic.php?f=12&t=55404&start=20#p230175

Trials can't be migrated seamlessly, for obvious reasons. However... I don't think there is anything stopping you from recreating your config manually. I wouldn't try either step until after you update the BIOS and see what the results are.

Tools, new config

Yes, but I will always keep a hardware pfsense box ready to spin up when it's needed. It's so easy to back up and restore, and my server has so much more horsepower it seemed like a waste to keep the hardware pfsense spun up all the time. Virtualized pfsense for the win.

No personal experience, I haven't even played with it because what you observed seems to be typical. Bonding seems to be like hyperthreading, in that it makes no difference unless the application is specifically written to take advantage of it. The only benefit you will probably see is the ability to lose one of the links seamlessly. You could also try NFS to one of the clients, I bet both clients would get 1Gb/s if one was nfs and the other was smb. If you want higher speeds you will need to move to 10Gb.

Did you by any chance do a new config and add the extra array drives and check the box saying parity was already valid?

Can you tether a mobile device to a windows computer and share the connection? If so, you can plug the server's ethernet cable into the ethernet of the windows machine and connect.

I suspect system recovery is needed, however this varies by manufacturer. You should consult the computer manufacturer for advice. This is not a general computing support area.

To some people? A great deal. To me? Not really. To you? Apparently not, but why rain on somebody else's parade?

I think it may be a browser display synchronization thing. Try doing a page refresh after you shut down the VM and see if the status is properly updated.

Make a copy of the image, and use testdisk from https://www.cgsecurity.org/

If it increased the uptime in a predictable and repeatable way but didn't solve the issue, that would point to power supply. Not necessarily the PSU itself, there are power supply circuits on the motherboard to further smooth, condition, and regulate the power to the memory and CPU. So, if totally removing 1 cpu and associated RAM "fixes" it, swap to the unused set of CPU and RAM and see if it stays "fixed". If it does, that further implicates the power supply chain. You could have a marginal motherboard power supply that has degraded over time. I've had boards that originally ran 4 sticks of RAM just fine, but later developed instability with more than 2 sticks of perfectly good RAM.

Depends on the connectors used. The source isn't the issue, a standard 4 pin connection can handle the current just fine. It's the SATA end of the power adapter that can cause fires. https://www.crucial.com/usa/en/dangerous-molex-to-sata-cables That link does a poor job of demonstrating which types of adapters to avoid, suffice it to say that some adapters are much safer than others. Do your research.