<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/"><channel><title>Lvm on Life</title><link>/tags/lvm/</link><description>Recent content in Lvm on Life</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Mon, 05 May 2014 12:50:00 +0530</lastBuildDate><atom:link href="/tags/lvm/index.xml" rel="self" type="application/rss+xml"/><item><title>Recovering a LUKS-Encrypted Ubuntu LVM Volume Group on Another System</title><link>/post/2014/2014-05-05-recovering-luks-encrypted-ubuntu-lv-group-when-mounting-on-a-different-ubuntu-system/</link><pubDate>Mon, 05 May 2014 12:50:00 +0530</pubDate><guid>/post/2014/2014-05-05-recovering-luks-encrypted-ubuntu-lv-group-when-mounting-on-a-different-ubuntu-system/</guid><description>&lt;p&gt;I frequently mirror and swap internal hard drives using an external USB/eSATA docking station. However, this creates a tricky issue when mounting on another Ubuntu machine.&lt;/p&gt;
&lt;p&gt;During standard installation with LUKS + LVM encryption, Ubuntu names the root volume group &lt;code&gt;ubuntu-vg&lt;/code&gt;. If you plug in a secondary drive where Ubuntu was also installed, LVM encounters a name conflict between the host&amp;rsquo;s volume group and the external disk&amp;rsquo;s volume group, preventing activation.&lt;/p&gt;</description></item></channel></rss>