From owner-freebsd-questions@FreeBSD.ORG Fri Apr 22 16:01:25 2005 Return-Path: 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 4BAA116A4CE for ; Fri, 22 Apr 2005 16:01:25 +0000 (GMT) Received: from engine140.deployzone.net (engine140.deployzone.net [193.17.85.140]) by mx1.FreeBSD.org (Postfix) with SMTP id 9AC5243D5D for ; Fri, 22 Apr 2005 16:01:24 +0000 (GMT) (envelope-from chris@czv.com) Received: from adsl-212-90-218-5.cybernet.ch [212.90.218.5] by engine140.deployzone.net; Fri, 22 Apr 2005 17:57:25 +0200 In-Reply-To: <4268E78D.6030009@dial.pipex.com> References: <5af4153cc97abfa75d403f30eb8e9963@czv.com> <4268E78D.6030009@dial.pipex.com> Mime-Version: 1.0 (Apple Message framework v622) Content-Type: text/plain; charset=US-ASCII; format=flowed Message-Id: Content-Transfer-Encoding: 7bit From: Chris Zumbrunn Date: Fri, 22 Apr 2005 18:01:22 +0200 To: Alex Zbyslaw X-Mailer: Apple Mail (2.622) cc: questions@freebsd.org Subject: Re: Stuck in bootstrapping hell - how do I troubleshoot? X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 22 Apr 2005 16:01:25 -0000 On Apr 22, 2005, at 2:01 PM, Alex Zbyslaw wrote: > Chris Zumbrunn wrote: > >>> The server is in a datacenter and I can only access it via ssh and >>> boot either from the local disks or via network (freebsd or linux) - >>> no serial console, so I can't see where it gets stuck during the >>> bootstrap. >>> > Do you mean that you can boot the machine from an OS it picks up from > the network? Yes, exactly. > I.e. you can boot some OS which is not the one of the local disk? If > so, then boot the network FreeBSD, mount your local disks and look at > /var/log/messages. If the machine was at least booting FreeBSD when > it died then you should see something. I did check that. Nothing is written to /var/log/messages during a local boot attempt. So, the boot fails before that. I checked the MBR by comparing the output of "dd if=/dev/ar0 bs=512 count=1" on the trouble machines with that of a machine that boots fine - and they look identical. So, the MBR seems to be where it belongs. I guess the boot process gets stuck either during boot1/boot2 but before the kernel loads or there is a problem with the RAID1 setup and the machine never even gets to the point where it would look for a MBR on the ar0 disks. Also, when a debian disk image is installed on the same machine, it does boot from the local disks. So, maybe something is goofy with the partitioning/slicing - but I can't see what that would be. # fdisk ar0 ******* Working on device /dev/ar0 ******* parameters extracted from in-core disklabel are: cylinders=14945 heads=255 sectors/track=63 (16065 blks/cyl) Figures below won't work with BIOS for partitions not in cyl 1 parameters to be used for BIOS calculations are: cylinders=14945 heads=255 sectors/track=63 (16065 blks/cyl) Media sector size is 512 Warning: BIOS sector numbering starts with sector 1 Information from DOS bootblock is: The data for partition 1 is: sysid 165,(FreeBSD/NetBSD/386BSD) start 63, size 240107427 (117239 Meg), flag 80 (active) beg: cyl 0/ head 1/ sector 1; end: cyl 1023/ head 254/ sector 63 The data for partition 2 is: The data for partition 3 is: The data for partition 4 is: # disklabel ar0s1 # /dev/ar0s1: type: ESDI disk: ar0s1 label: flags: bytes/sector: 512 sectors/track: 63 tracks/cylinder: 255 sectors/cylinder: 16065 cylinders: 14945 sectors/unit: 240107427 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: 240107427 0 4.2BSD 2048 16384 89 # (Cyl. 0 - 14945*) c: 240107427 0 unused 0 0 # (Cyl. 0 - 14945*) Any further ideas or hints on what else to check would be very appreciated... Chris