From owner-freebsd-questions Thu Jan 18 13:12:46 2001 Delivered-To: freebsd-questions@freebsd.org Received: from brutus.converging.net (edtn002029.hs.telusplanet.net [161.184.135.251]) by hub.freebsd.org (Postfix) with ESMTP id 6EC3B37B401 for ; Thu, 18 Jan 2001 13:12:28 -0800 (PST) Received: (from mgd@localhost) by brutus.converging.net (8.9.3/8.9.3) id OAA05231 for freebsd-questions@freebsd.org; Thu, 18 Jan 2001 14:10:13 -0700 (MST) (envelope-from mgd) From: Murray Date: Thu, 18 Jan 2001 14:10:13 -0700 To: freebsd-questions@freebsd.org Subject: Can't open /dev/ad1s1b: Device not configured Message-ID: <20010118141012.A5113@converging.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I am attempting to take a short cut in building a FreeBSD 4.2 box. I had a stable Freebsd 4.2 box running, but the hardware was a bit of an overkill for the purpose of the box (a firewall). So, I took the hard drive out of the stable box and put it into a new build. Yes, it would not boot because the CPU setting in the kernel was different. Therefore, I booted to manual config and issued these commands: unload load.GENERIC boot The GENERIC kernel was loaded and the boot process continued. However, the following posts appeared: ad0: 515MB [1048/16/63] at ata0-master PI03 Mounting root from ufs:/dev/ad1s1a Root mount failed:6 Mounting root from ufs:wd0s1a swapon: /dev/ad1s1b: Device not configured Automatic boot in progress... Can't open /dev/ad1s1a: Device not configured /dev/ad1s1a: CAN'T CHECK FILE SYSTEM. /dev/ad1s1a: UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY. Automatic file system check failed... help! Enter full pathname of shell or RETURN for /bin/sh: If I except the default shell and run fsck, I get the following errors: Can't open /dev/ad1s1a: Device not configured Can't open /dev/ad1s1f: Device not configured Can't open /dev/ad1s1e: Device not configured I am a bit puzzled by this. I should be able to swap the drives boot with the generic kernel and then edit the kernel, recompile and then whoosh, a new box. How does one recover from such a scenario, take the short long way and start from the beginning? -- Murray Davis Converging Technology Solutions Edmonton, AB To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message