--- Comment From thorsten.di...@de.ibm.com 2016-04-07 05:35 EDT---
(In reply to comment #14)
> Hi Dimitri,
> when fixing this, please consider the following three cases:
> 1.) DASD(s) available, at least one configured
> 2.) DASD(s) available, but none configured
> 3.) no DASD available
> i
--- Comment From thorsten.di...@de.ibm.com 2016-04-06 09:47 EDT---
Hi Dimitri,
when fixing this, please consider the following three cases:
1.) DASD(s) available, at least one configured
2.) DASD(s) available, but none configured
3.) no DASD available
in all three above cases the s390-zfcp
--- Comment From thorsten.di...@de.ibm.com 2016-04-01 09:19 EDT---
Obviously some of the changes are breaking the zfcp installation now. Installer
(no DASDs, but zfcp devices) dropped into the disk-detect menu, without asking
for zfcp device initialization. See LTC bug 139913 which is bei
--- Comment From brueck...@de.ibm.com 2016-03-31 08:32 EDT---
Hi Dimitri,
(In reply to comment #6)
> Both s390-dasd and s390-zfcp are priority standard, and thus are always
> installed in d-i.
Whether they are installed automatically or later through anna is not relevant
to the root probl
