[ale] mandrake 8.0 wackiness

[Jim Philips]

How did you run fsck? You may have a bad block somewhere on the hard drive. 
This will give you errors everytime some process tries to access that block. 
If you run fsck like so:

fsck -c -y

You will flag the bad blocks so that no process will try to access them. I had 
this problem a couple of weeks ago. It caused fsck to run every time I 
re-booted, even though I had rebooted cleanly. It also prevented me from 
installing certain rpm's. Aside from that, I had symptoms very much like 
yours. Things would seem to be running okay and then programs would start 
throwing errors and lock up. Try running fsck with the above flags. It takes 
awhile, but it solved all of my problems.

On Tuesday 23 April 2002 03:12 pm, Robert E. Karaffa, II wrote:
> Hi folks,
>     Last night I got ambitious and finally (FINALLY!) figured out how to
> configure SAMBA on my home LAN.  Now, both my Macs and my Windows boxes can
> take advantage of the Linux box for printing/file sharing.  I noticed this
> morning that the Linux box (all SCSI hardware in an old Packard Bell Legend
> Supreme 1800...sounds like a pizza...) was throwing all kinds of error
> messages on the screen.  All were disk I/O related...really screwy.  I
> usually leave the Linux box alone with no users logged in, and it just does
> its thing acting as my DSL gateway.  However, recently I gave it a SCSI CDR
> and re-installed the OS on newer SCSI drives (just after the last
> InstallFest).  All was fine until I fired up the smb/nmb daemons last
> night. I'm not sure if SAMBA is the cause of the error messages.  I was
> unable to login to the console, so I had to kill the power.  Rebooted and
> it ran fsck, which found errors and fixed them all.  I let if finish
> booting, then shut it down the correct way and did a cold restart.  All was
> well for about 10 minutes, then the error messages again.  I haven't had
> time to look yet at the logs.  Could this be simply bad hardware?  Really
> odd.
>
> -Bob K.


---
This message has been sent through the ALE general discussion list.
See http://www.ale.org/mailing-lists.shtml for more info. Problems should be
sent to listmaster at ale dot org.