Unfortunately, it didn't work out after the purge and re-installation. This is the output from the script (done before my /mnt "trick" mentioned below):
Code:
Boot Info Script 0.55 dated February 15th, 2010
============================= Boot Info Summary: ==============================
=> Grub 2 is installed in the MBR of /dev/sda and looks on the same drive in
partition #1 for /boot/grub.
sda1: _________________________________________________________________________
File system: ext3
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
sda2: _________________________________________________________________________
File system: ext3
Boot sector type: -
Boot sector info:
Operating System:
Boot files/dirs:
sda3: _________________________________________________________________________
File system: swap
Boot sector type: -
Boot sector info:
=========================== Drive/Partition Info: =============================
Drive: sda ___________________ _____________________________________________________
Disk /dev/sda: 40.0 GB, 40020664320 bytes
16 heads, 63 sectors/track, 77545 cylinders, total 78165360 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 55,054,754 55,054,692 83 Linux
/dev/sda2 55,054,755 76,019,579 20,964,825 83 Linux
/dev/sda3 76,019,580 78,156,224 2,136,645 82 Linux swap / Solaris
blkid -c /dev/null: ____________________________________________________________
Device UUID TYPE LABEL
/dev/sda1 29dba925-9910-4629-8934-6e9e1085e1e4 ext3
/dev/sda2 67f5d3fa-908e-4ce9-8662-28cfad55f4fa ext3
/dev/sda3 45fbf60b-02e2-4e08-83ef-54fe451b0477 swap
/dev/sda: PTTYPE="dos"
============================ "mount | grep ^/dev output: ===========================
Device Mount_Point Type Options
/dev/sda1 / ext3 (rw,errors=remount-ro)
/dev/sda2 /home ext3 (rw)
=========================== 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 $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,1)'
search --no-floppy --fs-uuid --set 29dba925-9910-4629-8934-6e9e1085e1e4
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,1)'
search --no-floppy --fs-uuid --set 29dba925-9910-4629-8934-6e9e1085e1e4
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,1)'
search --no-floppy --fs-uuid --set 29dba925-9910-4629-8934-6e9e1085e1e4
linux /boot/vmlinuz-2.6.32-21-generic root=UUID=29dba925-9910-4629-8934-6e9e1085e1e4 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,1)'
search --no-floppy --fs-uuid --set 29dba925-9910-4629-8934-6e9e1085e1e4
echo 'Loading Linux 2.6.32-21-generic ...'
linux /boot/vmlinuz-2.6.32-21-generic root=UUID=29dba925-9910-4629-8934-6e9e1085e1e4 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,1)'
search --no-floppy --fs-uuid --set 29dba925-9910-4629-8934-6e9e1085e1e4
linux16 /boot/memtest86+.bin
}
menuentry "Memory test (memtest86+, serial console 115200)" {
insmod ext2
set root='(hd0,1)'
search --no-floppy --fs-uuid --set 29dba925-9910-4629-8934-6e9e1085e1e4
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 nodev,noexec,nosuid 0 0
# / was on /dev/sda1 during installation
UUID=29dba925-9910-4629-8934-6e9e1085e1e4 / ext3 errors=remount-ro 0 1
# /home was on /dev/sda2 during installation
UUID=67f5d3fa-908e-4ce9-8662-28cfad55f4fa /home ext3 defaults 0 2
# swap was on /dev/sda3 during installation
UUID=45fbf60b-02e2-4e08-83ef-54fe451b0477 none swap sw 0 0
/dev/fd0 /media/floppy0 auto rw,user,noauto,exec,utf8 0 0
=================== sda1: Location of files loaded by Grub: ===================
27.8GB: boot/grub/core.img
27.8GB: boot/grub/grub.cfg
27.8GB: boot/initrd.img-2.6.32-21-generic
27.8GB: boot/vmlinuz-2.6.32-21-generic
27.8GB: initrd.img
27.8GB: vmlinuz
Perhaps my /mnt recovery trick should be outlined in case it reveals something:
- Boot alternate CD in recovery mode.
- Start script in /dev/sda1 and then run the following commands (the update-grub is probably not needed but I've been doing it regardless):
Code:
mount /dev/sda1 /mnt
grub-install --root-directory=/mnt /dev/sda
update-grub
- Reboot. The [grub rescue] prompt is displayed.
- Issue the following commands:
Code:
set prefix=(hd0,1)/boot/grub
insmod linux
linux /vmlinuz root=/dev/sda1 ro
initrd /initrd.img
boot
- Voila... Ubuntu 10.04 is served! (with a boot-up time that is *much* faster than lilo - EDIT: See footnote for disclaimer).
I hope that can shed some light on my crazy PC. I don't need to input any other commands at the grub rescue prompt... the root variable is already setup fine.
Are there any disadvantages to lilo I should be aware of (other than the boot-up speed - EDIT: See footnote for disclaimer)?
Footnote re: Lilo:
- Initial bootup would take a good 30 seconds more than Grub2.
- After setting Lilo up with UUIDs, the bootup time was comparable to Grub2.
- I.e. Lilo isn't slow as I initially made out.
Bookmarks