Thanks Don for your quick response. So I guess that this partion scheme is fixed? Do you have any suggestions/documentation how to configure a mirrored system for fail-over? Marcel
"Penney, Don" <Don.Penney@windriver.com> hat am 15. Januar 2019 um 16:21 geschrieben:
The initial primary disk filesystems are preconfigured by the kickstarts for each node. For the standard controller, for example, this is: - 500M for a boot partition - 20G for the rootfs (/) - the remainder for the primary volume group (currently named cgts-vg), which is used for various system volumes.
In addition, you've got the EFI partition that's automatically created as 300M. For legacy boot systems, there is a smaller BIOS boot partition.
-----Original Message----- From: Marcel Schaible [mailto:marcel@schaible-consulting.de] Sent: Tuesday, January 15, 2019 8:41 AM To: starlingx-discuss@lists.starlingx.io Subject: [Starlingx-discuss] Installation on a specific raid configuration?
Hi,
I am trying to install the 20190109 iso on a raid configuration with two nvme disks.
The installer by default creates the following disk layout and does not obye an existing partioning scheme:
# Start End Size Type Name 1 2048 616447 300M EFI System EFI System Partition 2 616448 1640447 500M Microsoft basic 3 1640448 42600447 19.5G Microsoft basic 4 42600448 430573567 185G Linux LVM
Questions: For waht are these partition #2 and #3 are used?
Actually we would like to have for a fail over scenario the following layout:
# Start End Size Type Name 1 2048 616447 300M EFI System EFI System Partition 2 616448 ...... 950G Raid mirrored to second nvme1n1p2 3 ....... ...... 32G swap
Is there a way to tell the installer this configuartion?
Thanks
Marcel
_______________________________________________ Starlingx-discuss mailing list Starlingx-discuss@lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss