Just wondering how you copied the old drive to the new one? If you manually copied the data, the blkids are different, so the boot and fstab information will have to manually be updated, or you will have to use blkid to change the blkids to match.
I generally clone disks to the new one, which also sets the blkids to be identical, so this problem doesn't happen.
I've maintained the disk imaging project G4L since 2004.
Good Luck.
On 25 Apr 2021 at 16:03, Robert McBroom via users wrote:
To: Fedora users@lists.fedoraproject.org Subject: Restored f33 on new drive from a tarball now a problem Date sent: Sun, 25 Apr 2021 16:03:57 -0400 Send reply to: Community support for Fedora users users@lists.fedoraproject.org From: Robert McBroom via users users@lists.fedoraproject.org Copies to: Robert McBroom robert.mcbroom@yahoo.com
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?
users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-leave@lists.fedoraproject.org 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@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
+------------------------------------------------------------+ Michael D. Setzer II - Computer Science Instructor (Retired) mailto:mikes@guam.net mailto:msetzerii@gmail.com Guam - Where America's Day Begins G4L Disk Imaging Project maintainer http://sourceforge.net/projects/g4l/ +------------------------------------------------------------+