JorgeB

OK, in that case it's not mounting because the pool is set to 2 slots, xfs only woks with 1 slot, if you change the pool to 1 slot and set the filesystem to auto it should mount.

Start here: https://forums.unraid.net/topic/46802-faq-for-unraid-v6/?do=findComment&comment=819173

If you are sure it was btrfs then it was wiped since the diags, just doing a new config won't do that, but you might be able to recover the filesystem with: btrfs-select-super -s 1 /dev/sdb

Fresh boot sometimes helps, that's why I ask for that.

OK, let me see if I understand, you are doing a new config and expect the data on the cache device to remain there, that is true, just doing a new config doesn't delete data on any devices, the diags don't show a new config, and since boot that cache device never had a btrfs filesystem, i.e., it was wiped before, assuming it was btrfs, since the pool is configured for two devices it assumes a btrfs fileystem, maybe it was xfs before, please post the output of blkid

Create a new flash drive and extract only the /config folder from the backup overwriting any existing files.

Closing this one since you started a new thread:

Disk10 dropped offline, cancel the rebuild, replace cables on the disk10 and try again.

Strange, don't remember a similar issue, but if it's working great.

Both btrfs pools are detecting data corruption, start by running memtest.

Backup current /config folder then recreate the flash drive using the USB tool, also make sure you are using a USB 2.0 port, if issues continue after that you should replace it.

Yes, replace cable, both power and SATA.

Oct 13 10:01:30 ShadowRaid kernel: nvme nvme0: I/O 471 QID 5 timeout, aborting Oct 13 10:01:30 ShadowRaid kernel: nvme nvme0: Abort status: 0x0 Oct 13 10:02:00 ShadowRaid kernel: nvme nvme0: I/O 355 QID 5 timeout, aborting Oct 13 10:02:00 ShadowRaid kernel: nvme nvme0: Abort status: 0x0 Oct 13 10:02:30 ShadowRaid kernel: nvme nvme0: I/O 356 QID 5 timeout, completion polled Oct 13 10:03:00 ShadowRaid kernel: nvme nvme0: I/O 357 QID 5 timeout, aborting Oct 13 10:03:00 ShadowRaid kernel: nvme nvme0: Abort status: 0x0 Oct 13 10:03:30 ShadowRaid kernel: nvme nvme0: I/O 358 QID 5 timeout, aborting Oct 13 10:03:30 ShadowRaid kernel: nvme nvme0: Abort status: 0x0 Looks like a problem with that NVMe device, but it doesn't necessarily mean a bad device, swap both NVMe devices and see if the problem follows it.

Except for some networking config issues not seeing anything relevant, do you now the actual time it last crashed?

Strange, try connecting a disk to one of those ports to see if there's any difference.

Correct, you could use the single profile to use all the space but it would still use both devices one at a time, so not the best for performance.

Looks more like a boad/BIOS problem, look for a BIOS update.

Run it again without -n or nothing will be done, if asks for -L use it.

It will start over from the beginning.

Yep.

I would recommend posting the diagnostics first but if you just want to rebuild you can do both at the same time, make sure the emulated disks are mounting before starting.

Also post the permanent syslog, it's not included in the diags.

Unmountable disk usually means a filesystem problem, check filesystem.

Yes, and that's usually the slower one. No, just for writes. And yes, they do look reasonable and about what I would expect.