archive mirror
 help / color / mirror / Atom feed
From: Roger Heflin <>
	LVM general discussion and development <>
Subject: Re: [linux-lvm] PV not found
Date: Wed, 2 Jan 2019 09:23:30 -0600	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

Disable lvmetad (in systemctl and by editing lvm.conf to not use metad).

I have had lvmetad cause disks to not get detected on boot up on
several reboots. Restarting it will fix it sometimes and then doing a
vgchange -ay afterwards enabled the lvs.  It is easiest to just
disable it as I believe I have seen notes indicating lvmetad is being
moved away from.

On Wed, Jan 2, 2019 at 4:11 AM Giuseppe Vacanti <> wrote:
> 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
> _______________________________________________
> linux-lvm mailing list
> read the LVM HOW-TO at

      reply	other threads:[~2019-01-02 15:23 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-12-15 17:59 [linux-lvm] PV not found Giuseppe Vacanti
2018-12-16  2:04 ` John Stoffel
2018-12-16  7:47   ` Giuseppe Vacanti
2018-12-16 20:40 ` Gionatan Danti
2018-12-17 20:41   ` Giuseppe Vacanti
2019-01-02 15:23     ` Roger Heflin [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).