Crash an reboot problems...

[Christian Baer <christian.baer%uni-dortmund.de@localhost>]

Hi people!

I'm having some problems with system crashed and while I'm looking into 
the background of those, I have to live with them. Only a crash that is 
reproducable can be traced.

The last one was pretty bad, because it pretty much screwed up one file 
system. The file system in question is completely unimportanted and 
because of this fact it was mounted async (to increase write performance).

The problem is that now NetBSD won't start up anymore. What I get is 
[1]. It is my understanding that NetBSD should normally drop down to 
single user mode, where I could run fsck manually or it I have to do a 
newfs on the partition in question. Is there any way I can get that done?

Regards,
Chris

[1] Partial output of dmesg, taken from the console while booting, since
    I never get far enough to actually type 'dmesg'
raid0: RAID Level 1
raid0: Components: /dev/sd0e /dev/sd1e
raid0: Total Sectors: 102399872 (49999 MB)
swapctl: adding /dev/sd0b as swap device at priority 0
Starting file system checks:
/dev/rsd0a: file system is clean; not checking
/dev/rsd0d: file system is clean; not checking
/dev/rsd1f: file system is clean; not checking
/dev/rsd0g: DIRECTORY CORRUPTED  I=23040  OWNER=christian MODE=40755
/dev/rsd0g: SIZE=512 MTIME=Jun 22 10:22 2008
DIR=?

/dev/rsd0g: UNEXPECTED INCONSISTENCY; RUN fsck_ffs MANUALLY.
THE FOLLOWING FILE SYSTEM HAD AN UNEXPECTED INCONSISTENCY:
        ffs: /dev/rsd0g (/usr/build)
Automatic file system check failed; help!
ERROR: ABORTING BOOT (sending SIGTERM to parent)!
Jun 22 11:10:04 inÿ
NOTE: It *really* stops there!