Re: 7.2-stable upgrade changes disknames

From: Willem Jan Withagen <wjw_at_digiware.nl>
Date: Sun, 28 Jun 2009 16:09:51 +0200
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:
<UNUSED>
The data for partition 3 is:
<UNUSED>
The data for partition 4 is:
<UNUSED>

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
Received on Sun Jun 28 2009 - 12:25:22 UTC

This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:39:50 UTC