Client startet nicht in WinPE (SSD nicht in UEFI als Bootoption sichtbar)

[plnb]

Hallo zusammen,

wir haben opsi für die automatische Windows-Installation via PXE konfiguriert und das ganze hatte für die betroffene Hardware bereits funktioniert. Seit dem sind wir uns keiner Änderungen bewusst; leider funktioniert die Installation jetzt nicht mehr.

Hardware: DELL Latitude 5530
Opsi-Version: 4.2

Das Verhalten ist folgendes:
Wenn ich das netboot-Produkt (Windows10) auf Setup setze, startet der Client wie gewünscht in das opsi-bootimage und formatiert und kopiert winpe.
Dann startet der Laptop neu und sollte in WinPE booten, das funktioniert aber nicht und wir landen wieder im PXE-Boot.
Im UEFI gibt es auch keinen Eintrag für die SSD im Bootorder-Menü.

Anbei die meiner Meinung nach relevanten Logzeilen:

Code: Alles auswählen

[...]
(6369)    [5] [2024-02-22 11:43:00.931] [               ] geometryLine : /dev/nvme0n1: 488386 cylinders, 64 heads, 32 sectors/track   (Posix.py:1557)
(6417)    [5] [2024-02-22 11:43:00.971] [               ] Disk order:   (<string>:68)
[...]
(6444)    [5] [2024-02-22 11:43:00.976] [               ]  - /dev/nvme0n1 (rotational? False) (sizeG 476) (uuid 5149e836)   (<string>:70)
(6445)    [5] [2024-02-22 11:43:00.976] [               ] Normally we using disk 0   (setup.py:586)
[...]
(6584)    [5] [2024-02-22 11:43:01.135] [               ] multi_disk_mode is 0 - so we use disk number: 0 uuid:5149e836   (setup.py:589)
(6585)    [5] [2024-02-22 11:43:01.135] [               ] Using disk device /dev/nvme0n1   (setup.py:591)
(6586)    [5] [2024-02-22 11:43:01.135] [               ] Check if disk /dev/nvme0n1 is ssd or classic (rotational) HD   (<string>:75)
(6587)    [5] [2024-02-22 11:43:01.136] [               ] Disk /dev/nvme0n1 is not rotational (SSD)   (<string>:91)
[...]
(6660)    [5] [2024-02-22 11:43:01.154] [               ] Clear first 512 bytes on /dev/nvme0n1 to remove grub and so on ...   (setup.py:970)
(6665)    [5] [2024-02-22 11:43:03.167] [               ] using sgdisk to clear not usable partition table of /dev/nvme0n1   (setup.py:988)
(6689)    [5] [2024-02-22 11:43:04.263] [               ] unrecognized partition table type, writing empty partitiontable   (Posix.py:1525)
(6725)    [5] [2024-02-22 11:43:04.291] [               ] geometryLine : /dev/nvme0n1: 488386 cylinders, 64 heads, 32 sectors/track   (Posix.py:1557)
(6732)    [5] [2024-02-22 11:43:04.299] [               ] geometryLine : /dev/nvme0n1: 488386 cylinders, 64 heads, 32 sectors/track   (Posix.py:1557)
(6745)    [5] [2024-02-22 11:43:04.307] [               ] Write Master Boot Record   (setup.py:995)
(6773)    [5] [2024-02-22 11:43:04.348] [               ] Create system partition on /dev/nvme0n1p1 start: 0M, size: 483386M   (<string>:263)
(6851)    [5] [2024-02-22 11:43:06.743] [               ] geometryLine : /dev/nvme0n1: 488386 cylinders, 64 heads, 32 sectors/track   (Posix.py:1557)
(6858)    [5] [2024-02-22 11:43:06.751] [               ] geometryLine : /dev/nvme0n1: 488386 cylinders, 64 heads, 32 sectors/track   (Posix.py:1557)
(6866)    [5] [2024-02-22 11:43:06.759] [               ] geometryLine : /dev/nvme0n1: 488386 cylinders, 64 heads, 32 sectors/track   (Posix.py:1557)
(6873)    [5] [2024-02-22 11:43:06.767] [               ] geometryLine : /dev/nvme0n1: 488386 cylinders, 64 heads, 32 sectors/track   (Posix.py:1557)
(6902)    [5] [2024-02-22 11:43:06.785] [               ] /dev/nvme0n1p1 exists as device - fine   (<string>:248)
(6903)    [5] [2024-02-22 11:43:06.789] [               ] Partition /dev/nvme0n1p1 has a correct block alignment   (<string>:154)
(6904)    [5] [2024-02-22 11:43:06.790] [               ] Create file system ntfs on partition system (/dev/nvme0n1p1)   (<string>:339)
(6923)    [5] [2024-02-22 11:43:21.961] [               ] /dev/nvme0n1p1 exists as device - fine   (<string>:329)
(6924)    [5] [2024-02-22 11:43:21.961] [               ] /dev/nvme0n1p1 created and formated   (<string>:365)
(6925)    [5] [2024-02-22 11:43:21.961] [               ] Check winpe partition   (setup.py:1064)
(6926)    [5] [2024-02-22 11:43:21.962] [               ] Check winpe partition at number 2   (setup.py:1066)
(6927)    [5] [2024-02-22 11:43:21.963] [               ] Create winpe partition on /dev/nvme0n1p2 start: 484386M, size: 4000M   (<string>:263)
(7011)    [5] [2024-02-22 11:43:24.475] [               ] geometryLine : /dev/nvme0n1: 488386 cylinders, 64 heads, 32 sectors/track   (Posix.py:1557)
(7018)    [5] [2024-02-22 11:43:24.483] [               ] geometryLine : /dev/nvme0n1: 488386 cylinders, 64 heads, 32 sectors/track   (Posix.py:1557)
(7026)    [5] [2024-02-22 11:43:24.491] [               ] geometryLine : /dev/nvme0n1: 488386 cylinders, 64 heads, 32 sectors/track   (Posix.py:1557)
(7033)    [5] [2024-02-22 11:43:24.499] [               ] geometryLine : /dev/nvme0n1: 488386 cylinders, 64 heads, 32 sectors/track   (Posix.py:1557)
(7075)    [5] [2024-02-22 11:43:24.533] [               ] /dev/nvme0n1p2 exists as device - fine   (<string>:248)
(7076)    [5] [2024-02-22 11:43:24.541] [               ] Partition /dev/nvme0n1p2 has a correct block alignment   (<string>:154)
(7077)    [5] [2024-02-22 11:43:24.543] [               ] /dev/nvme0n1p2 exists as device - fine   (<string>:248)
(7078)    [5] [2024-02-22 11:43:24.550] [               ] Partition /dev/nvme0n1p2 has a correct block alignment   (<string>:154)
(7079)    [5] [2024-02-22 11:43:24.553] [               ] /dev/nvme0n1p2 is not mounted   (<string>:452)
(7080)    [5] [2024-02-22 11:43:24.553] [               ] Create file system ntfs on partition winpe (/dev/nvme0n1p2)   (<string>:339)
(7100)    [5] [2024-02-22 11:43:39.653] [               ] /dev/nvme0n1p2 exists as device - fine   (<string>:329)
(7101)    [5] [2024-02-22 11:43:39.653] [               ] /dev/nvme0n1p2 created and formated   (<string>:365)
(7102)    [5] [2024-02-22 11:43:39.653] [               ] Write Master Boot Record   (setup.py:1250)
(7147)    [5] [2024-02-22 11:43:46.735] [               ] collect disk and partition infos   (setup.py:1284)
[...]
(7170)    [5] [2024-02-22 11:43:46.739] [               ] we have uuid b2ca50aa on /dev/nvme0n1   (setup.py:1286)
(7178)    [5] [2024-02-22 11:43:46.755] [               ] We save all partition infos ....   (setup.py:1330)
(7179)    [5] [2024-02-22 11:43:46.755] [               ] Check if disk /dev/nvme0n1 is raid member   (<string>:129)
(7180)    [5] [2024-02-22 11:43:46.759] [               ] Disk /dev/nvme0n1 is no (Soft/Fake) Raid Member   (<string>:144)
[...]
(7203)    [5] [2024-02-22 11:43:46.760] [               ] Check if disk /dev/nvme0n1 is raid  HD   (<string>:97)
(7204)    [5] [2024-02-22 11:43:46.760] [               ] Disk /dev/nvme0n1 is no (Soft/Fake) Raid   (<string>:123)
(7221)    [5] [2024-02-22 11:43:46.767] [               ] has disk /dev/nvme0n1 a gpt partition table ?   (setup.py:1343)
(7222)    [5] [2024-02-22 11:43:46.771] [               ] disk /dev/nvme0n1 have no gpt partition table   (setup.py:1346)
(7223)    [5] [2024-02-22 11:43:46.771] [               ] We have 2 partitions on disk /dev/nvme0n1   (setup.py:1359)
(7224)    [4] [2024-02-22 11:43:46.775] [               ] Warning 'subprocess 913 is still running' in file 'subprocess.py', line 1072   (logging.py:848)
(7236)    [4] [2024-02-22 11:43:46.776] [               ] Warning 'unclosed file <_io.TextIOWrapper name=10 encoding='UTF-8'>' in file '/tmp/setup.py', line 1360   (logging.py:848)
(7246)    [5] [2024-02-22 11:43:46.776] [               ] We have uuid b2ca50aa  on disk /dev/nvme0n1   (setup.py:1361)
[...]
(7363)    [5] [2024-02-22 11:43:46.808] [               ] mount winpe partition   (setup.py:1416)
(7364)    [5] [2024-02-22 11:43:46.808] [               ] mountpoint /mnt/hd exists   (<string>:408)
(7365)    [5] [2024-02-22 11:43:46.808] [               ] mountpoint /mnt/hd >> /dev/null 2>&1   (<string>:413)
(7366)    [5] [2024-02-22 11:43:46.810] [               ] Nothing mounted on /mnt/hd - fine   (<string>:428)
(7367)    [5] [2024-02-22 11:43:46.811] [               ] /dev/nvme0n1p2 is not mounted   (<string>:452)
(7372)    [5] [2024-02-22 11:43:46.821] [               ]  mount -t ntfs /dev/nvme0n1p2 /mnt/hd   (<string>:468)
(7373)    [5] [2024-02-22 11:43:51.847] [               ] /dev/nvme0n1p2 mounted on /mnt/hd - fine..   (<string>:476)
(7842)    [5] [2024-02-22 11:44:01.256] [               ] we do not copy the uefi boot files because we are not in uefi mode   (setup.py:1426)
[...]
(8467)    [5] [2024-02-22 11:44:06.274] [               ] installing drivers from win10-x64-bls/drivers   (setup.py:1498)
[...]
(12168)   [5] [2024-02-22 11:45:04.474] [               ] Creating work.cmd   (setup.py:1508)
(12504)   [5] [2024-02-22 11:45:05.183] [               ] Adding found driver c:\drv\53\oem203.inf to drvloadlist_org.txt
   (setup.py:1559)
