Am Samstag, 7. Januar 2012, 12:20:08 schrieb Jeff Cranmer:
> On Sat, 2012-01-07 at 10:11 -0500, Jeff Cranmer wrote:
> > > > > What am I missing?
> > > > 
> > > > have you set the type to linux raid autodetect?
> > > > 
> > > > have you tried mdadm --assemble?
> > > 
> > > mdadm --assemble /dev/md0 didn't make any difference.
> > > Where do I set the type?
> > 
> > after assembling,
> > results of cat/proc/mdstat
> > personalities : [linear] [raid0] [raid10] [raid6] [raid5] [raid4]
> > [multipath] [faulty]
> > md0 : inactive sdb1[0](S) sdd1[3](S) sdc1[1](S)
> > 
> >       4395409608 blocks super 1.2
> > 
> > unused devices: <none>
> > 
> > results of mdadm --detail /dev/md0
> > mdadm: md device /dev/md0 does not appear to be active.
> > 
> > results of /etc/init.d/mdadm status
> > 
> >  * status: started
> > 
> > fstab line
> > /dev/md0   /data   xfs   noatime   0 0
> > 
> > Is there a raid option I need to add to the fstab entry?
> > Is there another service that needs to run, other than mdam?
> > 
> > Thanks
> > 
> > Jeff
> 
> I tried changing the type of each array element in fdisk to fd (linux
> raid autodetect.
> 
> The array is still not being recognised at boot, with the same 'cannot
> read superblock' error.
> 
> I also tried re-running mdadm --create /dev/md0 --level=5
> --raid-devices=3 /dev/sdb1 /dev/sdc1 /dev/sdd1
> I get the error
> mdadm: device /dev/sdb1 not suitable for any style of array.
> 
> What is going on here?

I am thinking ;)


-- 
#163933

Reply via email to