Ubuntu 10.04 AMD64 Upgrade – Can't Dual Boot Into Windows Vista

[KNC]

Hello,


I have a dual hard-drive system with Windows Vista on the first hard drive and Ubuntu on the second. There was a clean install of Ubuntu 9.10 AMD64 on the second hard drive for a number of months and dual-booting worked just fine. Yesterday I did an upgrade of Ubuntu to 10.04 AMD64 and now the system can not boot into Vista. Boot into Ubuntu works fine.


It is possible to mount and access the first hard drive from within Ubuntu so data loss is not an issue.


Here is the symptom scenario:


Power-on and grub menu displays. Scroll down to the selection for Windows Vista, hit <Enter> and the screen goes black with the cursor blinking in the top left corner. No hard drive activity at all. I have left the system in that state for 5 minutes to remove any impatience on my part from influencing the observations.


Below is the output of boot_info_script*.sh








Boot Info Script 0.55 dated February 15th, 2010


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


=> Grub 2 is installed in the MBR of /dev/sda and looks on the same drive in
partition #1 for /boot/grub.
=> Grub 2 is installed in the MBR of /dev/sdb and looks on the same drive in
partition #1 for /boot/grub.


sda1: __________________________________________________ _______________________


File system: ntfs
Boot sector type: Grub 2
Boot sector info: Grub 2 is installed in the boot sector of sda1 and
looks at sector 275031 of the same hard drive for
core.img, but core.img can not be found at this
location. No errors found in the Boot Parameter Block.
Operating System: Windows Vista
Boot files/dirs: /bootmgr /Boot/BCD /Windows/System32/winload.exe


sda3: __________________________________________________ _______________________


File system: ntfs
Boot sector type: Grub 2
Boot sector info: Grub 2 is installed in the boot sector of sda3 and
looks at sector 275031 of the same hard drive for
core.img, but core.img can not be found at this
location. No errors found in the Boot Parameter Block.
Operating System:
Boot files/dirs: /bootmgr /boot/bcd


sdb1: __________________________________________________ _______________________


File system: ext4
Boot sector type: Grub 2
Boot sector info: Grub 2 is installed in the boot sector of sdb1 and
looks at sector 275031 of the same hard drive for
core.img, but core.img can not be found at this
location.
Operating System: Ubuntu 10.04 LTS
Boot files/dirs: /boot/grub/grub.cfg /etc/fstab /boot/grub/core.img


sdb2: __________________________________________________ _______________________


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


sdb5: __________________________________________________ _______________________


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


=========================== 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 / 512 bytes


Partition Boot Start End Size Id System


/dev/sda1 * 63 1,439,150,894 1,439,150,832 7 HPFS/NTFS
/dev/sda3 1,439,150,895 1,465,144,064 25,993,170 7 HPFS/NTFS




Drive: sdb ___________________ __________________________________________________ ___


Disk /dev/sdb: 1000.2 GB, 1000204886016 bytes
255 heads, 63 sectors/track, 121601 cylinders, total 1953525168 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes


Partition Boot Start End Size Id System


/dev/sdb1 63 1,905,501,779 1,905,501,717 83 Linux
/dev/sdb2 1,905,501,780 1,953,520,064 48,018,285 5 Extended
/dev/sdb5 1,905,501,843 1,953,520,064 48,018,222 82 Linux swap / Solaris




blkid -c /dev/null: __________________________________________________ __________


Device UUID TYPE LABEL


/dev/sda1 327CAEDC7CAE9A5D ntfs HP
/dev/sda3 949CA48C9CA46A86 ntfs FACTORY_IMAGE
/dev/sda: PTTYPE="dos"
/dev/sdb1 300287b9-0224-4c97-85d2-f4e509527005 ext4
/dev/sdb2: PTTYPE="dos"
/dev/sdb5 b1527b9e-073b-42fd-841c-95b91fb7d085 swap
/dev/sdb: PTTYPE="dos"
error: /dev/sdc: No medium found
error: /dev/sdd: No medium found
error: /dev/sde: No medium found
error: /dev/sdf: No medium found


