cod3fr3ak
September 14th, 2003, 15:08
[code:1:d67e57b309]
dkcsum: wd2 had no matching BIOS disk
[/code:1:d67e57b309]

System booted up this morning saying this. Anyone know what it means?

Here is the whole dmesg:
[code:1:d67e57b309]
# dmesg
OpenBSD 3.3 (GENERIC) #44: Sat Mar 29 13:22:05 MST 2003
deraadt@i386.openbsd.org:/usr/src/sys/arch/i386/compile/GENERIC
cpu0: Intel Pentium III (Coppermine) ("GenuineIntel" 686-class) 1 GHz
cpu0: FPU,V86,DE,PSE,TSC,MSR,PAE,MCE,CX8,SYS,MTRR,PGE,MC A,CMOV,PAT,PSE36,MMX,FXSR,SIMD
real mem = 536440832 (523868K)
avail mem = 491806720 (480280K)
using 4278 buffers containing 26923008 bytes (26292K) of memory
mainbus0 (root)
bios0 at mainbus0: AT/286+(81) BIOS, date 10/13/00, BIOS32 rev. 0 @ 0xfd790
pcibios0 at bios0: rev. 2.1 @ 0xfd790/0x870
pcibios0: PCI IRQ Routing Table rev. 1.0 @ 0xfdf20/192 (10 entries)
pcibios0: PCI Interrupt Router at 000:07:0 ("Intel 82371FB PCI-ISA" rev 0x00)
pcibios0: PCI bus #1 is the last bus
bios0: ROM list: 0xc0000/0xb200 0xcb800/0x4600 0xe0000/0x4000! 0xe4000/0xc000
pci0 at mainbus0 bus 0: configuration mode 1 (no bios)
pchb0 at pci0 dev 0 function 0 "Intel 82443BX PCI-AGP" rev 0x03
ppb0 at pci0 dev 1 function 0 "Intel 82443BX AGP" rev 0x03
pci1 at ppb0 bus 1
vga1 at pci1 dev 0 function 0 "SGS Thomson Kyro-II" rev 0x07
wsdisplay0 at vga1: console (80x25, vt100 emulation)
wsdisplay0: screen 1-5 added (80x25, vt100 emulation)
pcib0 at pci0 dev 7 function 0 "Intel 82371AB PIIX4 ISA" rev 0x02
pciide0 at pci0 dev 7 function 1 "Intel 82371AB IDE" rev 0x01: DMA, channel 0 wired to compatibility, channel 1 wired to compatibility
wd0 at pciide0 channel 0 drive 0: <Maxtor 91366U4>
wd0: 16-sector PIO, LBA, 12982MB, 16383 cyl, 16 head, 63 sec, 26588016 sectors
wd0(pciide0:0:0): using PIO mode 4, Ultra-DMA mode 2
atapiscsi0 at pciide0 channel 1 drive 0
scsibus0 at atapiscsi0: 2 targets
cd0 at scsibus0 targ 0 lun 0: <BCD, E520C, 0.40> SCSI0 5/cdrom removable
cd0(pciide0:1:0): using PIO mode 4, Ultra-DMA mode 2
uhci0 at pci0 dev 7 function 2 "Intel 82371AB USB" rev 0x01: irq 9
usb0 at uhci0: USB revision 1.0
uhub0 at usb0
uhub0: vendor 0x0000 UHCI root hub, class 9/0, rev 1.00/1.00, addr 1
uhub0: 2 ports with 2 removable, self powered
"Intel 82371AB Power Mgmt" rev 0x02 at pci0 dev 7 function 3 not configured
pciide1 at pci0 dev 14 function 0 "HighPoint HPT36x/37x IDE" rev 0x03: DMA
pciide1: using irq 10 for native-PCI interrupt
wd1 at pciide1 channel 0 drive 0: <WDC WD1200JB-00DUA3>
wd1: 16-sector PIO, LBA48, 114473MB, 16383 cyl, 16 head, 63 sec, 234441648 sectors
wd1(pciide1:0:0): using PIO mode 4, Ultra-DMA mode 4
wd2 at pciide1 channel 1 drive 0: <WDC WD1200JB-75CRA0>
wd2: 16-sector PIO, LBA, 114440MB, 16383 cyl, 16 head, 63 sec, 234375000 sectors
wd2(pciide1:1:0): using PIO mode 4, Ultra-DMA mode 4
nge0 at pci0 dev 15 function 0 "NS DP83820 1/10/100/1000" rev 0x00: irq 3: address: 00:04:5a:7c:1a:24
nsgphy0 at nge0 phy 1: DP83861 10/100/1000 media interface, rev. 2
"Conexant HSF 56k HSFi" rev 0x01 at pci0 dev 16 function 0 not configured
isa0 at pcib0
isadma0 at isa0
pckbc0 at isa0 port 0x60/5
pckbd0 at pckbc0 (kbd slot)
pckbc0: using irq 1 for kbd slot
wskbd0 at pckbd0: console keyboard, using wsdisplay0
pcppi0 at isa0 port 0x61
midi0 at pcppi0: <PC speaker>
sysbeep0 at pcppi0
npx0 at isa0 port 0xf0/16: using exception 16
pccom0 at isa0 port 0x3f8/8 irq 4: ns16550a, 16 byte fifo
fdc0 at isa0 port 0x3f0/6 irq 6 drq 2
fd0 at fdc0 drive 0: 1.44MB 80 cyl, 2 head, 18 sec
biomask c640 netmask c648 ttymask c64a
pctr: 686-class user-level performance counters enabled
mtrr: Pentium Pro MTRR support
dkcsum: wd0 matched BIOS disk 80
dkcsum: wd1 matched BIOS disk 81
dkcsum: wd2 had no matching BIOS disk
root on wd0a
rootdev=0x0 rrootdev=0x300 rawdev=0x302
uhidev0 at uhub0 port 1 configuration 1 interface 0
uhidev0: ATEN 4 Ports USB KVM A R1.31, rev 1.10/1.00, addr 2, iclass 3/1
ukbd0 at uhidev0: 8 modifier keys, 6 key codes
wskbd1 at ukbd0 mux 1
wskbd1: connecting to wsdisplay0
uhidev1 at uhub0 port 1 configuration 1 interface 1
uhidev1: ATEN 4 Ports USB KVM A R1.31, rev 1.10/1.00, addr 2, iclass 3/1
ums0 at uhidev1: 5 buttons and Z dir.
wsmouse0 at ums0 mux 0
umass0 at uhub0 port 2 configuration 1 interface 0
umass0: ----- Ltd. SPRING-Rev1.1, rev 1.10/0.12, addr 3
umass0: using SCSI over BBB-P
scsibus1 at umass0: 2 targets
sd0 at scsibus1 targ 1 lun 0: <SPRING, MultiCard Slot A, 0100> SCSI0 0/direct removable
sd0: drive offline
[/code:1:d67e57b309]

