[KLUG Members] Re: Laptop reiser corruption and fixing it

[Bruce Smith]

> > I also highly recommend GRUB over LILO because you can do so much
> > more at the command line (like boot a partition not in the config)
> > and look inside a filesystem before you boot.  That's saved my a$$
> > a few times recently.
> 
> I have been meaning to learn GRUB.  Got a good reference?

I got my start with the Linux Journal article about GRUB, sometime last
year.  (I can search for the exact month if you want me to)

IBM also has a good intro, I don't remember the exact URL, but go to:  

  http://www.ibm.com/developerWorks  and search for grub.

> I've avoided GRUB because it lacks an XFS driver.  But supposedly
> someone has written one.  It doesn't really matter either way
> because I use Ext2 for /.

One of the really nice things about GRUB is you can make a self
contained GRUB boot diskette, that lets you boot any partition on a
computer with a bad MBR.  Plus you can poke around the filesystem, list
directories, "cat" files, etc. before you boot (if you forget what
partition your system is on).

Upgrade your kernel and forget to run LILO, no problem with GRUB!
You can modify the config file on the fly.  Plus a lot of other goodies.

> > Want to have some fun?  Remove the /initrd directory on a SCSI
> > system (or any system where you use an initial ram disk) when
> > you're cleaning up, and you'll get a message that the init
> > program cannot be loaded, and try passing the kernel a "init="
> > parameter (which doesn't help).  That one took me some time to
> > track down!!!
> 
> I have no issues with initrds and LILO.  I use them liberally to
> pre-load drivers, so I don't need to compile a custom kernel (a
> waste of time IMHO ;-).  I also use it to do other things -- e.g.,
> to force the SCSI assigns when I have multiple SCSI disks, when
> /etc/modules.conf isn't doing the job.

I think you missed the point.  (I didn't explain it very well)

Do this (not really) on a Redhat 7.2 SCSI system w/ stock RH kernel:

  rmdir /initrd

  # now wait a few weeks and forget you removed that directory,
  # and forget all about this conversation.

  shutdown -r 0

Guess what?  Your system will NOT BOOT!  And you have no idea why.
(because you forgot about this conversation and the error message isn't
any help - cannot load init program, or some such)

It took me a long time to figure out Redhat NOW requires a directory
named /initrd when you are using an initrd during the boot.  (this is 
a _NEW_ requirement)

It has nothing to do with GRUB or LILO or the fact that I just upgraded
to the new Redhat kernel right before the reboot.  (the old kernel no
longer booted either).  And my backup partition didn't boot either
because it was copied over after I removed /initrd.  (and that has
nothing to do with a tar vs. cpio copy either :)

--------------------------------------------
Bruce Smith                bruce@armintl.com
System Administrator / Network Administrator
Armstrong International, Inc.
Three Rivers, Michigan  49093  USA
http://www.armstrong-intl.com/
--------------------------------------------