Quoting Bruce Anderson (21-Sep-01 06:07:31):

> On Wed, Sep 19, 2001 9:08 AM, Georges Heinesch
> <mailto:geohei-ml@geohei.lu> wrote:

>>Ok, I reformulate the questions somewhat:
>>
>>1. Is there anything wrong with this fdisk output?
>>
>>   ----- cut here -----
>>   NetBSD disklabel disk geometry:
>>   cylinders: 16383 heads: 16 sectors/track: 63 (1008
>>   sectors/cylinder)
>>
>>   BIOS disk geometry:
>>   cylinders: 1023 heads: 255 sectors/track: 63 (16065
>>   sectors/cylinder)
>>
>>   Partition table:
>>   0: sysid 23 (OS/2 BM: hidden IFS)
>>       start 63, size 4192902 (2047 MB), flag 0x0
>>       beg: cylinder    0, head   1, sector  1
>>       end: cylinder  260, head 254, sector 63
>>   1: sysid 15 (Ext. partition - LBA)
>>       start 8385930, size 25350570 (12378 MB), flag 0x0
>>       beg: cylinder  522, head   0, sector  1
>>       end: cylinder 1023, head 254, sector 63
>>   2: sysid 27 (unknown)
>>       start 4192965, size 4192965 (2047 MB), flag 0x80
>>       beg: cylinder  261, head   0, sector  1
>>       end: cylinder  521, head 254, sector 63
>>   3: <UNUSED>
>>   ----- cut here -----

*** Why is the last partition (3:) always <UNUSED>?

> Parti  start      size        end
> 0         63  4192902    4192965
> 2    4192965   4192965    8385930
> 1    8385930  25350570   33736500
> 3   <UNUSED>

> This looks ok.

I got the wrong disk here. Disreagrd the fdisk data above ... (sorry!)

w----- cut here -----
NetBSD disklabel disk geometry:
cylinders: 16383 heads: 16 sectors/track: 63 (1008 sectors/cylinder)

BIOS disk geometry:
cylinders: 1023 heads: 255 sectors/track: 63 (16065 sectors/cylinder)

Partition table:
0: sysid 15 (Ext. partition - LBA)
    start 16065, size 81931500 (40005 MB), flag 0x0
    beg: cylinder    1, head   0, sector  1
    end: cylinder 1022, head 254, sector 63
1: sysid 169 (NetBSD)
    start 81947565, size 8122275 (3965 MB), flag 0x0
    beg: cylinder 1022, head 254, sector 63
    end: cylinder 1022, head 254, sector 63
2: <UNUSED>
3: <UNUSED>
----- cut here -----

*** Why does 0: start at 16065? To me, it looks like some unused
partition would be ahead (possibly 2: or 3:)?

> Post   dmesg |grep ^wd  along with your fdisk output.

NetBSD is on wd1.

----- cut here -----
wd0 at pciide0 channel 0 drive 0: <Maxtor 91728D8>
wd0: drive supports 16-sector pio transfers, lba addressing
wd0: 16479 MB, 16383 cyl, 16 head, 63 sec, 512 bytes/sect x 33750864 sectors
wd0: 32-bit data port
wd0: drive supports PIO mode 4, DMA mode 2, Ultra-DMA mode 2
wd1 at pciide0 channel 0 drive 1: <IBM-DTLA-307045>
wd1: drive supports 16-sector pio transfers, lba addressing
wd1: 43979 MB, 16383 cyl, 16 head, 63 sec, 512 bytes/sect x 90069840 sectors
wd1: 32-bit data port
wd1: drive supports PIO mode 4, DMA mode 2, Ultra-DMA mode 5
wd0(pciide0:0:0): using PIO mode 4, Ultra-DMA mode 2 (using DMA data transfers)
wd1(pciide0:0:1): using PIO mode 4, Ultra-DMA mode 2 (using DMA data transfers)
wd0: no disk label
----- cut here -----

