Bug#281556: s390 installation report, installed system does not boot
On Nov 16, 2004, at 10:57 AM, Eugeniy Meshcheryakov wrote:
After using google.com I found that I need to pass dasd=0120 to zipl
to boot. That worked. It is posible that dasd parameter is missing
did not use d-i for formating dasd and partitioning.
I believe this is the case.
A workaround to 281407 (the formatting loop) problem exists, too, if
you don't have the fixed version: define more than one DASD device.
The loop only appears if you have exactly one disk.