Re: Trying to get gpt + software raid + LVM in kickstart
On 11/29/18 1:09 AM, Digimer wrote:
zerombr
clearpart --all --drives=/dev/vda,/dev/vdb
ignoredisk --only-use=/dev/vda,/dev/vdb
bootloader --location=mbr --driveorder=/dev/vda,/dev/vdb
--boot-drive=/dev/vda
My first guess is that you're not specifying the disks to clearpart
properly. The documentation says that you should be using "clearpart
--all --drives=vda,vdb" for example:
https://pykickstart.readthedocs.io/en/latest/kickstart-docs.html#chapter-...
Specifying the drives incorrectly to "ignoredisk --only-use" might
prevent the installer from using any disks.
Here's the anaconda log:
====
09:00:24,855 WRN network: apply kickstart: --device does not exist
09:00:25,332 WRN network: set ONBOOT: --device does not exist
09:00:31,610 DBG storage: clearpart: initializing vda
09:00:31,735 DBG storage: clearpart: initializing vdb
09:00:32,023 DBG storage_utils: /dev/vda matches ['vda'] for
devicetree=existing 20 GiB disk vda (3) with non-existent gpt disklabel
09:00:32,132 DBG storage_utils: /dev/vdb matches ['vdb'] for
existing 20 GiB disk vdb (13) with non-existent gpt disklabel
09:00:32,137 DBG bootloader: new disk order: ['vda', 'vdb']
09:00:32,244 DBG storage_utils: /dev/vda matches ['vda'] for
devicetree=existing 20 GiB disk vda (3) with non-existent gpt disklabel
09:00:33,221 ERR ui.tui.spokes.storage: storage configuration failed:
09:00:35,323 ERR bootloader: bios order specified unknown disk vdb
09:00:35,324 ERR bootloader: bios order specified unknown disk vda
The log's a little confusing because there are a few places where it
does seem to match /dev/vda with a device, but mostly it reports that
the disks are unknown or don't exist.