On Fri, Oct 5, 2012 at 6:47 PM, Kevin O'Gorman <kogorman@gmail.com> wrote:
> On Fri, Oct 5, 2012 at 4:59 PM, Avi Greenbury <lists@avi.co> wrote:
>> Kevin O'Gorman wrote:
>>> On Fri, Oct 5, 2012 at 3:28 PM, Avi Greenbury <lists@avi.co> wrote:
>>> > Kevin O'Gorman wrote:
>>> >> I had a system with a working Ubuntu 11.04 and Xubuntu 12.04.
>>> >> I went to upgrade the Ubuntu to 11.10, and all seemed well until I
>>> >> went to reboot.
>>> >> It got confusing after that. It looked like all of the right kernels
>>> >> were listed, but they all went to the same root.
>>> >
>>> > What do you mean by this? Each listing should generally be the same
>>> > root (both by grub's definition of 'root' and the kernel's).
>>>
>>> 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. I'd like to
>>> get back to that state.
>>
>> I'm still not sure I understand. Just to be clear, your system and its
>> kernels are all on the same volume? That being the case, when it
>> worked you cannot possibly have had more than one of any of the things
>> I can think of that I'd call 'roots'. That being the case, I don't
>> think it matters what we call them
>
> Let me try to clarify. I did indeed have two roots on the same
> volume, abeit not simultaneously. The GRUB menu had entries for both
> of them that would put me in the system I chose. In other words, it
> was just multibooting two alternative Linux setups. This was
> accomplished by the Xubuntu 12.04 GRUB, which I can no longer access.
>
>
>>
>>> >> I got in a rescue mode, and tried another update-grub. Again it
>>> >> seemed to work, but now grub goes directly to
>>> >> grub rescue>
>>> >> and I have no idea what to do there. So I'm writing this on another
>>> >> system, on which I'm not likely to upgrade the Ubuntu any time soon
>>> >> 8o)
>>
>>
>> Right now, on boot, your system goes straight to a grub rescue prompt?
>> (as in the prompt is 'grub rescue>')? That implies a broken grub and
>> the easiest way round that is normally to boot from a grub CD or DVD
>> and reinstall (or inspect) it from there.
>>
>> The Super Grub Disk is popular and here:
>> http://www.supergrubdisk.org/
>>
>> But I've found that there's a few sets of hardware on which that wont
>> boot but Grub 1 will. I've an ISO for that here:
>> http://avi.co/s/grub1.iso
>>
>> If you do get it to boot, could you let us know what you did? And, on
>> trying another grub-install how you invoked it and what it said.
>
> I'll try the supergrub. I don't want to get too far from what was working.
I tried supergrub with no luck
I've burned a supergrub disk, version 0.9799, the latest not-beta I could find.
Its help did not do that much for me, so I fumbled around a bit.
Because I have several partitions, I chose manual operation
- GRUB -> MBR & !LINUX! (>-2) MANUAL
- This gave me
-- selectfile /grub/stage1 /boot/grub/stage1
-- ERROR 15: File not found!
So I tried
- !LINUX!| (>=2) MANUAL
- This gave me
-- selectfile /boot/grub/menu.lst /grub/menu.lst
/boot/grub/grub.conf /grub/grub.conf
-- ERROR 15: File not found!
So I tried
- (ROOT) !LINUX! (>=2) MANUAL
- This gave me choices
-- It identified the systems on the two root partitions
correctly. The Xubuntu partition (hd0,1) failed, so I tried Ubuntu
(hd0,6), which also failed, but here I'll give details (the two failed
in very similar ways):
-- It showed me the vmlinux files, I chose the most recent
-- It showed me the initrd files, and I chose the matching one
-- It started booting
-- It gave up waiting for the root device and gave me some
possible causes (I'm not sure how to check on rootdelay= and root=)
-- It complained about a disk being unavailable and gave me the
UUID it was looking for
-- Then it could not load the /lib/modules file it wanted
-- and dropped me in busybox, which seems to be a simple shell
running in a ramdisk. It has no /dev/sd* entries, so it seems pretty
useless.
I booted an Xubuntu 12.04.1 live disk
- with blkid, I verified that the UUID it failed to find is (hd0,6)
aka /dev/sdb7) There are 3 drives in the system, but only one has a
partition 7, so there was no confusion
- "grub-install /dev/sda" fails, complaining it "cannot find a device
for /boot/grub (is /dev/ mounted?)"
- mounting /dev/sdb7 and chrooting to it does not fix this problem
I'm out of ideas at the moment....
++ kevin
--
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-06-2012, 06:30 AM
"Kevin O'Gorman"
GRUB badly broken during upgrade
On Fri, Oct 5, 2012 at 8:01 PM, Kevin O'Gorman <kogorman@gmail.com> wrote:
> On Fri, Oct 5, 2012 at 6:47 PM, Kevin O'Gorman <kogorman@gmail.com> wrote:
>> On Fri, Oct 5, 2012 at 4:59 PM, Avi Greenbury <lists@avi.co> wrote:
>>> Kevin O'Gorman wrote:
>>>> On Fri, Oct 5, 2012 at 3:28 PM, Avi Greenbury <lists@avi.co> wrote:
>>>> > Kevin O'Gorman wrote:
>>>> >> I had a system with a working Ubuntu 11.04 and Xubuntu 12.04.
>>>> >> I went to upgrade the Ubuntu to 11.10, and all seemed well until I
>>>> >> went to reboot.
>>>> >> It got confusing after that. It looked like all of the right kernels
>>>> >> were listed, but they all went to the same root.
>>>> >
>>>> > What do you mean by this? Each listing should generally be the same
>>>> > root (both by grub's definition of 'root' and the kernel's).
>>>>
>>>> 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. I'd like to
>>>> get back to that state.
>>>
>>> I'm still not sure I understand. Just to be clear, your system and its
>>> kernels are all on the same volume? That being the case, when it
>>> worked you cannot possibly have had more than one of any of the things
>>> I can think of that I'd call 'roots'. That being the case, I don't
>>> think it matters what we call them
>>
>> Let me try to clarify. I did indeed have two roots on the same
>> volume, abeit not simultaneously. The GRUB menu had entries for both
>> of them that would put me in the system I chose. In other words, it
>> was just multibooting two alternative Linux setups. This was
>> accomplished by the Xubuntu 12.04 GRUB, which I can no longer access.
>>
>>
>>>
>>>> >> I got in a rescue mode, and tried another update-grub. Again it
>>>> >> seemed to work, but now grub goes directly to
>>>> >> grub rescue>
>>>> >> and I have no idea what to do there. So I'm writing this on another
>>>> >> system, on which I'm not likely to upgrade the Ubuntu any time soon
>>>> >> 8o)
>>>
>>>
>>> Right now, on boot, your system goes straight to a grub rescue prompt?
>>> (as in the prompt is 'grub rescue>')? That implies a broken grub and
>>> the easiest way round that is normally to boot from a grub CD or DVD
>>> and reinstall (or inspect) it from there.
>>>
>>> The Super Grub Disk is popular and here:
>>> http://www.supergrubdisk.org/
>>>
>>> But I've found that there's a few sets of hardware on which that wont
>>> boot but Grub 1 will. I've an ISO for that here:
>>> http://avi.co/s/grub1.iso
>>>
>>> If you do get it to boot, could you let us know what you did? And, on
>>> trying another grub-install how you invoked it and what it said.
>>
>> I'll try the supergrub. I don't want to get too far from what was working.
>
> I tried supergrub with no luck
>
> I've burned a supergrub disk, version 0.9799, the latest not-beta I could find.
> Its help did not do that much for me, so I fumbled around a bit.
> Because I have several partitions, I chose manual operation
> - GRUB -> MBR & !LINUX! (>-2) MANUAL
> - This gave me
> -- selectfile /grub/stage1 /boot/grub/stage1
> -- ERROR 15: File not found!
>
> So I tried
> - !LINUX!| (>=2) MANUAL
> - This gave me
> -- selectfile /boot/grub/menu.lst /grub/menu.lst
> /boot/grub/grub.conf /grub/grub.conf
> -- ERROR 15: File not found!
>
> So I tried
> - (ROOT) !LINUX! (>=2) MANUAL
> - This gave me choices
> -- It identified the systems on the two root partitions
> correctly. The Xubuntu partition (hd0,1) failed, so I tried Ubuntu
> (hd0,6), which also failed, but here I'll give details (the two failed
> in very similar ways):
> -- It showed me the vmlinux files, I chose the most recent
> -- It showed me the initrd files, and I chose the matching one
> -- It started booting
> -- It gave up waiting for the root device and gave me some
> possible causes (I'm not sure how to check on rootdelay= and root=)
> -- It complained about a disk being unavailable and gave me the
> UUID it was looking for
> -- Then it could not load the /lib/modules file it wanted
> -- and dropped me in busybox, which seems to be a simple shell
> running in a ramdisk. It has no /dev/sd* entries, so it seems pretty
> useless.
>
> I booted an Xubuntu 12.04.1 live disk
> - with blkid, I verified that the UUID it failed to find is (hd0,6)
> aka /dev/sdb7) There are 3 drives in the system, but only one has a
> partition 7, so there was no confusion
> - "grub-install /dev/sda" fails, complaining it "cannot find a device
> for /boot/grub (is /dev/ mounted?)"
> - mounting /dev/sdb7 and chrooting to it does not fix this problem
>
> I'm out of ideas at the moment....
>
> ++ kevin
Well, not completely. The Xubuntu install is really fresh, and I
could back up the few things I configured, so I've re-installed. It
runs and my web site is back up. My mind is at ease enough to let it
be while I'm out of town much of tomorrow.
I think I know what caused the problem:
Ubuntu 10.10 and Xubuntu 12.04 have somewhat different grubs. It
shows in the way hard disks are named, for instance.
After installing 12.04 all was well.
But then I upgraded Ubutnu 10.04 to 10.10 and allowed its grub to fool
with things because its kernel was upgraded. One thing led to another
and the two grubs destroyed each others' work.
If anybody knows what I did wrong with the supergrub attempt, I'd like
to make a note of it.
--
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-06-2012, 01:35 PM
Tom H
GRUB badly broken during upgrade
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.
--
ubuntu-users mailing list
ubuntu-users@lists.ubuntu.com
Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-users
10-06-2012, 02:17 PM
Tom H
GRUB badly broken during upgrade
On Fri, Oct 5, 2012 at 7:20 PM, Kevin O'Gorman <kogorman@gmail.com> wrote:
> On Fri, Oct 5, 2012 at 4:08 PM, Tom H <tomh0665@gmail.com> wrote:
>> On Fri, Oct 5, 2012 at 6:53 PM, Kevin O'Gorman <kogorman@gmail.com> wrote:
>>>
>>> Update: I researched GRUB a little. I can now get the grub rescue to
>>> restore its 'normal' module, and boot a rescue kernel, which I can get
>>> into a root console session of the just-upgraded Ubuntu.
>>> NOTE: here's where I'm really glad I give root a password. The kernel
>>> requires a root password for this to work.
>>
>> Please don't pollute the list with nonsense regarding single user mode
>> and enabling root in Ubuntu (for the second time).
>>
>> You're being prompted for root's password because you've enabled root.
>> If root's password's locked, you get a root prompt directly.
>
> If that's true, it's new and news to me. I clearly remember being in
> the hell of having this capability unavailable because root had no
> password. It was quite a while ago, but established this mind-set
> pretty firmly. Once I get this running again -- and I'm sure a normal
> boot will work -- I'll experiment with it and maybe change my ways.
>
> I also have to say I don't understand your use of the phrase "root's
> password's locked" -- I'm not aware of locking or unlocking it, just
> of setting a password where there did not appear to be one before.
Single-user logon may or may but not have been broken at some point in
some Ubuntu release (I've never come across this problem but I might
have needed to boot in single-user mode when it was broken) but, by
design, if root's password is locked, you're dropped to a root prompt.
Ubuntu also has a "friendly-recovery" package that's installed by
default and gives you a dialog box about single-user options but I
never use it.
The (mechanical not philosophical) reason that root is "disabled" on
Ubuntu is that the password field for the "root ..." line in
"/etc/shadow" is a "!" or a "*" (I've forgotten which it is but both
work). If you "enable" root and later want to "disable" it, you have
to run "passwd {-l | --lock}" and the password field for the "root
..." line in "/etc/shadow" will be prepended with a "!".
--
ubuntu-users mailing list
ubuntu-users@lists.ubuntu.com
Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-users
10-06-2012, 02:35 PM
Tom H
GRUB badly broken during upgrade
On Fri, Oct 5, 2012 at 7:28 PM, Kevin O'Gorman <kogorman@gmail.com> wrote:
>
> I was interested enough to try it on this laptop, and find you're
> right. Rescue mode can access root without a password, and my little
> tweak actually makes it harder rather than easier. I'll never give
> root a password again, because that remembered debacle was my only
> reason for doing it.
I wasn't trying to convince to change, only pointing out that
single-user mode works correctly in a default Ubuntu root-locked
setup!
BTW, I was sent this 2005 bug [1] off-list and there may be others.
It's not quite related to a default setup since root's unlocked and
them locked again but...
--
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, 05:23 PM
"Kevin O'Gorman"
GRUB badly broken during upgrade
On Sat, Oct 6, 2012 at 7:35 AM, Tom H <tomh0665@gmail.com> wrote:
> On Fri, Oct 5, 2012 at 7:28 PM, Kevin O'Gorman <kogorman@gmail.com> wrote:
>>
>> I was interested enough to try it on this laptop, and find you're
>> right. Rescue mode can access root without a password, and my little
>> tweak actually makes it harder rather than easier. I'll never give
>> root a password again, because that remembered debacle was my only
>> reason for doing it.
>
> I wasn't trying to convince to change, only pointing out that
> single-user mode works correctly in a default Ubuntu root-locked
> setup!
>
> BTW, I was sent this 2005 bug [1] off-list and there may be others.
> It's not quite related to a default setup since root's unlocked and
> them locked again but...
>
> 1. https://bugs.launchpad.net/ubuntu/+source/sysvinit/+bug/18937
That bug is interesting, but not relevant to my experience. I
reverted to no password, not a present-but-locked root by changing the
entire password field in /etc/shadow to a single '!', as it is when
installed. I'm not sure why it's '!' instead of '*' like most of the
other system accounts, but it seems to work.
There have been times when sudo did not work well with graphical
things, but there are adequate workarounds like a linux console. That
being the case, I no longer have reason to break with the Ubuntu way
of doing things.
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.
--
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-07-2012, 05:34 PM
Colin Law
GRUB badly broken during upgrade
On 7 October 2012 18:23, Kevin O'Gorman <kogorman@gmail.com> 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.
It is usually easy to know which to use. If the command will just to
run in the terminal (eg apt-get update) then use sudo. If it will
bring up a graphical interface (gksu means graphical sudo) such as
gedit or nautilus then use gksu.
Colin
--
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, 05:37 PM
"Kevin O'Gorman"
GRUB badly broken during upgrade
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.
--
Kevin O'Gorman
programmer, n. an organism that transmutes caffeine into software.
--
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, 05:37 PM
"Kevin O'Gorman"
GRUB badly broken during upgrade
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.
--
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-07-2012, 05:38 PM
"Kevin O'Gorman"
GRUB badly broken during upgrade
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
--
ubuntu-users mailing list
ubuntu-users@lists.ubuntu.com
Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-users