From owner-freebsd-stable Tue Jan 8 6:41:25 2002 Delivered-To: freebsd-stable@freebsd.org Received: from mcqueen.wolfsburg.de (pns.wobline.de [212.68.68.5]) by hub.freebsd.org (Postfix) with ESMTP id 680AD37B421 for ; Tue, 8 Jan 2002 06:41:21 -0800 (PST) Received: from colt.ncptiddische.net (ppp-233.wobline.de [212.68.69.244]) by mcqueen.wolfsburg.de (8.11.3/8.11.3/tw-20010821) with ESMTP id g08Ef7M16634; Tue, 8 Jan 2002 15:41:07 +0100 Received: from tisys.org (poison.ncptiddische.net [192.168.0.5]) by colt.ncptiddische.net (8.11.6/8.11.6) with ESMTP id g08EfxX43373; Tue, 8 Jan 2002 15:42:00 +0100 (CET) (envelope-from nils@tisys.org) Received: (from nils@localhost) by tisys.org (8.11.6/8.11.6) id g08EfJ400576; Tue, 8 Jan 2002 15:41:19 +0100 (CET) (envelope-from nils) Date: Tue, 8 Jan 2002 15:40:44 +0100 From: "'Nils Holland'" To: Lawrence Farr Cc: freebsd-stable@freebsd.org Subject: Re: 4.5-PRERELEASE: VIA chases again... Message-ID: <20020108154044.A553@tisys.org> Mail-Followup-To: Lawrence Farr , freebsd-stable@freebsd.org References: <20020108125104.A172@tisys.org> <000801c1983d$dd7dca00$c80fa8c0@lfarr> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <000801c1983d$dd7dca00$c80fa8c0@lfarr>; from freebsd-net@epcdirect.co.uk on Tue, Jan 08, 2002 at 12:13:20PM -0000 X-Operating-System: FreeBSD poison.ncptiddische.net 4.5-PRERELEASE FreeBSD 4.5-PRERELEASE X-Machine-Uptime: 3:36PM up 22 mins, 2 users, load averages: 0.14, 0.17, 0.10 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Tue, Jan 08, 2002 at 12:13:20PM -0000, Lawrence Farr stood up and spoke: > > Moved the install back to another disk (I ran the IBM low level > disk > tools on the disk first, and it passed). Within an hour I had a panic. > It was a corrupt directory error, but it rebooted before I had chance to > write > down the error. I newfs'd it last night, and left it run with no > problems, > and it's buildingworld again now. So a simple newfs and restore operation solved your problem? For sure I'll try the same here now. Now that I think about it, the machine also tended to run rock-solid ever since I put it together in April 2001. The problems only started to occur when I changed the HD in December. WHile the new disk seems to be ok according to Western Digital's WDDIAG, I guess newfs'ing it and restoring the data to it surely cannot hurt... Greetings Nils -- Nils Holland Ti Systems - FreeBSD in Tiddische, Germany http://www.tisys.org * nils@tisys.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message