-
Notifications
You must be signed in to change notification settings - Fork 564
Replies: 3 comments · 5 replies
-
There is nothing in the screenshots which would indicate exactly the problem you're facing. It's way easier to use serial console logs for debugging, or capture at least the message before the reboot. |
Beta Was this translation helpful? Give feedback.
All reactions
-
Maybe this will be better visible, starting from the line [21.363289] |
Beta Was this translation helpful? Give feedback.
All reactions
-
I don't know what is going on here, and what you're doing, but it seems to do modprobe and do it wrong way. I don't know why it even does that, you need to load the modules in the machine configuration. |
Beta Was this translation helpful? Give feedback.
All reactions
-
modules are registered in the machine configuration
My machine configuration This behavior is different hardware servers and on virtual machines |
Beta Was this translation helpful? Give feedback.
All reactions
-
Always crashes at the same LVM phase step 14 and it doesn’t matter if I use only lvm mirror or lvm thin pool or their combination We do not call any additional scripts or the modprobe command separately.
|
Beta Was this translation helpful? Give feedback.
All reactions
-
The problem can be easily reproduced even on a virtual machine.
The bug is floating, so after the first reboot it can load successfully. Therefore, you need to repeat the cycle with a reboot. |
Beta Was this translation helpful? Give feedback.
All reactions
-
Beta Was this translation helpful? Give feedback.
All reactions
-
Full boot log
|
Beta Was this translation helpful? Give feedback.
-
Hi,
When using the lvm mirror and lvm thin pool functionality, the OS is loaded randomly.
When setting up for the first time, everything is fine, the kernel modules (dm_raid and dm_thin_pool) are loaded with the config. Then the lvm mirror and lvm thin pool volumes are created and everything works well until the server is rebooted (and the reboot can be caused by various reasons, be it talosctl upgrade with the --reboot-mode powercycle option or just talosctl reboot --mode powercycle). After a restart, talos does not start, but constantly goes into cyclic restarts and at some time of restart it can boot successfully.
Screenshots of unsuccessful launches that I managed to take:
Dump debug information about the cluster:
support.zip
Talos v1.7.6
Beta Was this translation helpful? Give feedback.
All reactions