On Wed, May 03, 2000 at 02:37:56PM -0500, linda hanigan wrote:
> .> Do you have an available partition or free space anywhere? If so, copy
> > / there (cp -a), then reboot with 'root=/dev/hda12' or whatever, mkfs
> > on the old root, copy everything back. This makes a nice safety hatch
> > too, in case of catastrophic problems with root (been there).
> no free space but I do have a backup on zip drives
Well, if/when you get that new drive, this is a nice thing to have in
emergency situations. My current mess started with some corrupted
libs, and was unbootable. I got in with a fully functional system on
the backup root, and fixed everything good as new <g>. For a while
anyway. But had to copy stuff back in order to get it working. fsck
can only do so much, and this was apparently beyond e2fsck's ability.
I run a cron job once a week to keep it mostly current.
> > I don't think there is any really way to know of a pending drive
> > failure for certain, short of 20-20 hindsight after the fact. There
> > may be symptoms and warnings, but some of the same symptoms might be
> > caused by a bad cable, loose cable, bad ram, controller, etc. Probably
> > worth checking these things first. Also, if you are doing anything
> > with 'hdparm', you might undo that for a while and see if that is
> > contributing.
> .I'll check the cables tonight when I don't have any little hands to help
> me.
> I saw you mentioned memtest86 in a different email is that what you use to
> test ram? Do you get it on freshmeat?
There are at least 2 RAM testers on Freshmeat (including this one).
Can't say which is better.
--
Hal B
[EMAIL PROTECTED]
--
--
To unsubscribe: mail [EMAIL PROTECTED] with "unsubscribe"
as the Subject.
