JorgeB

There are some IOMMU related call traces, update to latest Unraid and post new diags.

Please post the diagnostics.

Replace only works for multi device pools, please post the output of btrfs fi show

Try this:

It should, also make sure you check "parity is already valid" before array start, but if RAID controllers are involved you might get and invalid partition error, if that's the case post new diags.

Nov 28 09:12:38 Tower dhcpcd[1015]: br0: probing for an IPv4LL address Nov 28 09:12:43 Tower dhcpcd[1015]: br0: using IPv4LL address 169.254.195.99 DHCP server is not providing an IP address, this suggest a router problem, or your are not connected to one.

If Ubuntu connects it suggests an issue with your Windows installs, use the Ubuntu spare drive to do a clean Windows install to test.

You should post I the existing UD plugin support thread, and also post the diagnostics.

Yes, and cache pools can be redundant, but there's no dedicated parity, so just wanted to make sure you didn't mean the array.

Changed Status to Closed Changed Priority to Other

Stock Unraid doesn't have any fan control, see if the same happens after booting in safe mode.

Basically that, make sure docker and VM services are disabled if used.

In the earlier diags there are issues with multiple devices before parity drops offline: Nov 25 07:36:55 Tower kernel: ata14.00: exception Emask 0x10 SAct 0x0 SErr 0x0 action 0x6 frozen Nov 25 07:36:55 Tower kernel: ata14.00: irq_stat 0x48000001, interface fatal error Nov 25 07:36:55 Tower kernel: ata14.00: failed command: READ DMA EXT Nov 25 07:36:55 Tower kernel: ata14.00: cmd 25/00:40:48:0d:4a/00:05:f5:02:00/e0 tag 3 dma 688128 in Nov 25 07:36:55 Tower kernel: res 53/84:30:57:10:4a/00:02:f5:02:00/40 Emask 0x10 (ATA bus error) Nov 25 07:36:55 Tower kernel: ata14.00: status: { DRDY SENSE ERR } Nov 25 07:36:55 Tower kernel: ata14.00: error: { ICRC ABRT } Nov 25 07:36:55 Tower kernel: ata14: hard resetting link Nov 25 07:36:55 Tower kernel: ata11.00: exception Emask 0x10 SAct 0x0 SErr 0x0 action 0x6 frozen Nov 25 07:36:55 Tower kernel: ata11.00: irq_stat 0x48000001, interface fatal error Nov 25 07:36:55 Tower kernel: ata11.00: failed command: WRITE DMA EXT Nov 25 07:36:55 Tower kernel: ata11.00: cmd 35/00:40:48:f8:49/00:05:f5:02:00/e0 tag 7 dma 688128 out Nov 25 07:36:55 Tower kernel: res 51/84:40:48:f8:49/00:05:f5:02:00/e0 Emask 0x10 (ATA bus error) Nov 25 07:36:55 Tower kernel: ata11.00: status: { DRDY ERR } Nov 25 07:36:55 Tower kernel: ata11.00: error: { ICRC ABRT } Nov 25 07:36:55 Tower kernel: ata11: hard resetting link Nov 25 07:36:55 Tower kernel: ata14: SATA link up 6.0 Gbps (SStatus 133 SControl 300) Nov 25 07:36:55 Tower kernel: ata14.00: configured for UDMA/133 Nov 25 07:36:55 Tower kernel: ata14: EH complete Nov 25 07:36:55 Tower kernel: ata11: SATA link up 6.0 Gbps (SStatus 133 SControl 300) Nov 25 07:36:55 Tower kernel: ata11.00: configured for UDMA/133 Nov 25 07:36:55 Tower kernel: ata11: EH complete Nov 25 10:11:49 Tower kernel: ata14.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 Nov 25 10:11:49 Tower kernel: ata14.00: irq_stat 0x40000001 Nov 25 10:11:49 Tower kernel: ata14.00: failed command: READ DMA EXT Nov 25 10:11:49 Tower kernel: ata14.00: cmd 25/00:40:a8:16:ed/00:05:6d:03:00/e0 tag 24 dma 688128 in Nov 25 10:11:49 Tower kernel: res 53/84:c0:27:17:ed/00:04:6d:03:00/40 Emask 0x10 (ATA bus error) Nov 25 10:11:49 Tower kernel: ata14.00: status: { DRDY SENSE ERR } Nov 25 10:11:49 Tower kernel: ata14.00: error: { ICRC ABRT } Nov 25 10:11:49 Tower kernel: ata14: hard resetting link Nov 25 10:11:54 Tower kernel: ata14: link is slow to respond, please be patient (ready=0) Nov 25 10:11:59 Tower kernel: ata14: COMRESET failed (errno=-16) Nov 25 10:11:59 Tower kernel: ata14: hard resetting link Nov 25 10:12:02 Tower kernel: ata14: SATA link up 6.0 Gbps (SStatus 133 SControl 300) Nov 25 10:12:02 Tower kernel: ata14.00: configured for UDMA/133 Nov 25 10:12:02 Tower kernel: ata14: EH complete Nov 25 10:12:03 Tower kernel: ata11.00: exception Emask 0x10 SAct 0x0 SErr 0x10000 action 0xe frozen Nov 25 10:12:03 Tower kernel: ata11.00: irq_stat 0x80400000, PHY RDY changed Nov 25 10:12:03 Tower kernel: ata11: SError: { PHYRdyChg } Nov 25 10:12:03 Tower kernel: ata11.00: failed command: WRITE DMA EXT Nov 25 10:12:03 Tower kernel: ata11.00: cmd 35/00:40:28:71:ee/00:05:6d:03:00/e0 tag 3 dma 688128 out Nov 25 10:12:03 Tower kernel: res 50/00:00:28:71:ee/00:00:6d:03:00/e0 Emask 0x10 (ATA bus error) Nov 25 10:12:03 Tower kernel: ata11.00: status: { DRDY } Nov 25 10:12:03 Tower kernel: ata11: hard resetting link Nov 25 10:12:03 Tower kernel: ata11: SATA link down (SStatus 0 SControl 300) Nov 25 10:12:09 Tower kernel: ata11: hard resetting link Nov 25 10:12:09 Tower kernel: ata11: SATA link down (SStatus 0 SControl 300) Nov 25 10:12:14 Tower kernel: ata11: hard resetting link Nov 25 10:12:14 Tower kernel: ata19: SATA link down (SStatus 0 SControl 300) Nov 25 10:12:14 Tower kernel: ata20: SATA link down (SStatus 0 SControl 300) Nov 25 10:12:15 Tower kernel: ata11: SATA link down (SStatus 0 SControl 300) Nov 25 10:12:15 Tower kernel: ata11.00: disable device This is usually a power/connection problem, could also be a controller issue, save the current syslog cp /var/log/syslog /boot/syslog.txt then reboot and post new diags after array start.

