System does not boot after extending btrfs root filesystem
This document (000019686) is provided subject to the disclaimer at the end of this document.
SUSE Linux Enterprise Server 12 Service Pack 4 - System Z (s390x)
Systemd endlessly prints messages similar to:
"A start job is running for dev-disk...ab12cdef.device (60s / no limit)."
btrfs device add /dev/dasdb1 /
If you do this and have not rebooted, see TID 000019088 - System does not boot anymore after extending root filesystem for list of commands to run BEFORE reboot.
In short, the recovery process, is to run "grub2-install" but from a rescue boot, not from mounting on another VM.
Then you have to copy the new initrd from /boot/zipl/ to /boot/
There are variables that will need to be adjusted for each environment.
It is assumed you know how to use the IBM tools to adjust parmfiles, minidisk and IPL the system.
We assume you know how to boot the VM so it can start an FTP or HTTP install,
we'll add the "rescue" flag to the boot parameters instead of completing a normal install.
Here is an example parmfile for that:
InstNetDev=osa OsaInterface=qdio Layer2=1 PortNo=0 OSAHWAddr= HostIP=10.1.1.10/20 Hostname=sles12sp5.domain.com Gateway=10.1.1.1 Nameserver=10.1.1.1 Domain=domain.com ReadChannel=0.0.0600 WriteChannel=0.0.0601 DataChannel=0.0.0602 install=ftp://ftp-install.server.com/install/SLP/SLE-12-SP5-Server-GM/s390x/DVD1/ ssh=1 sshpassword=sshpasswd rescue=1
You will need the SLES OS s390 ISO.
The SLES12-SP5 s390 ISO is:
You will need to put these 4 files from the SLES12-SP5 s390 ISO on the "a" disk.
The files on the ISO are:
(With the parmfile edited to what is posted above).
The parmfile will need to be changed and customized for your environment.
The files are punched to the virtual card reader and then IPL'd
(booted) from the reader.
to start the VM run:
Once you're booted into rescue mode we want to name
the devices what they are actually named in the running OS.
Typically that would be 0100 and 0101.
chzdev -e 0.0.0100 chzdev -e 0.0.0101 lsdasd (to confirm) btrfs filesystem show / (to confirm both disks) mount /dev/dasda2 /mnt/ mount /dev/dasda1 /mnt/boot/zipl mount --rbind /dev /mnt/dev mount --rbind /proc /mnt/proc mount --rbind /sys /mnt/sys chroot /mnt/
Do not run "mkinitrd" or any of the other commands.
Then we need to copy the NEW initrd that was created in /boot/zipl/ to /boot/
Using "ls", you can check the dates, the initrd in /boot/zipl should be the current date:
(Depending on kernel version)
ls -la /boot/zipl/initrd-4.12.14-122.12-default
This one should be old:
ls -la /boot/initrd-4.12.14-122.12-default
cp /boot/zipl/initrd-4.12.14-122.12-default /boot/initrd-4.12.14-122.12-default(Change the kernel numbers to match the version you are running.)
Exit chroot and reboot:
exit umount /mnt/sys umount /mnt/proc umount /mnt/dev umount /mnt/boot/zip/ umount /mnt/ reboot
Then the VM should boot normally.
This Support Knowledgebase provides a valuable tool for SUSE customers and parties interested in our products and solutions to acquire information, ideas and learn from one another. Materials are provided for informational, personal or non-commercial use within your organization and are presented "AS IS" WITHOUT WARRANTY OF ANY KIND.
- Document ID:000019686
- Creation Date: 20-Aug-2020
- Modified Date:20-Aug-2020
- SUSE Linux Enterprise Server
For questions or concerns with the SUSE Knowledgebase please contact: firstname.lastname@example.org