No PXE boot since Win10 4.0.7.1-2 (SOLVED)

[loggenk]

Hi All,

After the product-updater i can't pxe boot with Win10.

Windows 7 works without problem. Whats changed?

With regards,

Kees...

[uncle_scrooge]

Come on, Kees, please.
You want to be a bit more specific, won't you?
What exactly happens when?

And for any changes the release notes would be a good start to read.

Thanks.

[loggenk]

Hi Scrooge,

You're right. Not much info.

I thought many users have same problem

After opsi-product-updater its not possible to pxe boot in win10-x64 4.0.7.1-2

Other osses can pxe boot.
So my idea is that its not the winpe that causes the problem.

Correct me if i'm wrong

With regards,

Kees.......

[m.radtke]

with no PXE boot you mean that the bootimage isn't loaded?

The netboot product itself has no affiliation with the pxe boot of the opsi bootimage.
whenever you set a product to setup a pipe is created that can be read by the PXE loader

you can check if it exists in

Code: Alles auswählen

/tftpboot/linux/pxelinux.cfg/01-MACADDRESS

you can always run

Code: Alles auswählen

 tail -f /var/log/syslog

to check what happens when the desired client tries to access the tftp on the opsi-server

Cheers
Mathias

[loggenk]

Thnxs Mathias,

I don't know what problem is. But this seems not ok.

Jan 17 10:21:31 opsi-nl-dev atftpd[2871]: Serving linux/pxelinux.0 to 192.168.11.54:2070
Jan 17 10:21:31 opsi-nl-dev atftpd[2871]: Serving linux/pxelinux.0 to 192.168.11.54:2071
Jan 17 10:21:31 opsi-nl-dev atftpd[2871]: Serving linux/pxelinux.cfg/44454c4c-4d00-1047-8053-b7c04f524632 to 192.168.11.54:57089
Jan 17 10:21:31 opsi-nl-dev atftpd[2871]: Serving linux/pxelinux.cfg/01-d4-81-d7-5a-eb-d5 to 192.168.11.54:57090
Jan 17 10:21:31 opsi-nl-dev atftpd[2871]: Serving linux/pxelinux.cfg/C0A80B36 to 192.168.11.54:57091
Jan 17 10:21:31 opsi-nl-dev atftpd[2871]: Serving linux/pxelinux.cfg/C0A80B3 to 192.168.11.54:57092
Jan 17 10:21:31 opsi-nl-dev atftpd[2871]: Serving linux/pxelinux.cfg/C0A80B to 192.168.11.54:57093
Jan 17 10:21:31 opsi-nl-dev atftpd[2871]: Serving linux/pxelinux.cfg/C0A80 to 192.168.11.54:57094
Jan 17 10:21:31 opsi-nl-dev atftpd[2871]: Serving linux/pxelinux.cfg/C0A8 to 192.168.11.54:57095
Jan 17 10:21:31 opsi-nl-dev atftpd[2871]: Serving linux/pxelinux.cfg/C0A to 192.168.11.54:57096
Jan 17 10:21:31 opsi-nl-dev atftpd[2871]: Serving linux/pxelinux.cfg/C0 to 192.168.11.54:57097
Jan 17 10:21:31 opsi-nl-dev atftpd[2871]: Serving linux/pxelinux.cfg/C to 192.168.11.54:57098
Jan 17 10:21:31 opsi-nl-dev atftpd[2871]: Serving linux/pxelinux.cfg/default to 192.168.11.54:57099
Jan 17 10:21:31 opsi-nl-dev atftpd[2871]: Serving linux/menu.c32 to 192.168.11.54:57100
Jan 17 10:21:31 opsi-nl-dev atftpd[2871]: Serving linux/pxelinux.cfg/default to 192.168.11.54:57101

[loggenk]

This happens when i try to image a win7-x64:

