# Fedora 28 - Grub2 "Error: No Such Device / Setting Partition Type to 0x83 / Error: Invalid Signature"

Just recently installed Fedora28 and everything was working pretty well. Yesterday, I was messing with 'Grub Customizer' a bit - really to just change the font size and perhaps the colors.

Didn't notice a problem until I attempted to boot Windows today. It resulted in this error:

Error: No Such Device
Setting Partition Type to 0x83
Error: Invalid Signature


So I did some digging around on various forums, checked the Grub2 docs and such.

On a side note; I did find a bugreport that's pretty much identical to my issue with Fedora 24: https://bugzilla.redhat.com/show_bug.... But it was never marked as solved due to EndOfLife on 24, according to the comments.

In any event - I checked the hard disk's UUID, using blkid

    [root@localhost ~]# blkid /dev/sda1
/dev/sda1: LABEL="System Reserved" UUID="7C941A89941A4654" TYPE="ntfs" PARTUUID="0d6e3339-01"


Then checked my grub file: (/boot/grub2/grub.cfg)

### BEGIN /etc/grub.d/45_custom_proxy ###
menuentry "Windows 10 (on /dev/sda1)" --class windows --class os $menuentry_id_option 'osprober-chain-7C941A89941A4654' { insmod part_msdos insmod ntfs set root='hd0,msdos1' if [ x$feature_platform_search_hint = xy ]; then
search --no-floppy --fs-uuid --set=root --hint-bios=hd0,msdos1 --hint-efi=hd0,msdos1 --hint-baremetal=ahci0,msdos1  7C941A89941A4654
else
search --no-floppy --fs-uuid --set=root 7C941A89941A4654
fi
parttool ${root} hidden- drivemap -s (hd0)${root}
}
### END /etc/grub.d/45_custom_proxy ###


It seems like the UUID matches ok and Windows will boot just fine if I flip the drive boot order in the BIOS... I read something about UEFI mode; but the comments there were about installing Fedora under legacy mode - but my thinking is that it would have never worked if that was the case?

I re-ran grub2-mkconfig for good measure as well.

I did confirm that Windows would boot up properly prior to messing with Grub... lol I figure I did something, just not sure what - any help would be most appreciated!

edit retag close merge delete

Sort by » oldest newest most voted

Just to follow up on this I suppose..

I have found - interestingly - that this doesn't happen all of the time. I recently re-loaded Fedora 28 because the update + nVidia drivers seem to have created a large enough problem that re-installing was the easiest way to go.

All the same - this problem continues, but not all of the time.

On a cold boot; after the system has been sitting a while, Windows will boot just fine via the GRUB2 menu and seems to on subsequent reboots. However; once I boot to Fedora - then I have to use the BIOS boot menu and select the drive specifically to boot Windows - because GRUB2 will error out each time after booting to Fedora.

It then kind of dawned on me that I recalled a similar problem on this same system a while back with Ubuntu/Debian, I figured at the time, it was something I did, but now I'm thinking there's something odd about this system board - possibly UEFI that is causing some issues with this. Well, that's the only thing that seems to make sense. And after re-loading I'm positive that this is some kind of a bug somewhere (system board firmware or grub2 I suspect) - because prior to reloading I cleaned the disk entirely since I wanted to change the partitioning scheme slightly - giving just a bit more space to the root volume. And on a new load - this problem persists. It can't be related to Windows itself or even Fedora - since this issue arises prior to any OS loading.

Odd little issue - the work-around is easy enough, I just hit F11 and select what device.

BTW: this is an ASRock system board. When I get home, I'll find the specific model and do a follow-up post - just in case anyone has a similar issue.

more