JonathanM

Are you sure that performs the same function? Some BIOS's have a "load performance settings" "load default settings" and possibly other options.

After you did that, did you "load cmos defaults"?

Is the motherboard BIOS latest version?

You said they boot in your gaming PC, so I assumed you saw the menu there.

Does the non-GUI mode work?

If you can't find it in your email history, contact support.

That's not necessarily true. If you know the drive assignments (which is covered in step 3) you can set a new config with the drives in all the right slots, select parity is already valid, and start the array in maintenance mode so nothing is written. Then shut down and remove the failed drive, and you should be back in the position to do a normal replacement. Depending on how far you got you may still be able to recover. Please start a new thread in general support with your current situation, how you got there, and your diagnostics zip file attached.

Because parity wasn't valid when disk1 dropped.

You will need to do that from your backups.

Probably because the Unraid container page tracks them by name, which doesn't change when updated. The actual container ID does change. Run the docker ps -a before and after an update, and compare the first value in each line. You can do docker ps -a>>/boot/list.txt which will write list.txt to the root of the flash drive if you want a more permanent copy, plus you can cut n paste to here easier.

Try looking through the support thread for the User Scripts plugin, if the question is not already answered post there.

You are missing the point. When you are accessing the WebUI, the IP range you are connecting FROM must be whitelisted in the LAN Network section.

Unclear what you mean there. User shares are simply a merged view of the root folders in all the participating array disks and pools. If a file exists in multiple locations that are merged, Unraid can't know which file is "correct", so it only shows one of the files in the user share. For example: /mnt/disk1/myshare/document1.txt and /mnt/pool/myshare/document1.txt are the same location /mnt/user/myshare/document1.txt so only one of the copies is actually shown in the user share. If the mover is set to move files from the pool to the array, it can't, because it would overwrite the file on disk1. Files that already exist in one location are overwritten rather than making a second copy, to avoid the issue I outlined above. The primary share location is only applied to new files, existing files are read and modified from their current location.

it would be easier to use the userscripts plugin so you don't have to redo everything at each reboot.

Most people just use a normal desktop type computer, size depending on how many disk drives you anticipate. Disk cooling is a critical consideration. A normal 4U rackmount server is also popular for very powerful builds.

No.

If you are ok with invalidating parity and rebuilding it, you can set a new config with all the drives and rebuild parity. You will be unprotected from drive failure for the duration of the parity build. Probably quicker just to let the clear finish.

Ok. I saw you redacted the info in previous posts, so didn't know if you meant to post that much of the URL.

Probably need to obscure your unraid link.

I'm not well versed in ZFS, but I think you have to destroy the dataset.

Does a file system check come back clean?

Have you used mc from the console?

What path did you specify for the appdata?

Probably because you didn't copy the tag correctly. linuxserver/transmission:4.0.5