PDA

View Full Version : [ubuntu_studio] To late to change boot sequence?



bigsmitty64
December 6th, 2009, 09:23 PM
Installed Ubuntu Studio 9.10. I missed someething during the install so now I can't dual boot. I have Vista on one drive and Installed Studio on a separate 1 TB drive. Is it too late to change now so I can dual boot? Its not a HUGE deal but would like the option,due to the fact that I have an iPhone and need iTunes to sync and update it.

Heres my info. Thanks in advance,
Smitty



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

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

sda1: __________________________________________________ _______________________

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

sda2: __________________________________________________ _______________________

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

sda5: __________________________________________________ _______________________

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

sdb1: __________________________________________________ _______________________

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: /Windows/System32/winload.exe

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

Drive: sda ___________________ __________________________________________________ ___

Disk /dev/sda: 1000.2 GB, 1000204886016 bytes
255 heads, 63 sectors/track, 121601 cylinders, total 1953525168 sectors
Units = sectors of 1 * 512 = 512 bytes
Disk identifier: 0xada241d7

Partition Boot Start End Size Id System

/dev/sda1 * 63 1,941,471,314 1,941,471,252 83 Linux
/dev/sda2 1,941,471,315 1,953,520,064 12,048,750 5 Extended
/dev/sda5 1,941,471,378 1,953,520,064 12,048,687 82 Linux swap / Solaris


Drive: sdb ___________________ __________________________________________________ ___

Disk /dev/sdb: 80.0 GB, 80026361856 bytes
255 heads, 63 sectors/track, 9729 cylinders, total 156301488 sectors
Units = sectors of 1 * 512 = 512 bytes
Disk identifier: 0xf7eef7ee

Partition Boot Start End Size Id System

/dev/sdb1 * 63 156,280,319 156,280,257 7 HPFS/NTFS


blkid -c /dev/null: __________________________________________________ __________

/dev/sda1: UUID="f9ed5b7b-b0e2-4586-92b8-1e02b35007c7" TYPE="ext4"
/dev/sda5: UUID="a9513f5e-8980-4d49-922c-d9ff9082f490" TYPE="swap"
/dev/sdb1: UUID="84E2D584E2D57B3E" TYPE="ntfs"

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

/dev/sda1 on / type ext4 (rw,errors=remount-ro)
proc on /proc type proc (rw)
none on /sys type sysfs (rw,noexec,nosuid,nodev)
none on /sys/fs/fuse/connections type fusectl (rw)
none on /sys/kernel/debug type debugfs (rw)
none on /sys/kernel/security type securityfs (rw)
udev on /dev type tmpfs (rw,mode=0755)
none on /dev/pts type devpts (rw,noexec,nosuid,gid=5,mode=0620)
none on /dev/shm type tmpfs (rw,nosuid,nodev)
none on /var/run type tmpfs (rw,nosuid,mode=0755)
none on /var/lock type tmpfs (rw,noexec,nosuid,nodev)
none on /lib/init/rw type tmpfs (rw,nosuid,mode=0755)
binfmt_misc on /proc/sys/fs/binfmt_misc type binfmt_misc (rw,noexec,nosuid,nodev)
gvfs-fuse-daemon on /home/marshall/.gvfs type fuse.gvfs-fuse-daemon (rw,nosuid,nodev,user=marshall)
/dev/sdb1 on /media/84E2D584E2D57B3E type fuseblk (rw,nosuid,nodev,allow_other,default_permissions,b lksize=4096)


=========================== sda1/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 /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 f9ed5b7b-b0e2-4586-92b8-1e02b35007c7
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 ###
set menu_color_normal=white/black
set menu_color_highlight=black/white
### END /etc/grub.d/05_debian_theme ###

### BEGIN /etc/grub.d/10_linux ###
menuentry "Ubuntu, Linux 2.6.31-9-rt" {
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 f9ed5b7b-b0e2-4586-92b8-1e02b35007c7
linux /boot/vmlinuz-2.6.31-9-rt root=UUID=f9ed5b7b-b0e2-4586-92b8-1e02b35007c7 ro quiet splash
initrd /boot/initrd.img-2.6.31-9-rt
}
menuentry "Ubuntu, Linux 2.6.31-9-rt (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 f9ed5b7b-b0e2-4586-92b8-1e02b35007c7
linux /boot/vmlinuz-2.6.31-9-rt root=UUID=f9ed5b7b-b0e2-4586-92b8-1e02b35007c7 ro single
initrd /boot/initrd.img-2.6.31-9-rt
}
### 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 ###
if [ ${timeout} != -1 ]; then
if keystatus; then
if keystatus --shift; then
set timeout=-1
else
set timeout=0
fi
else
if sleep --interruptible 3 ; then
set timeout=0
fi
fi
fi
### 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 ###

=============================== sda1/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/sda1 during installation
UUID=f9ed5b7b-b0e2-4586-92b8-1e02b35007c7 / ext4 errors=remount-ro 0 1
# swap was on /dev/sda5 during installation
UUID=a9513f5e-8980-4d49-922c-d9ff9082f490 none swap sw 0 0
/dev/scd0 /media/cdrom0 udf,iso9660 user,noauto,exec,utf8 0 0
/dev/fd0 /media/floppy0 auto rw,user,noauto,exec,utf8 0 0

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


