I assume it is still not bootable. But if the windows system is gone and you don't care about it, then I would set sda3 to be bootable. rescue it and then grub-install /dev/sda3 but make sure the newuuid is in both fstab (you have done that I think) and matches what is in the /boot/grub2/grub.cfg. if a different value is in the grub.cfg file then you can either make the actual fs uuid match that and update fstab to match, or edit the grub.cfg file that it says do not edit (I would think the grub2-install would fix that but it appears another command might be required for that--see below). I did a test and it looks like this will update the grub.cfg file and it should use the new uuid, try it and see if it uses the correct uuid and verify the old file did not have the correct uuid. grub2-mkconfig -o /boot/grub2/grub.cfg <save a copy of it first> On Fri, Apr 23, 2021 at 2:37 PM Michael Hennebry <hennebry@xxxxxxxxxxxxxxxxxxxxx> wrote: > > On Fri, 23 Apr 2021, Roger Heflin wrote: > > > If you used rsync to copy from one disk to the other then the uuid > > would have changed on the new fs as compared to the old fs. I > > Yup. > Needed to change fstab. > > > typically copy /boot the hard crude way (dd) and copy LVM using the > > LVM tools (pvmove and friends) and in both cases that maintains the > > same UUID on the old and new. > > I do not have a /boot partition. > /boot is in the root, aka / , partition. > I'm allergic to LVM. > The first time I encountered it > was in the middle of an install, > not the time to try something unexpected and new. > > > You will need to find the new uuid and update grub to be using that > > anyplace it has the old uuid then reinstall it on sda if grub is going > > to boot first, or see if a microsoft install cd will fix the windows > > side of the system, or see below match the new fs to have the old > > uuid. > > I thought I knew how to do that, > but apparently not. > The issue is not finding the new root IDs, > the issue is what to do with it. > > I considered directly copying sda5 to sda3 and changing the IDs on sda5. > sda3 is more than twice as large as sda3. > Whatever else I'd need to do, > I'd need to enlarge the filesystem after. > Does the enlarger work well for two to one enlargements? > > > What was sda3 before that you could now use it for the system on sda5? > > A Windows 7 partition that I had not used in a long time. > > > You might detail what the partition layout/usage was before and what > > you moved it to. > > I only changed partitions 2 and 3. > > sda before: > 1* 100 M Windows 7 boot? > 2 28 G Windows 7 > 3 4.7 G garbage no fs > 4 extended > 5 9.3 G / > 6 4.7 G /var > 7 4.7 G swap > 8 24.1 G /home > > sda now (intended): > 1 100 M Windows 7 boot? > 2 100 M garbage > 3 31.7 G / new > 4 extended > 5 9.3 G / retired > 6 4.7 G swap > 7 24.1 G /home > > -- > Michael hennebry@xxxxxxxxxxxxxxxxxxxxx > "Sorry but your password must contain an uppercase letter, a number, > a haiku, a gang sign, a heiroglyph, and the blood of a virgin." > -- someeecards > _______________________________________________ > 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 _______________________________________________ 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
