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 20 May 2010 23:43 Robert Nichols wrote: > 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. > I had them put in another rescue CD and it worked. Something with the media (disk) or possibly the CDROM drive was screwy, and it kept saying it couldn't read the CD for a media source for the rescue image. I assumed it needed a different image, but it just took 5 times of retrying. In fact, I only found this problem after I tried to grab the image from the hard drive itself (just to see if it would see the partitions at that point) and only after that attempt did it allow it to see the CD itself had the image needed. Strange stuff, but that was the issue. I've told them I'll create a bootable CD for future use, so I can just use it as a live CD and not worry about anything needing a specific image (and I can include whatever common modules or options I need). But, I might check out that CD you mentioned as well, it could save some time (especially if I set something up and find out I forgot some aspect and oops... :-)
From: Robert Riches on 21 May 2010 00:38 On 2010-05-21, Ohhhh maaan <nobodyhere(a)example.com> wrote: > 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. Wouldn't that be "disc"? One trick that might save you/me/anyone is to have multiple OS installations on one machine, and a boot manager (SBM or other) to choose which will be booted. Even on my home machines with only one physical disk drive, I have two OS installation areas and ping-pong between them (odd years vs. even years). As long as the boot manager is intact, I can boot either at will. On my first Linux machine, an Alpha, I had two physical disk drives, so I set up three OS installations, one standalone on each drive and one with partitions split between the two drives. Every once in a while, having _both_ a belt and suspenders can be advantageous. -- Robert Riches spamtrap42(a)verizon.net (Yes, that is one of my email addresses.)
From: Ohhhh maaan on 21 May 2010 22:18 Robert Riches wrote: > On 2010-05-21, Ohhhh maaan <nobodyhere(a)example.com> wrote: >> 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. > > Wouldn't that be "disc"? Probably. > > One trick that might save you/me/anyone is to have multiple OS > installations on one machine, and a boot manager (SBM or other) > to choose which will be booted. Even on my home machines with > only one physical disk drive, I have two OS installation areas > and ping-pong between them (odd years vs. even years). As long > as the boot manager is intact, I can boot either at will. On my > first Linux machine, an Alpha, I had two physical disk drives, so > I set up three OS installations, one standalone on each drive and > one with partitions split between the two drives. Every once in > a while, having _both_ a belt and suspenders can be advantageous. Well, if the bootloader worked, I could have selected different kernels. Even though this was a one OS install, I'd not have had the option to boot into another OS, because it never got that far. Anyway, I was able to access the shell prompt in the end, I just had to repeat the rescue image media source check that was failing. But, I suppose this is where the term live cd comes in, in place of a rescue CD.
From: Chris F.A. Johnson on 22 May 2010 09:30 On 2010-05-21, Robert Riches wrote: > On 2010-05-21, Ohhhh maaan <nobodyhere(a)example.com> wrote: .... >> I had attempted that previously, didn't work from rescue disk. In the >> end, it was a bad image on the (CD) disk. > > Wouldn't that be "disc"? That depends on where you live. -- Chris F.A. Johnson, <http://cfajohnson.com> Author: Pro Bash Programming: Scripting the GNU/Linux Shell (2009, Apress) Shell Scripting Recipes: A Problem-Solution Approach (2005, Apress)
From: J G Miller on 22 May 2010 10:20
On Sat, 22 May 2010 13:30:12 +0000, Chris F.A. Johnson wrote: > On 2010-05-21, Robert Riches wrote: >> On 2010-05-21, Ohhhh maaan <nobodyhere(a)example.com> wrote: > ... >>> I had attempted that previously, didn't work from rescue disk. In the >>> end, it was a bad image on the (CD) disk. >> >> Wouldn't that be "disc"? > > That depends on where you live. Both appear to be interchangeable, but is seems to me, perhaps erroneously, that usage is more commonly floppy *disk* and hard *disk*, but CD compact *disc* and DVD digital versatile *disc* |