.0GB: boot/grub/grub.cfg
.0GB: boot/initrd.img-2.6.31-9-rt
.0GB: boot/vmlinuz-2.6.31-9-rt
.0GB: initrd.img
.0GB: vmlinuz
=======Devices which don't seem to have a corresponding hard drive==============

sdc sdd sde sdf

jpmelos
December 6th, 2009, 09:36 PM
You can always change the boot sequence in your BIOS. Usually, you access it by pressing F2 or F3 before you computer loads an operating system.

If you mean you have both systems already installed in your HD, you need to configure your bootloader. In Ubuntu, download the startupmanager package(sudo apt-get install startupmanager), it's a graphic interface that does that.

Hope I helped!

darkod
December 6th, 2009, 09:42 PM
You seem to be missing the vista boot files. That why grub2 didn't locate them and didn't create entry for the grub menu. I don't know how you were booting vista before but if you look towards the top of the results file you can see under sdb1 in the boot files there are no /bootmgr and /boot/BCD that vista uses.
You could try to repair the vista boot process and after that grub2 should pick it up with update-grub. Info how to repair boot process for vista can be found here:
http://ubuntuforums.org/showthread.php?t=1014708

bigsmitty64
December 6th, 2009, 09:55 PM
You seem to be missing the vista boot files. That why grub2 didn't locate them and didn't create entry for the grub menu. I don't know how you were booting vista before but if you look towards the top of the results file you can see under sdb1 in the boot files there are no /bootmgr and /boot/BCD that vista uses.
You could try to repair the vista boot process and after that grub2 should pick it up with update-grub. Info how to repair boot process for vista can be found here:
http://ubuntuforums.org/showthread.php?t=1014708

Thanks darkrod,

Just to be certain here, I start on that page where it says this, right?

Hot to restore the Ubuntu Grub bootloader (9.10 and beyond)

darkod
December 6th, 2009, 09:59 PM
Yeah, you're not interested in grub right now. It continues how to restore XP boot, then vista and 7 boot. That's what you want.
Because that should restore vista boot on /dev/sdb your grub2 on /dev/sda should remain intact and fully functional. So I guess you should be able to boot into ubuntu again and do the:
sudo update-grub

to let grub2 find the repaired vista boot.

If by any chance you lose grub2 on /dev/sda, then you need the same article to restore grub2 from ubuntu 9.10 cd.

bigsmitty64
December 6th, 2009, 10:32 PM
O.K. I'll give it a go and get back to ya. Thanks man.

bigsmitty64
December 6th, 2009, 10:48 PM
O.K. I booted from the vista disk, and got to this point:

From the link you provided,

"On the next page, if it finds your Windows Vista/7 installation, make sure it is UNSELECTED before clicking next."

It didn't find my vista installation. Tried the command prompt anyways,but it did nothing. :)

darkod
December 6th, 2009, 10:55 PM
Repair your computer didn't find your vista? Ouch... I don't have an answer for that unfortunately. I hope we can trust MS that if there is windows installation it would be found.
I don't want to freak you out but you might be looking into vista reinstall. Check some MS forums about this problem, don't reinstall right now.
If it comes to that you can use Ubuntu to copy important data from the ntfs partitions on external hdd or the linux partitions. Sorry...

bigsmitty64
December 6th, 2009, 11:19 PM
I think you're correct sir. I decided to try and physically unplug the hard drive with Ubuntu on it,and boot from the windows drive. And got: BOOTMGR missing.

bigsmitty64
December 6th, 2009, 11:26 PM
Also,I can SEE the drive with windows from inside Ubuntu,and access all the files.So no worrys really,I can do like you said and copy any "personal files" to my ubuntu drive and just reinstall vista,I guess.

presence1960
December 6th, 2009, 11:33 PM
Also,I can SEE the drive with windows from inside Ubuntu,and access all the files.So no worrys really,I can do like you said and copy any "personal files" to my ubuntu drive and just reinstall vista,I guess.

when you reinstall vista make sure the "vista" disk is set to first in the hard disk boot order in BIOS. If it is not windows will attempt to write it's bootloader to whichever disk is first in the hard disk boot order, which in your case is your Ubuntu disk.

bigsmitty64
December 6th, 2009, 11:45 PM
I do that "during" the vista install correct?

darkod
December 6th, 2009, 11:48 PM
Yes, switch it before starting to install Vista. The point is when installing OSs on different drives, at time of install have that particular drive as first in BIOS. Especially for windows because I don't think you can select where to install the bootloader like you can with ubuntu. After vista install is done, switch back the ubuntu drive as first in boot order.

presence1960
December 6th, 2009, 11:52 PM
Yes, switch it before starting to install Vista. The point is when installing OSs on different drives, at time of install have that particular drive as first in BIOS. Especially for windows because I don't think you can select where to install the bootloader like you can with ubuntu. After vista install is done, switch back the ubuntu drive as first in boot order.

+1 that is a fact

Actually because windows always tries to put it's bootloader on the first disk is why the myth in here started that windows must be on the first disk, first primary partition. Thank God that is only a myth. I have had windows on first, second & fourth primary partitions on first, second & third disks on my rig.

bigsmitty64
December 7th, 2009, 12:09 AM
Alrighty then,I'll do this. Probably tomorrow though.I'll keep you guys up to date. Thanks a million.
Smitty