From owner-freebsd-questions Mon Jun 1 13:36:43 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA27593 for freebsd-questions-outgoing; Mon, 1 Jun 1998 13:36:43 -0700 (PDT) (envelope-from owner-freebsd-questions@FreeBSD.ORG) Received: from gdi.uoregon.edu (gdi.uoregon.edu [128.223.170.30]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA27501 for ; Mon, 1 Jun 1998 13:36:31 -0700 (PDT) (envelope-from dwhite@gdi.uoregon.edu) Received: from localhost (dwhite@localhost) by gdi.uoregon.edu (8.8.8/8.8.8) with SMTP id NAA16154; Mon, 1 Jun 1998 13:36:27 -0700 (PDT) (envelope-from dwhite@gdi.uoregon.edu) Date: Mon, 1 Jun 1998 13:36:27 -0700 (PDT) From: Doug White Reply-To: Doug White To: peterh@wartch.rih.org cc: freebsd-questions@FreeBSD.ORG Subject: Re: your mail In-Reply-To: <199805310821.BAA00737@wartch.rih.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, 31 May 1998 peterh@wartch.rih.org wrote: > Here is part of /var/log/messages that happened today. Look at the end for > the bad SCSI lines. A lot of the error messages aren't in the log. They > must not have been logged since the drive wasn't working. I saw them on the > console, but don't remember them. Also, when I rebooted, I had to run > fsck and there were quite a few errors. Now I'm missing a ton of files > like 'libstdc++.so.2.0'. I'm pretty well backed up so I'm not worried > about data, but is my hard drive dying or what? I'm guessing that the drive hit an error and didn't know how to deal with it. That's odd for a Seagate, they're usually very good about these things. You might try running scsi -f /dev/rsd0 -m 1 and check that AWRE and ARRE are enabled. Doug White | University of Oregon Internet: dwhite@resnet.uoregon.edu | Residence Networking Assistant http://gladstone.uoregon.edu/~dwhite | Computer Science Major To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message