Re: Restored f33 on new drive from a tarball now a problem

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On 26/04/2021 07:09, Robert McBroom via users wrote:
On 4/25/21 5:34 PM, George N. White III wrote:
On Sun, 25 Apr 2021 at 17:04, Robert McBroom via users <users@xxxxxxxxxxxxxxxxxxxxxxx <mailto:users@xxxxxxxxxxxxxxxxxxxxxxx>> wrote:

    New drive has the same msdos partition structure as the old. Legacy
    system with boot partition on a separate drive and from the root
    partition. System boots in mode 3 as specified but entering id and
    password flashes some text and returns to the login. Edited the grub
    entry to try a graphical boot but still get textmode.

    What can be done to get access to f33?


Were any original directories encrypted?   Can you boot in rescue mode?
If not, then you may have to arrange an alternate bootable drive (Live distro?).

Once you are booted in linux you can mount the root directory and do some
basic sanity checks for proper permissions, missing home directories, etc.

More details of the command used to create the tar archive might be useful.
You may be better off installing a fresh system and restoring just the home
directories and other changes outside the purview of distro (/opt, /usr/local, etc).

The drive was pulled out of the system to a usb external drive adapter on another system, mounted and entered from a terminal window.

in the mounted root of the partition the command used was

tar -czf /mnt/stor/system.gz *

to put the tarball on a NAS.

I can get to the F33 from an f31 install on the same computer, mounted on /mnt/sysimage and doing the binds to /dev, /proc, and /sys followed by

chroot gets me in to look at everything. Everything I look into looks correct. Short of ideas



I have never tried using a tar file to restore.  However using tar (both creating and restoring) without
using the --selinux parameter won't preserve selinux context.

Have you tried booting after adding "selinux=0" to the linux line in grub?



--
Remind me to ignore comments which aren't germane to the thread.

_______________________________________________
users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/users@xxxxxxxxxxxxxxxxxxxxxxx
Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure



[Index of Archives]     [Older Fedora Users]     [Fedora Announce]     [Fedora Package Announce]     [EPEL Announce]     [EPEL Devel]     [Fedora Magazine]     [Fedora Summer Coding]     [Fedora Laptop]     [Fedora Cloud]     [Fedora Advisory Board]     [Fedora Education]     [Fedora Security]     [Fedora Scitech]     [Fedora Robotics]     [Fedora Infrastructure]     [Fedora Websites]     [Anaconda Devel]     [Fedora Devel Java]     [Fedora Desktop]     [Fedora Fonts]     [Fedora Marketing]     [Fedora Management Tools]     [Fedora Mentors]     [Fedora Package Review]     [Fedora R Devel]     [Fedora PHP Devel]     [Kickstart]     [Fedora Music]     [Fedora Packaging]     [Fedora SELinux]     [Fedora Legal]     [Fedora Kernel]     [Fedora OCaml]     [Coolkey]     [Virtualization Tools]     [ET Management Tools]     [Yum Users]     [Yosemite News]     [Gnome Users]     [KDE Users]     [Fedora Art]     [Fedora Docs]     [Fedora Sparc]     [Libvirt Users]     [Fedora ARM]

  Powered by Linux