From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mx1.redhat.com (ext-mx03.extmail.prod.ext.phx2.redhat.com [10.5.110.27]) by smtp.corp.redhat.com (Postfix) with ESMTPS id 31A4B1000049 for ; Mon, 17 Dec 2018 20:41:07 +0000 (UTC) Received: from sender-pp-o92.zoho.eu (sender-pp-o92.zoho.eu [31.186.226.252]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by mx1.redhat.com (Postfix) with ESMTPS id 1858C7FDE5 for ; Mon, 17 Dec 2018 20:41:05 +0000 (UTC) From: Giuseppe Vacanti Message-Id: <167bde59673.fc2fc0a351387.5941487526649049402@vacanti.org> In-Reply-To: <807b41c03c2d66e16153a8ee3489b4f1@assyoma.it> References: <167b30557b8.d471a29712958.970233558882873666@vacanti.org> <807b41c03c2d66e16153a8ee3489b4f1@assyoma.it> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_138763_332312350.1545079199347" Subject: Re: [linux-lvm] PV not found Reply-To: giuseppe@vacanti.org, LVM general discussion and development List-Id: LVM general discussion and development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Date: Mon, 17 Dec 2018 20:41:09 -0000 List-Id: To: LVM general discussion and development ------=_Part_138763_332312350.1545079199347 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit Hello, I have found a solution to the problem, however the problem seems to come back after every reboot. I have been put on the good path by the remarks made on this list by John and Gionatan. The fix is the following: - convince myself that the device has the correct uuid, I used blkid and compared the result with the information in the lvm backup - run pvck -t on /dev/sdc. Nothing special, all seems OK - run vgscan --cache. This command brings back knowledge of the VG the PV belongs to - now pvs lists my PV again, but the LV is inactive - I activate the LV with lvchange - all is back, I can mount and use the LV 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. I have a running system, but I don't know what is happening. Where can I look to figure this out? Regards, Giuseppe -- Giuseppe Vacanti ------=_Part_138763_332312350.1545079199347 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable =

Hello,

I have found a solution to the problem, however= the problem seems to come back after every reboot.

I have been put on the good path by the remarks made on this list by = John and Gionatan.

The fix is the following:

- convince myself that the device has the corre= ct uuid, I used blkid and compared the result with the information in the l= vm backup

- run pvck -t on /dev/sdc. Nothing special, all see= ms OK

- run vgscan --cache. This command brings back knowledg= e of the VG the PV belongs to

- now pvs lists my PV again, bu= t the LV is inactive

- I activate the LV with lvchange

- all is back, I can mount and use the LV

<= 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.

<= /div>

I have a running system, but I don't know wh= at is happening. Where can I look to figure this out?

Regards, Giuseppe

<= div>--

Giuseppe Vacanti

<= br> ------=_Part_138763_332312350.1545079199347--