archive mirror
 help / color / mirror / Atom feed
From: Giuseppe Vacanti <>
To: linux-lvm <>
Subject: [linux-lvm] PV not found
Date: Sat, 15 Dec 2018 18:59:51 +0100	[thread overview]
Message-ID: <> (raw)


after a reboot after a maintenance power interruption of a few hours, one of my LVs is not coming back (Ubuntu 18.04). The situation I am at is the following:

- the physical disk is an iSCSI and it is seen by the kernel as /dev/sdc

- lvmdiskscan -v sees the PV on /dev/sdc
  /dev/sdc              [      72.76 TiB] LVM physical volume

- blkid returns the UUID that I can also find in the LVM configuration
 /dev/sdc: UUID="fvUXXf-pVOF-EPnn-c8eg-tZ5S-iMVW-wsSFDy" TYPE="LVM2_member"

- this entry lacks a PARTUUID entry that other LVs on the system have. Is this a clue? I could not quite connect this piece of info with anything.

- pvscan does not report /dev/sdc

- pvdisplay does not seem to know about this PV
  pvdisplay /dev/sdc
  Failed to find physical volume "/dev/sdc"

Reading man pages and searching the web does not really bring me closer to understanding what is happening. This machine has its OS on LVs and those have all come back, and of course it is not the first time that I reboot. Probably I lack the correct terms to describe the problem so that I can find a solution. Anybody here on this list who can point me in the right direction?

Regards, Giuseppe

Giuseppe Vacanti

             reply	other threads:[~2018-12-15 17:59 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-12-15 17:59 Giuseppe Vacanti [this message]
2018-12-16  2:04 ` [linux-lvm] PV not found 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

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