Re: Rebuilding RAID 1 Array in Linux with a new hard disk after a disk fault - Howto with screen shots
On Fri, Jun 18, 2010 at 4:27 AM, Michal <email@example.com> wrote:
> On 17/06/2010 14:08, Huang, Tao wrote:
>> On Thu, Jun 17, 2010 at 4:17 PM, Michal <firstname.lastname@example.org> wrote:
>>> This is a better way then disconnecting the drive and checking which
>>> drive was disconnected like I did, but I would still put a very easy to
>>> read label on the drive to say /dev/sdX. It would be far easier then
>>> checking a long serial number, especially if it's hard to read and you'd
>>> need to take each HDD out to check :)
>> I think the allocating of /dev/sdX depends on the order you plug the
>> drives into the machine.
>> so it changes over reconfiguring of the hardwares, which makes your
>> labels useless.
>> can someone confirm this?
> But how can this be correct when each raid partion is linked to the
> # cat /proc/mdstat
> Personalities : [raid1] [raid6] [raid5] [raid4]
> md3 : active raid1 sda2 sdb2
> 716796096 blocks [2/2] [UU]
> md2 : active raid1 sda5 sdb5
> 51199040 blocks [2/2] [UU]
> md0 : active raid1 sda1 sdb1
> 513984 blocks [2/2] [UU]
> md1 : active raid1 sda3 sdb3
> 102398208 blocks [2/2] [UU]
mdadm assembles an array according to data in the superblock so it
shouldn't matter whether the kernel recognizes sda and sdb as sdb and
sda respectively should you plug them in differently.