>Number:         21089
>Category:       kern
>Synopsis:       A current kernel panics trying to find init, when a not-so-current kernel finds it perfectly.
>Confidential:   no
>Severity:       critical
>Priority:       high
>Responsible:    kern-bug-people
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Thu Apr 10 11:07:01 PDT 2003
>Closed-Date:
>Last-Modified:
>Originator:     dive
>Release:        NetBSD 1.6P (1.6R-20030409 is unbootable)
>Organization:
>Environment:
Note: I was running 1.6Q, but my backup kernel is 1.6P since I had not yet
copied a backup of the working 1.6Q kernel before 1.6R overwrote onetbsd
System: NetBSD eros 1.6P NetBSD 1.6P (EROS) #464: Thu Mar 13 21:22:40 EST 2003 dive@eros:/sys/arch/i386/compile/EROS i386
Architecture: i386
Machine: i386
>Description:
NetBSD/i386 current (late 1.6Q was when I first noticed this) is unbootable
on this machine. It uses a promise PCI ata100 controller, and one drive on
each channel. I'm not sure what the changes were, but now it is unable to
find init on /, even though a 1.6P (and early 1.6Q) kernel could just fine.
The traceback is unhelpful, as it just points to the code that calls init.

>How-To-Repeat:
Try to boot a NetBSD/i386 1.6R machine you've just updated from 1.6Q.
>Fix:
Unknown, but I suspect it's related to the UFS2 (FFS2, whatever) changes.
all my partitions are FFS, and I've also noticed this:
eros# quotacheck -a
quotacheck: bad inode number 2 to nextinode
since the changes.
>Release-Note:
>Audit-Trail:
>Unformatted: