PDA

View Full Version : [SOLVED] Invalid Signature/No Such Device when Dual-booting with Windows 7



marlowp
October 21st, 2012, 07:26 PM
Hello,

I've searched for days looking for an answer but have been unable to find anything that works - although several people have reported similar situations.

I recently bought a laptop which came pre-loaded with Windows 7, and I want to have it dual-booted with Ubuntu 12.04 LTS. The laptop has two separate hard drives. Windows 7 is loaded into the MBR of the first hard drive, and I've loaded Ubuntu 12.04 LTS onto the second hard drive, with a separate boot partition on the second hard drive.

However, after installing Ubuntu, the Grub2 (v1.99) gives the following error whenever I attempt to load Windows 7.



error: no such device: 664A687A4A6848BF
error: invalid signature.


Because I installed Ubuntu on the second hard drive, I of course needed to change the boot order in the BIOS so that the Grub boot menu would appear. I know that Grub was installed in the boot partition, and not in the MBR on the first disk, nor the MBR on the second. I can get into Windows 7, if I enter the BIOS and change the boot order back to the first hard drive.

I've been using Ubuntu/Linux for years, but it's been a long time since I've done a dual-boot, so I'm by no means an expert when it comes to Grub.

As mentioned, I've come across several articles, some even depicting the same behaviour - that they can boot into either OS as long as they change the boot order within the BIOS. Here is another piece of information that I haven't seen anywhere else. If I boot into Windows 7 FIRST, then RESTART and change the boot order for Ubuntu. If I select Windows 7 from the Grub menu, it will boot successfully - but I had to have booted into Windows 7 successfully before changing the boot order. Once I physically shutdown the laptop, I'm back into the same scenario that Grub will not boot Windows 7.

So in summary - can boot into Windows 7 or Ubuntu if I change the boot order. Grub will ONLY boot Windows 7 if I have already successfully booted into Windows 7, then change the boot order for Ubuntu after a RESTART (not a shutdown).

Also, neither hard drive appears to be using GPT, and the BIOS has UEFI disabled.

Here's what I've tried.

From Ubuntu 12.04

Reissuing the os-prober command and update Grub:



sudo os-prober
sudo update-grub


No change.

I tried adding the insmod part_msdos to /etc/grub.d/40_custom then updating grub:


sudo update-grub

Again no change.

I followed steps in from https://wiki.archlinux.org/index.php/GRUB2#Boot_Microsoft_Windows_installed_in_BIOS-MBR_mode

Which stated to add the following into either /etc/grub.d/40_custom or /boot/grub/custom.cfg:



menuentry "Microsoft Windows Vista/7/8 BIOS-MBR" {
insmod part_msdos
insmod ntfs
insmod search_fs_uuid
insmod ntldr
search --fs-uuid --no-floppy --set=root --hint-bios=hd0,msdos1 --hint-efi=hd0,msdos1 --hint-baremetal=ahci0,msdos1 664A687A4A6848BF
ntldr /bootmgr
}


Then to regenerate the grub.cfg:


grub-mkconfig -o /boot/grub/grub.cfg

But when attempting to load into Windows, it complained about not understanding any of the hint arguments.

This was the original device.map file:



(hd0) /dev/disk/by-id/ata-Hitachi_HTS727575A9E364_J3740084HJHE0E
(hd1) /dev/disk/by-id/ata-SanDisk_SSD_i100_8GB_122900159311
(hd2) /dev/disk/by-id/ata-Hitachi_HTS727575A9E364_J3740084HJEZDE


I also tried changing these to the following:



(hd0) /dev/sda
(hd1) /dev/sdb
(hd2) /dev/sdc


Which also didn't affect anything.

Here is the Windows 7 menu entry generated by Grub:



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 664A687A4A6848BF
chainloader +1
}



From Windows 7

From windows, I tried all the steps using EasyBCD to modify the Windows 7 boot menu - and all it does is load into the GRUB4DOS prompt. It does not actually launch Ubuntu. Plus, I'd very much prefer to use Grub as my primary boot loader.

Before anybody suggests placing Grub in the MBR of the first hard disk, I do not want to do this. I will be updating to Windows 8 at some point, and I want to keep it as "Windows-only" as possible.

For more information, here is my fdisk output:



Disk /dev/sda: 750.2 GB, 750156374016 bytes
255 heads, 63 sectors/track, 91201 cylinders, total 1465149168 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disk identifier: 0x8df46ea1

Device Boot Start End Blocks Id System
/dev/sda1 * 2048 206847 102400 7 HPFS/NTFS/exFAT
/dev/sda2 206848 1419153407 709473280 7 HPFS/NTFS/exFAT
/dev/sda3 1419153408 1465147391 22996992 27 Hidden NTFS WinRE

Disk /dev/sdb: 8012 MB, 8012390400 bytes
246 heads, 40 sectors/track, 1590 cylinders, total 15649200 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x74f02dea

Device Boot Start End Blocks Id System
/dev/sdb1 2048 15646719 7822336 73 Unknown

Disk /dev/sdc: 750.2 GB, 750156374016 bytes
255 heads, 63 sectors/track, 91201 cylinders, total 1465149168 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disk identifier: 0x92cda70e

Device Boot Start End Blocks Id System
/dev/sdc1 * 2048 976895 487424 83 Linux
/dev/sdc2 978942 1465147391 732084225 5 Extended
Partition 2 does not start on physical sector boundary.
/dev/sdc5 1433899008 1465147391 15624192 82 Linux swap / Solaris
/dev/sdc6 978944 1433899007 716460032 83 Linux

Partition table entries are not in disk order


Here is my BootInfo script output:



Boot Info Script 0.61 [1 April 2012]


============================= Boot Info Summary: ===============================

=> Windows is installed in the MBR of /dev/sda.
=> No boot loader is installed in the MBR of /dev/sdb.
=> Grub2 (v1.99) is installed in the MBR of /dev/sdc and looks at sector 1 of
the same hard drive for core.img. core.img is at this location and looks
for (,msdos1)/grub on this drive.

sda1: __________________________________________________ ________________________

File system: ntfs
Boot sector type: Windows Vista/7: NTFS
Boot sector info: No errors found in the Boot Parameter Block.
Operating System:
Boot files: /bootmgr /BOOT/BCD

sda2: __________________________________________________ ________________________

File system: ntfs
Boot sector type: Windows Vista/7: NTFS
Boot sector info: No errors found in the Boot Parameter Block.
Operating System: Windows 7
Boot files: /Windows/System32/winload.exe

sda3: __________________________________________________ ________________________

File system: ntfs
Boot sector type: Windows Vista/7: NTFS
Boot sector info: No errors found in the Boot Parameter Block.
Operating System:
Boot files: /bootmgr /boot/bcd

sdb1: __________________________________________________ ________________________

File system:
Boot sector type: -
Boot sector info:
Mounting failed: mount: unknown filesystem type ''

sdc1: __________________________________________________ ________________________

File system: ext2
Boot sector type: -
Boot sector info:
Operating System:
Boot files: /grub/grub.cfg /grub/core.img

sdc2: __________________________________________________ ________________________

File system: Extended Partition
Boot sector type: -
Boot sector info:

sdc5: __________________________________________________ ________________________

File system: swap
Boot sector type: -
Boot sector info:

sdc6: __________________________________________________ ________________________

File system: ext4
Boot sector type: -
Boot sector info:
Operating System: Ubuntu 12.04.1 LTS
Boot files: /etc/fstab

============================ Drive/Partition Info: =============================

Drive: sda __________________________________________________ ___________________

Disk /dev/sda: 750.2 GB, 750156374016 bytes
255 heads, 63 sectors/track, 91201 cylinders, total 1465149168 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes

Partition Boot Start Sector End Sector # of Sectors Id System

/dev/sda1 * 2,048 206,847 204,800 7 NTFS / exFAT / HPFS
/dev/sda2 206,848 1,419,153,407 1,418,946,560 7 NTFS / exFAT / HPFS
/dev/sda3 1,419,153,408 1,465,147,391 45,993,984 27 Hidden NTFS (Recovery Environment)


Drive: sdb __________________________________________________ ___________________

Disk /dev/sdb: 8012 MB, 8012390400 bytes
246 heads, 40 sectors/track, 1590 cylinders, total 15649200 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes

Partition Boot Start Sector End Sector # of Sectors Id System

/dev/sdb1 2,048 15,646,719 15,644,672 73 Unknown


Drive: sdc __________________________________________________ ___________________

Disk /dev/sdc: 750.2 GB, 750156374016 bytes
255 heads, 63 sectors/track, 91201 cylinders, total 1465149168 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes

Partition Boot Start Sector End Sector # of Sectors Id System

/dev/sdc1 * 2,048 976,895 974,848 83 Linux
/dev/sdc2 978,942 1,465,147,391 1,464,168,450 5 Extended
/dev/sdc5 1,433,899,008 1,465,147,391 31,248,384 82 Linux swap / Solaris
/dev/sdc6 978,944 1,433,899,007 1,432,920,064 83 Linux


"blkid" output: __________________________________________________ ______________

Device UUID TYPE LABEL

/dev/sda1 664A687A4A6848BF ntfs SYSTEM
/dev/sda2 18E6EDC8E6EDA66A ntfs
/dev/sda3 364E3D404E3CF9E7 ntfs SAMSUNG_REC
/dev/sdc1 056cb02c-0533-48c7-ba52-0d14232dba27 ext2
/dev/sdc5 a1f0f1d0-1e4f-42d8-a282-488ce88b5244 swap
/dev/sdc6 a10ae001-2d6c-44d9-9e6d-fade7d25a368 ext4

================================ Mount points: =================================

Device Mount_Point Type Options

/dev/sdc1 /boot ext2 (rw)
/dev/sdc6 / ext4 (rw,errors=remount-ro)


============================= sdc1/grub/grub.cfg: ==============================

--------------------------------------------------------------------------------
#
# DO NOT EDIT THIS FILE
#
# It is automatically generated by grub-mkconfig using templates
# from /etc/grub.d and settings from /etc/default/grub
#

### BEGIN /etc/grub.d/00_header ###
insmod part_msdos
if [ -s $prefix/grubenv ]; then
set have_grubenv=true
load_env
fi
set default="0"
if [ "${prev_saved_entry}" ]; then
set saved_entry="${prev_saved_entry}"
save_env saved_entry
set prev_saved_entry=
save_env prev_saved_entry
set boot_once=true
fi

function savedefault {
if [ -z "${boot_once}" ]; then
saved_entry="${chosen}"
save_env saved_entry
fi
}

function recordfail {
set recordfail=1
if [ -n "${have_grubenv}" ]; then if [ -z "${boot_once}" ]; then save_env recordfail; fi; fi
}

function load_video {
insmod vbe
insmod vga
insmod video_bochs
insmod video_cirrus
}

insmod part_msdos
insmod ext2
set root='(hd2,msdos6)'
search --no-floppy --fs-uuid --set=root a10ae001-2d6c-44d9-9e6d-fade7d25a368
if loadfont /usr/share/grub/unicode.pf2 ; then
set gfxmode=auto
load_video
insmod gfxterm
insmod part_msdos
insmod ext2
set root='(hd2,msdos1)'
search --no-floppy --fs-uuid --set=root 056cb02c-0533-48c7-ba52-0d14232dba27
set locale_dir=($root)/grub/locale
set lang=en_CA
insmod gettext
fi
terminal_output gfxterm
if [ "${recordfail}" = 1 ]; then
set timeout=-1
else
set timeout=10
fi
### END /etc/grub.d/00_header ###

### BEGIN /etc/grub.d/05_debian_theme ###
set menu_color_normal=white/black
set menu_color_highlight=black/light-gray
if background_color 44,0,30; then
clear
fi
### END /etc/grub.d/05_debian_theme ###

