RE: Broken RAID1 boot arrays

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



> > > What type of filesystem is it?
> > >
> > > Try "mount -v /dev/md1 /"
> >
> > 	It doesn't matter what switches I try, it always gives me that
> > error.  The md1 array (/boot) is ext2, and the md2 array (/) is ext3.
> 
> Is mdadm actually assembling the arrays?

	It says it is.  I was able to resync /dev/md3, and I can get the
details on all three arrays from mdadm.  If it weren't assembling them, then
it should return an error when I query for details.
 
> what's the output of: "cat /proc/mdstat"

/dev # cat /proc/mdstat
Personalities : [raid1] [raid6] [raid5] [raid4]
md3 : active raid1 hda3[2] hdb3[1]
      204796548 blocks super 1.2 [2/2] [UU]
      bitmap: 0/196 pages [0KB], 512KB chunk

md2 : active raid1 hda2[2] hdb2[1]
      277442414 blocks super 1.2 [2/2] [UU]
      bitmap: 0/265 pages [0KB], 512KB chunk

md1 : active raid1 hda1[2] hdb1[1]
      6144816 blocks super 1.0 [2/2] [UU]
      bitmap: 0/6 pages [0KB], 512KB chunk

unused devices: <none>

	Note that last response is untrue.  There are 8 drives belonging to
a RAID5 array that is not assembled.  I presume, however, it is basing that
response on the (nonexistent) mdadm.conf file.

--
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

[Index of Archives]     [Linux RAID Wiki]     [ATA RAID]     [Linux SCSI Target Infrastructure]     [Linux Block]     [Linux IDE]     [Linux SCSI]     [Linux Hams]     [Device Mapper]     [Device Mapper Cryptographics]     [Kernel]     [Linux Admin]     [Linux Net]     [GFS]     [RPM]     [git]     [Yosemite Forum]


  Powered by Linux