On Sun, Oct 7, 2012 at 10:37 AM, Kevin O'Gorman <kogorman@gmail.com> wrote:
> On Sat, Oct 6, 2012 at 6:35 AM, Tom H <tomh0665@gmail.com> wrote:
>> On Fri, Oct 5, 2012 at 7:01 PM, Kevin O'Gorman <kogorman@gmail.com> wrote:
>>>
>>> When I had just installed Xubuntu, the grub menu would show its
>>> 3.0.0-26 kernel at the first two lines, followed by memtest, then the
>>> Ubuntu 2.6.x kernels with an explicit root for Ubuntu. The 3.0.0
>>> lines would boot to Xubuntu, and the 2.6 lines to Ubuntu.
>>
>> Please run bootinfoscript [1] and upload the results because I (for
>> one) don't understand your description of your setup.
>>
>> 1. http://sourceforge.net/projects/bootinfoscript/files/bootinfoscript/
>
> Nice script.
>
> When I ran this, the apparent state of things was that I had a working
> Xubuntu 12.04.1 on /dev/sdb2, and an unbootable Ubuntu 11.10 on
> /dev/sdb7.
>
> This brokenness of the 11.10 does not particularly trouble me, since I
> was migrating towards Xubuntu anyway, and I can mount the older setup
> to retrieve what I need. At the moment, I'm reluctant to try to
> rectify it for fear of losing the bootability of the Xubuntu. I've
> had to reinstall it once already, and I'd rather not do it again.
Oh, and the results of the bootinfo script are attached.
--
Kevin O'Gorman
programmer, n. an organism that transmutes caffeine into software.
Boot Info Script 0.61 [1 April 2012]
============================= Boot Info Summary: ===============================
=> Grub2 (v1.99) is installed in the MBR of /dev/sda and looks at sector 1 of
the same hard drive for core.img. core.img is at this location and uses an
embedded config file:
---------------------------------------------------------------------------
search.fs_uuid a70b0f4f-488b-439e-9cd0-5abb88ba7024 root
set prefix=($root)/boot/grub
---------------------------------------------------------------------------
-----.
=> Grub2 (v1.99) is installed in the MBR of /dev/sdb and looks at sector 1 of
the same hard drive for core.img. core.img is at this location and looks
for (,msdos2)/boot/grub on this drive.
=> Grub2 (v1.99) is installed in the MBR of /dev/sdc and looks at sector 1 of
the same hard drive for core.img. core.img is at this location and uses an
embedded config file:
---------------------------------------------------------------------------
search.fs_uuid a70b0f4f-488b-439e-9cd0-5abb88ba7024 root
set prefix=($root)/boot/grub
---------------------------------------------------------------------------
-----.
File system: vfat
Boot sector type: FAT32
Boot sector info: According to the info in the boot sector, sdb6 starts
at sector 0. But according to the info from fdisk,
sdb6 starts at sector 483936256.
Operating System:
Boot files:
--------------------------------------------------------------------------------
#
# 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
}
insmod part_msdos
insmod ext2
set root='(hd1,msdos2)'
search --no-floppy --fs-uuid --set=root ab460680-9e94-4898-8b46-f28d1615bf7b
if loadfont /usr/share/grub/unicode.pf2 ; then
set gfxmode=auto
load_video
insmod gfxterm
insmod part_msdos
insmod ext2
set root='(hd1,msdos2)'
search --no-floppy --fs-uuid --set=root ab460680-9e94-4898-8b46-f28d1615bf7b
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
### END /etc/grub.d/05_debian_theme ###
### BEGIN /etc/grub.d/10_linux ###
function gfxmode {
set gfxpayload="${1}"
if [ "${1}" = "keep" ]; then
set vt_handoff=vt.handoff=7
else
set vt_handoff=
fi
}
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.2.0-31-generic-pae' --class ubuntu --class gnu-linux --class gnu --class os {
recordfail
gfxmode $linux_gfx_mode
insmod gzio
insmod part_msdos
insmod ext2
set root='(hd1,msdos2)'
search --no-floppy --fs-uuid --set=root ab460680-9e94-4898-8b46-f28d1615bf7b
linux /boot/vmlinuz-3.2.0-31-generic-pae root=UUID=ab460680-9e94-4898-8b46-f28d1615bf7b ro quiet splash $vt_handoff
initrd /boot/initrd.img-3.2.0-31-generic-pae
}
menuentry 'Ubuntu, with Linux 3.2.0-31-generic-pae (recovery mode)' --class ubuntu --class gnu-linux --class gnu --class os {
recordfail
insmod gzio
insmod part_msdos
insmod ext2
set root='(hd1,msdos2)'
search --no-floppy --fs-uuid --set=root ab460680-9e94-4898-8b46-f28d1615bf7b
echo 'Loading Linux 3.2.0-31-generic-pae ...'
linux /boot/vmlinuz-3.2.0-31-generic-pae root=UUID=ab460680-9e94-4898-8b46-f28d1615bf7b ro recovery nomodeset
echo 'Loading initial ramdisk ...'
initrd /boot/initrd.img-3.2.0-31-generic-pae
}
submenu "Previous Linux versions" {
menuentry 'Ubuntu, with Linux 3.2.0-31-generic' --class ubuntu --class gnu-linux --class gnu --class os {
recordfail
gfxmode $linux_gfx_mode
insmod gzio
insmod part_msdos
insmod ext2
set root='(hd1,msdos2)'
search --no-floppy --fs-uuid --set=root ab460680-9e94-4898-8b46-f28d1615bf7b
linux /boot/vmlinuz-3.2.0-31-generic root=UUID=ab460680-9e94-4898-8b46-f28d1615bf7b ro quiet splash $vt_handoff
initrd /boot/initrd.img-3.2.0-31-generic
}
menuentry 'Ubuntu, with Linux 3.2.0-31-generic (recovery mode)' --class ubuntu --class gnu-linux --class gnu --class os {
recordfail
insmod gzio
insmod part_msdos
insmod ext2
set root='(hd1,msdos2)'
search --no-floppy --fs-uuid --set=root ab460680-9e94-4898-8b46-f28d1615bf7b
echo 'Loading Linux 3.2.0-31-generic ...'
linux /boot/vmlinuz-3.2.0-31-generic root=UUID=ab460680-9e94-4898-8b46-f28d1615bf7b ro recovery nomodeset
echo 'Loading initial ramdisk ...'
initrd /boot/initrd.img-3.2.0-31-generic
}
menuentry 'Ubuntu, with Linux 3.2.0-29-generic' --class ubuntu --class gnu-linux --class gnu --class os {
recordfail
gfxmode $linux_gfx_mode
insmod gzio
insmod part_msdos
insmod ext2
set root='(hd1,msdos2)'
search --no-floppy --fs-uuid --set=root ab460680-9e94-4898-8b46-f28d1615bf7b
linux /boot/vmlinuz-3.2.0-29-generic root=UUID=ab460680-9e94-4898-8b46-f28d1615bf7b ro quiet splash $vt_handoff
initrd /boot/initrd.img-3.2.0-29-generic
}
menuentry 'Ubuntu, with Linux 3.2.0-29-generic (recovery mode)' --class ubuntu --class gnu-linux --class gnu --class os {
recordfail
insmod gzio
insmod part_msdos
insmod ext2
set root='(hd1,msdos2)'
search --no-floppy --fs-uuid --set=root ab460680-9e94-4898-8b46-f28d1615bf7b
echo 'Loading Linux 3.2.0-29-generic ...'
linux /boot/vmlinuz-3.2.0-29-generic root=UUID=ab460680-9e94-4898-8b46-f28d1615bf7b ro recovery nomodeset
echo 'Loading initial ramdisk ...'
initrd /boot/initrd.img-3.2.0-29-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='(hd1,msdos2)'
search --no-floppy --fs-uuid --set=root ab460680-9e94-4898-8b46-f28d1615bf7b
linux16 /boot/memtest86+.bin
}
menuentry "Memory test (memtest86+, serial console 115200)" {
insmod part_msdos
insmod ext2
set root='(hd1,msdos2)'
search --no-floppy --fs-uuid --set=root ab460680-9e94-4898-8b46-f28d1615bf7b
linux16 /boot/memtest86+.bin console=ttyS0,115200n8
}
### END /etc/grub.d/20_memtest86+ ###
### BEGIN /etc/grub.d/30_os-prober ###
menuentry "Ubuntu, with Linux 3.0.0-26-generic-pae (on /dev/sdb7)" --class gnu-linux --class gnu --class os {
insmod part_msdos
insmod ext2
set root='(hd1,msdos7)'
search --no-floppy --fs-uuid --set=root a70b0f4f-488b-439e-9cd0-5abb88ba7024
linux /boot/vmlinuz-3.0.0-26-generic-pae root=/dev/sda7 ro quiet splash vt.handoff=7
}
menuentry "Ubuntu, with Linux 3.0.0-26-generic-pae (recovery mode) (on /dev/sdb7)" --class gnu-linux --class gnu --class os {
insmod part_msdos
insmod ext2
set root='(hd1,msdos7)'
search --no-floppy --fs-uuid --set=root a70b0f4f-488b-439e-9cd0-5abb88ba7024
linux /boot/vmlinuz-3.0.0-26-generic-pae root=/dev/sda7 ro recovery nomodeset
}
menuentry "Ubuntu, with Linux 2.6.38-16-generic-pae (on /dev/sdb7)" --class gnu-linux --class gnu --class os {
insmod part_msdos
insmod ext2
set root='(hd1,msdos7)'
search --no-floppy --fs-uuid --set=root a70b0f4f-488b-439e-9cd0-5abb88ba7024
linux /boot/vmlinuz-2.6.38-16-generic-pae root=UUID=a70b0f4f-488b-439e-9cd0-5abb88ba7024 ro quiet splash vt.handoff=7
initrd /boot/initrd.img-2.6.38-16-generic-pae
}
menuentry "Ubuntu, with Linux 2.6.38-16-generic-pae (recovery mode) (on /dev/sdb7)" --class gnu-linux --class gnu --class os {
insmod part_msdos
insmod ext2
set root='(hd1,msdos7)'
search --no-floppy --fs-uuid --set=root a70b0f4f-488b-439e-9cd0-5abb88ba7024
linux /boot/vmlinuz-2.6.38-16-generic-pae root=UUID=a70b0f4f-488b-439e-9cd0-5abb88ba7024 ro recovery nomodeset
initrd /boot/initrd.img-2.6.38-16-generic-pae
}
### 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 ###
--------------------------------------------------------------------------------
--------------------------------------------------------------------------------
# /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/sdb2 during installation
UUID=ab460680-9e94-4898-8b46-f28d1615bf7b / ext4 errors=remount-ro 0 1
# swap was on /dev/sdb8 during installation
UUID=8b3a6d4a-8881-48c0-aff8-f77f70e096bf none swap sw 0 0
--------------------------------------------------------------------------------
#
# 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
}
insmod part_msdos
insmod ext2
set root='(hd0,msdos7)'
search --no-floppy --fs-uuid --set=root a70b0f4f-488b-439e-9cd0-5abb88ba7024
if loadfont /usr/share/grub/unicode.pf2 ; then
set gfxmode=auto
load_video
insmod gfxterm
insmod part_msdos
insmod ext2
set root='(hd0,msdos7)'
search --no-floppy --fs-uuid --set=root a70b0f4f-488b-439e-9cd0-5abb88ba7024
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
### 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-26-generic-pae' --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,msdos7)'
search --no-floppy --fs-uuid --set=root a70b0f4f-488b-439e-9cd0-5abb88ba7024
linux /boot/vmlinuz-3.0.0-26-generic-pae root=/dev/sda7 ro quiet splash vt.handoff=7
}
menuentry 'Ubuntu, with Linux 3.0.0-26-generic-pae (recovery mode)' --class ubuntu --class gnu-linux --class gnu --class os {
recordfail
insmod gzio
insmod part_msdos
insmod ext2
set root='(hd0,msdos7)'
search --no-floppy --fs-uuid --set=root a70b0f4f-488b-439e-9cd0-5abb88ba7024
echo 'Loading Linux 3.0.0-26-generic-pae ...'
linux /boot/vmlinuz-3.0.0-26-generic-pae root=/dev/sda7 ro recovery nomodeset
}
submenu "Previous Linux versions" {
menuentry 'Ubuntu, with Linux 2.6.38-16-generic-pae' --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,msdos7)'
search --no-floppy --fs-uuid --set=root a70b0f4f-488b-439e-9cd0-5abb88ba7024
linux /boot/vmlinuz-2.6.38-16-generic-pae root=UUID=a70b0f4f-488b-439e-9cd0-5abb88ba7024 ro quiet splash vt.handoff=7
initrd /boot/initrd.img-2.6.38-16-generic-pae
}
menuentry 'Ubuntu, with Linux 2.6.38-16-generic-pae (recovery mode)' --class ubuntu --class gnu-linux --class gnu --class os {
recordfail
insmod gzio
insmod part_msdos
insmod ext2
set root='(hd0,msdos7)'
search --no-floppy --fs-uuid --set=root a70b0f4f-488b-439e-9cd0-5abb88ba7024
echo 'Loading Linux 2.6.38-16-generic-pae ...'
linux /boot/vmlinuz-2.6.38-16-generic-pae root=UUID=a70b0f4f-488b-439e-9cd0-5abb88ba7024 ro recovery nomodeset
echo 'Loading initial ramdisk ...'
initrd /boot/initrd.img-2.6.38-16-generic-pae
}
}
### 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,msdos7)'
search --no-floppy --fs-uuid --set=root a70b0f4f-488b-439e-9cd0-5abb88ba7024
linux16 /boot/memtest86+.bin
}
menuentry "Memory test (memtest86+, serial console 115200)" {
insmod part_msdos
insmod ext2
set root='(hd0,msdos7)'
search --no-floppy --fs-uuid --set=root a70b0f4f-488b-439e-9cd0-5abb88ba7024
linux16 /boot/memtest86+.bin console=ttyS0,115200n8
}
### END /etc/grub.d/20_memtest86+ ###
### BEGIN /etc/grub.d/30_os-prober ###
menuentry "Ubuntu, with Linux 3.2.0-31-generic-pae (on /dev/sda2)" --class gnu-linux --class gnu --class os {
insmod part_msdos
insmod ext2
set root='(hd0,msdos2)'
search --no-floppy --fs-uuid --set=root f71d3572-440d-4c3c-98b0-be3d3227d55a
linux /boot/vmlinuz-3.2.0-31-generic-pae root=UUID=f71d3572-440d-4c3c-98b0-be3d3227d55a ro quiet splash $vt_handoff
initrd /boot/initrd.img-3.2.0-31-generic-pae
}
menuentry "Ubuntu, with Linux 3.2.0-31-generic-pae (recovery mode) (on /dev/sda2)" --class gnu-linux --class gnu --class os {
insmod part_msdos
insmod ext2
set root='(hd0,msdos2)'
search --no-floppy --fs-uuid --set=root f71d3572-440d-4c3c-98b0-be3d3227d55a
linux /boot/vmlinuz-3.2.0-31-generic-pae root=UUID=f71d3572-440d-4c3c-98b0-be3d3227d55a ro recovery nomodeset
initrd /boot/initrd.img-3.2.0-31-generic-pae
}
menuentry "Ubuntu, with Linux 3.2.0-31-generic (on /dev/sda2)" --class gnu-linux --class gnu --class os {
insmod part_msdos
insmod ext2
set root='(hd0,msdos2)'
search --no-floppy --fs-uuid --set=root f71d3572-440d-4c3c-98b0-be3d3227d55a
linux /boot/vmlinuz-3.2.0-31-generic root=UUID=f71d3572-440d-4c3c-98b0-be3d3227d55a ro quiet splash $vt_handoff
initrd /boot/initrd.img-3.2.0-31-generic
}
menuentry "Ubuntu, with Linux 3.2.0-31-generic (recovery mode) (on /dev/sda2)" --class gnu-linux --class gnu --class os {
insmod part_msdos
insmod ext2
set root='(hd0,msdos2)'
search --no-floppy --fs-uuid --set=root f71d3572-440d-4c3c-98b0-be3d3227d55a
linux /boot/vmlinuz-3.2.0-31-generic root=UUID=f71d3572-440d-4c3c-98b0-be3d3227d55a ro recovery nomodeset
initrd /boot/initrd.img-3.2.0-31-generic
}
menuentry "Ubuntu, with Linux 3.2.0-29-generic (on /dev/sda2)" --class gnu-linux --class gnu --class os {
insmod part_msdos
insmod ext2
set root='(hd0,msdos2)'
search --no-floppy --fs-uuid --set=root f71d3572-440d-4c3c-98b0-be3d3227d55a
linux /boot/vmlinuz-3.2.0-29-generic root=UUID=f71d3572-440d-4c3c-98b0-be3d3227d55a ro quiet splash $vt_handoff
initrd /boot/initrd.img-3.2.0-29-generic
}
menuentry "Ubuntu, with Linux 3.2.0-29-generic (recovery mode) (on /dev/sda2)" --class gnu-linux --class gnu --class os {
insmod part_msdos
insmod ext2
set root='(hd0,msdos2)'
search --no-floppy --fs-uuid --set=root f71d3572-440d-4c3c-98b0-be3d3227d55a
linux /boot/vmlinuz-3.2.0-29-generic root=UUID=f71d3572-440d-4c3c-98b0-be3d3227d55a ro recovery nomodeset
initrd /boot/initrd.img-3.2.0-29-generic
}
### 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 ###
--------------------------------------------------------------------------------
--------------------------------------------------------------------------------
# /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
UUID=a70b0f4f-488b-439e-9cd0-5abb88ba7024 / ext3 acl,errors=remount-ro 0 1
# swap was on /dev/sda8 during installation
UUID=8b3a6d4a-8881-48c0-aff8-f77f70e096bf none swap sw 0 0
# glibc 2.2 and above expects tmpfs to be mounted at /dev/shm for
# POSIX shared memory (shm_open, shm_unlink).
# (tmpfs is a dynamically expandable/shrinkable ramdisk, and will
# use almost no memory if not populated with files)
shm /dev/shm tmpfs nodev,nosuid,noexec 0 0
#-----------------------------------------------------------------------------------------------
# Pretty much as they were on Gentoo version of treat, 2nd IDE drive.
# Now recovered from 111020 backup.
xz: (stdin): Compressed data is corrupt
xz: (stdin): Compressed data is corrupt
xz: (stdin): Compressed data is corrupt
awk: cmd. line:36: Math support is not compiled in
awk: cmd. line:36: Math support is not compiled in
awk: cmd. line:36: Math support is not compiled in
awk: cmd. line:36: Math support is not compiled in
awk: cmd. line:36: Math support is not compiled in
awk: cmd. line:36: Math support is not compiled in
awk: cmd. line:36: Math support is not compiled in
awk: cmd. line:36: Math support is not compiled in
awk: cmd. line:36: Math support is not compiled in
awk: cmd. line:36: Math support is not compiled in
awk: cmd. line:36: Math support is not compiled in
awk: cmd. line:36: Math support is not compiled in
awk: cmd. line:36: Math support is not compiled in
awk: cmd. line:36: Math support is not compiled in
awk: cmd. line:36: Math support is not compiled in
awk: cmd. line:36: Math support is not compiled in
awk: cmd. line:36: Math support is not compiled in
awk: cmd. line:36: Math support is not compiled in
awk: cmd. line:36: Math support is not compiled in
--
xubuntu-users mailing list
xubuntu-users@lists.ubuntu.com
Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/xubuntu-users
10-07-2012, 08:24 PM
NoOp
GRUB badly broken during upgrade
On 10/07/2012 10:38 AM, Kevin O'Gorman wrote:
...
>
> Oh, and the results of the bootinfo script are attached.
This is what pastebin is for:
http://pastebin.ubuntu.com/
also see:
https://wiki.ubuntu.com/Pastebin
(removed cross post to xubuntu.user)
--
ubuntu-users mailing list
ubuntu-users@lists.ubuntu.com
Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-users
10-07-2012, 10:00 PM
Avi Greenbury
GRUB badly broken during upgrade
Kevin O'Gorman wrote:
> I've also been told that gksu(1) would help for some things, but I've
> never really understood the difference between it and sudo well enough
> to know when to use it.
su and sudo in the terminal
gksu for GTK apps
kdesu for QT/KDE apps
Generally I treat kdesu as equivalent to gksu and nothing's broken
yet.
--
Avi
--
ubuntu-users mailing list
ubuntu-users@lists.ubuntu.com
Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-users
10-08-2012, 08:22 PM
Tom H
GRUB badly broken during upgrade
On Sun, Oct 7, 2012 at 1:38 PM, Kevin O'Gorman <kogorman@gmail.com> wrote:
> On Sun, Oct 7, 2012 at 10:37 AM, Kevin O'Gorman <kogorman@gmail.com> wrote:
>> On Sat, Oct 6, 2012 at 6:35 AM, Tom H <tomh0665@gmail.com> wrote:
>>> On Fri, Oct 5, 2012 at 7:01 PM, Kevin O'Gorman <kogorman@gmail.com> wrote:
>>>>
>>>> When I had just installed Xubuntu, the grub menu would show its
>>>> 3.0.0-26 kernel at the first two lines, followed by memtest, then the
>>>> Ubuntu 2.6.x kernels with an explicit root for Ubuntu. The 3.0.0
>>>> lines would boot to Xubuntu, and the 2.6 lines to Ubuntu.
>>>
>>> Please run bootinfoscript [1] and upload the results because I (for
>>> one) don't understand your description of your setup.
>>>
>>> 1. http://sourceforge.net/projects/bootinfoscript/files/bootinfoscript/
>>
>> Nice script.
>>
>> When I ran this, the apparent state of things was that I had a working
>> Xubuntu 12.04.1 on /dev/sdb2, and an unbootable Ubuntu 11.10 on
>> /dev/sdb7.
>>
>> This brokenness of the 11.10 does not particularly trouble me, since I
>> was migrating towards Xubuntu anyway, and I can mount the older setup
>> to retrieve what I need. At the moment, I'm reluctant to try to
>> rectify it for fear of losing the bootability of the Xubuntu. I've
>> had to reinstall it once already, and I'd rather not do it again.
>
> Oh, and the results of the bootinfo script are attached.
What a mess!
The "grub.cfg" in the sdb2 "/boot" (Xubuntu 12.04) points to incorrect
"/boot" and "/" because it's pointing at a non-existent UUID
("ab460680-9e94-4898-8b46-f28d1615bf7b").
It points at the 3.2 kernel on "ab460680-9e94-4898-8b46-f28d1615bf7b"
(the non-existent one) and the 3.0 and 2.6 kernels on sdb7.
The "grub.cfg" in the sdb7 "/boot" (Ubuntu 11.10) points to "/boot"
and "/" on sdb7 but considers sdb to be sda since it calls it hd0.
It points at the the 3.0 and 2.6 kernels on sdb7 using the correct
UUID ("f71d3572-440d-4c3c-98b0-be3d3227d55a") and the 3.2 kernel on
sdb2.
"core.img" on sda and sdc is pointing at sdb7 via embedding a file
into "core.img" to set the UUID of "/boot" and the corresponding
prefix. I don't see how this could possibly have been done by the
automated installation tools. You must've created the "core.img" on
sda and sdc and embedded a file into it with "-c".
"core.img" on sdb points at "/boot/grub/" on sdb2.
You said in one of your posts that you get a "grub rescue" prompt.
What's the result of "ls" and "set" at that prompt? We should be able
to walk you through boting from that prompt.
--
ubuntu-users mailing list
ubuntu-users@lists.ubuntu.com
Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-users
10-08-2012, 08:24 PM
Tom H
GRUB badly broken during upgrade
On Sun, Oct 7, 2012 at 4:24 PM, NoOp <glgxg@sbcglobal.net> wrote:
> On 10/07/2012 10:38 AM, Kevin O'Gorman wrote:
>>
>> Oh, and the results of the bootinfo script are attached.
>
> This is what pastebin is for:
> http://pastebin.ubuntu.com/
> also see:
> https://wiki.ubuntu.com/Pastebin
The disadvantage of the pastebin sites is that the uploads are deleted
after a period of time whereas pasting the (long) ooutput inline or
attaching it preserves all the information.
--
ubuntu-users mailing list
ubuntu-users@lists.ubuntu.com
Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-users
10-08-2012, 09:38 PM
"Kevin O'Gorman"
GRUB badly broken during upgrade
I'm going to have to reply piecemeal because doing this stuff requires reboot.
First the things off the top of my head....
On Mon, Oct 8, 2012 at 1:22 PM, Tom H <tomh0665@gmail.com> wrote:
> On Sun, Oct 7, 2012 at 1:38 PM, Kevin O'Gorman <kogorman@gmail.com> wrote:
>> On Sun, Oct 7, 2012 at 10:37 AM, Kevin O'Gorman <kogorman@gmail.com> wrote:
>>> On Sat, Oct 6, 2012 at 6:35 AM, Tom H <tomh0665@gmail.com> wrote:
>>>> On Fri, Oct 5, 2012 at 7:01 PM, Kevin O'Gorman <kogorman@gmail.com> wrote:
>>>>>
>>>>> When I had just installed Xubuntu, the grub menu would show its
>>>>> 3.0.0-26 kernel at the first two lines, followed by memtest, then the
>>>>> Ubuntu 2.6.x kernels with an explicit root for Ubuntu. The 3.0.0
>>>>> lines would boot to Xubuntu, and the 2.6 lines to Ubuntu.
>>>>
>>>> Please run bootinfoscript [1] and upload the results because I (for
>>>> one) don't understand your description of your setup.
>>>>
>>>> 1. http://sourceforge.net/projects/bootinfoscript/files/bootinfoscript/
>>>
>>> Nice script.
>>>
>>> When I ran this, the apparent state of things was that I had a working
>>> Xubuntu 12.04.1 on /dev/sdb2, and an unbootable Ubuntu 11.10 on
>>> /dev/sdb7.
>>>
>>> This brokenness of the 11.10 does not particularly trouble me, since I
>>> was migrating towards Xubuntu anyway, and I can mount the older setup
>>> to retrieve what I need. At the moment, I'm reluctant to try to
>>> rectify it for fear of losing the bootability of the Xubuntu. I've
>>> had to reinstall it once already, and I'd rather not do it again.
>>
>> Oh, and the results of the bootinfo script are attached.
>
> What a mess!
>
> The "grub.cfg" in the sdb2 "/boot" (Xubuntu 12.04) points to incorrect
> "/boot" and "/" because it's pointing at a non-existent UUID
> ("ab460680-9e94-4898-8b46-f28d1615bf7b").
>
> It points at the 3.2 kernel on "ab460680-9e94-4898-8b46-f28d1615bf7b"
> (the non-existent one) and the 3.0 and 2.6 kernels on sdb7.
>
> The "grub.cfg" in the sdb7 "/boot" (Ubuntu 11.10) points to "/boot"
> and "/" on sdb7 but considers sdb to be sda since it calls it hd0.
>
> It points at the the 3.0 and 2.6 kernels on sdb7 using the correct
> UUID ("f71d3572-440d-4c3c-98b0-be3d3227d55a") and the 3.2 kernel on
> sdb2.
>
> "core.img" on sda and sdc is pointing at sdb7 via embedding a file
> into "core.img" to set the UUID of "/boot" and the corresponding
> prefix. I don't see how this could possibly have been done by the
> automated installation tools. You must've created the "core.img" on
> sda and sdc and embedded a file into it with "-c".
Not that I'm aware of. But remember some things were done in both
sdb2 and sdb7 systems, plus the supergrub boot CD. But I'm pretty
sure I never typed a "-c" because I don't have a clue how to use it
well and I know I don't.
> "core.img" on sdb points at "/boot/grub/" on sdb2.
>
> You said in one of your posts that you get a "grub rescue" prompt.
>
> What's the result of "ls" and "set" at that prompt? We should be able
> to walk you through boting from that prompt.
I'll be back for this after reboot
--
Kevin O'Gorman
programmer, n. an organism that transmutes caffeine into software.
--
ubuntu-users mailing list
ubuntu-users@lists.ubuntu.com
Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-users
10-08-2012, 10:03 PM
"Kevin O'Gorman"
GRUB badly broken during upgrade
This is after the reboot....
On Mon, Oct 8, 2012 at 1:22 PM, Tom H <tomh0665@gmail.com> wrote:
> On Sun, Oct 7, 2012 at 1:38 PM, Kevin O'Gorman <kogorman@gmail.com> wrote:
>> On Sun, Oct 7, 2012 at 10:37 AM, Kevin O'Gorman <kogorman@gmail.com> wrote:
>>> On Sat, Oct 6, 2012 at 6:35 AM, Tom H <tomh0665@gmail.com> wrote:
>>>> On Fri, Oct 5, 2012 at 7:01 PM, Kevin O'Gorman <kogorman@gmail.com> wrote:
>>>>>
>>>>> When I had just installed Xubuntu, the grub menu would show its
>>>>> 3.0.0-26 kernel at the first two lines, followed by memtest, then the
>>>>> Ubuntu 2.6.x kernels with an explicit root for Ubuntu. The 3.0.0
>>>>> lines would boot to Xubuntu, and the 2.6 lines to Ubuntu.
>>>>
>>>> Please run bootinfoscript [1] and upload the results because I (for
>>>> one) don't understand your description of your setup.
>>>>
>>>> 1. http://sourceforge.net/projects/bootinfoscript/files/bootinfoscript/
>>>
>>> Nice script.
>>>
>>> When I ran this, the apparent state of things was that I had a working
>>> Xubuntu 12.04.1 on /dev/sdb2, and an unbootable Ubuntu 11.10 on
>>> /dev/sdb7.
>>>
>>> This brokenness of the 11.10 does not particularly trouble me, since I
>>> was migrating towards Xubuntu anyway, and I can mount the older setup
>>> to retrieve what I need. At the moment, I'm reluctant to try to
>>> rectify it for fear of losing the bootability of the Xubuntu. I've
>>> had to reinstall it once already, and I'd rather not do it again.
>>
>> Oh, and the results of the bootinfo script are attached.
>
> What a mess!
>
> The "grub.cfg" in the sdb2 "/boot" (Xubuntu 12.04) points to incorrect
> "/boot" and "/" because it's pointing at a non-existent UUID
> ("ab460680-9e94-4898-8b46-f28d1615bf7b").
>
> It points at the 3.2 kernel on "ab460680-9e94-4898-8b46-f28d1615bf7b"
> (the non-existent one) and the 3.0 and 2.6 kernels on sdb7.
>
> The "grub.cfg" in the sdb7 "/boot" (Ubuntu 11.10) points to "/boot"
> and "/" on sdb7 but considers sdb to be sda since it calls it hd0.
>
> It points at the the 3.0 and 2.6 kernels on sdb7 using the correct
> UUID ("f71d3572-440d-4c3c-98b0-be3d3227d55a") and the 3.2 kernel on
> sdb2.
>
> "core.img" on sda and sdc is pointing at sdb7 via embedding a file
> into "core.img" to set the UUID of "/boot" and the corresponding
> prefix. I don't see how this could possibly have been done by the
> automated installation tools. You must've created the "core.img" on
> sda and sdc and embedded a file into it with "-c".
>
> "core.img" on sdb points at "/boot/grub/" on sdb2.
>
> You said in one of your posts that you get a "grub rescue" prompt.
>
> What's the result of "ls" and "set" at that prompt? We should be able
> to walk you through boting from that prompt.
The grub rescue prompt stopped happening when I reinstalled Xubuntu
(from scratch).
The grub menu shows 11 items. Kernels are in normal/rescue pairs
1,2) Unusable boot to a 3.0.0 kernel. the "linux" line explicitly has
root=/dev/sda7 which may explain its being dead; the drive with a
partition 7 more frequently comes up as sdb, but has been sda in the
past. 3.0.0 is an appropriate kernel for Ubuntu 11.10, which is
what's on sdb7.
3) "Previous versions" legend line
4,5) memtest. This operates normally
6,7) 3.2.0-31-pae kernel. root=UUID of the sdb2 partition. That's
what i'm running now. free(1) shows 8GB ram.
8.9) as 6&7, but it's the generic kernel which only sees 3 GB ram
10,11) as 8&9 (generic) an older kernel version.
I think 1&2 may be fixable if I can get them to use the UUID. In GRUB
1 I could do this manually. I don't know how to do it in GNU GRUB.
I'm going to ditch 8-11 as useless.
--
Kevin O'Gorman
programmer, n. an organism that transmutes caffeine into software.
--
ubuntu-users mailing list
ubuntu-users@lists.ubuntu.com
Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-users
10-08-2012, 10:21 PM
"Kevin O'Gorman"
GRUB badly broken during upgrade
On Mon, Oct 8, 2012 at 3:03 PM, Kevin O'Gorman <kogorman@gmail.com> wrote:
> This is after the reboot....
>
> On Mon, Oct 8, 2012 at 1:22 PM, Tom H <tomh0665@gmail.com> wrote:
>> On Sun, Oct 7, 2012 at 1:38 PM, Kevin O'Gorman <kogorman@gmail.com> wrote:
>>> On Sun, Oct 7, 2012 at 10:37 AM, Kevin O'Gorman <kogorman@gmail.com> wrote:
>>>> On Sat, Oct 6, 2012 at 6:35 AM, Tom H <tomh0665@gmail.com> wrote:
>>>>> On Fri, Oct 5, 2012 at 7:01 PM, Kevin O'Gorman <kogorman@gmail.com> wrote:
>>>>>>
>>>>>> When I had just installed Xubuntu, the grub menu would show its
>>>>>> 3.0.0-26 kernel at the first two lines, followed by memtest, then the
>>>>>> Ubuntu 2.6.x kernels with an explicit root for Ubuntu. The 3.0.0
>>>>>> lines would boot to Xubuntu, and the 2.6 lines to Ubuntu.
>>>>>
>>>>> Please run bootinfoscript [1] and upload the results because I (for
>>>>> one) don't understand your description of your setup.
>>>>>
>>>>> 1. http://sourceforge.net/projects/bootinfoscript/files/bootinfoscript/
>>>>
>>>> Nice script.
>>>>
>>>> When I ran this, the apparent state of things was that I had a working
>>>> Xubuntu 12.04.1 on /dev/sdb2, and an unbootable Ubuntu 11.10 on
>>>> /dev/sdb7.
>>>>
>>>> This brokenness of the 11.10 does not particularly trouble me, since I
>>>> was migrating towards Xubuntu anyway, and I can mount the older setup
>>>> to retrieve what I need. At the moment, I'm reluctant to try to
>>>> rectify it for fear of losing the bootability of the Xubuntu. I've
>>>> had to reinstall it once already, and I'd rather not do it again.
>>>
>>> Oh, and the results of the bootinfo script are attached.
>>
>> What a mess!
>>
>> The "grub.cfg" in the sdb2 "/boot" (Xubuntu 12.04) points to incorrect
>> "/boot" and "/" because it's pointing at a non-existent UUID
>> ("ab460680-9e94-4898-8b46-f28d1615bf7b").
>>
>> It points at the 3.2 kernel on "ab460680-9e94-4898-8b46-f28d1615bf7b"
>> (the non-existent one) and the 3.0 and 2.6 kernels on sdb7.
>>
>> The "grub.cfg" in the sdb7 "/boot" (Ubuntu 11.10) points to "/boot"
>> and "/" on sdb7 but considers sdb to be sda since it calls it hd0.
>>
>> It points at the the 3.0 and 2.6 kernels on sdb7 using the correct
>> UUID ("f71d3572-440d-4c3c-98b0-be3d3227d55a") and the 3.2 kernel on
>> sdb2.
>>
>> "core.img" on sda and sdc is pointing at sdb7 via embedding a file
>> into "core.img" to set the UUID of "/boot" and the corresponding
>> prefix. I don't see how this could possibly have been done by the
>> automated installation tools. You must've created the "core.img" on
>> sda and sdc and embedded a file into it with "-c".
>>
>> "core.img" on sdb points at "/boot/grub/" on sdb2.
>>
>> You said in one of your posts that you get a "grub rescue" prompt.
>>
>> What's the result of "ls" and "set" at that prompt? We should be able
>> to walk you through boting from that prompt.
>
> The grub rescue prompt stopped happening when I reinstalled Xubuntu
> (from scratch).
>
> The grub menu shows 11 items. Kernels are in normal/rescue pairs
> 1,2) Unusable boot to a 3.0.0 kernel. the "linux" line explicitly has
> root=/dev/sda7 which may explain its being dead; the drive with a
> partition 7 more frequently comes up as sdb, but has been sda in the
> past. 3.0.0 is an appropriate kernel for Ubuntu 11.10, which is
> what's on sdb7.
> 3) "Previous versions" legend line
> 4,5) memtest. This operates normally
> 6,7) 3.2.0-31-pae kernel. root=UUID of the sdb2 partition. That's
> what i'm running now. free(1) shows 8GB ram.
> 8.9) as 6&7, but it's the generic kernel which only sees 3 GB ram
> 10,11) as 8&9 (generic) an older kernel version.
>
> I think 1&2 may be fixable if I can get them to use the UUID. In GRUB
> 1 I could do this manually. I don't know how to do it in GNU GRUB.
> I'm going to ditch 8-11 as useless.
I ditched the generic kernels and rebooted. Boot was normal (of
course I had to select line 6). Lines 8-11 are still there, which
makes no sense because the kernels they refer to are gone. I have no
idea how to fix this, but it's not important.
What would be much better would be to make lines 1&2 functional.
Then it would be nice to swap the contents of 1&2 with 6&7.
--
Kevin O'Gorman
programmer, n. an organism that transmutes caffeine into software.
--
ubuntu-users mailing list
ubuntu-users@lists.ubuntu.com
Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-users
10-09-2012, 04:02 AM
NoOp
GRUB badly broken during upgrade
On 10/08/2012 01:24 PM, Tom H wrote:
> On Sun, Oct 7, 2012 at 4:24 PM, NoOp <glgxg@sbcglobal.net> wrote:
>> On 10/07/2012 10:38 AM, Kevin O'Gorman wrote:
>>>
>>> Oh, and the results of the bootinfo script are attached.
>>
>> This is what pastebin is for:
>> http://pastebin.ubuntu.com/
>> also see:
>> https://wiki.ubuntu.com/Pastebin
>
> The disadvantage of the pastebin sites is that the uploads are deleted
> after a period of time whereas pasting the (long) ooutput inline or
> attaching it preserves all the information.
>
I suppose & YMMV, but I'd say that 2-3 years is certainly long enough
for the problem to be examined and resolved. Example:
http://pastebin.ubuntu.com/528557/
[Paste from kaushal at Tue, 9 Nov 2010 07:46:05 +0000]
IMO encouraging a poster (and a moderator (Kevin) for this list to boot)
to post 739 lines (which includes a 38.4KB attachment) rather than post
to a postbin doesn't make sense & seems rude (to me).
--
ubuntu-users mailing list
ubuntu-users@lists.ubuntu.com
Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-users
10-09-2012, 04:06 AM
NoOp
GRUB badly broken during upgrade
On 10/08/2012 03:21 PM, Kevin O'Gorman wrote:
> On Mon, Oct 8, 2012 at 3:03 PM, Kevin O'Gorman <kogorman@gmail.com> wrote:
...
>> The grub menu shows 11 items. Kernels are in normal/rescue pairs
>> 1,2) Unusable boot to a 3.0.0 kernel. the "linux" line explicitly has
>> root=/dev/sda7 which may explain its being dead; the drive with a
>> partition 7 more frequently comes up as sdb, but has been sda in the
>> past. 3.0.0 is an appropriate kernel for Ubuntu 11.10, which is
>> what's on sdb7.
>> 3) "Previous versions" legend line
>> 4,5) memtest. This operates normally
>> 6,7) 3.2.0-31-pae kernel. root=UUID of the sdb2 partition. That's
>> what i'm running now. free(1) shows 8GB ram.
>> 8.9) as 6&7, but it's the generic kernel which only sees 3 GB ram
>> 10,11) as 8&9 (generic) an older kernel version.
>>
>> I think 1&2 may be fixable if I can get them to use the UUID. In GRUB
>> 1 I could do this manually. I don't know how to do it in GNU GRUB.
>> I'm going to ditch 8-11 as useless.
>
> I ditched the generic kernels and rebooted. Boot was normal (of
> course I had to select line 6). Lines 8-11 are still there, which
> makes no sense because the kernels they refer to are gone. I have no
> idea how to fix this, but it's not important.
>
> What would be much better would be to make lines 1&2 functional.
> Then it would be nice to swap the contents of 1&2 with 6&7.
>
Why don't you just reinstall grub to whichever device(s) you boot to? I
fail to understand using SuperGrub et al when this list is full of
advise on how to simply reinstall grub/grub2 from a LiveCD. Ditto for
checking UUID's.
--
ubuntu-users mailing list
ubuntu-users@lists.ubuntu.com
Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-users