lnthai20022
February 10th, 2016, 04:51 PM
Hello,
I have an Asrock H97M Pro4 with an SSD and a SSHD. I disabled fast boot, secure boot in the efi. Then I installed windows 10 on the SSD (formatted as GPT using windows diskpart). Everything is fine. I noticed there is a boot/efi partition that windows 10 created in this disk.
Then i hooked in my SSHD, format it as GPT (using parted) and installed ubuntu 14.04 on it, I selected the custom installation and partition the disk as:
Create a 200MB boot partition on the SSHD
Create a 4gb swap area on the SSHD.
Create an LVM pv, 1 vg and 2 lv
Mapped the /boot to the boot partition create in 1.
Mapped the 2 lv to / and /home
Then finish the rest of the installation.
After the installation i went to the motherboard efi and set Ubuntu as the first boot loader then windows as the 2nd one and rebooted.
I was happy to see grub loaded and correctly recognize my windows 10 installation. The joy went on for a month or so and then suddenly (after a windows update i guess), i no longer see grub. When the machine boot from cold state (shutdown previously), only windows boot loader is present in the motherboard efi thus it boot directly to windows. If i restart the machine and go to motherboard efi i can see 2 boot loaders : windows as the 1st and ubuntu as 2nd. I can switch the order to make grub appear again but the boot order only stay when i reboot, if i shutdown the machine, i lost grub again.
I think i read something about some uefi implementation stop after it found the first boot partition, it it correct? Has anyone experience the same issue?
I have an Asrock H97M Pro4 with an SSD and a SSHD. I disabled fast boot, secure boot in the efi. Then I installed windows 10 on the SSD (formatted as GPT using windows diskpart). Everything is fine. I noticed there is a boot/efi partition that windows 10 created in this disk.
Then i hooked in my SSHD, format it as GPT (using parted) and installed ubuntu 14.04 on it, I selected the custom installation and partition the disk as:
Create a 200MB boot partition on the SSHD
Create a 4gb swap area on the SSHD.
Create an LVM pv, 1 vg and 2 lv
Mapped the /boot to the boot partition create in 1.
Mapped the 2 lv to / and /home
Then finish the rest of the installation.
After the installation i went to the motherboard efi and set Ubuntu as the first boot loader then windows as the 2nd one and rebooted.
I was happy to see grub loaded and correctly recognize my windows 10 installation. The joy went on for a month or so and then suddenly (after a windows update i guess), i no longer see grub. When the machine boot from cold state (shutdown previously), only windows boot loader is present in the motherboard efi thus it boot directly to windows. If i restart the machine and go to motherboard efi i can see 2 boot loaders : windows as the 1st and ubuntu as 2nd. I can switch the order to make grub appear again but the boot order only stay when i reboot, if i shutdown the machine, i lost grub again.
I think i read something about some uefi implementation stop after it found the first boot partition, it it correct? Has anyone experience the same issue?