On Mon, Nov 27, 2006 at 01:06:21AM +0900, Henry Nelson wrote:
> On Mon, Nov 27, 2006 at 12:31:43AM +0900, Henry Nelson wrote:
> > I _still_ don't have it right.  It's getting rather serious as the
> > new disk I'm trying to boot is the only one with a complete set of
> > data.
> > 
> > I did the following:
> > 
> > # fdisk -i wd1
> > # fdisk -0 -c /usr/mdec/mbr -u wd1
> > # fdisk -a wd1
> > 
> > # disklabel wd0 > protolabel
> > # vi protolabel
> > # disklabel -FrR wd1 protolabel
> > 
> > # newfs /dev/wd1a
> 
> Weird, the mail got cut off. Continuing from here I put the
> data on the disk, and then executed the commands:
> 
> # mount /dev/wd1a /mnt
> # cp /usr/mdec/boot /mnt
> # umount /mnt
> # installboot -o console=com0 -o speed=38400 /dev/rwd1a /usr/mdec/bootxx_ffsv1
> 
> When I try to boot on that disk after moving it to the master position
> (now wd0), nothing comes across on the serial console, and if I hook up
> the monitor to the video card, all I get is "NetBSD MBR boot    Error
> No NetBSD partition".

The 'mbr' boot code can only output to the bios console device - which is
why the error message is output there.

You haven't given the output of 'fdisk wd1' or 'disklabel wd1', but the
text 'No NetBSD partition' ought to be a clue!
The 'mbr' code has booted the active partition, but the netbsd code in that
partition has failed to find a valid netbsd partition in the MBR [1]

I suspect that you haven't set the partition type to 169 in fdisk.

	David

[1] yes, it has to re-read sector zero and search the mbr partition table
again in order to find the sector number it was read from.

-- 
David Laight: david@l8s.co.uk