Need help fixing boot problem on Ubuntu/WinXp dual-boot

Ay-Karamba! · 09-05-2005, 09:29 AM

Hi, I have Ubuntu and WinXp dualboot system, and somehow after I installed my Ubuntu, my I can't boot my WinXp anymore. Everytime I tried, I only get a blue screen saying windows was forced to shutdown. I've been searching the threads for answers, and I found out we could actually use Repair mode on WinXp CD and do FIXMBR, but I'm not sure about this, cos last time my friend tried that, he lost thewhole hardisk. So my question is, what's the best method to fix my WinXP? Will FIXMBR actually affect hardisk content? Can I do FIXMBR, and after my windows is fixed, reinstall grub? Thanks.

christine_lewis · 09-05-2005, 11:45 AM

What does your grub.conf look like?

I'm not sure this will be your problem but if you have Windows on a second hard drive that may be part of what's causing problems (it could be fixed without reinstalling anything though).

-Christine

Ay-Karamba! · 09-05-2005, 05:42 PM

You mean my /boot/grub/menu.lst ? Here it is

Code:

# menu.lst - See: grub(8), info grub, update-grub(8)
#            grub-install(8), grub-floppy(8),
#            grub-md5-crypt, /usr/share/doc/grub
#            and /usr/share/doc/grub-doc/.

## default num
# Set the default entry to the entry number NUM. Numbering starts from 0, and
# the entry number 0 is the default if the command is not used.
#
# You can specify 'saved' instead of a number. In this case, the default entry
# is the entry saved with the command 'savedefault'.           
default		0

## timeout sec
# Set a timeout, in SEC seconds, before automatically booting the default entry
# (normally the first entry defined).
timeout		3

## hiddenmenu
# Hides the menu by default (press ESC to see the menu)
hiddenmenu

# Pretty colours
#color cyan/blue white/blue

## password ['--md5'] passwd
# If used in the first section of a menu file, disable all interactive editing
# control (menu entry editor and command-line)  and entries protected by the
# command 'lock'
# e.g. password topsecret
#      password --md5 $1$gLhU0/$aW78kHK1QfV3P2b2znUoe/
# password topsecret

#
# examples
#
# title		Windows 95/98/NT/2000
# root		(hd0,0)
# makeactive
# chainloader	+1
#
# title		Linux
# root		(hd0,1)
# kernel	/vmlinuz root=/dev/hda2 ro
#

#
# Put static boot stanzas before and/or after AUTOMAGIC KERNEL LIST

### BEGIN AUTOMAGIC KERNELS LIST
## lines between the AUTOMAGIC KERNELS LIST markers will be modified
## by the debian update-grub script except for the default optons below

## DO NOT UNCOMMENT THEM, Just edit them to your needs

## ## Start Default Options ##
## default kernel options
## default kernel options for automagic boot options
## If you want special options for specifiv kernels use kopt_x_y_z
## where x.y.z is kernel version. Minor versions can be omitted.
## e.g. kopt=root=/dev/hda1 ro
# kopt=root=/dev/hda2 ro

## default grub root device
## e.g. groot=(hd0,0)
# groot=(hd0,1)

## should update-grub create alternative automagic boot options
## e.g. alternative=true
##      alternative=false
# alternative=true

## should update-grub lock alternative automagic boot options
## e.g. lockalternative=true
##      lockalternative=false
# lockalternative=false

## altoption boot targets option
## multiple altoptions lines are allowed
## e.g. altoptions=(extra menu suffix) extra boot options
##      altoptions=(recovery mode) single
# altoptions=(recovery mode) single

## nonaltoption boot targets option
## This option controls options to pass to only the
## primary kernel menu item.
## You can have ONLY one nonaltoptions line
# nonaltoptions=quiet splash

## controls how many kernels should be put into the menu.lst
## only counts the first occurence of a kernel, not the
## alternative kernel options
## e.g. howmany=all
##      howmany=7
# howmany=all

## should update-grub create memtest86 boot option
## e.g. memtest86=true
##      memtest86=false
# memtest86=true

## ## End Default Options ##

title		Ubuntu, kernel 2.6.10-5-386 
root		(hd0,1)
kernel		/boot/vmlinuz-2.6.10-5-386 root=/dev/hda2 ro quiet splash
initrd		/boot/initrd.img-2.6.10-5-386
savedefault
boot

title		Ubuntu, kernel 2.6.10-5-386 (recovery mode)
root		(hd0,1)
kernel		/boot/vmlinuz-2.6.10-5-386 root=/dev/hda2 ro single
initrd		/boot/initrd.img-2.6.10-5-386
savedefault
boot

title		Ubuntu, kernel memtest86+ 
root		(hd0,1)
kernel		/boot/memtest86+.bin  
savedefault
boot

### END DEBIAN AUTOMAGIC KERNELS LIST

# This is a divider, added to separate the menu items below from the Debian
# ones.
title		Other operating systems:
root


# This entry automatically added by the Debian installer for a non-linux OS
# on /dev/hda1
title		Microsoft Windows XP Professional
root		(hd0,0)
savedefault
makeactive
chainloader	+1

syg00 · 09-05-2005, 06:55 PM

Did you pick the partitions to install to,or let the installer handle it ??.
Was XP on the first partition prior to you starting - i.e. was their a vendor recovery partition ???.
fixmbr is generally safe, but unlikely to help here, as it appears the chainload to the XP boot sector record is succeeding. Can you post the output from

Code:

fdisk -l

(that's small l as in list)

Ay-Karamba! · 09-06-2005, 03:31 AM

Thanks for your replying, but what do you mean by vendor recovery partition? All I did when I setup my system is:
1. First I installed WinXP, and use partition editor on the windows CD to create 20GB partition for it
2. Then I Installed Ubuntu, and create another 120GB partition for it (including 1.5GB for swap), leaving 20GB empty space which was planned for another partition for backup, but currently still empty

Here's my fdisk -l

Code:

Disk /dev/hda: 160.0 GB, 160041885696 bytes
116 heads, 43 sectors/track, 62666 cylinders
Units = cylinders of 4988 * 512 = 2553856 bytes

   Device Boot      Start         End      Blocks   Id  System
/dev/hda1   *           1        8212    20480706+   7  HPFS/NTFS
/dev/hda2            8213       54221   114746446   83  Linux
/dev/hda3           54222       54808     1463978    5  Extended
/dev/hda5           54222       54808     1463956+  82  Linux swap / Solaris

syg00 · 09-06-2005, 09:20 PM

The reason I asked is because the vendors sometimes put a (hidden) recovery partition on the disk, and this may confuse the installer.
You look to be o.k.

I have Ubuntu dual-boot on my test machine - thought it was still XP so I could look around for you.
Unfortunately I had forgotten I trashed the XP and replaced it with Solaris, so that's no help.

I've never had any issues with the Ubuntu installer though - sorry, I can't help.