I have a single disk that I want to create a mirror of; let’s call this disk sda. I have just bought another identically-sized disk, which we can call sdb. sda and sdb have one partition called sda1 and sdb1 respectively.
My current idea is to create one software array, class RAID-6, with 4 member drives, using mdadm.
I have a server with three identical SATA/600 3TB drives: /dev/sda, /dev/sdb, /dev/sdc. The drives are partitioned, using GPT with three partitions each:
I had just asked this question where I was unable to boot after installing a new RAID1 Array. I was able to get to the terminal, but once I sorted that out I realized that my problem isn’t so much an fstab boot problem as an mdadm auto assemble problem.
I have a software RAID5 array (Linux md) on 4 disks.
Can someone explain the difference between the UUID’s reported by blkid and mdadm? On one of our CentOS systems, for example:
1st attempt: Mounting disks alone
Can someone please explain to me, what the difference is between creating mdadm array using partitions or the whole disks directly? Supposing I intend to use the whole drives.
I’m using GPT as my partitioning scheme. I check the UUID’s of my partitions:
I’m about to re-organise all my HDDs in my home linux box nas and would like to use mdadm raid for data protection and its flexibility for reshaping the arrays. However, before I use mdadm for this I’d like to know how it handles bit rot. Specifically the kinds of bit rot that do not result in unrecoverable read error messages being sent from the HDD.