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

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(a)lists.fedoraproject.org <mailto:users@lists.fedoraproject.org>> 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