On 20/11/17 20:14, andreil1@starlett.lv wrote:
By the way, something else important :-)
Somebody had a glitch on their array because they swapped a disk out, then tried to add it back as a spare except mdadm got confused.
Make sure you use a *different* machine (or hotplug this drive *after* your array is up and running), and do a "mdadm --wipe-superblock" on the drive.
Otherwise, if this disk gets back into the machine, you could find yourself with a recovery scenario on your hands :-(
Cheers, Wol
Hi, Wol,
Thanks. RAID5 will be used on the same machine it is installed right now. BTW, mdadm is related to osftware RAID, in this particular case I have hardrware RAID. I stopped using software RAIDs long time ago.
Sorry, I don't think I made myself clear. If the old disk was swapped out and copied, then the old disk is "clean". If this disk gets back into the same machine as the raid array, and the machine is rebooted, mdadm IS GOING TO GET CONFUSED. Not a good idea. So *please* make sure you wipe all trace of the raid from the *old* disk, before you have an accident ... :-) (As the system boots, mdadm will add drives to the raid as udev finds them. If udev finds the old disk before it finds the disk that replaced it, mdadm will assemble the array with the wrong drives, and the result will be a bit of a mess. Not a problem with raids 5 & 6, but I gather you can trash a mirror pretty easily :-( Cheers, Wol -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org