From owner-freebsd-current@FreeBSD.ORG Sat Nov 1 07:36:12 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3EC8116A4CE for ; Sat, 1 Nov 2003 07:36:12 -0800 (PST) Received: from segfault.kiev.ua (segfault.kiev.ua [193.193.193.4]) by mx1.FreeBSD.org (Postfix) with ESMTP id EDA5643FBD for ; Sat, 1 Nov 2003 07:36:10 -0800 (PST) (envelope-from netch@iv.nn.kiev.ua) Received: (from uucp@localhost) by segfault.kiev.ua (8) with UUCP id hB1Fa0YB037012; Sat, 1 Nov 2003 17:36:00 +0200 (EET) (envelope-from netch@iv.nn.kiev.ua) Received: (from netch@localhost) by iv.nn.kiev.ua (8.12.9p2/8.12.9) id hA1FYdnL001782; Sat, 1 Nov 2003 17:34:39 +0200 (EET) (envelope-from netch) Date: Sat, 1 Nov 2003 17:34:39 +0200 From: Valentin Nechayev To: Sergey Matveychuk Message-ID: <20031101153439.GB1626@iv.nn.kiev.ua> References: <3F9F299C.8050504@ciam.ru> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <3F9F299C.8050504@ciam.ru> X-42: On Organization: Dark side of coredump cc: current@freebsd.org Subject: Re: problems with sysinstall X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 01 Nov 2003 15:36:12 -0000 Wed, Oct 29, 2003 at 05:44:44, sem (Sergey Matveychuk) wrote about "problems with sysinstall": SM> The first one: when I install -current on disk where WinXP on first SM> slice, sysinstall brakes WinXP boot complete. I got 'Missing operation SM> system' everytime. Even I've tried 'fixboot' and reinstall WinXP. SM> Helps only 'dd if=/dev/zero of=/dev/ad0 count=100' and reinstall WinXP SM> on clean disk. It can be better reported if you show here 1) 0th block of disk (where MBR and master PT resides) 2) full PT listing, with both standard fdisk and linux fdisk (from ports) and both of them before installing FreeBSD (when XP works) and after (when is already broken). SM> When I've installed first -current on first slice and second -current on SM> second slice I got booting only first one. I use grub and either I set SM> root(hd1,0) or root(hd1,1) (yes, it's a second disk) and 'chainloader SM> +1' and 'boot' I've got always first -current boot. Looks like problem SM> with boot sector where hardcoded booting from first slice (?). Yes, this is tied to algorithm of boot1. On first step, it founds first *active* BSD partition in master PT. If didn't find any, it tries to find BSD partition in any state (inactive, due to first step failure). When found, records its number and starts boot2. Boot switcher, called boot0 (/boot/boot0) or BootEasy (in sysinstall), changes active partition flag (see boot0cfg(8)). When you use GRUB to call chainloader, it will start boot1 with the described result. To select boots using GRUB, use UFS1 (GRUB can't understand UFS2), with "root (hd0,1); boot /boot/loader", or use boot0. SM> The second: when I've tried to save results from Fdisk or Label menu SM> I've got the message: 'ERROR: Unable to write data to disk ad0!' SM> Why? I can change slices and partitions only when I boot from CD-ROM. Current GEOM implementation is too restrictive and doesn't allow any write to disk which has opened slices/partitions. phk@ promised change of this as soon as someone gives working implementation. -netch-