switched motherboards 4.4

[vdubjunkie]

Hi all,

considered posting this in installation and upgrading, but I did neither. Feel free to move it should it make sense to do so.

I moved an existing OpenBSD 4.4 system on two ide drives to a new motherboard, yet the same 3 3com 905ctx cards. After telling my bios to use disk-1 I was proceeding forward nicely. However, when it was done booting, I had the request to tell it what shell to boot. Both disks seem to be recognized well. However, they are "not configured". Below is my dmesg gained by using a keyspan usb serial adapter on a mac running minicom and a "set tty com0" to capture the text

#  dmesg
OpenBSD 4.4 (GENERIC) #1021: Tue Aug 12 17:16:55 MDT 2008
    deraadt@i386.openbsd.org:/usr/src/sys/arch/i386/compile/GENERIC
cpu0: Unknown CPU Typ ("AuthenticAMD" 686-class, 512KB L2 cache) 1.11 GHz
cpu0: FPU,V86,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,ME
real mem  = 1039691776 (991MB)
avail mem = 996839424 (950MB)
mainbus0 at root
bios0 at mainbus0: AT/286+ BIOS, date 07/28/04, BIOS32 rev. 0 @ 0xfb990, SMBIOS)
bios0: vendor Phoenix Technologies, LTD version "ASUS A7V8X-MX SE ACPI BIOS Rev4
bios0: ASUS A7V8X-MX SE
apm0 at bios0: Power Management spec V1.2 (slowidle)
apm0: AC on, battery charge unknown
acpi at bios0 function 0x0 not configured
pcibios0 at bios0: rev 2.1 @ 0xf0000/0xd8d4
pcibios0: PCI IRQ Routing Table rev 1.0 @ 0xfd830/160 (8 entries)
pcibios0: PCI Exclusive IRQs: 3 5 10 11
pcibios0: PCI Interrupt Router at 000:17:0 ("VIA VT82C596A ISA" rev 0x00)
pcibios0: PCI bus #1 is the last bus
bios0: ROM list: 0xc0000/0x7e00 0xc8000/0x8000! 0xd0000/0x800 0xd1000/0x800
cpu0 at mainbus0
pci0 at mainbus0 bus 0: configuration mode 1 (no bios)
pchb0 at pci0 dev 0 function 0 "VIA VT8378 PCI" rev 0x00
ppb0 at pci0 dev 1 function 0 "VIA VT8377 AGP" rev 0x00
pci1 at ppb0 bus 1
vga1 at pci1 dev 0 function 0 "VIA VT8378 VGA" rev 0x01
wsdisplay0 at vga1 mux 1: console (80x25, vt100 emulation)
wsdisplay0: screen 1-5 added (80x25, vt100 emulation)
agp0 at vga1: v3, aperture at 0xe0000000, size 0xf000000
drm at vga1 unsupported
xl0 at pci0 dev 8 function 0 "3Com 3c905C 100Base-TX" rev 0x74: irq 11, addressc
bmtphy0 at xl0 phy 24: Broadcom 3C905C internal PHY, rev. 6
xl1 at pci0 dev 9 function 0 "3Com 3c905C 100Base-TX" rev 0x78: irq 5, address 4
bmtphy1 at xl1 phy 24: Broadcom 3C905C internal PHY, rev. 7
xl2 at pci0 dev 10 function 0 "3Com 3c905C 100Base-TX" rev 0x74: irq 10, addres4
bmtphy2 at xl2 phy 24: Broadcom 3C905C internal PHY, rev. 6
uhci0 at pci0 dev 16 function 0 "VIA VT83C572 USB" rev 0x80: irq 11
uhci1 at pci0 dev 16 function 1 "VIA VT83C572 USB" rev 0x80: irq 5
uhci2 at pci0 dev 16 function 2 "VIA VT83C572 USB" rev 0x80: irq 10
ehci0 at pci0 dev 16 function 3 "VIA VT6202 USB" rev 0x82: irq 3
usb0 at ehci0: USB revision 2.0
uhub0 at usb0 "VIA EHCI root hub" rev 2.00/1.00 addr 1
viapm0 at pci0 dev 17 function 0 "VIA VT8235 ISA" rev 0x00
iic0 at viapm0
spdmem0 at iic0 addr 0x50: 512MB DDR SDRAM non-parity PC2300CL2.5
spdmem1 at iic0 addr 0x51: 512MB DDR SDRAM non-parity PC2100CL2.5
pciide0 at pci0 dev 17 function 1 "VIA VT82C571 IDE" rev 0x06: ATA133, channel y
wd0 at pciide0 channel 0 drive 0: <SAMSUNG SV1204H>
wd0: 16-sector PIO, LBA, 114498MB, 234493056 sectors
wd0(pciide0:0:0): using PIO mode 4, Ultra-DMA mode 5
wd1 at pciide0 channel 1 drive 0: <IBM-DPTA-371360>
wd1: 16-sector PIO, LBA, 13042MB, 26712000 sectors
wd1(pciide0:1:0): using PIO mode 4, Ultra-DMA mode 4
auvia0 at pci0 dev 17 function 5 "VIA VT8233 AC97" rev 0x50: irq 10
ac97: codec id 0x41445370 (Analog Devices AD1980)
ac97: codec features headphone, 20 bit DAC, No 3D Stereo
audio0 at auvia0
vr0 at pci0 dev 18 function 0 "VIA RhineII-2" rev 0x74: irq 11, address 00:11:21
ukphy0 at vr0 phy 1: Generic IEEE 802.3u media interface, rev. 10: OUI 0x0040632
usb1 at uhci0: USB revision 1.0
uhub1 at usb1 "VIA UHCI root hub" rev 1.00/1.00 addr 1
usb2 at uhci1: USB revision 1.0
uhub2 at usb2 "VIA UHCI root hub" rev 1.00/1.00 addr 1
usb3 at uhci2: USB revision 1.0
uhub3 at usb3 "VIA UHCI root hub" rev 1.00/1.00 addr 1
isa0 at mainbus0
isadma0 at isa0
com0 at isa0 port 0x3f8/8 irq 4: ns16550a, 16 byte fifo
com0: console
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>
spkr0 at pcppi0
lpt0 at isa0 port 0x378/4 irq 7
wbsio0 at isa0 port 0x2e/2: W83697HF rev 0x12
lm1 at wbsio0 port 0x290/8: W83697HF
npx0 at isa0 port 0xf0/16: reported by CPUID; using exception 16
fdc0 at isa0 port 0x3f0/6 irq 6 drq 2
biomask ff6d netmask ff6d ttymask ffff
mtrr: Pentium Pro MTRR support
uhidev0 at uhub2 port 1 configuration 1 interface 0 " USB Keyboard" rev 1.10/1.2
uhidev0: iclass 3/1
ukbd0 at uhidev0: 8 modifier keys, 6 key codes
wskbd1 at ukbd0 mux 1
wskbd1: connecting to wsdisplay0
uhidev1 at uhub2 port 1 configuration 1 interface 1 " USB Keyboard" rev 1.10/1.2
uhidev1: iclass 3/0, 2 report ids
uhid0 at uhidev1 reportid 1: input=1, output=0, feature=0
uhid1 at uhidev1 reportid 2: input=3, output=0, feature=0
softraid0 at root
root on wd1a swap on wd1b dump on wd1b

