*BSD News Article 92314


Return to BSD News archive

Path: euryale.cc.adfa.oz.au!newshost.carno.net.au!harbinger.cc.monash.edu.au!news.cs.su.oz.au!inferno.mpx.com.au!nsw1.news.telstra.net!news.telstra.net!news.att.net.au!news.att.net.hk!newsgate.cuhk.edu.hk!news.hk.net!howland.erols.net!cam-news-hub1.bbnplanet.com!news.bbnplanet.com!news.maxwell.syr.edu!newsfeed.direct.ca!nntp.portal.ca!van-bc!ddsw1!news.mcs.net!ddsw1!not-for-mail
From: font@MCS.COM (Font)
Newsgroups: comp.unix.bsd.freebsd.misc
Subject: Duplicated boot disk panics; cannot mount root
Date: 27 Mar 1997 19:57:50 -0600
Organization: MCSNet Services
Lines: 52
Message-ID: <5hf8iu$31n$1@Venus.mcs.net>
NNTP-Posting-Host: venus.mcs.net
Xref: euryale.cc.adfa.oz.au comp.unix.bsd.freebsd.misc:38039

My goal: duplicate a boot disk on a FreeBSD 2.1.6.1 system.

My problem: after duplicating the disk, the duplicate will not boot;
after the generic kernel devices are configured, booting stops with a
panic, with the console indicating the root could not be mounted.

    ...
    npx0 on motherboard
    npx0: INT 16 interface
    panic: cannot mount root

    syncing disks... done
    Automatic reboot in 15 seconds - press a key on the console to abort

The hardware: Dell P75t, AHA2940AU, Seagate Fast SCSI-2 boot, Imprimis
SCSI-1 duplicate.

How the duplication was attempted (1):

    - duplicate disk came from a Macintosh
    - duplicate disk formatted with scsiformat
    - disklabel and boot written with disklabel
	disklabel -r -w sd1 auto
	disklabel -B sd1
	disklabel -e sd1
	- these steps sometimes result in console errors, including a
	  lack of magic
    - newfs on /dev/rsd1[a,e,f,g]
    - swap drive ids and reboot

Since this failed, we also have How the duplication was attempted (2):

    - from MS-DOS, FDISK /MBR, and then made a FAT32 partition
    - from FreeBSD, change FAT32 partition to FreeBSD partition/slice
    - disklabel and newfs as above
    - swap drive ids and reboot to identical failure

Finally, How the duplication was attempted (3):

    - identical to process described in FAQ
    - swap drive ids and reboot to identical failure

There must be something obvious eluding me.  Please, what is it?  I'd
tear out my hair but I don't have much of it left.

I noticed in /dev I have no [r]sd1s[1234]* entries, though I have
[r]sd1* without slices.  Do I need to MAKEDEV these somehow or is this
unrelated?

No, I am not related to any Higher Source people.  :-/
-- 
font@mcs.net                              Wishes are like dishes.