yes, I should have thought of that. Now that you mention it, I believe
lbc was one of the files that e2fsck had to fix. Silly me.
Ok, I can also boot off another disk and mount this one to muck with it,
but that's not really the problem. My problem is that my backups were not
that good, so I don't have these libs. I'm not sure how much trouble it
will be to get the right version.
An upgrade to 6.2 should do it right? Probably a good idea anyway.
Ok, now how about *why* this has happened. Does anyone have any ideas!
thanks Steve, you are a never ending source of help to me :)
charles
On Thu, 14 Sep 2000, Steve Borho wrote:
> On Thu, Sep 14, 2000 at 12:41:42AM -0400, Charles Galpin wrote:
> > Can bad cables cause file corruption on a disk? I'm assuming yes.
> >
> > Can this happen with no messages in the message log?
> >
> > I have a 6.1 box that has had files on the root partition get severly
> > corrupted. The first time I restored a few key files under /etc, and the
> > box was back in operation. A week later it happened again, and I'm still
> > not quite sure what got corrupted, but when booting, I get to the point
> > where init starts and
> >
> > INIT: entering runlevel 3
> > INIT: cannot execute "/etc/rc.d/rc"
> >
> > followed by a bunch of these
> > INIT: ld "1" respawning too fast: disabled for 5 minutes
> > INIT: ld "2" respawning too fast: disabled for 5 minutes
> > ...
>
> I'd make sure libc and the dynamic linker are still ok
_______________________________________________
Redhat-list mailing list
[EMAIL PROTECTED]
https://listman.redhat.com/mailman/listinfo/redhat-list