Jan 17 10:25:15 opsi-nl-dev atftpd[2871]: Serving linux/pxelinux.cfg/C0A80B3 to 192.168.11.54:57092
Jan 17 10:25:15 opsi-nl-dev atftpd[2871]: Serving linux/pxelinux.cfg/C0A80B to 192.168.11.54:57093
Jan 17 10:25:15 opsi-nl-dev atftpd[2871]: Serving linux/pxelinux.cfg/C0A80 to 192.168.11.54:57094
Jan 17 10:25:15 opsi-nl-dev atftpd[2871]: Serving linux/pxelinux.cfg/C0A8 to 192.168.11.54:57095
Jan 17 10:25:15 opsi-nl-dev atftpd[2871]: Serving linux/pxelinux.cfg/C0A to 192.168.11.54:57096
Jan 17 10:25:15 opsi-nl-dev atftpd[2871]: Serving linux/pxelinux.cfg/C0 to 192.168.11.54:57097
Jan 17 10:25:15 opsi-nl-dev atftpd[2871]: Serving linux/pxelinux.cfg/C to 192.168.11.54:57098
Jan 17 10:25:15 opsi-nl-dev atftpd[2871]: Serving linux/pxelinux.cfg/default to 192.168.11.54:57099
Jan 17 10:25:15 opsi-nl-dev atftpd[2871]: Serving linux/menu.c32 to 192.168.11.54:57100
Jan 17 10:25:15 opsi-nl-dev atftpd[2871]: Serving linux/pxelinux.cfg/default to 192.168.11.54:57101
Jan 17 10:27:14 opsi-nl-dev atftpd[2871]: Serving linux/pxelinux.0 to 192.168.11.54:2070
Jan 17 10:27:14 opsi-nl-dev atftpd[2871]: Serving linux/pxelinux.0 to 192.168.11.54:2071
Jan 17 10:27:14 opsi-nl-dev atftpd[2871]: Serving linux/pxelinux.cfg/44454c4c-4d00-1047-8053-b7c04f524632 to 192.168.11.54:57089
Jan 17 10:27:14 opsi-nl-dev atftpd[2871]: Serving linux/pxelinux.cfg/01-d4-81-d7-5a-eb-d5 to 192.168.11.54:57090
Jan 17 10:27:14 opsi-nl-dev atftpd[2871]: Serving linux/install to 192.168.11.54:57091
Jan 17 10:27:22 opsi-nl-dev atftpd[2871]: Serving linux/miniroot.bz2 to 192.168.11.54:57092

[m.radtke]

looks like the pipe is not available

please check the log file locatet at

Code: Alles auswählen

/var/log/opsi/opsipxeconfd.log

if the entry is created and then again check if the pipe exists in

Code: Alles auswählen

/tftpboot/linux/pxelinux.cfg/01-MACADDRESS

[uncle_scrooge]

This is strange, to say the least.
As Mathias already mentioned, there is no direct connection between PXE boot and a OPSI netboot product (Be it W10, W7 or whatever.)
When you set a netboot product to 'setup' a pipe named 01-<MAC address of the client in question> is written to the 'PXE boot menu'.
When a client starts into PXE it looks for entries containing its IP address or part of (in hex) and entries containing its MAC address or part of.
If it finds something approbiate it will start it.

In both log snippets the client finds the correct entry (linux/pxelinux.cfg/01-d4-81-d7-5a-eb-d5). But only in the second it executes it.

Some questions.
After the update you restarted opsipxeconfd?
This happens only with this machine? Or are all of your clients affected?

And please do the following:
Set the W10 netboot product to setup.
Do a 'cat /tftpboot/linux/pxelinux.cfg/01-d4-81-d7-5a-eb-d5' on the OPSI server and post the output.
Make sure /tftpboot/linux/pxelinux.cfg/01-d4-81-d7-5a-eb-d doesn't exist any more.
(If it still exists, set the W10 netboot product back to none.)
Set the W7 netboot product to setup.
Do a 'cat /tftpboot/linux/pxelinux.cfg/01-d4-81-d7-5a-eb-d5' on the OPSI server and post the output.

Thanks.

[loggenk]

I'm a bit further now. But just a bit!

It does see the image now. But now it can't load pxelinux.cfg/01-d4-81-d7-5a-eb-d5

[loggenk]

Hi,

I restored a backup. But now i have another problem. When i try to image from a depot Opsi doesn't see the waiting image. In tftpboot/pxelinux the entry is present in the config server.

root@opsi-nl-dev:~# cat /tftpboot/linux/pxelinux.cfg/01-00-50-56-9b-d7-48
default opsi-install

label opsi-install
kernel install
append initrd=miniroot.bz2 video=vesa:ywrap,mtrr vga=791 quiet splash --no-log console=tty1 console=ttyS0 dn=dev.xxx.nl lang=en product=win10-x64 pckey=cc1f414fc16e291981c8096cfabcde7e service=https://192.168.13.60:4447/rpc hn=test-pxe-bar