How do I drop to shell from rescue CD???
in [General Linux]
|
Prev: Working on a Mobile or Embedded Device/System? Tell VDC about your experiences for a chance to WIN!
Next: sadc system activity collector missing from slackware 13
From: Ohhhh maaan on 19 May 2010 22:28 Keith Keller wrote: > On 2010-05-19, Ohhhh maaan <nobodyhere(a)example.com> wrote: >> >> I appreciate the suggestion, but the data center only has on hand >> what they have and I didn't want to make a big deal about it with >> them, and I don't need anything beyond the very basic. I was just >> wondering if someone can use a rescue CD in the same manner you'd be >> able to use a >> Live CD. I didn't want to have to ask them to swap it out (if they >> even have it on hand) if I could have just dropped into shell from >> the rescue CD. I suppose this answers my question though, there is no >> way to do this it seems (or no one seems to know) > > People do know. As I and others have mentioned, the CentOS install CD > supports multiple virtual consoles, but you need to be able to pass > through Ctrl-Alt-Fn (or in some cases just Alt-Fn) to the console. Right, I know this, too, but it's not an option over KVM. Again, I was 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). >> ... unless there's >> something unique happening with this file system, I suppose. > > It almost certainly has nothing to do with the filesystem. Apologies, I meant on the CD rom disk. >> Regardless, I've made a mental note about the shell based rescue >> CD's, which could come in handy (I can't stand remote GUI interfaces >> over KVM anyway). > > Agreed. You can try out the various non-GUI CDs locally (preferably > on hardware that comes close to what you have at your remote data > center), pick the one you like, and send that to the DC ops people. > > --keith I probably can't wait that long, and will have to see what they have on hand, or have them burn a live CD they can just boot into. Literally, that's all I need (just to break out of that rescue mode GUI or go straight to a booted OS from CD).
From: jellybean stonerfish on 19 May 2010 23:11 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.
From: jellybean stonerfish on 19 May 2010 23:15 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.
From: Sidney Lambe on 19 May 2010 23:43 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. Go away. <plonk> Bet I already have a dozen of the aliases you hide behind in my killfile. [delete] Sid
From: Keith Keller on 19 May 2010 23:44
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. 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. FWIW, I believe the bootloader on many rescue CDs is actually ISOLINUX or SYSLINUX. So neither of the above will work here. (I don't think ISOLINUX supports a shell-like environment, but I've never tried it.) > 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. 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. --keith -- kkeller-usenet(a)wombat.san-francisco.ca.us (try just my userid to email me) AOLSFAQ=http://www.therockgarden.ca/aolsfaq.txt see X- headers for PGP signature information |