From owner-freebsd-questions Thu Mar 12 16:24:47 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA06363 for freebsd-questions-outgoing; Thu, 12 Mar 1998 16:24:47 -0800 (PST) (envelope-from owner-freebsd-questions@FreeBSD.ORG) Received: from toybox.cc.iastate.edu (toybox.cc.iastate.edu [129.186.142.95]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA06344 for ; Thu, 12 Mar 1998 16:24:34 -0800 (PST) (envelope-from graphix@toybox.cc.iastate.edu) Received: (from graphix@localhost) by toybox.cc.iastate.edu (8.8.7/8.8.7) id SAA11363 for freebsd-questions@freebsd.org; Thu, 12 Mar 1998 18:24:28 -0600 (CST) Date: Thu, 12 Mar 1998 18:24:28 -0600 (CST) From: Kent Vander Velden Message-Id: <199803130024.SAA11363@toybox.cc.iastate.edu> To: freebsd-questions@FreeBSD.ORG Subject: root filesystem and -current Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hos something changed in -current during the past two weeks that would affect how the root filesystem is mounted? The problem that I am seeing at the moment is with a new -current kernel, the root file system will fail to mount on boot. Running mount with no arguments shows that / has the device 'root_device' mounted on it and not '/dev/sd0a' as I would aspect. When I try to mount '/dev/sd0a' on / mount gives the error: "Specified device does not match mounted device.\n". I will try recompiling mount in a moment. Any other suggestions? Thanks. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message