and here is the output from the disklabel and fdisk programs:
[code:1:d67e57b309]
> p m
device: /dev/rwd2c
type: ESDI
disk: ESDI/IDE disk
label: WDC WD1200JB-75C
bytes/sector: 512
sectors/track: 63
tracks/cylinder: 16
sectors/cylinder: 1008
cylinders: 16383
total sectors: 234375000
free sectors: 0
rpm: 3600

16 partitions:
# size offset fstype [fsize bsize cpg]
a: 114439.6M 0.0M 4.2BSD 1024 8192 16 # (Cyl. 0 - 232512*)
c: 114440.9M 0.0M unused 0 0 # (Cyl. 0 - 232514*)

# fdisk wd2
Disk: wd2 geometry: 14589/255/63 [234372285 Sectors]
Offset: 0 Signature: 0x0
Starting Ending LBA Info:
#: id C H S - C H S [ start: size ]
------------------------------------------------------------------------
0: A6 0 0 1 - 14588 254 63 [ 0: 234372285 ] OpenBSD
1: 00 0 0 0 - 0 0 0 [ 0: 0 ] unused
2: 00 0 0 0 - 0 0 0 [ 0: 0 ] unused
3: 00 0 0 0 - 0 0 0 [ 0: 0 ] unused

[/code:1:d67e57b309]

bmw
September 14th, 2003, 15:28
I'll take a wild stab:

The PC BIOS enumerates certain well-known devices (eg LPT1:, COM1:) for use by code that makes INTxx calls. It creates short lists in BIOS ram of these. It counts up the hard disks and they eventually show up in DOS or Windows with drive letters.

I'm guessing that your wd2 drive is connected in some non-trad way (maybe?) such that the BIOS didn't see it on bootup.

[code:1:65608e7411]dkcsum: wd0 matched BIOS disk 80
dkcsum: wd1 matched BIOS disk 81
dkcsum: wd2 had no matching BIOS disk[/code:1:65608e7411]

80 and 81 are the codes that you pass in a register to an INT13 call when you want to read sectors during the early boot.

cod3fr3ak
September 14th, 2003, 16:56
Ok I'd buy that. But how do I fix it. It wasn't always reporting this.

bmw
September 14th, 2003, 17:40
Is anything actually broken? ("If it ain't broke ...")

Perhaps you updated the firmware on that HighPoint controller? Or flashed the BIOS? I assume that something changed recently ...

cod3fr3ak
September 16th, 2003, 00:10
Neg nothing changed that I can tell...