From owner-freebsd-current Sun Oct 3 12:42:52 1999 Delivered-To: freebsd-current@freebsd.org Received: from io.yi.org (24.66.174.118.bc.wave.home.com [24.66.174.118]) by hub.freebsd.org (Postfix) with ESMTP id 134FE14DE6 for ; Sun, 3 Oct 1999 12:42:49 -0700 (PDT) (envelope-from jake@checker.org) Received: from io.yi.org (localhost [127.0.0.1]) by io.yi.org (Postfix) with ESMTP id 5C2911FD7; Sun, 3 Oct 1999 12:42:54 -0700 (PDT) X-Mailer: exmh version 2.0.2 2/24/98 To: Christopher Masto Cc: current@FreeBSD.ORG Subject: Re: SOLVED (partly): Re: Can't start vinum with new kernels In-reply-to: Your message of "Sun, 03 Oct 1999 15:09:02 EDT." <19991003150902.A15336@netmonger.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 03 Oct 1999 12:42:54 -0700 From: Jake Burkholder Message-Id: <19991003194254.5C2911FD7@io.yi.org> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I found out what was causing "Can't get device list: Cannot allocate > memory".. libdevstat mismatch. > > Now I'm getting a panic, but hopefully I'll have a decent backtrace > out of it soon. I ran into to that too and thought I was screwed, but vinum read worked. I built the new kernel rebuilt modules rebuilt /sbin/vinum rebooted...Can't get device list: Cannot allocate memory...single user mode vinum read /dev/wd0 /dev/wd1 exit then promptly rebuilt the world, and everything was fine. the panic could be from old /sbin/vinum with new kernel and/or vinum.ko, I'd suggest rebuilding that too. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message