You might try disabling DMA on your harddrive on the offending drive via
Prior to the fsck, try setting hdparm.
hdparm -X34 -d1 <offending device>
Hope this helps.
----- Original Message -----
From: "Roger Irwin" <rog at powerup.com.au>
To: <ilug at linux.ie>
Sent: Saturday, July 14, 2001 6:53 PM
Subject: [ILUG] fsck problem
> I have just upgraded my system from Slackware 7 to 8 and all went well bar
> one small problem. When I went to reboot my system it gets stuck on fsck.
> I have left it for 6 hours and it still keeps going and my Harddrive isn't
> that big. I have mannaged to get my system up by putting a # in the
> /etc/rc.d/rc.S where it loads:
>> fsck -A -a
>> I can see that fsck hasn't hang by running it when the system is booted.
> Top reports it uses 98% CPU and it seams to be working fine.
> I know that I shouldn't run my system like this but not sure what to do.
> Can anyone please help?
> Irish Linux Users' Group: ilug at linux.ie>http://www.linux.ie/mailman/listinfo/ilug for (un)subscription
> List maintainer: listmaster at linux.ie
Maintained by the ILUG website team. The aim of Linux.ie is to
support and help commercial and private users of Linux in Ireland. You can
display ILUG news in your own webpages, read backend
information to find out how. Networking services kindly provided by HEAnet, server kindly donated by
Dell. Linux is a trademark of Linus Torvalds,
used with permission. No penguins were harmed in the production or maintenance
of this highly praised website. Looking for the
Indian Linux Users' Group? Try here. If you've read all this and aren't a lawyer: you should be!