Automatic file system check failed in NetBSD dom-U

[Rainer Brinkmöller <rainer.brinkmoeller%web.de@localhost>]

Hi,

i have the following problem at an NetBSD 3 / Xen 2.0.7 environment:

I did run a 'make install' for Xorg-Server and KDE in the dom-0 and 4 
dom-U in a test environment at the same time.
After a 2 days and nights it finished and all seems fine. Then shutdown 
the dom-U's stopped xend and shutdown the
dom-0. A day later i'd start NetBSD as dom-0 again. All fine. The try to 
start the dom-U's. All did start with this output:

...
Searching for RAID components...
boot device: xbd0
root on xbd0a dumps on xbd0b
mountroot: trying smbfs...
mountroot: trying coda...
mountroot: trying msdos...
mountroot: trying cd9660...
mountroot: trying ntfs...
mountroot: trying nfs...
mountroot: trying lfs...
mountroot: trying ext2fs...
mountroot: trying ffs...
root file system type: ffs
init: copying out path '/sbin/init' 11
Fri Jan 27 16:44:33 GMT 2006
swapctl: /dev/wd0b: Device not configured
Checking for botched superblock upgrades: done.
Starting file system checks:
Can't open /dev/rwd0a: Device not configured
CAN'T CHECK FILE SYSTEM.
/dev/rwd0a: UNEXPECTED INCONSISTENCY; RUN fsck_ffs MANUALLY.
Automatic file system check failed; help!
Jan 27 16:44:33 init: /bin/sh on /etc/rc terminated abnormally, going to 
single user mode
Enter pathname of shell or RETURN for /bin/sh:

I'd setup the dom-U's in disklabel partitions. For each dom-U one 
disklabel partition.

Here the disklabel output from dom-0:

# /dev/rwd0d:
type: unknown
disk: NBSD3ST312002
label:
flags:
bytes/sector: 512
sectors/track: 63
tracks/cylinder: 16
sectors/cylinder: 1008
cylinders: 232581
total sectors: 234441648
rpm: 3600
interleave: 1
trackskew: 0
cylinderskew: 0
headswitch: 0        # microseconds
track-to-track seek: 0    # microseconds
drivedata: 0

16 partitions:
#        size    offset     fstype [fsize bsize cpg/sgs]
a:    525168        63     4.2BSD   1024  8192 43768  # (Cyl.      
0*-    521*)
b:    263088    525231       swap                     # (Cyl.    
521*-    782*)
c: 234441585        63     unused      0     0        # (Cyl.      0*- 
232580)
d: 234441648         0     unused      0     0        # (Cyl.      0 - 
232580)
e:  16778160    788319     4.2BSD   2048 16384 27680  # (Cyl.    782*-  
17427*)
f:   1049328  17566479     4.2BSD   1024  8192 43728  # (Cyl.  17427*-  
18468*)
g:    263088  18615807     4.2BSD   1024  8192 32888  # (Cyl.  18468*-  
18729*)
h:   2097648  18878895     4.2BSD   2048 16384 21872  # (Cyl.  18729*-  
20810*)
i:  41943040  20976543     4.2BSD      0     0     0  # (Cyl.  20810*-  
62420*)
j:  41943040  62919583     4.2BSD      0     0     0  # (Cyl.  62420*- 
104030*)
k:  41943040 104862623     4.2BSD      0     0     0  # (Cyl. 104030*- 
145640*)
l:  41943040 146805663     4.2BSD      0     0     0  # (Cyl. 145640*- 
187250*)


So the first dom-U is at i: the second at j: and so on to 4 dom-U's. I'd 
use whole hard disk for the
basic NetBSD installation and did use an Install-CD from this
ftp://iso3.de.netbsd.org/pub/NetBSD/iso/3.0/i386pkg-3.0.iso
image for it.
Till installing Xorg and KDE i could start and stop the dom-U's as often 
as i wish, without any problem.
Any idea what could the reason for my problem and what to do?
I am not sure if it is a god idea to run fsck_ffs in those dom-U's. If i 
really should, i am also not sure with
what parameter.
I fear the hard disk is going to say good by, but i hope i'm wrong.

Oh, one further question, is procfs integrated in the netbsd-XENU kernel 
or do i have to use this entry
in the fstab for linux compatibility?:

procfs  /proc   procfs   ro,linux    0 0

If any further information is needed, let me know.

thanks in advanced,
Rainer