Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 29 Jan 1998 18:39:40 +1100 (EST)
From:      Douglas Ray <doug@connect.com.au>
To:        questions@FreeBSD.ORG
Cc:        doug@connect.com.au
Subject:   grief booting 2.2.5-R on wd0s4
Message-ID:  <199801290739.SAA01619@nara.off.connect.com.au>

next in thread | raw e-mail | index | archive | help
Problem with target handling in boot command?
   /dev/wd0s4a on /: Specified device does not match mounted device

I'm not subscribed to the list:  please reply directly.

The gory story:

2.2.5-R installed on wd0s4 (via FTP for 12h, X-DEVELOPER):
1579 cyl, 16 heads, 63 S/T
 offset	   size	    END	Name	PType	Desc	SubType	FLAGS
      0	     63	     62	-	6	unused	0
     63	  34208	  34270	wd0s1	2	fat	6
  34271	      1	  34271	wd0s2	2	fat	6
  34272	  40320	  74591	wd0s3	2	fat	6
  74592	1516032	1590623	wd0s4	3	freebsd	165	C
1590624	   1008	1591631	-	6	unused	0

wd0s4 (777Mb) has default partitioning (but I didn't
transcribe the details)
	wd0s4a	/
	wd0s4b	swap
	wd0s4e	var
	wd0s4f	usr	

The target info appears to be ignored:
	boot: 0:wd(4,a)?
and
	boot: 0:wd(0,a)?
both show that the kernel is "kernel.GENERIC"

Currently both
	boot: 0:wd(4,a)kernel.GENERIC
	boot: 0:wd(0,a)kernel.GENERIC
load kernel, complain about no kernel.GENERIC.config, go
through boot sequence up to just before the fsck's where it
changes the root device (and before swapon).   At that point

	boot: 0:wd(4,a)kernel.GENERIC
says
	changing root device to wd4a
	panic : cannot mount root
and reboots (yes, that's wd4a not wd0s4a), but
	boot: 0:wd(0,a)kernel.GENERIC
runs through swapon, the fsck's, and fails on the subsequent
rw re-mount of / with diagnostic message

   /dev/wd0s4a on /: Specified device does not match mounted device

This is some way down the debug trail.   I first saw fstab with
	/dev/wd0a	/
and I had to mount /wd0s4a on /mnt to update it (didn't have
man page, and "mount -w /dev/wd0s4a /" failed with the device
mismatch diagnostic), and a couple of fsck's later we can now
get to the rw re-mount point in the boot sequence.   There was
an initial phase, prob. red herring, where the only way I seemed
to be able to load kernel and start the device polls was with
	boot: 0:wd(0,c)kernel.GENERIC

Platform is digital's multia.

grateful for any help...
						- douglas ray
						doug@connect.com.au
						network engineer



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199801290739.SAA01619>