From owner-freebsd-questions@FreeBSD.ORG Sun Apr 27 14:52:24 2003 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 06ED037B401 for ; Sun, 27 Apr 2003 14:52:24 -0700 (PDT) Received: from mx1.eskimo.com (mx1.eskimo.com [204.122.16.48]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5D4C143FAF for ; Sun, 27 Apr 2003 14:52:23 -0700 (PDT) (envelope-from ripper@eskimo.com) Received: from eskimo.com (ripper@eskimo.com [204.122.16.13]) by mx1.eskimo.com (8.9.3/8.8.8) with ESMTP id OAA00325 for ; Sun, 27 Apr 2003 14:52:21 -0700 Received: (from ripper@localhost) by eskimo.com (8.9.1a/8.9.1) id OAA16382 for freebsd-questions@freebsd.org; Sun, 27 Apr 2003 14:52:21 -0700 (PDT) Date: Sun, 27 Apr 2003 14:52:21 -0700 From: Ross Lippert To: freebsd-questions@freebsd.org Message-ID: <20030427145221.A15019@eskimo.eskimo.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5.1i WWW-Home-Page: http://www.eskimo.com/~ripper Subject: new hard drive, new problems, possibly related to 16383 cylinder spec X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 27 Apr 2003 21:52:24 -0000 Hi, We installed a new harddrive over here. The first sign something was screwy was when the FBSD (4.8) installed said "this drive has 74123 [some number about there] cylinders and that is impossible! Please specify the geometry manually" (well I didn't write the message down, so that's more of a paraphrase ofit). After reading up on the fact that larger than 8GB drives (the new one is 40GB) will report 16383x16x63 as the geometry, it seemed to me like this drive was slightly violating this spec and reporting its true cylinder count. So we manually set the geom to 16383x16x63 and proceeded merrily along. The install went off fine otherwise. The first boot went fine, and we did the usual stuff, cvsup, rebuild kernel, recover homedirs from backups and so on. Second boot gives a lot of trouble on the fsck. All the partitions come up with /dev/ad0s1[aefg]: FILESYSTEM CLEAN SKIPPING CHECKS, which I guess is odd because we had modified the filesystem quite a bit, and then the show-stopper: /dev/ad0s1d: UNEXPECTED INCONSISTENCY, RUN fsck MANUALLY. The above happens to be /var for what that's worth. So we take the shell and do a manual fsck and are told: CANNOT READ BLK 16 CONTINUE? y THE FOLLOWING DISK SECTORS COULD NOT BE READ: 16, 17, ..., 31 /dev/ad0s1d: NOT LABELLED AS A BSD FILESYSTEM (unused) What the heck just happened and how do we fix it? -r