[Expired for grub2 (Ubuntu) because there has been no activity for 60
days.]
** Changed in: grub2 (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1561842
Just checking my email this AM and reading your recent replies to Ubuntu
GNOME mailing list i see you included a boot info summary with both the
Windows drive and the Ubuntu drive connected:
http://paste.ubuntu.com/15574213/
The output of parted -l shows Win 7 is installed non-EFI but Ubuntu is
@Phillip Susi
No, I'm not able to find a particular cause for it. As I had said, the
system works and acts perfectly normal before this happens and works
normal after installing grub again.
I'm a bit confused as to how the motherboard/BIOS could have just
*forgot* that Grub existed. Not that
Based on what's said in comment #3 I suspect that there is an EFI System
Partition on both the Windows drive (which was disconnected when boot
info was gathered) and the Ubuntu drive. That becomes problematic and
really is just a limitation of UEFI in itself. I still frequently run
into problems
I'm afraid this looks like a bad motherboard/firmware; it appears to
have simply "forgot" that it should boot grub. Unless you can identify
some particular software action that seems to cause it?
** Package changed: grub (Ubuntu) => grub2 (Ubuntu)
** Changed in: grub2 (Ubuntu)
Status:
I've personally never used update-grub before, so unless the command was
given by an update, no.
I run Windows 7 and Ubuntu Gnome on separate hard drives. I had
unplugged the Windows 7 HDD for the boot-repair.
Don't think so since it happens when restarting from Ubuntu Gnome and
never from
Grub shouldnt just disappear!
Does running "update-grub" break it? (that would get triggered from time to
time on system updates)
You dual boot with Windows? Is it possible that Windows is messing with the
UEFI Boot Manager? Or does it happen when you reboot from Ubuntu?
I notice this diffing
