Date: Mon, 11 Oct 2004 23:10:14 +0200 From: Emanuel Strobl <Emanuel.Strobl@gmx.net> To: freebsd-current@freebsd.org Cc: Marcel Moolenaar <marcel@xcllnt.net> Subject: Re: missing ad0p2 device while GEOM sees GPT Message-ID: <200410112310.19966.Emanuel.Strobl@gmx.net> In-Reply-To: <20041011170312.GA16348@ns1.xcllnt.net> References: <200410111101.59356.Emanuel.Strobl@gmx.net> <200410111848.15914.Emanuel.Strobl@gmx.net> <20041011170312.GA16348@ns1.xcllnt.net>
next in thread | previous in thread | raw e-mail | index | archive | help
--nextPart1350075.zK3Ay9GF4q
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline
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=20
I set up a standard MBR with one standard slice and standard labels inside.=
=20
Then I issued 'gpt migrate -k -s ad0' and now I have a booting box and coul=
d=20
add ('gpt add -b ??????? -s 2000000 -i 3 -t ufs ad0') a third GPT part of=20
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=
=20
16?
And like I posted in another mail, as soon as there is a GPT on the disk=20
sysinstall panickes (BARF <171>, panic: Going nowhere without my init!).
And while I'm at sysinstall I'd liek to repeat another posting: Sysinstall=
=20
always sets the boot flag to any slice, so if you add (or define two at onc=
e)=20
a slice you have a invalid partition tabel (in the MBR) with two active=20
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
--nextPart1350075.zK3Ay9GF4q
Content-Type: application/pgp-signature
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.6 (FreeBSD)
iD8DBQBBava7Bylq0S4AzzwRAvrrAKCG/mOzmWW6/ptLd6E4EKX6D3MzyACgj/G4
vGS6X7MhzO3RQ9ZNpKBaF6Q=
=o1c0
-----END PGP SIGNATURE-----
--nextPart1350075.zK3Ay9GF4q--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200410112310.19966.Emanuel.Strobl>