I too had filesystem errors until I erased the "-q -m16" part from
the hdparm line. I personally feel that anything like this that even has
the potential for causing problems for even a small percentage of users
should be made an option to enable, not disable.

If I hadn't been on this list, I probably wouldn't have known what to try
to fix the FS errors that kept poping up.

Jay Summet

On Thu, 1 Jul 1999, Gerben Welter wrote:

> At 18:37 6/30/99 -0400, you wrote:
> 
> >Greetings.  I have what seems to me to be a rather serious complaint/bug.
> >
> >I recently installed Mandrake 6.0.  Shortly thereafter I started noticing
> >hard disk problems that I couldn't explain, including filesystem corruption
> >and I/O errors.  I've had no problems with my disks before this.  I
> >eventually tracked down the problem to this code in /etc/rc.d/rc.sysinit:
> 
> I never got that far. After a fresh install of Mandrake 6.0, hdparm let my 
> system hang when booting. So I had to uncomment the hdparm part of 
> rc.sysinit. Maybe Mandrake should leave hdparm out and put it somewhere 
> else as a hd tune script.
> 
> Grtz Gerben.
> 
> 

Reply via email to