Systemback

Failure to connect to lvmetad

Asked by tim O

Systemback 1.7

My laptop has a 60GB hard drive. I had Debian 8.x installed, but only 30GB were used. I used LVM and encryption. Today I've used Systemback 1.7 to create a restore point to an external HD.
I wiped the internal hard drive and installed Debian 8.x again, but used the entire 60GB; again I used LVM and encryption. Then I installed Systemback 1.7 and recovered from the restore point I recently created.
Upon reboot I get the following message over and over again:

/run/lvm/lvmetad.socket: connect failed: No such file or directory
  WARNING: Failed to connect to lvmetad. Falling back to internal scanning.

It appears my system is now hosed and I can go back to my previous restore point. I've used Systemback in the same fashion (create restore point > re-install Debian > recover restore point) on other systems.

Why is it failing now?

Question information

Language:
English Edit question
Status:
Answered
For:
Systemback Edit question
Assignee:
No assignee Edit question
Last query:
Last reply:
Revision history for this message
Kendek (nemh) said : 		#1

Unfortunately the cross-system restoration is not supported if you using LVM (basically because the initramfs issue).
The LVM and the encryption are not supported by the Systemback. If you using the system copy or system install functions, the copied and the installed systems uses normal partitions, without encryptions.

Can you help with this problem?

Provide an answer of your own, or ask tim O for more information if necessary.

To post a message you must log in.