RAID 5 array. 2 arrays (/) and (/home) - asks about this

Question

Hello pals. On wiki, we'have that it's necessary create the array with mdadm, after assemble, and after installs arch like anyother disk system, just add while in chroot "mdadm_udev" and run "mkinitcpio -p linux"
My question, however, is:
In a first try, I don't know if I did the mistake, but my /home partition were mounted, with, the root partition. So "not enough space".
I've reinstalled all again, Everithing working since, but yesterday, arch halts and, after reboot, I "lost" my /home, and not "md0" and "md1" devices, but "md126" and "md127" ones are founded on my arrays, and, no more linux.
fsck didn't work (not found the uuid XXXX partition"
I'm using a RAID5 scheme with "md0" as /root and "md1" as /home. md0 with 3 hard disks and md1 with three too.
RAID is a LSICorp with 21320R 6 bay. HD SCSI
partition type were XFS to "root" and "ext4" to /home.
Begginer's guide to install, and
https://wiki.archlinux.org/index.php/RAID
to create RAID

Answer 1

Ok... everything reinstaled.
sdc                                                                       
└─sdc1  linux_raid_member archiso:0   5a556144-7cad-36e1-b969-300e33e42055
  └─md0 xfs               root        3cd56eab-5747-4468-92e0-d53baf0d5544 /
sdd                                                                       
└─sdd1  linux_raid_member archiso:0   5a556144-7cad-36e1-b969-300e33e42055
  └─md0 xfs               root        3cd56eab-5747-4468-92e0-d53baf0d5544 /
sde                                                                       
└─sde1  linux_raid_member archiso:0   5a556144-7cad-36e1-b969-300e33e42055
  └─md0 xfs               root        3cd56eab-5747-4468-92e0-d53baf0d5544 /
sdf                                                                       
└─sdf1  linux_raid_member archiso:1   d27f91fb-ed92-12a7-340c-11b8636d491f
  └─md1 ext4              home        6cb919d4-9016-4a7b-8336-01a1244a0630 /home
sdg                                                                       
└─sdg1  linux_raid_member archiso:1   d27f91fb-ed92-12a7-340c-11b8636d491f
  └─md1 ext4              home        6cb919d4-9016-4a7b-8336-01a1244a0630 /home
sdh                                                                       
└─sdh1  linux_raid_member archiso:1   d27f91fb-ed92-12a7-340c-11b8636d491f
  └─md1 ext4              home        6cb919d4-9016-4a7b-8336-01a1244a0630 /home
cat /proc/mdstat
cat /proc/mdstat
Personalities : [raid6] [raid5] [raid4]
md1 : active raid5 sdh1[3] sdg1[1] sdf1[0]
      142884864 blocks super 1.2 level 5, 64k chunk, algorithm 2 [3/3] [UUU]
md0 : active raid5 sde1[3] sdc1[0] sdd1[1]
      70778880 blocks super 1.2 level 5, 64k chunk, algorithm 2 [3/3] [UUU]
/etc/fstab
# /etc/fstab: static file system information
# <file system> <dir>   <type>  <options>       <dump>  <pass>
# /dev/md0 LABEL=root
UUID=3cd56eab-5747-4468-92e0-d53baf0d5544       /               xfs             rw,relatime,attr2,inode64,logbsize=64k,sunit=128,swidth=256,noquota  0 1
# /dev/md1 LABEL=home
UUID=6cb919d4-9016-4a7b-8336-01a1244a0630       /home           ext4            rw,relatime,stripe=192,data=ordered  0 2
Anything to change?
I remember that the ~last problem~ were during a upgrade.