From owner-freebsd-current Fri Dec 13 11:22:11 2002 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5135137B401 for ; Fri, 13 Dec 2002 11:22:10 -0800 (PST) Received: from rootlabs.com (root.org [67.118.192.226]) by mx1.FreeBSD.org (Postfix) with SMTP id F157443EA9 for ; Fri, 13 Dec 2002 11:22:09 -0800 (PST) (envelope-from nate@rootlabs.com) Received: (qmail 36878 invoked by uid 1000); 13 Dec 2002 19:22:10 -0000 Date: Fri, 13 Dec 2002 11:22:10 -0800 (PST) From: Nate Lawson To: Kevin Oberman Cc: current@freebsd.org Subject: Re: Losing the battle with RC1 In-Reply-To: <20021213190352.C33BD5D04@ptavv.es.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Fri, 13 Dec 2002, Kevin Oberman wrote: > For the past few days I have been trying to get RC1 running on my old > laptop (IBM ThinkPad 600E). The installation worked pretty well, but > the system crashes frequently when acpi is running. > > I decided to get a dump to look at and added the following to my > rc.conf: > dumpdev="/dev/ad0s2b" > dumpdir="/scratch" > > ad0s2 IS my swap partition. I don't think the /scratch directory is > relevant as I never get to the savecore. ad0s2 needs to be as big as main memory or dumps may overwrite the next partition. > After I re-boot, the system boots just fine and soon I get the acpi > crash. At that point I need to enter "continue" several times at the > db> prompt before the system finally dumps. type "panic" instead. "cont" may obscure the true source of the crash. > When I try to reboot, the system starts to boot normally until it > tries to mount the root file system. IT then reports that it can't > mount the system and asks for the manual entry of the root fs. > > I tried booting the fixit disk and looking at the disk. fsck_ffs > reports that the super block is bad and that values disagree with > those in the first alternate. Continuing produces many, many errors. How does this work for you? fsck_ffs -b 32 / Also, try mounting the fs read only if you just need to read files off it. -Nate To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message