Installed Ubuntu 11.10, already had Win7 and Win7 wont start

BustaBust

Golden Member
Dec 21, 2001
1,425
2
81
I already had Windows 7 on my C: drive.
I used the Ubuntu LiveCD which didn't contain any rescue software to install.
I had an NTFS partition (C: for Windows), blank NTFS partition Dee

I used the partition program/installer from the Ubuntu LiveCD. I chose custom,
formatted the Dee drive and installed Ubuntu to it. It created a swap drive on it's own.
Left C: intact. I must have chose the wrong bootloader when setting up because the grub loader shows Linux, Linux Recovery, 2 Memtests, and Windows 7. When I choose Windows 7 it just loops back to the same screen that prompts me for a choice. I booted into Ubuntu and checked the disks, the main partition states NTFS and partition type states 'Linux (0x83)', this is my main partition that contains Windows 7 (/dev/sda2). Both partitions are on 1 hard drive (/dev/sda) Ubuntu is on /dev/sda5

I tried booting with a Windows 7 disk to repair the mbr, but first I had to go into BIOS and turn on the ACPI. Then I tried again and the recovery tool showed my previously installed Windows but an error pops up saying the System Recovery tool isn't compatible for this version of Windows or something like that. Keep in mind I'm using the same Windows CD that I used to install it in the first place. I found ms-sys for linux but I don't know how to compile it. Also, I have Boot-Repair and don't know how to fix this problem. I also have Grub-Customizer and don't know how to use it either. I have the Linux LiveCD but don't know how to do anything with it. I've installed LILO as well.

I've read about these:

sudo ms-sys -7 /dev/sda
fixmbr
fixboot

I cannot use any of those because of what I stated above.
Windows was already installed first, Win 7 CD won't work,
have Linux CD, need help with ms-sys 2.2.1 if possible, boot-repair or grub-customizer help if possible OR any other fix is appreciated.

Thanks.

EDIT - Dee is supposed to be the fourth letter in the alphabet. Typed this way to avoid "Disgusted" face smiley


EDIT:
Boot Info Script 0.60 from 17 May 2011


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

=> Lilo is installed in the MBR of /dev/sda.

sda1: __________________________________________________________________________

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

sda5: __________________________________________________________________________

File system: ext4
Boot sector type: -
Boot sector info:
Operating System: Ubuntu 11.10
Boot files: /boot/grub/grub.cfg /etc/fstab /etc/lilo.conf
/boot/grub/core.img

sda2: __________________________________________________________________________

File system: ntfs
Boot sector type: Grub2 (v1.99)
Boot sector info: Grub2 (v1.99) is installed in the boot sector of sda2
and looks at sector 14149632 of the same hard drive
for core.img. core.img is at this location and looks
for on this drive. No errors found in the Boot
Parameter Block.
============================ 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 Sector End Sector # of Sectors Id System

/dev/sda1 2,046 31,133,695 31,131,650 5 Extended
/dev/sda5 2,048 31,133,695 31,131,648 83 Linux
/dev/sda2 * 31,133,970 1,465,144,064 1,434,010,095 7 NTFS / exFAT / HPFS


"blkid" output: ________________________________________________________________

Device UUID TYPE LABEL

/dev/sda2 EECC59B5CC5978B3 ntfs
/dev/sda5 8481f207-2d07-492b-8e19-ca3768ff8ecd ext4

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

Device Mount_Point Type Options

/dev/sda2 /tmp/BootInfo0/sda2 ntfs (ro)
/dev/sda5 / ext4 (rw,errors=remount-ro,commit=0)


=========================== sda5/boot/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 ###
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='(hd0,msdos5)'
search --no-floppy --fs-uuid --set=root 8481f207-2d07-492b-8e19-ca3768ff8ecd
if loadfont /usr/share/grub/unicode.pf2 ; then
set gfxmode=auto
load_video
insmod gfxterm
insmod part_msdos
insmod ext2
set root='(hd0,msdos5)'
search --no-floppy --fs-uuid --set=root 8481f207-2d07-492b-8e19-ca3768ff8ecd
set locale_dir=($root)/boot/grub/locale
set lang=en_US
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 0,71,115; then
clear
fi
### END /etc/grub.d/05_debian_theme ###

