From owner-freebsd-current@FreeBSD.ORG Sun Jun 28 14:25:22 2009 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 98750106564A for ; Sun, 28 Jun 2009 14:25:22 +0000 (UTC) (envelope-from wjw@digiware.nl) Received: from mail.digiware.nl (mail.digiware.nl [80.255.245.173]) by mx1.freebsd.org (Postfix) with ESMTP id 581068FC19 for ; Sun, 28 Jun 2009 14:25:22 +0000 (UTC) (envelope-from wjw@digiware.nl) Received: from localhost (localhost.digiware.nl [127.0.0.1]) by mail.digiware.nl (Postfix) with ESMTP id EE73C153435; Sun, 28 Jun 2009 16:09:49 +0200 (CEST) X-Virus-Scanned: amavisd-new at digiware.nl Received: from mail.digiware.nl ([127.0.0.1]) by localhost (rack1.digiware.nl [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id BfmHQlCCRdKS; Sun, 28 Jun 2009 16:09:47 +0200 (CEST) Received: from [192.168.2.10] (vaio [192.168.2.10]) by mail.digiware.nl (Postfix) with ESMTP id D8E6B153434; Sun, 28 Jun 2009 16:09:47 +0200 (CEST) Message-ID: <4A4779AF.1020303@digiware.nl> Date: Sun, 28 Jun 2009 16:09:51 +0200 From: Willem Jan Withagen Organization: Digiware Management User-Agent: Thunderbird 2.0.0.22 (Windows/20090605) MIME-Version: 1.0 To: Aisaka Taiga References: <4A476C7C.3020605@withagen.nl> <4A477576.6030701@haruhiism.net> In-Reply-To: <4A477576.6030701@haruhiism.net> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Mailman-Approved-At: Mon, 29 Jun 2009 00:53:44 +0000 Cc: current@freebsd.org Subject: Re: 7.2-stable upgrade changes disknames X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 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: Sun, 28 Jun 2009 14:25:22 -0000 Aisaka Taiga wrote: > Willem Jan Withagen wrote: >> Tried UPGRADING, but could not find any suggestions that this was to >> be expected. Could also not find any previous suggestions for this. >> After which I got complaints that ad0s1a no longer existed. >> Al of a sudden it was called ad0a... >> In essence not a serious problem if one is a little fluent in FreeBSD, >> but could prove a source of a lot of questions, once 8.0 is released. > This isn't related to -current changes. > The naming scheme of ad0s1a refers to a classic DOS partition table with > a FreeBSD slice as DOS partition 0, and the FreeBSD root partition as > the first (a) partition inside the slice. > ad0a device name stands for a dangerously dedicated disk with no > partition table whatsoever; i.e. it's like doing not "fdisk /dev/ad0 ; > bsdlabel {params} /dev/ad0s1", but going "bsdlabel /dev/ad0" without > creating a DOS-style partition table. > > In your case it might mean some data corruption within the partition table. > What does fdisk /dev/ad0 report? You are correct that I installed "dangerously", since I do not want anything else on this disk: Asterbsd# fdisk /dev/ad0 ******* Working on device /dev/ad0 ******* parameters extracted from in-core disklabel are: cylinders=38792 heads=16 sectors/track=63 (1008 blks/cyl) Figures below won't work with BIOS for partitions not in cyl 1 parameters to be used for BIOS calculations are: cylinders=38792 heads=16 sectors/track=63 (1008 blks/cyl) Media sector size is 512 Warning: BIOS sector numbering starts with sector 1 Information from DOS bootblock is: The data for partition 1 is: sysid 165 (0xa5),(FreeBSD/NetBSD/386BSD) start 0, size 39102336 (19092 Meg), flag 80 (active) beg: cyl 0/ head 0/ sector 1; end: cyl 1023/ head 1/ sector 63 The data for partition 2 is: The data for partition 3 is: The data for partition 4 is: But the fstab was also installed by sysinstall from 7.2. So probably you are right that this is not specific a 8.0 problem. On 7.2 this used to work(tm), on 8.0 boot start complaining. So somewhere a (unwanted) flexibility got deleted And I have to manually fix my /etc/fstab to what is factual correct. And that was what my message was about: It can/will(??) bite a lot more users. With similar remarks and/or questions. --WjW