On 05/21/2017 09:40 AM, Lucélio Gomes de Freitas wrote: > Hi friends, > > Anybody helps? > > Runnning old "Fedora 20-x86_64", and want to install > Fedora-Kde-live-25-1-3. > > Situation: > [lucelio@localhost ~]$ uname -rov > 3.19.8-100.fc20.x86_64 #1 SMP Tue May 12 17:08:50 UTC 2015 GNU/Linux > > [lucelio@localhost ~]$ sudo lvmdiskscan > /dev/fedora/root [ 50,00 GiB] > /dev/fedora/swap [ 3,77 GiB] > /dev/sda2 [ 500,00 MiB] > /dev/vg_maq01/lv_swap [ 5,75 GiB] > /dev/sda3 [ 118,75 GiB] LVM physical volume > /dev/vg_maq01/lv_home [ 63,00 GiB] > /dev/vg_maq01/lv_root [ 50,00 GiB] > /dev/fedora/home [ 48,48 GiB] > /dev/sdb2 [ 500,00 MiB] > /dev/sdb3 [ 194,87 GiB] > /dev/sdb4 [ 500,00 MiB] > /dev/sdb5 [ 102,24 GiB] LVM physical volume > 6 disks > 4 partitions > 0 LVM physical volume whole disks > 2 LVM physical volumes > > The /dev/sda* is a SSD(KINGSTON SV200S3128G) 128GB, with old "Fedora > 16-x86_64", and only want to recover some files in /home. > > The /dev/sdb* is a Seagate(ST3320613AS) 320GB, running old "Fedora > 20-x86_64", with some important file in /home. > > [lucelio@localhost ~]$ sudo lvscan > ACTIVE '/dev/fedora/swap' [3,77 GiB] inherit > ACTIVE '/dev/fedora/home' [48,48 GiB] inherit > ACTIVE '/dev/fedora/root' [50,00 GiB] inherit > ACTIVE '/dev/vg_maq01/lv_swap' [5,75 GiB] inherit > ACTIVE '/dev/vg_maq01/lv_home' [63,00 GiB] inherit > ACTIVE '/dev/vg_maq01/lv_root' [50,00 GiB] inherit > > [lucelio@localhost ~]$ mount | grep /dev/mapper > /dev/mapper/fedora-root on / type ext4 (rw,relatime,seclabel,data=ordered) > /dev/mapper/fedora-home on /home type ext4 > (rw,relatime,seclabel,data=ordered) > > Problem: > Want to mount the SSD on "Fedora 20" to recover some files, copying it > to /dev/sdb3 space(/dev/sdb3 not used/mounted). After this, I can > erase all SSD and install "Fedora 25" on it. Looks like you've used Fedora's default naming scheme for VGs and LVs (the default VG name of "fedora" and LVs such as "root", "home", "swap" and the like). This is normal, but can cause pain if you want to mount LVs on other systems that ALSO use the default naming conventions. I tend to bypass the default naming conventions and embed the OS version in the VG and LV names, e.g. "f25vg" for the volume group and "f25root", "f25home" and such for the volume names to avoid such issues, but I'm weird. Judging from what you have above, I doubt seriously that the /dev/sda- related stuff is really your old F16. Generally, /dev/sda will be your boot disk, and the VGs/LVs on it is your current system. Checking isn't hard. First off, note that device mapper names can take several forms: /dev/mapper/<VGName>-<LVName> -OR- /dev/<VGName>/<LVName> Using that information, it's easy to find the volume group (VG). In my case my root filesystem is "/dev/mapper/f25vg-f25root" (or "/dev/f25vg/f25root". From that, I know the VG is "f25vg". If, however, you're not sure about that: 1. Do a "mount" as the root user. Go through the list and find the line that describes your / (root) filesystem. For example, in my case: /dev/mapper/f25vg-f25root on / type ext4 (rw,relatime,seclabel,data=ordered) The first entry in that line (/dev/mapper/f25vg-f25root) is the root filesystem. 2. Do an "lvdisplay -v" on that and look for the line that contains "VG Name" [root@prophead ~]# lvdisplay -v /dev/mapper/f25vg-f25root <snip> VG Name f25vg So, the volume group is "f25vg" (as could have been deciphered from name easily). Now, you want to know what physical volumes (PVs) make up that volume group. Do an "vgdisplay -v" on that VG name: [root@prophead ~]# vgdisplay -v f25vg You'll get a bunch of data from that. There will be data on the volume group itself and each of the logical volumes it has. Down at the bottom of all that, you'll see some information headed by the line "--- Physical volumes ---". You're interested in the line that contains "PV Name": PV Name /dev/sda2 So, my / (root) filesystem is the logical volume "f25root" in the volume group "f25vg". The volume group itself lives on physical device /dev/sda2. Using this, verify what devices are actually active on your machine. As I said, if you're running an OS other than F16 or F20 (the two you mentioned) and your active filesystems are on /dev/sda, then /dev/sda is NOT your old F16 data. We may have to dig a bit deeper on your system to find your data and we may have to rename VGs and LVs to actually mount them. ---------------------------------------------------------------------- - Rick Stevens, Systems Engineer, AllDigital ricks@xxxxxxxxxxxxxx - - AIM/Skype: therps2 ICQ: 226437340 Yahoo: origrps2 - - - - Let us think the unthinkable. Let us do the undoable. Let us - - prepare to grapple with the ineffable itself, and see if we may - - not eff it up after all. - - -- Douglas Adams - ---------------------------------------------------------------------- _______________________________________________ users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx
