Bug#445148: S390: Build w/ /boot partition succeeds, but re-boot fails in fsck

[Frans Pop <elendil@planet.nl>]

severity 445148 important
reassign 445148 zipl-installer
thanks

> Configuration is a 125 cylinder /dev/dasda1, which is to be mounted
> as /boot, and a large /dev/dasdb1 which is to be mounted as /.
>
> fsck fails for dasda1, but I don't see anywhere that dasda1 is mounted.
> mount /boot says that it's already mounted or dasda1 is busy, and
> umount /boot says it isn't mounted. Tried the boot several times w/ same
> results. Building system to a single disk works w/o problems.

This is almost certainly because zipl-installer just does not check if /boot
is mounted on a separate partition and thus the partition referred to in the
kernel boot parameters is / instead of /boot.

You can work around this in two ways.

During the installation
-----------------------
Before the system reboots:
- start a shell (using a second ssh session to the installer)
- chroot /target
- make sure /boot is mounted
- edit /etc/zipl.conf and correct the dasd that is listed there
- run zipl
- exit the chroot
- finish the installation

To repair an existing installation
----------------------------------
- boot the installer and proceed until you can mount partitions
  (after the dasd initialization step)
- start a shell (using a second ssh session to the installer)
- mkdir target
- mount /
- chroot /target
- mount /boot
- edit /etc/zipl.conf and correct the dasd that is listed there
- run zipl
- exit the chroot
- abort the installation

Cheers,
Frans Pop