For experimental reasons I was running a RAID0 array (the speed!) off of two Sandisk Cruiser Mini USB sticks connected to a Raspberry PI.
As expected, due to wear and tear one of the flash memories eventually failed causing the array to go read-only and crash everything that was writing to it, including the array activation.
Loading a RAID driver for the motherboard integrated controller is a familiar procedure for anyone having used such a setup under Windows regardless of using AMD or Intel-based systems.
However, the AMD Ryzen series of chipsets have a slightly odd driver initialization procedure needing the use of multiple driver layers loaded in the correct order.
After migrating a RAID volume to new disks it’s handy to keep a full partition backup around.
For this we can use partclone, a handy smart backup utility which is capable of recognizing multiple filesystem structures and then save only used data.
Every once in a while hardware needs to be replaced. Sometimes boards, sometimes CPUs and sometimes drives. Drives are the ones most difficult to replace as they hold all that precious data one does not want to lose.
I personally hate reinstalling stuff; so I try as much as possible to “migrate” my data around. In this tutorial I’ll be replacing two drives under a RAID1 array with two newer bigger drives (and resize the array accordingly).
When replacing a failed RAID1 member from the array, setting up the replacement disk requires to partition it exactly as the existing disk. But this takes time to do manually…
Fortunately, sfdisk comes in handy by providing a very fast shortcut…
I decided to rearrange space a bit on the new CentOS server I am setting up…
This tutorial lists the steps I took to resize (grow) a functional RAID1 volume to a new size without losing data.
I recently attempted to install a fresh CentOS on a pair of recycled (previously used in a different linux sistem) hard disks.
Of course I got the classical message that the disks already had RAID metadata on them: “Disk contains BIOS metadata, but is not part of any recognized BIOS RAID sets. Ignoring disk sda”
