Rather than going into a well deserved rant about inadequate pre-release testing I'll go ahead and put forth my problem, not that I can put much information in here. The attachment limits preclude attaching the JPG screen dumps of the error logs.
So I have a pretty beefy SuperMicro dual CPU machine with 24GB of RAM and a SATA backplane that can handle 10 drives, four on an add-on card, and the other six on the motherboard IO channel. My previous installation of F17 had four of the drives configured as a raid-5 array, with a fifth drive as a "raw partitioned" system disk, and a hot-swap bay for backups and to do upgrades to a clean disk.
I downloaded the full F19 x86_64 DVD and set up my machine to boot my USB DVD drive, and swapped the boot order in BIOS so that the new blank system disk is the primary.
The install program bombs almost immediately after booting with a graphical "unkown error" message...and the buttons for "more info" and "report bug" are inactive. The kernel is still running, as I can switch to the log screen or to a shell. I cannot however attach my JPG screen dumps of those logs to this report.
I do see some messages about not being able to write some /tmp/anaconda???? to /mnt/sysimage/root though.
and a message about not being able to find /mnt/sysimage/etc/blkid/blkid.tab
and it says "teardown of 1 failed: mddeactivate failed for /dev/md/blackbox:1...presumably not able to deactivate my existing raid-5 array.
I have had soooo many problems with Fedora installations in recent years on machines where I've created disk manager raid arrays. I don't generally wrap the system disk but use raw partitions when installing, and reserve specific disks dedicated for software raid storage.
Anybody want to take a gander as to why the installation program bombs? or more importantly, what to do about it?
So I have a pretty beefy SuperMicro dual CPU machine with 24GB of RAM and a SATA backplane that can handle 10 drives, four on an add-on card, and the other six on the motherboard IO channel. My previous installation of F17 had four of the drives configured as a raid-5 array, with a fifth drive as a "raw partitioned" system disk, and a hot-swap bay for backups and to do upgrades to a clean disk.
I downloaded the full F19 x86_64 DVD and set up my machine to boot my USB DVD drive, and swapped the boot order in BIOS so that the new blank system disk is the primary.
The install program bombs almost immediately after booting with a graphical "unkown error" message...and the buttons for "more info" and "report bug" are inactive. The kernel is still running, as I can switch to the log screen or to a shell. I cannot however attach my JPG screen dumps of those logs to this report.
I do see some messages about not being able to write some /tmp/anaconda???? to /mnt/sysimage/root though.
and a message about not being able to find /mnt/sysimage/etc/blkid/blkid.tab
and it says "teardown of 1 failed: mddeactivate failed for /dev/md/blackbox:1...presumably not able to deactivate my existing raid-5 array.
I have had soooo many problems with Fedora installations in recent years on machines where I've created disk manager raid arrays. I don't generally wrap the system disk but use raw partitions when installing, and reserve specific disks dedicated for software raid storage.
Anybody want to take a gander as to why the installation program bombs? or more importantly, what to do about it?