From owner-freebsd-current Wed Feb 17 17:49:49 1999 Delivered-To: freebsd-current@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (Postfix) with ESMTP id D763410FAE for ; Wed, 17 Feb 1999 17:49:46 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id RAA13438; Wed, 17 Feb 1999 17:49:41 -0800 (PST) (envelope-from dillon) Date: Wed, 17 Feb 1999 17:49:41 -0800 (PST) From: Matthew Dillon Message-Id: <199902180149.RAA13438@apollo.backplane.com> To: Gianmarco Giovannelli Cc: current@FreeBSD.ORG Subject: Re: panic mount root failed References: <4.1.19990218023835.00a55430@194.184.65.4> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :Env: : :Yesterday I went to a friends house for installing a box from the freebsd :3.0-release cdrom (I have also the src and obj very current on another cd :to do a quick make installword :-). : :He has : :1 hd master (A) + 1 cdrom slave on primary ch. :1 hd master (B) + 1 zip atapi slave on secundary ch. : :on (A) there is a primary win98 partition. on (B) there is a fat partition :on wd2s1 and a freebsd installation on wd2s2a. : :The installation procedure was fine, but at the next reboot it can't mount :the root fs because it tries to mount / on wd1s2a even if in /etc/fstab :there is wd2s2a ! I think it is a problem related to the fact that the :cdrom make confusion on the routine that have to find the hd & slice number... : :everything was fine after adding a boot config with 1:wd(2,a)kernel : :Is it a known problem or I miss something ? : :Best Regards, :Gianmarco Giovannelli , "Unix expert since yesterday" :http://www.giovannelli.it/~gmarco :http://www2.masternet.it Look at the disklabel for wd2s2. If the 'disk:' field in the label says wd1 that may be your problem. -Matt Matthew Dillon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message