/usr/sbin/grub-probe: warning: Couldn't find physical volume `pv1'.

Bug #1662661 reported by Larry Irwin
10
This bug affects 2 people
Affects Status Importance Assigned to Milestone
grub2 (Ubuntu)
Confirmed
Undecided
Unassigned

Bug Description

This warning started appearing after adding a new disk to the VM and using the GUI logical volume manager to add it to the existing volume group.
It does not cause issues, other than erroneously displaying incorrect information.

Linux ubu16svr 4.4.0-62-generic #83-Ubuntu SMP Wed Jan 18 14:10:15 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux
Running in VM under ESXi5
Completely up-to-date as of 2/7/2017.

root@ubu16svr:/usr/bin# lsb_release -rd
Description: Ubuntu 16.04.1 LTS
Release: 16.04

root@ubu16svr:/boot/grub# apt-cache policy grub-common
grub-common:
  Installed: 2.02~beta2-36ubuntu3.6
  Candidate: 2.02~beta2-36ubuntu3.7
  Version table:
     2.02~beta2-36ubuntu3.7 500
        500 http://us.archive.ubuntu.com/ubuntu xenial-updates/main amd64 Packages
 *** 2.02~beta2-36ubuntu3.6 100
        100 /var/lib/dpkg/status
     2.02~beta2-36ubuntu3 500
        500 http://us.archive.ubuntu.com/ubuntu xenial/main amd64 Packages

root@ubu16svr:/usr/bin# df -h
Filesystem Size Used Avail Use% Mounted on
udev 7.9G 0 7.9G 0% /dev
tmpfs 1.6G 9.4M 1.6G 1% /run
/dev/mapper/ubu16svr--vg-root 33G 4.6G 27G 15% /
tmpfs 7.9G 176K 7.9G 1% /dev/shm
tmpfs 5.0M 0 5.0M 0% /run/lock
tmpfs 7.9G 0 7.9G 0% /sys/fs/cgroup
tmpfs 7.9G 0 7.9G 0% /run/shm
/dev/sda1 472M 113M 335M 26% /boot
/dev/mapper/ubu16svr--vg-u 50G 6.2G 41G 14% /u
tmpfs 1.6G 28K 1.6G 1% /run/user/112
tmpfs 1.6G 0 1.6G 0% /run/user/0

root@ubu16svr:/usr/bin# pvdisplay
  --- Physical volume ---
  PV Name /dev/sda5
  VG Name ubu16svr-vg
  PV Size 49.52 GiB / not usable 2.00 MiB
  Allocatable yes (but full)
  PE Size 4.00 MiB
  Total PE 12677
  Free PE 0
  Allocated PE 12677
  PV UUID 0oMBEX-ic7t-FTdn-cLu7-KPiL-7oDp-mbKZGu

  --- Physical volume ---
  PV Name /dev/sdb
  VG Name ubu16svr-vg
  PV Size 50.00 GiB / not usable 4.00 MiB
  Allocatable yes (but full)
  PE Size 4.00 MiB
  Total PE 12799
  Free PE 0
  Allocated PE 12799
  PV UUID QkmmnW-Pdgm-L22d-ry2O-4RD6-eJc1-tcFtZc

root@ubu16svr:/usr/bin# vgdisplay
  --- Volume group ---
  VG Name ubu16svr-vg
  System ID
  Format lvm2
  Metadata Areas 2
  Metadata Sequence No 5
  VG Access read/write
  VG Status resizable
  MAX LV 0
  Cur LV 3
  Open LV 3
  Max PV 0
  Cur PV 2
  Act PV 2
  VG Size 99.52 GiB
  PE Size 4.00 MiB
  Total PE 25476
  Alloc PE / Size 25476 / 99.52 GiB
  Free PE / Size 0 / 0
  VG UUID 8U9kUQ-3OKE-MkU7-feOI-99jh-R5Rm-f7LVfp

