Upgrade from 3.7 to 3.8 with kernel replacement breaks HDD LVM installation
I am running multiple Alpine Dom0s which are typically installed on LVM
partitions on the top of 32GB SSD (I have bunch of identical machines).
Nothing fancy, this is one of the options offered by the installer (I
didn’t know that sys option which installs OS on the raw ext4 is
preferred). Upgrade routine brings the system to 3.8 but leaves
4.9.65-1-hardened kernel which is full of zero-day exploits. Adding
linux-vanilla kernel and rebooting breaks the system as
/dev/vg0/lv_root
can’t be found. This is my /etc/fstab
<code class="lua">
/dev/vg0/lv_root / ext4 rw,relatime,data=ordered 0 1
UUID=54852e93-e164-4d23-ae7a-5e91fedcac88 /boot ext4 rw,relatime,data=ordered 0 2
/dev/vg0/lv_swap swap swap defaults 0 0
/dev/cdrom /media/cdrom iso9660 noauto,ro 0 0
/dev/usbdisk /media/usb vfat noauto 0 0
UUID=7e0dcf46-d8e1-405d-835d-8a9d76d2d394 /xen-images xfs defaults 0 0
</code>
Apparently even though mkinitfs
is run after adding linux-vanilla
kernel something is wrong with the order
<code class="lua">
xen1:/etc/mkinitfs# more mkinitfs.conf
features="ata base ide scsi usb virtio ext4 lvm"
</code>
(from redmine: issue id 9062, created on 2018-07-07)