Boot problem with grub2

miros84 · 01-07-2013, 01:37 PM

I have installed Mint and Windows 7 on different partition.
I boot Mint and added that to 40_custom

Code:

menuentry “Windows 7″ {
set root=(hd0,1)
chainloader /bootmgr
}

and Windows is installed in

Code:

/dev/sda1: LABEL="Windows7" UUID="0484706A8470605A" TYPE="ntfs"

When I restart and try to boot Windows 7, it shows me error.

Code:

Invalid Signature TYPE="ntfs"

What colud be the problem?

Snark1994 · 01-07-2013, 04:41 PM

Where has

Code:

/dev/sda1: LABEL="Windows7" UUID="0484706A8470605A" TYPE="ntfs"

come from? Is that output from a command (if so, which one) or is it something you've put into a file?

Can you also tell us the exact steps you've gone through in order to configure/install grub, please? (i.e. did you follow a particular guide?)

miros84 · 01-08-2013, 01:45 AM

Hi Snark1994,

Command is blkid. It outputs me where is installed Windows 7 and Linux Mint.

About grub I did:

Quote:

grub-install /dev/sda
Add en entry to 40_custom
update-grub

Snark1994 · 01-09-2013, 04:02 AM

Hm. What does

Code:

sudo fdisk -l /dev/sda

print? And can you post your grub.cfg, please?

Regards,

syg00 · 01-09-2013, 04:11 AM

I'm surprised you need to do anything with Mint - been a couple of releases since I looked at it though.
"update-grub" doesn't build a complete grub.cfg ?.

yancek · 01-09-2013, 09:43 AM

Have you run 'sudo os-prober' and 'sudo update-grub' from Mint?

I have Mint 13 and can boot windows 7 with the grub.cfg entry below. You would obviously need to replace the uuid after --set=root with your own:

Quote:

menuentry "Windows 7 (loader) (on /dev/sda1)" --class windows --class os {
insmod part_msdos
insmod ntfs
set root='(hd0,msdos1)'
search --no-floppy --fs-uuid --set=root A0A03A5CA03A395C
chainloader +1
}

miros84 · 01-09-2013, 02:49 PM

Yeah, update-grub found Windows 8 bootloader, because I have Windows 8 installed too.
But I hate Windows 8 bootloader. I prefer Windows 7 loader and that's why I want to chainloader bootmgr instead first 512 bytes.

---------- Post added 01-09-13 at 03:49 PM ----------

Yeah, update-grub found Windows 8 bootloader, because I have Windows 8 installed too.
But I hate Windows 8 bootloader. I prefer Windows 7 loader and that's why I want to chainloader bootmgr instead first 512 bytes.

yancek · 01-09-2013, 05:34 PM

Quote:

Yeah, update-grub found Windows 8 bootloader, because I have Windows 8 installed too.

That would have been useful information for your first post. Grub usually just chainloads to windows and historically their bootloaders have been backward compatible only. The link below indicates it should be possible to do with EasyBCD. Make sure all your 7 boot files are where they need to be. Are both 7 and 8 on primary partitions?:

http://www.youtube.com/watch?v=gSACjBulq5Q

Snark1994 · 01-10-2013, 04:01 AM

Quote:

Originally Posted by miros84

Yeah, update-grub found Windows 8 bootloader, because I have Windows 8 installed too.
But I hate Windows 8 bootloader. I prefer Windows 7 loader and that's why I want to chainloader bootmgr instead first 512 bytes

As yancek said, that's important information. Are you using UEFI to boot or BIOS? The two need very different setup processes (on Arch, anyway)... Could you try running the command I posted,

Code:

sudo fdisk -l /dev/sda

?

My suspicion is that you've got a GPT, and Windows boots with UEFI, so you won't be able to boot using the MBR.

miros84 · 01-11-2013, 01:19 AM

Here it is:

Code:

  Device Boot      Start         End      Blocks   Id  System
/dev/sda1   *      206848   207570943   103682048    7  HPFS/NTFS/exFAT
/dev/sda2       207570944   295598079    44013568    7  HPFS/NTFS/exFAT
/dev/sda3       295598080   315123711     9762816   83  Linux
/dev/sda4       315123712  1953521663   819198976    7  HPFS/NTFS/exFAT

UEFI or Bios. This motherboard is asrock N68. I think it has no UEFI. Should be BIOS.

yancek · 01-11-2013, 09:29 AM

The link below indicates that there have been significant changes to the windows bootloader in windows8 and the sites I visited all suggest installing w8 last.

http://www.7tutorials.com/how-dual-b...-or-windows-xp

Snark1994 · 01-12-2013, 03:35 PM

I managed to install the Arch (Grub 2) bootloader after Windows 8, using https://wiki.archlinux.org/index.php/GRUB2 - but it was a bit of a pain (though I was using UEFI not the old MBR bootloaders).