I just upgraded to 3.7.8 kernel and I am getting this error message
[ 4.500584] traps: lvmetad general protection ip:7f7240b24c25 sp:7f723bffebe0 error:0 in libc-2.17.so[7f7240aaa000+1a4000]
[ 4.969091] EXT4-fs (sda1): mounted filesystem with ordered data mode. Opts: (null)
[ 5.577531] systemd: systemd 197 running in system mode. (+PAM -LIBWRAP -AUDIT -SELINUX -IMA -SYSVINIT +LIBCRYPTSETUP +GCRYPT +ACL +XZ)
[ 5.594958] systemd: Set hostname to <xenhebe2>.
[ 5.846098] systemd: [/usr/lib/systemd/system/xenstored.service:4] Failed to add dependency on run, ignoring: Invalid argument
[ 5.846209] systemd: [/usr/lib/systemd/system/xenstored.service:4] Failed to add dependency on lib, ignoring: Invalid argument
[ 6.021567] systemd: Cannot add dependency job for unit lvm.service, ignoring: Unit lvm.service failed to load: No such file or directory. See system $
[ 6.021646] systemd: Cannot add dependency job for unit display-manager.service, ignoring: Unit display-manager.service failed to load: No such file o$
[ 6.022161] systemd: Starting Forward Password Requests to Wall Directory Watch.
[ 6.022386] systemd: Started Forward Password Requests to Wall Directory Watch.
How I can solve the issue ?
Read the news?
I experience the same problem as the OP: the lvm.service file can't be found.
Read the news?
There is a news entry from 2013-02-12 concerning changes to LVM. It states:
With lvm2 2.02.98-3, we now utilize lvmetad to activate LVM volumes automatically. This implies the following changes: ...
I did carefully read the instructions and applied the changes. I suspect that relying on lvmetad to activate LVM volumes implicates that we can disable lvm.service. But this is a mere guess and I didn't have this idea when reading the news a few weeks ago.
Edit: lvm.service can't be disabled, presumably because the symlink /etc/systemd/system/basic.target.wants/lvm.service isn't valid anymore. Does that mean we have to delete the link by hand?
I just scanned the news for other instructions concerning this file, but I didn't find any hint. Suggestions?
Last edited by ball (2013-03-19 15:05:52)
Must admit I fell afoul of this one too. I read the news item when it came out and checked all the bullet points - sorted them as reccommended and required. I upgraded lvm on 2013-02-12.
Had no issues until this morning, when I got the boot failure due to lvm.service not found. The system booted no problem yesterday and I didn't upgrade anything yesterday either.
So it's not that I don't know it failed this morning, but why it's worked for the last month.
Anyway, I deleted the symlink /etc/systemd/system/basic.target.wants/lvm.service and the system then booted fine.
"...one cannot be angry when one looks at a penguin." - John Ruskin
"Life in general is a bit shit, and so too is the internet. And that's all there is." - scepticisle