<html><head><meta http-equiv="Content-Type" content="text/html charset=windows-1252"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">I recovered my data. <div>Thanks for all your help. </div><div>The problem was in fact knoppix, but not because it had an older version of lvm2 or even lvm1.</div><div><br></div><div>The problem was that the human-readable part I extracted from the beginning of the device contained invisible characters in front of the </div><div>'vol0' label in the file 'volt.txt' .</div><div>These characters were not visible in terminal using 'cat', 'more', and they also did not appear in standard error as a consequence of the 'vgcfgrestore' command, as witnessed by the first line of the error:</div><div><br></div><div>'data/vol0.txt' does not contain volume group 'vol0'.</div><div><br></div><div>The reason why I could not observe this problem under knoppix is, that I did not use any other programs to display text than 'cat', 'more', standard error/standard out, and libreoffice. So I could not see that there were these invisible characters in front of 'vol0'.</div><div>Under knoppix, I did not have xemacs, which I usually use, so I could not locate the problem, thinking that my restore file vol0.txt was ok.</div><div>This belief was reinforced by the fact that I could use the file without problems to recreate the physical volume using pvcreate with the uuid switch.</div><div><br></div><div>You helped me finding the problem because of your comments on possible lvm2-version differences between ubuntu and knoppix, so I redid the whole thing with a ubuntu live cd, where I could install xemacs, and I noticed the characters. </div><div>I could then remove the bogey volume group that I had created from scratch using vgremove, and after that, the</div><div>vgcfgrestore command with the corrected file vol0.txt worked without problems. </div><div><br></div><div>Right now I am doing my backup, before switching the faulty drive to the new replacement… This is not gonna happen again.</div><div><br></div><div>Bottom-line: </div><div>Something during the replacement happened that did something with the metadata for the physical volume. I do not know what that was. </div><div>The human-readable metadata at the beginning of the raid10 device was still there and intact.</div><div>I copied the data from the beginning of the raid10 device using </div><div><br></div><div><pre class="bbcode_code" style="margin-top: 0px; margin-bottom: 0px; padding: 6px; font-family: 'Ubuntu Mono', monospace; line-height: 14px; border: 1px inset; text-align: left; overflow: auto; direction: ltr; background-image: none; background-color: rgb(239, 239, 239); font-size: 14px; height: 36px; background-repeat: repeat no-repeat; ">sudo dd if=/dev/md127 bs=512 count=255 skip=1 of=md0.txt</pre><div><br></div></div><div>Then copied the volume group description from md0.txt to a file called vol0.txt.</div><div><br></div><div>I could then recreate the physical volume using </div><div><br></div><div><pre class="bbcode_code" style="margin-top: 0px; margin-bottom: 0px; padding: 6px; font-family: 'Ubuntu Mono', monospace; line-height: 14px; border: 1px inset; text-align: left; overflow: auto; direction: ltr; background-image: none; background-color: rgb(239, 239, 239); font-size: 14px; height: 36px; background-repeat: repeat no-repeat; ">sudo pvcreate --uuid WFo1On-anFb-2av8-DuRq-vKee-nJEt-ZLnu26 --restorefile vol0.txt /dev/md127</pre><div><br></div></div><div>and I could recover the volume group and all its logical volumes using</div><div><br></div><div><pre class="bbcode_code" style="margin-top: 0px; margin-bottom: 0px; padding: 6px; font-family: 'Ubuntu Mono', monospace; line-height: 14px; border: 1px inset; text-align: left; overflow: auto; direction: ltr; background-image: none; background-color: rgb(239, 239, 239); font-size: 14px; height: 36px; background-repeat: repeat no-repeat; ">sudo vgcfgrestore -f vol0.txt vol0</pre><div><br></div></div><div>Thanks for helping!</div><div><br></div><div><br></div><div><br><div><div>On Mar 27, 2013, at 21:08 , Stuart D Gathman <<a href="mailto:stuart@bmsi.com">stuart@bmsi.com</a>> wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite">On 03/25/2013 05:50 PM, Björn Nadrowski expounded in part:<br><blockquote type="cite">Well, I see I would have to remove the volume group first, at the very least.<br></blockquote>I wouldn't. Just think of your vgcreate as removing all LVs and renaming the VG. Now you want to undo all that<br>with a vgcfgrestore.<br><blockquote type="cite">But I would just be back in the middle of my problem description on ubuntuforums, wouldn' t I?<br>Still no volume group, still no logical volumes...<br></blockquote>Does knoppix have an older lvm version that doesn't recognize your metadata? I *hope* it doesn't have lvm1, which used binary metadata....<br><br>If you see the human readable metadata, and knoppix doesn't, then there is a problem with knoppix. Either ancient lvm, or the device filtered out for vgscan in lvm.conf.<br><br>_______________________________________________<br>linux-lvm mailing list<br><a href="mailto:linux-lvm@redhat.com">linux-lvm@redhat.com</a><br>https://www.redhat.com/mailman/listinfo/linux-lvm<br>read the LVM HOW-TO at http://tldp.org/HOWTO/LVM-HOWTO/<br></blockquote></div><br></div></body></html>