That's usually just a filesystem problem, not drive, but because of the controller cannot see SMART for the device.

BTRFS error (device sdc1): parent transid verify failed on 430581235712 wanted 3932779 found 3932422 This error is fatal, it happens when there are lost writes, i.e. when the controller/device tells the OS all writes were complete when in fact they weren't, usually a device/controller firmware issue, also note that RAID controllers are not recommended and can cause this. Best bet to recover the data is usually btrfs restore, option #2 here: https://forums.unraid.net/topic/46802-faq-for-unraid-v6/?do=findComment&comment=543490

There's no parity drive for pools, assuming you still mean a pool and not the array you can fix that by unassigning the pool device, start array, stop array, re-assign the device, start array. Note that some USB bridges are not transparent, i.e., it won't detect the old partition, if that happens don't format.

Is this a single drive pool?

They should mount using the Unassigned Devices plugin.

With NOCOW cheksums are disabled, so there's no way for btrfs to reconstruct the data if one device fails, possibly worse than that, if one device drops offline for some time and comes back online btrfs has no way of knowing which device has the correct data, and as it reads from both devices it will corrupt existing data.

By console I meant to use a keybaord and monitor on the server or IPMI if you have it.

The PCIe errors are likely unrelated, but this might help with those. As for the parity errors, run another check if more errors are found start by running memtest.

Try renaming/deleting network.cfg on the flash drive then reboot and post new diags.

Please post new diags after array start.

Try booting in safe mode to rule out any plugin issues but it could be a compatibility issue between your hardware and the newer kernel.

That suggests they were never btrfs or they were completely wiped with a trim command or similar, you'll need to restore the data from backups.