PDA

View Full Version : [ubuntu] Boot Problem: XP and Ubuntu 10.4



l3ecl
May 10th, 2010, 08:37 AM
i had 10.4 installed perfectly under a different partition but when i try to boot xp, i get a missing hal.dll error. so i patched up xp but now cannot get into ubuntu. how do i fix this booting problem?

also my swap of 10g is probably overkill haha. it would be nice if i could change that. but its not a priority, i just want my ubuntu back!

here are my diagnostics:


Boot Info Script 0.55 dated February 15th, 2010

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

=> Windows is installed in the MBR of /dev/sda
=> Syslinux is installed in the MBR of /dev/sdb

sda1: __________________________________________________ _______________________

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

sda5: __________________________________________________ _______________________

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

sda2: __________________________________________________ _______________________

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

sda3: __________________________________________________ _______________________

File system: ntfs
Boot sector type: Windows XP
Boot sector info: No errors found in the Boot Parameter Block.
Operating System: Windows XP
Boot files/dirs: /boot.ini /ntldr /NTDETECT.COM

sdb1: __________________________________________________ _______________________

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

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

Drive: sda ___________________ __________________________________________________ ___

Disk /dev/sda: 60.0 GB, 60011642880 bytes
255 heads, 63 sectors/track, 7296 cylinders, total 117210240 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes

Partition Boot Start End Size Id System

/dev/sda1 2,046 21,483,519 21,481,474 5 Extended
/dev/sda5 2,048 21,483,519 21,481,472 82 Linux swap / Solaris
/dev/sda2 21,483,520 52,676,607 31,193,088 83 Linux
/dev/sda3 * 52,677,135 117,210,239 64,533,105 7 HPFS/NTFS


Drive: sdb ___________________ __________________________________________________ ___

Disk /dev/sdb: 2055 MB, 2055019520 bytes
16 heads, 63 sectors/track, 3981 cylinders, total 4013710 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes

Partition Boot Start End Size Id System

/dev/sdb1 * 63 4,013,709 4,013,647 b W95 FAT32


blkid -c /dev/null: __________________________________________________ __________

Device UUID TYPE LABEL

/dev/loop0 squashfs
/dev/ramzswap0 swap
/dev/sda1: PTTYPE="dos"
/dev/sda2 f7b3fe51-b14f-485f-be91-4cff9fa45112 ext4
/dev/sda3 90ACCE3BACCE1C1A ntfs
/dev/sda5 ee5114dd-c952-4e4a-9fc8-ac5d12f6569b swap
/dev/sda: PTTYPE="dos"
/dev/sdb1 5C1A-6088 vfat PORTABLE
/dev/sdb: PTTYPE="dos"

============================ "mount | grep ^/dev output: ===========================

Device Mount_Point Type Options

aufs / aufs (rw)
/dev/sr0 /cdrom iso9660 (ro,noatime)
/dev/loop0 /rofs squashfs (ro,noatime)
/dev/sdb1 /media/PORTABLE vfat (rw,nosuid,nodev,uhelper=udisks,uid=999,gid=999,sh ortname=mixed,dmask=0077,utf8=1,flush)


=========================== sda2/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 $prefix/grubenv ]; then
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
}
insmod ext2
set root='(hd0,3)'
search --no-floppy --fs-uuid --set f7b3fe51-b14f-485f-be91-4cff9fa45112
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
insmod ext2
set root='(hd0,3)'
search --no-floppy --fs-uuid --set f7b3fe51-b14f-485f-be91-4cff9fa45112
set locale_dir=($root)/boot/grub/locale
set lang=en
insmod gettext
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
### END /etc/grub.d/05_debian_theme ###

