Re: missing ad0p2 device while GEOM sees GPT

From: Emanuel Strobl <Emanuel.Strobl_at_gmx.net>
Date: Mon, 11 Oct 2004 23:10:14 +0200
Am Montag, 11. Oktober 2004 19:03 schrieb Marcel Moolenaar:
[...]
> > But when I try it fails becaus there also is no /dev/ad0p at all.
>
> Odd. I'll see if I can reproduce this. In the mean time, see if md(4)
> exhibits the same behaviour.
>
> > Btw, it's a i386 box, not ia64.
>
> I know. :-)

Nice :) I have news, please let me know if I'm doing things the right way. Now 
I set up a standard MBR with one standard slice and standard labels inside. 
Then I issued 'gpt migrate -k -s ad0' and now I have a booting box and could 
add ('gpt add -b ??????? -s 2000000 -i 3 -t ufs ad0') a third GPT part of 
type ufs.
After a reboot I also have the device ad0p3, but why do I need to reboot?
And why doesn't 'gpt show ad0' work without setting kern.geom.debugflags to 
16?
And like I posted in another mail, as soon as there is a GPT on the disk 
sysinstall panickes (BARF <171>, panic: Going nowhere without my init!).

And while I'm at sysinstall I'd liek to repeat another posting: Sysinstall 
always sets the boot flag to any slice, so if you add (or define two at once) 
a slice you have a invalid partition tabel (in the MBR) with two active 
flags.

Here's some logs:
GEOM: new disk ad0
GEOM: Configure ad0s1, start 32256 length 10733958144 end 10733990399
GEOM: Configure ad0s2, start 10733990400 length 10733990400 end 21467980799
GEOM: Configure ad0p3, start 21467980800 length 1024000000 end 22491980799
[0] f:80 typ:165 s(CHS):0/1/1 e(CHS):1023/254/63 s:63 l:20964762
[1] f:00 typ:165 s(CHS):1023/255/63 e(CHS):1023/254/63 s:20964825 l:20964825
[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 10733958144 end 10733990399
GEOM: Configure ad0s2, start 10733990400 length 10733990400 end 21467980799
WARNING: Expected rawoffset 0, found 63
GEOM: Configure ad0s1a, start 0 length 268435456 end 268435455
GEOM: Configure ad0s1b, start 268435456 length 2121146368 end 2389581823
GEOM: Configure ad0s1c, start 0 length 10733958144 end 10733958143
GEOM: Configure ad0s1d, start 2389581824 length 268435456 end 2658017279
GEOM: Configure ad0s1e, start 2658017280 length 268435456 end 2926452735
GEOM: Configure ad0s1f, start 2926452736 length 7807505408 end 10733958143
WARNING: Expected rawoffset 0, found 20964825
GEOM: Configure ad0s2c, start 0 length 10733990400 end 10733990399
GEOM: Configure ad0s1a, start 0 length 268435456 end 268435455
GEOM: Configure ad0s1b, start 268435456 length 2121146368 end 2389581823
GEOM: Configure ad0s1c, start 0 length 10733958144 end 10733958143
GEOM: Configure ad0s1d, start 2389581824 length 268435456 end 2658017279
GEOM: Configure ad0s1e, start 2658017280 length 268435456 end 2926452735
GEOM: Configure ad0s1f, start 2926452736 length 7807505408 end 10733958143
GEOM: Configure ad0s2c, start 0 length 10733990400 end 10733990399

Received on Mon Oct 11 2004 - 19:10:23 UTC

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