PFT

I moved the Parity 1 disk to an unused port on an AOC-SAS2LP-MV8 controller card and disk is now present. The array starts without problem, as originally expected. I conclude there is something configured on the Mobo which means its onboard controller ports are not compatible. Next time I power up the system I'll take a look especially to see if they are configured for Raid. But the bottom line is everything works as anticipated so thanks again for your help.

Both parity disks are connected to controller ports on the Supermicro X10 mobo, Originally (prior to switching cable to P1) P1 was connected to Sata0 and P2 to Sata1. After the switch P1 is connected to Sata2 (which was previously connected to an unused slot, slot 2).

tower2-diagnostics-20221205-1619.zip

OK thanks, I'll give it another go. Presumably getting diagnostics without starting the array will be OK?

I have a dual parity setup running 6.9.2. Parity 1 is in slot 0 and Parity 2 is in the adjacent slot, slot 1. Both disks are 16TB. Parity 1 has been reporting incrementing UDMA_CRC errors for some time now, which usually seem to occur when the disk is under heavy use e.g. at parity check time. I’ve done the recommended physical checks (cabling, connector seating etc) but the issue is recurring. I thought an easy fix would be to disconnect the Sata cable to the mobo port and connect a different cable to an unused controller port, in the belief that Unraid doesn’t care which controller port a disk is connected to. I did this but on restarting the system the Parity 1 disk is shown as missing. Being unsure how to proceed from here, I powered down the system and restored the cabling as before. Any advice will be appreciated.

OK thanks for the response. I had been pressing done and not apply. Now it works and you get get a message saying 'array reset'. The old disk slot is now unassigned and I can start parity. Thanks!

OK thank you. I have finally got round to upgrading the array and am following the 'Faster Method' as given in the article linked above. All the files have been copied to the new 16T disk and the old 4T disk removed. After powering up I am sitting at #8 'Use New Config to unassign removed disks and assign parity'. The parity assignment worked OK but I am unable to unassign the old disk which Unraid says is 'missing' Consequently I am unable to start the parity check due to 'Too many wrong and/or missing disks' What am I doing wrong? Thanks in advance.

I’ve been an Unraid user for over ten years and have had very few issues that I haven’t been able to resolve using the docs and the fantastic resource provided by the forum experts. Current scenario concerns a 24-disc array in a Supermicro enclosure running 6.9.2. I would like to replace around half of the disks, which are 4TB with power-on hours around the 60,000 mark, with a smaller number (3 or 4) of much larger disks. I’ve already replaced the 2 parity disks with 16TB Seagate Exos as well as one of the old data disks which Unraid had previously disabled. At this point I would like to start moving data files from some of the oldest 4TB disks to the new 16TB disk, then remove the now-empty 4TB(s) from the array, so I’m looking for an idiot-proof guide on how to do this. Especially for a two-parity configuration running 6.9.x. The closest I’ve come across so far is this: https://wiki.unraid.net/Replacing_Multiple_Data_Drives_with_a_Single_Larger_Drive Is this the latest ‘official’ procedure? Is it suitable for a 2-parity setup? I don’t see this wiki document in the current (6.9.2) pdf version of the Unraid manual. Thanks in advance for any advice.

I need to upgrade 4 of the older 2TB disks in my 24-disk server running 5.0. The replacements are 4TB all already pre-cleared. I understand that a rebuild must be done after swapping out each individual disk but is it necessary to run a parity check after each rebuild or can I wait until all four have been rebuilt? What if anything bad might happen if I do defer the parity check until the end of the process? Thanks.

Ok thanks. Once the parity check completes I'll go through the cable/port routine again to make sure I didn't miss anything.

Syslog showing errors with new disk (at end). syslog5-swapped_disks.zip

Well the mystery deepens. The disk passed the long smart so I replaced it with a newly pre-cleared one and let the system start the rebuild. Everything seemed to be OK at first but then several hours into the process there was a flurry of errors including some '10B8B LinkSeq' that I hadn't seen before. All again pointing to ata1 and slot 3. Right now I'm planning to let the rebuild finish and then move the disk to the slot currently occupied by the cache leaving slot 3 empty.

Yes, I tried that in #3 above. The motherboard has 14 SATA ports so that's an easy one. Also put the backplane (which supports 4 disks) on a separate power rail, but no change. Presently running another long smart test since the only constant in all this appears to be the drive in slot 3. Strangely though the system is telling me it will take 520 minutes, the previous one took 255.

Long Smart test passed. smart-long.txt

It turns out that there was nothing wrong with the chassis and I now have a spare power module. The problem was a faulty CPU.