### BEGIN /etc/grub.d/10_linux ###
menuentry 'Ubuntu, with Linux 2.6.32-21-generic' --class ubuntu --class gnu-linux --class gnu --class os {
recordfail
insmod ext2
set root='(hd0,3)'
search --no-floppy --fs-uuid --set f7b3fe51-b14f-485f-be91-4cff9fa45112
linux /boot/vmlinuz-2.6.32-21-generic root=UUID=f7b3fe51-b14f-485f-be91-4cff9fa45112 ro quiet splash
initrd /boot/initrd.img-2.6.32-21-generic
}
menuentry 'Ubuntu, with Linux 2.6.32-21-generic (recovery mode)' --class ubuntu --class gnu-linux --class gnu --class os {
recordfail
insmod ext2
set root='(hd0,3)'
search --no-floppy --fs-uuid --set f7b3fe51-b14f-485f-be91-4cff9fa45112
echo 'Loading Linux 2.6.32-21-generic ...'
linux /boot/vmlinuz-2.6.32-21-generic root=UUID=f7b3fe51-b14f-485f-be91-4cff9fa45112 ro single
echo 'Loading initial ramdisk ...'
initrd /boot/initrd.img-2.6.32-21-generic
}
### END /etc/grub.d/10_linux ###

### BEGIN /etc/grub.d/20_memtest86+ ###
menuentry "Memory test (memtest86+)" {
insmod ext2
set root='(hd0,3)'
search --no-floppy --fs-uuid --set f7b3fe51-b14f-485f-be91-4cff9fa45112
linux16 /boot/memtest86+.bin
}
menuentry "Memory test (memtest86+, serial console 115200)" {
insmod ext2
set root='(hd0,3)'
search --no-floppy --fs-uuid --set f7b3fe51-b14f-485f-be91-4cff9fa45112
linux16 /boot/memtest86+.bin console=ttyS0,115200n8
}
### END /etc/grub.d/20_memtest86+ ###

