PDA

View Full Version : [ubuntu] Vista/Ubuntu 9.04 Dual Boot Woes



Alaydriem
April 28th, 2009, 04:22 AM
Greetings,

I've been running a Dual Boot with Vista and Ubuntu 8.10 for a while now. I decided to upgrade to Jaunty to try out ext4. I reformated 8.10 so I could run 9.04 under ext4. Everything ran without a problem in regard to the Dual Booting until this afternoon. This afternoon I was running Vista, and switched over to run Ubuntu to keep trying out the new operating system. When I tried to switch back over to Vista, I ended up getting Blue Screened a few moments after the Vista bootloader. I'm not sure what happened, Vista and Ubuntu have always run well together on this box (Dell Vostro 1500).

Vista BlueScreen says: "Process1_Initilization_Failure"

I tried the Repair Disk twice and it ran and Fixed the Vista bootloader but that didn't seem to fix anything, Vista still can't load. I can still access all of my files from Ubuntu, however I would really not like to reformat and reinstall my Vista Partition.

I searched around the forums and Google and didn't find anything pertaining to Vista and "Process1_Initilization_Failure". A forum post I found recommended I run "boot info summary"to check the boot sectors. It outputs as follows:


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

=> Grub0.97 is installed in the MBR of /dev/sda and looks on the same drive
in partition #4 for /boot/grub/stage2 and /boot/grub/menu.lst.

sda1: __________________________________________________ _______________________

File system: ntfs
Boot sector type: Windows Vista
Boot sector info: No errors found in the Boot Parameter Block.
Operating System:
Boot files/dirs:

sda2: __________________________________________________ _______________________

File system: ntfs
Boot sector type: Windows Vista
Boot sector info: 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: Extended Partition
Boot sector type: -
Boot sector info:

sda5: __________________________________________________ _______________________

File system: ntfs
Boot sector type: Windows Vista
Boot sector info: According to the info in the boot sector, sda5 starts
at sector 2048.
Operating System:
Boot files/dirs:

sda4: __________________________________________________ _______________________

File system: ext4
Boot sector type: -
Boot sector info:
Operating System: Ubuntu 9.04
Boot files/dirs: /boot/grub/menu.lst /etc/fstab

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

Drive: sda ___________________ __________________________________________________ ___

Disk /dev/sda: 250.0 GB, 250059350016 bytes
255 heads, 63 sectors/track, 30401 cylinders, total 488397168 sectors
Units = sectors of 1 * 512 = 512 bytes
Disk identifier: 0x68000000

Partition Boot Start End Size Id System

/dev/sda1 2,048 21,166,071 21,164,024 7 HPFS/NTFS
/dev/sda2 * 21,166,080 254,998,511 233,832,432 7 HPFS/NTFS
/dev/sda3 254,999,745 425,481,524 170,481,780 f W95 Ext d (LBA)
/dev/sda5 255,000,576 425,480,183 170,479,608 7 HPFS/NTFS
/dev/sda4 425,481,525 488,392,064 62,910,540 83 Linux


blkid -c /dev/null: __________________________________________________ __________

/dev/sda1: UUID="96A41481A41465D1" LABEL="Server" TYPE="ntfs"
/dev/sda2: UUID="7424230B2422CFC2" LABEL="Vista" TYPE="ntfs"
/dev/sda4: UUID="b8853993-9d13-46e1-8596-7f022c1660c7" TYPE="ext4"
/dev/sda5: UUID="040A71EA0A71D95E" LABEL="Documents & Files" TYPE="ntfs"

=============================== "mount" output: ===============================

/dev/sda4 on / type ext4 (rw,relatime,errors=remount-ro)
tmpfs on /lib/init/rw type tmpfs (rw,nosuid,mode=0755)
proc on /proc type proc (rw,noexec,nosuid,nodev)
sysfs on /sys type sysfs (rw,noexec,nosuid,nodev)
varrun on /var/run type tmpfs (rw,nosuid,mode=0755)
varlock on /var/lock type tmpfs (rw,noexec,nosuid,nodev,mode=1777)
udev on /dev type tmpfs (rw,mode=0755)
tmpfs on /dev/shm type tmpfs (rw,nosuid,nodev)
devpts on /dev/pts type devpts (rw,noexec,nosuid,gid=5,mode=620)
fusectl on /sys/fs/fuse/connections type fusectl (rw)
lrm on /lib/modules/2.6.28-11-generic/volatile type tmpfs (rw,mode=755)
/dev/sda2 on /media/Vista type fuseblk (rw,nosuid,nodev,allow_other,blksize=4096)
/dev/sda1 on /media/Server type fuseblk (rw,nosuid,nodev,allow_other,blksize=4096)
/dev/sda5 on /media/Documents & Files type fuseblk (rw,nosuid,nodev,allow_other,blksize=4096)
binfmt_misc on /proc/sys/fs/binfmt_misc type binfmt_misc (rw,noexec,nosuid,nodev)
gvfs-fuse-daemon on /home/charlesportwoodii/.gvfs type fuse.gvfs-fuse-daemon (rw,nosuid,nodev,user=charlesportwoodii)


=========================== sda4/boot/grub/menu.lst: ===========================

# 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'.
# WARNING: If you are using dmraid do not use 'savedefault' or your
# array will desync and will not let you boot your system.
default 0

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

## 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 options 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 specific 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_2_6_8=root=/dev/hdc1 ro
## kopt_2_6_8_2_686=root=/dev/hdc2 ro
# kopt=root=UUID=b8853993-9d13-46e1-8596-7f022c1660c7 ro

## default grub root device
## e.g. groot=(hd0,0)
# groot=b8853993-9d13-46e1-8596-7f022c1660c7

