Nuking these error messages during bootup?

Ok folks, I make this as painless as possible, +REP will be given.
System: openSUSE 13.1 (Tumbleweed), encrypted with LVM2.

Dateisystem             Größe Benutzt Verf. Verw% Eingehängt auf
/dev/mapper/system-root   20G    5,2G   14G   28% /
devtmpfs                 733M     32K  733M    1% /dev
tmpfs                    746M    612K  745M    1% /dev/shm
tmpfs                    746M    3,3M  742M    1% /run
tmpfs                    746M       0  746M    0% /sys/fs/cgroup
tmpfs                    746M    3,3M  742M    1% /var/lock
tmpfs                    746M    3,3M  742M    1% /var/run
/dev/sda1                379M     87M  268M   25% /boot
/dev/mapper/system-home   25G     21G  3,4G   86% /home

Error messages:

  1. “Failed to connect to lvmetad, falling back to internal scanning”
  2. “Volume group ‘System’ not found”

I’ve done a search, but no clear answers popped up. How to solve mentioned issues?

Tumbleweed problems/questions belong in the Tumbleweed forum where the other Tumbleweed users are.

This will be moved and is CLOSED for the moment.

Mov ed from Install/Boot/Login and open again.

Thank you for moving this thread and your recommendations, @hcvv. To find the cause of the error messages, let me clarify: I can normally boot into my system and do not experience any issues. It’s just mentioned messages that bother me during startup, right before being asked for the password to decrypt my LVM volume.

I am no Tumbleweed user, thus I feel not realy qualified here. But as I know a bit about LVM, I will try to throw in my two cents.

There is a message, but that does not mean it is an error message. There are also message for warning and simple for information.

The message talks about the Volume group ‘System’. Is ther such a volume group? You did not post a list of volume groups.

su - -c 'vgdisplay -s'

I’m not using Tumbleweed. I get these messages with basic 13.1, too. They started with an “lvm2” update.

I am treating them as hard-wired unavoidable messages that can be safely ignored.

I get those messages on every computer where I use an encrypted LVM with opensuse 13.1. On one computer, I have an sd-card reader for several different kinds of card. I get 4 of those messages for each of the supported sd-card types, even though no card is plugged in.

I’m pretty sure that it is quite safe to ignore these messages if there are no related problems. So it’s just a noisy boot screen, but otherwise no big deal.

Exactly. And I would like to get rid of these warnings or whatever that is. It makes me feel bad on evey bootup.

They most likely can be ignored, but since it makes me feel bad, I opened this thread to find a solution for it.

Awful man. Hope we’ll find a solution here and find out what exactly causes this behaviour. Bare with us.

Here is some output to throw in:

SecUpwN@openSUSE:~> su - -c 'vgdisplay -s'

  "system" 74.17 GiB [47.00 GiB used / 27.17 GiB free]

Well, “System” seems to be your only VG. And as your system just functions, I agree with nrickert that it is just something to forget. I do not know why it gives you a bad feeling. Do you realy undrstand all the messages that scroll past during booting in a way that you are very happy with all of them except this one?

But when you want to take action, you can file a bug at (same username/password as here). You have evidence and documentation about it enough now (report it against 13.1, not Tumbleweed and don not forget the LVM version).

You could post the bug nummer here, thus everybody coming here through a search could then add info to the bug report if needed.

Yes I do. And yes, it is THAT annoying.

Great suggestion, but currently I am having a huge problem with my mail provider as I have no access to my mail address and cannot access my account, nor delete my mailing address. Would you please do me a favour and file mentioned things as a bug in their bugtracker? I owe you a huge beer then. THANK YOU!

@hcvv, I don’t like to bother you, but have you filed this as a bug yet? :stuck_out_tongue:

Of course not:
a) I have no problem with it;
b) I can not re-create the problem, thus I can not provide first hand documentaion, nor can I add more information when asked for.