### BEGIN /etc/grub.d/10_linux ###
function gfxmode {
set gfxpayload="${1}"
if [ "${1}" = "keep" ]; then
set vt_handoff=vt.handoff=7
else
set vt_handoff=
fi
}
if [ "${recordfail}" != 1 ]; then
if [ -e ${prefix}/gfxblacklist.txt ]; then
if hwmatch ${prefix}/gfxblacklist.txt 3; then
if [ ${match} = 0 ]; then
set linux_gfx_mode=keep
else
set linux_gfx_mode=text
fi
else
set linux_gfx_mode=text
fi
else
set linux_gfx_mode=keep
fi
else
set linux_gfx_mode=text
fi
export linux_gfx_mode
if [ "${linux_gfx_mode}" != "text" ]; then load_video; fi
menuentry 'Ubuntu, with Linux 3.2.0-32-generic' --class ubuntu --class gnu-linux --class gnu --class os {
recordfail
gfxmode $linux_gfx_mode
insmod gzio
insmod part_msdos
insmod ext2
set root='(hd2,msdos1)'
search --no-floppy --fs-uuid --set=root 056cb02c-0533-48c7-ba52-0d14232dba27
linux /vmlinuz-3.2.0-32-generic root=UUID=a10ae001-2d6c-44d9-9e6d-fade7d25a368 ro quiet splash $vt_handoff
initrd /initrd.img-3.2.0-32-generic
}
menuentry 'Ubuntu, with Linux 3.2.0-32-generic (recovery mode)' --class ubuntu --class gnu-linux --class gnu --class os {
recordfail
insmod gzio
insmod part_msdos
insmod ext2
set root='(hd2,msdos1)'
search --no-floppy --fs-uuid --set=root 056cb02c-0533-48c7-ba52-0d14232dba27
echo 'Loading Linux 3.2.0-32-generic ...'
linux /vmlinuz-3.2.0-32-generic root=UUID=a10ae001-2d6c-44d9-9e6d-fade7d25a368 ro recovery nomodeset
echo 'Loading initial ramdisk ...'
initrd /initrd.img-3.2.0-32-generic
}
submenu "Previous Linux versions" {
menuentry 'Ubuntu, with Linux 3.2.0-29-generic' --class ubuntu --class gnu-linux --class gnu --class os {
recordfail
gfxmode $linux_gfx_mode
insmod gzio
insmod part_msdos
insmod ext2
set root='(hd2,msdos1)'
search --no-floppy --fs-uuid --set=root 056cb02c-0533-48c7-ba52-0d14232dba27
linux /vmlinuz-3.2.0-29-generic root=UUID=a10ae001-2d6c-44d9-9e6d-fade7d25a368 ro quiet splash $vt_handoff
initrd /initrd.img-3.2.0-29-generic
}
menuentry 'Ubuntu, with Linux 3.2.0-29-generic (recovery mode)' --class ubuntu --class gnu-linux --class gnu --class os {
recordfail
insmod gzio
insmod part_msdos
insmod ext2
set root='(hd2,msdos1)'
search --no-floppy --fs-uuid --set=root 056cb02c-0533-48c7-ba52-0d14232dba27
echo 'Loading Linux 3.2.0-29-generic ...'
linux /vmlinuz-3.2.0-29-generic root=UUID=a10ae001-2d6c-44d9-9e6d-fade7d25a368 ro recovery nomodeset
echo 'Loading initial ramdisk ...'
initrd /initrd.img-3.2.0-29-generic
}
}
### END /etc/grub.d/10_linux ###

### BEGIN /etc/grub.d/20_linux_xen ###
### END /etc/grub.d/20_linux_xen ###

### BEGIN /etc/grub.d/20_memtest86+ ###
menuentry "Memory test (memtest86+)" {
insmod part_msdos
insmod ext2
set root='(hd2,msdos1)'
search --no-floppy --fs-uuid --set=root 056cb02c-0533-48c7-ba52-0d14232dba27
linux16 /memtest86+.bin
}
menuentry "Memory test (memtest86+, serial console 115200)" {
insmod part_msdos
insmod ext2
set root='(hd2,msdos1)'
search --no-floppy --fs-uuid --set=root 056cb02c-0533-48c7-ba52-0d14232dba27
linux16 /memtest86+.bin console=ttyS0,115200n8
}
### END /etc/grub.d/20_memtest86+ ###