## 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

## additional options to use with the default boot option, but not with the
## alternatives
## e.g. defoptions=vga=791 resume=/dev/hda5
# defoptions=quiet splash

## should update-grub lock old automagic boot options
## e.g. lockold=false
## lockold=true
# lockold=false

## Xen hypervisor options to use with the default Xen boot option
# xenhopt=

## Xen Linux kernel options to use with the default Xen boot option
# xenkopt=console=tty0

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

## 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

## specify if running in Xen domU or have grub detect automatically
## update-grub will ignore non-xen kernels when running in domU and vice versa
## e.g. indomU=detect
## indomU=true
## indomU=false
# indomU=detect

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

## should update-grub adjust the value of the default booted system
## can be true or false
# updatedefaultentry=false

## should update-grub add savedefault to the default options
## can be true or false
# savedefault=false

## ## End Default Options ##

title Ubuntu 9.04, kernel 2.6.28-11-generic
uuid b8853993-9d13-46e1-8596-7f022c1660c7
kernel /boot/vmlinuz-2.6.28-11-generic root=UUID=b8853993-9d13-46e1-8596-7f022c1660c7 ro quiet splash
initrd /boot/initrd.img-2.6.28-11-generic
quiet

title Ubuntu 9.04, kernel 2.6.28-11-generic (recovery mode)
uuid b8853993-9d13-46e1-8596-7f022c1660c7
kernel /boot/vmlinuz-2.6.28-11-generic root=UUID=b8853993-9d13-46e1-8596-7f022c1660c7 ro single
initrd /boot/initrd.img-2.6.28-11-generic

### 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/sda2
title Windows Vista (loader)
rootnoverify (hd0,1)
savedefault
makeactive
chainloader +1


=============================== sda4/etc/fstab: ===============================

# /etc/fstab: static file system information.
#
# -- This file has been automaticly generated by ntfs-config --
#
# <file system> <mount point> <type> <options> <dump> <pass>

proc /proc proc defaults 0 0
# Entry for /dev/sda4 :
UUID=b8853993-9d13-46e1-8596-7f022c1660c7 / ext4 relatime,errors=remount-ro 0 1
/dev/scd0 /media/cdrom0 udf,iso9660 user,noauto,exec,utf8 0 0
/dev/sda2 /media/Vista ntfs-3g defaults,locale=en_US.UTF-8 0 0
/dev/sda1 /media/Server ntfs-3g defaults,locale=en_US.UTF-8 0 0
/dev/sda5 /media/Documents\040&\040Files ntfs-3g defaults,locale=en_US.UTF-8 0 0

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


219.7GB: boot/grub/menu.lst
219.7GB: boot/grub/stage2
219.6GB: boot/initrd.img-2.6.28-11-generic
219.7GB: boot/vmlinuz-2.6.28-11-generic
219.6GB: initrd.img
219.7GB: vmlinuzI didn't see anything wrong in the output, but then again I'm just guessing at reading it.

I'd really appreciate any insight or advice as to getting my Vista partition to get working again. It didn't crash until after I ran apt-get upgrade, but I don't see how that could mess anything up. Any help would be greatly appreciated if possible from the Ubuntu side. Thank you.

In Him,

jamesrico
April 29th, 2009, 03:27 AM
Hello, I did exactly the same thing loaded 9.04, then checked for upgrades. Later tried to get on to vista and I get an lost ini file error message.

James

talz13
April 29th, 2009, 03:46 PM
I had the same issue, vista bluescreening after installing 9.04. I had changed my sata controller FROM AHCI to NATIVE IDE mode as well. I could understand bluescreening being a result of changing IDE to AHCI mode, but not the other way around!

I now have a winxp install on my other drive and am playing with it to get it to dual boot. No luck there yet. If I select xp from grub, it promptly reboots my pc.

Alaydriem
May 3rd, 2009, 07:05 AM
Greetings,

Does anyone have any suggestions on how to recover this partition from Ubuntu?

Thank you,
In Him,

anthonie
May 3rd, 2009, 09:19 AM
Greetings,

Does anyone have any suggestions on how to recover this partition from Ubuntu?

Thank you,
In Him,

Well, I have not installed 9.04 on this machine just yet but have seen these problems before. If I were you Alaydriem I would surely look into you BIOS settings first. Many times all you have to do is reset your SATA/IDE controller in order for Vista to run again. That's what happened to me when I installed 8.10 a while ago and also after a Vista update, I had to do the reset as well as I was not able to boot into Vista though booting to Ubuntu worked fine.

If you keep having problems after looking into your BIOS thing, I'd advice to first try out the Super Grub disk and otherwise to install and use testdisk (available through apt-get).

Good luck!

Mark Phelps
May 3rd, 2009, 09:33 PM
Given the high excellence value of MS Windows tools (yeah, I'm being facetious), you often have to run the Startup Repair three or more times. Apparently, it's only able fix one thing at a time, and since there can be any number of problems, you have to keep running it again and again until it finds no more problems to fix.

Alaydriem
May 4th, 2009, 04:49 PM
Greetings,

Thanks for the advice Mark. I ran the disk a few more times and it indicated that I have a bad hard disk. (Sarcastic shouts of joy...). I tried running chkdsk a few times and now the file system is detected as RAW instead of NTFS.

Fortunately I'm still under warranty from Dell, so they're shipping me a replacement HDD.

What I still don't understand is how my entire Vista Partition can be inoperable, yet my Files Partition can still be read, Ubuntu still runs perfectly, and I can still view files on the Vista Partition from Ubuntu without a hitch. That is what doesn't make sense to me.

Thanks for all you help though!

In Him,