The interface setting on the server used to work for this, but it also caused issues if you had the wrong interface name.

Rather than deal with the interface naming for a task that needs to be exact, the IP of the fog server is used to automatically determine the interface to use for multicast tasks.

The interface setting in the GUI, now, basically just sets up the interface to check bandwidth from.

@arnaudrigole I believe I understand what you’re saying. You already have Windows installed on the machines, and switching to AHCI from the current RAID configuration will make your install unable to boot.

That said, while I understand the hardship it can require, you could switch it to AHCI and reinstall the instance of Windows.

That said, it seems, too me, that you may be potentially doing something illegally.

1. You have your machines and they came pre-installed with windows. This is fine by itself, but trying to capture an image is not technically allowed.
2. You’ve customized the machine to how you need it, and are trying to make an image that you can use for multiple machines of the same make/model. This shouldn’t cause any major issues from a legal standpoint so long as the machines to be receiving this image are using the very same install disk and software. But I believe customizing the OS is not allowed from a legal standpoint.

If you’re hard set on using the RAID in the current mode, I believe you would need to add mdraid=true on each of the machines host arguments that this would impact.

@Joe-Gill Then something is not working for yours as the “magnifying glass” should look like:

Notice the search text field.

I’m not seeing an issue with entering the search and pressing enter or entering the search and clicking the magnifying glass.

@Sebastian-Roth No ideas really.

However, the fact that it’s referencing the “boot” sector as the issue, I’m guessing the Partition table is configured in GPT? Does it look similar to the other GPT threads where the last partition in the disk is also the boot partition?

@UWPVIOLATOR once all nodes are at 1.5.5 I don’t imagine there being an issue with updating nodes as needed. 1.5.5 the logic for replication changed quite a lot which is why we highly suggest making sure all nodes are at least st this level first.

Mind you reasoning:

1. Logic checks occur at the nodes themselves, so 1.5.5 modified how these checks operated.

2. Master checks changed and need the information returned in such a way that only 1.5.5 did properly.

I’m sure there’s more but this is more to just illustrate the point more directly as to the “why”

@Quazz Such a simple mistake and yet so hard to see. Thanks for seeing it for sure.

The worry I see then,

/datastore/images is mounted how on the system?

What’s output of:

cat /etc/fstab

@Sebastian-Roth he has 4 shares. The FSid fields are copied thus likely causing the issue.

EDIT: Never mind, was on cell phone looking at the file didn’t see the commented out for the /images lines.

Move the components of imgargs to the kernel line after vmlinuz

Remove imgargs line