system-summary shows wrong physical volume state

[Uwe G.]

- Ubuntu is started in recovery mode
- I choose "system summary"

- every time I do this it shows:
 === LVM state ===
Physical Volumes: not ok (BAD)

I guess that's because of a wrong pvck call in /lib/recovery-mode/options/system-summary, it is called without arguments, which leads to an error.

Ubuntu 18.04.1 LTS
friendly-recovery 0.2.38

[Uwe G. (uwe-007)]

I installed Kubuntu 18.10 in a virtual vmware machine and activated lvm2.
After installing and rebooting I see again the wrong error message in recovery mode / system summary.
I guess this is the Package wants to do:

root@virtfred:~# pvck /dev/sda1
File descriptor 24 (socket:[32480]) leaked on pvck invocation. Parent PID 1896: -su
  Found label on /dev/sda1, sector 1, type=LVM2 001
  Found text metadata area: offset=4096, size=1044480

But this is what it does:
root@virtfred:~# pvck
File descriptor 24 (socket:[32480]) leaked on pvck invocation. Parent PID 1896: -su
  No command with matching syntax recognised. Run 'pvck --help' for more information.
  Correct command syntax is:
  pvck PV ...

If the installation is done without active lvm, but package lvmw2 is installed, you will see the wrong error too.

[Uwe G. (uwe-007)]

You can start the script /lib/recovery-mode/options/system-summary in a terminal to check this issue.

[Launchpad Janitor (janitor)]

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

[Chris Guiver (guiverc)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. Please execute the following command only once, as it will automatically gather debugging information, in a terminal:

apport-collect 1790468

When reporting bugs in the future please use apport by using 'ubuntu-bug' and the name of the package affected. You can learn more about this functionality at https://wiki.ubuntu.com/ReportingBugs.

[Tim Potter (musikgoat)]

I can also confirm this bug occurs for me, and led me down a rabbit hole trying to understand the lvm physical volume status validation.

replacing "pvck >/dev/null 2>&1" with "pvs --no-headings|awk '{print $1}'|xargs pvck >/dev/null 2>&1" allows the tool to output the correct status.

[Paddy Landau (paddy-landau)]

I have just come across this. It happens on both Ubuntu 20.04 and Lubuntu 20.04.

[fred.thomas (fred-thomas-5of9au84)]

This also happens in Mint 20.3 XFCE. New install using LVM, boot using shift, select Advanced features, boot recovery, select system-summary:

=== LVM state ===
Physical Volumes: not ok (BAD)
Volume Groups: ok (good)