### BEGIN /etc/grub.d/30_os-prober ###
menuentry "Microsoft Windows XP Professional (on /dev/sda2)" {
insmod ntfs
set root='(hd0,2)'
search --no-floppy --fs-uuid --set 90acce3bacce1c1a
drivemap -s (hd0) ${root}
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 ###

=============================== sda2/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 nodev,noexec,nosuid 0 0
# / was on /dev/sda3 during installation
UUID=f7b3fe51-b14f-485f-be91-4cff9fa45112 / ext4 errors=remount-ro 0 1
# swap was on /dev/sda5 during installation
UUID=ee5114dd-c952-4e4a-9fc8-ac5d12f6569b none swap sw 0 0

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


24.0GB: boot/grub/core.img
19.9GB: boot/grub/grub.cfg
24.0GB: boot/initrd.img-2.6.32-21-generic
24.0GB: boot/vmlinuz-2.6.32-21-generic
24.0GB: initrd.img
24.0GB: vmlinuz

================================ sda3/boot.ini: ================================

[boot loader]
timeout=30
default=multi(0)disk(0)rdisk(0)partition(2)\WINDOW S
[operating systems]
multi(0)disk(0)rdisk(0)partition(2)\WINDOWS="Microsoft Windows XP Professional" /noexecute=optin /fastdetect

C:\wubildr.mbr="Ubuntu C"
D:\wubildr.mbr="Ubuntu D"
E:\wubildr.mbr="Ubuntu E"
F:\wubildr.mbr="Ubuntu F"
C:\grldr="Start GRUB4DOS"



=========================== Unknown MBRs/Boot Sectors/etc =======================

Unknown BootLoader on sda1

00000000 61 7a 94 79 70 bc 97 46 60 52 8a b1 9a 43 5b 5d |az.yp..F`R...C[]|
00000010 61 a7 a0 3a dc c3 29 72 66 76 a5 99 40 7a 5f 87 |a..:..)rfv..@z_.|
00000020 94 8f 46 9e 8b 4b 76 6c 6f 5a 5e 68 ac 84 51 c8 |..F..KvloZ^h..Q.|
00000030 a5 3f 82 75 56 81 72 71 82 74 71 b7 8a 56 bf a6 |.?.uV.rq.tq..V..|
00000040 47 5c 5f 64 a0 77 6c 5e 4f 89 c9 b8 2e 7f 6f 77 |G\_d.wl^O.....ow|
00000050 5e 51 85 8e 6e 79 85 75 75 76 68 7b bf 96 52 ae |^Q..ny.uuvh{..R.|
00000060 80 5b bb 9b 41 c0 96 4c cd ad 38 aa 7e 57 66 5a |.[..A..L..8.~WfZ|
00000070 82 a9 88 60 78 7d 60 8c 7b 6d a2 7b 55 ae 96 46 |...`x}`.{m.{U..F|
00000080 5d 4f 86 a6 77 5c 7c 6b 5a 87 74 59 ca a8 3f d4 |]O..w\|kZ.tY..?.|
00000090 b8 36 ba 8d 59 86 77 6d a9 90 49 5c 5e 62 83 71 |.6..Y.wm..I\^b.q|
000000a0 7a 71 5a 8a 78 6d 5b 65 54 8c c6 b1 32 c6 b4 2f |zqZ.xm[eT...2../|
000000b0 b8 9a 51 7d 80 58 6f 5d 88 a5 73 6d 7a 6a 5c af |..Q}.Xo]..smzj\.|
000000c0 7d 61 d6 c2 28 8d 7c 6c cd ac 3d a2 76 5b 86 76 |}a..(.|l..=.v[.v|
000000d0 71 aa 76 68 b7 aa 3a 77 5d 88 b7 a0 4d a3 74 6b |q.vh..:w]...M.tk|
000000e0 d7 bd 2f cc ab 3a 6f 70 62 7a 77 58 7d 6d 5b 67 |../..:opbzwX}m[g|
000000f0 68 61 5f 51 8c 70 58 8c 66 53 90 d9 bd 31 b8 a9 |ha_Q.pX.fS...1..|
00000100 39 8f 7f 6a a7 75 67 74 6f 5a 77 7b 61 7b 67 7e |9..j.ugtoZw{a{g~|
00000110 b7 94 45 b5 92 48 d0 b7 38 b3 8f 58 96 76 70 9e |..E..H..8..X.vp.|
00000120 7f 68 df c4 2b b7 ac 36 aa 78 5f bf a0 3e b1 80 |.h..+..6.x_..>..|
00000130 5f d8 c4 27 dc c1 2f 57 5e 67 9d 76 59 7c 70 70 |_..'../W^g.vY|pp|
00000140 86 6e 79 61 53 86 9b 87 4d 67 63 5e a6 73 67 d0 |.nyaS...Mgc^.sg.|
00000150 b8 30 a1 90 48 d0 af 3a 89 71 76 86 78 70 87 12 |.0..H..:.qv.xp..|
00000160 bf 5d 00 00 03 bd 49 44 41 54 18 19 05 c1 79 4c |.]....IDAT....yL|
00000170 d6 05 00 00 d0 f7 73 cd 52 a6 99 84 a9 30 d7 1c |......s.R....0..|
00000180 f5 4d 9d 82 c6 72 9a 85 46 60 e6 48 0b 67 a2 e9 |.M...r..F`.H.g..|
00000190 02 f5 43 99 c5 42 4d 10 3c 96 1a 39 0d 47 87 1c |..C..BM.<..9.G..|
000001a0 22 a9 1d 5a ea 92 3f 5c 0b c1 86 42 2d 33 92 2c |"..Z..?\...B-3.,|
000001b0 13 31 9b 78 94 09 63 b1 31 6c 8a f6 5e 30 00 20 |.1.x..c.1l..^0. |
000001c0 21 00 82 49 d0 ff 02 00 00 00 00 c8 47 01 00 00 |!..I........G...|
000001d0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................|
*
000001f0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 55 aa |..............U.|
00000200

