Posts made by abos_systemax

As far as I am concerned: Yes, but the issue itself might not yet be fixed

Hi Tom, sorry for me not replying. I was busy with different work in the meantime.
I am unable to recall the IPadress of the NIC, because the chosen NIC was connected to a VLAN that does not have a DHCP-server nor a static IP assigned. Also; as soon as we took the other NIC down, the problem resolved itself. I am willing to check what happens if I re-enable the second NIC, but am not able to do so in the upcoming week.

@Sebastian-Roth

I used the command as stated above (dd, on linux).
However; I can no longer test the devices because they really had to be shipped to the customer.

For now this thread is solved (it ‘works’), but as soon as I can get my hands on a new device; I will test the ISO mentioned above.

Thanks all for the support!

@Tom-Elliott Trunk version 7843.

@Sebastian-Roth
I must be doing something wrong, but this ISO does not create a bootable USB stick (in fact, the dd command renders my USB completely useless)…

As far as I can see in the root of the stick, is that I am missing the BOOTX64.efi file, does that have to be created with ‘make’?

– edit: the USB sticks boots into Grub Rescue mode now, but booting to bzImage and init.xz results into unknown filesystem errors

all settings were set to eth0. As soon as we removed eth1, the multicast got onto the right eth port

Hello,

We’ve noticed an issue with a fresh Trunk installation (and upgrade after that) that the multicast session gets started on the wrong eth port.

We’ve found an article on this, explaining that you can select a eth port in the storage nodes configuration but, apparently eth0 is selected there, but the multicast service outputs to eth1. This is a nic that is not connected.

We are running fog on ESXi, with 2 nics attached to the VM

@abos_systemax said in Only one computer in group:

We are having the same issues here, on Trunk version 7843.
We’ve just updated and did not yet perform a removal of the dbase

With the new group table SQL from earlier this thread, it is resolved.

We are having the same issues here, on Trunk version 7843.
We’ve just updated and did not yet perform a removal of the dbase

Thanks. this seems to be my case

@Sebastian-Roth

none of the kernel options above yielded other results than no kernel options at all

Hello,

When I add a host to a group, (either via the host itself, or via the group list), the new host replaces the host(s) already in that group.
Adding does not work somehow.

@george1421 This is acceptable for the devices at this stage. The Task management window actually displays the current task status so that is ‘enough’ vision for us.

Although i’d be happy to help in the debug process, these 3 devices really have to go asap; so maybe we’d be able to run some more tests tomorrow, or else we have to wait till new machines get ordered.

I’ve noticed the weirdest things of all: The Capture task is actually running while the display stays black.
So, in fact the kernel and init.xz is just running as usual, but the display is not displaying anything

:edit: the display is not completely Black, it is ‘frozen’ in the iPXE output; so the last data displayed is

bzImage…OK
Init.xz…OK

Hi @Sebastian-Roth
I’ve tried the bzImage_epk with the specified host settings, but I still receive no messages; only ‘bzImage…OK!, init.xz…OK!’ and then nothing

@Sebastian-Roth
Same goes for your responses. We are very happy with your quick responses.

Sadly, I just got kicked out of the company because we’re closing for the night. But I will try the suggested option when I’m back tomorrow. Will post back as soon as I can.

@Sebastian-Roth said in unable to boot HP z240 in UEFI:

@abos_systemax Can you please try the mentioned old/bzImage_ad via PXE boot? So instead of copy it to the USB key you put it onto your FOG server (/var/www/fog/service/ipxe/bzImage). Rename the current bzImage yo sou can easily switch back later on. Leave DEBUG options on.

Did that, received the same output as when I booted to it from USB

No change after changing the debug level.

I am running BIOS level 1.21, I can only Rollback to 1.11, so that is not the route to go.
I will follow the other steps, post back soon

This is what I see with the bzImage_ad

This is what I see with Mattieuh’s bzImage_rb

is it me, or don’t I get Kernel Panics?

@Sebastian-Roth

I am afraid, that I am not seeing anything after booting to the USB.

How did you resolve the HP X2 210’s? reading the topic linked above…