Need help with mounting an old logical volume

[Fulko Hew <fulko.hew@xxxxxxxxx>]

To make a long story short, my laptop screen died, so I bought a new laptop.

I installed Fedora 25.  Then I wanted to copy my old stuff off of the old drive

(Fedora 23) so I took the drive out and put it into a USB container and plugged

it in.

The first problem is that its got a logical volume,
and its name is duplicated with the current name ('fedora').

Searching the web I find that I have to rename the old volume to something unique.

a) I used 'pvs' to determine the device names and to see the sizes,

b) I then used 'vgs -d vg_all' to find the UUID that matched the sizes
   of the device I needed to alter.

c) Having the UUID, I then used 'vgrename UUID fedora_old'

d) Then I needed 'ls /dev/fedora_old' to see the 'sub-device' called 'root00'
e) That let me 'mount /dev/fedora_old/root00 mydir'

That was good enough to allow me to copy some of my data off,

but it wasn't showing anything in /home/fulko.

My next step was to plug an external monitor into that old laptop

and reboot, and try to FTP the remainder of my data from /home/fulko.

That didn't work because the volume name was now changed.

So I had to change it back.

I booted an F23 live CD, used 'vgs' to find the UUID, and the  'vgrename'

to rename it back to 'fedora'.

Rebooting with the drive, now fails with the following error messages:

   ...
   Failed to start File System Check on /dev/mapper/fedora-root00

   See 'systemctl status systemd-fsck-root.service' for details.

   Dependency failed for /sysroot.

   Dependency failed for Initrd Root File System

   Dependency failed for Reload Configuration from the Real Root.

   ...

and then goes into emergency mode.

Following the instructions in those error messages, I used 'sytemctl'

to see what I could see, and it says:

/dev/mapper/fedora-root00: Inode 1317765, end of extent exceeds allowed value

    (logical block 128, physical block 7479168, len 15)

/dev/mapper/fedora-root00: UNEXPECTED INCONSISTENCY: run FsCK manually.

   (i.e. without -a or -p options) fsck failed with error code 4.
Running request emergency.target/start/replace
...

Now what?

I'm afraid of running fsck on it to resolve whatever problems it may have,
(because I'm afraid of screwing it up even more)
and on the other hand, what did I do wrong to get problems in the place?

Comments and suggestions will be more than welcome.

Thanks in advance.

Fulko

_______________________________________________
users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx