MBR in disaster/recovery

[Shaw, Marco]

> Somewhere in making the partitioning mods, I confused grub and/or the
> master boot record.  The system was in a permanent reboot loop with
> "GRUB" flashing each time it recycled.  I'm thinking that there are
> additional files that I should not have recovered and I am unsure what
> they are.
> 
> 5.  upgrade to RHEL4 WS U2 and create a new MBR.  All is well.
> 
> As the system was slated for the upgrade anyway, this was not 
> a problem,
> just the additional time that my user was without their system wasn't
> good.  What should I have done to have the new disk partitioning and
> have the system functionally recovered?

Assuming you have a standard where you create a /boot FS for all
the grub and kernel stuff, I'd stay clear from trying to restore
anything in /boot.  That means your vanilla system that you start
restoring to should already have the kernel version you want
already insalled prior to the restore.

Something more for you to consider is better organizing the workstations
so you just need to restore local application directories.  In my
opinion,
starting to restore stuff like /lib/* or /usr/*, for example might be
messy.

Marco
RHCE