From owner-freebsd-sysinstall@FreeBSD.ORG Fri Aug 30 13:31:50 2013 Return-Path: Delivered-To: freebsd-sysinstall@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 6C74691 for ; Fri, 30 Aug 2013 13:31:50 +0000 (UTC) (envelope-from nwhitehorn@freebsd.org) Received: from smtpauth3.wiscmail.wisc.edu (wmauth3.doit.wisc.edu [144.92.197.226]) (using TLSv1 with cipher RC4-MD5 (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 415B9254F for ; Fri, 30 Aug 2013 13:31:50 +0000 (UTC) MIME-version: 1.0 Content-transfer-encoding: 7BIT Content-type: text/plain; CHARSET=US-ASCII Received: from avs-daemon.smtpauth3.wiscmail.wisc.edu by smtpauth3.wiscmail.wisc.edu (Oracle Communications Messaging Server 7u4-27.01(7.0.4.27.0) 64bit (built Aug 30 2012)) id <0MSC00K00H82SC00@smtpauth3.wiscmail.wisc.edu> for freebsd-sysinstall@freebsd.org; Fri, 30 Aug 2013 08:31:43 -0500 (CDT) X-Spam-PmxInfo: Server=avs-3, Version=6.0.3.2322014, Antispam-Engine: 2.7.2.2107409, Antispam-Data: 2013.8.30.131815, SenderIP=0.0.0.0 X-Spam-Report: AuthenticatedSender=yes, SenderIP=0.0.0.0 Received: from wanderer.tachypleus.net (172-12-164-50.lightspeed.wlfrct.sbcglobal.net [172.12.164.50]) by smtpauth3.wiscmail.wisc.edu (Oracle Communications Messaging Server 7u4-27.01(7.0.4.27.0) 64bit (built Aug 30 2012)) with ESMTPSA id <0MSC00JSCIWR9010@smtpauth3.wiscmail.wisc.edu>; Fri, 30 Aug 2013 08:31:41 -0500 (CDT) Message-id: <52209EBB.7080703@freebsd.org> Date: Fri, 30 Aug 2013 06:31:39 -0700 From: Nathan Whitehorn User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:17.0) Gecko/20130811 Thunderbird/17.0.8 To: Mehmet Erol Sanliturk Subject: Re: Bug in bsdinstall (fs found where not present) References: <521FBC34.4070604@freebsd.org> <52200CEB.9030101@freebsd.org> In-reply-to: X-Enigmail-Version: 1.5.1 Cc: freebsd-sysinstall@freebsd.org X-BeenThere: freebsd-sysinstall@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Sysinstall Work List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 30 Aug 2013 13:31:50 -0000 On 08/29/13 22:39, Mehmet Erol Sanliturk wrote: > > > > On Thu, Aug 29, 2013 at 11:09 PM, Nathan Whitehorn > > wrote: > > On 08/29/13 17:02, Warren Block wrote: > > On Thu, 29 Aug 2013, Nathan Whitehorn wrote: > > > >> On 08/29/13 14:04, Warren Block wrote: > >>>> From a 9.2-PRERELEASE snapshot, go into the shell, create a > GPT disk > >>> layout with a bunch of partitions for filesystems and swap. > Exit the > >>> shell and run the installer. > >>> > >>> Go through each partition setting a mount point. Tell > bsdinstall to > >>> continue. It reports that the / partition has a preexisting > >>> filesystem (it does not, in fact; this disk had a mishmash of > MBR and > >>> NTFS on it). > >>> > >>> Tell bsdinstall to continue anyway. It does, and then reports > that it > >>> can't mount /dev/ada0p2 on /mnt, presumably because, contrary > to the > >>> misleading and incorrect error message, there is no filesystem on > >>> there. > >>> > >>> The install fails, try again, entering all the mount points, > and it > >>> will fail the same. > >>> > >>> Short term solution: newfs the / partition, so there really is a > >>> filesystem there for bsdinstall to detect and warn about. Then it > >>> works. > >> > >> bsdinstall has no way to detect whether or not you already have > UFS in a > >> freebsd-ufs file system. It assumes, when not given contrary > >> information, that a partition that exists is initialized. There > does not > >> seem to be a way around this. If you have any ideas, those would of > >> course be helpful. > > > > file(1) works well for detecting filesystems. > > > > For that matter, what is bsdinstall doing now that makes it say > there > > is a filesystem on a partition? Maybe the message is misleading. > > What that actually means is that the partition exists. (file doesn't > work on block devices, by the way) I'm happy to change the error > message. The default behavior is that, like partitioners on all other > operating systems, it treats creating partitions and running newfs as > intimately linked activities -- similarly, that the type marked in the > partition table is the actual filesystem type. Intermediate cases are > very hard to detect reliably. > -Nathan > _______________________________________________ > > > > > I am installing many different operating systems . > > One of the important problems is when > > "Use entire disk" > > is selected , some of the installers are still searching valid > partitions on disk > and failing miserably because there does not exist any one ( because > unit is new or corrupted ) or there are some partitions , etc. > remained from another different operating system . > > My opinion is that the first question should be to select an option among > > "Use entire disk" or > "Use existing file systems" . > > alternatives , only search valid file system(s) when "Use existing > file systems" is > selected . > > When "Use entire disk" is selected , directly apply file systems > creations by just > after determining the geometry of the unit under consideration . I agree with you -- that is exactly what the installer does in this case. -Nathan