Date: Sun, 21 Nov 2004 09:04:57 +0000 From: Matthew Seaman <m.seaman@infracaninophile.co.uk> To: "Jeffrey S. Kaye" <random@jeffreykaye.com> Cc: freebsd-questions@freebsd.org Subject: Re: BTX halted on backup server Message-ID: <20041121090457.GC10264@happy-idiot-talk.infracaninophile.co.uk> In-Reply-To: <41A02F9B.1020903@jeffreykaye.com> References: <41A02F9B.1020903@jeffreykaye.com>
next in thread | previous in thread | raw e-mail | index | archive | help
--iFRdW5/EC4oqxDHL Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sat, Nov 20, 2004 at 10:03:07PM -0800, Jeffrey S. Kaye wrote: > We have two servers, one mirrors the other. The backup server showed=20 > the following a couple days ago. It's still down. Any ideas? The=20 > primary is working just fine. > -jk >=20 > FreeBSD/i386 bootstrap loader, Revision 0.8 > (root@freebsd-stable.sentex.ca <mailto:root@freebsd-stable.sentex.ca>,=20 > Thu Apr 3 08:41:45 GMT 2003) > Loading /boot/defaults/loader.conf > /kernel text=3D0x171368 data=3D0x2342c+0x1bd08 > \ > Hit [Enter] to boot immediately, or any other key for command prompt. > Booting [kernel]... > - > int=3D0000000d err=3D00000000 efl=3D00010093 eip=3D002b200a > eax=3D0011e2e0 ebx=3D00000000 ecx=3D00000003 edx=3D000274c0 > esi=3Dffffffff edi=3D0003841c ebp=3D00094a7d esp=3D0009ea3f > cs=3D0008 ds=3D0010 es=3D0010 fs=3D0010 gs=3D0010 ss=3D0010 > cs:eip=3D6f 6e 73 6f 6c 65 3d 76-69 64 63 6f 6e 73 6f 6c > ss:esp=3D00 00 00 00 00 47 95 00-00 00 00 00 80 04 00 20 > BTX halted The boot loader cannot read the kernel from the disk drive into memory. That's pretty bad. Often it indicates that the disk has crashed. Or it could be a memory stick going AWOL. Or the CPU itself may have died. You need to investigate the machine to check if all of the hardware is in working order, and then depending on what you find, you probably need to reinstall and recover the system from backup. Try running memtest86 (http://www.memtest86.org/) from a floppy for several testing cycles: if memtest86 shows errors, then you've definitely got bad memory. If it doesn't show any errors, then you might still have bad memory, just beyond what memtest86 can detect; however that is quite rare. Next try booting from disk2 (from the installation media set) -- if that succeeds in booting and the memtest86 stuff ran OK then the CPU is probably OK. Then you can try running fsck(8) on all of the filesystems on your hard drive -- you may need to run it several times over the same partition. With luck you'll be able to get it to say 'filesystem clean'. Note that even if fsck(8) says the filesystem is clean, various files and directories may have disappeared, so recovering from backup once you've verified the hardware would be a good idea. Cheers, Matthew --=20 Dr Matthew J Seaman MA, D.Phil. 26 The Paddocks Savill Way PGP: http://www.infracaninophile.co.uk/pgpkey Marlow Tel: +44 1628 476614 Bucks., SL7 1TH UK --iFRdW5/EC4oqxDHL Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.6 (FreeBSD) iD8DBQFBoFo5iD657aJF7eIRAoC8AJ9zbtWDSbDDOauYGPTS23ubSmSUFgCbBdJI TgUM6pLn7g/Mm0eGaxLCick= =iphv -----END PGP SIGNATURE----- --iFRdW5/EC4oqxDHL--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20041121090457.GC10264>