lechien73
May 10th, 2010, 09:16 AM
Your boot_info_script output shows that Windows has restored its bootloader into the MBR of /sda - your primary hard drive.

To get Grub working again for both Ubuntu and Windows, follow these instructions (http://ubuntuforums.org/showthread.php?t=1014708), under the heading: "How to restore the Ubuntu grub bootloader (9.10 and beyond)"

wilee-nilee
May 10th, 2010, 09:35 AM
mmm

darkod
May 10th, 2010, 09:58 AM
Also, if this is a brand new ubuntu I would consider deleting this installation and doing it again with smaller swap and bigger root. Like you said, 10GB swap is overkill and you have only 15GB root remaining.

That's plenty for a root partition (depending what type of files you store in your /home which is part of /) but the space is sitting just wasted in the swap partition. Reinstall now before starting to load software and settings. Resizing the root can be more complicated later and unneeded if you can make another new install now.

rcadby
June 4th, 2010, 07:26 PM
I did an upgrade from 9.10 to 10.4. The upgrade got interrupted (my connection sucks), but I managed to complete the update (let it run all night). However, I'm having a multitude of different boot problems.

I do not have a dual boot.

The boot hangs several times before it finally finishes. It either freezes at some point or hangs with color bars.

I have tried all sorts of ways (F2, F12, Esc, power off and on) and after several attempts will finally get it running.

Is there a way to re-load 10.4 or get back to 9.10?

Is there any known conflicts of add-ons or extensions with 10.4 that I should know about so that I can remove them?

darkod
June 4th, 2010, 07:35 PM
I did an upgrade from 9.10 to 10.4. The upgrade got interrupted (my connection sucks), but I managed to complete the update (let it run all night). However, I'm having a multitude of different boot problems.

I do not have a dual boot.

The boot hangs several times before it finally finishes. It either freezes at some point or hangs with color bars.

I have tried all sorts of ways (F2, F12, Esc, power off and on) and after several attempts will finally get it running.

Is there a way to re-load 10.4 or get back to 9.10?

Is there any known conflicts of add-ons or extensions with 10.4 that I should know about so that I can remove them?

Your problem has nothing to do with the OP problem. Why did you decide to post in a 3 weeks old thread?

Make a new thread, and run the boot info script and post the content of your results file. If you need instructions:
http://ubuntuforums.org/showpost.php?p=8844901&postcount=4

Also, did you try to run 10.04 in live mode before upgrading? Running the cd in live mode can show any hardware issues.

rcadby
June 4th, 2010, 08:40 PM
Your problem has nothing to do with the OP problem.

OK. I have to admit, up front, that I'm not as smart as the folks here.

Why did you decide to post in a 3 weeks old thread?

Well, I did a bunch of searching re 10.4 boot problems and landed here.

Make a new thread, and run the boot info script and post the content of your results file. If you need instructions:
http://ubuntuforums.org/showpost.php?p=8844901&postcount=4

I'll check this out. As you can tell, I'm new here.

Also, did you try to run 10.04 in live mode before upgrading?

No, as I think I said, I did an update, not a new install...did not have a CD.

Running the cd in live mode can show any hardware issues.

Well, if they are hardware issues, I didn't have them with the 9.10 version I was running.

I'm sorry I bothered you. I was looking for help, not discouragement.

wilee-nilee
June 4th, 2010, 08:48 PM
Well, if they are hardware issues, I didn't have them with the 9.10 version I was running.

I'm sorry I bothered you. I was looking for help, not discouragement.

Holster your ego, and it might help to know that the person who responded to you is on the forums every day and is one of the best at helping in this area. Take the logical advice, which is based on common sense and the rules of the forum, and follow it if you really want qualified help. ;)

rcadby
June 4th, 2010, 09:13 PM
Holster your ego, and it might help to know that the person who responded to you is on the forums every day and is one of the best at helping in this area.

