Return to BSD News archive
#! rnews 1996 bsd
Path: euryale.cc.adfa.oz.au!newshost.anu.edu.au!harbinger.cc.monash.edu.au!simtel!col.hp.com!usenet.eel.ufl.edu!news.interlog.com!io.org!nobody
From: taob@io.org (Brian Tao)
Newsgroups: comp.unix.bsd.bsdi.misc
Subject: "Specified device does not match mounted device" error?
Date: 25 Sep 1995 05:28:52 -0400
Organization: Internex Online (io.org) Data: 416-363-4151 Voice: 416-363-8676
Lines: 30
Message-ID: <445sok$b0t@ionews.io.org>
NNTP-Posting-Host: trepan.io.org
Last week, I needed to repartition the boot drive on one of our
BSD/OS 2.0 systems to make more room in the root filesystem. I had a
spare drive, so I figured I would make the new filesystems on it and
simply copy all the files from the old drive to the new, to save on
downtime.
Both drives are Seagate Hawk 2's (ST12400N). I booted with the
old drive and mounted the new drive as /mnt. Every single file on
the old drive was then migrated over to the new using "pax -r -w".
When I removed the old drive and replaced it with the new drive and
rebooted, I got this error when it came to mount root:
/dev/sd0a on /: Specified device does not match mounted device
What is that supposed to mean? The kernel is configured to mount
root from sd0a. The old drive, with the exact same files (including
/boot and /bsd) boots and mounts root just fine. Does it have
something to do with the new drive's "a" partition being previously on
the /mnt mount point? Should that even make a difference?
From the source, mount(8) prints that error when mount(2) returns
an EINVAL. According the the mount(2) man page, EINVAL is returned
when a "pathname contains a character with the high-order bit set".
This is obviously not the case here. The boot blocks are fine and
there is nothing wrong with the filesystems (they all pass fsck if I
first boot from the old drive). What am I missing?
--
Brian Tao <taob@io.org>
System Administrator, Internex Online Inc.
"Though this be madness, yet there is method in't"