Recent content by Pride1922

  1. P

    Boot Failure on upgrade to VE 7.2 with kernel 5.15.35-1-pve

    Same problem here... megaraid_sas 0000:01:00:0: Failed to init firmware / Failed to do reset /dev/mapper/pve-root on /root failed: input/output error [ 1011.642] Any solution? Temporary is fine.
  2. P

    Upgrade to 7.1 gone wrong: activating LV 'pve/data' failed

    You should open a new thread on the forum so others can help you. I do not know how to help you then.
  3. P

    Upgrade to 7.1 gone wrong: activating LV 'pve/data' failed

    This is not a command. This is a parameter on lvm.conf. Can you post the contents of you lvm.conf?
  4. P

    Upgrade to 7.1 gone wrong: activating LV 'pve/data' failed

    I don't understand your question. Let me grab a screenshoot:
  5. P

    Upgrade to 7.1 gone wrong: activating LV 'pve/data' failed

    yes, first make a local copy of lvm.conf, just in case, then add thin_check_options = [ "-q", "--skip-mappings" ] to your lvm.conf and reboot the machine. cd /etc/lvm cp lvm.conf lvm.backup nano lvm.conf inside nano is CTRL +W to search for thin_check_options, uncomment / edit it to look like...
  6. P

    Upgrade to 7.1 gone wrong: activating LV 'pve/data' failed

    Solution: add "thin_check_options = [ "-q", "--skip-mappings" ]" to lvm.conf Explanation: "It's not an LVM bug, but should rather be considered a bug in Proxmox VE's (and likely Debian's) init configuration/handling. What (likely) happens is that the thin_check during activation takes too long...
  7. P

    PVE Upgrade 6.4 to 7.1 destroys LVM (thin provision)

    Did you ever find a solution? I have the same problem.
  8. P

    Upgrade to 7.1 gone wrong: activating LV 'pve/data' failed

    Hey guys, I just upgrade proxmox to 7.1, everything went good. Upon reboot I get this error: "activating LV 'pve/data' failed: Activation of logical volume pve/data is prohibited while logical volume pve/data_tmeta is active. (500)". root@proxmox:~# lsblk NAME MAJ:MIN RM SIZE RO...