You're right, of course. I shouldn't expect answers to dumb questions and didn't get them.

Take the logical advice, which is based on common sense and the rules of the forum, and follow it if you really want qualified help. ;)

OK. I'll work it out. Thanks, anyway. I should know better than to take/make it personal. I normally try to never do that. I apologize.



Bye.

wilee-nilee
June 4th, 2010, 09:35 PM
Bye.

I think we all have been in a tight position at some point and let that overtake our reasoning, hey I do it on a daily basis in some way or another.

Your problem though will be exposed with the bootscript so even if you don't start a thread down load and run it and look to see if grub is in a MS part of a dual boot, if thats your set up. I suggest this in that if it is, there are some specific fixes for this and just pecking at it may make it worse leaving you with only being able to recover data rather then just fix it. ;)

rcadby
June 4th, 2010, 10:33 PM
I think we all have been in a tight position at some point and let that overtake our reasoning, hey I do it on a daily basis in some way or another.

Your problem though will be exposed with the bootscript so even if you don't start a thread down load and run it and look to see if grub is in a MS part of a dual boot, if thats your set up. I suggest this in that if it is, there are some specific fixes for this and just pecking at it may make it worse leaving you with only being able to recover data rather then just fix it. ;)

OK. As I had said, I don't have a dual boot. The original install replaced the MS XP (I thought) and was an ubuntu 8.04 ISO download, then a 9.10 upgrade and finally the recent 10.4 upgrade.

After a Restart and running the bootscript I get this:

<code>
Boot Info Script 0.55 dated February 15th, 2010

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

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

sda1: __________________________________________________ _______________________

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

sda2: __________________________________________________ _______________________

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

sda5: __________________________________________________ _______________________

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

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

Drive: sda ___________________ __________________________________________________ ___

Disk /dev/sda: 120.0 GB, 120034123776 bytes
255 heads, 63 sectors/track, 14593 cylinders, total 234441648 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes

Partition Boot Start End Size Id System

/dev/sda1 * 63 229,167,224 229,167,162 83 Linux
/dev/sda2 229,167,225 234,436,544 5,269,320 5 Extended
/dev/sda5 229,167,288 234,436,544 5,269,257 82 Linux swap / Solaris


blkid -c /dev/null: __________________________________________________ __________

Device UUID TYPE LABEL

/dev/sda1 70695576-f73d-47ba-ab89-88b8c59b2a31 ext3
/dev/sda2: PTTYPE="dos"
/dev/sda5 f64aca2b-5eaf-4bbb-b597-6e61cdc90b19 swap
/dev/sda: PTTYPE="dos"

============================ "mount | grep ^/dev output: ===========================

Device Mount_Point Type Options

/dev/sda1 / ext3 (rw,relatime,errors=remount-ro)


=========================== sda1/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 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 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=70695576-f73d-47ba-ab89-88b8c59b2a31 ro

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

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

## 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 10.04 LTS, kernel 2.6.32-22-generic
root (hd0,0)
kernel /boot/vmlinuz-2.6.32-22-generic root=UUID=70695576-f73d-47ba-ab89-88b8c59b2a31 ro quiet splash
initrd /boot/initrd.img-2.6.32-22-generic
quiet

title Ubuntu 10.04 LTS, kernel 2.6.32-22-generic (recovery mode)
root (hd0,0)
kernel /boot/vmlinuz-2.6.32-22-generic root=UUID=70695576-f73d-47ba-ab89-88b8c59b2a31 ro single
initrd /boot/initrd.img-2.6.32-22-generic

title Ubuntu 10.04 LTS, kernel 2.6.31-21-generic
root (hd0,0)
kernel /boot/vmlinuz-2.6.31-21-generic root=UUID=70695576-f73d-47ba-ab89-88b8c59b2a31 ro quiet splash
initrd /boot/initrd.img-2.6.31-21-generic
quiet

