Building Out XenServer 6.5 with USB Boot and Software RAID 10

scottalanmiller

We need to find the missing array before we can do anything else. As @romo mentioned we need to scan and see if the array is out there somewhere.

DustinB3403

DustinB3403

Running

    mount md0

results in

   mount: mount point /mnt/raid10 does not exist

scottalanmiller

mkdir /mnt/raid10

Romo

@DustinB3403 what is in your mdadm.conf?

DustinB3403

Can't find

    md0 in /etc/fstab or /etc/mtab

scottalanmiller

@DustinB3403 said:

Can't find

    md0 in /etc/fstab or /etc/mtab

Should not be there, right?

DustinB3403

@Romo said:

@DustinB3403 what is in your mdadm.conf?

DustinB3403

@scottalanmiller said:

@DustinB3403 said:
Can't find
    md0 in /etc/fstab or /etc/mtab
Should not be there, right?

I added an entry into fstab. It may have a typo...

DustinB3403

fstab

DustinB3403

fstab corrected, entry reversed.

     mount raid10
mount: /mnt/raid10 is not a block device

Romo

Your could run

mdadm --examine --scan >> /etc/mdadm/mdadm.conf

To recreate the conf and see if it fixes the problem. /dev/md/0 should be a symbolic link to /dev/md0

DustinB3403

@Romo Same response when reexamining the disks. this is for both

mount /mnt/raid10 && mount /dev/md10

dafyre

mount /dev/md0 /mnt/raid10 ?

scottalanmiller

/dev/md0 not md10

scottalanmiller

Using RAID 10 in names anywhere is very confusing and hard to read. I think several of these issues are partially stemming just from poor naming conventions. Name mount points by purpose, not technology.

Romo

You can't mount /dev/md0, because according to the mdadm --examine --scan ouput, the array, is at /dev/md/0

StrongBad

@Romo said:

You can't mount /dev/md0, because according to the mdadm --examine --scan ouput, the array, is at /dev/md/0

Good eye, that was hard to see.

Romo

What is the ouput for:
cat /dev/md/md-device-map

DustinB3403

cat /dev/md/md-device-map
cat: /dev/md/md-device-map: No such file or directory