Re: UEFI booting

Worked it out... The machine was in the GRUB_EFI class, but the package config that it was using was not telling it to install the "grub-efi" package, instead it was installing "grub-pc", so the command in the GRUB_EFI/10-setup script was working, it just wasn't doing what it was supposed to...

Re: MD devices are not wiped if LVM exists

Moving away from Andrew's WIPEDISKS script for a second, I have made a simple script containing just vgdisplay The output from this is null, suggesting that FAI does not see any LVM stuff at this stage, however after it has completed these bits of the disk_config, Executing: wipefs -af

Re: Limitation on VG name in setup-storage?

> On Tue, 02 Jul 2019 22:57:48 +1200, Andrew Ruthven > said: > When we manually create them, we tend to name our VGs for SSDs as: vg- > ssd[0-9]+ . > However, setup-storage doesn't like that and ends up confused with the > colums on the vg line in the disk_config file.

Re: Short circuit dracut?

> On Tue, 02 Jul 2019 22:52:58 +1200, Andrew Ruthven > said: > That. Is. Brilliant. > Thank you, 'ipappend 2' worked beautifully! I always use IAPPEND 6 which also sets the variable SYSUUID for more hardware details. -- regards Thomas

Limitation on VG name in setup-storage?

Hey, When we manually create them, we tend to name our VGs for SSDs as: vg- ssd[0-9]+ . However, setup-storage doesn't like that and ends up confused with the colums on the vg line in the disk_config file. Would it be able possible to have VG names allow hyphens? Cheers, Andrew -- Andrew

Re: MD devices are not wiped if LVM exists

Hey Jerry, That indicates to me that the MD is still running for some reason. I have occasionally had that as an intermittent fault, but I can't recall what I did to resolve it. Sorry, Andrew On Tue, 2019-07-02 at 11:34 +0100, Jerry Steele wrote: > Hi Andrew, > > Many thanks for that, however,

Re: Short circuit dracut?

That. Is. Brilliant. Thank you, 'ipappend 2' worked beautifully! On Tue, 2019-07-02 at 08:12 +0100, Justin Cattle wrote: > If you're using PXELINUX to boot, you can use the ipappend option > like this in your pxe config: > > ipappend 2 > > That will make it add this to the kernel comandline

Re: MD devices are not wiped if LVM exists

Hi Andrew, Many thanks for that, however, that seems to bring up another issue. During the partitioning step, it is able to create all the underlying partitions, but fails with: Executing: yes | mdadm --create /dev/md0 --level=raid1 --force --run --raid-devices=2 /dev/sda1 /dev/sdb1 (STDERR)

Re: Short circuit dracut?

If you're using PXELINUX to boot, you can use the ipappend option like this in your pxe config: ipappend 2 That will make it add this to the kernel comandline for the device it pxe'd from: BOOTIF= So dracut _should_ only use that interface and ignore the others. If that's not working for you

Short circuit dracut?

Hey, I think this has been asked before (possibly by me), but is it possible to short circuit dracut so it stops processing interfaces as soon as it has a successful DHCP responses? I'm doing some test builds on a machine with 10 interfaces and dracut takes 60 seconds to timeout on each

Re: MD devices are not wiped if LVM exists

On Mon, 2019-07-01 at 16:10 +0200, Thomas Lange wrote: > You can write a simple hook, which is then executed before > task_partition. Therefore, create a shell script > hooks/partition.DEFAULT Hey, Here is what I have as hooks/partition.WIPEDISKS it'll stop any MDs or VGs that were started by