DragonFly BSD
DragonFly users List (threaded) for 2004-11
[Date Prev][Date Next]  [Thread Prev][Thread Next]  [Date Index][Thread Index]

Re: Inconsistant Fdisk Data


From: fu <fu@xxxxxxxxxxx>
Date: Mon, 22 Nov 2004 22:40:35 -0500

Gary Tivey wrote:

Hi Y'all;

In the process of trying to create an additional DFBSD/UFS partiton,
I've happend to get the following fdisk responses:

_____________________________________________________________________________


1.) After creating da0s3 using 1.1-Stable DragonFly fdisk interactive


 >fdisk da0
****** Working on device /dev/da0 *******
parameters extracted from in-core disklabel are:
cylinders=2233 heads=255 sectors/track=63 (16065 blks/cyl)

Figures below won't work with BIOS for partitions not in cyl 1
parameters to be used for BIOS calculations are:
cylinders=2233 heads=255 sectors/track=63 (16065 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 6,(Primary 'big' DOS (> 32MB))
    start 63, size 4192902 (2047 Meg), flag 0
        beg: cyl 0/ head 1/ sector 1;
        end: cyl 260/ head 254/ sector 63
The data for partition 2 is:
sysid 165,(DragonFly/FreeBSD/NetBSD/386BSD)
    start 4192965, size 20964825 (10236 Meg), flag 80 (active)
        beg: cyl 261/ head 0/ sector 1;
        end: cyl 541/ head 254/ sector 63
The data for partition 3 is:
sysid 165,(DragonFly/FreeBSD/NetBSD/386BSD)
    start 25157853, size 10474317 (5114 Meg), flag 0
        beg: cyl 542/ head 1/ sector 1;
        end: cyl 169/ head 254/ sector 63
The data for partition 4 is:
<UNUSED>

*** Notice that the ending cyl for partition 3 is '169'

_____________________________________________________________________

2.) Not being satisfied with this, I delete the partiton and create a new da0s3 using FreeBSD-4.10 sysinstall and get this:

 >fdisk da0
******* Working on device /dev/da0 *******
parameters extracted from in-core disklabel are:
cylinders=2233 heads=255 sectors/track=63 (16065 blks/cyl)

Figures below won't work with BIOS for partitions not in cyl 1
parameters to be used for BIOS calculations are:
cylinders=2233 heads=255 sectors/track=63 (16065 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 6,(Primary 'big' DOS (> 32MB))
    start 63, size 4192902 (2047 Meg), flag 0
        beg: cyl 0/ head 1/ sector 1;
        end: cyl 260/ head 254/ sector 63
The data for partition 2 is:
sysid 165,(DragonFly/FreeBSD/NetBSD/386BSD)
    start 4192965, size 20964825 (10236 Meg), flag 80 (active)
        beg: cyl 261/ head 0/ sector 1;
        end: cyl 1023/ head 254/ sector 63
The data for partition 3 is:
sysid 165,(DragonFly/FreeBSD/NetBSD/386BSD)
    start 25157790, size 10715355 (5232 Meg), flag 0
        beg: cyl 1023/ head 255/ sector 63;
        end: cyl 1023/ head 254/ sector 63
The data for partition 4 is:
<UNUSED>

*** Note ending cyl for partiton 2 is now '1023' and the data for partition 3 is obviously incorrect.

__________________________________________________________________



Since partition 3 is OK (disklabel/newfs/mounts) ,
The question here is ...." should I ignore the fdisk data?"

Thanks,
TIV
I tend to find issues when mixing Plan9 or other dos style disklabels, and BSD partitions. The loser , if there is a problem, is the Dos-based partition.



[Date Prev][Date Next]  [Thread Prev][Thread Next]  [Date Index][Thread Index]