[jggimi]

Both drives -- wd0 and wd1 -- are certainly configured in the dmesg you have posted here. I am going to take a wild guess and assume you've swapped channels when you connected the drives, and wd0 and wd1have reversed. Note the size difference of the two drives, and that wd0 is the larger:

wd0 at pciide0 channel 0 drive 0: <SAMSUNG SV1204H>
wd0: 16-sector PIO, LBA, 114498MB, 234493056 sectors
wd0(pciide0:0:0): using PIO mode 4, Ultra-DMA mode 5
wd1 at pciide0 channel 1 drive 0: <IBM-DPTA-371360>
wd1: 16-sector PIO, LBA, 13042MB, 26712000 sectors
wd1(pciide0:1:0): using PIO mode 4, Ultra-DMA mode 4

And look which drive you used for booting:

root on wd1a swap on wd1b dump on wd1b

Either swap IDE connections, or edit /etc/fstab while in single user mode and change drive numbers.

[vdubjunkie]

You know, it's funny. The one thing I knew I wasn't taking special note of was the drives. I actually did it intentionally to put myself in the situation to learn to know whether it would matter or not. I figured if I simply changed the disk BIOS expected to boot that it would be fine. Clearly I wasn't thinking too completely. It was much fun changing the drive again in BIOS, redirecting the display to com0 on boot, and watching it load on my MBP. Wicked fun.

Thank you very much for your assistance. It was also nice to learn exactly how you determined it. I bragged to my wife a couple of hours ago about the fact that likely within about 2 hours I'd have somebody reply who knew exactly. You guys never fail to maintain this image. Perhaps if I can spend more time in my professional life ON BSD, I will be able to contribute like so many of you do now!

Incidentally, my old MBP with what I believe to be a graphics instability has just become a 4.6 OS. Brilliant. My existing setup has 3 905ctxm NICs doing external, wired, wireless, with the wireless going to a vlan on my Catalyst, then joining with my linksys wap. That thing has become very flaky, and the MBP with a usb ethernet will do it all in one, much tighter space, and far more resources than necessary.

I love this OS

[There0]

I love this OS

Roger that, what person can not "love" this operating system? it is a gift from the developers to non-uber fellows like myself, and once agian i thank them endlessly ....

I use an old HP TC4200 tablet for my firewall, extra PCMCIA card and BAM its been running for almost 4 years now, feeding it an upgrade every release of OpenBSD. Works great, uses less room, no heat, and it runs Snort and some other tools just great sitting on my desk looking VERY non-threatening

[cohumat]

I've always been interspersed to learn from other peoples error and falsies. As of writing the reply some fifteen years later. I can remember how much of a struggle I had as bed newbie trying out and struggling with all three of the BSds. I can't tell you how many time I'd be up late in to the night on my Friday ans Saturday evenings trying what i at the time thought was every conceivable approach to both looking at the issue(s) that I was coming up against and trying to troubleshoot and fix my own messes.