On Wed, 03 May 2000, linda hanigan wrote:
> The filesystem though had numerous problems with bad groups
> and inodes that had to be fixed. Both times the messed up file system was
> /dev/hda10 which is root. (Well atleast I shouldn't have to worry about
> my data and programs that I am working on as they are on different
> partitions)
>
There is a possibility that your system is trying to use
hard drive optimizations (hdparm) that your controller/hard
drive can't keep up with. Another (slim) possibility is
that you've got a flaky IDE controller (assuming built-in,
which would mean a flaky motherboard.) Finally (my best
guess) is that you've got a flaky hard drive.
I'd try "hdparm /dev/hda" (as root) and see what it says.
Do you know what brand/model of hard drive you're using for
hda? According to the manpage for hdparm, certain models of
Seagate hard drives will go into "sleep" mode at
inopportune times and certain Western Digital drives need a
smaller "block transfer mode" set since they have a small
drive cache. If you do (as root) hdparm -i /dev/hda it
shoudl tell you the brand and model number, as well as
serial number, etc.
John
--
To unsubscribe: mail [EMAIL PROTECTED] with "unsubscribe"
as the Subject.
