grub2 cannot find lvmid device when an additional disk has been added to root volume group
This document (000020635) is provided subject to the disclaimer at the end of this document.
Environment
SUSE Linux Enterprise Server 15
SUSE Linux Enterprise Server for SAP Applications 15
SUSE Linux Enterprise Server for SAP Applications 15
Situation
Extension of root volume (LVM) is needed due to running out of space.
In order to achieve it, a additional physical volume (PV) needs be created and added to the volume group (VG) containing '/'.
As next step, the root volume is extended using lvextend command, and filesystem of '/' is as well extended using either xfs_growfs or resize2fs.
After system reboot, grub2 cannot find the root volume anymore, and it is entering in rescue mode with an error similar as below...
In order to achieve it, a additional physical volume (PV) needs be created and added to the volume group (VG) containing '/'.
As next step, the root volume is extended using lvextend command, and filesystem of '/' is as well extended using either xfs_growfs or resize2fs.
After system reboot, grub2 cannot find the root volume anymore, and it is entering in rescue mode with an error similar as below...
Resolution
Please follow the below steps to resolve the issue.
1. Boot the system in rescue mode
2. Enter the rescue mode by providing root user only
3. Verify the location of boot partition using 'fdisk -l | grep boot'
1. Boot the system in rescue mode
2. Enter the rescue mode by providing root user only
3. Verify the location of boot partition using 'fdisk -l | grep boot'
tty1:rescue:~ # fdisk -l | grep boot /dev/vda1 2048 6143 4096 2M BIOS boot tty1:rescue:~ #4. Verify the location of root partition using 'fdisk -l | grep root'
tty1:rescue:~ # fdisk -l | grep root Disk /dev/mapper/system-root: 67.99 GiB, 73001861120 bytes, 142581760 sectors tty1:rescue:~ #5. Mount root LV using /dev/mapper and bind /proc, /dev, /sys and /run to it
tty1:rescue:~ # mount /dev/mapper/system-root /mnt tty1:rescue:~ # for i in dev proc sys run ; do mount -o bind /$i /mnt/$i ; done6. chroot /mnt
tty1:rescue:~ # chroot /mnt7. Install grub on /dev/vda
tty1:rescue:~ # grub2-install /dev/vda8. Update/ recreate grub.cfg configuration file
tty1:rescue:~ # grub2-mkconfig -o /boot/grub2/grub.cfg9. Next, make a backup of the old initrd and create a new one using the following commands
tty1:rescue:~ # cd /boot tty1:rescue:~ # mkdir brokeninitrd tty1:rescue:~ # cp initrd-<version> brokeninitrd tty1:rescue:~ # mkinitrd10. Exit chroot, and reboot the system
tty1:rescue:~ # exit; sync && reboot
Cause
The reason is unknown as of yet, but SUSE engineering is aware of it and investigating.
Additional Information
The boot issue happens while extending the logical volume by:
1. Creating an additional PV
2. Extending VG
3. Extending LV
4. Extending/ resizing FS
* The boot issue could be avoided by performing steps 6, 7, and 8 from above, prior to reboot...
1. Creating an additional PV
2. Extending VG
3. Extending LV
4. Extending/ resizing FS
* The boot issue could be avoided by performing steps 6, 7, and 8 from above, prior to reboot...
Disclaimer
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:000020635
- Creation Date: 07-Apr-2022
- Modified Date:05-Sep-2023
-
- SUSE Linux Enterprise Server
- SUSE Linux Enterprise Server for SAP Applications
For questions or concerns with the SUSE Knowledgebase please contact: tidfeedback[at]suse.com
