On Thu, 2012-08-09 at 17:04 +0200, Jos Vos wrote: > Hi, > > When trying to do a test install of F17 on server hardware (a dual > AMD Opteron system from 2006 with 1 GB of memory), I noticed several > issues, while CentOS 6.3 installs fine. So I want to share my > experiences, ask for your feedback, and then file bugs when needed. > > There are 3 major issues, at first sight unrelated. Everything is > fully reproducable (also the succeeding CentOS 6.3 install). > > (1) > The system has 3 NIC's, 2x Broadcom BCM5704 and 1x Netgear GA630. > I use a BCM5704 for network install. This works fine on CentOS with > ksdevice=link. With F17 I see multiple dhcp being started, resulting > in multiple timeouts (I even see a second dhcp being started for em2 > while just before the console says that em1 got a link), and only > after quite some time (a *long* time) the kickstart file is found > and the install continues. A wild shot in the dark, but not https://fedoraproject.org/wiki/Common_F17_bugs#ksdevice-case-sensitive ? I wrote that because we had one person who was using 'ksdevice=BOOTIF'... > (2) > The F17 installer can't start X and falls back to text mode, while > the CentOS installer works fine in graphical mode. The server has > a simple onboard VGA controller. This is what lspci says about the > graphics controller: > > VGA compatible controller: Advanced Micro Devices [AMD] nee ATI Rage XL (rev 27) > > In the X.log I see: > > [ 182.375] Backtrace: > [ 182.375] 0: Xorg (xorg_backtrace+0x36) [0x464d46] > [ 182.375] 1: Xorg (0x400000+0x69d99) [0x469d99] > [ 182.375] 2: /lib64/libpthread.so.0 (0x7f315a2bf000+0xefe0) [0x7f315a2cdfe0] > [ 182.375] 3: Xorg (UnloadSubModule+0xf) [0x475fbf] > [ 182.375] 4: /usr/lib64/xorg/modules/drivers/mach64_drv.so (0x7f3157146000+0x183c3) [0x7f315715e3c3] > [ 182.375] 5: Xorg (InitOutput+0x8ba) [0x4843ca] > [ 182.375] 6: Xorg (0x400000+0x23246) [0x423246] > [ 182.375] 7: /lib64/libc.so.6 (__libc_start_main+0xf5) [0x7f3158f46735] > [ 182.375] 8: Xorg (0x400000+0x236bd) [0x4236bd] > [ 182.375] > [ 182.375] Segmentation fault at address (nil) > [ 182.375] > Fatal server error: > [ 182.375] Caught signal 11 (Segmentation fault). Server aborting Looks like a fairly straightforward X driver crash, so leave that one to airlied...you might want to file a bug for it with relevant info from https://fedoraproject.org/wiki/How_to_debug_Xorg_problems . > (3) > > And finally there is a fatal error: it won't accept my kickstart file > and gives "reboot" as only option. The error is: > > Only RAID0 arrays can contain growable members > > The line it refers to in the kickstart file is this one: > > raid pv.02 --level=1 --device=md2 raid.03 raid.13 > > The complete context is: > > zerombr > clearpart --all --initlabel > ignoredisk --drives=sdc,sdd > > part raid.01 --size=500 --ondisk=sda --asprimary > part raid.02 --size=50000 --ondisk=sda --asprimary > part raid.03 --size=100 --ondisk=sda --asprimary --grow > part raid.04 --size=100 --ondisk=sda --asprimary --grow > > part raid.11 --size=500 --ondisk=sdb --asprimary > part raid.12 --size=50000 --ondisk=sdb --asprimary > part raid.13 --size=100 --ondisk=sdb --asprimary --grow > part raid.14 --size=100 --ondisk=sdb --asprimary --grow > > raid /boot --level=1 --device=md0 --fstype=ext4 raid.01 raid.11 > raid pv.01 --level=1 --device=md1 raid.02 raid.12 > raid pv.02 --level=1 --device=md2 raid.03 raid.13 > raid pv.03 --level=1 --device=md3 raid.04 raid.14 > > After this I define the volume groups and logical volumes in the > kickstart file. The same configuration works fine for RHEL6. > Did something change so that this is not valid anymore? Poking the relevant line in anaconda source with git blame gets me: commit 958c9ea170a3630124a32bc87bc68eeb6ed4cc7b Author: David Lehman <dlehman@xxxxxxxxxx> Date: Fri May 6 10:17:31 2011 -0500 Allow growable md member requests but only for RAID0. Related: rhbz#659700 Perhaps prior to that, the parameter was simply ignored, so in your CentOS install those partitions aren't actually growable? I'm not sure, though. dlehman can likely explain better. -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Twitter: AdamW_Fedora | identi.ca: adamwfedora http://www.happyassassin.net -- devel mailing list devel@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/devel
