On Tue, 2010-03-02 at 18:41 -0500, Paul LaMadeleine wrote: > Greetings, > During a recent reboot, my RHEL 5.3 server (2.6.18-128.1.6.el5) came > up with a corrupted root partition. I’ve got LVM installed, with > root, /var, /usr/local, /home, /opt and /opt/oradata as logical > volumes. Only the root LVM had corruption issues. > I am able to boot the server, but I seem to be missing a lot of > library files and misc files in /etc seem to be altered. > While I know a full reinstall is probably the best bet, it’s also > going to take the longest and I’m being rushed to get this server back > into service. > The server was installed as a 5.2 server and then patched to the > current level, so I don’t have boot media for the current level. > What I was thinking was doing a reinstall to the latest 5.4 release > using the existing partitions. Do you think my oracle install will > survive this? That’s the main thing I’m trying to save. > Any thoughts and/or suggestions would be greatly appreciated.
- Do you have any backups? If so, boot into rescue mode, mount only root (/) and restore files for it only. - If no backups ... If you trust /var, boot into rescue mode, mount root (/) and /var, and run: # rpm -qa --root /mnt/sysimage This will give you a list of all RPMs that were installed. At this point, if you are familiar with kickstart, create a kickstart with all those packages and attempt an install to a new set of filesystems. Some might fail as they are 3rd party. You can deal with those later. If you are not familiar, install the system, then feed the package list to yum after it is installed. Once the new system has been installed, run some "diff" comparisons between your new and old root filesystems and see what might be missing. It sounds like you've lost quite a bit from /etc, so there's likely enough that is missing that it will still require manual configuration. Backups are always essential here. -- Bryan P.S. On servers, I always separate out /usr and /tmp as well for the same reasons as /opt (and /usr/local) as well as /var. Especially /tmp and /var, which have massive, continual meta-data changes. Fedora-based distros, including Red Hat Enterprise Linux, are designed so /usr does not need to be available at boot (unlike some distros). And even in the case of /tmp not mounting because it has issues, the underlying (and 1777 default permissions) /tmp directory "fall back" works just fine as well (since nothing in /tmp should ever be persistent). -- Bryan J Smith Senior Consultant Red Hat, Inc Professional Consulting http://www.redhat.com/consulting mailto:[email protected] +1 (407) 489-7013 (Mobile) mailto:[email protected] (Blackberry/Red Hat-External) -------------------------------------------------------- You already know Red Hat as the entity dedicated to 100% no-IP-strings-attached, community software development. But do you know where CIOs rate Red Hat versus other software and services firms for their own, direct needs, year after year? http://www.redhat.com/promo/vendor/ _______________________________________________ rhelv5-list mailing list [email protected] https://www.redhat.com/mailman/listinfo/rhelv5-list
