From owner-freebsd-stable Mon Sep 16 6:23: 9 2002 Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E520E37B401; Mon, 16 Sep 2002 06:23:06 -0700 (PDT) Received: from mail.thinkburst.com (juno.geocomm.com [204.214.64.110]) by mx1.FreeBSD.org (Postfix) with ESMTP id 59CE643E77; Mon, 16 Sep 2002 06:23:06 -0700 (PDT) (envelope-from jbozza@thinkburst.com) Received: from mailgate.thinkburstmedia.com (gateway.thinkburstmedia.com [204.214.64.100]) by mail.thinkburst.com (Postfix) with ESMTP id E62ECAED8; Mon, 16 Sep 2002 08:23:33 -0500 (CDT) Received: from sigma.geocomm.com (sigma.geocomm.com [10.1.1.5]) by mailgate.thinkburstmedia.com (Postfix) with ESMTP id 7DE6720F03; Mon, 16 Sep 2002 08:23:05 -0500 (CDT) Received: by sigma.geocomm.com (Postfix, from userid 805) id 6EFEA24538; Mon, 16 Sep 2002 08:23:05 -0500 (CDT) Received: from bozza (dhcp00.geocomm.com [10.1.1.100]) by sigma.geocomm.com (Postfix) with ESMTP id 042C32453F; Mon, 16 Sep 2002 08:23:05 -0500 (CDT) From: "Jaime Bozza" To: "'Greg 'groggy' Lehey'" Cc: Subject: RE: vinum/softupdates/fsck strange problem Date: Mon, 16 Sep 2002 08:20:11 -0500 Message-ID: <006701c25d83$c8feb5b0$6401010a@bozza> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook, Build 10.0.4024 Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4910.0300 In-Reply-To: <20020916003357.GO30557@wantadilla.lemis.com> X-Sanitizer: ThinkBurst Media, Inc. mail filter 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 >>> Hmm, that's a known problem with Vinum, but only after things have >>> gone wrong at some earlier point. You should take a look at >> >> Will do. Like it said though, rebooting made it show the correct >> devices for the drives and I haven't seen the problem since. > >Hmm, that does rather suggest a hardware problem, then. It should >have found the same devices every time. dmesg showed the same devices, the root filesystem showed the correct slice. It was just vinum that acted as if the 's1' wasn't there. (Using ad0h instead of ad0s1h) These are systems that have been around a while. I just recently converted the regular filesystems over to vinum (The filesystems were dump/restored). Previous to that, I had never had a problem. Granted, it still may be a hardware problem (which I'll watch out for), but having it happen on two completely different systems the exact same way makes me think something else. These *are* IDE drives and write caching was on, so there could be something there. I have turned write caching (hw.ata.wc) off this weekend. >> I'm building a new system from scratch here though, so I'll see if I >> can simulate some failures (and reboots) to see if I can get a >> similar error. > >Would this be an AMD system? Is it possible that you're having >thermal problems? P3-500's, Asus P2B-F motherboards. Fans are working fine. Come to think of it, those are the only two systems using the configuration. Jaime To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message