The wikis are now using the new authentication system.
If you did not migrate your account yet, visit


Jump to: navigation, search

A potential issue with dual booting into Windows with 13.2 on GRUB2-EFI boot loader into recent HP Dimension systems where a new hard disk has been added for the linux install

Some who dual boot do this by adding a new drive to their system rather than allowing OpenSuse to install on the original drive (Advantage - less chance of losing Windows data). OpenSuse will recognise this configuration on an install (with secureboot disabled) if the second disk (sdb) has relevant pre-formated linux partitions (at least 3 plus swap) and with EFI, preserve sda. Access to sda is offered by GRUB2s default boot menu in OpenSuse as the option "Windows Boot Manager" which classically loads from the EFI partition sda2 and is found at /efi/Microsoft/Boot/bootmgfw.efi. There is some noise on the forums about HP UEFI/BIOS but no more than most vendors.

However an attempt at this did not work after an install of OpenSuse 13.2 onto a new from shop but end of line HP Dimension system to which a new hard disk had been added (HP dimensions have spare SATA and power connections but no empty hard drive bay, even if enough room in the box so not ideal). The boot into sda2 (Windows boot manager) failed with classic drive not recognised message. It was easy to establish that sda intact with a BIOS F10/F9 boot into Windows (reordered boot order). Inspection of the grub.cfg file with comparison to an OpenSuse 13.1 system on a same vendor box where also OpenSuse had been installed on a new disk without an issue suggested grub.cfg was fine, as transpired to be the case. No obvious solution existed on the net.

In due course it was discovered that hda was not being given time to initialise with grub2 taking over the boot to hdb too soon. Michaeljenkinson (talk) 22:03, 19 April 2015 (UTC)

Tested on openSUSE

Recommended articles



Related articles