JonathanM

No. Each disk in the parity array is an independent filesystem, the user shares are a merged directory tree across same named root folders on all participating disks. Technically the answer to your thread title is yes, you can create vdisk's larger than the available space because they are created sparse, and only occupy the space actually written inside the image. However, as you found out, when the containing disk runs out of space, the vdisk doesn't have anywhere to put the data, so the virtual filesystem doesn't work correctly. Instead of using the parity array, you can assign multiple disks to a pool, which can use either BTRFS or ZFS RAID levels to create a single filesystem spanning multiple physical disks.

Most motherboards have 6 or more SATA ports, if you need more drives than that,

That will work fine.

If you have a different IP assigned to the container that's not host mode. A unique IP can open any and all ports without conflict. Host mode uses the Unraid main IP and can conflict with Unraid's native services. Bridge mode is more like giving the containers their own router and setting up port forwarding where needed.

If you are talking about changing the format of the drive when you switched them, you erased the data. Unraid's parity doesn't hold files, it emulates the whole drive, format included, so the only thing it can rebuild is the original format. When you reformatted, you told Unraid to put a new blank filesystem on the drive. Try attaching the old drive to Unraid and see if the Unassigned Devices plugin can mount it. If so, you should be able to copy the files back to the new drive. BTW, this is an old thread, I'd recommend starting a new one in the general support area.

It shows bridge mode allocations. Host mode containers open a whole can of worms, they have free reign to use whatever ports they want. Don't use host if you can at all help it. Do whatever it takes to figure out what ports are needed and use bridge mode.

Is fast boot disabled? Can you select the USB drive in the hard drive boot section? Some motherboards put the USB sticks in the hard drive list as well as the USB list.

As long as you can format it to FAT32 it should work. IIRC windows won't do FAT32 larger than 32G, but third party programs and non-brain dead OS's can as well. Use the manual install method, I'm not sure if the USB creator program can deal with it either. RUFUS is a good option for formatting.

Have you reformatted to FAT32 using RUFUS?

Collect diagnostics before the issue occurs, it contains system profile and settings information that may be relevant. It's not a universal issue that effects everyone, so anything that may help find commonalities is needed.

Look through the support thread specifically for tdarr on Unraid. If you can't find the answer there, the first post in that thread has a link to a discord, or ask in that thread.

This may partially explain the update loop that happens sometimes. I've always had a sense that when the loop happens it's using old information.

Crappy print quality, but it shows the basic form.

Try recreating the .ovpn file from your expressvpn account.

Once you have your largest disk completely copied elsewhere, change the desired format in that disk's properties page, when you start the array it will show unmountable and ask you to format it. As long as that particular drive is the only one showing unmountable, go ahead and format. Then copy the entire content of your next largest disk to the newly formatted disk, verify the copy was completed accurately with file comparisons or whatever, change the source disk format, lather, rinse, repeat.

Do you have enough free space on your array to empty your largest data disk?

As long as you stay out of the /mnt/user tree, MC will be fine. DFM has built in safeguards to keep you from corrupting data by mixing user and disk paths. I recommend copying vs. moving, that way your old disks remain intact as a backup, plus it's much faster because the parity drive doesn't get thrashed writing to both data disks each operation.

Probably, but the file manager would most likely be better.

Probably best to open another thread, this one has a clear problem and resolution.

I spent a few hours in blender, here's a rough draft. I can add Unraid text pretty easily, but I just wanted to get a proof of concept going. It's a very tight fit, Printed in PETG, so stringing galore across all the tiny holes. First draft was no ventilation, just the two shells, which printed perfect in PETG, but I wanted airflow possibilities. Have you checked temps after prolonged running yet?

If you really want to, you can delete the trial key and put your old license key file on the new stick and do the automated transfer, but that blacklists the old stick, limiting your options, and you only get 1 transfer per year through the automated system, otherwise you must contact support to get things sorted. Much easier to just use the old stick with a valid license already.

All your customizations are stored on the USB stick in the config folder. You are transferring all that information to the registered stick, then putting the registration key back with it so it knows it's a legit full license and not the trial. As long as you make a full backup of all the files on both sticks, you can reconstruct them at any point.

Yep. Unraid never moves data from one array disk to another by itself. You can use the Dynamix File Manager plugin.

Sounds like you have major hardware problems. Does the motherboard have a speaker attached? Any beeps?