From owner-freebsd-current  Tue Mar 10 20:26:47 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id UAA11696
          for freebsd-current-outgoing; Tue, 10 Mar 1998 20:26:47 -0800 (PST)
          (envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19])
          by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA11691
          for <current@FreeBSD.ORG>; Tue, 10 Mar 1998 20:26:41 -0800 (PST)
          (envelope-from bde@godzilla.zeta.org.au)
Received: (from bde@localhost)
	by godzilla.zeta.org.au (8.8.7/8.8.7) id PAA25533;
	Wed, 11 Mar 1998 15:24:23 +1100
Date: Wed, 11 Mar 1998 15:24:23 +1100
From: Bruce Evans <bde@zeta.org.au>
Message-Id: <199803110424.PAA25533@godzilla.zeta.org.au>
To: current@FreeBSD.ORG, jmz@cabri.obs-besancon.fr
Subject: Re: Panic with the new slice stuff
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

>I wanted to know if my boot disk is dedicated ot not :-)
>
>I got: 'error 6: panic: cannot mount root (2)', just after the message:
>changing root device to sd0s5a

This is normal for fully dedicated disks :-).

>What can I do?

It should be fixed in the current vfs_conf.c, except for the bogus device
name in the "changing" message.  This is not easy to fix, since it is
not known until later that slice == 5 (sd0s4, not sd0s5) passed by the
boot blocks really means slice == 0, (sd0, not sd0s-1).

Bruce

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message