This one time, at band camp, Jörgen Tegnér said: > I tried 3 runs with one parameter each run: -c1, -I and -i. The same > crap happened, and also something odd: > > mail:/etc/init.d# file /bin/*grep > /bin/egrep: ERROR: cannot open `/bin/egrep' (Unknown error 990) > /bin/fgrep: ERROR: cannot open `/bin/fgrep' (Unknown error 990) > /bin/grep: ELF 32-bit LSB executable, Intel 80386, version 1 (SYSV), > for GNU/Linux 2.2.0, dynami > > mail:/var/log# tail -17 kern.log > Jul 26 06:52:06 email kernel: hda: lost interrupt > Jul 26 06:52:07 email last message repeated 3 times > Jul 26 06:52:07 email kernel: hda: status error: status=0x58 > { DriveReady SeekComplete DataRequest } > Jul 26 06:52:07 email kernel: > Jul 26 06:52:07 email kernel: hda: drive not ready for command > Jul 26 06:52:07 email kernel: hda: lost interrupt > Jul 26 06:52:07 email last message repeated 10 times > Jul 26 06:52:07 email kernel: hda: status error: status=0x58 > { DriveReady SeekComplete DataRequest } > Jul 26 06:52:07 email kernel: > Jul 26 06:52:07 email kernel: hda: drive not ready for command > Jul 26 06:52:07 email kernel: hda: status error: status=0x50 > { DriveReady SeekComplete } > Jul 26 06:52:07 email kernel: > Jul 26 06:52:07 email kernel: hda: no DRQ after issuing WRITE > Jul 26 06:52:07 email kernel: hda: status timeout: status=0xd0 { Busy } > Jul 26 06:52:07 email kernel: > Jul 26 06:52:07 email kernel: hda: no DRQ after issuing WRITE > Jul 26 06:52:07 email kernel: ide0: reset: success > > So running from the /etc/init.d script caused these problems, while on > the other hand nothing particular was seen when running plain hdparm > from a shell. > > One note about the machine: dual P120, whith a locally compiled SMP > kernel. I'll reboot tonigth and send you the output of sh > -x /etc/init.d/hdparm restart. > > Any other ideas?
Yes, your hard drive is dying, and you are suffering file system corruption as a result. The binaries egrep and fgrep are corrupted and throw an error when the script calls egrep. You need backups, and quick! To confirm, just run egrep 'hda: (status|drive)' /var/log/kern.log If that blows up, the problem is in egrep. I would suggest not running hdparm any more on this drive, as it's about to go. Let me know if the egrep test also fails, and I'll consider this bug as closed. If egrep itself runs, I am still leaning towards hard disk failure, but am willing to keep it open for now. Thanks, and good luck, -- ----------------------------------------------------------------- | ,''`. Stephen Gran | | : :' : [EMAIL PROTECTED] | | `. `' Debian user, admin, and developer | | `- http://www.debian.org | -----------------------------------------------------------------
signature.asc
Description: Digital signature