I have upgraded three VMware images previously running Fedora 29 to Fedora 30 using system-upgrade. All the images are running on the same ESC hardware and, so far as I know, use the same VMware foundation. The first worked flawlessly. Both the second and third failed in exactly the same way: they failed to reboot successfully after the upgrade. When the reboot occurred, VMware reported a "alloc magic" error immediately and froze. Not being a VMware expert, I referred the issue to someone who is and he discovered that the MBR, master boot record, on the image was corrupt. After installing a new MBR, the system booted and the upgrade showed no further problems. While investigating, we were sidetracked by the content of grub.cfg. It appears that grub no longer includes a section for each possible system to be booted. Not seeing any, we thought grub.cfg was corrupt also. But that is apparently not the case. After the MBR fix, the generated grub.cfg works properly. -- Dave Close _______________________________________________ users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@xxxxxxxxxxxxxxxxxxxxxxx
