Carpet3

Ah, thank you I'll give this a try and mark this as solved hopefully.

Hi, Running Unraid 6.9.2serenity-diagnostics-20220315-1844.zip Hopefully someone can help me with this. My secondary parity drive keeps throwing an error. This has been happening for a couple of months. I can add the drive to the array and it will be fine for a week or so (this is with normal reading/writing to the array during that week) and then enventually the array with fall into an error state with the second parity drive showing 896 errors. I can remove the parity drive from the array and the array will then be fine. If I re-add the drive back to the array it will rebuild fine and last another week of normal usage before throwing the exact same 896 errors again. SMART report is coming back as ok on the drive and I have tried changing the cable on it. I have run a preclear on the drive after it threw the error and it all goes ok with no errors. Added back into the array and a week (ish) later it'll be back to the same. From what i've seen , it's always 896 errors, seems pretty consistent on that which I find odd and can't work out what's causing it. I also seem to have a failing cache drive (the reallocated sectors has been slowly creeping up over the last couple of weeks but I believe this to be a separate issue) Diagnostics attached. serenity-diagnostics-20220315-1844.zip

Ah ok, I think I see how you determined that. Thanks for the help. I'll try a memtest and change that cable over and see how it goes

Hey, thanks for the response. Why do you say parity 2? How did you identify that was potentially the problem? I recently (a few weeks ago) upgraded that drive. It precleared ok

For reference, I'm using all the ports on my motherboard and a M1015/SAS9220-8i card in IT mode

Hi, I've just started getting tens of thousands of errors on my server. First check got 46724, I did a subsequent (none correcting) check and it came up with 99800. Could someone help with what's going on? Diagnostics attached before I rebooted it. I can see the following error again and again in the log: Mar 4 23:56:24 Serenity kernel: ata10: SATA link up 6.0 Gbps (SStatus 133 SControl 300) Mar 4 23:56:24 Serenity kernel: ata10.00: configured for UDMA/133 Mar 4 23:56:24 Serenity kernel: ata10: EH complete Mar 4 23:58:25 Serenity kernel: ata10: limiting SATA link speed to 3.0 Gbps Mar 4 23:58:25 Serenity kernel: ata10.00: exception Emask 0x10 SAct 0x0 SErr 0x190002 action 0xe frozen Mar 4 23:58:25 Serenity kernel: ata10.00: irq_stat 0x80400000, PHY RDY changed Mar 4 23:58:25 Serenity kernel: ata10: SError: { RecovComm PHYRdyChg 10B8B Dispar } Mar 4 23:58:25 Serenity kernel: ata10.00: failed command: READ DMA EXT Mar 4 23:58:25 Serenity kernel: ata10.00: cmd 25/00:40:d8:c5:9b/00:01:05:00:00/e0 tag 20 dma 163840 in Mar 4 23:58:25 Serenity kernel: res 50/00:00:d8:c5:9b/00:00:05:00:00/e0 Emask 0x10 (ATA bus error) Mar 4 23:58:25 Serenity kernel: ata10.00: status: { DRDY } Mar 4 23:58:25 Serenity kernel: ata10: hard resetting link Mar 4 23:58:31 Serenity kernel: ata10: SATA link up 3.0 Gbps (SStatus 123 SControl 320) Mar 4 23:58:31 Serenity kernel: ata10.00: configured for UDMA/133 Mar 4 23:58:31 Serenity kernel: ata10: EH complete I'm guessing it's either the card or one of the drives but I don't see how to identify which? I recently (before these errors showed up) did a quick SMART test on all the drives and they all passed. I know one of the disks (7) has a lot of UDMA errors but this was due to a faulty cable a while back and has been fine for a long time. Thanks in advance serenity-diagnostics-20200304-2331.zip

Upgraded, has rebooted ok.

Nice to see another update (Although I was a bit disappointed when I saw 6.1.8 and not 6.2)

Would anyone be able to help me? I'm trying to create a raid array but it isn't allowing me. Further details in this thread: http://lime-technology.com/forum/index.php?topic=23009.0 Thanks

I power cycled before wiping the MBR but not after. I'll try that now. This is so frustrating!

The cycle has just finished. It went through all the steps ok (monitored it and watched it as it went through) Each step completed but I get the same error at the end. The drive wont respond at the moment but a powercycle will get it back up and running again I've no idea what to do

Thanks very much for this. I've just cleared the mbr on the drive using the -z option and have now started a new -A preclear. See what happens You truly are a huge asset to this forum

My apologies, upon searching this thread for the command to clear the mbr it appears i'm not the first with this sort of problem. Can I just confirm with you that to clear the mbr you need to use the -n switch and then just stop the process once the clearing of the rest of the drive starts? I assume once that's done I can just restart the server and do a normal preclear?

Would clearing the mbr help? Weird thing is this is very consistent

Having a problem with a new 10EARS hdd. I've run the preclear twice now and each time it fails at stage 10 and says the drive cant be completed. I've run DLGDIAG afterwards and on a quick scan it says the drive is fine but on a long scan it says errors were found but fixed. I've just run it again on a long scan and it says there were no errors detected with the drive. It's now doing a third preclear so i'll see what happens. Is there anything else I can do or it the drive on the way out? Edit: added pic

Could it be added to the array with no problems or not?

What happens if you cancel preclear when it's zeroing the drive on the second or third cycle?

I assumed as much just wanted to be sure Cheers

I've been running pre clear on my new hdd and the first cycle is almost complete but it's been running for 41 hours so far and stupidly i set it to run for 3 cycles. Its now at 96% of the first cycle and honestly i dont want to run it anymore. Once this cycle is complete can i just exit pre clear?