Linux Mint 19.1 Dual Boot Install Faulty (Aspire E1-731-4651)

WJB-2

I just installed Linux Mint 19.1 Xfce alongside the Windows Boot Manager controlling Windows 10 version 1809, with the intention of eventually dropping Windows entirely. Curiously, Linux Mint's Ubuntu installer failed to offer a choice for default operating system. So I went to the UEFI control panel to set Mint as default, only to find to my bewilderment there is no Ubuntu selection. So to get to my preferred OS I must manually bring up the Boot Option Menu and select Ubuntu, per below, which brings me to GRUB.

1. Windows Boot Manager (ST500LT012-1DG142)
2. ubuntu (ST500LT012-1DG142)
3. HDD1: (ST500LT012-1DG142)

Beyond the inconvenience – especially when you “miss” and pokey Windows 10 boots -- it's simply not how a dual boot should work. My disk now has six partitions. (See image below.) I suspected something wasn't right when the Ubuntu installer failed to restart to let me disable Secure Boot, which was necessary for installing Third-party software, such as multimedia codecs, proprietary graphic hardware drivers, wi-fi drivers, etc. I’m about to start over, but because the same thing may well happen again I wanted to seek forum input.

Thanks,
Bill

WJB-2

Sorry @JackE, photos always best for perspective. You quoted the Boot Manager's Boot Option Menu, shown here:

Selecting Ubuntu brings you GRUB, here:

From there, selecting "System Setup" or alternately hitting F2 at boot/reboot, gives you the EFI Boot Mode settings with Boot Priority Order shown here:

See, no EFI File Boot for GRUB whatsoever in the settings. My understanding for recent Mint versions is that when you select Dual Installation -- whether adjusting the partitions manually or allowing it to be done automatically, as I chose -- you're supposed to be asked to set your default OS. I received no such option. While that concerned me I figured I'd just do it later with the Boot Manager. But while the Boot Option Menu has Ubuntu, it's not available in the EFI/BIOS boot priority order as you see above.

Essentially, I seem to have exhausted everything I and others can think of, and see no way to make Mint/Ubuntu/GRUB 2.02 the default.

JackE

Did you select (or enter from the keyboard) the actual grub EFI as trusted in the BIOS setup Security tab? Sometimes the EFI file must be actually entered letter for letter from the keyboard because selecting/highlighting doesn't seem to automatically enter it into the BIOS memory. See step #10 in this link https://community.acer.com/en/discussion/comment/598047/#Comment_598047   Jack E/NJ

MaClane

Good Morning WJB-2 !

The issue of patches and updates of Windows 10 is that they often end up changing some of the Kernel's configuration and in this way Grub is affected.
In most cases, Grub simply loses the system function by booting Windows.
That way you would have to reassemble the Grub entries and reactivate it again.

MaClane

The reality is that unfortunately Microsoft has always tried to somehow prevent the use of dual-boot with Linux, especially since the releases of version 10.
Even Intel (with RST Raid implementation) ends up preventing those with less knowledge from getting an installation on systems with this feature.

I myself have a multiple boot system:
WIndows 7, Windows 10, Debian, Kubunto and Kali.
Each one with its own utilities.

As it is known, Microsoft will launch in the second half of 2019 the new version of WSL (acronym Windows Subsystem for Linux) will be based on this internally customized Linux kernel.
"Custom internally" read: "let's remove all the good that Linux has and leave only what is of interest to us".

MaClane

Good night WJB-2 !

From what I understand, Grub 2.0 does not load automatically, right?
Have you installed Mint in UEFi mode?
Have you checked that both systems are in the same time zone and at the right time?

WJB-2

Responding to MaClane:

From what I understand, Grub 2.0 does not load automatically, right?

• Correct. Turn this E1 on without hitting F12 and it ignores the dual boot installation and does what ACER designed it to do -- enter Windows. Hit F12 at start or restart and it goes to GNU Grub 2.02. From there are choices to allow Linux Mint to start, enter UEFI/BIOS, or launch Windows Boot Loader.

Have you installed Mint in UEFI mode?

• Well, being a 2014 model the E1-731 is purely UEFI and Mint 19.1/Ubuntu automatically detects that and retains the GPT partition style. All I can add is that I was very impressed with the Ubuntu installer when I made Mint the sole OS for my 2012 Aspire Z1620. The original Z1620 has a hybrid BIOS with EFI support through an auto-detect feature. With the HDD partitioned as GPT, the BIOS automatically switches to EFI mode -- and Ubuntu readily detected that. By contrast, a Windows 10 version 1809 clean install created problems by changing the partitions to MBR. Which is why I went solo Linux.

Have you checked that both systems are in the same time zone and at the right time?

