From owner-freebsd-questions Tue Jul 18 01:41:42 1995 Return-Path: questions-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id BAA16286 for questions-outgoing; Tue, 18 Jul 1995 01:41:42 -0700 Received: from genesis.atrad.adelaide.edu.au (genesis.atrad.adelaide.edu.au [129.127.96.120]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id BAA16278 for ; Tue, 18 Jul 1995 01:41:35 -0700 Received: from msmith@localhost by genesis.atrad.adelaide.edu.au (8.6.9/8.6.9) id SAA05275; Tue, 18 Jul 1995 18:25:07 +0930 From: Michael Smith Message-Id: <199507180855.SAA05275@genesis.atrad.adelaide.edu.au> Subject: Re: Fail to mount root after recompiling kernel To: ywliu@lin.wsl.sinica.edu.tw (Yen-Wei Liu) Date: Tue, 18 Jul 1995 18:25:07 +0930 (CST) Cc: msmith@atrad.adelaide.edu.au, questions@freebsd.org In-Reply-To: <199507180807.RAA05153@genesis.atrad.adelaide.edu.au> from "Yen-Wei Liu" at Jul 18, 95 03:41:38 pm Content-Type: text Content-Length: 2066 Sender: questions-owner@freebsd.org Precedence: bulk Yen-Wei Liu stands accused of saying: > I didn't give too many details because I just wanted to know if there > is anyone having similar experience before I dumped everyone with > a lot of mumurs. Anyway, here it is : ... > Machine One : at my home - A Cyrix 486DX66 with 16MB RAM, used to run > FreeBSD 2.0R before yesterday I installed 2.05R. 2 IDE drives - one 300MB ... Here is useful fact #1. > finally worked. The device name now are not wd1s1, but the old 2.0 name > wd1b or wd1c. Yup. You're still using a legacy disklabel format; this is supposedly explained in the help for the slice editor. (So I've been told; I never read it 8) > I recompiled one new kernel for the hope of being able to use Fujitsu MO, > finished it, moved it to /kernel.1, rebooting with kernel.1. This time it > was worse, FreeBSD failed to mount root sd1a. Ok. I tried to reboot with > the original kernel if this was my fault with the options I gave to the > new kernel. It still didn't find the root device, even with the original > kernel - panic, sync, rebooting. Let's guess; you're using a bootmanager, and asking it to boot what, sd(1,a)? sd(2,a)? > I just wonder why both the new and the original kernels didn't recognize > the device names any more. And these two machines used to run FreeBSD > 2.0R well. There's no problem with 'not recognising device names'; the first is an odd compatability feature (though I'm mildly surprised that the installer got it wrong; it never has for me...), the second appears to be a misconfiguration or misunderstanding on your part. We'll need to know what you're giving the bootstrap to boot from in order to answer that. > Yen-Wei Liu -- ]] Mike Smith, Software Engineer msmith@atrad.adelaide.edu.au [[ ]] Genesis Software genesis@atrad.adelaide.edu.au [[ ]] High-speed data acquisition and [[ ]] realtime instrument control (ph/fax) +61-8-267-3039 [[ ]] My car has "demand start" - Terry Lambert [[