============================ "mount | grep ^/dev output: ===========================


Device Mount_Point Type Options


/dev/sdb1 / ext4 (rw,errors=remount-ro)




=========================== sdb1/boot/grub/grub.cfg: ===========================


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


### BEGIN /etc/grub.d/00_header ###
if [ -s $prefix/grubenv ]; then
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
}
insmod ext2
set root='(hd1,1)'
search --no-floppy --fs-uuid --set 300287b9-0224-4c97-85d2-f4e509527005
if loadfont /usr/share/grub/unicode.pf2 ; then
set gfxmode=640x480
insmod gfxterm
insmod vbe
if terminal_output gfxterm ; then true ; else
# For backward compatibility with versions of terminal.mod that don't
# understand terminal_output
terminal gfxterm
fi
fi
insmod ext2
set root='(hd1,1)'
search --no-floppy --fs-uuid --set 300287b9-0224-4c97-85d2-f4e509527005
set locale_dir=($root)/boot/grub/locale
set lang=en
insmod gettext
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 ###
insmod ext2
set root='(hd1,1)'
search --no-floppy --fs-uuid --set 300287b9-0224-4c97-85d2-f4e509527005
insmod tga
if background_image /usr/share/images/grub/Lake_mapourika_NZ.tga ; then
set color_normal=black/black
set color_highlight=magenta/black
else
set menu_color_normal=white/black
set menu_color_highlight=magenta/black
fi
### END /etc/grub.d/05_debian_theme ###


### BEGIN /etc/grub.d/10_linux ###
menuentry 'Ubuntu, with Linux 2.6.32-22-generic' --class ubuntu --class gnu-linux --class gnu --class os {
recordfail
insmod ext2
set root='(hd1,1)'
search --no-floppy --fs-uuid --set 300287b9-0224-4c97-85d2-f4e509527005
linux /boot/vmlinuz-2.6.32-22-generic root=UUID=300287b9-0224-4c97-85d2-f4e509527005 ro quiet splash
initrd /boot/initrd.img-2.6.32-22-generic
}
menuentry 'Ubuntu, with Linux 2.6.32-22-generic (recovery mode)' --class ubuntu --class gnu-linux --class gnu --class os {
recordfail
insmod ext2
set root='(hd1,1)'
search --no-floppy --fs-uuid --set 300287b9-0224-4c97-85d2-f4e509527005
echo 'Loading Linux 2.6.32-22-generic ...'
linux /boot/vmlinuz-2.6.32-22-generic root=UUID=300287b9-0224-4c97-85d2-f4e509527005 ro single
echo 'Loading initial ramdisk ...'
initrd /boot/initrd.img-2.6.32-22-generic
}
menuentry 'Ubuntu, with Linux 2.6.31-21-generic' --class ubuntu --class gnu-linux --class gnu --class os {
recordfail
insmod ext2
set root='(hd1,1)'
search --no-floppy --fs-uuid --set 300287b9-0224-4c97-85d2-f4e509527005
linux /boot/vmlinuz-2.6.31-21-generic root=UUID=300287b9-0224-4c97-85d2-f4e509527005 ro quiet splash
initrd /boot/initrd.img-2.6.31-21-generic
}
menuentry 'Ubuntu, with Linux 2.6.31-21-generic (recovery mode)' --class ubuntu --class gnu-linux --class gnu --class os {
recordfail
insmod ext2
set root='(hd1,1)'
search --no-floppy --fs-uuid --set 300287b9-0224-4c97-85d2-f4e509527005
echo 'Loading Linux 2.6.31-21-generic ...'
linux /boot/vmlinuz-2.6.31-21-generic root=UUID=300287b9-0224-4c97-85d2-f4e509527005 ro single
echo 'Loading initial ramdisk ...'
initrd /boot/initrd.img-2.6.31-21-generic
}
### END /etc/grub.d/10_linux ###


