Hi Drew, Please don't top-post. Repaired again. On 11/18/2012 12:39 PM, Drew Reusser wrote: > On Sun, Nov 18, 2012 at 5:01 PM, Phil Turmel <philip@xxxxxxxxxx> wrote: [trim /] >> This all looks like it should work. >> >> Please try "mdadm -v --assemble /dev/md0 /dev/sd[abde]1" and show the >> output. If it doesn't work, also show "cat /proc/mdstat" and "dmesg". > The issue is not that I cannot get the raid to create, it is that I > cannot access any of the files on the system when I mount it. It was > setup as an ext4 filesystem and it all was working and I rebooted and > it was not after that point. > > > mint mnt # mount -t ext4 /dev/md0 /mnt/raid > mount: wrong fs type, bad option, bad superblock on /dev/md0, > missing codepage or helper program, or other error > In some cases useful info is found in syslog - try > dmesg | tail or so > > mint dev # mdadm -v --assemble /dev/md0 /dev/sd[abde]1 > mdadm: looking for devices for /dev/md0 > mdadm: /dev/sda1 is identified as a member of /dev/md0, slot 0. > mdadm: /dev/sdb1 is identified as a member of /dev/md0, slot 1. > mdadm: /dev/sdd1 is identified as a member of /dev/md0, slot 2. > mdadm: /dev/sde1 is identified as a member of /dev/md0, slot 3. > mdadm: added /dev/sdb1 to /dev/md0 as 1 > mdadm: added /dev/sdd1 to /dev/md0 as 2 > mdadm: added /dev/sde1 to /dev/md0 as 3 > mdadm: added /dev/sda1 to /dev/md0 as 0 > mdadm: /dev/md0 has been started with 4 drives. > mint dev # cat /proc/mdstat > Personalities : [raid10] > md0 : active raid10 sda1[0] sde1[3] sdd1[2] sdb1[1] > 1952211968 blocks super 1.2 512K chunks 2 near-copies [4/4] [UUUU] > > unused devices: <none> Ok. So it's not a raid problem. You didn't show your dmesg. Phil -- To unsubscribe from this list: send the line "unsubscribe linux-raid" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
