... | @@ -267,3 +267,47 @@ Verify that the new volume is mounted correctly and restart services: |
... | @@ -267,3 +267,47 @@ Verify that the new volume is mounted correctly and restart services: |
|
|
|
|
|
findmnt
|
|
findmnt
|
|
systemctl start docker gitlab-runner
|
|
systemctl start docker gitlab-runner
|
|
|
|
|
|
|
|
# Renaming
|
|
|
|
|
|
|
|
## Rename volume group containing root
|
|
|
|
|
|
|
|
Assuming a situation where a machine was deployed successfully but the volume
|
|
|
|
group name is not adequate and should be changed. In this example, we'll change
|
|
|
|
`vg_ganeti` to `vg_tbbuild05`.
|
|
|
|
|
|
|
|
This operation requires at least one reboot, and a live rescue system if the
|
|
|
|
root filesystem is encrypted.
|
|
|
|
|
|
|
|
First, rename the LVM volume group:
|
|
|
|
|
|
|
|
vgrename vg_ganeti vg_tbbuild05
|
|
|
|
|
|
|
|
Then adjust some configuration files and regenerate the initramfs to replace
|
|
|
|
the old name:
|
|
|
|
|
|
|
|
sed -i 's/vg_ganeti/vg_tbbuild05/g' /etc/fstab
|
|
|
|
sed -i 's/vg_ganeti/vg_tbbuild05/g' /boot/grub/grub.cfg
|
|
|
|
update-initramfs -u -k all
|
|
|
|
|
|
|
|
The next step depends on whether the root volume is encrypted or not. If it's
|
|
|
|
encrypted, the last command will output an error like:
|
|
|
|
|
|
|
|
update-initramfs: Generating /boot/initrd.img-5.10.0-14-amd64
|
|
|
|
cryptsetup: ERROR: Couldn't resolve device /dev/mapper/vg_ganeti-root
|
|
|
|
cryptsetup: WARNING: Couldn't determine root device
|
|
|
|
|
|
|
|
If this happens, boot the live rescue system and follow the [remount
|
|
|
|
procedure](howto/new-machine-cymru#remount-procedure) to `chroot` into the root
|
|
|
|
filesystem of the machine. Then, inside the chroot, execute these two commands
|
|
|
|
to ensure GRUB and the initramfs use the new root LV path/name:
|
|
|
|
|
|
|
|
update-grub
|
|
|
|
update-initramfs -u -k all
|
|
|
|
|
|
|
|
Then exit the `chroot`, cleanup and reboot back into the normal system.
|
|
|
|
|
|
|
|
If the root volume is *not* encrypted, the last steps should be enough to
|
|
|
|
ensure the system boots. To ensure everything works as expected, run the
|
|
|
|
`update-grub` command after rebooting and ensure `grub.cfg` retains the new
|
|
|
|
volume group name. |