Brad Hinson wrote:
Thang Pham wrote:
I am trying kicktstart to install RHEL5.4 on a z/VM virtual machine. I
have not problems setting up the kickstart file, parm-r54 and conf-r54
files. But during the kickstart installation, I get this question:
The partition table on device dasdb (0.0.0101) was unreadable. To create
new partitions it must be initialized, causing the loss of ALL DATA on
this drive.
This operation will override any previous installation choices about
which
drives to ignore.
Would you like to initialize this drive, erasing ALL DATA?
yesno []
If I put in yes, it continuously prints out 'y' and never ends. If I
press the 'enter' key, I get:
sh-3.2#
I did specifiy 'clearpart --all --initlabel' in my kickstart
configuration
file. So the disks should have been formatted automatically.
# The following is the partition information you requested
# Note that any partitions you deleted are not expressed
# here so unless you clear all partitions first, this is
# not guaranteed to work
zerombr yes
clearpart --all --initlabel
part / --fstype ext3 --size=1 --grow --ondisk=dasda
part /usr --fstype ext3 --size=1 --grow --ondisk=dasdb
What could I be doing wrong?
Thank you,
---------------------------------
Thang Pham
IBM Poughkeepsie
---------------------------------
Your kickstart options are correct. This looks like a bug. Can you
open a ticket with support?
Thanks,
-Brad
After some further digging, this works for me with the line:
clearpart --initlabel --drives=dasda,dasdb
Note --all is replaced with --drives=. Can you verify this works for you?
fyi, the --drives= option is only necessary when the disk is *very*
unformatted, i.e. cpfmtxa/cpformat/dasdfmt has never been run on this
disk. It was tough to get a disk back into this state after it's been
used in Linux, but by using dasdfmt (killed prematurely before if
finished), I was able to attach the disk to another guest, and lsdasd
showed:
0.0.1000(ECKD) at ( 94: 24) is dasdg : n/f
0.0.1001(ECKD) at ( 94: 32) is dasdi : n/f
(with n/f meaning not formatted)
Under this situation, --drives is needed. Otherwise, --all --initlabel
will do the trick. I believe it has to do with this error printed on
the console:
16:59:08 INFO : inserted /tmp/dasd_diag_mod.ko
16:59:08 INFO : inserted /tmp/dasd_fba_mod.ko
dasd_erp(3990): 0.0.0100: EXAMINE 24: No Record Found detected
dasd_erp(3990): 0.0.0101: EXAMINE 24: No Record Found detected
16:59:08 INFO : inserted /tmp/dasd_eckd_mod.ko
In this state, clearpart --all can't "find" dasda/dasdb, so you have to
specify that you want to format them with --drives=dasda,dasdb.
-Brad
----------------------------------------------------------------------
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu with the message: INFO LINUX-390
or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
--
Brad Hinson <bhin...@redhat.com>
Sr. Support Engineer Lead, System z
Red Hat, Inc.
(919) 754-4198
www.redhat.com/z
----------------------------------------------------------------------
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or
visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
--
Brad Hinson <bhin...@redhat.com>
Sr. Support Engineer Lead, System z
Red Hat, Inc.
(919) 754-4198
www.redhat.com/z
----------------------------------------------------------------------
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
