Search results

  1. S

    local-LVM not available after Kernel update on PVE 7

    Today I upgraded the server to 5.13.19-2-pve. Everything works great.
  2. S

    local-LVM not available after Kernel update on PVE 7

    thin_check_options = present in config. It only needs to be find and corrected.
  3. S

    local-LVM not available after Kernel update on PVE 7

    Yes! This fixes my problem. Thank You!
  4. S

    local-LVM not available after Kernel update on PVE 7

    Yes, I am following this discussion. I will try to check soon
  5. S

    local-LVM not available after Kernel update on PVE 7

    I don’t know how to do it, I don’t know how to describe it, I don’t know how to arrange it. If possible, You can do it.
  6. S

    local-LVM not available after Kernel update on PVE 7

  7. S

    local-LVM not available after Kernel update on PVE 7

  8. S

    local-LVM not available after Kernel update on PVE 7

    I originally had Proxmox 7 installed. The problem arose after updating the system. The kernel has changed from version 5.11.22-4 to 5.11.22-5. Loading the previous kernel does nothing. After boot im have to execute the lvchange -ay command with your hands and start the machines. Update log...
  9. S

    local-LVM not available after Kernel update on PVE 7

    Same issue.
  10. S

    [SOLVED] cannot start VM after upgraded to 7.0-11

    On the weekend I also got this problem. lvscan shows all vms inactive. The /dev/vms folder is missing. lvchange -ay /dev/vms activates all disks and machines start. After rebooting the server, everything is the same - the disks are inactive. The logs contain the following: Oct 23 10:23:34...
Top Bottom