Description of problem: ======================= I have a Windows/Linux dual boot system, installed as follows: 0) Use Legacy Boot and MBR partition table 1) Install "Windows 7" in partition sda1 ("recovery partition" and boot stuff) and sda2 ("C:" drive) then 2) Install Linux in extended partition sda6 ("/boot"), sda7 (encrypted root filesystem) and sda8 (encrypted home filesystem). This is actually a clonezilla image of an earlier installation which I finagled to get into the right partitions. Be that as it may... 3) Apply grub2-install This results in a boot menu that allows one to select Linxu kernels or Windows (the latter via chainloader) This works initially. However after some time (not sure what happened, maybe a Windows update), when booting "Windows 7", grub announces that: ---------- error: no such device: E4DE45CCDE4597A6 Setting partition type to 0x83 error: invalid signature. ---------- (The "setting partition type to..." is misleading, it should be "interpreting partition type of [type] as 0x83 (Linux)" as nothing is being set, but that's another problem) This can easily be fixed by editing the boot instructions for Windows, which read: ---------- setparams 'Windows 7 (loader) (hd0,msdos1)' insmod part_msdos insmod ntfs # set root='hd0,msdos1' search --no-floppy --fs-uuid --set=root E4DE45CCDE4597A6 parttool ${root} hidden- chainloader +1 ---------- Comment out the search instruction which is not finding anything as for some reason the filesystem id has changed, and use the set instruction instead. ---------- setparams 'Windows 7 (loader) (hd0,msdos1)' insmod part_msdos insmod ntfs set root='hd0,msdos1' # search --no-floppy --fs-uuid --set=root E4DE45CCDE4597A6 parttool ${root} hidden- chainloader +1 ---------- Ctrl-x and off we go. But is the grub setup too confident for some reason? Can the filesystem id change?? Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
On second thoughts, Could be the following happened: 1. Linux system has been installed from clonezilla image, so retains an old Windows filesystem UUID somewhere in the grub setup 2. Initial installation of grub uses the correct filesystem UUID as it gets it from the Windows partition directly, but does not update the old Windows filesystem UUID which remains somewhere in the grub setup 3. Fedora kernel update causes the boot menu to be regenerated, at which point the old Windows filesystem UUID is recycled 4. Boot failure occurs
This message is a reminder that Fedora 24 is nearing its end of life. Approximately 2 (two) weeks from now Fedora will stop maintaining and issuing updates for Fedora 24. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '24'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 24 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 24 changed to end-of-life (EOL) status on 2017-08-08. Fedora 24 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.