Date: Sun, 1 Sep 1996 21:45:25 -0700 (PDT) From: Doug White <dwhite@gdi.uoregon.edu> To: Brandon Gillespie <brandon@tombstone.sunrem.com> Cc: freebsd-questions@FreeBSD.org Subject: Re: Boot Freeze after fsck.. Message-ID: <Pine.BSI.3.94.960901214419.227D-100000@gdi.uoregon.edu> In-Reply-To: <Pine.BSF.3.91.960901175309.183A-100000@tombstone.sunrem.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sun, 1 Sep 1996, Brandon Gillespie wrote: > I'm in the process of upgrading from a DELL 486 to a p150 on a tritonII > motherboard. It is SCSI based booting from an IDE drive and serving two > SCSI disks through an adapted 1540 controller. I pull the ram/disks over > to the pentium system and boot, everything _seems_ fine except for it > just STOPS after fsck reports fragmentation etc on all of the disks. > Usually at this point it would do ifconfig, fire up the net and go > through the rest of its boot. I just pulled everything from the pentium > system, plugged it into the 486 system and it works fine, completely > boots as it should (!?!). Try hitting Control-C and see what that does. It may be hanging up on a nameserver lookup on the ifconfig_xxx lines in sysconfig. Change any names there to their respective IP addresses and try that. > On the pentium system I can boot to a shell (-s), manually run fsck on > the disks and mount them, I can fire up the network by hand and it works, > everything SEEMINGLY should work, but it still halts after fsck. > > Help? Check your Ethernet card configuration too. Doug White | University of Oregon Internet: dwhite@resnet.uoregon.edu | Residence Networking Assistant http://gladstone.uoregon.edu/~dwhite | Computer Science Major
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSI.3.94.960901214419.227D-100000>