I dont really get this, what am i supposed to do?

I checked dmesg for these drives,

wd0 at atabus0 drive 0: <SAMSUNG SP0802N>
wd0: drive supports 16-sector PIO transfers, LBA48 addressing
wd0: 76351 MB, 155127 cyl, 16 head, 63 sec, 512 bytes/sect x 156368016 sectors
wd0: 32-bit data port
wd0: drive supports PIO mode 4, DMA mode 2, Ultra-DMA mode 5 (Ultra/100)
wd1 at atabus0 drive 1: <ST340015A>
wd1: drive supports 16-sector PIO transfers, LBA addressing
wd1: 38166 MB, 77545 cyl, 16 head, 63 sec, 512 bytes/sect x 78165360 sectors
wd1: 32-bit data port
wd1: drive supports PIO mode 4, DMA mode 2, Ultra-DMA mode 5 (Ultra/100)

One thing that confuses me is the that the disk i used with OpenBSD
(wd0) says LBA48 adressing and wd1 says LBA adressing, why is it like
that ?

On Wed, 20 Oct 2004 13:52:56 +0200, Martin Schmitz
<martin-schmitz@web.de> wrote:
> roberto wrote:
> > Martin Schmitz wrote:
> >
> >>evilknievel wrote:
> >>
> >>>I know it is 'd' i forgot to mention it, ive tried mounting 'a' but
> >>>with the same results.
> >>
> >>Your disklabel looks really weird. Normally, under NetBSD, Partition 'd'
> >>isn't actually a Partition you can mount, it's the whole disk, while
> >>Partition 'c' ist the whole NetBSD-Portion of the disk. In your case a
> >>and b looks the same, which is weird also. And they start with 0 which
> >>isn't correct either.
> >>
> > Yes, I agree: this is true on i386 architecture;
> 
> Oh yes, good point. I always tend to forget that NetBSD runs on so many
> platforms...
> 
> >>I suggest that you look in the NetBSD Handbook. There is a section about
> >>"Adding a new Harddisk" where there is a nice description of how to
> >>write a new disklabel to the disk. You should create a correct NetBSD
> >>disklabel which at least should contain an 'a' partition with the values
> >>below:
> >
> > Please take enough care when modifing the disklabel: al least make a
> > backup of it. Or make a backup of the data from OpenBSD.
> 
> Writing a new disklabel isn't so dangerous. By writing a new disklabel
> you can not actually destroy any data. The point is that it have to
> match the boundaries of the filesystems the disk contains.
> 
> If the OP had only one partition on this disk, chances are very good
> that it's boundaries are the same than the boundaries of the
> fdisk-partition (which the output of the fdisk command shows).
> 
> Martin
>