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

I ran a correcting check, that corrected the errors, then ran a non correcting check, which returned no errors. Then on this months scheduled check that ran last night, it picked up 51, so I stopped that check and starting a correcting check , which is 33% complete , and has corrected the 51 errors. I have noted this from the logs though 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) Which doesnt look good

Hello Having corrected a 1000+ Paity Sync Errors , and replaced a disk last month, had errors on Night 1 of the new parity Check, so have stopped the check , and im now running a correcting check. Can anyone see from the logs, why this is happening? mordor-diagnostics-20250502-1529.zip

and im back again Woke up to a disk being dropped from the array this morning Please find diags attached, have replaced the faulty disk which was in slot 12. Rebuild is in progress, but early in the logs was seeing this? What disk does this relate too? Apr 5 09:16:01 Mordor kernel: ata4.00: failed command: READ FPDMA QUEUED Apr 5 09:16:01 Mordor kernel: ata4.00: cmd 60/20:c0:48:75:dd/01:00:00:00:00/40 tag 24 ncq dma 147456 in Apr 5 09:16:01 Mordor kernel: res 40/00:01:01:4f:c2/00:00:00:00:00/00 Emask 0x10 (ATA bus error) Apr 5 09:16:01 Mordor kernel: ata4.00: status: { DRDY } Apr 5 09:16:01 Mordor kernel: ata4: hard resetting link Apr 5 09:16:07 Mordor kernel: ata4: link is slow to respond, please be patient (ready=0) Apr 5 09:16:11 Mordor kernel: ata4: COMRESET failed (errno=-16) Apr 5 09:16:11 Mordor kernel: ata4: hard resetting link Apr 5 09:16:16 Mordor kernel: x86/split lock detection: #AC: CPU 0/KVM/40313 took a split_lock trap at address: 0xfffff80585c7b62f Apr 5 09:16:16 Mordor kernel: ata4: SATA link up 1.5 Gbps (SStatus 113 SControl 310) Apr 5 09:16:16 Mordor kernel: ata4.00: configured for UDMA/100 Once it dropped to ata100, it seems happy and is rebuilding at speeds I would expect mordor-diagnostics-20250405-0933.zip

Ok so the correcting check finished, and now the non correcting check has also finished, with no errors. Please find logs attached, anything else I need 2 do? mordor-diagnostics-20250404-0643.zip

Shall do, many thanks for the quick response!!!!

Hi woke up to seeing a bunch of uncorrected sync errors this morning, was a bit odd to say the least, currently running a parity correcting sync, please see logs attached. Currently have 5644 Errors at 27%, but doesn't seem to be climbing, anyway of seeing what's gone on mordor-diagnostics-20250401-1725.zip

Sorry its taken me a while to come back round to this. Having done some digging, im not sure it will work with tailscale. found a post that said the following "I don’t think that would work either. Roon device discovery uses IP multicast, which does not traverse the Tailscale VPN (there’s extensive discussion of this on other Tailscale threads). Roon ARC connects to the Roon server via a specified IP address, and traffic then flows over Tailscale. But the standard Roon app, designed for the local network, relies on Roon’s multicast discovery, and so it can’t find the Roon server when it is away from the local network where the server resides."

Sure will grab some screenshots from the docker container

Hi there, im trying to get Roon to work over tailscale from inside of a Docker Container, but it doesn't work, outside my network, although it joins my tailscale account just fine. Has anybody done this, and can tell me how this might work. I have it working over zeriotier, but would prefer to move everything to tailscale

Getting a similar issue , mover not moving any files, once I removed the mover tuning plugin its worked as expected