Description of problem:
The installer attempts to add all devices to the Linux dasd driver and even
decides to format the disk without interaction with the user. There does not
seem to be a way to restrict the range of dasd devices the installer picks
Version-Release number of selected component (if applicable):
initrd dated Jul 22 00:43
netstg2.img Jul 22 00:44
Installing in a virtual machine the console is filled with lots of msgs like
dasd: <devno 000e> Add lowmem page :...
dasd: device range 019b-019b: device 019b already in a range
I believe earlier versions used the DASD= option in the parameter
file that is used for the first part of the configuration.
I've tested this with our latest images on s390 and s390x with a DASD=XXX parameter in
the .parm file. Only the defined dasds were probed and added to /proc/dasd/devices.
Did you test this in hercules ? We could reproduce this in hercules, but not on real hardware.
Or did you leave out the DASD= parameter ? We accidently left it out in our documentation but
added it in the meantime.
Can you please elaborate on 'decides to format the disk without interaction with the user' ?
Which DASD has been reformatted ? Has it been a CMS disk or maybe a LDL formatted disk ?
Created attachment 93973 [details]
console log of the install
The log shows the DASD=200-207 and further down you see the installer tamper
with devices outside that range (not even disks).
The log file shows the installer tampering with devices outside that list. Also,
a nother disk in the specified range but not formatted was not picked up.
Re: unsolicited formatting
This was a recycled virtual machine, so the disk was probably CDL format and
most likely had a ReiserFS filesystem on it. If really helpful I can make sure
to try with that combination next time I run the install.
easy fix: reorder your .parm file so that DASD= isn't the first parameter in the .parm file.
I've already committed the real fix to CVS.
Closing MODIFIED bugs as fixed. Please reopen if the problem perists.