JorgeB

You need to do a new config without disk1 and re-sync parity, note that any data there will be gone, though it's unmountable anyway.

share.cfg doesn't yet exist, change a relevant setting, e.g,, enable disks shares, apply, change back and apply again then make sure that shareCacheEnabled="yes" exists on config/share.cfg, if it doesn't add it.

Why not just rebuild? You can do a clone but for parity to remain valid the array will need to be offline during it, disk needs to be the exact same size and you'd need to a new config once it's done.

You can still try this.

Diagnostics will show if you didn't reboot yet.

Do you have the optional SAS license?

You should run an extended SMART test on parity then act according to the result, but unlikely that's crashing the server, could be this issue:

Still looks related to the same issue as posted above.

Jan 30 01:55:40 Titanium kernel: macvlan_broadcast+0x116/0x144 [macvlan] Jan 30 01:55:40 Titanium kernel: macvlan_process_broadcast+0xc7/0x10b [macvlan] Macvlan call traces are usually the result of having dockers with a custom IP address, upgrading to v6.10 and switching to ipvlan might fix it (Settings -> Docker Settings -> Docker custom network type -> ipvlan (advanced view must be enable, top right)), or see below for more info. https://forums.unraid.net/topic/70529-650-call-traces-when-assigning-ip-address-to-docker-containers/ See also here: https://forums.unraid.net/bug-reports/stable-releases/690691-kernel-panic-due-to-netfilter-nf_nat_setup_info-docker-static-ip-macvlan-r1356/

After fixing the RAM run xfs_repair again, trying to fix it with bad RAM might makes things worse.

Looks unrelated to the new device, what happened to the other cache device? Balance is because there's a missing device and the log you posted ends during the balance without any errors for that that I can see, though btrfs is detecting corruption on multiple filesystems, so you likely have some hardware issue like bad RAM, and if the balance crashed after it's possibly because of that, start by running memtest.

Looks unrelated to the new device, what happened to the other cache device? Balance is because there's a missing device and the log you posted ends during the balance without any errors for that that I can see, though btrfs is detecting corruption on multiple filesystems, so you likely have some hardware issue like bad RAM, and if the balance crashed after it's possibly because of that, start by running memtest.

Post the command you used and the full output of xfs_repair. Lots of crashing, you should run memtest.

If you still have access to the pool you should back it up then re-format.

If TV Shows is the share it should be split only the top two directory levels, some examples below: https://forums.unraid.net/topic/59589-solved-v635-advice-please-on-shares-settings/?tab=comments#comment-584558

SMART test if failing, that might be the common N300 seek error issue, but that together with all the UNC errors means that IMHO the disk should be replaced.

Should be, even brackets for other controllers like the SASLP and SAS2LP work with standard LSI controllers. Yep.

https://forums.unraid.net/topic/51703-vm-faq/?do=findComment&comment=557606

Uninstall the corefreq plugin.

Fine if flashed to LSI IT mode. Both will have the same performance with SAS2/SATA3 expander/devices. Correct, and the bracket can usually be found on ebay. Usually it's fine, but to be sure you'd need to try it, or find anyone else using it with the same board.

That means the new config wasn't properly done, repeat the procedure.

Correct, all pool data became inaccessible.

Jan 28 10:35:32 TSA-NAS01 kernel: ahci 0000:03:00.1: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x000e address=0xb0010000 flags=0x0000] Problem with the onboard SATA controller, both cache devices dropped offline because of that: Jan 28 10:36:33 TSA-NAS01 kernel: ata1.00: disabled Jan 28 10:37:30 TSA-NAS01 kernel: ata2.00: disabled This is quite common with some Ryzen boards, rebooting should bring the pool back but if it keeps happening best to use an ad-don controller (or replace the board).

Best IMHO would be to move or re-create the docker image on cache.