NVMe madness

[Fog_Newb]

@Sebastian-Roth

Quick question. Does 1.5.9.36 dev build have these NVME related intits?

[Sebastian Roth]

@Fog_Newb No, not yet.

[Fog_Newb]

@Sebastian-Roth

Thanks. I updated and instead of checking I got lazy and posted. Where can I find info on what’s changed in each dev build? Github didn’t seem to have anything listed.

[Sebastian Roth]

@Fog_Newb Every dev version is just one single new commit to the dev-branch. So you know what changed looking at the commit history on github.

[Fog_Newb]

@sebastian-roth

Thanks.

[JJ Fullmer]

@fog_newb I suggest bookmarking https://github.com/FOGProject/fogproject/commits/dev-branch
So you can do a quick check for updates on the dev-branch anytime

@Sebastian-Roth So, just so I’m documenting the right thing.
Should I update the field’s documentation here https://docs.fogproject.org/en/latest/management/host-management.html#primary-disk
With a note (and a link to this forum post) that you can put either the devname or the exact blocksize/sector count with the linux command to find said sector count. Is that command accessible in the fog debug console? It looks like in windows you can use the powershell command get-disk | select Number, "FriendlyName", Size to list available disks by number and friendly name and display the blocksize. So it can be found fairly easily in Windows and Linux.

Is just adding a note by the field enough, or should there be a separate page explaining nvme selection?

[Fog_Newb]

@jj-fullmer

Thanks. That is exactly what I did.

[Sebastian Roth]

@JJ-Fullmer said:

Should I update the field’s documentation here https://docs.fogproject.org/en/latest/management/host-management.html#primary-disk

I had this on my list for a long time but somehow lost track of this, sorry.

The command on the FOS debug console would be: blockdev --getsize64 /dev/nvme0n1 (or whatever disk you want to get the block count from, e.g. /dev/sda)

It looks like in windows you can use the powershell command get-disk | select Number, "FriendlyName", Size …

Could be right but I am not exactly sure. Would you be able to verify this is the same number as we get from blockdev --getsize64 ... on a few systems?

Is just adding a note by the field enough, or should there be a separate page explaining nvme selection?

From my point of view adding this as a note is enough. The current explanation is pretty short and we might also add some examples.

[Fog_Newb]

@sebastian-roth

Are the new version going to have inits that use the device size? I am still copying over those custom ones after every update.

[Sebastian Roth]

@fog_newb said in NVMe madness:

Are the new version going to have inits that use the device size? I am still copying over those custom ones after every update.

Absolutely, the current inits on the fogproject website have the feature included. Though there was a bug in the script code that broke a deployment when no Host Primary Disk is set: https://forums.fogproject.org/topic/15523/dell-5060

I will update the official inits as soon as we have a reply the fixed init is working.

[Sebastian Roth]

Hi @JJ-Fullmer, as we have new requests on this topic I am going to rework this part again. So don’t bother about editing this part of the docs yet.

It looks like in windows you can use the powershell command get-disk | select Number, “FriendlyName”, Size …

Could be right but I am not exactly sure. Would you be able to verify this is the same number as we get from blockdev --getsize64 … on a few systems?

Can you please verify this is correct?

Is just adding a note by the field enough, or should there be a separate page explaining nvme selection?

From my point of view adding this as a note is enough. The current explanation is pretty short and we might also add some examples.

The new logic will be a bit more complex under the hood but still pretty straight forward for users. So adding this to the docs when it’s done together with some examples should be enough.

[JJ Fullmer]

@sebastian-roth I need to get back into those docs. Things have been just so crazy lately. When you have something working let me know and we’ll get it documented.