From owner-freebsd-hackers Fri Sep 14 15: 5:13 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.speakeasy.net (mail11.speakeasy.net [216.254.0.211]) by hub.freebsd.org (Postfix) with ESMTP id 20DC337B408 for ; Fri, 14 Sep 2001 15:05:10 -0700 (PDT) Received: (qmail 30802 invoked from network); 14 Sep 2001 22:05:09 -0000 Received: from unknown (HELO laptop.baldwin.cx) ([64.81.54.73]) (envelope-sender ) by mail11.speakeasy.net (qmail-ldap-1.03) with SMTP for ; 14 Sep 2001 22:05:09 -0000 Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <3BA27936.E3D2FF13@urx.com> Date: Fri, 14 Sep 2001 15:05:01 -0700 (PDT) From: John Baldwin To: Kent Stewart Subject: Re: Does boot1 still have a > 1023 cyl limit? Cc: freebsd-hackers@freebsd.org, roam@ringlet.net, msmith@freebsd.org, rnordier@FreeBSD.org Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG >> Umm, ok. Did you do 'disklabel -B' to update the boot blocks on the disk >> (the >> boot blocks do _not_ live in the /boot files, they are part of the >> disklabel) >> when you updated the boot1 in bootsect.bsd? > > That I didn't do. What do I need to do? I'm reading the man page and > this is foreign country. This system was created at 4.2 and they were > created for me at that point. I don't want to have to reset the ntldr > butI could find the floppies to do a console recovery if I have to. > > Kent 'disklabel -B ad0' as root, where 'ad0' is the disk that boots FreeBSD and that the root filesystem is on. The files in /boot are sort of like the 'reference' version of the boot blocks. At the beginning of a FreeBSD slice is a 16-sector disklabel that describes the 'a', 'e', 'f' partitions, etc. The first sector of that is boot1. The second sector is the disklabel table itself, and the remaining 14 sectors hold boot2. Hope that makes sense. Until you use disklabel to update those boot blocks at the start of the slice, you are still using the old boot1 and boot2. However, you are using the ntldr which gets boot1 from somewhere else (not from the slice on the disk). When you updated that file, you ended up with mismatch since the new boot1 is still loading the boot2 off of the front of the slice, thus you end up with a new boot1 and an old boot2. -- John Baldwin -- http://www.FreeBSD.org/~jhb/ PGP Key: http://www.baldwin.cx/~john/pgpkey.asc "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message