On 24. 12. 21 17:46, Michael D. Setzer II via users wrote:
Did have our Admin have a System that was running SCO
and it had a failure in a 3 disk system. It kept working
fine after failure, but when they replace the bad drive the
rebuild that was suppose to be automatic failed. Some
how it mixed up which drive to rebuild and corrupted the
whole raid. (Could have been operator error, but that is
what they said happened?). Fortunately they did have a
back right before they did the replacement, so just a
couple days of down time. But know many never test that
the system works or how to do the restores, and just hope
it works. I like to also do bare metal backups just to be
sure. Running one right now on my only windows 10
machines to one of my 5 Fedora machines.
Best of luck to everyone. Unfortuantely, drives fail, and
often don't give warnings. But prices are less expensive.
Recall the 9G SCSI drives where like $450 each. My first
computer had an option for a 20M Seagate ST-225, but it
was a $2,000 option in 1983, so got my Heathkit H-120
Dual CPU system 8088/8080 with dual 320K floppies and
768K of Ram (more ram than IBM PC). Loved that
machine 8Mhz CPU.
Merry Christmas to those that celebrate it, and Best
Wishes to others.
Good point about raid mixing up which drive to rebuild. I was scared
shi***ss when I added one of the disks and saw mdraid status show drives
in the wrong order and I aborted the rebuild.
Turns out the order in which mdraid displays the drives and the UU_U(s)
is not relavant. I could not verify this in the docs, just found a
random forum post about it..