From: Alecks Gates <alecks.g@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Re: GRUB2 migration
Date: Thu, 5 Jul 2012 19:26:51 -0500 [thread overview]
Message-ID: <CAKkyAYZ=J8L3mhXsQ0rnU7vuhpY5sPzgYJbHEcRvnoDzcRjz8w@mail.gmail.com> (raw)
In-Reply-To: <4FF62EE2.6050703@gmail.com>
On Thu, Jul 5, 2012 at 7:18 PM, Dale <rdalek1967@gmail.com> wrote:
> Peter Humphrey wrote:
>>
>>> I'm waiting on new/more docs myself. I want to know not only how to
>>> upgrade but how to fix if it pukes on my keyboard. Hopefully other
>>> than chroot'in in and all. I have a lot of partitions and they are
>>> on LVM right now. That chroot'in is a pain in the butt. Oh, LOTS
>>> of stuff in /usr too so it has to be mounted for you to fix grub.
>> I have what seems to be an unusual solution of that problem. Each of my
>> boxes has a small, bootable rescue system in its own partition, and of
>> course its own entry in grub.conf. Its fstab defines all the main-system
>> partitions so I only have to mount them. Chrooting is as painless as it
>> can be.
>>
>> Recently, since I've banished ~amd64 except in a few cases, I've only
>> used any of the rescue systems for backing up its main system to a USB
>> drive.
>>
>
> But if you try to boot and the grub menu doesn't come up at all, then
> what? You can't select to boot anything including the rescue system.
>
> I want to be able to fix whatever happens. Grub has been good to me so
> far but I have had a time when after the BIOS was done, I got nothing,
> nothing at all. That would be something I would want to know how to fix
> since I can't even boot to get help or search google. If it isn't
> between my ears, I'm toast. Right now, there is very little grub2
> between my ears. Sometimes there is very little at all between my
> ears. lol
>
> Dale
>
> :-) :-)
>
> --
> I am only responsible for what I said ... Not for what you understood or how you interpreted my words!
>
>
I like to keep a copy of "Super Grub[2] Disk" around:
http://www.supergrubdisk.org/
Never heard of "rescatux" until now, but that looks interesting.
next prev parent reply other threads:[~2012-07-06 0:28 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-05 16:20 [gentoo-user] GRUB2 migration James
2012-07-05 18:28 ` [gentoo-user] " Grant Edwards
2012-07-05 21:41 ` Sebastian Pipping
2012-07-05 23:20 ` Dale
2012-07-05 23:57 ` Peter Humphrey
2012-07-06 0:18 ` Dale
2012-07-06 0:26 ` Alecks Gates [this message]
2012-07-06 0:52 ` Peter Humphrey
2012-07-06 1:17 ` Dale
2012-07-06 8:19 ` Neil Bothwick
2012-07-06 9:02 ` Dale
2012-07-06 4:28 ` Terry
2012-07-06 0:37 ` walt
2012-07-06 0:51 ` Dale
2012-07-06 8:23 ` Neil Bothwick
2012-07-06 9:04 ` Dale
2012-07-06 4:32 ` Terry
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAKkyAYZ=J8L3mhXsQ0rnU7vuhpY5sPzgYJbHEcRvnoDzcRjz8w@mail.gmail.com' \
--to=alecks.g@gmail.com \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox