Overclock.net › Forums › Software, Programming and Coding › Operating Systems › Linux, Unix › Getting dual-boot to work?
New Posts  All Forums:Forum Nav:

Getting dual-boot to work? - Page 2

post #11 of 27
That's just because fdisk doesn't support GPT partitions, you can do the same with ` # parted -l `.

Anyway's, open up " /ect/grub.d/40_custom " and enter;
menuentry 'Windows 7 (loader) (on /dev/sda1)' --class windows --class os $menuentry_id_option 'osprober-chain-C412F76C12F761BA' {
    insmod part_msdos
    insmod ntfs
    set root='hd0,msdos1'
    if [ x$feature_platform_search_hint = xy ]; then
      search --no-floppy --fs-uuid --set=root --hint-bios=hd0,msdos1 --hint-efi=hd0,msdos1 --hint-baremetal=ahci0,msdos1  C412F76C12F761BA
      search --no-floppy --fs-uuid --set=root C412F76C12F761BA
    chainloader +1

Just make sure to change the UUID's to that of your Windows Partition. ( use ` # blkid ` )

Edit: I guess I should mention it needs to be the SYSTEM_RESERVED partition as that's where Windows normally keeps it's bootmgr file.
Edited by Shrak - 2/6/13 at 6:56pm
post #12 of 27
Thread Starter 
I presume I edit it with Notepad? I don't have permissions to save that file.
Edited by Sebiale - 2/6/13 at 7:20pm
post #13 of 27
any editor you wish as long as you open it with root permissions.
post #14 of 27
Thread Starter 
I have no idea what command I would use to open a shell script into notepad . . . :S
post #15 of 27
Sudo gedit /etc/grub.d/40_custom

Then simply paste the code in, and make sure to use your own UUIDs.
post #16 of 27
Thread Starter 
K, opened, copied and pasted, and added the UUID I got from the blkid command.

Fingers crossed. smile.gif
post #17 of 27
Thread Starter 
It did not work. frown.gif

The GNU Grub on startup still only lists Linux Mint 14 and the Linux Mint 14 recovery version.
post #18 of 27
Did you run update-grub again?
post #19 of 27
Thread Starter 
Generating grub.cfg ...
Found linux image: /boot/vmlinuz-3.5.0-17-generic
Found initrd image: /boot/initrd.img-3.5.0-17-generic

Do you mean the UUID was supposed to be that of the boot partition? The one I changed them to was the main windows partition (sda3):
sudo blkid
/dev/sda1: UUID="9A24-8C34" TYPE="vfat"
/dev/sda3: UUID="72CA2ED7CA2E96FF" TYPE="ntfs"
/dev/sda4: UUID="044919e8-b0de-47a4-87f7-757fc321dd5f" TYPE="ext4"
/dev/sda6: UUID="ccae7852-73d7-434b-90ae-582c6c272fc2" TYPE="ext4"
/dev/mapper/cryptswap1: UUID="7e3d4e06-f79c-45e3-8018-d07ddd493fee" TYPE="swap"

ETA: I ran Ubuntu's Boot Repair and got this: http://paste2.org/p/2835028

Haven't restarted the computer yet though; it said to make sure the BIOS boots on sda1/EFI/linuxmint/grubx64.efi file, not sure how to do that.

Other message it gave:
The boot files of [The OS now in use - Linux Mint 14 Nadia] are far from the start of the disk. Your BIOS may not detect them. You may want to retry after creating a /boot partition (EXT4, >200MB, start of the disk). This can be performed via tools such as gParted. Then select this partition via the [Separate /boot partition:] option of [Boot Repair]. (https://help.ubuntu.com/community/BootPartition)

Edited by Sebiale - 2/7/13 at 9:09am
post #20 of 27
Not sure what the vfat partition is, normally if there is a SYSTEM_RESERVED then it's ntfs. Unless that is the OEM RECOVERY partition. I'm kind of wondering where /dev/sda2 is, as that would be SYSTEM_RESERVED if /dev/sda1 is RECOVERY. So as far from that list goes, I'd say there isn't a SYSTEM_RESERVED and you would go ahead and use /dev/sda3 as the boot device.

If you run ` parted -l ` it'll give you the labels of the ntfs/vfat partitions if you don't know them.

Grubs message won't show the Windows entry as it's automatically included into the config file via the 40_custom file.

I'm not sure right now and don't have enough time to think of something else currently since I'm at work, but I'll be back on later tonight.
New Posts  All Forums:Forum Nav:
  Return Home
  Back to Forum: Linux, Unix
Overclock.net › Forums › Software, Programming and Coding › Operating Systems › Linux, Unix › Getting dual-boot to work?