From owner-freebsd-current Sun Nov 28 7:56:33 1999 Delivered-To: freebsd-current@freebsd.org Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.40.131]) by hub.freebsd.org (Postfix) with ESMTP id B21C9150AE for ; Sun, 28 Nov 1999 07:56:08 -0800 (PST) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.9.3/8.9.2) with ESMTP id QAA16444; Sun, 28 Nov 1999 16:55:27 +0100 (CET) (envelope-from phk@critter.freebsd.dk) To: Brian Somers Cc: freebsd-current@FreeBSD.ORG Subject: Re: HEADS UP - don't forget to MAKEDEV In-reply-to: Your message of "Sun, 28 Nov 1999 15:41:22 GMT." <199911281541.PAA00555@hak.lan.Awfulhak.org> Date: Sun, 28 Nov 1999 16:55:27 +0100 Message-ID: <16442.943804527@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <199911281541.PAA00555@hak.lan.Awfulhak.org>, Brian Somers writes: >Hi, > >Just a quick HEADS UP.... since the final bits of the block device >removal have gone in, it's now possible to dig yourself a hole if you >forget to MAKEDEV your disk devices (with the latest version of >MAKEDEV) and end up with a corrupt disk at boot.... fsck will fail >to set the device clean. You've then got to mount -f /, MAKEDEV your >disk devices, fsck them and then reboot. I hope this is not true. I think fsck sets the device clean, but the "reload" of the root filesystem seems to fail still. If you get in this situation try this: fsck -p reboot you should now come up with no problem, if not send me email! -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." FreeBSD -- It will take a long time before progress goes too far! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message