Veah

The policy and execution I suspect do not match regarding key transfer. I bet it happens and it would be an extremely tough issue to combat; the juice not being worth the squeeze.

Extremely inciteful. Invested folks should read this several times and digest slowly. It's all valid.

Just found this, super helpful. Thank you.

Had a chance to verify mine, the comma/space bit is sorted just as itimpi pointed out. I better understand that line at least. Seems my issue resides elsewhere. Still hope your problem is resolved.

Did this work? I've had the same issue since about 6.12.1(ish)

Any updated gossip on the 6.13 release timeframe?

Had my turn today. Was able to change IP of PC logging in from LAN (.14 > .214 in my case) and it worked. The principle may work in a remote scenario if using vpn to change the ip.

The pdf here says operating temps 0-70C. Not sure if it covers your exact model. Saw 70C on a few sites while looking for something that seems official. https://www.crucial.com/content/dam/crucial/ssd-products/P2/flyer/crucial-P2-productflyer-consumer.pdf The trick I couldn't figure out was how to set different temp notification limits for different type drives... Hdd vs nvme vs SSD.

Consider after swapping parity and 1 data drive, see if all your data fits on the single drive. If it does, remove all the excess old drives so you only have 1 data + 2 parity. Then add all the new drives at once. Could keep things down to 4 parity rebuilds that way... If the data all fits on one drive anyway. May need to do it with 2 if not all fits. Edit:. Might be able to save another rebuild if you drop to a single parity instead of 2, I'm not certain that a final rebuild for 1 parity + all remaining data disks would work like I think.

You should start a new thread. This one is marked solution so many of the big brains around here may overlook this.

I have some old 1tb WD Greens that hold back my parity checks to ~80MBps speeds. My others are 18TB Exos. Once the WDs finish at about 6% of the check, the speeds pick right up to ~230MBps for the rest. So the initial prediction time drops a lot at my 6% mark. Found it fascinating when I noticed it.

Oof. That's rough. Hope it's not your biggest capacity.

I didn't think they did. It's been so long since I really had to know this stuff that it's easy for me to doubt my memory or just think things have changed again. Hoping OP gets the fix being searched for regardless.

Yes. The drive will not retain the information coming from it's previous home. All that goes away. unRAID will treat it like a new empty drive and make it ready for it's new home. It's previous life will be lost. Edit add: it will populate as if it is the drive you are replacing.

If the errors clear that's great. If they keep going up, not so great. After the parity is done building, he can look and see where it's at. Curious to know.

On mobile and can't read log. Look in the SMART section for your drive and you can see it's log. Some key points to see are power on hours, and crc errors. If it's new, those should be low and zero. Several other attributes there most of which should read zero. Double and triple check your power and data cables to include different cables. If it's a sata drive, give it a shot in the mb port to see if different results.

I did not check if you are running a gpu. If not, should be ok barring a weak 12V rail that can sometimes happen when a psu gets really old.

The other looks fine. Go into your diagnostic, under SMART, then open up both the ST4000DMxyz files side by side. You will see the columns I see and you can compare them side by side. *edit: CRC is basically the worst thing you can see in a HDD*

If you still have your receipt, I'd say its worth taking it back even if it is working based on that error.

Was just looking at the drive log more... 12 power on hours and 199 UDMA_CRC_Error_Count -OSRCK 197 193 000 - 40; you might have a lemon. I dont think drives bounce back from cyclic redundancy check errors, but maybe I'm wrong.

I see CRC errors on Device Model: ST4000DM004-2U9104 Serial Number: WFN85C8K That is your parity drive. It looks like a new drive is in your future.

Ok, got logged into mine and did a step by step for what I was attempting to convey. Passing to you exactly what I intended and see. Sorry its ugly cause I'm lazy and copy/pasted from notes I was taking. *** Stop array Set parity drive to ‘no device’ Scroll down, see this: Start will disable the missing disk and then bring the array on-line. Install a replacement disk as soon as possible. Yes, I want to do this Click Yes and then Start. Array started with no parity. Stop array again. Assign my initial disk to the parity position. Scroll down Start array. (Start will Parity-Sync and/or Data-Rebuild) *** In about a day and a half, I expect my parity to be rebuilt. Hope this helps. It's all I got to offer.

Just add the drive. Your other unRAID will format it and enable it for you with no difference from a new drive.

Initial thought is to take array offline. Remove the parity drive. Add it back and be sure it has the format disk option button/warning when you enable the array. It should begin building it.

Does it work with a single 3TB parity drive? If so, swap it out with the other 3TB drive. Does the 2nd drive work? When you see for sure they both work fine as individual parity drives, add the second one. Also be sure you are giving enough time for the single drive to be (re)built, if the 1st one doesn't finish, I don't believe a second, which is essentially a mirror) will correctly build. Side note: majority of users only use a single parity drive.