From owner-freebsd-questions Wed Jan 25 14:17:26 1995 Return-Path: questions-owner Received: (from root@localhost) by freefall.cdrom.com (8.6.9/8.6.6) id OAA04992 for questions-outgoing; Wed, 25 Jan 1995 14:17:26 -0800 Received: from time.cdrom.com (time.cdrom.com [192.216.223.46]) by freefall.cdrom.com (8.6.9/8.6.6) with ESMTP id OAA04986; Wed, 25 Jan 1995 14:17:25 -0800 Received: from localhost (localhost [127.0.0.1]) by time.cdrom.com (8.6.9/8.6.9) with SMTP id OAA01014; Wed, 25 Jan 1995 14:16:45 -0800 To: Dave Waddell cc: questions@FreeBSD.org, phk@FreeBSD.org Subject: Re: More on stand/newfs failure In-reply-to: Your message of "Wed, 25 Jan 95 15:45:10 CST." Date: Wed, 25 Jan 1995 14:16:45 -0800 Message-ID: <1013.791072205@time.cdrom.com> From: "Jordan K. Hubbard" Sender: questions-owner@FreeBSD.org Precedence: bulk > about newfs /dev/rsd1a before failing with the message: > > Exec (/stand/newfs) failed, code = 5888. > < OK > I think I know the problem. You have a large disk here, but are using a very aggressive translation scheme (4MB cylinders would be my guess). FreeBSD just plain doesn't deal with this properly, and if you flipped over to the second screen (ALT-F2) you'd probably see newfs complaining bitterly about how it wants the fragment/block sizes to be considerably larger. We didn't take this into account with the 2.0 installation and didn't give the user (shame on us) a chance to enter parameters for newfs, or at the very least pick more intelligent values. Sigh. Let me talk to Poul-Henning and see if we can't generate you a custom set of boot floppies that don't have this problem! Thanks! Jordan