### BEGIN /etc/grub.d/20_memtest86+ ###
menuentry "Memory test (memtest86+)" {
insmod ext2
set root='(hd1,1)'
search --no-floppy --fs-uuid --set 300287b9-0224-4c97-85d2-f4e509527005
linux16 /boot/memtest86+.bin
}
menuentry "Memory test (memtest86+, serial console 115200)" {
insmod ext2
set root='(hd1,1)'
search --no-floppy --fs-uuid --set 300287b9-0224-4c97-85d2-f4e509527005
linux16 /boot/memtest86+.bin console=ttyS0,115200n8
}
### END /etc/grub.d/20_memtest86+ ###


### BEGIN /etc/grub.d/30_os-prober ###
menuentry "Windows Vista (loader) (on /dev/sda1)" {
insmod ntfs
set root='(hd0,1)'
search --no-floppy --fs-uuid --set 327caedc7cae9a5d
chainloader +1
}
menuentry "Windows Vista (loader) (on /dev/sda3)" {
insmod ntfs
set root='(hd0,3)'
search --no-floppy --fs-uuid --set 949ca48c9ca46a86
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 ###


=============================== sdb1/etc/fstab: ===============================


# /etc/fstab: static file system information.
#
# Use 'blkid -o value -s UUID' 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 defaults 0 0
# / was on /dev/sdb1 during installation
UUID=300287b9-0224-4c97-85d2-f4e509527005 / ext4 errors=remount-ro 0 1
# swap was on /dev/sdb5 during installation
UUID=b1527b9e-073b-42fd-841c-95b91fb7d085 none swap sw 0 0
/dev/scd0 /media/cdrom0 udf,iso9660 user,noauto,exec,utf8 0 0


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




.1GB: boot/grub/core.img
2.4GB: boot/grub/grub.cfg
12.9GB: boot/initrd.img-2.6.31-21-generic
12.9GB: boot/initrd.img-2.6.32-22-generic
2.2GB: boot/vmlinuz-2.6.31-21-generic
13.6GB: boot/vmlinuz-2.6.32-22-generic
12.9GB: initrd.img
12.9GB: initrd.img.old
13.6GB: vmlinuz
2.2GB: vmlinuz.old
=======Devices which don't seem to have a corresponding hard drive==============


sdc sdd sde sdf
=============================== StdErr Messages: ===============================


umount: /tmp/BootInfo0/sda1: device is busy.
(In some cases useful info about processes that use
the device is found by lsof(8) or fuser(1))


Any help beyond this point is appreciated.


Thanks

[drs305]

You have grub installed on the Windows partition (sda1). Normally grub should be installed on the drive but not on a specific partition (and certainly not on the Windows partition).

Take a look at this link for the likely solution:

http://sourceforge.net/apps/mediawiki/bootinfoscript/index.php?title=Boot_Problems:Boot_Sector

Note: Grub2 will boot faster if you go into BIOS and select sdb as the drive your system boots first (with G2 installed on sdb).

[darkod]

sda1: __________________________________________________ _______________________


File system: ntfs
Boot sector type: Grub 2
Boot sector info: Grub 2 is installed in the boot sector of sda1 and
looks at sector 275031 of the same hard drive for
core.img, but core.img can not be found at this
location. No errors found in the Boot Parameter Block.
Operating System: Windows Vista
Boot files/dirs: /bootmgr /Boot/BCD /Windows/System32/winload.exe

You have installed grub2 to the vista partition. Use these instructions to remove it:
http://sourceforge.net/apps/mediawiki/bootinfoscript/index.php?title=Boot_Problems:Boot_Sector

So, you need to apply the fix on partition #1 on disk /dev/sda.

That should sort it out.

You have the same on /dev/sda3 which looks like your restore partition, so if you want to access it from the grub2 menu, you need to do the same for /dev/sda3 too.

[Norwal]

I hope this help. I had the same issue after I decided to upgrade to Win7. I did a complete install of Win7 followed by a new install of Ubuntu 9.10 64 bit(separate drives). All was fine until I did a update on Ubuntu. After much searching on the forums, I discovered that Grub2 doesn't play nice in the park anymore and the upgrade I did included Grub2.

http://ubuntuforums.org/showthread.php?t=1328983

To fix this annoying little step backwards by Grub, you can follow all the complex fixes on the forums or do what I did. I reformatted my Ubuntu drive and start over. This time I tried 10.04. I did all the updates, minus the Grub2 "upgrade" and everything still works. :P

[KNC]

Thank you folks. The website that drs305 directed me to had the answer. I had a slightly different third screen come up, but it worked!

Thanks!

[darkod]

I hope this help. I had the same issue after I decided to upgrade to Win7. I did a complete install of Win7 followed by a new install of Ubuntu 9.10 64 bit(separate drives). All was fine until I did a update on Ubuntu. After much searching on the forums, I discovered that Grub2 doesn't play nice in the park anymore and the upgrade I did included Grub2.

http://ubuntuforums.org/showthread.php?t=1328983

To fix this annoying little step backwards by Grub, you can follow all the complex fixes on the forums or do what I did. I reformatted my Ubuntu drive and start over. This time I tried 10.04. I did all the updates, minus the Grub2 "upgrade" and everything still works. :P

Please don't confuse the OP. This has nothing to do with grub2 directly.

It has to do with installing grub2 onto the windows partition. And even if ubuntu is reinstalled now, grub2 will still remain on the windows partition and grub1 nor grub2 can boot windows in that situation.

When asked by the upgrade process where to install grub2, the OP checked all partitions. You can see it on all partitions in the results file.

Only disk(s) need to be selected, not partitions, when asked where you want grub2 by the upgrade process.

[darkod]

Thank you folks. The website that drs305 directed me to had the answer. I had a slightly different third screen come up, but it worked!

Thanks!

Great. :) Good job.

