Hi,

2.0_BETA (and previous 1.6?? versions) panic when trying to fsck.

Here is the condensed log:

# uname -a
NetBSD  2.0_BETA NetBSD 2.0_BETA (VAXENTOY) #0: Fri Apr  9 22:34:03 CEST 2004  chris@langhals:/local/netbsdsrc-2.0/src/sys/arch/vax/compile/VAXENTOY vax

# fsck_ffs -b 16 /dev/sd0a
Alternate super block location: 16
** /dev/rsd0a
panic: lockmgr: no context
Stopped at      netbsd:lockmgr+0x66:    movab   lwp0, r2
db> bt

?04 ISP ERR
    PC = 80000466
 85 RESTART SYS
 84 FAIL


The SCSI driver is the si driver.

I have to admit, I don't know which m3x/m4x model it really is. How
can I find out?

regards,
chris


For reference, the complete boot log:
----------------------------------
> boot netbsd
962400+184432 [102704+80531]=0x144dd0
Copyright (c) 1996, 1997, 1998, 1999, 2000, 2001, 2002, 2003, 2004
    The NetBSD Foundation, Inc.  All rights reserved.
Copyright (c) 1982, 1986, 1989, 1991, 1993
    The Regents of the University of California.  All rights reserved.

NetBSD 2.0_BETA (VAXENTOY) #0: Fri Apr  9 22:34:03 CEST 2004
        chris@langhals:/local/netbsdsrc-2.0/src/sys/arch/vax/compile/VAXENTOY

VAXstation 3100/m{30,40}
cpu: KA41/42
cpu: Enabling primary cache, secondary cache
total memory = 16260 KB
avail memory = 14112 KB
sysctl_createv: sysctl_create(console_device) returned 17
mainbus0 (root)
vsbus0 at mainbus0
vsbus0: interrupt mask 8
le0 at vsbus0 csr 0x200e0000 vec 120 ipl 14 maskbit 5 buf 0x244000-0x253fff
le0: address 08:00:2b:0e:c4:96
le0: 32 receive buffers, 8 transmit buffers
dz0 at vsbus0 csr 0x200a0000 vec 304 ipl 14 maskbit 6
dz0: 4 lines
lkkbd0 at dz0
wskbd0 at lkkbd0 mux 1
lkms0 at dz0
wsmouse0 at lkms0 mux 0
si0 at vsbus0 csr 0x200c0080 vec 770 ipl 14 maskbit 1
si0: NCR5380, SCSI ID 6
scsibus0 at si0: 8 targets, 8 luns per target
si1 at vsbus0 csr 0x200c0180 vec 774 ipl 14 maskbit 0
si1: NCR5380, SCSI ID 6
scsibus1 at si1: 8 targets, 8 luns per target
smg0 at vsbus0 csr 0x200f0000 vec 104 ipl 14 maskbit 3
wsdisplay0 at smg0 kbdmux 1
wsmux1: connecting to wsdisplay0
wskbd0: connecting to wsdisplay0
wsdisplay0: screen 0-3 added (128x57, vt100 emulation)
scsibus0: waiting 2 seconds for devices to settle...
scsibus1: waiting 2 seconds for devices to settle...
sd0 at scsibus0 target 1 lun 0: <FUJITSU, M2684S-512, 2035> disk fixed
sd0: drive offline
sd0: async, 8-bit transfers
sd1 at scsibus0 target 2 lun 0: <IBM, DSAS-3540, S47K> disk fixed
sd1: drive offline
sd1: async, 8-bit transfers
sd2 at scsibus1 target 0 lun 0: <DEC, RX23     (C) DEC, 0054> disk removable
sd2: drive offline
sd2: async, 8-bit transfers
boot device: sd0
root on sd0a dumps on sd0b
WARNING: possible botched superblock upgrade detected
on filesystem previously mounted on /mnt
fs_bsize == fs_maxbsize (0x00002000) but FS_FLAGS_UPDATED is not set
Test your filesystem by running fsck_ffs -n -f on it.
If it reports:
``VALUES IN SUPER BLOCK DISAGREE WITH THOSE IN FIRST ALTERNATE''
you should be able to recover with fsck_ffs -b 16 -c 4
See the file src/UPDATING or
http://mail-index.NetBSD.org/current-users/2004/01/11/0022.html
for more details
Clock has lost 12518 day(s) - CHECK AND RESET THE DATE.
/etc/rc.conf is not configured.  Multiuser boot aborted.
Enter pathname of shell or RETURN for /bin/sh: 
We recommend creating a non-root account and using su(1) for root access.
No entry for terminal type "dumb";
using dumb terminal settings.
# mount -r /usr
WARNING: possible botched superblock upgrade detected
on filesystem previously mounted on /usr
fs_bsize == fs_maxbsize (0x00002000) but FS_FLAGS_UPDATED is not set
Test your filesystem by running fsck_ffs -n -f on it.
If it reports:
``VALUES IN SUPER BLOCK DISAGREE WITH THOSE IN FIRST ALTERNATE''
you should be able to recover with fsck_ffs -b 16 -c 4
See the file src/UPDATING or
http://mail-index.NetBSD.org/current-users/2004/01/11/0022.html
for more details
# uname -a
NetBSD  2.0_BETA NetBSD 2.0_BETA (VAXENTOY) #0: Fri Apr  9 22:34:03 CEST 2004  chris@langhals:/local/netbsdsrc-2.0/src/sys/arch/vax/compile/VAXENTOY vax
# fsck -b 16 /dev/sd0a
fsck: unknown option -- b
usage: fsck [-dfnpqvy] [-T fstype:fsoptions] [-t fstype] [special|node]...
# fsck_ffs -b 16 /dev/sd0a
Alternate super block location: 16
** /dev/rsd0a
panic: lockmgr: no context
Stopped at      netbsd:lockmgr+0x66:    movab   lwp0, r2
db> bt
p
?04 ISP ERR
    PC = 80000466
 85 RESTART SYS
 84 FAIL
----------------------------------