(12524)   [5] [2024-02-22 11:45:05.219] [               ] Here comes the /mnt/hd/opsi/drvloadlist_org.txt   (setup.py:1567)
(12536)   [5] [2024-02-22 11:45:05.274] [               ] Creating startnet.cmd   (setup.py:1611)
(12537)   [5] [2024-02-22 11:45:05.275] [               ] Creating diskpart.txt to delete winpe   (setup.py:1643)
(12538)   [5] [2024-02-22 11:45:05.275] [               ] No Partition IDs to backup - do not create /mnt/hd/opsi/partunhide.txt   (setup.py:1686)
(12539)   [5] [2024-02-22 11:45:05.275] [               ] No Partition IDs to backup - do not create /mnt/hd/opsi/parthide.txt   (setup.py:1707)
(12540)   [5] [2024-02-22 11:45:05.275] [               ] write disk and partition infos to /mnt/hd/opsi/diskinfo.ini   (setup.py:1713)
(12541)   [5] [2024-02-22 11:45:05.275] [               ] Here comes the /mnt/hd/opsi/diskinfo.ini   (setup.py:1718)
(12580)   [5] [2024-02-22 11:45:05.291] [               ] Creating opsi-script-infos.ini   (setup.py:1728)
(12581)   [5] [2024-02-22 11:45:05.292] [               ] Patching unattend.xml and config.ini   (setup.py:1752)
(12642)   [5] [2024-02-22 11:45:06.623] [               ] Here comes the unattend.xml    (setup.py:1758)
(12893)   [5] [2024-02-22 11:45:06.640] [               ] Reading config.ini data: config_service.url: https://172.20.21.4:4447/rpc    (setup.py:1775)
(12894)   [5] [2024-02-22 11:45:06.640] [               ]  config_service.url from clientconfig: https://172.20.21.4:4447/rpc    (setup.py:1776)
(12951)   [5] [2024-02-22 11:45:07.079] [               ] diskcounter is still 0   (setup.py:1833)
(12952)   [5] [2024-02-22 11:45:07.079] [               ] Set to setup bls_gen-local-admin-pw   (<string>:1115)
(12956)   [5] [2024-02-22 11:45:07.243] [               ] Set to setup windomain-bls   (<string>:1115)
(12962)   [5] [2024-02-22 11:45:07.464] [               ] Script execution successful   (run-master:2033)
(13316)   [5] [2024-02-22 11:45:07.521] [               ] Writing log to service   (run-master:2107)

