From owner-freebsd-questions Mon Oct 7 1:54:21 2002 Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 98F4B37B401 for ; Mon, 7 Oct 2002 01:54:17 -0700 (PDT) Received: from fatma.kssgm.gov.tr (fatma.kssgm.gov.tr [195.142.143.69]) by mx1.FreeBSD.org (Postfix) with SMTP id 5E32D43E65 for ; Mon, 7 Oct 2002 01:54:14 -0700 (PDT) (envelope-from ulku.sayilan@kssgm.gov.tr) Received: (qmail 69574 invoked from network); 7 Oct 2002 08:52:09 -0000 Received: from unknown (HELO MELIHA) (172.16.0.2) by 0 with SMTP; 7 Oct 2002 08:52:09 -0000 Date: Mon, 7 Oct 2002 11:45:06 +0300 From: =?ISO-8859-1?B?3Gxr/CBTQVlJTEFO?= X-Mailer: The Bat! (v1.45) Personal Reply-To: ulku SAYILAN Organization: DGSPW X-Priority: 3 (Normal) Message-ID: <1367818873.20021007114506@kssgm.gov.tr> To: freebsd-questions@FreeBSD.ORG Subject: Fwd: Re[2]: BTX halted Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Hi, Monday, September 30, 2002, 6:28:12 PM, you wrote: I think this is SCSI device settle problem, since default boot has been set up from CD and SCSI ID 0 and disk SCSI ID is 4. Before FreeBSD installation MS NT was working on this computer. After installation FreeBSD, it doesnt start kernel boot but it has found disk and has do partitions. is it possible setting up SCSI device during installion?!? I have tried all installaion procedure but I couldn't found any setting I belive that SCSI contoller isnt work properly. Also maybe FreeBSD hasn't got drive of this controler?!?! Tekram DC - 390F PCI SCSI controller BIOS version V3.20 date 1999-3-29 disk is Quantum Atlas SCSI HD another error had depend on partition I understant but SCSý problem going on. Now it give such kind of error maounting root from ufs:/dev/md0c /stand/sysinstall running as init on vty0 page fault syncing disk done uptime 21 sn --------reboot------ During my search I've found such URL consist of some error code and linux kernel... http://lists.insecure.org/linux-kernel/2000/Feb/1489.html http://www.saclug.org/archive/2000/07/0332.html especially such URL same as my problems http://lists.insecure.org/linux-kernel/2000/Feb/0975.html I decided to this SCSI controller has got some problems about unix and derivatives... :( I couldn't kernel compile in FreeBSD ... I wonder I am wrong? can you advice me? I have done your previous advice during lsdev it couldn't found any device and than founded 12 different kernel error. MS> 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? MS> That's the boot loader crashing. That's pretty severe. In principal, MS> given the crashdump you've printed out, it should be possible to go MS> into the loader code and work out what was happening at that point, MS> but you'ld probably have to ask on freebsd-hackers to find someone MS> with the skills to do that. MS> This could be one of a number of problems --- disk hardware failure, MS> problems with the BIOS, wrong disk geometry. It's unlikely to be MS> anything to do with the NICs. MS> One problem, and the first thing to check, is something that used to MS> be fairly common until sysinstall was modified to remove the MS> temptation to use such things. "Dangerously dedicated" disks sound MS> pretty cool to the uninitiated, but beware: many SCSI MS> controllers/bioses can't cope with them. Unfortunately, the only MS> solution if you've installed your system this way is to go back to the MS> beginning and start all over again, and this time, install a proper MS> partition table. MS> If that isn't the case, can you verify that you can boot using the MS> boot blocks from the installation media (I assume CD Rom)? MS> Use this procedure: MS> Start to boot the system from the CD. When you get the 10 second MS> count down, hit the space bar to interrupt. You should end up at MS> the boot: prompt. MS> Now type: MS> unload MS> lsdev MS> This will either generate a BTX dump (in which case, you've MS> probably got pretty bad hardware problems) or it should show you a MS> list of all potential boot devices, including your hard drive. Now MS> type: MS> set currdev={harddrive} (ie. what lsdev returned for your HD) MS> load kernel MS> boot MS> and you should end up with a running system. MS> If that whole rigmarole worked, then the problem is that somehow the MS> boot blocks on your hard drive have become scrambled, and you can MS> probably repair things by reinstalling them. MS> If it didn't work and you're not using dangerously dedicated disks, MS> then you've got really nasty trouble lowlevel trouble which will take MS> time, effort and probably the services of a FreeBSD guru to sort out. MS> Cheers, MS> Matthew -- This e-mail was scanned by Antivirus! http://www.kssgm.gov.tr To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message