Grub bug report

[Ty Young]

I redid update-grub with Windows drive plugged in. No change or 
difference: same output and can still boot into "ubuntu".

On 03/31/2016 10:49 PM, Tim wrote:
>
> On 01/04/16 10:54, Ty Young wrote:
>> Sorry for the late reply!
>>
>> On 03/28/2016 03:58 AM, Narcis Garcia wrote:
>>> If you want Windows entries not appears in GRUB menu, you can disable
>>> the detection of other operating systems:
>>> chmod a-x /etc/grub.d/30_os-prober
>>>
>>> Than you can run update-grub with Windows HDD plugged, and menu will not
>>> include MS/Windows boot.
>>> Usually, when GRUB has no different OS to show in the menu, it's
>>> configured hidden to boot faster. If you want to discover the menu, you
>>> must hold [Shift] key at boot manager stage.
>> A bit confused here... are you talking about the Ubuntu boot option in GRUB? No, that in itself was/is(currently) fine and working. The menu
>> I'm talking about is the BIOS boot device manager/window that comes up by entering BIOS Boot Options/holding F12 after POST. The entry to boot
>> to "ubuntu"(The HDD where Ubuntu-Gnome is on) was gone, with only the HDD model(as mentioned previously) option remaining.
> If you are talking about the efi boot manager, I think that entry should be added at install time (and not touched again), though not entirely sure.
>
> Though from your logs, efi boot doesnt seem to change?
>
> =================== efibootmgr -v (Before boot-repair)
> BootCurrent: 0004
> Timeout: 1 seconds
> BootOrder: 0003,0004,0000,0001,0002
> Boot0000* UEFI Device: Generic-SD/MMC/MS/MSPRO 1.00	BBS(17,,0x0)
> Boot0001* UEFI Device: P5: HL-DT-ST DVDRAM GH70N     	BBS(18,,0x0)
> Boot0002* UEFI Device: USB Flash Disk 1100	BBS(19,,0x0)
> Boot0003* UEFI Device: ST3750528AS	PciRoot(0x0)/Pci(0x1f,0x2)/Sata(1,65535,0)/HD(1,GPT,4f39d2b7-00d2-4be4-a2d4-a3a41eceeb6e,0x800,0x100000)
> Boot0004* UEFI Device: Generic Flash Disk 8.00	PciRoot(0x0)/Pci(0x1a,0x0)/USB(1,0)/USB(1,0)/HD(1,MBR,0x0,0x2a8,0x7a8d58) =================== efibootmgr -v (after)
> BootCurrent: 0004
> Timeout: 1 seconds
> BootOrder: 0003,0004,0000,0001,0002
> Boot0000* UEFI Device: Generic-SD/MMC/MS/MSPRO 1.00	BBS(17,,0x0)
> Boot0001* UEFI Device: P5: HL-DT-ST DVDRAM GH70N     	BBS(18,,0x0)
> Boot0002* UEFI Device: USB Flash Disk 1100	BBS(19,,0x0)
> Boot0003* UEFI Device: ST3750528AS	PciRoot(0x0)/Pci(0x1f,0x2)/Sata(1,65535,0)/HD(1,GPT,4f39d2b7-00d2-4be4-a2d4-a3a41eceeb6e,0x800,0x100000)
> Boot0004* UEFI Device: Generic Flash Disk 8.00	PciRoot(0x0)/Pci(0x1a,0x0)/USB(1,0)/USB(1,0)/HD(1,MBR,0x0,0x2a8,0x7a8d58)
>

Don't know anything about GRUB, so I'm not sure. I just generated the 
logs via boot-repair GUI app from a flash drive both before and after 
the new GRUB install. I didn't mess with the drive other than that.


>> Attempting to boot to the HDD model option after "ubuntu" goes missing just boots to Windows. I'm guessing that is because it couldn't find an
>> OS on the HDD so it went to my default boot option, which was my Windows 7 HDD...
>>
>> AFAIK, my install of Ubuntu-Gnome itself is fine. Every time I've reinstalled GRUB via boot-repair it always lets me boot back into the OS
>> with no problems, but eventually goes missing again... even months later apparently.
>>
>>> El 28/03/16 a les 02:32, Ty Young ha escrit:
>>>> On 03/27/2016 04:24 AM, Narcis Garcia wrote:
>>>>> Do you want to use GRUB With or Without Windows?
>>>>> Then will you update-grub With or Without Windows HDD plugged?
>>>>>
>>>> Without. The test that I just did was without Windows, though normally
>>>> it is plugged in during updates.
>>>>
>>>>> El 27/03/16 a les 00:26, Ty Young ha escrit:
>>>>>> Sent this earlier with an image attached but the size was too big and it
>>>>>> needed to be approved by a mod. I'll just include a link instead...
>>>>>>
>>>>>> On 03/25/2016 03:40 AM, Narcis Garcia wrote:
>>>>>>> I suppose the only thing to seem disappeared is GRUB's menu (hidden to
>>>>>>> be more precise).
>>>>>>>
>>>>>>> If you already boot to GNU/Linux (Ubuntu), the command "update-grub"
>>>>>>> will rebuild menu's entries with plugged volumes that have operating
>>>>>>> systems.
>>>>>> I removed my Windows HDD and did update-grub and I can still boot into
>>>>>> Ubuntu Gnome. This is what it gave for output, if it helps any:
>>>>>> https://i.gyazo.com/882030bc7803cc353078120ed48e6043.png
>>>>>>
>>>>>>> El 25/03/16 a les 08:12, Ty Young ha escrit:
>>>>>>>> On 03/25/2016 01:58 AM, Tim wrote:
>>>>>>>>> On 25/03/16 17:12, Ty Young wrote:
>>>>>>>>>> I've personally never used update-grub before, so unless the command
>>>>>>>>>> was given by an update, no.
>>>>>>>>> Yes it will get triggered by system updates from time to time, so it
>>>>>>>>> would be worth trying and see if breaks things. A reproducible bug is
>>>>>>>>> much
>>>>>>>>> better than one that says "things break after a random reboot"!
>>>>>>>> Just update-grub? No special arguments/options? I'll try that tomorrow
>>>>>>>> and see what happens.
>>>>>>>>
>>>>>>>> Yeah, sorry about that. I said that because I have no clue what
>>>>>>>> could be
>>>>>>>> causing it. I hadn't installed any grub updates in a long time and
>>>>>>>> I've
>>>>>>>> only recently upgraded the kernel to 4.5, the only times I would think
>>>>>>>> update-grub would run.
>>>>>>>>
>>>>>>>> I swear this has happened without even installing updates before
>>>>>>>> though.
>>>>>>>> Guess I'll found out tomorrow when I run it...
>>>>>>>>
>>>>>>>>>> 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 Windows 7 to Ubuntu Gnome if the option was there before
>>>>>>>>>> restarting Ubuntu Gnome.
>>>>>>>>> OK, its probably not from windows then
>>>>>>>>>> If it matters any, I get a duplicate UEFI entry for Ubuntu, named
>>>>>>>>>> after the hard drive model(Model: ST3750528AS). If i select it, the
>>>>>>>>>> screen
>>>>>>>>>> flashes blue and enters grub as normal(or looks normal, anyway).
>>>>>>>>> I don't have any UEFI hardware still, so not entirely sure about
>>>>>>>>> this.
>>>>>>>>> But I believe the UEFI entries are added by the OS, maybe you can use
>>>>>>>>> efibootmgr to remove the dupe. No idea if this is causing your issues
>>>>>>>>> though.
>>>>>>>>>
>>>>>>>>>
>>
>