On Mon Jul 13 02:19:31 UTC 2015 Chris Murphy typed:
So there's the kernel bug, 1225671, that ends up stopping the arrays, but then there's a misleading message saying there's a problem that's been corrected, yet clearly not corrected.
The exact wording of the message is: 'Unexpected system error. The system has encountered a problem and recovered.'
Does this same kernel call trace happen with Fedora 21's installer? Or does it fail for a different reason?
With the F21 installer, there is no error message, and the installer does find the raid1 array. But it finds it only as one ~ 460 GB 'physical volume'; my existing LVM partitions are not recognized, so I can't install into them.
There is a beta release criteria for this: Hardware and firmware RAID The installer must be able to detect and install to hardware or firmware RAID storage devices. And there are test cases, and there's an entry for software raid in the test matrix. So it should get tested multiple times per build, and there will be a dozen builds pre-alpha, pre-beta, and pre-final. So it's a bit surprising this is so easy to hit (the bug report has someone hitting it in virtual box). Obviously this can't be fixed with official media, you could roll your own workstation installer compose and instead use kernel 4.0.5 which should fix this bug, and then you'd be able to install F22 to this existing software raid. -- Chris Murphy
Alas, rolling my own workstation installer is beyond my present skill level. I must decide whether to wait for Fedora 23, or to back up everything and let the F22 installer have a crack at creating a new raid1 array with LVMs on top of it. Thanks again for the help, -jmw- -- users mailing list users@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
