From owner-freebsd-current Tue Nov 24 10:28:04 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA21656 for freebsd-current-outgoing; Tue, 24 Nov 1998 10:28:04 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from alpha.xerox.com (alpha.Xerox.COM [13.1.64.93]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id KAA21649 for ; Tue, 24 Nov 1998 10:28:03 -0800 (PST) (envelope-from fenner@parc.xerox.com) Received: from mango.parc.xerox.com ([13.1.102.232]) by alpha.xerox.com with SMTP id <52043(3)>; Tue, 24 Nov 1998 10:27:53 PST Received: (from fenner@localhost) by mango.parc.xerox.com (8.8.8/8.8.8) id KAA24423; Tue, 24 Nov 1998 10:27:52 -0800 (PST) (envelope-from fenner) Date: Tue, 24 Nov 1998 10:27:52 PST From: Bill Fenner Message-Id: <199811241827.KAA24423@mango.parc.xerox.com> To: current@FreeBSD.ORG, jdp@polstra.com Subject: Re: Is fsck broken for autoboot? In-Reply-To: Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I had this happen a lot when I was still using compatibility slices in fstab; your example of "/dev/rsd2a: CLEAN FLAG NOT SET ..." seems to imply that you're using the compatibility slices too. Switch to /dev/rsd2sNa (where N is the FreeBSD slice on that disk). Bill To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message