root@ubu16svr:/usr/bin# lvdisplay
  --- Logical volume ---
  LV Path /dev/ubu16svr-vg/root
  LV Name root
  VG Name ubu16svr-vg
  LV UUID mJ1QGk-GRIq-UevN-1Pz3-3cJV-67eC-joF4hX
  LV Write Access read/write
  LV Creation host, time ubu16svr, 2016-09-01 11:00:07 -0400
  LV Status available
  # open 1
  LV Size 33.52 GiB
  Current LE 8581
  Segments 1
  Allocation inherit
  Read ahead sectors auto
  - currently set to 256
  Block device 252:0

  --- Logical volume ---
  LV Path /dev/ubu16svr-vg/swap_1
  LV Name swap_1
  VG Name ubu16svr-vg
  LV UUID hfxDTL-4c3c-tX8Y-vfQ2-0qjq-7fCK-a5NCE8
  LV Write Access read/write
  LV Creation host, time ubu16svr, 2016-09-01 11:00:08 -0400
  LV Status available
  # open 2
  LV Size 16.00 GiB
  Current LE 4096
  Segments 1
  Allocation inherit
  Read ahead sectors auto
  - currently set to 256
  Block device 252:1

  --- Logical volume ---
  LV Path /dev/ubu16svr-vg/u
  LV Name u
  VG Name ubu16svr-vg
  LV UUID uyyGK8-ju2p-MFWV-cjR3-8zPi-UItn-dfA4kh
  LV Write Access read/write
  LV Creation host, time ubu16svr, 2017-01-23 17:10:17 -0500
  LV Status available
  # open 1
  LV Size 50.00 GiB
  Current LE 12799
  Segments 1
  Allocation inherit
  Read ahead sectors auto
  - currently set to 256
  Block device 252:2

Revision history for this message
Larry Irwin (lrirwin) wrote :

-- Didn;t see that there were still 47 packages to update --
After applying upgrade, issue still exists.
New policy info:

root@ubu16svr:~# apt-cache policy grub-common
grub-common:
  Installed: 2.02~beta2-36ubuntu3.7
  Candidate: 2.02~beta2-36ubuntu3.7
  Version table:
 *** 2.02~beta2-36ubuntu3.7 500
        500 http://us.archive.ubuntu.com/ubuntu xenial-updates/main amd64 Packages
        100 /var/lib/dpkg/status
     2.02~beta2-36ubuntu3 500
        500 http://us.archive.ubuntu.com/ubuntu xenial/main amd64 Packages

Revision history for this message
Phillip Susi (psusi) wrote :

What does ls -l show at the grub prompt? I noticed that your new volume is a whole disk volume rather than being partitioned. I wonder if that is the cause?

Revision history for this message
Larry Irwin (lrirwin) wrote :

Here's the output I get:
grub> ls -l
Device proc: Filesystem type procfs - Sector size 512B - Total size 0KiB
Device hd0: No known filesystem detected - Sector size 512B - Total size 52428800KiB
  Partition hd0,msdos5: No known filesystem detected - Partition start at 500736KiB - Total size 51927040KiB
  Partition hd0,msdos1: Filesystem Type ext* - Last modification time 2017-02-13 20:46:41 Monday, UUID [long-uuid] - Partition start at 1024KiB - Total size 498688KiB
Device hd1: No known filesystem detected - Sector size 512B - Total size 52428800KiB
Device fd0: No known filesystem detected - Sector size 512B - Total size 1440KiB

Revision history for this message
Larry Irwin (lrirwin) wrote :

Also, here is the info from fdisk.
=====
# fdisk /dev/sda

Welcome to fdisk (util-linux 2.27.1).
Changes will remain in memory only, until you decide to write them.
Be careful before using the write command.

Command (m for help): p
Disk /dev/sda: 50 GiB, 53687091200 bytes, 104857600 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0xe151ee04

Device Boot Start End Sectors Size Id Type
/dev/sda1 * 2048 999423 997376 487M 83 Linux
/dev/sda2 1001470 104855551 103854082 49.5G 5 Extended
/dev/sda5 1001472 104855551 103854080 49.5G 8e Linux LVM

Command (m for help): q
=====
# fdisk /dev/sdb

Welcome to fdisk (util-linux 2.27.1).
Changes will remain in memory only, until you decide to write them.
Be careful before using the write command.

