Hello. I have installed Rocky 9.2 and I am experiencing a strange /boot partition problem. After installation (done via kickstart) when powered down, I add a second disk.
Here is my basic kickstart config:
# Generated using Blivet version 3.6.0 ignoredisk --only-use=sda # Partition clearing information clearpart --none --initlabel # Disk partitioning information part pv.515 --fstype="lvmpv" --ondisk=sda --size=1571839 part /boot --fstype="xfs" --ondisk=sda --size=1024
When the install is completed, and powered off, add the second disk and boot the server back up, my boot partition seems to have been moved to /dev/sdb1. How can that be?
[root@mars ~]# df -h /boot Filesystem Size Used Avail Use% Mounted on /dev/sdb1 1014M 273M 742M 27% /boot [root@mars ~]# cat /etc/fstab | grep boot UUID=79c66ebc-996a-4fe4-9569-0969b403bf1f /boot xfs defaults 0 0
The install happens with only a single disk. How does it manage to carve out a slice of the second disk? I have the second disk sticktly for data, and thus the second disk becomes useless.
Here are my vm options for the server:
Anything obvious I am missing? Any help would be greatly appreciated.