Re: missing ad0p2 device while GEOM sees GPT

From: Emanuel Strobl <Emanuel.Strobl_at_gmx.net>
Date: Mon, 11 Oct 2004 18:48:09 +0200
Am Montag, 11. Oktober 2004 17:51 schrieb Marcel Moolenaar:
> On Oct 11, 2004, at 2:01 AM, Emanuel Strobl wrote:
> > Hello,
> >
> > I managed to get a GPT table onto my disk while beeing still able to
> > boot.
> > In verbose boot GEOM creates ad0p2 but no device is generated.
>
> The dmesg(8) below shows that da0p2c is created. Did you disklabel(8)
> (or should I say bsdlabel(8) the GPT partition?

No I didn't because I didn't know that I need a label inside a GPT partition.
But when I try it fails becaus there also is no /dev/ad0p at all.
Btw, it's a i386 box, not ia64.

Thank you,

-Harry

>
> > vberbose boot logs:
> > GEOM: new disk ad0
> > GEOM: Configure ad0p2, start 2146798080 length 512000000 end 2658798079
> > [0] f:80 typ:165 s(CHS):0/1/1 e(CHS):260/254/63 s:63 l:4192902
> > [1] f:00 typ:0 s(CHS):0/0/0 e(CHS):0/0/0 s:0 l:0
> > [2] f:00 typ:0 s(CHS):0/0/0 e(CHS):0/0/0 s:0 l:0
> > [3] f:00 typ:0 s(CHS):0/0/0 e(CHS):0/0/0 s:0 l:0
> > GEOM: Configure ad0s1, start 32256 length 2146765824 end 2146798079
> > WARNING: Expected rawoffset 0, found 4192965
> > GEOM: Configure ad0p2c, start 0 length 77876951040 end 77876951039
> > GEOM: Configure ad0s1a, start 0 length 1072693248 end 1072693247
> > GEOM: Configure ad0s1b, start 1072693248 length 1074072576 end
> > 2146765823
> > GEOM: Configure ad0s1c, start 0 length 2146765824 end 2146765823

Received on Mon Oct 11 2004 - 14:48:18 UTC

This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:38:16 UTC