Re: Adding Raidframe to existent GPT system

[César Catrián C. <ccatrian%eml.cc@localhost>]

On Mon, May 9, 2022, at 9:40 AM, Robert Elz wrote:
> Date:        Mon, 09 May 2022 09:08:36 -0400
>     From:        =?UTF-8?Q?C=C3=A9sar_Catri=C3=A1n_C=2E?= <ccatrian%eml.cc@localhost>
>     Message-ID:  <e032b817-b288-462b-b024-02c21bd73c3f%www.fastmail.com@localhost>
>
>   | Can someone please help me to find documentation for enabling
>   | raidframe for it.
>
> Unless you have at least 1 more drive, raidframe makes no
> sense.   If you do, just make equal sized partitions on
> both drives (recognise that any data that was there will be lost,
> no make backups) and follow the instruction in raidctl(8).
>
> If you are just wanting to combine two partitions on that
> drive into one, use ccd, not raidframe, it will work better
> in that environment.  Of course if the two partitions are
> adjacent, just delete the second, and make tge first bigger.
>
> With the possible exception of the last (which with care and
> the right steps, might preserve data in the first partition...
> might) all affected partitions are going to neex to be
> created anew for any of this.
>
> kre

Got three drives, two for a RAID-1 array and one more for backup. 

Got it enabled for MBR, but it seems the GPT adds complexity for Raidframe due that each GPT partition is offered as a new disk/wedge to the system.

Should be created only one wedge at first, using the entire disk, then apply raidframe to it (don't know if raidframe is ready for GPT?), then do again a GPT layout into the raid0 device to deploy the filesystems?


Regards
-- 
  César Catrián C.