mdadm raid5 recover double disk failure – with a twist (drive order)

To answer your questions, Can it be restored? First thing’s first – STOP, sit back and just think a little. Yes, algorithm, chunk size and disk order is vital to getting whatever filesystem that was present, to properly re-assemble. But since you’ve overwritten the superblocks, you’re now left with trial and error. Second, is there … Read more

Unable to mount an XFS filesystem from Linux RAID6 array (“Log inconsistent”)

I want to extend suggestions above. It is extremly worth setting up overlay block device, so any changes to the file system that you’ll do in attempt to recover it will not change anything on the RAID and this will allow you to reset everything and start from the beginning. Therefore, you’ll be given infinite … Read more

mdadm – Remove disk from RAID0

First of all: to those, who still believes in “RAID0 has no hot spare”. It could have a manual spare, done by human, who understand RAID levels and mdadm. mdadm is software RAID, so it could do a lot of interesting things. Credits to Zoredache for the idea! So, the situation: you have RAID0 array … Read more

How do I list which drives are part of each RAID array?

cat /proc/mdstat will give you the output you need, relatively easy to parse, because the mapped device is on the same line as its members, e.g.: $ cat /proc/mdstat Personalities : [raid0] [raid1] [raid10] [raid6] [raid5] [raid4] [linear] [multipath] md0 : active raid1 sdf2[1] sde2[0] 81854336 blocks super 1.2 [2/2] [UU] md127 : active raid0 … Read more

explain md’s raid10,f2

Actually I think Wikipedia explains it better than the actual docs. Here’s the text from the article. The Linux kernel software RAID driver (called md, for “multiple device”) can be used to build a classic RAID 1+0 array, but also (since version 2.6.9) as a single level with some interesting extensions. The standard “near” layout, … Read more