I'm not 100% sure that this will work, however it shouldn't hurt either... As root: mkdir /oldboot mount /dev/VolGroup00/LogVol01 /oldboot The file systems should now be available off of /oldboot If you want to make it available and mounted at boot time, update your fstab Hope this helps... <tt>> Good afternoon, Chris. > > My problem is related but not exactly the same. In my case I have > upgraded from FC5 to F9 by doing a fresh install on a new hard drive, > and I need to mount the old FC5 boot disk to copy some stuff off of it. > > "mount /dev/sdb2 /driveb" doesn't work for the reasons noted > (/dev/sdb2 is a container and not a volume). > > So, I said "lvm vgscan" and got: > > File descriptor 20 left open > Reading all physical volumes. This may take a while... > Found volume group "VolGroup00" using metadata type lvm2 > Found volume group "VolGroup00" using metadata type lvm2 > > Then I said "pvs" and got: > > File descriptor 20 left open > PV VG Fmt Attr PSize PFree > /dev/sda2 VolGroup00 lvm2 a- 111.59G 32.00M > /dev/sdb2 VolGroup00 lvm2 a- 76.22G 32.00M > > (Hope the formatting and column alignment on the above doesn't come > through all screwed up...) > > Apparently it thinks that both volumes are named VolGroup00 (instead > of ...00 and ...01) so things like lvm vgchange don't do any good > because it doesn't know which VolGroup00 to make available. > > /dev/mapper contains: > > crw-rw---- 1 root root 10, 60 2008-09-22 11:20 control > brw-rw---- 1 root disk 253, 0 2008-09-22 15:20 VolGroup00-LogVol00 > brw-rw---- 1 root disk 253, 1 2008-09-22 11:20 VolGroup00-LogVol01 > > ... with no corresponding LogVol00/01 for VolGroup01 (since the > system was told that both of the volumes are named VolGroup00). > > I've Googled everything I can think of and am out of ideas. > > Thanks... </tt> TIA, Gene Poole