title Ubuntu 10.04 LTS, kernel 2.6.31-21-generic (recovery mode)
root (hd0,0)
kernel /boot/vmlinuz-2.6.31-21-generic root=UUID=70695576-f73d-47ba-ab89-88b8c59b2a31 ro single
initrd /boot/initrd.img-2.6.31-21-generic

title Ubuntu 10.04 LTS, kernel 2.6.28-18-generic
root (hd0,0)
kernel /boot/vmlinuz-2.6.28-18-generic root=UUID=70695576-f73d-47ba-ab89-88b8c59b2a31 ro quiet splash
initrd /boot/initrd.img-2.6.28-18-generic
quiet

title Ubuntu 10.04 LTS, kernel 2.6.28-18-generic (recovery mode)
root (hd0,0)
kernel /boot/vmlinuz-2.6.28-18-generic root=UUID=70695576-f73d-47ba-ab89-88b8c59b2a31 ro single
initrd /boot/initrd.img-2.6.28-18-generic

title Ubuntu 10.04 LTS, kernel 2.6.27-17-generic
root (hd0,0)
kernel /boot/vmlinuz-2.6.27-17-generic root=UUID=70695576-f73d-47ba-ab89-88b8c59b2a31 ro quiet splash
initrd /boot/initrd.img-2.6.27-17-generic
quiet

title Ubuntu 10.04 LTS, kernel 2.6.27-17-generic (recovery mode)
root (hd0,0)
kernel /boot/vmlinuz-2.6.27-17-generic root=UUID=70695576-f73d-47ba-ab89-88b8c59b2a31 ro single
initrd /boot/initrd.img-2.6.27-17-generic

title Ubuntu 10.04 LTS, memtest86+
root (hd0,0)
kernel /boot/memtest86+.bin
quiet

### END DEBIAN AUTOMAGIC KERNELS LIST

=============================== sda1/etc/fstab: ===============================

# /etc/fstab: static file system information.
#
# <file system> <mount point> <type> <options> <dump> <pass>
proc /proc proc defaults 0 0
# /dev/sda1
UUID=70695576-f73d-47ba-ab89-88b8c59b2a31 / ext3 relatime,errors=remount-ro 0 1
# /dev/sda5
UUID=f64aca2b-5eaf-4bbb-b597-6e61cdc90b19 none swap sw 0 0
/dev/scd0 /media/cdrom0 udf,iso9660 user,noauto,exec,utf8 0 0

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


101.6GB: boot/grub/menu.lst
101.6GB: boot/grub/stage2
101.6GB: boot/initrd.img-2.6.27-17-generic
101.7GB: boot/initrd.img-2.6.28-18-generic
101.6GB: boot/initrd.img-2.6.31-21-generic
101.6GB: boot/initrd.img-2.6.32-22-generic
101.7GB: boot/vmlinuz-2.6.27-17-generic
101.6GB: boot/vmlinuz-2.6.28-18-generic
101.6GB: boot/vmlinuz-2.6.31-21-generic
101.6GB: boot/vmlinuz-2.6.32-22-generic
101.6GB: initrd.img
101.6GB: initrd.img.old
101.6GB: vmlinuz
101.6GB: vmlinuz.old
</code>

which is all Greek to me.

Please note that I have uninstalled "Tracking", a file indexing program that facilitated easy searching for 'stuff'. It ran in the background and updated itself at startup. It seemed to slow operations down and I suspected it might have been affecting startups. So, since then, I have actually booted twice in a row with only small problems (flashing of different screens before settling into a normal boot).

It's possible the booting and operation can now be 'lived with', but I'm not sure all the weirdness is gone, yet.

If you spot something that obviously needs fixing from the boot report above I'd appreciate your feedback.

Thanks......Ron

