Dustin Puryear
2003-Jul-09 19:59 UTC
[SAGE] FreeBSD 4.4-REL to FreeBSD 4.8-STABLE upgrade problem.
Before reading below: I am considering a new install rather than an upgrade of our servers. However, now I just want to beat this problem. :) At 02:19 PM 7/8/2003 +0000, Phil Pennock wrote:>On 2003-07-08 at 14:09 +0000, Phil Pennock wrote: > > There was a fairly major update to the IDE disk device handlers which > > required new device nodes. Bringing in the new MAKEDEV script and > > running that to create the disk devices will probably let you boot on > > the new kernel and try to repair things from there. > >Okay, I'll go get more coffee after sending this. You noticed this one. >Sorry. > >There are two mergemaster steps, one which does the minimum needed to >let the rest of the build continue.Yes, I ran 'mergemaster -p' but found that it really only merged my passwd and group files with the new ones. Unless it did some other things behind the scenes then there is no fix here.>The issue is, as you note, the device stuff. As I said though, just >pull in MAKEDEV manually and run it. That will fix this. Either >"sh MAKEDEV all" or "sh MAKEDEV ad0" ...I keep thinking it's the device stuff myself, but even MAKEDEV didn't do the trick (interesting notes below this stuff): # cd /usr/src # make update # /usr/src/usr.sbin/mergemaster/mergemaster.sh -p # make buildworld # make buildkernel # make installkernel # cd /etc # mv MAKEDEV MAKEDEV.old # cp /usr/src/etc/MAKEDEV . # sh MAKEDEV all # reboot Upon reboot I get my favorite lines: blah, blah blah, blah ar0: ... <ATA RAID1 array> [...] status: READY subdisks: 0 READY ad4: ... at ata2-master UDMA100 1 READY ad6: ... at ata3-master UDMA100 acd0: CDROM ... at ata0-master PIO4 Mounting root from ufs:/dev/ad4s1a Root mount failed: 16 Manual root filesystem specification: blah, blah Okay, so I reboot, but this time I load kernel.good and the system comes up fine with the old 4.4-REL kernel: ar0: ... <ATA RAID1 array> [...] status: READY subdisks: ad4: ... at ata2-master UDMA100 ad6: ... at ata3-master UDMA100 acd0: CDROM ... at ata0-master using PIO4 Oh, and I found that this server has a HighPoint RAID controller which can do RAID 0, 1, 0+1, and JBOD. Looking in my array configuration I see that we have: Channel Mode Status Primary Master: Mirror (RAID 1) for array #0 UDMA 5 HDD0 Secondary Master: Mirror ... UDMA 5 Hidden I initially said that this was a Promise controller. Here is my /etc/fstab for /: /dev/ad4s1a / ufs rw 1 1 Following is /var/run/dmesg.log after booting from kernel.good: Copyright (c) 1992-2001 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD 4.4-RELEASE #1: Sun Jun 30 21:23:39 CDT 2002 root@XXX:/usr/src/sys/compile/WWW Timecounter "i8254" frequency 1193182 Hz Timecounter "TSC" frequency 1494468860 Hz CPU: Pentium 4 (1494.47-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0xf07 Stepping = 7 Features=0x3febf9ff<FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CLFLUSH,DTS,ACPI,MMX,FXSR,SSE,SSE2,SS,<b28>,ACC> real memory = 268369920 (262080K bytes) avail memory = 257404928 (251372K bytes) Preloaded elf kernel "kernel.good" at 0xc0375000. md0: Malloc disk Using $PIR table, 12 entries at 0xc00fdea0 npx0: <math processor> on motherboard npx0: INT 16 interface pcib0: <Host to PCI bridge> on motherboard pci0: <PCI bus> on pcib0 pcib1: <PCI to PCI bridge (vendor=8086 device=2532)> at device 1.0 on pci0 pci1: <PCI bus> on pcib1 pci1: <NVidia Riva Vanta TNT2 graphics accelerator> at 0.0 irq 12 pcib2: <Intel 82801BA/BAM (ICH2) Hub to PCI bridge> at device 30.0 on pci0 pci2: <PCI bus> on pcib2 rl0: <D-Link DFE-530TX+ 10/100BaseTX> port 0x9000-0x90ff mem 0xd9000000-0xd90000ff irq 11 at device 3.0 on pci2 rl0: Ethernet address: 00:50:ba:60:7b:83 miibus0: <MII bus> on rl0 rlphy0: <RealTek internal media interface> on miibus0 rlphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto atapci0: <HighPoint HPT370 ATA100 controller> port 0xa400-0xa4ff,0xa000-0xa003,0x9c00-0x9c07,0x9800-0x9803,0x9400-0x9407 irq 10 at device 6.0 on pci2 ata2: at 0x9400 on atapci0 ata3: at 0x9c00 on atapci0 isab0: <Intel 82801BA/BAM (ICH2) PCI to LPC bridge> at device 31.0 on pci0 isa0: <ISA bus> on isab0 atapci1: <Intel ICH2 ATA100 controller> port 0xf000-0xf00f at device 31.1 on pci0 ata0: at 0x1f0 irq 14 on atapci1 ata1: at 0x170 irq 15 on atapci1 pci0: <Intel 82801BA/BAM (ICH2) USB controller USB-A> at 31.2 irq 11 pci0: <unknown card> (vendor=0x8086, dev=0x2443) at 31.3 irq 0 pci0: <Intel 82801BA/BAM (ICH2) USB controller USB-B> at 31.4 irq 11 pci0: <unknown card> (vendor=0x8086, dev=0x2445) at 31.5 irq 9 orm0: <Option ROM> at iomem 0xcc000-0xcf7ff on isa0 fdc0: <NEC 72065B or clone> at port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on isa0 fdc0: FIFO enabled, 8 bytes threshold fd0: <1440-KB 3.5" drive> on fdc0 drive 0 atkbdc0: <Keyboard controller (i8042)> at port 0x60,0x64 on isa0 atkbd0: <AT Keyboard> flags 0x1 irq 1 on atkbdc0 kbd0 at atkbd0 vga0: <Generic ISA VGA> at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 sc0: <System console> at flags 0x100 on isa0 sc0: VGA <16 virtual consoles, flags=0x300> sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 sio0: type 16550A sio1 at port 0x2f8-0x2ff irq 3 on isa0 sio1: type 16550A ppc0: <Parallel port> at port 0x378-0x37f irq 7 on isa0 ppc0: Generic chipset (NIBBLE-only) in COMPATIBLE mode lpt0: <Printer> on ppbus0 lpt0: Interrupt-driven port ppi0: <Parallel I/O> on ppbus0 ar0: 39266MB <ATA RAID1 array> [5005/255/63] subdisks: ad4: 39266MB <IC35L040AVER07-0> [79780/16/63] at ata2-master UDMA100 ad6: 39266MB <IC35L040AVER07-0> [79780/16/63] at ata3-master UDMA100 acd0: CDROM <CREATIVE CD5250E> at ata0-master using PIO4 Mounting root from ufs:/dev/ad4s1a --- Dustin Puryear <dustin@puryear-it.com> Puryear Information Technology, LLC <http://www.puryear-it.com> Providing expertise in the management, integration, and security of Windows and UNIX systems, networks, and applications.
Dustin Puryear
2003-Jul-09 19:59 UTC
[SAGE] FreeBSD 4.4-REL to FreeBSD 4.8-STABLE upgrade problem.
At 07:05 PM 7/9/2003 -0700, David Wolfskill wrote:> ># cd /etc > ># mv MAKEDEV MAKEDEV.old > ># cp /usr/src/etc/MAKEDEV . > ># sh MAKEDEV all > ># reboot > >Huh? I wouldn't expect MAKEDEV to live in /etc: > >g1-13(4.8-S)[1] ls /etc/MAK* >ls: No match. >g1-13(4.8-S)[2] uname -a >FreeBSD g1-13.catwhisker.org 4.8-STABLE FreeBSD 4.8-STABLE #586: Wed >Jul 9 06:23:15 PDT >2003 root@d146.catwhisker.org:/common/S1/obj/usr/src/sys/LAPTOP_30W i386 >g1-13(4.8-S)[3] ls -l /dev/MAKEDEV* >-r-xr-xr-x 1 root wheel 43789 Feb 11 06:40 /dev/MAKEDEV >-r-xr-xr-x 1 root wheel 2064 May 17 2001 /dev/MAKEDEV.local >g1-13(4.8-S)[4]Typo. I should have written /dev. Come on now.. --- Dustin Puryear <dustin@puryear-it.com> Puryear Information Technology, LLC <http://www.puryear-it.com> Providing expertise in the management, integration, and security of Windows and UNIX systems, networks, and applications.
Scott Lambert
2003-Jul-09 23:09 UTC
[SAGE] FreeBSD 4.4-REL to FreeBSD 4.8-STABLE upgrade problem.
On Wed, Jul 09, 2003 at 09:54:55PM -0500, Dustin Puryear wrote:> blah, blah > blah, blah > ar0: ... <ATA RAID1 array> [...] status: READY subdisks: > 0 READY ad4: ... at ata2-master UDMA100 > 1 READY ad6: ... at ata3-master UDMA100 > acd0: CDROM ... at ata0-master PIO4 > Mounting root from ufs:/dev/ad4s1a > Root mount failed: 16You need to be using /dev/ar0s1a. It is not good to use the devices in a RAID without going through the RAID controller. -- Scott Lambert KC5MLE Unix SysAdmin lambert@lambertfam.org
Dustin Puryear
2003-Jul-10 07:40 UTC
[SAGE] FreeBSD 4.4-REL to FreeBSD 4.8-STABLE upgrade problem.
At 02:08 AM 7/10/2003 -0400, Scott Lambert wrote:>On Wed, Jul 09, 2003 at 09:54:55PM -0500, Dustin Puryear wrote: > > blah, blah > > blah, blah > > ar0: ... <ATA RAID1 array> [...] status: READY subdisks: > > 0 READY ad4: ... at ata2-master UDMA100 > > 1 READY ad6: ... at ata3-master UDMA100 > > acd0: CDROM ... at ata0-master PIO4 > > Mounting root from ufs:/dev/ad4s1a > > Root mount failed: 16 > >You need to be using /dev/ar0s1a. It is not good to use the devices in >a RAID without going through the RAID controller.I agree but this is how the systems were setup and it worked *fine* with FreeBSD 4.4-REL. If it just plain doesn't work in 4.8-STABLE then okay, but I want to be sure that this is the problem. As I mentioned earlier I am now willing just to do a reinstall with 4.8-STABLE on several servers, but I am very curious about the real cause of this. Basically, I just want to know why this isn't working. --- Dustin Puryear <dustin@puryear-it.com> Puryear Information Technology, LLC <http://www.puryear-it.com> Providing expertise in the management, integration, and security of Windows and UNIX systems, networks, and applications.