>> >/  # 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.

You mean the whole array md124 goes read-only?  
Yes, the entire array.
Or are the partitions on
it mounted ro? 
Unable to mount any partitions when the array is in auto-read-ony state.
 Why do you need to rewrite the partition tables?
Well that the jist of this post. F19 fails to detect something needed for the array
to work properly. Rewriting the partition table just gets things working again.

How do you know when any of the physical disks go bad?
Hopefully smart will pick-up id there is a disk problem.
So far it reports no errors for either disk member of the array.

Thanks
Alan