I have 2 questions dealing with 2 different kickstart files. 1) my kickstart sections for RAID disk setup and kickstart reports it cannot find sda. Why is that. sda is there and works. clearpart --all --initlabel part raid.01 --asprimary --bytes-per-inode=4096 --fstype="raid" --onpart=sda1 --size=20000 part swap --asprimary --bytes-per-inode=4096 --fstype="swap" --onpart=sda2 --size=4000 part raid.02 --bytes-per-inode=4096 --fstype="raid" --grow --onpart=sda3 --size=1 part raid.03 --asprimary --bytes-per-inode=4096 --fstype="raid" --onpart=sdb1 --size=20000 part swap --asprimary --bytes-per-inode=4096 --fstype="swap" --onpart=sdb2 --size=4000 part raid.04 --asprimary --bytes-per-inode=4096 --fstype="raid" --grow --onpart=sdb3 --size=1 raid / --bytes-per-inode=4096 --device=md0 --fstype="ext3" --level=1 raid.01 raid.03 raid / --bytes-per-inode=4096 --device=md1 --fstype="ext3" --level=1 raid.02 raid.04 2) my kickstart section for normally single disk setup. However with 2 disks present in box it put / on sda and /home on sdb. Is there a way to put it ALL on sda??? If there is a second disk I want it left alone. clearpart --all --initlabel part / --fstype ext3 --size=20000 --asprimary part swap --size=4000 --asprimary part /home --fstype ext3 --size=100 --grow --asprimary THanks, Jerry
On Fri, 28 Mar 2008 at 2:43pm, Jerry Geis wrote> I have 2 questions dealing with 2 different kickstart files. > > 1) my kickstart sections for RAID disk setup and kickstart reports it cannot > find sda. Why is that. sda is there and works. > > clearpart --all --initlabel > part raid.01 --asprimary --bytes-per-inode=4096 --fstype="raid" --onpart=sda1Is sda already partitioned?> raid / --bytes-per-inode=4096 --device=md0 --fstype="ext3" --level=1 raid.01 > raid.03 > raid / --bytes-per-inode=4096 --device=md1 --fstype="ext3" --level=1 raid.02 > raid.04If that's cut and pasted from your ks file, then you're requesting the same partition twice...> 2) my kickstart section for normally single disk setup. However with 2 disks > present in box > it put / on sda and /home on sdb. Is there a way to put it ALL on sda??? If > there is a second disk I want it left alone. > > clearpart --all --initlabel > part / --fstype ext3 --size=20000 --asprimary > part swap --size=4000 --asprimary > part /home --fstype ext3 --size=100 --grow --asprimaryAdd --ondisk=sda to each line. I refer to http://www.redhat.com/docs/manuals/enterprise/RHEL-5-manual/en-US/RHEL510/Installation_Guide/s1-kickstart2-options.html quite often... -- Joshua Baker-LePain QB3 Shared Cluster Sysadmin UCSF
Jerry Geis wrote:> I have 2 questions dealing with 2 different kickstart files. > > 1) my kickstart sections for RAID disk setup and kickstart reports it > cannot find sda. Why is that. sda is there and works. > > clearpart --all --initlabel > part raid.01 --asprimary --bytes-per-inode=4096 --fstype="raid" > --onpart=sda1 --size=20000I've had issues with onpart in the past. I had to use ondisk and trust the anaconda to put the partitions in a good place.> > 2) my kickstart section for normally single disk setup. However with 2 > disks present in box > it put / on sda and /home on sdb. Is there a way to put it ALL on sda??? > If there is a second disk I want it left alone. > > clearpart --all --initlabel > part / --fstype ext3 --size=20000 --asprimary > part swap --size=4000 --asprimary > part /home --fstype ext3 --size=100 --grow --asprimaryUse --ondisk to specify which disk. Also, if there is a 2nd disk, it will lose it's partition table because of your clearpart. You may want ot explore an ignoredisk command. -- Milton Calnek BSc, A/Slt(Ret.) milton at calnek.com 306-717-8737 -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean.
part of my kickstart file is now: clearpart --all --initlabel part --ondisk=sda raid.01 --asprimary --bytes-per-inode=4096 --fstype="raid" --onpart=sda1 --size=20000 part --ondisk=sda swap --asprimary --bytes-per-inode=4096 --fstype="swap" --onpart=sda2 --size=4000 part --ondisk=sda raid.02 --asprimary --bytes-per-inode=4096 --fstype="raid" --onpart=sda3 --size=1 --grow part --ondisk=sdb raid.03 --asprimary --bytes-per-inode=4096 --fstype="raid" --onpart=sdb1 --size=20000 part --ondisk=sdb swap --asprimary --bytes-per-inode=4096 --fstype="swap" --onpart=sdb2 --size=4000 part --ondisk=sdb raid.04 --asprimary --bytes-per-inode=4096 --fstype="raid" --onpart=sdb3 --size=1 --grow raid / --bytes-per-inode=4096 --device=md0 --fstype="ext3" --level=1 raid.01 raid.03 raid /home --bytes-per-inode=4096 --device=md1 --fstype="ext3" --level=1 raid.02 raid.04 I changed the config to use --ondisk above and at install I get a message saying: "Unable to locate partition sda1 to use for ." Press OK to reboot your system. The above is the correct message. I did not leave any words out. It looks good to me. What might I have wrong? sda works just fine when not installing RAID. Jerry