l i n u x - u s e r s - g r o u p - o f - d a v i s
Next Meeting:
July 7: Social gathering
Next Installfest:
Latest News:
Jun. 14: June LUGOD meeting cancelled
Page last updated:
2001 Dec 30 16:45

The following is an archive of a post made to our 'vox mailing list' by one of its subscribers.

Report this post as spam:

(Enter your email address)
Re: [vox] repairing LILO on RH 7.1 install.
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [vox] repairing LILO on RH 7.1 install.

I'm only effective in the Slackware Boot/Root/BootCD domain.
How wimpy is the system? Is RAM a problem?  Perhaps you need a toned down 

When I get in a jam (all things being equal), I boot off the Slackware 
Install CD and type 'mount root=/dev/hda4'. (My Linux partition.)
When I get in a jam and my stupid ATA66 card is a punk and needs a 
specific kernel, I boot off Slackware Boot and Root disks and do the same 
command.  With 'mount' being the image name from hitting <tab>.

You might need to edit your /etc/fstab as well to make sure the entree 
for the root partition is correct.

(An idea (baised of course): Make a Slackware boot and root disk (or 
Tom's boot and root!), then mount your linux partition under /mnt.  Go in 
and edit /etc/lilo.conf and /etc/fstab.  Then while in /mnt do a 
'chroot . bash' and then run lilo.  Praying seems to help.  Sometimes it 
requires a quarter as well... (Too much MAME on the box I suppose.)

Good Luck!

> Yeah, I thought it would be pretty straight forward myself.
> In my (admittedly limited) experience with recovery disks, the process 
> something like this:
> 1) Put bootable CD into CD drive or floppy into fd0
> 2) Wait for LILO boot:
> 3) Type 'linux single root=/dev/hda1 initrd=' (the 'initrd=' is to 
prevent a
> ramdisk from being loaded).
> 4) Watch all the pretty boot messages.  When the login: prompt appears, 
> in as root.
> 5) Edit /etc/lilo.conf, make sure the default boot is /dev/hda1, run 
> 6) Reboot without any disks in the removable drives.
> Things that have gotten me before would be forgetting to set the hard 
> to master (not a problem here, since both drives had been master), 
> the wrong partition using root=, and forgetting about initrd= and 
having an
> initial ramdisk load...
> I guess, if this process doesn't work, I'm out of ideas...  Anyone else
> wanna give it a go?
> -- Geoffrey
> begin  John McDonnell quotation:
> > On Tue, 24 Jul 2001, Geoffrey Herteg wrote:
> > 
> > > What's the layout of your hard drive?  Can you paste the partition
> > > information into an email and post it?
> > 
> > when I boot of the 2nd HD, the partition scheme is:
> > 
> > /dev/hda1 /
> > /dev/hdc1 /mnt/old_box
> > /dev/hda5 /mnt/old_box/mp3
> > /dev/hda6 /mnt/old_box/home
> > 
> > trying to boot, I have switched cables so that it should be:
> > 
> > /dev/hda1 /
> > /dev/hda5 /mp3
> > /dev/hda6 /home
> > 
> > apologies if this isn't quite what you're looking for but the Linux 
box is
> > in another room, isolated from the world due to lack of various 
> > 
> > I've tried to make the two installs as similar as possible and was 
> > that it would be fairly straightforward.
> > 
> > johnmc.
> > -- 
> >  . http:// | johnmc.org      - +1-707-446-7229 (home) .
> >  . johnmc@ | bucketchild.net - +1-   -   -     (cell) .
> > -- 

Attachment: bin00003.bin
Description: other/unknown

Attachment: bin00004.bin
Description: other/unknown

Attachment: bin00005.bin
Description: other/unknown

LUGOD Group on LinkedIn
Sign up for LUGOD event announcements
Your email address:
LUGOD Group on Facebook
'Like' LUGOD on Facebook:

Hosting provided by:
Sunset Systems
Sunset Systems offers preconfigured Linux systems, remote system administration and custom software development.

LUGOD: Linux Users' Group of Davis
PO Box 2082, Davis, CA 95617
Contact Us

LUGOD is a 501(c)7 non-profit organization
based in Davis, California
and serving the Sacramento area.
"Linux" is a trademark of Linus Torvalds.

Sponsored in part by:
Sunset Systems
Who graciously hosts our website & mailing lists!