> Ignore the CHS output, only start and size will be correct.

> Note that you only have 33736500 sectors in the table.
> 33736500/2^21 = 16.0868GB

ok.

> bruce@cougar$ fdisk wd1
> NetBSD disklabel disk geometry:
> cylinders: 16383 heads: 16 sectors/track: 63 (1008 sectors/cylinder)

> BIOS disk geometry:
> cylinders: 16383 heads: 16 sectors/track: 63 (1008 sectors/cylinder)

> Partition table:
> 0: sysid 169 (NetBSD)
>     start 63, size 87930801 (42934 MB), flag 0x80
>         beg: cylinder    0, head   1, sector  1
>         end: cylinder 1022, head  15, sector 63
> 1: <UNUSED>
> 2: <UNUSED>
> 3: <UNUSED>

> bruce@cougar$ dmesg |grep ^wd1
> wd1 at pciide0 channel 1 drive 0: <WDC WD450AA-00BAA0>
> wd1: drive supports 16-sector pio transfers, lba addressing
> wd1: 42934 MB, 16383 cyl, 16 head, 63 sec, 512 bytes/sect x 87930864
> sectors wd1: 32-bit data port wd1: drive supports PIO mode 4, DMA
> mode 2, Ultra-DMA mode 4 wd1(pciide0:1:0): using PIO mode 4,
> Ultra-DMA mode 2 (using DMA data transfers)
> ---------

> 1) Take the number of sectors from dmesg.
> 2) Do the math:
>    cougar wd1 = 87930864 sectors.
>    For Partition 0: size + start <= 87930864 sectors.
>    63 + 87930801 = 87930864 sectors.
> 87930864/2^21 = 41.92GB

geohei wd1 = 90069840 sectors.
For Partition 1: size + start <= 90069840 sectors
                 8122275+81947565=90069840
90069840/2^21 = 42.9486 GB

This looks all right for me ?!

Here the e-mail from the PowerQuest support. This is what all this is
about:

----- cut here -----
Partition errors are a result of discrepancies between the Cylinders,
Heads, Sectors being reported in the BIOS and the partition table
within the Master Boot Record. PartitionMagic will not allow for
changes to be made which would perpetuate existing problems on your
system.

The Partinfo indicates a problem that can not be resolved by
PartitionMagic. It will be necessary to backup the info in the NetBSD
partition, delete the partition and then recreate the partition. To
overcome this problem, please start PartitionMagic from the Rescue
Disk. When PartitionMagic comes up on the screen, exit the program and
then at the A:>, type PQMAGIC /IPE. This will ignore the partition
error and allow for the deletion of the problem partition.

Make the above changes, reboot your system and start without the
switch. Then recreate the partition and restore the data.
----- cut here -----

There must be another solution than to backup, recreate the partitions
and restore them. There are in fact 2 errors that PartitionInfo
reports.

----- cut here -----
0  1  80  1022  254  63  A9  1022  254  63  81,947,565  8,122,275
Info: Begin C,H,S values were large drive placeholders.
Info: End C,H,S values were large drive placeholders.
Actual values are:
0  1  80  5101    0   1  A9  5606  149  63  8,194,7565  8,122,275
Error #109: Partition ends after end of disk.
  ucEndCylinder (5606) must be less than 5606.
Info: Partition didn't end on cylinder boundary.
  ucEndHead expected to be 254, not 149.
----- cut here -----

1. The EndCyl is 1 Cyl too high.
2. The haed is wrong (149 instead of 254).

However I don't know if there values are now the BIOS reported values
or the MBR values?!

I'm sure there is a way to fix that without backup, recreating and
restore.

Any help would be greatly appreciated!

-- 
Cu  Georges Heinesch, Luxembourg
    geohei@geohei.lu
    http://www.geohei.lu
    PGP RSA & DH/DSS public key on request and on public servers

... ELLX