From owner-freebsd-questions@FreeBSD.ORG Sat Oct 1 16:31:56 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 5DE5216A41F for ; Sat, 1 Oct 2005 16:31:56 +0000 (GMT) (envelope-from malachid@gmail.com) Received: from wproxy.gmail.com (wproxy.gmail.com [64.233.184.193]) by mx1.FreeBSD.org (Postfix) with ESMTP id CAA9C43D45 for ; Sat, 1 Oct 2005 16:31:55 +0000 (GMT) (envelope-from malachid@gmail.com) Received: by wproxy.gmail.com with SMTP id 36so52032wra for ; Sat, 01 Oct 2005 09:31:55 -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:references; b=JLWuSORVU3zMiNNoMa8i+4XVbE7FCtHIaC3yI0y8zJIvVCqKH44AKxZl3VMVOGhmYxmKammliKJW3tuJ/N81pYdjRSIaBQ9D6FT7SX300xng3CPziwU6nffxfBrJLSBAcAjFoBLk2hysdyj4oHUTBT80wq9hkLMCJCopkIN8gsY= Received: by 10.54.86.1 with SMTP id j1mr410005wrb; Sat, 01 Oct 2005 09:31:55 -0700 (PDT) Received: by 10.54.78.14 with HTTP; Sat, 1 Oct 2005 09:31:54 -0700 (PDT) Message-ID: Date: Sat, 1 Oct 2005 09:31:54 -0700 From: =?ISO-8859-1?Q?Malachi_de_=C6lfweald?= To: Kris Kennaway In-Reply-To: <20051001162036.GA80292@xor.obsecurity.org> MIME-Version: 1.0 References: <56342.202.142.188.22.1128175746.squirrel@webmail3.pair.com> <20051001162036.GA80292@xor.obsecurity.org> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: questions@freebsd.org, kashif@ebs.net.pk Subject: Re: NO dump device defined X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: =?ISO-8859-1?Q?Malachi_de_=C6lfweald?= List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 01 Oct 2005 16:31:56 -0000 Actually, I am having a similar problem.... Asus A8N-SLI Premium I was trying to do RAID5 on the Si3114. Then I found out the 3114 didn't support RAID5 in FreeBSD, and didn't support SATAII at all. So I switched t= o doing Raid 0+1 on the nVidia controller so that I could at least do SATAII. at the partition screen, I see: ad10 ad4 ad6 ad8 ar0 I assume that the ar0 is the raid, and the others are the drives that make up the raid I choose ar0 I see a disk with 976784130 sectors (476945MB) so looks like ar0 is the right one did "A: Use Entire Disk" and "S: Set Bootable" chose FreeBSD BootManager label screen ar0s1a / 1024MB UFS2 Y ar0s1b swap 8192MB SWAP ar0s1d /var 2048MB UFS2+S Y ar0s1e /tmp 2048 UFS2+S Y ar0s1f /home 8192MB UFS2+S Y ar0s1g /burn/image 10240MB UFS2+S Y ar0s1h /burn/tmp 15360MB UFS2+S Y X /usr 100GB UFS2+S Y X /jail 319GB UFS2+S Y distribution: all media: cd/dvd commit: panic: driver error: busdma dflt_lock called uptime: ?missed it? cannot dump. no dump device defined. rebooting On 10/1/05, Kris Kennaway wrote: > > On Sat, Oct 01, 2005 at 10:09:06AM -0400, 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 abor= t > > > > - --> Press a key on the console to reboot, > > > > - --> or switch off the system now. > > What does this have to do with the following question? > > > 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 > and > > 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! > For > > 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''. > > > > > > 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? > > It's almost always correct to just let sysinstall do what it wants. > Does this not work? > > Kris > > >