From owner-freebsd-stable@FreeBSD.ORG Mon Jan 30 04:57:18 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9CFC816A420 for ; Mon, 30 Jan 2006 04:57:18 +0000 (GMT) (envelope-from freebsd@bolingbroke.com) Received: from sauron.bolingbroke.com (mail.bolingbroke.com [64.62.145.200]) by mx1.FreeBSD.org (Postfix) with ESMTP id 17C9443D46 for ; Mon, 30 Jan 2006 04:57:15 +0000 (GMT) (envelope-from freebsd@bolingbroke.com) Received: from sauron.bolingbroke.com (localhost.bolingbroke.com [127.0.0.1]) by sauron.bolingbroke.com (8.13.4/8.13.4) with ESMTP id k0U4vjqf001788 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Sun, 29 Jan 2006 20:57:45 -0800 (PST) (envelope-from freebsd@bolingbroke.com) Received: from localhost (ken@localhost) by sauron.bolingbroke.com (8.13.4/8.12.10/Submit) with ESMTP id k0U4vjJZ001785 for ; Sun, 29 Jan 2006 20:57:45 -0800 (PST) (envelope-from freebsd@bolingbroke.com) X-Authentication-Warning: sauron.bolingbroke.com: ken owned process doing -bs Date: Sun, 29 Jan 2006 20:57:45 -0800 (PST) From: Ken Bolingbroke X-X-Sender: ken@sauron.bolingbroke.com To: freebsd-stable@freebsd.org Message-ID: <20060129205612.G751@sauron.bolingbroke.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Subject: Re: Have the device names for hard discs been changed? (fwd) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 30 Jan 2006 04:57:18 -0000 On Sun, 29 Jan 2006, Christian Baer wrote: > ... > After that I started sysinstall and created a new slice and a new > partition which sysinstall called /dev/ad6s1d - which I expected. But > after creating the partition, the mount failed, because "no such file or > directory". And sure enough, ad6s1d did not exist in /dev/: > > jon# ls -l /dev/ad6* > crw-r----- 1 root operator 0, 76 Jan 22 15:23 /dev/ad6 > crw-r----- 1 root operator 0, 93 Jan 22 15:00 /dev/ad6c > crw-r----- 1 root operator 0, 96 Jan 22 15:00 /dev/ad6cs1 > crw-r----- 1 root operator 0, 92 Jan 22 15:00 /dev/ad6s1 > crw-r----- 1 root operator 0, 94 Jan 22 15:00 /dev/ad6s1c All the other responses on this thread are confusing the 'c' in here with the normal bsdlabel slice 'c' that covers the whole partition. This is something entirely different, a bug in sysinstall... You start out with a disk, /dev/ad6, and you "dangerously dedicate" it, then you _should_ have 's1' appended to /dev/ad6 to make /dev/ad6s1. But for some reason, it's appending it to /dev/ad6c instead to make /dev/ad6cs1, and then sysinstall tries to label the disk with /dev/ad6cs1c, etc, and fails. (Note the _two_ 'c' characters in that device name) My work around so far is after using fdisk in sysinstall to "dangerously dedicate" my disk, I exit, then "rm /dev/ad6cs1", then go back to sysinstall and label the disk, and then it will correctly use /dev/ad6s1. If I find some time, I might see how to submit a bug report on this... Ken