Red Hat Bugzilla – Bug 142093
install using multiple disks - only sda used in anaconda-ks.cfg
Last modified: 2007-11-30 17:07:05 EST
From Bugzilla Helper: User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; X11; Linux i686) Opera 7.54 [en] Description of problem: Hi, i use RHAS3U3 to install several similar systems with two old 4 GB hardisks. i choose autoinstall and let anaconda do the autopartitioning which results in: Filesystem Size Used Avail Use% Mounted on /dev/sdb1 4.0G 1.5G 2.3G 40% / /dev/sda1 99M 15M 79M 16% /boot /dev/sda2 512M anaconda-ks.cfg which i wanted to use for further kickstart installations instead shows me the following: clearpart --all --drives=sda,sdb part /boot --fstype "ext3" --size=100 --ondisk=sda part / --fstype "ext3" --size=1024 --grow --ondisk=sda part swap --size=256 --grow --maxsize=512 --ondisk=sda so, only sda is used instead of sdb for / as on the native install i performed. also SWAP space is only half of the original ... Version-Release number of selected component (if applicable): How reproducible: Always Steps to Reproduce: 1.install with multiple (2) disks, allow autopartition to use them all 2.look at resulting anaconda-ks.cfg 3. Actual Results: clearpart --all --drives=sda,sdb part /boot --fstype "ext3" --size=100 --ondisk=sda part / --fstype "ext3" --size=1024 --grow --ondisk=sda part swap --size=256 --grow --maxsize=512 --ondisk=sda Expected Results: clearpart --all --drives=sda,sdb part /boot --fstype "ext3" --size=100 --ondisk=sda part / --fstype "ext3" --size=1024 --grow --ondisk=sdb part swap --size=256 --grow --maxsize=512 --ondisk=sda Additional info:
We're not reproducing this here. Can you provide /tmp/anaconda.log and /tmp/syslog from within the installer?
Created attachment 114559 [details] anaconda logfile during installation
Created attachment 114560 [details] syslog file during installation
Hi, i have reproduced this problem very easy by just installing a default system within VMWare using 2 scsi disks of size 4GB. logfiles are available. reards, Matthias
Can you please test this with RHEL5 and see if it's still a problem on that release? If you are still experiencing it on RHEL5, feel free to reopen this bug and we can target a fix for an update release.