Skip site navigation (1)Skip section navigation (2)
Date:      Sun, 9 Jan 2011 11:27:09 +0200
From:      Zeus V Panchenko <zeus@ibs.dn.ua>
To:        "Luchesar V. ILIEV" <luchesar.iliev@gmail.com>
Cc:        freebsd-geom@freebsd.org
Subject:   Re: "secondary GPT table is corrupt or invalid" issue again
Message-ID:  <20110109092709.GC66627@relay.ibs.dn.ua>
In-Reply-To: <4D28FB15.9090907@gmail.com>
References:  <20110104170611.GA67159@relay.ibs.dn.ua> <4D28509D.607@yandex.ru> <20110108223747.GA66627@relay.ibs.dn.ua> <4D28FB15.9090907@gmail.com>

next in thread | previous in thread | raw e-mail | index | archive | help
Hi Luchesar,

thank you for reply,
> 
> Just my two cents. If I understood correctly from your first mail,
> you've set up the gmirror on /dev/ada{1,2}p1; that is, you're not
> mirroring the whole disk, but just the (single) partition on it.
> 
really the history was this:
i configured first drive as GPT (whole dedicated drive), newfs-ed it
and filled with data

after what i created mirror on it but not on entire disk /dev/ada0 (not on it's
single partition /dev/ada0p1) and i believe it was the cause of corruption

latter i found maillist explanation of the mistake and reconfigured
the mirror to use partitions instead of entire disk ... so, this way
the corruption appeared as i can judge now 

> have overwritten the secondary GPT. I was wondering if your problem
> could be related to the ahci(4) driver? I think I've seen reports of

no, i do not believe it is ahci(4) related issue since no other
simpthomes were observed (smart data shows no problems too) 

> 
> # gmirror label -v -h -b load gm0 gpt/teradisk0
> # gmirror insert -v -h -p 1 gm0 gpt/teradisk1
> 
> Using -h is important here, as otherwise gmirror will "forget" the
> labels. I'd like to draw your attention to the -p parameter as well.
> AFAIK it's not good to have the components with equal priority. Priority
> determines not only the preferred disk for the "prefer" algorithm, but,

mmm ... what will happend when master dies? will gmirror understand
that 0 priority disk now the one remaining alive? or i have to handle
that manually? to reassign 0 to the survived disk and to assign next
index to the new disk?

-- 
Zeus V. Panchenko
IT Dpt., IBS ltd			      	        GMT+2 (EET)



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20110109092709.GC66627>