JorgeB

Yes. Raid0. You need at least one array device assigned, it can be an old flash drive assigned as a data device.

Since parity is disable you can do it with the array started, then you'll need to re-sync parity.

See here:

That's usually the result of a device with multiple partitions not being correctly wiped by Unraid, wipe it with blkdiscard and re-format.

Auto parity check after a reboot is non correct, you need to run a correcting check, but most importantly you need to resolve what's causing the server to hang/reboot.

This indicates a CRC error, 9 times out of 10 it's a bad SATA cable.

You can.

You need to let a parity sync finish, parity check you can just cancel and add the drives.

It's a bug with the rc, go to Settings -> Global Share Settings and enable user shares.

Parity2 has pending sectors and appears to be failing, you are already running an extended SMART test, wait for the result, you should do the same for disk16 since it's logged as a disk problem on SMART.

I meant having only a device in the adapter first slot. Unfortunately that's not possible, it's transparent to the OS, you see the NVMe device(s) if it works, but noting if it doesn't or there aren't any NVMe devices installed.

Nothing NVMe related being detected, if there's just a device in the first slot there could be other issues.

Note that this can also be a device problem, you should also test with another device if available.

Yes, first one should still work, diagnostics might show something.

You're not, currently you can only have one pool per share, but since for this purpose you only write once then just need read access it's fairly easy to get around, you can configure the use cache option to only for the pool you're currently filling, when that one gets full change to next one, or just move the files there manually, once the files are there all the files on that share will still be under /mnt/user/share, so the farmer will see them all independent of the use cache setting.

Replace SATA cable.

Board would need x4/x4/x4/x4 bifurcation support, which as far as I know is not available for LGA1151, there are server boars with two x8 slots that can bifurcate one of them to x4/x4, that would work.

Those are historical devices, you can click on the red x to remove it from the listing.

You should try that if possible.

Disk10 looks OK, you should do a new config (Tools -> New config) and re-sync parity, after that's done run a non correcting parity check, if errors are found run another one and post new diags, all without rebooting.

Unraid supports multiple pools, you can have multiple small pools of a few disks, how many I would feel comfortable with will depend mostly on the size of the disks, plots on each pool can all be on the same share, same one as the array if you also have plots there, as long as you adjust the use cache setting correctly, this way chia can access all the pots with a single entry, e.g.: /mnt/user/plots, and if you lose a disk in a pool you only lose the plots in that pool.

You did, maybe you missed it:

According to that yes, it was disk12, disk itself looks OK, just a lot of CRC errors which suggest a cable problem, if you didn't write anything to the emulated disk once disk12 got disable you could just re-sync parity (after replacing SATA cables on disk12) but if you want to go back to how it was you can do this: -Since you've already re-assigned all the disks, so just make sure all assignments are correct. -IMPORTANT - Check both "parity is already valid" and "maintenance mode" and start the array (note that the GUI will still show that data on parity disk(s) will be overwritten, this is normal as it doesn't account for the checkbox, but it won't be as long as it's checked) -Stop array -Unassign disk12 -Start array (in normal mode now), ideally the emulated disk will now mount and contents look correct, if it doesn't you should run a filesystem check on the emulated disk -If the emulated disk mounts and contents look correct you can then rebuild to a new disk or the old one.

Diags are after rebooting so we can't see what happened, but the disk look healthy, so suggest replacing cables to rule that out and rebuilding on top: https://wiki.unraid.net/Manual/Storage_Management#Rebuilding_a_drive_onto_itself

Depends on the model, usually no.