Search results

  1. F

    [SOLVED] LVM-Thin pool is inactive after system reboot

    thanks for reminding me nano /etc/default/grub GRUB_DEFAULT=0 GRUB_TIMEOUT=5 GRUB_DISTRIBUTOR="Proxmox Virtual Environment" GRUB_CMDLINE_LINUX_DEFAULT="" GRUB_CMDLINE_LINUX=" rootdelay=8 " Adding root delay 8 seems to fix the issue. Thank you
  2. F

    [SOLVED] LVM-Thin pool is inactive after system reboot

    Hi, So I'm trying to create a new LVM-thin pool to use with a new SSD I've installed. I've created the pool with: lvcreate -L 440G -n vmstuff SEi lvconvert --type thin-pool SEi/vmstuff after a restart, Proxmox cannot start my containers because it cannot find the VM disks. lvscan...
  3. F

    PVE Unable to access vm disks after restart

    Solved(partially): Turns out - I don't know the reason why - the lv partition was inactive lvm> lvscan inactive '/dev/samsevo/spool' [400.00 GiB] inherit inactive '/dev/samsevo/vm-220-disk-2' [20.00 GiB] inherit inactive '/dev/samsevo/vm-110-disk-1' [8.00 GiB]...
  4. F

    PVE Unable to access vm disks after restart

    Hi, So after restarting my PVE Box I notice that all my VMs and CTs on my LVM-Thin Storage cannot start. I believe it may be because the storage device is not present. I say this because when I tried to backup my VM/CTs, It gave me this error. INFO: creating archive...

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!