Date: Sat, 4 Nov 2000 13:03:18 -0500 (EST) From: Jason W <jason@welsh.dynip.com> To: questions@freebsd.org Subject: hard disk problems? Message-ID: <Pine.BSF.4.21.0011041255380.88589-100000@welsh.dynip.com>
next in thread | raw e-mail | index | archive | help
I have a brand new (few months old) western digital EIDE hard drive in my
system. I am running
FreeBSD welsh.dynip.com 4.1-RELEASE FreeBSD 4.1-RELEASE #1: Fri Sep 8
22:19:09 EST 2000 root@welsh.dynip.com:/usr/src/sys/compile/ROLAND
i386
and all of a sudden I am getting a lot of error messages in my syslog
refering to the hard drive and I hear the hard drive "ticking" off and on
when there is much disk activity (ftp). The messages are
Nov 4 10:20:54 welsh /kernel: ata0: resetting devices .. done
Nov 4 10:20:54 welsh /kernel: swap_pager: indefinite wait
buffer: device: #ad/0x20001, blkno: 296, size: 4096
Nov 4 10:23:04 welsh /kernel: ad0: READ command timeout - resetting
Nov 4 10:23:04 welsh /kernel: ata0: resetting devices .. done
Nov 4 10:23:04 welsh /kernel: ad0: read interrupt arrived earlyad0: read
error detected (too) late
Nov 4 10:27:06 welsh /kernel: ad0: READ command timeout - resetting
Nov 4 10:27:07 welsh /kernel: ata0: resetting devices .. done
Nov 4 10:27:07 welsh /kernel: ad0: read interrupt arrived earlyad0: read
error detected (too) late
Nov 4 10:31:37 welsh /kernel: ad0: READ command timeout - resetting
Nov 4 10:31:38 welsh /kernel: ata0: resetting devices .. done
Nov 4 10:31:42 welsh /kernel: ad0: read interrupt arrived earlyad0: read
error detected (too) late
Nov 4 10:31:55 welsh /kernel: ad0: READ command timeout - resetting
Nov 4 10:32:16 welsh /kernel: ata0: resetting devices .. done
Nov 4 10:32:16 welsh /kernel: ad0: read interrupt arrived earlyad0: read
error detected (too) latead0: READ command timeout - resetting
Nov 4 10:32:16 welsh /kernel: ata0: resetting devices .. done
Nov 4 10:34:48 welsh /kernel: ad0: READ command timeout - resetting
Nov 4 10:34:53 welsh /kernel: ata0: resetting devices .. done
Nov 4 10:34:53 welsh /kernel: ad0: read interrupt arrived earlyad0: read
error detected (too) late
I have searched the archives on usenet and see that this seems to happen
to a lot of people running 4.0,4.1 freebsd. I have seen some people say
that a kernel update solved the problem, others said that you need to do
"There is a work-around if you are installing FreeBSD 4.0 stable onto an
existing system: add
/sbin/sysctl -w hw.atamodes=pio,pio,pio,pio
to the beginning (just after #!/bin/sh) of /etc/rc and also /root/.login
(for csh) and /root/profile (for sh)."
I'm not sure who to believe. I will upgrade if necessary, for what its
worth, heres the output of whatever this command is ;)
[root@welsh]# sysctl hw.atamodes
hw.atamodes: pio,---,
hardware problem or software problem?
any help apprectiated.
regards,
Jason
--
=======================================================================
| Jason Welsh jason@welsh.dynip.com | If you think there's |
| | good in everybody, you |
| http://welsh.dynip.com/ | haven't met everybody. |
=======================================================================
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-questions" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.4.21.0011041255380.88589-100000>