From owner-freebsd-questions@FreeBSD.ORG Tue May 10 07:34:41 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 5A16516A4F1 for ; Tue, 10 May 2005 07:34:41 +0000 (GMT) Received: from wproxy.gmail.com (wproxy.gmail.com [64.233.184.207]) by mx1.FreeBSD.org (Postfix) with ESMTP id F354443D6E for ; Tue, 10 May 2005 07:34:40 +0000 (GMT) (envelope-from ben.haysom@gmail.com) Received: by wproxy.gmail.com with SMTP id 69so1436881wra for ; Tue, 10 May 2005 00:34:40 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:mime-version:content-type:content-transfer-encoding:content-disposition; b=uWeu7t5eUuR3UonAwI8KLbNUxxkgGUd+vl0fcJletOc6Mubn9vQ/c/yR5alQPMnuJIRlR+yW/VIxuNgTa7eloiiTndPZiC+RbOPyWP0vwn9LqimBGQP5entpMZjMYcCxUapQ/L6rJksO4s77M4icOSuI6INZAkj7+4aidZv5jr4= Received: by 10.54.50.73 with SMTP id x73mr341162wrx; Tue, 10 May 2005 00:34:40 -0700 (PDT) Received: by 10.54.67.2 with HTTP; Tue, 10 May 2005 00:34:40 -0700 (PDT) Message-ID: Date: Tue, 10 May 2005 08:34:40 +0100 From: Ben Haysom To: freebsd-questions@freebsd.org Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Subject: error 16 X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: Ben Haysom List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 10 May 2005 07:34:41 -0000 Hi I have an AMD Duron 700Mhz running FreeBSD 5.3. When power up I get error 16 lba 287 error 16 lba 287 No /boot/loader fdisk from the installation CD finds the harddrive as normal. A friend found the following for me http://lists.freebsd.org/pipermail/freebsd-questions/2005-March/081879.html Seems to be the same, but the commands that person entered don't work for m= e.. I couldn't find anything searching on the full error. Any ideas, or shall I just do a complete reinstall? The machine isn't vital so that is plausible. Ben Haysom.