From owner-freebsd-questions@FreeBSD.ORG Sun May 18 17:17:34 2003 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 179E037B404 for ; Sun, 18 May 2003 17:17:34 -0700 (PDT) Received: from twix.hotpop.com (twix.hotpop.com [204.57.55.70]) by mx1.FreeBSD.org (Postfix) with ESMTP id DBEB743F93 for ; Sun, 18 May 2003 17:17:32 -0700 (PDT) (envelope-from kitbsdlists@HotPOP.com) Received: from hotpop.com (kubrick.hotpop.com [204.57.55.16]) by twix.hotpop.com (Postfix) with SMTP id BBE491B9A98 for ; Mon, 19 May 2003 00:17:29 +0000 (UTC) Received: from fortytwo. (ip68-109-49-234.lu.dl.cox.net [68.109.49.234]) by smtp-2.hotpop.com (Postfix) with SMTP id 5CFD01800D7; Mon, 19 May 2003 00:17:27 +0000 (UTC) Date: Mon, 19 May 2003 20:16:51 -0500 From: Vulpes Velox To: freebsd-questions@freebsd.org Message-Id: <20030519201651.01120e84.kitbsdlists@HotPOP.com> In-Reply-To: References: X-Mailer: Sylpheed version 0.8.2claws (GTK+ 1.2.10; i386-portbld-freebsd4.7) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-HotPOP: ----------------------------------------------- Sent By HotPOP.com FREE Email Get your FREE POP email at www.HotPOP.com ----------------------------------------------- Subject: Re: Kernel panic -supervisor read, page not present X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 19 May 2003 00:17:34 -0000 On Sun, 18 May 2003 13:47:09 -0700 Doug Hardie wrote: > > On Sunday, May 18, 2003, at 09:34 US/Pacific, Doug Hardie wrote: > > > I have a system that is almost a year old. It started rebooting last > > week several times each day with the message "supervisor read, page > > not present". A search of the archives indicates this is most likely > > a hardware failure, but there is no indication of what might have > > failed. The only messages preceeding the panic have been a gzip that > > failed, several crons and atruns that failed. Most of the panics show > > nothing unusual preceeding them in console.log or messages. The > > machine is an archive server. Its role in life is to do an rsync > > every 5 minutes for off-site archival storage. Nothing else is > > running on it. Any ideas how to determine the failure as its still > > under warrantee for a few more weeks. > > The situation is deteriating. Now rsync is core dumping. ls works, > but ls -l does not. It also core dumps. The problem occurs when > reading /etc/spwd.db. Something must be corrupt in it. I can't find > any info on that file. Sounds like the HD may be going. What I would do is find a cable that is known to be good and test it in another machine. If the problems persist it is the harddrive, most likely.