Dual boot system: unable to boot Windows

Hebang · 2014-12-08 10:59:59

Hello guys!

I've read a lot of resources about this problem, but I didn't find any solution yet. Hope you can help me.

I'm trying to install Arch in a disk that already has a Windows partition.

I've followed all steps described in Begginers Instalation Guide but, after Grub is installed and boot files are generated, after the reboort I'm able to boot in the new Arch system, but Windows keeps unreachable.
I receive an error just saying that the system couldn't boot properly (meaningless, I know).

My harddrive is setted with a GPT table.

So, I've followed what's described in arch's guide: I've created a separated boot partition of 300Mb, formatted as EXT4, and an extra UEFI partition, formatted as ef00 in gparted, with ~3Mb.

I've installed Grub normally in boot partition and created the boot files.

After all, Windows keeps refusing to boot.

I can't format Windows partition, since I still use it for my job and I'll spend a lot of time I don't have to reconfigure everything.

I just need to know the correct step-by-step I need to follow my case.
The whole Arch System is configured and running well (without UI yet). So, I'm just having troubles with boot manager.

Some extra informations:
MACHINE: MSI GT70 2OD
DISK TABLE TIPE: GPT
WINDOWS INSTALLED: Windows 7 64bits

If you guys need any extra information, feel free to ask.
I'll provide it as soon as possible.

Thanks in advance for your support, and have a nice week o/

clfarron4 · 2014-12-08 13:07:45

Was the WIndows 7 installation using UEFI or Legacy to boot before you installed Arch?

Hebang · 2014-12-08 13:18:52

Hello!

Thanks for your quick response.

I'm really not sure about it.

In fact, my OS instalation order was:
Windows 7, then Ubuntu and, now, I'v formatted Ubuntu partition to install Arch.

So, I guess Windows used to boot using its default boot mode, since it was the very first OS on disk.

Is there a way to discover this information?

Please tell me and I'll provide it ASAP.

Thanks!

Head_on_a_Stick · 2014-12-08 13:39:43

Hebang wrote:

So, I've followed what's described in arch's guide: I've created a separated boot partition of 300Mb, formatted as EXT4, and an extra UEFI partition, formatted as ef00 in gparted, with ~3Mb.
I've installed Grub normally in boot partition and created the boot files.

This is not what the guide advises.

To boot up in EFI-mode, it is simplest to mount /boot to the EFI system partition (the one Windows has already generated).

Also, "ef00" is a partition type rather than a "format" -- if you were creating a new one, it would have to be formatted to FAT(32).
However, as I said you should be sharing the ESP that was already there.

I think we need to see the output of:

# gdisk -l /dev/sda
lsblk -f

You must be booting in EFI-mode: a GPT disk needs a BIOS boot partition (ef02) to boot in non-EFI mode...

I can only presume GRUB cannot find Windows because it is expecting the Windows bootloader to be occupying the same partition as /boot...

Hebang · 2014-12-08 13:48:35

Hello!

Thanks for your reply!

Maybe I've misunderstood the tutorial.

In fact, I've created both boot and UEFI partitions, and formatted them as EXT4 and FAT32, respectively.

So, I've mounted my root partition in /mnt, created /mnt/boot and mounted the boot partition in /mnt/boot.
The UEFI partition wasn't even mounted anywhere.

About using the partition created previously by Windows, I've checked my partition table a priori and this partition didn't exist. So, I've created a new one.

As soon I get home, I'll print out my partition table and send for you guys.

Thanks again for your support so far!

Hebang · 2014-12-09 01:07:32

Hello guys!

Sorry for the retard sending the commands output.

