Open spigell opened 3 years ago
I haven't double-checked but LVM should be present in the initrd. You may need a modules
entry in your config.yaml
.
Hi! i have attached a screenshot to description. I tried to add lvm to modules and also specify 'vgchange -a y' to init_cmd => It can't find partition with K3OS_STATE label because a lvm volume is not activated.
@spigell, can you show us your config.yaml
? I have successfully mounted a LVM RAID5 device but am now using mdadm
for the same.
@ivan98 Hi. Here it is:
init_cmd:
- 'sudo vgchange -a y'
boot_cmd:
- 'sudo sh -c "echo GA_PATH=/dev/vport1p1 > /etc/conf.d/qemu-guest-agent"'
k3os:
modules:
- lvm
- wireguard
password: "$6$7Mw7WhZ6wwxR28uD$W3VhXiO7zTQm.jubGlxHLxWsXKFLNwQUbIenxjfRnqoUrfyl0ORlYRB9m3AJcvFppkccO6BsCV7cT5hIzglwM."
Version (k3OS / kernel) v0.20.11-k3s2r1
Architecture amd64
Describe the bug Greeting! I created my own disk layout and installed bootloader. But when k3os boots all volumes not activated. Is there any workarounds?
To Reproduce
Packer boot_command
create-disk-layout.sh
Expected behavior All lvm volumes will be activated
Actual behavior Without lvm k3os can't determine boot mode. If I specify mode via kernel (k3os.mode=disk) k3os can't mount root partition Additional context