Date: Mon, 30 Sep 2002 16:28:12 +0100 From: Matthew Seaman <m.seaman@infracaninophile.co.uk> To: =?iso-8859-1?Q?=DClk=FC?= SAYILAN <ulku.sayilan@kssgm.gov.tr> Cc: freebsd-questions@FreeBSD.ORG Subject: Re: BTX halted Message-ID: <20020930152812.GB81795@happy-idiot-talk.infracaninophi> In-Reply-To: <19427074029.20020930170407@kssgm.gov.tr> References: <19427074029.20020930170407@kssgm.gov.tr>
index | next in thread | previous in thread | raw e-mail
On Mon, Sep 30, 2002 at 05:04:07PM +0300, Ülkü SAYILAN wrote:
> I have installed the freebsd 4.3 to no name SCSI pent 166 pc after
> installation, during boot process he has gave error like this
>
> int:0000... err:000....1a efl:......1026 eip
> esi:00000.. ebx:0...... 0 ecx:........ edx
> cs:0... ed:0.......43 ebp:......... esp
>
>
> ds es fs gs ss
> cs:eip:cc:00..........00
> ss:ep:..............0300
>
> BTX halted
>
>
> What's the mean of this, anybody can explane this message?!?!?
>
> is the problem depend on SCSI boot/disk partition, or ethernet cards?
> or anythings?
That's the boot loader crashing. That's pretty severe. In principal,
given the crashdump you've printed out, it should be possible to go
into the loader code and work out what was happening at that point,
but you'ld probably have to ask on freebsd-hackers to find someone
with the skills to do that.
This could be one of a number of problems --- disk hardware failure,
problems with the BIOS, wrong disk geometry. It's unlikely to be
anything to do with the NICs.
One problem, and the first thing to check, is something that used to
be fairly common until sysinstall was modified to remove the
temptation to use such things. "Dangerously dedicated" disks sound
pretty cool to the uninitiated, but beware: many SCSI
controllers/bioses can't cope with them. Unfortunately, the only
solution if you've installed your system this way is to go back to the
beginning and start all over again, and this time, install a proper
partition table.
If that isn't the case, can you verify that you can boot using the
boot blocks from the installation media (I assume CD Rom)?
Use this procedure:
Start to boot the system from the CD. When you get the 10 second
count down, hit the space bar to interrupt. You should end up at
the boot: prompt.
Now type:
unload
lsdev
This will either generate a BTX dump (in which case, you've
probably got pretty bad hardware problems) or it should show you a
list of all potential boot devices, including your hard drive. Now
type:
set currdev={harddrive} (ie. what lsdev returned for your HD)
load kernel
boot
and you should end up with a running system.
If that whole rigmarole worked, then the problem is that somehow the
boot blocks on your hard drive have become scrambled, and you can
probably repair things by reinstalling them.
If it didn't work and you're not using dangerously dedicated disks,
then you've got really nasty trouble lowlevel trouble which will take
time, effort and probably the services of a FreeBSD guru to sort out.
Cheers,
Matthew
--
Dr Matthew J Seaman MA, D.Phil. 26 The Paddocks
Savill Way
Marlow
Tel: +44 1628 476614 Bucks., SL7 1TH UK
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-questions" in the body of the message
help
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20020930152812.GB81795>