Wenn man Windows mit einem USB-Stick installiert funktioniert es, er erkennt dann auch die Platte usw.

Was geht hier schief? Die Zeile

Code: Alles auswählen

(7842)    [5] [2024-02-22 11:44:01.256] [               ] we do not copy the uefi boot files because we are not in uefi mode   (setup.py:1426)

macht mich außerdem recht stutzig, weil es hier ja eben doch ein UEFI-System ist; der Haken "Uefi Boot" beim Client ist auch gesetzt.

Hat dazu jemand eine Idee?
Danke!

[m.radtke]

Hi

Schuss ins Blaue: updated mal das netboot Paket. Vor vielen Monaten gab es da eine Änderung wie im Bootimage erkannt wird ob die Maschine im UEFI Modus ist oder nicht und der alte Weg funktioniert so nicht mehr.

Gruß
Mathias

[plnb]

Hallo Matthias,
das wars, jetzt läuft die Installation wieder wie gewünscht durch!
1000 Dank dafür

Wir setzen zwei netboot-Produkte ein, eins heißt win10-x64 und erhält entsprechend automatisch Updates, wenn ich das richtig verstehe; das andere heißt win10-x64-name und hat die Updates so nicht bekommen. Gibt es die Möglichkeit hier ein automatisches Update zu konfigurieren? Die Files aus dem win10-x64-Produkt, auf dem das aufbaut könnten ja eigentlich einfach drüber kopiert werden...

Eine Scriptlösung wäre natürlich machbar, aber gibt es da vlt. irgend einen buildin-Mechanismus?

Gruß, Patrick

[SisterOfMercy]

Wir setzen zwei netboot-Produkte ein, eins heißt win10-x64 und erhält entsprechend automatisch Updates, wenn ich das richtig verstehe; das andere heißt win10-x64-name und hat die Updates so nicht bekommen. Gibt es die Möglichkeit hier ein automatisches Update zu konfigurieren? Die Files aus dem win10-x64-Produkt, auf dem das aufbaut könnten ja eigentlich einfach drüber kopiert werden...

Why do you use this solution?

[plnb]

Why do you use this solution?

Because we supply two different domains with it.

[SisterOfMercy]

Because we supply two different domains with it.

Now, why would you need two different windows netboot products for two different domains?
If you are deploying a different version of windows, say 22h2 and some ltsc version, you can easily do this with one netboot product, by changing the imagename and installfiles_dir product property.