<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"><html><head><meta content="text/html;charset=UTF-8" http-equiv="Content-Type"></head><body ><div style='font-size:10pt;font-family:Calibri,Arial,Verdana,sans-serif;color:#00000;'><div class="zmail_extra"><div><div><div>Hello,<br></div><div><br></div><div>I have found a solution to the problem, however the problem seems to come back after every reboot.<br></div><div><br></div><div>I have been put on the good path by the remarks made on this list by John and Gionatan.<br></div><div><br></div><div>The fix is the following:<br></div><div><br></div><div>- convince myself that the device has the correct uuid, I used blkid and compared the result with the information in the lvm backup<br></div><div>- run pvck -t on /dev/sdc. Nothing special, all seems OK<br></div><div>- run vgscan --cache. This command brings back knowledge of the VG the PV belongs to<br></div><div>- now pvs lists my PV again, but the LV is inactive<br></div><div>- I activate the LV with lvchange<br></div><div>- all is back, I can mount and use the LV<br></div><div><br></div><div>After a reboot however the information about the VG is gone again, and I have to repeat the steps above to be able to use the LV.<br></div></div></div></div><div><br></div><div>I have a running system, but I don't know what is happening. Where can I look to figure this out?<br></div><div><br></div><div>Regards, Giuseppe<br></div><div><br></div><div id="Zm-_Id_-Sgn"><div>--<br></div><div>Giuseppe Vacanti<br></div></div><div><br></div></div><br></body></html>