From oguzyilmazlist at gmail.com Sun Aug 4 20:39:37 2013 From: oguzyilmazlist at gmail.com (Oguz Yilmaz) Date: Sun, 4 Aug 2013 23:39:37 +0300 Subject: Problem with finding kickstart file from the cdrom Message-ID: Hello, I was using a kickstart distro with kernel 2.6.18. Recently I have decided to change this distro cd to use kernel 3.4.52. I have prepared all new rpm files and produced iso. I am testing the iso file on proxmox environment with qemu. With tha same guest vm the oldu distro succfully boots and find kickstart file and installs. With the new iso I have problems. "unable to find the kickstart file...." cdrom:/isolinux/ssd.cfg In tty3 I can follow: [ 1.620980] sd 0:0:0:0: Attached scsi generic sg0 type 0 [ 1.621253] sd 0:0:0:0: [sda] 33554432 512-byte logical blocks: (17.1 GB/16.0 GiB) [ 1.621359] sd 0:0:0:0: [sda] Write Protect is off [ 1.621401] sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA [ 1.628975] scsi 6:0:1:0: CD-ROM QEMU QEMU DVD-ROM 1.4. PQ: 0 ANSI: 5 [ 1.628978] sda: sda1 sda2 sda3 sda4 < sda5 > [ 1.629546] sd 0:0:0:0: [sda] Attached SCSI disk [ 1.630073] usb 1-1: new full-speed USB device number 2 using uhci_hcd [ 1.634874] sr0: scsi3-mmc drive: 4x/4x cd/rw xa/form2 tray [ 1.636220] cdrom: Uniform CD-ROM driver Revision: 3.20 When I add loglovel-debug in to anaconda boot cmdline I can see error log. ERROR: No CDROM devices found! I have also checked the previous iso file. It was correctly recognizing cdrom as hdb while problematic new kernel iso recognizes it as sr0 device. hdb: QEMU DVD-ROM, ATAPI CD/DVD-ROM drive ide0 at 0x1f0-0x1f7,0x3f6 on irq 14 mntloop loop0 on /mnt/runtime as .... got url from cdrom://hdb:/mnt/source If I write ks url as "hd:scd0:/isolinux/ssd.cfg" then anaconda mounts and reads the ks file. getting kickstart file from harddrive Loading ks from device scd0 on path /isolinux/ssd.cfg ... file copied to /tmp/ks.cfg However ks.cfg includes "install" and "cdrom" lines. Then it againg tries to find Cdrom and gives error. This problem occurs in stage1 and this stage does not enable tty2 debug shell and sshd options. So I have limited debug options. Anaconda version is 11.1.2.168 , kernel version 3.4.52. What do you suggest on the problem? Oguz -------------- next part -------------- An HTML attachment was scrubbed... URL: From oguzyilmazlist at gmail.com Mon Aug 5 06:57:29 2013 From: oguzyilmazlist at gmail.com (Oguz Yilmaz) Date: Mon, 5 Aug 2013 09:57:29 +0300 Subject: Problem with finding kickstart file from the cdrom In-Reply-To: References: Message-ID: I have tried in physical hardware and physical cdrom. The problem is the same with physical machines. -- Oguz YILMAZ On Sun, Aug 4, 2013 at 11:39 PM, Oguz Yilmaz wrote: > Hello, > > I was using a kickstart distro with kernel 2.6.18. Recently I have decided > to change this distro cd to use kernel 3.4.52. I have prepared all new rpm > files and produced iso. > > I am testing the iso file on proxmox environment with qemu. With tha same > guest vm the oldu distro succfully boots and find kickstart file and > installs. With the new iso I have problems. > > "unable to find the kickstart file...." > cdrom:/isolinux/ssd.cfg > > In tty3 I can follow: > [ 1.620980] sd 0:0:0:0: Attached scsi generic sg0 type 0 > [ 1.621253] sd 0:0:0:0: [sda] 33554432 512-byte logical blocks: (17.1 > GB/16.0 GiB) > [ 1.621359] sd 0:0:0:0: [sda] Write Protect is off > [ 1.621401] sd 0:0:0:0: [sda] Write cache: enabled, read cache: > enabled, doesn't support DPO or FUA > [ 1.628975] scsi 6:0:1:0: CD-ROM QEMU QEMU DVD-ROM > 1.4. PQ: 0 ANSI: 5 > [ 1.628978] sda: sda1 sda2 sda3 sda4 < sda5 > > [ 1.629546] sd 0:0:0:0: [sda] Attached SCSI disk > [ 1.630073] usb 1-1: new full-speed USB device number 2 using uhci_hcd > [ 1.634874] sr0: scsi3-mmc drive: 4x/4x cd/rw xa/form2 tray > [ 1.636220] cdrom: Uniform CD-ROM driver Revision: 3.20 > > When I add loglovel-debug in to anaconda boot cmdline I can see error log. > > ERROR: No CDROM devices found! > > > I have also checked the previous iso file. It was correctly recognizing > cdrom as hdb while problematic new kernel iso recognizes it as sr0 device. > > hdb: QEMU DVD-ROM, ATAPI CD/DVD-ROM drive > > ide0 at 0x1f0-0x1f7,0x3f6 on irq 14 > > mntloop loop0 on /mnt/runtime as .... > > got url from cdrom://hdb:/mnt/source > > > If I write ks url as "hd:scd0:/isolinux/ssd.cfg" then anaconda mounts and > reads the ks file. > > > getting kickstart file from harddrive > > Loading ks from device scd0 on path /isolinux/ssd.cfg > > ... > > file copied to /tmp/ks.cfg > > > However ks.cfg includes "install" and "cdrom" lines. Then it againg tries > to find Cdrom and gives error. > > > This problem occurs in stage1 and this stage does not enable tty2 debug > shell and sshd options. So I have limited debug options. > > > Anaconda version is 11.1.2.168 , kernel version 3.4.52. > > > What do you suggest on the problem? > > > Oguz > -------------- next part -------------- An HTML attachment was scrubbed... URL: From jos at xos.nl Mon Aug 5 08:17:02 2013 From: jos at xos.nl (Jos Vos) Date: Mon, 5 Aug 2013 10:17:02 +0200 Subject: Problem with finding kickstart file from the cdrom In-Reply-To: References: Message-ID: <20130805081702.GA20643@jasmine.xos.nl> On Sun, Aug 04, 2013 at 11:39:37PM +0300, Oguz Yilmaz wrote: > "unable to find the kickstart file...." > cdrom:/isolinux/ssd.cfg [...] > If I write ks url as "hd:scd0:/isolinux/ssd.cfg" then anaconda mounts and > reads the ks file. Did you try: ks=cdrom:/dev/sr0:/ks/ks-install.cfg This at least works for Fedora 18 (and "cdrom" in kickstart file). But from what you wrote, I guess this won't work either. -- -- Jos Vos -- X/OS Experts in Open Systems BV | Phone: +31 20 6938364 -- Amsterdam, The Netherlands | Fax: +31 20 6948204 From oguzyilmazlist at gmail.com Mon Aug 5 08:59:12 2013 From: oguzyilmazlist at gmail.com (Oguz Yilmaz) Date: Mon, 5 Aug 2013 11:59:12 +0300 Subject: Problem with finding kickstart file from the cdrom In-Reply-To: <20130805081702.GA20643@jasmine.xos.nl> References: <20130805081702.GA20643@jasmine.xos.nl> Message-ID: Yes, but did NOT worked, also. -- Oguz YILMAZ On Mon, Aug 5, 2013 at 11:17 AM, Jos Vos wrote: > On Sun, Aug 04, 2013 at 11:39:37PM +0300, Oguz Yilmaz wrote: > > > "unable to find the kickstart file...." > > cdrom:/isolinux/ssd.cfg > > [...] > > > If I write ks url as "hd:scd0:/isolinux/ssd.cfg" then anaconda mounts and > > reads the ks file. > > Did you try: > > ks=cdrom:/dev/sr0:/ks/ks-install.cfg > > This at least works for Fedora 18 (and "cdrom" in kickstart file). > But from what you wrote, I guess this won't work either. > > -- > -- Jos Vos > -- X/OS Experts in Open Systems BV | Phone: +31 20 6938364 > -- Amsterdam, The Netherlands | Fax: +31 20 6948204 > > _______________________________________________ > Kickstart-list mailing list > Kickstart-list at redhat.com > https://www.redhat.com/mailman/listinfo/kickstart-list > -------------- next part -------------- An HTML attachment was scrubbed... URL: From hhoffman at ip-solutions.net Sun Aug 11 15:06:45 2013 From: hhoffman at ip-solutions.net (Harry Hoffman) Date: Sun, 11 Aug 2013 11:06:45 -0400 Subject: Anaconda 13.21.195 mistakenly creating two physical volume groups Message-ID: <5207A885.8070703@ip-solutions.net> Hi All, I'm attempting to do a install of CentOS 6.4 and anaconda is doing some weird things with my partitions. It's creating my volume group and a test_vg volume group too. I'm running the install through cobbler 2.4.0-1 (latest version) and the system being installed is a kvm guest with a 8GB disk. Both are x86_64 arch. Here's the partitioning I'm requesting via the kickstart: # Partition clearing information zerombr clearpart --all --initlabel partition /boot --fstype ext4 --size=512 --asprimary partition pv.2 --grow --size=1 --asprimary volgroup OS_VOL --pesize=4096 pv.2 logvol / --fstype ext4 --name=lv_root --vgname=OS_VOL --size=1024 logvol swap --name=lvSwap --vgname=OS_VOL --size=512 logvol /var --fstype ext4 --name=lv_var --vgname=OS_VOL --size=1024 logvol /var/log --fstype ext4 --name=lv_var_log --vgname=OS_VOL --size=1024 logvol /var/log/audit --fstype ext4 --name=lv_audit --vgname=OS_VOL --size=512 logvol /home --fstype ext4 --name=lv_home --vgname=OS_VOL --size=1024 logvol /tmp --fstype ext4 --name=lv_tmp --vgname=OS_VOL --size=768 Anaconda is reporting errors about there not being enough space for the requested partitions. When I switch to vc 2 and run pvdisplay I see *two* physical volume groups! LV Creation host, time test.ip-solutions.net, 2013-08-11 14:47:39 -0400 [anaconda root at test /]# pvdisplay --- Physical volume --- PV Name /dev/sda4 VG Name OS_VOL PV Size 3.50 GiB / not usable 0 Allocatable yes(but full) PE Size 4.00 MiB Total PE 897 Free PE 0 Allocated PE 897 PV UUID RAltM1-9ApR-HEi2-lwUF-dY8j-iA34-1pG5gx --- Physical volume --- PV Name /dev/sda4 VG Name vg_test PV Size 3.50 GiB / not usable 0 Allocatable yes(but full) PE Size 4.00 MiB Total PE 897 Free PE 0 Allocated PE 897 PV UUID D2XcwM-wYb3-8QW1-egKt-rrZN-WSXB-1Gc8BI Has anyone seen this before? Cheers, Harry From gnetravali at sonusnet.com Wed Aug 14 05:45:19 2013 From: gnetravali at sonusnet.com (Netravali, Ganesh) Date: Wed, 14 Aug 2013 05:45:19 +0000 Subject: Removing unwanted packages with dependencies Message-ID: <1BAFEA29B37FDF429C31C4B2588ADF6BE7B3@inba-mail01.sonusnet.com> Hi In the kickstart to avoid some of the package installation I am using - option under %packages section. If rpm has got some of the dependency packages, kickstart is not able to remove the package. Is there any option to remove the package along with dependency during kickstart? Presently I am using "yum remove -y to remove the package with dependencies as part of %post section. Thanks Ganesh -------------- next part -------------- An HTML attachment was scrubbed... URL: From Jiaqiang.a.Zhang at alcatel-sbell.com.cn Fri Aug 16 07:52:25 2013 From: Jiaqiang.a.Zhang at alcatel-sbell.com.cn (ZHANG Jiaqiang A) Date: Fri, 16 Aug 2013 07:52:25 +0000 Subject: how to create lvm partion by kickstart Message-ID: <22DF64FBB39B5741B47434ECB9151B0C37C30EC3@CNSHJMBX04.ad4.ad.alcatel.com> Hi All, I try to use kickstart to install server and set disk layout by lvm. But there is error when I execute the pvs after installation. Maybe there is something wrong with my ks files ? But I am not sure where. If there is anyone can give me any suggestion ? Couldn't find device with uuid GmxJ6H-uM3f-AQrp-Hmh7-h0Zt-WfP8-mLaI3M. Couldn't find device with uuid AcBVR7-iF01-ujlx-C4L8-mfr6-R7pg-j1eBe6. Couldn't find device with uuid Ph6vrv-k2AP-Hnpc-lrEM-5SkJ-Whsl-8e1Ivm. PV VG Fmt Attr PSize PFree /dev/cciss/c0d2p1 vg_data lvm2 a-- 1.36T 0 /dev/md1 vg_sys lvm2 a-- 119.97G 0 /dev/md2 vg_app lvm2 a-- 159.16G 0 /dev/sda1 VolGroup00 lvm2 a-- 3.72G 0 unknown device VolGroup00 lvm2 a-m 279.34G 0 unknown device VolGroup00 lvm2 a-m 1.36T 0 unknown device VolGroup00 lvm2 a-m 279.25G 0 Here is the ks snippet I used to setup lvm: #################################################################### # LD0 300G # LD1 300G # LD2 1.39T clearpart --drives=$LD0,$LD1,$LD2 --all --initlabel #------------------------------------------------------------------------# #-------------------------------------------------------------------------# # /boot # /, /usr, /var, swap # /opt, /home part raid.00 --size 204 --ondrive=$LD0 --asprimary part raid.10 --size 204 --ondrive=$LD1 --asprimary part raid.01 --size 122880 --ondrive=$LD0 --asprimary part raid.11 --size 122880 --ondrive=$LD1 --asprimary part raid.02 --size 1 --grow --ondrive=$LD0 part raid.12 --size 1 --grow --ondrive=$LD1 part pv.10 --size=1 --grow --ondisk=$LD2 raid /boot --fstype ext3 --device md0 --level=RAID1 raid.00 raid.10 raid pv.1 --fstype ext4 --device md1 --level=RAID1 raid.01 raid.11 raid pv.2 --fstype ext4 --device md2 --level=RAID1 raid.02 raid.12 volgroup vg_sys pv.1 volgroup vg_app pv.2 volgroup vg_data pv.10 logvol / --vgname=vg_sys --size=52428 --name=lv_root logvol swap --vgname=vg_sys --size=$SWAP_SIZE --name=lv_swap logvol /usr --vgname=vg_sys --size=10240 --name=lv_usr logvol /var --vgname=vg_sys --size=1 --grow --name=lv_var logvol /opt --vgname=vg_app --size=52428 --name=lv_opt logvol /home --vgname=vg_app --size=1 --grow --name=lv_home logvol /data --vgname=vg_data --size=1 --grow --name=lv_data #################################################################### -------------- next part -------------- An HTML attachment was scrubbed... URL: From Tim.Mooney at ndsu.edu Fri Aug 16 19:43:15 2013 From: Tim.Mooney at ndsu.edu (Tim Mooney) Date: Fri, 16 Aug 2013 14:43:15 -0500 (CDT) Subject: how to create lvm partion by kickstart In-Reply-To: <22DF64FBB39B5741B47434ECB9151B0C37C30EC3@CNSHJMBX04.ad4.ad.alcatel.com> References: <22DF64FBB39B5741B47434ECB9151B0C37C30EC3@CNSHJMBX04.ad4.ad.alcatel.com> Message-ID: In regard to: how to create lvm partion by kickstart, ZHANG Jiaqiang A said...: > Here is the ks snippet I used to setup lvm: > > #################################################################### > # LD0 300G > # LD1 300G > # LD2 1.39T > clearpart --drives=$LD0,$LD1,$LD2 --all --initlabel > #------------------------------------------------------------------------# > #-------------------------------------------------------------------------# > # /boot > # /, /usr, /var, swap > # /opt, /home > > part raid.00 --size 204 --ondrive=$LD0 --asprimary > part raid.10 --size 204 --ondrive=$LD1 --asprimary > part raid.01 --size 122880 --ondrive=$LD0 --asprimary > part raid.11 --size 122880 --ondrive=$LD1 --asprimary > part raid.02 --size 1 --grow --ondrive=$LD0 > part raid.12 --size 1 --grow --ondrive=$LD1 > > part pv.10 --size=1 --grow --ondisk=$LD2 Are you certain that LD0, LD1 and LD2 are being set correctly before partitioning happens? > raid /boot --fstype ext3 --device md0 --level=RAID1 raid.00 raid.10 > raid pv.1 --fstype ext4 --device md1 --level=RAID1 raid.01 raid.11 > raid pv.2 --fstype ext4 --device md2 --level=RAID1 raid.02 raid.12 If you want pv.1 and pv.2 to be LVM, why are you setting --fstype ext4? Our kickstart uses: raid pv.01 --fstype "physical volume (LVM)" --level=RAID1 --device=md3 raid.13 raid.23 Tim -- Tim Mooney Tim.Mooney at ndsu.edu Enterprise Computing & Infrastructure 701-231-1076 (Voice) Room 242-J6, IACC Building 701-231-8541 (Fax) North Dakota State University, Fargo, ND 58105-5164 From vpodzime at redhat.com Tue Aug 20 14:56:49 2013 From: vpodzime at redhat.com (Vratislav Podzimek) Date: Tue, 20 Aug 2013 16:56:49 +0200 Subject: Configure NTP during Kickstart (Dean Hunter) In-Reply-To: <51E41F3D.1020401@cadence.com> References: <51E41F3D.1020401@cadence.com> Message-ID: <1377010609.24792.5.camel@vpodzime.anaconda.englab.brq.redhat.com> On Mon, 2013-07-15 at 17:11 +0100, Steve Robson wrote: > kickstart-list-request at redhat.com wrote: > > > > I can not get the Kickstart commands correct to configure and enable > > ntpd instead of chronyd. Here is my script for use with Fedora 19: > > You probably need to copy in a suitable ntp.conf during your %post. And > perhaps disable chronyd (I'm not familiar with what that is, sorry) Yeah, we really just write out configuration file for the chronyd and make the service enabled. So you'd need to copy the configuration somehow and you may try to add '-chrony' to the %packages section. That should prevent chronyd from being installed and systemd should pick up the right NTP service automatically. Or at least as far as the theory goes... -- Vratislav Podzimek Anaconda Rider | Red Hat, Inc. | Brno - Czech Republic From anders.blomdell at control.lth.se Thu Aug 22 18:05:19 2013 From: anders.blomdell at control.lth.se (Anders Blomdell) Date: Thu, 22 Aug 2013 20:05:19 +0200 Subject: What is the correct way to reuse an existing RAID/LVM configuration Message-ID: <521652DF.7070003@control.lth.se> On a system with the following disk layout: Disk /dev/sda: 2000.4 GB, 2000398934016 bytes, 3907029168 sectors Units = sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 4096 bytes Disk label type: dos Disk identifier: 0x83dae9c4 Device Boot Start End Blocks Id System /dev/sda4 2048 3907029167 1953513560 5 Extended /dev/sda5 4096 4198399 2097152 fd Linux raid autodetect /dev/sda6 4200448 3907029167 1951414360 fd Linux raid autodetect Disk /dev/sdb: 2000.4 GB, 2000398934016 bytes, 3907029168 sectors Units = sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 4096 bytes Disk label type: dos Disk identifier: 0x88b817cf Device Boot Start End Blocks Id System /dev/sdb4 2048 3907029167 1953513560 5 Extended /dev/sdb5 4096 4198399 2097152 fd Linux raid autodetect /dev/sdb6 4200448 3907029167 1951414360 fd Linux raid autodetect PV VG Fmt Attr PSize PFree /dev/md1 vg0 lvm2 a-- 1.82t 1.63t LV VG Attr LSize Pool Origin Data% Move Log Copy% Convert opt vg0 -wi-a---- 60.00g root vg0 -wi-a---- 60.00g src vg0 -wi-d---- 60.00g swap vg0 -wi-a---- 16.00g I'm trying to kickstart a Fedora-19 system with the following partitioning: part raid.0a --onpart=sda5 --noformat part raid.0b --onpart=sdb5 --noformat raid /boot --fstype=ext4 --level=1 --device=md0 raid.0a raid.0b part raid.1a --onpart=sda6 --noformat part raid.1b --onpart=sdb6 --noformat raid pv.0 --level=1 --device=md1 raid.1a raid.1b volgroup vg0 --noformat pv.0 logvol / --vgname=vg0 --useexisting --name=root --fstype=ext4 logvol swap --vgname=vg0 --useexisting --name=swap logvol /opt --vgname=vg0 --useexisting --name=opt --fstype=ext4 But it fails miserably with: Traceback (most recent call first): File "/usr/lib/python2.7/site-packages/blivet/devices.py", line 789, in create raise DeviceCreateError(str(e), self.name) File "/usr/lib/python2.7/site-packages/blivet/deviceaction.py", line 272, in execute self.device.create() File "/usr/lib/python2.7/site-packages/blivet/devicetree.py", line 237, in processActions action.execute() File "/usr/lib/python2.7/site-packages/blivet/__init__.py", line 310, in doIt self.devicetree.processActions() File "/usr/lib/python2.7/site-packages/blivet/__init__.py", line 169, in turnOnFilesystems storage.doIt() File "/usr/lib64/python2.7/site-packages/pyanaconda/install.py", line 140, in doInstall turnOnFilesystems(storage, mountOnly=flags.flags.dirInstall) File "/usr/lib64/python2.7/threading.py", line 764, in run self.__target(*self.__args, **self.__kwargs) File "/usr/lib64/python2.7/site-packages/pyanaconda/threads.py", line 168, in run threading.Thread.run(self, *args, **kwargs) DeviceCreateError: ('mdcreate failed for /dev/md/1: running mdadm --create /dev/md/1 --run --level=1 --raid-devices=2 --metadata=default --bitmap=internal /dev/sda6 /dev/sdb6 failed', '1') Any help is appreciated. /Anders -- Anders Blomdell Email: anders.blomdell at control.lth.se Department of Automatic Control Lund University Phone: +46 46 222 4625 P.O. Box 118 Fax: +46 46 138118 SE-221 00 Lund, Sweden From anders.blomdell at control.lth.se Fri Aug 23 12:08:51 2013 From: anders.blomdell at control.lth.se (Anders Blomdell) Date: Fri, 23 Aug 2013 14:08:51 +0200 Subject: What is the correct way to reuse an existing RAID/LVM configuration In-Reply-To: <521652DF.7070003@control.lth.se> References: <521652DF.7070003@control.lth.se> Message-ID: <521750D3.1000502@control.lth.se> On 2013-08-22 20:05, Anders Blomdell wrote: > On a system with the following disk layout: > > > Disk /dev/sda: 2000.4 GB, 2000398934016 bytes, 3907029168 sectors > Units = sectors of 1 * 512 = 512 bytes > Sector size (logical/physical): 512 bytes / 4096 bytes > I/O size (minimum/optimal): 4096 bytes / 4096 bytes > Disk label type: dos > Disk identifier: 0x83dae9c4 > > Device Boot Start End Blocks Id System > /dev/sda4 2048 3907029167 1953513560 5 Extended > /dev/sda5 4096 4198399 2097152 fd Linux raid autodetect > /dev/sda6 4200448 3907029167 1951414360 fd Linux raid autodetect > > Disk /dev/sdb: 2000.4 GB, 2000398934016 bytes, 3907029168 sectors > Units = sectors of 1 * 512 = 512 bytes > Sector size (logical/physical): 512 bytes / 4096 bytes > I/O size (minimum/optimal): 4096 bytes / 4096 bytes > Disk label type: dos > Disk identifier: 0x88b817cf > > Device Boot Start End Blocks Id System > /dev/sdb4 2048 3907029167 1953513560 5 Extended > /dev/sdb5 4096 4198399 2097152 fd Linux raid autodetect > /dev/sdb6 4200448 3907029167 1951414360 fd Linux raid autodetect > PV VG Fmt Attr PSize PFree > /dev/md1 vg0 lvm2 a-- 1.82t 1.63t > > LV VG Attr LSize Pool Origin Data% Move Log Copy% Convert > opt vg0 -wi-a---- 60.00g > root vg0 -wi-a---- 60.00g > src vg0 -wi-d---- 60.00g > swap vg0 -wi-a---- 16.00g > > I'm trying to kickstart a Fedora-19 system with the following partitioning: > > part raid.0a --onpart=sda5 --noformat > part raid.0b --onpart=sdb5 --noformat > raid /boot --fstype=ext4 --level=1 --device=md0 raid.0a raid.0b > > part raid.1a --onpart=sda6 --noformat > part raid.1b --onpart=sdb6 --noformat > raid pv.0 --level=1 --device=md1 raid.1a raid.1b > > volgroup vg0 --noformat pv.0 > logvol / --vgname=vg0 --useexisting --name=root --fstype=ext4 > logvol swap --vgname=vg0 --useexisting --name=swap > logvol /opt --vgname=vg0 --useexisting --name=opt --fstype=ext4 Using the partitioning info returned in anaconda-ks.cfg from a manual install on the same disk: part raid.8 --fstype="mdmember" --noformat --onpart=sdb5 part raid.2 --fstype="mdmember" --noformat --onpart=sda5 part raid.9 --fstype="mdmember" --noformat --onpart=sdb6 part raid.4 --fstype="mdmember" --noformat --onpart=sda6 raid /boot --device=nieman:0 --fstype="ext4" --level=1 --useexisting --label=boot raid.2 raid.8 raid pv.5 --device=nieman:1 --fstype="lvmpv" --level=1 --noformat --useexisting raid.4 raid.9 volgroup vg0 --noformat --pesize=32768 --useexisting pv.5 logvol /opt --fstype="ext4" --useexisting --label="opt" --name=opt --vgname=vg0 logvol / --fstype="ext4" --useexisting --label="root" --name=root --vgname=vg0 logvol /usr/src --fstype="ext4" --noformat --useexisting --label="/usr/src" --name=src --vgname=vg0 logvol swap --fstype="swap" --useexisting --name=swap --vgname=vg0 Fails with: Members may not be specified for preexisting RAID device > > > But it fails miserably with: > > > Traceback (most recent call first): > File "/usr/lib/python2.7/site-packages/blivet/devices.py", line 789, in create > raise DeviceCreateError(str(e), self.name) > File "/usr/lib/python2.7/site-packages/blivet/deviceaction.py", line 272, in execute > self.device.create() > File "/usr/lib/python2.7/site-packages/blivet/devicetree.py", line 237, in processActions > action.execute() > File "/usr/lib/python2.7/site-packages/blivet/__init__.py", line 310, in doIt > self.devicetree.processActions() > File "/usr/lib/python2.7/site-packages/blivet/__init__.py", line 169, in turnOnFilesystems > storage.doIt() > File "/usr/lib64/python2.7/site-packages/pyanaconda/install.py", line 140, in doInstall > turnOnFilesystems(storage, mountOnly=flags.flags.dirInstall) > File "/usr/lib64/python2.7/threading.py", line 764, in run > self.__target(*self.__args, **self.__kwargs) > File "/usr/lib64/python2.7/site-packages/pyanaconda/threads.py", line 168, in run > threading.Thread.run(self, *args, **kwargs) > DeviceCreateError: ('mdcreate failed for /dev/md/1: running mdadm --create /dev/md/1 --run --level=1 --raid-devices=2 --metadata=default --bitmap=internal /dev/sda6 /dev/sdb6 failed', '1') > > > Any help is appreciated. > > /Anders -- Anders Blomdell Email: anders.blomdell at control.lth.se Department of Automatic Control Lund University Phone: +46 46 222 4625 P.O. Box 118 Fax: +46 46 138118 SE-221 00 Lund, Sweden From oguzyilmazlist at gmail.com Fri Aug 23 13:13:23 2013 From: oguzyilmazlist at gmail.com (Oguz Yilmaz) Date: Fri, 23 Aug 2013 16:13:23 +0300 Subject: Problem with finding kickstart file from the cdrom In-Reply-To: References: <20130805081702.GA20643@jasmine.xos.nl> Message-ID: For this issue, I have added another kernel and configured anaconda to use this older 2.6.18 kernel during installation. This anaconda running on 2.6.18 has installed 3.x kernel correctly. Thanks. -- Oguz YILMAZ On Mon, Aug 5, 2013 at 11:59 AM, Oguz Yilmaz wrote: > Yes, but did NOT worked, also. > > > > > -- > Oguz YILMAZ > > > On Mon, Aug 5, 2013 at 11:17 AM, Jos Vos wrote: > >> On Sun, Aug 04, 2013 at 11:39:37PM +0300, Oguz Yilmaz wrote: >> >> > "unable to find the kickstart file...." >> > cdrom:/isolinux/ssd.cfg >> >> [...] >> >> > If I write ks url as "hd:scd0:/isolinux/ssd.cfg" then anaconda mounts >> and >> > reads the ks file. >> >> Did you try: >> >> ks=cdrom:/dev/sr0:/ks/ks-install.cfg >> >> This at least works for Fedora 18 (and "cdrom" in kickstart file). >> But from what you wrote, I guess this won't work either. >> >> -- >> -- Jos Vos >> -- X/OS Experts in Open Systems BV | Phone: +31 20 6938364 >> -- Amsterdam, The Netherlands | Fax: +31 20 6948204 >> >> _______________________________________________ >> Kickstart-list mailing list >> Kickstart-list at redhat.com >> https://www.redhat.com/mailman/listinfo/kickstart-list >> > > -------------- next part -------------- An HTML attachment was scrubbed... URL: