From owner-freebsd-current Thu Apr 22 14: 7:48 1999 Delivered-To: freebsd-current@freebsd.org Received: from ceia.nordier.com (196-7-192-117.iafrica.com [196.7.192.117]) by hub.freebsd.org (Postfix) with ESMTP id 91E8915A36 for ; Thu, 22 Apr 1999 14:07:38 -0700 (PDT) (envelope-from rnordier@nordier.com) Received: (from rnordier@localhost) by ceia.nordier.com (8.8.7/8.6.12) id XAA19051; Thu, 22 Apr 1999 23:03:24 +0200 (SAT) From: Robert Nordier Message-Id: <199904222103.XAA19051@ceia.nordier.com> Subject: Re: Boot error In-Reply-To: <199904221610.MAA00841@kiwi.datasys.net> from Ayan George at "Apr 22, 99 12:10:56 pm" To: ayan@kiwi.datasys.net (Ayan George) Date: Thu, 22 Apr 1999 23:03:22 +0200 (SAT) Cc: freebsd-current@freebsd.org X-Mailer: ELM [version 2.4ME+ PL31 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Ayan George wrote: > Ever since installing 4.0-CURRENT, I've gotten the following > message when I boot FreeBSD: > > Disk error 0x1 (lba=0x12007f) > No /boot/loader > > >> FreeBSD/i386 BOOT > Default: 0:wd(0,a)kernel > > boot: > > > If I type: > > wd(0,a)/boot/loader > > at the boot prompt, it claims it cant find the file but I know it > exists. > > I can load the kernel from the boot prompt however. I've tried > rebuilding /boot/loader from newer source to no avail. > > There is obviously something I'm overlooking. Has anyone else seen > this problem and know how to fix it? > > -Ayan Disk error 0x1 means "invalid argument". The most likely cause is that your / filesystem spans cylinder 1023 and /boot/loader is inaccessible for this reason. -- Robert Nordier To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message