### BEGIN /etc/grub.d/30_os-prober ###
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 664A687A4A6848BF
chainloader +1
}
menuentry "Windows Recovery Environment (loader) (on /dev/sda3)" --class windows --class os {
insmod part_msdos
insmod ntfs
set root='(hd0,msdos3)'
search --no-floppy --fs-uuid --set=root 364E3D404E3CF9E7
drivemap -s (hd0) ${root}
chainloader +1
}
### END /etc/grub.d/30_os-prober ###

### BEGIN /etc/grub.d/40_custom ###
# This file provides an easy way to add custom menu entries. Simply type the
# menu entries you want to add after this comment. Be careful not to change
# the 'exec tail' line above.
### END /etc/grub.d/40_custom ###

### BEGIN /etc/grub.d/41_custom ###
if [ -f $prefix/custom.cfg ]; then
source $prefix/custom.cfg;
fi
### END /etc/grub.d/41_custom ###
--------------------------------------------------------------------------------

=================== sdc1: Location of files loaded by Grub: ====================

GiB - GB File Fragment(s)

= grub/core.img 2
= grub/grub.cfg 1
= initrd.img-3.2.0-29-generic 57
= initrd.img-3.2.0-32-generic 60
= vmlinuz-3.2.0-29-generic 21
= vmlinuz-3.2.0-32-generic 21

=============================== sdc6/etc/fstab: ================================

--------------------------------------------------------------------------------
# /etc/fstab: static file system information.
#
# Use 'blkid' to print the universally unique identifier for a
# device; this may be used with UUID= as a more robust way to name devices
# that works even if disks are added and removed. See fstab(5).
#
# <file system> <mount point> <type> <options> <dump> <pass>
proc /proc proc nodev,noexec,nosuid 0 0
# / was on /dev/sdc6 during installation
UUID=a10ae001-2d6c-44d9-9e6d-fade7d25a368 / ext4 errors=remount-ro 0 1
# /boot was on /dev/sdc1 during installation
UUID=056cb02c-0533-48c7-ba52-0d14232dba27 /boot ext2 defaults 0 2
# swap was on /dev/sdc5 during installation
UUID=a1f0f1d0-1e4f-42d8-a282-488ce88b5244 none swap sw 0 0
--------------------------------------------------------------------------------

=================== sdc6: Location of files loaded by Grub: ====================

GiB - GB File Fragment(s)

= initrd.img 60
= initrd.img.old 57
= vmlinuz 21
= vmlinuz.old 21

========= Devices which don't seem to have a corresponding hard drive: =========

sdd

=============================== StdErr Messages: ===============================

xz: (stdin): Compressed data is corrupt
awk: cmd. line:36: Math support is not compiled in
awk: cmd. line:36: Math support is not compiled in
awk: cmd. line:36: Math support is not compiled in
awk: cmd. line:36: Math support is not compiled in
awk: cmd. line:36: Math support is not compiled in
awk: cmd. line:36: Math support is not compiled in
awk: cmd. line:36: Math support is not compiled in
awk: cmd. line:36: Math support is not compiled in
awk: cmd. line:36: Math support is not compiled in
awk: cmd. line:36: Math support is not compiled in


Any ideas/help/assistance would be hugely appreciated.

oldfred
October 21st, 2012, 09:57 PM
With grub2 1.99 we have seen where it says no such device and then boots after a bit of a delay.

Your recovery has this but your Windows does not.

drivemap -s (hd0) ${root}

I thought anytime you boot from another drive like your hd2 or sdc, that you need the drivemap to reset the BIOS setting so Windows thinks it still is on hd0 or drive0. That may have been more for XP as it is hard coded.

You can also experiment with removing set root or the search line. If set root is correct the search is not required or if using search it overides the set root setting. That is to allow for cases like yours where a flash drive becomes sdb and changes drive order. Boot drive in BIOS/grub is always hd0. On my system then the remaining drives are in SATA port order. But when I plug in a flash drive order may get reset. I use entires like Cavsfans that do not have search so set root has to be correct. Sometimes when booting from another drive or plugging in a flash drive I have to use e in grub menu and change the hdX to Y as the number has changed

