From owner-freebsd-current Wed Apr 25 21:15:10 2001 Delivered-To: freebsd-current@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 821) id 8600F37B422; Wed, 25 Apr 2001 21:15:06 -0700 (PDT) Date: Wed, 25 Apr 2001 21:15:06 -0700 From: "John W. De Boskey" To: Current List Subject: 4.3-RELEASE will not boot after install (boot0 ?) Message-ID: <20010425211505.A15712@FreeBSD.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, I have a Dell Optiplex GXi 200Mhz machine which will not boot after installing 4.3-RELEASE. After rebooting, the normal F1 FreeBSD prompt comes up with a beep. Pressing F1 causes the machine to beep again. I believe the following code sequence is the failure location: /usr/src/sys/boot/i386/boot0/boot0.s main.15: movw $LOAD,%bx # Address for read movb $0x2,%ah # Read sector callw intx13 # from disk jc main.10 # If error cmpw $MAGIC,0x1fe(%bx) # Bootable? jne main.10 # No where main.10 beeps... maybe we could have it beep twice for a read err, once for a MAGIC error.. How I got here... Sysinstall disk sequence: Expert, delete existing partition, All, Quit, BootMgr, Auto, quit, etc, etc.. The above sequence works fine and produces a bootable system on other machines. Anyways, after doing a expert install but before rebooting, I can then go to the debug shell and get the following: From df Filesystem 512-blocks Used Avail Capacity Mounted on /dev/md0c 5607 3819 1732 69% / /dev/ad0s1a 198366 58206 124292 32% /mnt /mnt/dev/ad0s1f 1676814 1211590 331080 79% /mnt/usr /mnt/dev/ad0s1e 39630 234 36226 1% /mnt/var /dev/cd0c 1317216 1317216 0 100% /dist From dislabel -r ad0 # /dev/ad0c: type: ESDI disk: ad0s1 label: flags: bytes/sector: 512 sectors/track: 32 tracks/cylinder: 64 sectors/cylinder: 2048 cylinders: 1032 sectors/unit: 2115552 rpm: 3600 interleave: 1 trackskew: 0 cylinderskew: 0 headswitch: 0 # milliseconds track-to-track seek: 0 # milliseconds drivedata: 0 8 partitions: # size offset fstype [fsize bsize bps/cpg] a: 204800 0 4.2BSD 1024 8192 16 # (Cyl. 0 - 99) b: 139376 204800 swap # (Cyl. 100 - 168*) c: 2115552 0 unused 0 0 # (Cyl. 0 - 1032*) e: 40960 344176 4.2BSD 1024 8192 16 # (Cyl. 168*- 188) f: 1730416 385136 4.2BSD 1024 8192 16 # (Cyl. 188*- 1032*) I have dumped the 1st 100 blocks of the disk. They are at: http://people.freebsd.org/~jwd/noboot/bblocks.hd (hex dump) http://people.freebsd.org/~jwd/noboot/bblocks (raw data) the output from 'fdisk ad0' is: http://people.freebsd.org/~jwd/noboot/fdisk and the dmesg for the machine: http://people.freebsd.org/~jwd/noboot/dmesg The next thing I will try is a 'dd if=/dev/zero of=/dev/ad0 count=2'. If this fixes the problem, it seems to indicate the install process has a problem with existing fdisk partition information. If someone can provide some pointers I'll try to figure what is going on. Thanks, John To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message