•  A very interesting question; since the attempted dual boot installation Windows 10 always starts with UTC time. Linux Mint always shows my correct Eastern US time. Fixing the Windows 10 time requires toggling the automatic time/time zone switches, often several times, until it corrects. But it reverts to UTC each time the PC is started. Perhaps I should set it manually.

JackE

>>>Boot Option Menu and select Ubuntu>>>

Try moving grub to the top of the boot order. Jack E/NJ

MaClane

I asked you about the time zone because this difference between systems usually causes this error you describe.
Manually change the Windows spindle so that it fits Mint and see if the error is resolved.

https://www.maketecheasier.com/fix-windows-linux-show-different-times/

WJB-2

Thanks @MaClane and @JackE. Fixed clock via MS Windows, but Grub/boot issue remains. Didn't get far with JackE's suggestion, though am providing details in two concurrent replies to benefit future forum searches. It is likely not worth anyone troubling themselves further on this one. Because I'm about to place Windows 10 version 1809 on either FDD or external SSD using AOEMI Disk Partition Assistant, then remove Windows from the E1. Meaning once support for 1809 ends, I'll happily be done with Microsoft. I'd prefer waiting for 1903, but Microsoft is so pathetic getting its act together I can't be bothered to wait.

A post at "Linux Mint Forums" suggested problems identical or similar to mine are common to Aspire. The comments, which I'm not necessarily endorsing, suggest ACER along with other major PC manufacturers is intentionally unhelpful to Linux.

Anyway, per JackE I selected Ubuntu from Boot Option Menu (below) to "Try moving grub to the top of the boot order."

1. Windows Boot Manager (ST500LT012-1DG142)
2. ubuntu (ST500LT012-1DG142)
3. HDD1: (ST500LT012-1DG142)

You get GNU GRUB 2.02 offering:

*Linux Mint 19.1 Xfce
Advanced Options for Linux Mint 19.1 Xfce
Windows Boot Manager (on /dev/sda2)

System Settings

Nothing there to work with but System Settings.  Yet no "Ubuntu" available:

1. Windows Boot Manager
2. HDD: ST500LT012-1DG142
3. ATPI CDROM: MATSHI TADVD-RAM UJ8E0
4. USB FDD:
5. Network Boot--IPV4:
6. USB HDD:
7. USB CDROM:
8. Network Boot--IPV6:

Finally I went into Windows 10 System Settings where there's an option to select default OS. But as I expected the only choice in the drop-down was Windows 10.

Following in a separate reply are Ubuntu terminal results for "sudo efibootmgr" and "sudo update-grub."

WJB-2

Before running the following two Terminal commands I tried another of multiple suggestions for dual boot trouble, which is booting with shift down. This did nothing but freeze the Windows Boot Loader. So I ran sudo efibootmgr and got this:

wjb2@wjb2-Aspire-E1-731:~$ sudo efibootmgr
[sudo] password for wjb2:        
BootCurrent: 0002
Timeout: 0 seconds
BootOrder: 0001,0002,0000
Boot0000* HDD1:
Boot0001* Windows Boot Manager
Boot0002* ubuntu
wjb2@wjb2-Aspire-E1-731:~$

Next I ran sudo update-grub and got this:

wjb2@wjb2-Aspire-E1-731:~$ sudo update-grub
[sudo] password for wjb2:        
Sourcing file `/etc/default/grub'
Sourcing file `/etc/default/grub.d/50_linuxmint.cfg'
Generating grub configuration file ...
Found linux image: /boot/vmlinuz-4.15.0-52-generic
Found initrd image: /boot/initrd.img-4.15.0-52-generic
Found linux image: /boot/vmlinuz-4.15.0-51-generic
Found initrd image: /boot/initrd.img-4.15.0-51-generic
Found linux image: /boot/vmlinuz-4.15.0-20-generic
Found initrd image: /boot/initrd.img-4.15.0-20-generic
Found Windows Boot Manager on /dev/sda2@/EFI/Microsoft/Boot/bootmgfw.efi
Adding boot menu entry for EFI firmware configuration
done

wjb2@wjb2-Aspire-E1-731:~$

No change. Mint via Ubuntu only available through Boot Option Menu. Over at "Linux Mint Forums" it was suggested to "disconnect all the drives except the Mint one, and then do a normal install of Mint. Then reconnect the other drives, and change the boot order in the BIOS to make the Mint drive first. Then you only have to use the boot options when you want to go into Windows." Nice forum; good, helpful folks over there. But I've already spent too much time on a wretched OS, Windows, that I just can't wait to be rid of.

With thanks for the inputs.

JackE

>>>Anyway, per JackE I selected Ubuntu from Boot Option Menu (below) to "Try moving grub to the top of the boot order."

Windows Boot Manager (ST500LT012-1DG142)

ubuntu (ST500LT012-1DG142)

