[Parity disabled with read errors during array shrinking]

Cool then. Thanks for your help @JorgeB!

[Parity disabled with read errors during array shrinking]

Parity check completed with a ton of errors.... Should I be concerned about the health of my parity drive?

The smart report I attached to the first post didn't seem to indicate anything bad... but this sounds a bit worrisome:
 

Last check completed on Thu 30 Mar 2023 03:36:21 AM MDT (today)
 Duration: 18 hours, 5 minutes, 48 seconds. Average speed: 153.5 MB/s
 Finding 1678945 errors

 

[Parity disabled with read errors during array shrinking]

Ok, so tools > new config > preserve current assignments > all > yes I want to do this > apply/done. The warning on this page had me worried: 

Quote

DO NOT USE THIS UTILITY THINKING IT WILL REBUILD A FAILED DRIVE - it will have the opposite effect of making it impossible to rebuild an existing failed drive - you have been warned!

Then on main page, remove disk3 from array >
At this point do I check the "parity is already valid" box as described in Shrink array - Unraid | Docs step 14?

Then start array and manually start a parity check?

 

[Parity disabled with read errors during array shrinking]

I tried reseating all the cables and swapping slots. What do I need to do to "re-sync"? 

I failed to mention that one of the reasons I'm concerned with doing anything to the array configuration to rebuild parity is because that disk3 that I was removing is now showing as unmountable (you can see that in the diagnostics), I think because the disk has been wiped so there's no filesystem or anything. I'm concerned that trying to "rebuild" parity with that disk still part of the array configuration but being unmountable is going to bork the parity rebuild.

Can I finish removing the disk _and_ rebuild the parity, or is there something else I should do like reformat disk3 but keep it in the array to rebuild parity?

(I'll add a note to the original post about the disk3 unmountable issue for future readers)

[Parity disabled with read errors during array shrinking]

I was in the process of shrinking my array following the "Clear Drive then Remove Drive" method. I had manually removed everything from the disk and had kicked off the clear-drive script... and forgotten about it for a few days (so I didn't do steps 10-17 from the instructions about creating the new config and retaining the current configuration and removing the drive). Then I got some alerts about some read errors and the parity drive is now disabled.

I stopped the array and ran the extended smart test on the parity drive, tried rebooting (hopefully I didn't shoot myself in the foot there) but I'm too nervous to do anything with the array configuration. I've attached my smart test and my diagnostics. 

What should I do to get back to working order?

Edit: I failed to clarify that disk3 that was being removed is now reporting as "unmountable", which I think is because it was wiped clean. The diagnostics show the error when trying to mount that disk into the array. My concern is with the combination of the disabled parity _and_ the unmountable disk3 and how that might impact an attempt to rebuild parity or something.

diego-smart-20230328-1203.zip diego-diagnostics-20230328-1206.zip

[VM's snapshots]

This would be great!

[[SOLVED] Cannot access dockers using custom:br0]

On 6/28/2020 at 8:13 AM, ceyo14 said:

ok, so I have Host Access to custom networks Enabled, but for some reason it doesn't work all the time...I remembered I had to disable and enable the option for it to work a while back... I did this now and it fixed my issue again...

 

On 9/13/2020 at 5:04 AM, OFark said:

 I too am seeing this error. I have the Access to custom networks enabled, but upon restart access has been lost. Disable Docker, Apply, disable access to custom networks, Apply, Re-enable Docker and access to customer networks and boom back again. A touch frustrating.

Oh man! Thanks guys! I had these issues with my HomeAssistant VM and a mariadb container months ago and started getting them again over the weekend after restarting my unraid host. It took me hours to find this thread that lead to the solution that I no doubt implemented back then.

I'm assuming this (the need to disable and reenable for it to take effect) is some sort of bug then that needs to be fixed?

 

[[6.6.6] 24/7 Surveillance server NOT on the array?]

@Efficiency93 I think I'm following down your same path... and am similar to you in that I get easily intimidated with things I don't understand. I've got the zoneminder docker setup and just put a surveillance hd in the machine. I think I installed the unassigned devices plugin correctly and am wondering if you could post those step by step instructions to add that drive to the zoneminder docker and possibly explain if you ended up moving all the appdata off the array/cache drives too. I think I remember reading that zoneminder does a lot of read/writes for events and stuff.

 

Any help would be greatly appreciated!

Thanks