Fog deploy drive order

[RocksAndRolls]

Hi I’m writing to some nvme systems. They have two nvme’s each.

We remove the secondary 250GB drive from the boot order and just left the 400s in right after IBM CL PXE boot option. So only two boot options… not that that would really help I guess.
There are no hard drive BBS options in this BIOS. Dont know if that helps anything.

The deploy keeps going on the wrong drives sometimes!

Do you know how we can force it to deploy to a particular drive?

[RocksAndRolls]

@sebastian-roth OK thanks, we’re on Latest from 25.07.2021, so we’ll update and try. Thank you for your time. Fog really is amazing software and saved us big time!!

[Sebastian Roth]

@rocksandrolls said in Fog deploy drive order:

We ran blockdev --getsize64 /dev/nmveblabla
and got this value:
500107862016
We put the drive size in bytes (above) into the “Host Primary disk” field.

For this to work you need the latest FOS init. In my last post I asked which version of FOG you use for that exact reason.

Read a bit on here:
https://forums.fogproject.org/topic/14822/nvme-madness/25?lang=en-US&page=2
and tried to get the file listed in one of your posts in that thread:
https://fogproject.org/inits/init-disk-size.xz
but the link is dead. Not sure if thats critical or not?

I removed that link because this is part of the latest inits since some time.

You can download those from github: https://github.com/FOGProject/fos/releases

[RocksAndRolls]

@sebastian-roth Hi thanks!

Read a bit on here:
https://forums.fogproject.org/topic/14822/nvme-madness/25?lang=en-US&page=2
and tried to get the file listed in one of your posts in that thread:
https://fogproject.org/inits/init-disk-size.xz
but the link is dead. Not sure if thats critical or not?

We ran blockdev --getsize64 /dev/nmveblabla
and got this value:
500107862016

We put the drive size in bytes (above) into the “Host Primary disk” field.

On boot after ipxe start, it says “Failed to read back partitions”
and “Args Passed: 500107862016”
Then it reboots.

Is it possible that blockdev --getsize64 is outputting a slightly incorrect number so that it wouldn’t work?

[Sebastian Roth]

@RocksAndRolls The issue with two or more NVMe drives is that the Linux kernel (which we use in FOG) enumerates NVMe drives in a non-predictable way. On every boot the order can be different. We have struggled with this and added an option to distinguish NVMe drives by size some months ago.

Which version of FOG do you use?