From owner-freebsd-stable Thu Jul 26 14:37:10 2001 Delivered-To: freebsd-stable@freebsd.org Received: from knock.econ.vt.edu (knock.econ.vt.edu [128.173.172.240]) by hub.freebsd.org (Postfix) with ESMTP id D32AF37B403 for ; Thu, 26 Jul 2001 14:37:06 -0700 (PDT) (envelope-from rdmurphy@knock.econ.vt.edu) Received: (from rdmurphy@localhost) by knock.econ.vt.edu (8.11.4/8.11.4) id f6QLb6632748; Thu, 26 Jul 2001 17:37:06 -0400 (EDT) (envelope-from rdmurphy) From: "Russell D. Murphy Jr." MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <15200.36226.224588.350729@localhost.econ.vt.edu> Date: Thu, 26 Jul 2001 17:37:06 -0400 To: Stable@FreeBSD.org Subject: "Root mount failed" in 3.5-Stable to 4.1-Release upgrade X-Mailer: VM 6.92 under 21.1 (patch 14) "Cuyahoga Valley" XEmacs Lucid Reply-To: rdmurphy@vt.edu Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG I'm upgrading an old machine from 3.5-Stable to 4.1-Release (on the way to 4.3-Stable). I've been following /usr/src/UPDATING. The buildworld, buildkernel, installkernel, modules, and mknod steps went fine (as far as I can tell). I copied /usr/src/etc/MAKEDEV to /dev and ran MAKEDEV for ad0 and ad0s2a. The only filesystems in use were wd0s2a, wd0s2h, wd0s2e wd0s2g, and wd0s2f. The first slice is a 100MB dos partition. I changed fstab to reflect ad0 rather than wd0. When I try to re-boot into single user mode with either the new kernel or the new GENERIC kernel, I get: mounting root from ufs:wd0s2a wd0: bad sector table not supported wd0s2a: bad sector table not supported Root mount failed: 22 I tried asking it to boot from ad0s2a, ad0s2, ad0, wd0s2a, wd0s2, and wd0 with the same results. If I boot kernel.old (3.5-Stable), I can boot, but can't mount anything read-write. / will fsck OK, but: mount /dev/wd0s2a / generates mount: Block device required I've tried using the fixit floppy to re-make the devices ad0, ad0s2a, wd0, and wd0s2a, but this didn't seem to help (though I may not have done it in a completely kosher fashion). I've checked the list archives, but didn't find anything helpful (probably looked for the wrong keywords. . .). Any suggestions? Thanks- Russ Murphy -- Russell D. Murphy Department of Economics Virginia Polytechnic Institute and State University Blacksburg, Virginia 24061 (540) 231-4537 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message