/dev/sdb: device contains a valid 'LVM2_member' signature; it is strongly recommended to wipe the device with wipefs(8) if this is unexpected, in order to avoid possible collisions

Device does not contain a recognized partition table.
Created a new DOS disklabel with disk identifier 0xe4bfc16c.

Command (m for help): p
Disk /dev/sdb: 50 GiB, 53687091200 bytes, 104857600 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0xe4bfc16c

Command (m for help): q

Revision history for this message
Lucas S (lucas-rdg) wrote :
Download full text (5.6 KiB)

This warning is still appearing in ubuntu 18.04, it seems indeed to be related to my partitionless PV as the message doesn't appear when i pull it out of the VG

$ lsb_release -rd
Description: Ubuntu 18.04.3 LTS
Release: 18.04

$ apt-cache policy grub-common
grub-common:
  Installé : 2.02-2ubuntu8.14
  Candidat : 2.02-2ubuntu8.14
 Table de version :
 *** 2.02-2ubuntu8.14 500
        500 http://fr.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages
        100 /var/lib/dpkg/status
     2.02-2ubuntu8 500
        500 http://fr.archive.ubuntu.com/ubuntu bionic/main amd64 Packages

$ df -h
Sys. de fichiers Taille Utilisé Dispo Uti% Monté sur
udev 16G 0 16G 0% /dev
tmpfs 3,2G 1,8M 3,2G 1% /run
/dev/mapper/ubuntu--vg-root 98G 8,4G 85G 9% /
tmpfs 16G 82M 16G 1% /dev/shm
tmpfs 5,0M 4,0K 5,0M 1% /run/lock
tmpfs 16G 0 16G 0% /sys/fs/cgroup
/dev/loop0 4,3M 4,3M 0 100% /snap/gnome-calculator/544
/dev/loop1 1,0M 1,0M 0 100% /snap/gnome-logs/81
/dev/loop3 1,0M 1,0M 0 100% /snap/gnome-logs/61
/dev/loop2 15M 15M 0 100% /snap/gnome-characters/399
/dev/loop4 143M 143M 0 100% /snap/slack/21
/dev/loop5 55M 55M 0 100% /snap/core18/1668
/dev/loop6 55M 55M 0 100% /snap/core18/1066
/dev/loop8 150M 150M 0 100% /snap/gnome-3-28-1804/67
/dev/loop10 43M 43M 0 100% /snap/gtk-common-themes/1313
/dev/loop11 15M 15M 0 100% /snap/gnome-characters/296
/dev/loop7 45M 45M 0 100% /snap/gtk-common-themes/1440
/dev/loop16 92M 92M 0 100% /snap/core/8689
/dev/loop17 3,8M 3,8M 0 100% /snap/gnome-system-monitor/100
/dev/loop12 4,2M 4,2M 0 100% /snap/gnome-calculator/406
/dev/loop14 89M 89M 0 100% /snap/core/7270
/dev/loop9 161M 161M 0 100% /snap/gnome-3-28-1804/116
/dev/loop15 3,8M 3,8M 0 100% /snap/gnome-system-monitor/127
/dev/sda1 40M 12M 28M 30% /boot/efi
/dev/mapper/ubuntu--vg-home 482G 21G 436G 5% /home
/dev/mapper/ubuntu--vg-isos 9,8G 5,0G 4,3G 54% /isos
tmpfs 3,2G 20K 3,2G 1% /run/user/1000

$ sudo pvdisplay
  --- Physical volume ---
  PV Name /dev/sda3
  VG Name ubuntu-vg
  PV Size 635,26 GiB / not usable 3,00 MiB
  Allocatable yes
  PE Size 4,00 MiB
  Total PE 162627
  Free PE 9027
  Allocated PE 153600
  PV UUID 6JNPjc-KHGn-A7jA-YPlW-bjz5-07se-xJfSfL

  --- Physical volume ---
  PV Name /dev/nvme0n1
  VG Name ubuntu-vg
  PV Size <476,94 GiB / not usable <2,34 MiB
  Allocatable yes
  PE Size ...

Read more...

Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in grub2 (Ubuntu):
status: New → Confirmed
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.