### BEGIN /etc/grub.d/10_linux ###
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.0.0-16-generic' --class ubuntu --class gnu-linux --class gnu --class os {
recordfail
set gfxpayload=$linux_gfx_mode
insmod gzio
insmod part_msdos
insmod ext2
set root='(hd0,msdos5)'
search --no-floppy --fs-uuid --set=root 8481f207-2d07-492b-8e19-ca3768ff8ecd
linux /boot/vmlinuz-3.0.0-16-generic root=UUID=8481f207-2d07-492b-8e19-ca3768ff8ecd ro quiet splash vt.handoff=7
initrd /boot/initrd.img-3.0.0-16-generic
}
menuentry 'Ubuntu, with Linux 3.0.0-16-generic (recovery mode)' --class ubuntu --class gnu-linux --class gnu --class os {
recordfail
insmod gzio
insmod part_msdos
insmod ext2
set root='(hd0,msdos5)'
search --no-floppy --fs-uuid --set=root 8481f207-2d07-492b-8e19-ca3768ff8ecd
echo 'Loading Linux 3.0.0-16-generic ...'
linux /boot/vmlinuz-3.0.0-16-generic root=UUID=8481f207-2d07-492b-8e19-ca3768ff8ecd ro recovery nomodeset
echo 'Loading initial ramdisk ...'
initrd /boot/initrd.img-3.0.0-16-generic
}
submenu "Previous Linux versions" {
menuentry 'Ubuntu, with Linux 3.0.0-12-generic' --class ubuntu --class gnu-linux --class gnu --class os {
recordfail
set gfxpayload=$linux_gfx_mode
insmod gzio
insmod part_msdos
insmod ext2
set root='(hd0,msdos5)'
search --no-floppy --fs-uuid --set=root 8481f207-2d07-492b-8e19-ca3768ff8ecd
linux /boot/vmlinuz-3.0.0-12-generic root=UUID=8481f207-2d07-492b-8e19-ca3768ff8ecd ro quiet splash vt.handoff=7
initrd /boot/initrd.img-3.0.0-12-generic
}
menuentry 'Ubuntu, with Linux 3.0.0-12-generic (recovery mode)' --class ubuntu --class gnu-linux --class gnu --class os {
recordfail
insmod gzio
insmod part_msdos
insmod ext2
set root='(hd0,msdos5)'
search --no-floppy --fs-uuid --set=root 8481f207-2d07-492b-8e19-ca3768ff8ecd
echo 'Loading Linux 3.0.0-12-generic ...'
linux /boot/vmlinuz-3.0.0-12-generic root=UUID=8481f207-2d07-492b-8e19-ca3768ff8ecd ro recovery nomodeset
echo 'Loading initial ramdisk ...'
initrd /boot/initrd.img-3.0.0-12-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='(hd0,msdos5)'
search --no-floppy --fs-uuid --set=root 8481f207-2d07-492b-8e19-ca3768ff8ecd
linux16 /boot/memtest86+.bin
}
menuentry "Memory test (memtest86+, serial console 115200)" {
insmod part_msdos
insmod ext2
set root='(hd0,msdos5)'
search --no-floppy --fs-uuid --set=root 8481f207-2d07-492b-8e19-ca3768ff8ecd
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/sda2)" --class windows --class os {
insmod part_msdos
insmod ntfs
set root='(hd0,msdos2)'
search --no-floppy --fs-uuid --set=root EECC59B5CC5978B3
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 ###
--------------------------------------------------------------------------------

=============================== sda5/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/sda5 during installation
UUID=8481f207-2d07-492b-8e19-ca3768ff8ecd / ext4 errors=remount-ro 0 1
--------------------------------------------------------------------------------

============================= sda5/etc/lilo.conf: ==============================

--------------------------------------------------------------------------------
# /etc/lilo.conf - systemwide LILO configuration (LILO 23)
# details see in manpages: lilo(8) and lilo.conf(5)

# +-------------------------------------------------------------+
# | !! Reminder !! |
# | |
# | Don't forget to run 'lilo' after you make changes to this |
# | conffile or you have installed a new kernel. |
# +-------------------------------------------------------------+


# #################### LILO global section ######################

# With all newer systems (until year 2004) you can use the RAM
# above 15 MB. This option allows the use of this range of RAM.
#large-memory

# With all newer systems you can boot from any partition on disks
# with more than 1024 cylinders. This option allows the use of
# partitions above 1024 cylinders.
lba32

# Specifies the boot device. This is where Lilo installs its boot
# block. It can be either a partition, or the raw device, in which
# case it installs in the MBR, and will overwrite the current MBR.
# With newer kernel you should use the ID of the boot device, which
# can be found here: /dev/disks/by-id/ata*.
#boot = /dev/sda
boot = /dev/disk/by-id/ata-WDC_WD7500AAKS-22RBA0_WD-WCAPT0817149

# This option may be needed for some software RAID installs.
#raid-extra-boot = mbr-only

# Enable map compaction. This tries to merge read requests for
# adjacent sectors into a single read request. This drastically
# reduces load time and keeps the map smaller. Using 'compact'
# is especially recommended when booting from a floppy disk.
# It is disabled here by default because it doesn't always work.
#compact

# Set the verbose level for bootloader installation. Value range:
# 0 to 5. Default value is 0.
#verbose = 1

# Specifies the location of the map file. Lilo creates the (sector)
# map file of direct sector addresses which are independent of any
# filesystem.
map = /boot/map

# ---------------------------------------------------------------

# Specifies the menu interface. You have the choice between:
# text: simple text menu with black background and white text
# menu: configurable text menu with background and text colors.
# bmp: graphical menu with 640x480 bitmap background.
install = menu

# A) Customized boot message for choice 'text'.
# For the simple text menu you can set an extra message in the
# created file. Its text will be displayed before boot prompt.
#message = /boot/message.txt

# B) Configuration of the scheme for choice 'menu'.
# Use following coding: <text>:<highlight>:<border>:<title>
# The first character of each part sets the text frontcolor,
# the second character of earch part sets the text backcolor,
# an upper-case character sets bold face text (frontcolor).
# i.g. 'menu-scheme=wm:rw:wm:Wm'. Possible colors:
# k=black, b=blue, g=green, c=cyan, r=red, m=magenta, y=yellow, w=white.
menu-scheme = Wb:Yr:Wb:Wb
#menu-title = " DESDEMONA Boot-Manager "

# C) Configuration of the image for choice 'bmp'.
# For the graphical menu you need a bitmap file, which needs a special
# menu configuration in the file header (see: lilo -E). Ideally you
# use one of the delivered images of the lilo package.
# with 16 colors: onlyblue, tuxlogo, inside
# with 256 colors: coffee
# for Debian: debianlilo, debian, debian-de
#bitmap = /boot/tuxlogo.bmp

# ---------------------------------------------------------------

# Specifies the number of deciseconds (0.1 seconds) how long LILO
# should wait before booting the first image. LILO doesn't wait if
# 'delay' is omitted or set to zero. You do not see the defined menu.
#delay = 20

# Prompt to start one certain kernel from the displayed menu.
# It is very recommeded to also set 'timeout'. Without timeout boot
# will not take place unless you hit return. Timeout is the number
# of deciseconds (0.1 seconds) after there the default image will
# be started. With 'single-key' alias numbers for each menu line can
# be used.
prompt
timeout = 100
#single-key

# ---------------------------------------------------------------

# Specifying the VGA text mode that should be selected when booting.
# The following values are recognized (case is ignored):
# vga=normal 80x25 text mode (default)
# vga=extended 80x50 text mode (abbreviated to 'ext')
# vga=ask stop and ask for user input: choice of text mode
# vga=<mode> use the corresponding text mode number. A list of
# available modes can be obtained by booting with
# vga=ask' and then pressing [Enter].
# Another way is the use of frame buffer mode. Then the kernel
# will switch from the normal vga text mode (80x25) to the frame
# buffer mode (if frame buffer support is in the kernel):
# vga=0x314 800x600 @ 16 bit
# vga=0x317 1024x768 @ 16 bit
# vga=0x318 1024x768 @ 24 bit
#vga = ask
vga = normal
#vga = 0x317

# ---------------------------------------------------------------

# Kernel command line options that apply to all installed images go
# here. See 'kernel-parameters.txt' in the Linux kernel 'Documentation'
# directory. I.g. for start into 'init 5' write: append="5"
#append = ""

# If you used a serial console to install Debian, this option should be
# enabled by default.
#serial = 0,9600

# Set the image which should be started after delay or timeout.
# If not set, the first defined image will be started.
#default = Linux


# ################### LILO per-image section ####################

# Each image is configured with the linux kernel (=image) and
# usually with the initrd file. Configure all GNU/Linux systems
# on other partitions, too.

--------------------------------------------------------------------------------

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

GiB - GB File Fragment(s)

7.547878265 = 8.104472576 boot/grub/core.img 1
7.586662292 = 8.146116608 boot/grub/grub.cfg 1
2.766178131 = 2.970161152 boot/initrd.img-3.0.0-12-generic 2
7.969726562 = 8.557428736 boot/initrd.img-3.0.0-16-generic 2
6.724067688 = 7.219912704 boot/vmlinuz-3.0.0-12-generic 1
4.552219391 = 4.887908352 boot/vmlinuz-3.0.0-16-generic 2
7.969726562 = 8.557428736 initrd.img 2
2.766178131 = 2.970161152 initrd.img.old 2
4.552219391 = 4.887908352 vmlinuz 2
6.724067688 = 7.219912704 vmlinuz.old 1

========================== sda2/grldr embedded menu: ===========================

--------------------------------------------------------------------------------

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

sdb sdc sdd sde sdf

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

unlzma: Decoder error
/home/maulin/Desktop/boot_info_script.sh: line 1888: ( / 2 ) + 16 : syntax error: operand expected (error token is "/ 2 ) + 16 ")
 
Last edited:

buckjrdley

Member
Feb 28, 2011
35
0
0
Try this link:
http://www.supergrubdisk.org/

I use the super grub disk all the time. I've had a lot of success booting into both Ubuntu and Windows using it after my system becomes unbootable.

I've never used Rescatux, but if it's as good as super grub then I'll have to add it to my cd collection. It claims that it can fix both grub and windows boot problems (it will even repair the mbr for either system).

Good luck to you.
 

boochi

Senior member
May 21, 2011
984
0
0
The partition that has the windows boot loader may no longer be the active partition. If you can boot to ubuntu you can check the active partition with gparted. If that does not work and you have a copy of Hiren's or Ultimate Boot CD you can boot into windows by selecting the os partition with Plop Boot Manager.
 

BustaBust

Golden Member
Dec 21, 2001
1,425
2
81
I checked GParted and it's all active. I'm downloading RescaTux and trying the Win MBR option. Will let you know what's happening.

Thank you guys.
 

BustaBust

Golden Member
Dec 21, 2001
1,425
2
81
The RescaTux Windows MBR didn't work.
The DOS screen says "MBR" and then it loads up to the Linux loader screen with all of the options. Choosing Windows loops back to the menu screen.
 

BustaBust

Golden Member
Dec 21, 2001
1,425
2
81
It does state the Windows 7 partition is Windows Vista though. Maybe this is why the Windows 7 repair said it was the wrong version. I'm confused though because I know for sure I have running Windows 7 for forever now!
 

boochi

Senior member
May 21, 2011
984
0
0
Have you tried using the Plop Boot Loader found on Ultimate Boot CD or Hiren's? If you can boot into windows with that you can rebuild the windows boot loader easily with EasyBCD. I can't make heads or tails with that added info in the first post.
 

BustaBust

Golden Member
Dec 21, 2001
1,425
2
81
Getting UBCD 5.1.1 with AVG now will update soon.

EDIT - Don't even know what the hell to use.
 
Last edited: