JonathanM

In the past, the docker engine required a certain filesystem with specific options. An image was a quick way to make sure the correct options were used, without requiring an entire drive to be formatted that way.

Total RAM?

I know you are kicking yourself hard enough already, but I do need to point out that using disk encryption can greatly complicate file system corruption issues because there is another layer that has to be perfect. I would NEVER recommend encrypting drives where you aren't keeping current separate backups, it's just too risky. Verify your backup strategy works by restoring random files and comparing them before you start using encryption. Honestly, I wouldn't recommend encryption unless you have a well laid out argument FOR encrypting.

Client / server based backups. If you install a proper backup software inside the VM, it can do valid backups without taking down the VM. I personally use UrBackup, there is a container for it in the app section of Unraid, but you can just as easily use the built in windows backup if you are using microsoft products, or acronis, or any number of proper backup softwares. Doing it this way instead of trying to do a live image snapshot ensures you will have a valid backup instead of a crash consistent one. If you restore a snapshot that was taken of a running VM, you risk the snapshot not containing a valid backup, because there is no way for the VM client to know that it needs to commit changes from RAM to disk. Snapshots of VM's are only a good backup if you are willing to properly shut down the VM before taking the snapshot, or have some other feature in the VM to allow a live snapshot to work 100% of the time. Much easier to not reinvent the wheel and use good backup software in the VM.

You do realize this will still limit your writes, since every write is updating the parity disk(s). Have you looked into turbo write?

Just keep in mind if you want to upsize the zfs pool I think it's a little more complicated than just adding a single disk, unlike the parity pool.

Depends on size of parity disk and speed of the rest of the drives / HBA involved. If it's truly urgent to get your main server back on line you probably need to just cancel that and wait until support gets back to you on the plus license. A 16TB parity drive build could take a day or more.

Welcome! Don't hesitate to speak up if you are having issues, we're generally game to troubleshoot right along with you!

@eliminatrix2,BTW, I'm not an employee, just a very long time user. Please try to be polite, escalating attitudes isn't going to get things moving faster, it generally makes people less willing to assist.

You can't do that. Once a drive has been blacklisted it's done. What you can do, is transfer the entire content of the config folder WITHOUT the licence key file from one drive to another. So... first things first. Make a backup of ALL the flash drives, taking notes on what went where. Take the stick that has the currently valid pro license, and put the entire contents and the config folder from your main server on it minus the license key file, making sure to put the current pro license file back on it.

One of the issues with this style of selling is the lack of concrete delivery dates. They hope they can just stall the shipments until the prices people paid become normal market prices because tech tends to get cheaper as newer higher capacity items come on the market. I see this as the best case scenario, where you do actually receive the products eventually, but by the time they ship, you could purchase them on the open market for cheaper. Worst case, they are outright frauds, and intend to close up shop shortly after shipping enough units to satisfy the influencers that were gullible enough to hype them. The kickstarter model has so little accountability, any money you send now before products are available for resale on the open market should be considered gifts to the campaign, and you just hope that they are good people that are honest enough to not skidaddle with millions of free dollars. This particular campaign has just the right mix of authenticity to bring in huge amounts of cash, I hope they really do have the knowledge and honesty to deliver, but it doesn't smell that way right now.

What version is listed on the "Next" branch? 6.12 isn't stable yet.

I wouldn't if it were me. Isolate the PSU, so the only thing connected is the power cord, that way if the PSU is faulty it can't hurt anything else.

That explains why you are getting a copy / delete. Not directly, but that could cause some strange behaviour if the downloads share is set to cache:yes Before you start changing things around I think you need to get a deeper understanding of user shares and how they interact with the disk paths. hard links cannot be valid across the two types of paths.

No, you don't. You've looked so many times you can't see the issue. Not making fun, I've been there, done that. Compare letter by letter if you need to.

Smart money would reserve judgement until there are actually products in the general public, reviewers posting success stories don't count.

Whether a copy / erase or a rename is used by a move action depends on how the application views the file systems. If it sees the two locations as being part of the same file system it will rename, if it thinks there are two different file systems it will copy / delete. From the *arr's viewpoint, do the two paths share a common root? Or is it two root folders, /downloads and /TV?

Multiple pools have been available for a while now. 6.12 adds the ability to use ZFS for those multiple pools. It's the single volume per drive parity based array that is being proposed to have multiple instances. That style of array will likely always be restricted to single file systems on each member drive, thus the multi drive reliant features of ZFS will never be able to be used in the traditional Unraid parity array.

Did you a. Try the board separate from the case, laying on the box it came in if you need to account for pcie card overhang? The antistatic bag it was packaged in is good as a base to be sure it doesn't get damaged. b. Map out all the case standoffs and be sure they don't touch anything on the bottom of the board? Also, disconnect all the case LED and switch leads, you don't really need them to run the board, briefly shorting the power switch header should be enough to start things. Remove the RAM as well, so it's just the PSU leads the CPU and CPU fan lead connected, and see if you at least get fan spin. Is there a power present LED on the motherboard? Does it light up when the PSU has mains voltage? The IPMI portion of the board should be active and working even without the CPU if it's like some of the server boards.

I don't use plex, but I think if you don't assign an external folder for transcoding, it happens inside the image.

To add to Frank's excellent answer, I'll give you an analog that works the same way. Take a RAID1 volume with 2 members. Delete a file from the RAID1 set. The file gets removed from both members at the same time, to keep them in sync. Parity is the same concept, just expanded to cover all the parity array members. If parity is in sync, any one (or two if you have dual parity) drives can be removed and the parity bits will fill in the blanks and allow you to work with them just like they still were there, and when you assign a physical disk back to the slot, it will rebuild that emulated disk back to the physical drive to keep parity in sync. Just like how you can seamlessly continue to work with a degraded 2 member RAID1 volume that is missing a disk, and when you add a disk back it gets synced back in to match what was done on the degraded volume.

Install windows in a VM on the macbook? If you know what you are doing, it's easier to do the moves directly with the unraid terminal, mc is really convenient. Just don't stray outside /mnt/user unless you know what you are doing.

Check your plex library settings to make sure none of them are set to delete after watching.

Hard to determine exactly what this means, so I'll just leave a warning here about modular power supplies. The physical pins often look identical, but the pin assignments can differ without warning. NEVER swap modular cables without using either a multimeter or some other form of validation to be sure the correct voltages are being sent to the drives. A mistake here will be VERY expensive to correct, the cheapest way out is buying all new drives and abandoning any data on the blown drives. The safest and best method for powering drives is using only the cables that are soldered to the PSU board. If the PSU doesn't have enough connectors, the next best thing is a 4 pin "molex" to dual SATA power adapter connected to each 4 pin connector available on the PSU. Use as many of the stock 4 pin "molex" style connectors as you can, they have the highest current rating. If you are in any way questioning what you are seeing when you are tracing things out, take good pictures and post them here. We can help decipher what you are seeing.

The PSU total capacity isn't always the issue, if you have too many drives on a single PSU power feed it can cause voltage sags. Splitters can amplify that problem because each slip fit connection limits the current by increasing the resistance of the cable. Make sure you use as many direct individual cables from the PSU as you can to power the drives. The shorter the better. If you still have that 5 bay cage, make sure to feed it with at least 2 different sets of cables from the PSU.