From: Robert Nichols on
On 05/19/2010 02:30 PM, Ohhhh maaan wrote:
> Hans-Peter Diettrich wrote:
>
>> Ohhhh maaan schrieb:
>>
>>> I have a kernel panic and need to fix a typo. I don't have the
>>> install disks, and I just want to use the CD to access the shell
>>> prompt so I can run the commands need. I can't get to the grub boot
>>> loader screen.
>>
>> Can you still boot any live-CD, and apply your corrections from there?
>>
>> DoDi
>
> I may be able to, I will check. I suppose, in the meantime, that the
> rescue CD is intended for a specific purpose then and it's not
> something you can drop into shell from (at least without physical
> console access or going through some rescue mode steps)?

It might help to know where this "CentOS 5.x rescue CD" came from. I
know about "Live CD", "Installation CD", and "Installation DVD", but
it sounds as if you have something different.

My personal choice for system maintenance is SystemRescueCd from
http://www.sysresccd.org . I have it on a USB flash drive that I
generally keep close at hand.

--
Bob Nichols AT comcast.net I am "RNichols42"
From: Ohhhh maaan on
Sidney Lambe wrote:

> On comp.os.linux.misc, Ohhhh maaan <nobodyhere(a)example.com>
> wrote:
>
>> Sidney Lambe wrote:
>>
>>> On comp.os.linux.misc, Ohhhh maaan <nobodyhere(a)example.com>
>>> wrote:
>>>
>>> [delete]
>>>
>>> This is a stupid thread.
>>
>> Not really.
>>
>>> You stick the rescue cd into the slot and you reboot
>>
>> Obviously.
>>
>>> and then you mount the hdd make your repairs.
>>
>> I think the "stupid" thing here, is that you're hostile and
>> paranoid and you lack the ability to read what was said.
>> There's no "repair" to make,
>
> And the thread just gets stupider.

As soon as you entered it, I agree.

> Go away.

You're not the boss of this group.

> <plonk>

Right back at ya, kook!

> Bet I already have a dozen of the aliases you hide behind
> in my killfile.

Yes, that's what people spend their days doing.

> [delete]

That makes no sense.

> Sid

T.r.o.l.l.
From: Ohhhh maaan on
Keith Keller wrote:

> On 2010-05-20, Ohhhh maaan <nobodyhere(a)example.com> wrote:
>>
>> Yes, I'm certain that's what it's running off of, but how to get to
>> it? I.e., if I was in a boot loader (lilo), I could CTRL+X, if I was
>> in grub, I could type linux single... or any number of things.
>
> Just to be clear, ctrl-X from lilo offers a lilo shell. I believe
> grub
> has a similar capability (a?). But neither is a bash or sh shell,
> which
> is what you'd need to fix a broken grub.

Yeah.

> And if (as you mentioned
> somewhere else) this is a drive that was mirrored from another working
> drive, depending on exactly how it was mirrored it may not have grub
> on the MBR, and you'll need a linux shell to fix that.

Yeah. I figured out that the media was bad. I was able to boot into the
rescue kernel, but it wasn't able to read the rescue image. Once it
was, I was able to gain the normal shell.

....
>
>> Right, but the KVM access I have doesn't allow this. That would
>> indeed be very simple.
>
> Well, not to sound snide, but it's not the fault of the CD if your KVM
> doesn't allow this.

Of course not. But, that's why I was asking.

> But jellybean offered another potential solution,
> using init=/bin/bash or /bin/sh. I've used this to try to reset a
> root password, but it might be helpful in your situation as well.

I had attempted that, but it didn't work from the rescue disk's boot:
prompt. Turns out it was just a bad CD image.

From: Ohhhh maaan on
jellybean stonerfish wrote:

> On Wed, 19 May 2010 19:22:48 -0700, Ohhhh maaan wrote:
>
> <Rest of thread cut>
>> if there's a way to just skip all of that, bypass that junk and drop
>> into a shell prompt
>
> Add "init=/bin/sh" to the kernel options at the start of your cd boot.

Tried it, and it didn't work from the rescue CD. Turns out it was a bad
image on the disk though.
From: Ohhhh maaan on
jellybean stonerfish wrote:

> On Wed, 19 May 2010 19:28:05 -0700, Ohhhh maaan wrote:
>
>> just hopeful there was some command I could pass to the boot: prompt
>> or some combination of keys or whatever, so I could bypass all of
>> that, have it load the kernel from the rescue CD disk and drop me
>> into shell. I guess that unless I have the rescue image it needs and
>> it's able to complete those steps, that I have to have someone boot
>> from a live CD instead (if they have that option available).
>>
>
>
> pass 'init=/bin/sh' or 'init=/bin/bash' to the kernel.

I had attempted that previously, didn't work from rescue disk. In the
end, it was a bad image on the (CD) disk.