From owner-freebsd-questions@FreeBSD.ORG Sat Oct 1 14:43:10 2005 Return-Path: X-Original-To: questions@freebsd.org 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 BF29416A41F for ; Sat, 1 Oct 2005 14:43:10 +0000 (GMT) (envelope-from robbak@gmail.com) Received: from wproxy.gmail.com (wproxy.gmail.com [64.233.184.197]) by mx1.FreeBSD.org (Postfix) with ESMTP id 54EFA43D46 for ; Sat, 1 Oct 2005 14:43:09 +0000 (GMT) (envelope-from robbak@gmail.com) Received: by wproxy.gmail.com with SMTP id 36so47181wra for ; Sat, 01 Oct 2005 07:43:09 -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:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=j4S4AsHyvmYGBDMF9rsA2vg+oSNebds0clrgtC65Qw+pfdJq/Fe6vfjTF0sUNknIjAoKnpiaZCc8xTYJWd4Aj5GU7GucDO2iu8EQR4IvLIJOsc+MsJ4Bvo2vwStcluioQLwoFzRamNdtvv4ySyuBWYt/LyNb7RTPNrT9mcmHOqU= Received: by 10.54.139.13 with SMTP id m13mr1140631wrd; Sat, 01 Oct 2005 07:43:09 -0700 (PDT) Received: by 10.54.130.7 with HTTP; Sat, 1 Oct 2005 07:43:09 -0700 (PDT) Message-ID: Date: Sat, 1 Oct 2005 14:43:09 +0000 From: Robert Backhaus To: "kashif@ebs.net.pk" In-Reply-To: <56342.202.142.188.22.1128175746.squirrel@webmail3.pair.com> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline References: <56342.202.142.188.22.1128175746.squirrel@webmail3.pair.com> Cc: questions@freebsd.org Subject: Re: NO dump device defined X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Robert Backhaus List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 01 Oct 2005 14:43:11 -0000 On 10/1/05, kashif@ebs.net.pk wrote: > Dear sir, > > I've had this problem for some time, and ,when i install freebsd 5.4 on > mercury Booard then following error message occur. > > > > panic: no init > > > Uptime: 2s > > > Cannot dump. No dump device defined. > > > Automatic reboot in 15 seconds - press a key on the console to abort > > > - --> Press a key on the console to reboot, > > > - --> or switch off the system now. > > > > > A one drives of 80GB, all exactly the same drives. > > The BIOS gives me this geometry: > Cylinders: 38309 > Head: 16 > Sectors: 255 > > > FreeBSD says, during bootup (dmesg): > Cylinders: 9729 > Head: 255 > Sectors: 63 > > Now, when i go to /stand/sysinstall, choose Index, Choose Partitioning an= d > choose a drive, for example ad1, i get this message: > > > WARNING: A geometry of 9729/16/63 for ad1 is incorrect. Using a more > likely geometry. If this geometry is incorrect or you are unsure as to > whether or not it's correct, please consult the Hardware Guide in the > Documentation submenu or use the (G)eometry command to change it now. > > Remember: you need to enter whatever your BIOS thinks the geometry is! Fo= r > IDE, it's what you were told in the BIOS setup. For SCSI, it's the > translation mode your controller is using. Do NOT use a ``physical > geometry''. Isn't it high time we got rid of this bit of noise? It wories so many peopl= e unneccesarily, and gets them (and us) bogged down with trying to work it out instead of addressing their problem!! > > > I did read lots on this, it seems sysinstall uses a limit of 63 sectors > and xxxxx cylinders, thus not accepting both the FreeBSD dmesg geometry > and the BIOS geometry. It then changes the geometry to: > > Cylinders: 14946 > Head: 255 > Sectors: 63 > Totalling 117239MB per drive > > This seems wrong to me, as the other two calculations produce 117246MB of > space. > > My question: how can I force the use of either the BIOS geometry or the > geometry given by dmesg? > > > Though i need to add that i've had this problem before, with a totally > different system with other chipset, other drive (WDM400 80GB) and with > FreeBSD 5.4. > > Anyone can help? Thanks!! :) > > Best Regard, > Muhammad kashif Forget the disk warning error: it is not your problem. Does the install complete without any other errors? By the way, your error is 'panic: no init'. No, I do not know what this mea= ns. Some useful information can be found by googling for that error message.