mraerosmith

That won’t be the case Parity must be equal to or larger than ur biggest data disk , as you have added a 12tb data disk, parity disk must be 12tb or larger so you will be blocked from adding the 6tb as parity , you could however add it as a data disk

That did the trick, many thanks

Converted to internal boot today, did the following Created a new pool cache used the wizard to make it boot with data then added a second drive, to mirror but in the gui it shows an error. Diags Attached Any help gratefully recieved. mordor-diagnostics-20260525-2232.zip

What firmware is the 9305 running ?

Seeing the below in my logs, can anyone tell me how I know which HDD this is referencing, diags are also attached Feb 1 13:42:00 Mordor kernel: ata8: hard resetting link Feb 1 13:42:06 Mordor kernel: ata8: link is slow to respond, please be patient (ready=0) Feb 1 13:42:07 Mordor kernel: ata8: SATA link up 3.0 Gbps (SStatus 123 SControl 320) Feb 1 13:42:07 Mordor kernel: ata8.00: configured for UDMA/133 mordor-diagnostics-20260201-1345.zip

Many thanks all good now

how do I tell what mount is being used, sorry this side of unraid is a bit new to me. Im using rysnc to move the data, and yep disabled docker and vm

Will the name of the new pool cause issues with docker etc ? Whats the best way to move the data to the new pool?

I have an existing 2TB NVME , that I wish to mirror to another NVME Drive, I get the error that the new drive is 2 small, and I can confirm that it is, although both are sold as 2TB Drives, is there anything I can do, short of buying another drive. See Diags attached, many thanks for any help. mordor-diagnostics-20251030-0950.zip

im using btrfs for my array disks, im not concerned per say, just the 2nd month I have had parity errors, and wondering if this is damging my files, how do I tell with btrfs

A further question, if the parity check has failed and then is ok and repairs itself after the check, is there any chance of file data corruption?

Finished with no errors, logs attached. Anything else I need 2 to be aware of? mordor-diagnostics-20250505-0917.zip

Correcting check has now finished, logs attached, now rebooting, and will run another check mordor-diagnostics-20250503-1522.zip

Shall do, will take a few days, but will let you know

May 2 15:36:02 Mordor kernel: ata4.00: exception Emask 0x10 SAct 0x900038e0 SErr 0x48d0002 action 0xe frozen May 2 15:36:02 Mordor kernel: ata4.00: irq_stat 0x04400040, connection status changed May 2 15:36:02 Mordor kernel: ata4: SError: { RecovComm PHYRdyChg CommWake 10B8B LinkSeq DevExch } May 2 15:36:02 Mordor kernel: ata4.00: failed command: READ FPDMA QUEUED May 2 15:36:02 Mordor kernel: ata4.00: cmd 60/00:28:b8:ad:be/04:00:51:02:00/40 tag 5 ncq dma 524288 in May 2 15:36:02 Mordor kernel: res 40/00:01:00:4f:c2/00:00:00:00:00/00 Emask 0x10 (ATA bus error) May 2 15:36:02 Mordor kernel: ata4.00: status: { DRDY } May 2 15:36:02 Mordor kernel: ata4.00: failed command: READ FPDMA QUEUED May 2 15:36:02 Mordor kernel: ata4.00: cmd 60/00:30:b8:b1:be/04:00:51:02:00/40 tag 6 ncq dma 524288 in May 2 15:36:02 Mordor kernel: res 40/00:01:00:00:00/00:00:00:00:00/00 Emask 0x10 (ATA bus error) May 2 15:36:02 Mordor kernel: ata4.00: status: { DRDY } May 2 15:36:02 Mordor kernel: ata4.00: failed command: READ FPDMA QUEUED May 2 15:36:02 Mordor kernel: ata4.00: cmd 60/00:38:b8:c1:be/04:00:51:02:00/40 tag 7 ncq dma 524288 in May 2 15:36:02 Mordor kernel: res 40/00:01:01:4f:c2/00:00:00:00:00/00 Emask 0x10 (ATA bus error) May 2 15:36:02 Mordor kernel: ata4.00: status: { DRDY } May 2 15:36:02 Mordor kernel: ata4.00: failed command: READ FPDMA QUEUED May 2 15:36:02 Mordor kernel: ata4.00: cmd 60/00:58:b8:b5:be/04:00:51:02:00/40 tag 11 ncq dma 524288 in May 2 15:36:02 Mordor kernel: res 40/00:01:01:4f:c2/00:00:00:00:00/00 Emask 0x10 (ATA bus error) May 2 15:36:02 Mordor kernel: ata4.00: status: { DRDY } May 2 15:36:02 Mordor kernel: ata4.00: failed command: READ FPDMA QUEUED May 2 15:36:02 Mordor kernel: ata4.00: cmd 60/00:60:b8:b9:be/04:00:51:02:00/40 tag 12 ncq dma 524288 in May 2 15:36:02 Mordor kernel: res 40/00:01:00:4f:c2/00:00:00:00:00/00 Emask 0x10 (ATA bus error) May 2 15:36:02 Mordor kernel: ata4.00: status: { DRDY } May 2 15:36:02 Mordor kernel: ata4.00: failed command: READ FPDMA QUEUED May 2 15:36:02 Mordor kernel: ata4.00: cmd 60/00:68:b8:bd:be/04:00:51:02:00/40 tag 13 ncq dma 524288 in May 2 15:36:02 Mordor kernel: res 40/00:01:00:4f:c2/00:00:00:00:00/00 Emask 0x10 (ATA bus error) May 2 15:36:02 Mordor kernel: ata4.00: status: { DRDY } May 2 15:36:02 Mordor kernel: ata4.00: failed command: READ FPDMA QUEUED May 2 15:36:02 Mordor kernel: ata4.00: cmd 60/00:e0:b8:a5:be/04:00:51:02:00/40 tag 28 ncq dma 524288 in May 2 15:36:02 Mordor kernel: res 40/00:01:01:4f:c2/00:00:00:00:00/00 Emask 0x10 (ATA bus error) May 2 15:36:02 Mordor kernel: ata4.00: status: { DRDY } May 2 15:36:02 Mordor kernel: ata4.00: failed command: READ FPDMA QUEUED May 2 15:36:02 Mordor kernel: ata4.00: cmd 60/00:f8:b8:a9:be/04:00:51:02:00/40 tag 31 ncq dma 524288 in May 2 15:36:02 Mordor kernel: res 40/00:01:00:00:00/00:00:00:00:00/00 Emask 0x10 (ATA bus error) May 2 15:36:02 Mordor kernel: ata4.00: status: { DRDY } May 2 15:36:02 Mordor kernel: ata4: hard resetting link May 2 15:36:08 Mordor kernel: ata4: link is slow to respond, please be patient (ready=0) May 2 15:36:12 Mordor kernel: ata4: COMRESET failed (errno=-16) May 2 15:36:12 Mordor kernel: ata4: hard resetting link May 2 15:36:17 Mordor kernel: ata4: SATA link up 6.0 Gbps (SStatus 133 SControl 300) May 2 15:36:17 Mordor kernel: ata4.00: configured for UDMA/133 May 2 15:36:17 Mordor kernel: ata4: EH complete