Having an odd problem with my raid 1 array after upgrade to F19. Upgraded using fedup from 18 to 19. Did not have any problems with the upgrade itself but since my raid 1 array is stuck read only after each reboot.
This is a bios intel raid set-up I have been using for a little over three years. So I know it has been quite stable.
The os is installed on the raid 0 array. I use the raid 1 for things I would rather not lose.
I have to re-write out the partition table using fdisk after each reboot to get the array to go active.
https://bugzilla.redhat.com/show_bug.cgi?id=985638
cat /etc/mdadm.conf # mdadm.conf MAILADDR root AUTO +imsm +1.x -all ARRAY /dev/md/imsm1 metadata=imsm UUID=c740a986:078365cb:f43671d1:e459c34b ARRAY /dev/md/imsm0 metadata=imsm UUID=a28154cd:08577e7a:8ef68be8:34e15a4b ARRAY /dev/md/Volume2 container=/dev/md/imsm1 member=0 UUID=f9dc1dab:feebb78c:b196dcc5:6d6ba98d ARRAY /dev/md/Volume1_0 container=/dev/md/imsm0 member=0 UUID=79b75950:70d29fd6:e69a64d6:89b23747
# 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
# fdisk -l /dev/md124
Disk /dev/md124: 300.1 GB, 300065751040 bytes, 586065920 sectors Units = sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk label type: dos Disk identifier: 0x000de834
Device Boot Start End Blocks Id System /dev/md124p1 2048 419432447 209715200 7 HPFS/NTFS/exFAT /dev/md124p2 419432448 503318527 41943040 7 HPFS/NTFS/exFAT /dev/md124p3 503318528 586065919 41373696 8e Linux LVM
# fdisk -l /dev/md126
Disk /dev/md126: 160.0 GB, 160047300608 bytes, 312592384 sectors Units = sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 131072 bytes / 262144 bytes Disk label type: dos Disk identifier: 0x3198d489
Device Boot Start End Blocks Id System /dev/md126p1 * 2048 156297215 78147584 7 HPFS/NTFS/exFAT /dev/md126p2 156297216 157321215 512000 83 Linux /dev/md126p3 157321216 312592383 77635584 8e Linux LVM
On Jul 18 11:45, Alan Gagne wrote:
Having an odd problem with my raid 1 array after upgrade to F19. Upgraded using fedup from 18 to 19. Did not have any problems with the upgrade itself but since my raid 1 array is stuck read only after each reboot.
This is a bios intel raid set-up I have been using for a little over three years. So I know it has been quite stable.
The os is installed on the raid 0 array. I use the raid 1 for things I would rather not lose.
I have to re-write out the partition table using fdisk after each reboot to get the array to go active.
Is that the journal option problem, maybe? See the last three entries from http://forums.fedoraforum.org/archive/index.php/t-287286.html
I encountered the same problem when upgrading one of my machines from F18 to F19. No idea why it worked before.
Corinna
Alan Gagne alanjgagne@gmail.com writes:
# 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?
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.
Is md124 a RAID-1 on top of a RAID-0?