Red Hat Bugzilla – Bug 253888
Anaconda Kickstart doesn't see zFCP devices (sda)
Last modified: 2007-11-30 17:07:47 EST
Description of problem:
Within the kickstart file for a RHEL5 s390x install.
Using the keyword zFCP and it's options sets up my FCP drives. They come up as
sda and sdb. Alas when trying to partition them using the part commands anaconda
whines and quits essentially complaining that at kickstart line X nonexistant
The kickstart line looks like:
part raid.30 --size=100 --grow --ondisk=sda
part raid.31 --size=100 --grow --ondisk=sdb
Also I'm passing proper FCP_x arguments via zVM.
I've tried initiating the zFCP drive manually in my pre script.
It does the same stuff.
The installation works file w/o kickstart.
Version-Release number of selected component (if applicable):
RHEL 5 GOLD INSTALL
Is this happening with a 5.1 tree? Nightly or beta.
I haven't tried this with a 5.1 tree as yet. Should I?
Also I've found out that the:
clearpart --all --initlabel
seems not to work as well.
While DASDs are get formatted by dasdfmt the zFCP devices do not get
(re)initialized and still have information on them.
I deducted this by creating a md1 device out of the zFCP devices when i
installed RHEL and adding it to VolGroup00, extending the root lv (LogVol00),
expanding the ext3 fs then kicking off a fresh install (manually).
Next thing I'll attach is the kickstart file.
Yeah, please do testing with 5.1 trees now. We're so near the release and so
much work has gone in to 5.1 now.
Created attachment 171256 [details]
It works well on the 20070822.1 tree
Just fails badly on 5.0 Gold
Here is the kickstart file.