![](https://seccdn.libravatar.org/avatar/6fed37b7418cd38e30d029f755e33f03.jpg?s=120&d=mm&r=g)
Andrei Borzenkov <arvidjaar@gmail.com> schreef:
11.10.2015 16:31, Istvan Gabor пишет:
As you see the array has only two devices still the "number" for the devices are 3 and 2. How could I change this to have number 0 for /dev/sdb13 and number 1 for /dev/sdc13?
Does it really matter?
The higher numbers have probably resulted from a disk being re-added to the array after the system has booted with only one disk, some time. So it started out as 0 1, then some disk became 2, then another disk became 3. You can see here on a system of mine that I have the same: md0 : active raid1 sda3[2] sdb3[0] md4 : active raid1 sda2[3] sdb2[2] This is because I have experimented with booting with only one disk to see what would happen and what I needed to do to get the array working again. I have no solution for your ...problem though ;-). Sure I would love the same. I also don't know how to reorder the raid numbers: md0 : active raid1 sda3[2] sdb3[0] md1 : active raid0 sda4[1] sdb4[0] md2 : active raid0 sda5[1] sdb5[0] md3 : active raid1 sda6[2] sdb6[0] md4 : active raid1 sda2[3] sdb2[2] as you can see the last array was added after the others, and it includes the boot partitions. You can also see that the stripe raids never did any kind of reordering (number increment) because they are simply not loaded when a disk is missing. I wonder how I can turn md4 into md0 and increment md0-md3, but I worry that grub will start to bolt if I do something wrong (it is a remote system). It also complains that my mdadm.conf is wrong (that no arrays are defined) but that is even another story. Regards.. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org