<div id="RTEContent"> Michael Loftis <mloftis@wgops.com> wrote:<blockquote class="replbq" style="border-left: 2px solid rgb(16, 16, 255); margin-left: 5px; padding-left: 5px;"> <internetbizmail@yahoo.com>LVM is not a filesystem, it's a block device layer. If you're running/using LVM on the existing system it's vgscan and vgchange on startup should have activated all the old LVs/VGs and mapped them to /dev/VGNAME/LVNAME -- those are the devices you mount. </internetbizmail@yahoo.com></blockquote>Thanks. I realise this. But the disk I'm trying to mount is built the same way as the new disk I've built. So the both have a VolGroup00. What I would like to do is to either understand how I can change the volume group info so it will become a distinct volume group, and then I can 'import' this into my new environment, or how I can get into the block system so I can access the filesystem structure it embeds. This is where I! 'm struggling. I would like to create a VolGroup01 device file, rename the volume group within the physical volume, and then mount that. Is it possible to 'hack' the old drive like this? </div>__________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com