(seems I will monopolize UNRAID support with my system - a system that worked fine for years)

 

So after reaching a "looking stable" state in my UNRAID (you can see other threads of my odyssey), where I have a system that looks like it is notrebooting, has a valid parity, 10 valid data disks and a disk that has been disabled... I decided I will do the proper thing (since the disabled disk was fine and a result of my other issues, to rebuild that (very important) disk, by "removing" it and re-adding it and letting system rebuild it (over the correct data) from the other disks.

And a new thing happened! One OTHER disk (that was not part of any of the previous issues), started having thousands of read errors!
I suspect cable again, but whatever I suspect I cannot try.

Because it DOES NOT cancel my data rebuild! I clicked 4-5 times already, it pops that it will stop data-rebuild, yet IT DOESN'T STOP!!!

Rebuild shows like it will take 2.5 years (estimated finish) and I am left without a way out!!!

 

What can I do!?

Why doesn't it stop!?
With disk's read errors it has messed the rebuild already?

 

How can I stop it, check the disk (cables etc.) and re-start the rebuild!?

 

This is an unbelievable mess!

 

..it stopped after 10 minutes of trying to stop it (!?).

I stopped array, shutdown, moved cables again, rebooted.

Now disk shows fine, like it was never removed.
I started in maintenance mode without the original ex-disabled disk. Stopped again and added it back.

It started rebuilding it from the beggining, with fine reads from all disks and write to the ex-disabled.

So, assuming that the above problem, didn't write-back to parity anything (how could it, after all), I probably fixed it.

The rebuild is slow because now I was forced to use some of my (deteriorating?) SATA controllers' ports and a couple of on-board SATA ports - but at least if NOTHING else happens (I have disabled mover too for now), I will be back to fully working and protected order in a few days.

 

I expect the last remaining issues to be resolved with the arrival of my new-to-me 9400 16i controller that will take over the ageing dual LSI 2008 compatible controllers.

Wish me luck. For whoever read about my Odyssey over 4-5 different threads (for different issues), I think you will do it.

 

Remaining issue (aside from above waiting to be ticked "ok"), is the docker DNS issue I now have (has its own thread).