PDA

View Full Version : [ubuntu] Problem with Ubuntu 9.10 and Windows 7 dual boot



topgun_tapan
November 1st, 2009, 05:52 AM
I installed ubuntu 9.10 first and then installed Windows 7. After that i followed the tutorial here (https://wiki.ubuntu.com/Grub2#Recover%20Grub%202%20via%20LiveCD) to reinstall grub. After i ran the command update-grub, it detected Windows 7 automatically and added it to the grub.cfg file. However, now when I try to start windows from the grub, It doesn't load windows and instead just shows the grub again after a second. Here is my fdisk -l


Disk /dev/sda: 120.0 GB, 120034123776 bytes
255 heads, 63 sectors/track, 14593 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0x597e5e85

Device Boot Start End Blocks Id System
/dev/sda1 1 4255 34178256 83 Linux
/dev/sda2 4256 4379 996030 5 Extended
/dev/sda3 * 4380 14593 82043955 7 HPFS/NTFS
/dev/sda5 4256 4379 995998+ 82 Linux swap / Solaris

and here is my grub.cfg file

#
# 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 /boot/grub/grubenv ]; then
have_grubenv=true
load_env
fi
set default="0"
if [ ${prev_saved_entry} ]; then
saved_entry=${prev_saved_entry}
save_env saved_entry
prev_saved_entry=
save_env prev_saved_entry
fi
insmod ext2
set root=(hd0,1)
search --no-floppy --fs-uuid --set fa42374d-e7b7-4877-848f-f9d80985c641
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
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=(hd0,1)
search --no-floppy --fs-uuid --set fa42374d-e7b7-4877-848f-f9d80985c641
insmod tga
if background_image /usr/share/images/grub/splash.tga ; then
set color_normal=black/black
set color_highlight=magenta/black
else
set menu_color_normal=white/black
set menu_color_highlight=black/white
fi
### END /etc/grub.d/05_debian_theme ###

### BEGIN /etc/grub.d/10_linux ###
menuentry "Ubuntu, Linux 2.6.31-14-generic" {
recordfail=1
if [ -n ${have_grubenv} ]; then save_env recordfail; fi
set quiet=1
insmod ext2
set root=(hd0,1)
search --no-floppy --fs-uuid --set fa42374d-e7b7-4877-848f-f9d80985c641
linux /boot/vmlinuz-2.6.31-14-generic root=UUID=fa42374d-e7b7-4877-848f-f9d80985c641 ro quiet splash
initrd /boot/initrd.img-2.6.31-14-generic
}
menuentry "Ubuntu, Linux 2.6.31-14-generic (recovery mode)" {
recordfail=1
if [ -n ${have_grubenv} ]; then save_env recordfail; fi
insmod ext2
set root=(hd0,1)
search --no-floppy --fs-uuid --set fa42374d-e7b7-4877-848f-f9d80985c641
linux /boot/vmlinuz-2.6.31-14-generic root=UUID=fa42374d-e7b7-4877-848f-f9d80985c641 ro single
initrd /boot/initrd.img-2.6.31-14-generic
}
### END /etc/grub.d/10_linux ###

### BEGIN /etc/grub.d/20_memtest86+ ###
menuentry "Memory test (memtest86+)" {
linux16 /boot/memtest86+.bin
}
menuentry "Memory test (memtest86+, serial console 115200)" {
linux16 /boot/memtest86+.bin console=ttyS0,115200n8
}
### END /etc/grub.d/20_memtest86+ ###

### BEGIN /etc/grub.d/30_os-prober ###
menuentry "Windows 7 (loader) (on /dev/sda3)" {
insmod ntfs
set root=(hd0,3)
search --no-floppy --fs-uuid --set f0107bd3107b9f72
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 ###

Herman
November 1st, 2009, 10:59 AM
I don't see any problems there, your grub.cfg looks okay and it matches your fdisk output.

In the past, rebooting into GRUB right after selecting Windows and trying to boot has been caused by installing GRUB to the Windows partition boot sector.
I can't imagine how that can happen by accident, but if you have any reason to think that might possibly be the problem maybe you should try repairing your Windows boot sector.

You should be able to repair your Windows Boot Sector by booting with your Windows 7 DVD in the CD-ROM drive and run 'Startup Repair'.

If that doesn't fix it automatically, you might also need to open a command prompt and run bootrec /fixboot.