[Norwal]

When asked by the upgrade process where to install grub2, the OP checked all partitions. You can see it on all partitions in the results file.

Only disk(s) need to be selected, not partitions, when asked where you want grub2 by the upgrade process.

Thanks for the reply darkod. I guess I don't understand the process well enough. When I did the update that last time, I used Synaptic and don't recall being prompted. I guess now that all other updates are completed, I could try again. The worse thing that could happen is another reinstall. :)

The point I was making was this; If you don't update to Grub2, then the dual boot still works from a clean install. ie: if it ain't broke don't fix it. But then again where is the fun and learning in that?

Cheers

[darkod]

The point I was making was this; If you don't update to Grub2, then the dual boot still works from a clean install.


I'm not sure I can follow you on this. A clean install, according to me at least, is when you install ubuntu without previously having one, or over your existing install formatting the old root partition, which wipes everything from it.

Either way, if you don't install grub2 (the bootloader) during the clean install, what are you going to boot ubuntu with?

This can only work if you also have another linux distro with its grub/grub2 already installed, and want to use that one to boot your new ubuntu.

Otherwise, for a windows/ubuntu dual boot, not installing a bootloader during clean install will definitely not make it work, because the grub2 that remains on the MBR will have his files wiped from the old root partition by the clean install. That is a very good recipe how to break your dual boot.

[s2f]

You have grub installed on the Windows partition (sda1). Normally grub should be installed on the drive but not on a specific partition (and certainly not on the Windows partition).

Take a look at this link for the likely solution:

http://sourceforge.net/apps/mediawiki/bootinfoscript/index.php?title=Boot_Problems:Boot_Sector

Note: Grub2 will boot faster if you go into BIOS and select sdb as the drive your system boots first (with G2 installed on sdb).

wow this saved me from going completely grey haired. everything was working fine until i upgraded to lucid lynx. thanks a lot to you and the original poster

[darkod]

wow this saved me from going completely grey haired. everything was working fine until i upgraded to lucid lynx. thanks a lot to you and the original poster

Just a quick reminder, everything was working fine until you selected to install grub2 on the windows partition. This "problem" has nothing to do with the upgrade itself. As long as you don't install grub2 on the windows partition, it will be fine.
You made it sound like the upgrade itself will make windows unbootable.