HDD1: (ST500LT012-1DG142)>>>

Not sure if I'm following you? Is this your order in the BIOS Boot Tab or not? Do you see something like the image below in the  BIOS Boot tab or not? Jack E/NJ

WJB-2

Sorry @JackE, photos always best for perspective. You quoted the Boot Manager's Boot Option Menu, shown here:

Selecting Ubuntu brings you GRUB, here:

From there, selecting "System Setup" or alternately hitting F2 at boot/reboot, gives you the EFI Boot Mode settings with Boot Priority Order shown here:

See, no EFI File Boot for GRUB whatsoever in the settings. My understanding for recent Mint versions is that when you select Dual Installation -- whether adjusting the partitions manually or allowing it to be done automatically, as I chose -- you're supposed to be asked to set your default OS. I received no such option. While that concerned me I figured I'd just do it later with the Boot Manager. But while the Boot Option Menu has Ubuntu, it's not available in the EFI/BIOS boot priority order as you see above.

Essentially, I seem to have exhausted everything I and others can think of, and see no way to make Mint/Ubuntu/GRUB 2.02 the default.

JackE

Did you select (or enter from the keyboard) the actual grub EFI as trusted in the BIOS setup Security tab? Sometimes the EFI file must be actually entered letter for letter from the keyboard because selecting/highlighting doesn't seem to automatically enter it into the BIOS memory. See step #10 in this link https://community.acer.com/en/discussion/comment/598047/#Comment_598047   Jack E/NJ

WJB-2

Outstanding instructions, @JackE. I easily clicked my way right through. Well, up until the question, "Do you wish to add this file to allowable database?" required a "Boot Description." Luckily, as I fumbled about trying to determine the response, I caused a box to appear with the four-letter word answer. No, no, not THAT kind of four-letter word; those are reserved for Microsoft. Speaking of which, your opening comment in the instructions, "You'll forget that Win is even there and available should you ever need it for something" is tempting. But wouldn't best practice be to let Windows do its patches, updates, upgrades, etc. at least once a month? Otherwise one could be in for what I experienced after unpacking the E1 back in late 2014 -- an hour or so of updates followed by a lengthy system cleaning that lasted well into the wee morning hours.

MaClane

Good Morning WJB-2 !

The issue of patches and updates of Windows 10 is that they often end up changing some of the Kernel's configuration and in this way Grub is affected.
In most cases, Grub simply loses the system function by booting Windows.
That way you would have to reassemble the Grub entries and reactivate it again.

WJB-2

MaClane said:

Good Morning WJB-2 !

The issue of patches and updates of Windows 10 is that they often end up changing some of the Kernel's configuration and in this way Grub is affected.
In most cases, Grub simply loses the system function by booting Windows.
That way you would have to reassemble the Grub entries and reactivate it again.

Well, @MaClane, your sobering yet highly valuable information clarifies claims that Windows Updater damaged Linux partitions. Your explanation must relate to that. Raising two questions:

1. Why grant Windows space on a Linux PC knowing it can damage the kernel?
2. Windows' automatic updates can be deactivated, yet why retain highly "buggy" Windows if we can't let it patch, update, etc.?

Before @JackE shared his easy fix, I planned to have AOMEI Partition Assistant create an executable Windows 10 version 1809 on a FD or external SSD. I would then delete the last Windows I maintain on a PC. When 1809 support ends, I believe I could not install version 1903 on a non-Windows system despite the Windows Key remaining within the UEFI/BIOS in perpetuity. However, my ACER Android 8.1 tablet has Microsoft's applications plus One Drive online service. That 10-inch tablet is all I need should a so far seemingly unlikely Libre Office compatibility issue arise.

I suppose most Linux users who retain Microsoft/MS Windows are guarding against compatibility quirks and/or play certain games. I keep it for now simply as a ruse. Because as a semi-retired print and broadcast journalist consulting media and telecommunications companies it would be awkward at best should a client notice a non-Microsoft GUI. Yet the "joke's on them" because I haven't owned an MS Office product in years and must use One Drive. And that can be done from any computing device using Linux to Android to Mac OS.

Well anyway, much thanks for the highly helpful, valuable information. I think.

MaClane

The reality is that unfortunately Microsoft has always tried to somehow prevent the use of dual-boot with Linux, especially since the releases of version 10.
Even Intel (with RST Raid implementation) ends up preventing those with less knowledge from getting an installation on systems with this feature.

I myself have a multiple boot system:
WIndows 7, Windows 10, Debian, Kubunto and Kali.
Each one with its own utilities.

As it is known, Microsoft will launch in the second half of 2019 the new version of WSL (acronym Windows Subsystem for Linux) will be based on this internally customized Linux kernel.
"Custom internally" read: "let's remove all the good that Linux has and leave only what is of interest to us".