SOLVED: 6.1.5 after install "open netbsd: no such file or directory": after successful install, can't boot

["John Refling" <netbsdrat%gmail.com@localhost>]

OK, here is how to make the install work without spending hours zeroing
entire disk, when the disk came from FreeBSD with gpt or ???:

1.  Boot the NetBSD 6.1.5 install CD
2.  Start a shell and if using entire disk type: ?gpt destroy wd0?
3.  Reboot with the CD again (make sure that the dk0? wedges are NOT in
dmesg)
4.  Continue with normal install.

If step 3 is skipped and there are gpt wedges, then the newfs in the install
will fail with 'device busy' since the dk wedge device will have the disk
open also.

It seems that I recall also that another installation proceeded w/o any
error messages (appeared to be fine), but the boot failed.

Is there some way to make the CD boot without the dk devices taking over the
disks?  Or turn off the dk devices after boot?

The install program should really handle this automatically, and not make an
unusable system.  Besides if we are overwriting the disk, we don't need the
dk stuff running at all.

John Refling


________________________________________
From: John Refling [mailto:netbsdrat%gmail.com@localhost] 
Sent: Saturday, February 07, 2015 3:18 PM
To: 'netbsd-users%NetBSD.org@localhost'
Subject: 6.1.5 after install "open netbsd: no such file or directory": after
successful install, can't boot

Still have the same problem as here:

http://mail-index.netbsd.org/netbsd-users/2013/12/07/msg013685.html

with 6.1.5, after install from CD, on boot get:

?open netbsd: no such file or directory?

The disk had FreeBSD on it and zeroing out the first part of the disk did
not help on multiple reinstall attempts.

ONLY AFTER ZEROING ENTIRE DISK USING COMMAND FROM INSTALL CD BEFORE INSTALL
HELPED:

       dd if=/dev/zero of=/dev/rwd0d bs=10m

WHY IS THIS ????  Even when I zeroed out the first part of the disk
(presumably the partition table info) and rebooting (to remove any inkernel
memory of old partition table info) the install failed.

Had to zero ENTIRE disk.

Also, the first attempt to install NetBSD after FreeBSD resulted in newfs
failing since ?device was busy?? I wonder if dk (disk wedge controller) was
controlling part of the disk and interfering with newfs and partitioning.

The install program should be able to start with fresh info and create fresh
bootable partition and turn off drivers that interfere with that.

John Refling