Below are the link to the commands output (PNG format, since I'm unable to paste the command from notebook):

Lsblk output
Gdisk output

If you guys need any extra informations, feel free to contact me.

Thanks in advance!

Last edited by Hebang (2014-12-09 15:15:12)

Hebang · 2014-12-09 01:27:24

With the partition table above, grub-install returns this:

Grub output

Last edited by Hebang (2014-12-09 15:03:20)

clfarron4 · 2014-12-09 13:16:08

OK, you need to read the GRUB Wiki Page, specifically the part about BIOS booting with GPT, because you seem to be aiming for GPT with BIOS/Legacy mode, not GPT with UEFI, based on that partition table.

Hebang · 2014-12-09 13:32:23

clfarron4 wrote:

OK, you need to read the GRUB Wiki Page, specifically the part about BIOS booting with GPT, because you seem to be aiming for GPT with BIOS/Legacy mode, not GPT with UEFI, based on that partition table.

So, in my case, I just need to follow GUID Partition Table (GPT) specific instructions?
The MBR isn't applicable in my case, correct?!

So, if I understood well, I just need:

Create a 1MiB partition of type ef02 and don't format it
Follow the installation process normally, as described in Bios System

Is that right?!
Just to be sure: this new 1MiB partition shouldn't be mounted, since it hasn't formatted, correct?!
So, I'll just mount my root partition on /mnt and leave boot empty.

Thanks for your support so far!

Last edited by Hebang (2014-12-09 13:36:45)

Head_on_a_Stick · 2014-12-09 14:17:25

@OP: Yes, that's right.

The relevant ArchWiki page is here:
https://wiki.archlinux.org/index.php/GU … OS_systems

There are sometimes problems with GPT disks booting non-EFI systems; some workarounds are described here:
http://mjg59.dreamwidth.org/8035.html
http://rodsbooks.com/gdisk/bios.html
Just in case...

It is all a bit strange though because according to the first link I have given above, Windows cannot boot a GPT disk in non-EFI mode.
You didn't change the partition table type of your disk, did you?
If you did, that's why Windows won't boot...

ArchWiki wrote:

Warning: For Windows, there is no support for booting from a BIOS/GPT partitioning scheme.

EDIT: It might be an idea to replace your massive images with thumbnail links before you irritate the mods (and any other forum users with crap/metered connections)...

Last edited by Head_on_a_Stick (2014-12-09 14:18:56)

Hebang · 2014-12-09 15:12:18

Hello!

No, I haven't changed the partition table type.

Before I start to install Arch, the partition was already setted as GPT.

I'll read all the links and follow them.

As soon I have a position, I'll share here.

Again, thanks a lot for all the support so far

Cheers o/

PS: I've removed the images due their sizes and replaced by the respective links.

Hebang · 2014-12-09 15:18:03

About the problem in booting Windows from a GPT partition, why is this happening with Arch?!

As I said before, I've installed Ubuntu and both the OS booted normally, and I haven't made any change on partition table type.

clfarron4 · 2014-12-09 16:48:15

Hebang wrote:

No, I haven't changed the partition table type.
Before I start to install Arch, the partition was already setted as GPT.

Right, in this case (as @Head_on_a_Stick rightly points out), you would have been using EFI with Windows 7, because of the GPT partitioned disk. This would mean that you would have had a small-ish (anything from around 50MB to 200MB) FAT32 partition, known as the EFI system partition which would have booted Windows.

I don't see one in any of your previous posts, so you'll need to re-create this in order to boot Windows.

This would also mean that you should be installing GRUB for a UEFI system, not a BIOS/Legacy system...

Last edited by clfarron4 (2014-12-09 16:49:20)

Hebang · 2014-12-09 17:11:38

Hello!

It's a little bit strange indeed. Before starting install Arch, I've checked my partition table searching for this boot partition created by Windows but it didn't exist

So, just to align the next steps:
Install Grub using UEFI system instructions instead BIOS/Legacy, correct?!

Thanks!

Head_on_a_Stick · 2014-12-09 17:43:19

A few points:

When posting the output of `lsblk -f`, this needs to be done after you have (arch-)chroot'ed into the target root partition, otherwise the mountpoints don't show up.
You claim that you created "an extra EFI partition" -- this is not present in the `gdisk -l` output: why not?
What was the original GRUB install command that was used (as described in the original post)? You can boot into Arch, so clearly that worked...
I really don't understand how Arch managed to boot at all if you were running a non-EFI system from a GPT disk without a BIOS Boot Partition -- this should not be possible!

In short, this thread makes no sense at all.

I think you should use a Windows rescue disk to get Windows booting again.
Then load up the Arch .iso, run `gdisk -l /dev/sda` and post the output here.
Then we can see for sure the partition table used by your Windows installation.

I think you must have deleted one or more of the partitions needed by Windows during the Arch installation proceedure.

Hebang · 2014-12-09 18:28:57

A few points:
When posting the output of `lsblk -f`, this needs to be done after you have (arch-)chroot'ed into the target root partition, otherwise the mountpoints don't show up.
You claim that you created "an extra EFI partition" -- this is not present in the `gdisk -l` output: why not?
What was the original GRUB install command that was used (as described in the original post)? You can boot into Arch, so clearly that worked...
I really don't understand how Arch managed to boot at all if you were running a non-EFI system from a GPT disk without a BIOS Boot Partition -- this should not be possible!

I didn't realized that.
I'll perform all steps again, taking in count the observations above and post the result here.
I think I've taken the SS after a try of making the system work, so maybe I've deleted the partition.
Don't worry, I'll redo all the steps again and give you a more accurate situation

About booting in Arch, in one of my tries I've achieved to install Grub successfully (I don't remember which configuration I've used). Arch loaded perfectly, but Windows not, and after that I've tried many configurations.

I think you must have deleted one or more of the partitions needed by Windows during the Arch installation proceedure.

No, I'm pretty sure I haven't deleted anything.
As I said, before running any command to install Arch I've checked my partition table and no boot partition, from both Windows or Linux, was present.

I'll recreate the steps and give you guys a clearer view about the problem.

Thanks again, and sorry about the messy

Hebang · 2014-12-10 11:23:15

Hello guys!

I've redone all steps related to bootloader and I'm sharing now the two approches I've tried.

EF02 Partition

In this case, I've created a ef02 partition, not formated.
Then, I've mounted / (sda1) and /boot (sda3) partitions under /mnt and then, executed the grub-install command.

The command executed well, no errors.
After that, I've generated config files for grub (grub-mkconfig), placed them in the /boot/grub, exited chroot, umount everything and reboot.

After reboot, the Grub OS selection screen isn't displayed, just the Grub plain text console. But, if i press any key on this screen, BigFoot (a program that came installed in bios machine) tries to load something and nothing happens.

After that, I rebooted with Arch live USB and tried to remount / and /boot partitions under /mnt, but now, the /boot partition was refused to be mounted.

Screenshots below:
Ef02 Partition

EF00 Partition

In this case, I've created a ef00 partition and formatted it as Fat32.

Then, I've made the whole process again:

Mount / (sda1) and /boot (sda3) under /mnt
Chroot
grub-install

In Grub install, the process failed, as shown in the image below:

EF00 Partition

I hope this gives you a more accurate view about my problem.

If you need further informations or command outputs, don't hesitate to ask me for.

Thanks for all the support!

PS: If you guys prefer, you can contact me via personal e-mail.

clfarron4 · 2014-12-10 11:30:26

OK, have you actually tried to restore Windows to a boot-able state and then tried to find out what Windows uses to boot (post the partition layout here if needs be and we'll work it out for you)?

Once we've worked that out, we can work out what set-up you should be using.

Hebang · 2014-12-10 11:32:48

Hello!

No, I haven't tried, since I don't have the instalation media with me anymore.

I can get a new one, just to recovery, however this will take some time.

Is there a way to do that in Arch?

clfarron4 · 2014-12-10 11:39:19

Hebang wrote:

Hello!
No, I haven't tried, since I don't have the instalation media with me anymore.
I can get a new one, just to recovery, however this will take some time.
Is there a way to do that in Arch?

If you want a boot-able Windows, you'll at least need a Windows recovery disk, but you can do it with a Windows installation disk as well. It is easier to sort out Windows problems with Windows software and then get onto other Operating Systems...

There are solutions out there such as Boot-Repair (which I often see for rescuing Linux bootloaders), but I don't know whether they can restore Windows bootloaders.

Last edited by clfarron4 (2014-12-10 11:40:08)

Hebang · 2014-12-10 11:40:58

Ok, I'll find a way to boot on Windows again.

Then, I send you Windows Boot Mode.

Thanks!

TheSaint · 2014-12-10 16:37:00

As far as I could jump back and forth to read your pictures and decipher the results, you should see why efibootmgr is not up into your installation.
What says

ls /sys/firmware/efi/efivars/
pacman -Qs efibootmgr

from inside chroot and install efibootmgr from there, if necessary.
Otherwise, in a particular case you may use from arch iso

mount /dev/sda1 /mnt
pacman -S efibootmgr -r /mnt

We do rather prefer few kbytes here in the forum rather than seeing picture links, if you mind to know how to redirect your results into a file and post the results here, it will improve readability very much.
As second chance you may prefer an Live CD with GUI, for the purpose to inspect files and post on the forum copied files and chrooting into your installation. Arch based live CD are more convenient.

Hebang · 2014-12-10 17:04:51

Thanks TheSaint!!

I didn't know that efibootmgr was a package that should be installed a part.

I thought that it was a file created automatically during grub-install, but for some reason wasn't

I'll give a try as soon I get home and let you know about the result.

Also, I'll try to recover Windows bootloader in order to provide the information asked by clfarron4.

Thanks for the support!

TheSaint · 2014-12-10 17:13:21

If inadvertently you wipe the ESP, then you need to fix windows first and later you will repeat the grub installation.
The win recovery may disregard other boot loader in the ESP.
Once you chroot in your installation you should check if you have os-prober installed, too.

Hebang · 2014-12-10 17:17:50

I got a Win7 CD here.

Tonight I'll recovery Win Bootloader to rebuild boot partition and discover boot mode used by it.

And yes, I've already installed os-prober on my Arch box.

Grub-mkconfig is already recognizing Windows partition perfectly

Thanks!

Arch Linux

#1 2014-12-08 10:59:59