Promox VE 9 upgrade and thin_check_options in lvm.conf

Flappie

New Member
Nov 18, 2024
3
0
1
Hi everybody,

I have Promox 8 running. When running pve8to9 --full i get this in the output:
FAIL: detected override for 'thin_check_options' in 'global' section without '--clear-needs-check-flag' option - add the option to your override (most likely in /etc/lvm/lvm.conf)

However, i have a modified version of lvm.conf with this options set:
thin_check_options = [ "-q", "--skip-mappings" ]

I added --skip-mappings because i took to long and timesout to on a specific disk.
When i add --clear-needs-check-flag, after that, my VM's wont start anymore and i get an error: Check of pool pve/data failed: status 1

So i need the --skip-mappings option, howver i cannot upgrade to 9 without --clear-needs-check-flag

What is a safe way to upgrade?
 
Hi there!

When you run pve8to9 and get the following warning in the output:
Code:
FAIL: detected override for 'thin_check_options' in 'global' section without '--clear-needs-check-flag' option - add the option to your override (most likely in /etc/lvm/lvm.conf)
you probably tried to change the line thin_check_options = [ "-q", "--skip-mappings" ] in the file /etc/lvm/lvm.conf and added the recommended option, so that the line was thin_check_options = [ "-q", "--skip-mappings", "--clear-needs-check-flag" ] afterwards. After a restart, your storage is not available anymore. If you undo the change, you get the warning above again and can't upgrade from pve 8 to 9.

The reason could be this:
Maybe you added the line and activated it because of this post:
local-LVM not available after Kernel update on PVE 7

What to do:
Comment the line out so it looks like this: ### thin_check_options = [ "-q", "--skip-mappings" ] For safety reasons I would not yet delete the line, so you can restore it easily. Now restart your Proxmox host, it will take longer than usual, while the storage is being mounted. The mount takes longer, because the default mount options are used. Your storage should be available after this operation as usual, please check in the WebUI. If the storage is okay, you can run the command pve8to9 --full again, it should not throw the warning again and you can update your Proxmox system.

I have no solution, though, if after uncommenting the line the storage can not be mounted, you must activate the line again and hopefully some Proxmox staff member can help in this case.
 
Last edited: