wir haben brandneue HP ProBook 450 G9 in zwei verschiedenen Varianten:
- P/N 4D3W9AV (CPU: 12th Gen Intel(R) Core(TM) i3-1215U)
- P/N 674N0AV (CPU: 12th Gen Intel(R) Core(TM) i5-1235U)
Code: Alles auswählen
(11384) [6] [2022-07-22 13:52:17.437] [ ] Executing: /bin/efibootmgr -v (Posix.py:980)
(11385) [6] [2022-07-22 13:52:17.438] [ ] Using encoding 'UTF-8' (Posix.py:1007)
(11386) [7] [2022-07-22 13:52:18.596] [ ] >>> BootCurrent: 0001 (Posix.py:1053)
(11387) [7] [2022-07-22 13:52:18.596] [ ] >>> Timeout: 0 seconds (Posix.py:1053)
(11388) [7] [2022-07-22 13:52:18.596] [ ] >>> BootOrder: 0001,0000,0003,0004,0005,0002 (Posix.py:1053)
(11389) [7] [2022-07-22 13:52:18.596] [ ] >>> Boot0000* SAMSUNG MZVLQ256HBJD-00BH1-S672NS0T562680 PciRoot(0x0)/Pci(0x6,0x2)/Pci(0x0,0x0)/NVMe(0x1,00-25-38-D5-21-44-FE-D0)N.....YM....R,Y.....ISPH (Posix.py:1053)
(11390) [7] [2022-07-22 13:52:18.596] [ ] >>> Boot0001* IPV4 Network - Realtek PCIe GBE Family Controller PciRoot(0x0)/Pci(0x1c,0x7)/Pci(0x0,0x0)/MAC(5c60ba5fdd74,0)/IPv4(0.0.0.00.0.0.0,0,0)N.....YM....R,Y.....ISPH (Posix.py:1053)
(11391) [7] [2022-07-22 13:52:18.597] [ ] >>> Boot0002* IPV6 Network - Realtek PCIe GBE Family Controller PciRoot(0x0)/Pci(0x1c,0x7)/Pci(0x0,0x0)/MAC(5c60ba5fdd74,0)/IPv6([::]:<->[::]:,0,0)N.....YM....R,Y.....ISPH (Posix.py:1053)
(11392) [7] [2022-07-22 13:52:18.597] [ ] >>> Boot0003 USB: PciRoot(0x0)/Pci(0x14,0x0)N.....YM....R,Y.....ISPH (Posix.py:1053)
(11393) [7] [2022-07-22 13:52:18.597] [ ] >>> Boot0004 USB NETWORK BOOT: PciRoot(0x0)/Pci(0x0,0x0)/IPv4(0.0.0.00.0.0.0,0,0)N.....YM....R,Y.....ISPH (Posix.py:1053)
(11394) [7] [2022-07-22 13:52:18.597] [ ] >>> Boot0005 USB NETWORK BOOT: PciRoot(0x0)/Pci(0x0,0x0)/IPv6([::]:<->[::]:,0,0)N.....YM....R,Y.....ISPH (Posix.py:1053)
(11395) [7] [2022-07-22 13:52:18.597] [ ] >>> (Posix.py:1053)
(11396) [7] [2022-07-22 13:52:18.597] [ ] Exit code: 0 (Posix.py:1060)
(11397) [5] [2022-07-22 13:52:18.597] [ ] setting winpe to the top of winpe boot order (setup.py:1790)
(11398) [7] [2022-07-22 13:52:18.597] [ ] Removing LD_LIBRARY_PATH from env for subprocess (Posix.py:893)
(11399) [6] [2022-07-22 13:52:18.597] [ ] Executing: /bin/efibootmgr -c --disk /dev/nvme0n1 --part 5 -L opsitempwinpe --loader \\EFI\\boot\\bootx64.efi (Posix.py:980)
(11400) [6] [2022-07-22 13:52:18.598] [ ] Using encoding 'UTF-8' (Posix.py:1007)
(11401) [7] [2022-07-22 13:52:19.444] [ ] >>> Could not prepare Boot variable: Invalid argument (Posix.py:1053)
(11402) [7] [2022-07-22 13:52:19.444] [ ] >>> (Posix.py:1053)
(11403) [7] [2022-07-22 13:52:19.444] [ ] Exit code: 5 (Posix.py:1060)
(11404) [2] [2022-07-22 13:52:20.448] [ ] Command '/bin/efibootmgr -c --disk /dev/nvme0n1 --part 5 -L opsitempwinpe --loader \\EFI\\boot\\bootx64.efi' failed (5):
(11405) Could not prepare Boot variable: Invalid argument
(11406) (Logger.py:344)
(11407) Traceback (most recent call last):
(11408) File "run-master", line 1683, in <module>
(11409) File "/tmp/setup.py", line 1806, in <module>
(11410) execute('/bin/efibootmgr -c --disk %s --part %s -L opsitempwinpe --loader \\\\EFI\\\\boot\\\\bootx64.efi' % (disk.device, winpePartitionNumber))
(11411) File "OPSI/System/Posix.py", line 1068, in execute
(11412) RuntimeError: Command '/bin/efibootmgr -c --disk /dev/nvme0n1 --part 5 -L opsitempwinpe --loader \\EFI\\boot\\bootx64.efi' failed (5):
(11413) Could not prepare Boot variable: Invalid argument
(11414)
(11415) [7] [2022-07-22 13:52:20.449] [ ] Backend: <JSONRPCBackend()> (run-master:1738)
(11416) [7] [2022-07-22 13:52:20.449] [ ] ProductId: win10-x64 (run-master:1739)
(11417) [7] [2022-07-22 13:52:20.449] [ ] ClientId: amt001455.amt.cic.fldk.net (run-master:1740)
(11418) [7] [2022-07-22 13:52:20.449] [ ] ProductOnClient: <ProductOnClient(clientId='amt001455.amt.cic.fldk.net', productId='win10-x64', installationStatus='unknown', actionRequest='none')> (run-master:1741)
(11419) [6] [2022-07-22 13:52:20.449] [ ] Updating productOnClient: {'targetConfiguration': None, 'installationStatus': 'unknown', 'actionRequest': 'none', 'lastAction': None, 'actionProgress': '', 'actionResult': 'failed', 'productVersion': None, 'packageVersion': None, 'modificationTime': None, 'actionSequence': None, 'productId': 'win10-x64', 'productType': 'NetbootProduct', 'clientId': 'amt001455.amt.cic.fldk.net', 'type': 'ProductOnClient'} (run-master:1753)
(11420) [6] [2022-07-22 13:52:20.449] [ ] JSONRPC request to https://10.2.32.51:4447/rpc: ip_version=4, id=25, method=productOnClient_updateObjects, Content-Type=application/msgpack, Content-Encoding=lz4, timeout=(10, 300) (jsonrpc.py:429)
(11421) [7] [2022-07-22 13:52:20.450] [ ] Resetting dropped connection: 10.2.32.51 (connectionpool.py:273)
(11422) [7] [2022-07-22 13:52:20.450] [ ] Using ip version 4 (jsonrpc.py:240)
(11423) [7] [2022-07-22 13:52:20.473] [ ] https://10.2.32.51:4447 "POST /rpc HTTP/1.1" 200 25 (connectionpool.py:456)
(11424) [6] [2022-07-22 13:52:20.473] [ ] Got response status=200, Content-Type=application/msgpack, Content-Encoding=, duration=0.024s (jsonrpc.py:452)
(11425) [5] [2022-07-22 13:52:20.473] [ ] EXITING (run-master:1759)
(11426) [5] [2022-07-22 13:52:20.473] [ ] Writing log to service (run-master:1765)
Auffallend ist, dass in der "Hardware-Info" beim i5 keine Sektion "Festplatte" und keine Sektion "SCSI-Controller" zu finden ist. Beim i3 findet sich eine Festplatte ...
Code: Alles auswählen
Name SAMSUNG MZVLQ256HBJD-00BH1
Beschreibung Laufwerk
Hersteller (Standardlaufwerke)
Modell SAMSUNG MZVLQ256HBJD-00BH1
Seriennummer 0025_38D5_2145_28C9.
Größe 238.468 GByte
Cylinder 31130
Heads 255
Sektoren 500103450
Partitionen 3
Code: Alles auswählen
Name Standardmäßiger NVM Express-Controller
Beschreibung Standardmäßiger NVM Express-Controller
Hersteller Standardmäßiger NVM Express-Controller
Gerätetyp PCI
Hersteller-ID 144D
Geräte-ID A809
Subsystem-Hersteller-ID A801
Subsystem-Geräte-ID 144D
Revision 00
Viellleicht hilft ein neuerer Kernel was?
Gruß
kinzi