wilee-nilee
June 4th, 2010, 10:59 PM
The few things I see is that since you upgraded starting from Hardy you don't have the advantages of ext4 in partitioning, and I think grub2 is easier to deal with but thats just me. You also appear to have some sort of password lock and a xen something, I don't know what these are. It looks from a armchair view that the customizations you have done along with updating instead of a fresh install somewhere in there due to the default partition changes and grub changes to grub2, have left you with a difficult system.

Since Lucid is working I would just back up what you want to save, could be just shrinking the main partition, and moving this back up to another partition and doing a fresh install that can be customized as you like might be the best answer. Personally I just keep everything I need to save on a external HD and hardly anything on my computer, so a external backup works for me. I also always have the ISO of installed OS's burned to a cd or loaded to a thumb so when all else fails I can access the installed OS and tweak if needed. This way that I do things is basically the same as having a insurance policy.

This change in partition types and grub has caused some problems with some peoples systems basically due to user error generally and using a confirmation bias to negate the great performance and ease of access given by ext4 partitioning and grub2, and fresh installs. Also just not recognizing that a fresh install in the end really is the cleanest setup; especially if a user is not able to really search and find any inherent problems with a continuous upgrades schema.

oldfred
June 4th, 2010, 11:12 PM
I do not see anything wrong. Yes it is old grub but if it works that is ok. The future is grub2 and eventually you will convert. Some like ext4, I have had no troubles, but others want to stick to ext3.

I think it was my 9.04 install that had trouble with either the tracker or the nvidia as I had 100% processor until I turned off tracker but also updated nvidia at the same time so I do not know for sure.

Since I have separate /home (and /dats) I only need 20-25GB for root so I do new install into a new root partition. I had such good luck with Karmic I am doing that from now on, but it still requires additional work to copy over programs and system settings that are not in /home.

wilee-nilee
June 4th, 2010, 11:25 PM
I do not see anything wrong. Yes it is old grub but if it works that is ok. The future is grub2 and eventually you will convert. Some like ext4, I have had no troubles, but others want to stick to ext3.

I think it was my 9.04 install that had trouble with either the tracker or the nvidia as I had 100% processor until I turned off tracker but also updated nvidia at the same time so I do not know for sure.

Since I have separate /home (and /dats) I only need 20-25GB for root so I do new install into a new root partition. I had such good luck with Karmic I am doing that from now on, but it still requires additional work to copy over programs and system settings that are not in /home.

Thanks for your help here, I'm not fully up on reading that bootscript with the skills you and darkod have or the just overall knowledge base.

I am going to start using this home partition schema when I get my netbook repaired and reinstall the OS's I want.
So at the least I understand how that works. I assume that you have to do a automount of the static home I'm not sure though, it would make sense that it is auto mounted anyway, but as I said I'm not sure.

rcadby
June 7th, 2010, 05:45 PM
Thanks for your help here, I'm not fully up on reading that bootscript with the skills you and darkod have or the just overall knowledge base.

I am going to start using this home partition schema when I get my netbook repaired and reinstall the OS's I want.
So at the least I understand how that works. I assume that you have to do a automount of the static home I'm not sure though, it would make sense that it is auto mounted anyway, but as I said I'm not sure.

I'm not sure how to mark my post(s) SOLVED, but wish to thank y'all for the help.

I lied. The problem was not solved. It still only booted after a lot of re-boots using an attached monitor that would work part of the times.

What I've done is downloaded the 10.4 ISO, copied it to a CD and a USB stick and then booted from both successfully. After that, my normal boot has also been working....'normally' and (so far) the weirdness (freezing, flashing color bar screens) has not occurred again.

WRONG!

I'm guessing the new ISO boot wrote over some corruption that occurred when I did the 9.10-10.4 upgrade. Does that sound right?

I ended up finding ~/boot/grub/grub.cfg (in new partition, .../menu.lst in old) that had options "quiet splash" that were making the display hang freezing the computer. I removed them and now it shuts down, sleeps, hibernates, et al and comes back or boots OK now.