.How to: Create a Customized GRUB2 Screen that is Maintenance Free.- Cavsfan
https://help.ubuntu.com/community/MaintenanceFreeCustomGrub2Screen

marlowp
October 24th, 2012, 04:12 AM
Thank you for your help.

Unfortunately none of it has seemed to help. Taking the set root='(hd0,msdos1)' had no affect. Removing the search line got rid of the no such device error, but the invalid signature error remained.

I also followed the steps outlined in the article you supplied from Cavsfan, which also did not change anything with respect to the Windows 7 boot load.

I went a step further, and reinstalled Ubuntu in the MBR of the second disk (I really don't want to have to install it in the MBR of the first disk). After all, if I'm having problems getting Grub to boot to Windows drive, I'd hate to have it reversed, where it would recognise Windows being in the MBR of the first drive, but unable to boot into Ubuntu.

Still, this has not allowed me to boot into Windows, albeit with a different error.



error: no such device: 664A687A4A6848BF
error: no such partition.


The no such device is the same, however instead of complaining about an invalid signature, now it's complaining about the partition.

I then went ahead and updated my Grub to 2.00 - but still it had the same affect.

Here is the menu entry contents generated by Grub:



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 664A687A4A6848BF
else
search --no-floppy --fs-uuid --set=root 664A687A4A6848BF
fi
chainloader +1


Nothing changes if I remove the line containing set root, nor does it change if I remove either of the search lines as well (also removing the if structure of course). If I take out the entire if structure, along with the search commands, the no such device error goes away, but I'm still left with the no such partition error.

If anybody has any kind of an explanation for me, it'd be great to know before I pull all my hair out! ;)

oldfred
October 24th, 2012, 04:53 AM
Not sure as I am booting Quantel from sda, but it is in sdc and I normally boot precise from sdc.

But my XP shows the drivemap command:


menuentry 'Microsoft Windows XP Professional (on /dev/sda1)' --class windows --class os $menuentry_id_option 'osprober-chain-04B05B70B05B6768' {
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 04B05B70B05B6768
else
search --no-floppy --fs-uuid --set=root 04B05B70B05B6768
fi
drivemap -s (hd0) ${root}
chainloader +1
}

marlowp
October 27th, 2012, 03:57 PM
Here's the latest update. I tried using a drivemap entry as you suggested, with the same results.

I also went back, and reinstalled Ubuntu, just to get a vanilla install of Grub v1.99 (since I had upgraded to v2.00), and tried the drivemap command there as well, again with no luck.

At this point, I'm willing to try and put more effort into seeing if I can get it to dual boot using the Windows boot loader/EasyBCD, but that hasn't worked either - just takes me into the Grub4Dos command line prompt.

Any other ideas, or even possible explanations would be appreciated. Since I cannot dual boot (right now) from either hard drive, could there be something unusual with my laptop setup, perhaps it's BIOS? Seems to me, that during boot, both hard drives are not being recognised properly - whether it's booting from Ubuntu/Grub or Windows.

I'm open to any comments, even something "out of the box".

Given everything, do you think it's worthwhile to try and place Grub in the MBR of the first disk? I want to make sure I don't pooch Window of course.

Thanks for your time.

oldfred
October 27th, 2012, 04:17 PM
We have seen similar issues with older BIOS and IDE drives where the BIOS setting could not be remapped and you could only install grub to sda where Windows was. But newer BIOS do not usually have that issue.

Perhaps a setting in BIOS. Are you in AHCI mode. If Windows is not already you may have to add a driver before changing the setting in BIOS.

Also settings like quick boot or similar names can interfere with 'normal' booting.

marlowp
October 28th, 2012, 12:19 AM
Thank you very much for all the responses on this, I really appreciate it.

It's now working thanks to you - my system was already using ACHI, so all I had to do was disable the quick boot as you suggested.

Thanks again!