F19 raid 1 stuck read only after reboot

[Alan Gagne]

> >/  # cat /proc/mdstat
> />/  Personalities : [raid0] [raid1]
> />/  md124 : active raid1 sdb[1] sdc[0]
> />/        293032960 blocks super external:/md125/0 [2/2] [UU]
> />/
> />/  md125 : inactive sdb[1](S) sdc[0](S)
> />/        6184 blocks super external:imsm
> />/
> />/  md126 : active raid0 sdd[1] sde[0]
> />/        156296192 blocks super external:/md127/0 128k chunks
> />/
> />/  md127 : inactive sde[1](S) sdd[0](S)
> />/        5032 blocks super external:imsm
> /
> Super something on external devices which are inactive?
They are all internal drives. That is the normal good state
for the arrays. After a reboot md124 would show auto-read-only
instead of active. When in that state I cannot mount the filesystem.
>
> I think I would try to make it so that the mdtools figure out what the
> arrays consist of automatically.  IIRC it is not necessary, maybe not
> even advisable, to specify explicitly in mdadm.conf what the arrays are
> made of because there is information stored on the disks that allow to
> build them automatically.
The mdadm.conf was built when F18 was installed.
Running mdadm --detail --scan returns the same info as what is in the
conf file. I checked that already to make sure there was not any 
differences.
>
> Is md124 a RAID-1 on top of a RAID-0?
Two separate arrays.

Thanks
Alan
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.fedoraproject.org/pipermail/users/attachments/20130718/a146d49f/attachment.html>