Re: more gpart/glabel problems

> This is an OpenPGP/MIME signed message (RFC 2440 and 3156) > --enig796DC9FCBCDF02E77B675B44 > Content-Type: text/plain; charset=KOI8-R > Content-Transfer-Encoding: quoted-printable > > On 14.01.2011 14:33, Daniel Braniss wrote: > >> On 14.01.2011 13:37, Daniel Braniss wrote: > >>> an

Re: more gpart/glabel problems

On 14.01.2011 14:33, Daniel Braniss wrote: >> On 14.01.2011 13:37, Daniel Braniss wrote: >>> and on the console: >>> GEOM: mfid0: the secondary GPT table is corrupt or invalid. >>> GEOM: mfid0: using the primary only -- recovery suggested. >>> GEOM: mfid0: the secondary GPT table is cor

Re: more gpart/glabel problems

> On 14.01.2011 13:37, Daniel Braniss wrote: > > and on the console: > > GEOM: mfid0: the secondary GPT table is corrupt or invalid. > > GEOM: mfid0: using the primary only -- recovery suggested. > > GEOM: mfid0: the secondary GPT table is corrupt or invalid. > > GEOM: mfid0: using

Re: more gpart/glabel problems

On 14.01.2011 13:37, Daniel Braniss wrote: > and on the console: > GEOM: mfid0: the secondary GPT table is corrupt or invalid. > GEOM: mfid0: using the primary only -- recovery suggested. > GEOM: mfid0: the secondary GPT table is corrupt or invalid. > GEOM: mfid0: using the

Re: more gpart/glabel problems

Am 14.01.2011 um 11:37 schrieb Daniel Braniss: > now: > glabel lable r0 mfid0 > so what am I doing wrong? glabel uses the last sector of the device to store the label. GPT keeps it's backup table there. Additionally, GEOM then tastes the glabel device, and the size of the glabel device

more gpart/glabel problems

the provider in this case is mfid0 mfi0: mfid0: on mfi0 mfid0: 953344MB (1952448512 sectors) RAID volume 'r0' is optimal so I first use gpart: gpart create -s GPT mfid0 gpart bootcode -b /boot/pmbr mfid0 gpart add -s2G -t freebsd-ufs mfid0 so far,