Skip to main content

PXE boot sometimes hangs on "Reading all physical volumes. This may take a while..."

Thread needs solution
Beginner
Posts: 1
Comments: 4

Details:"

Closed Network. No outside access, only used for imaging. Two Cisco Switches. One switch is the DHCP server. Acronis Management /OS Deploy/ PXE server is a Windows 10 workstation. Acronis v. 5.02,028.

 All imaging devices are Windows 10 tablets, all hardware is the same. When booting from PXE 10/15 successfully boot into the Acronis Snap Deploy Agent. The remaining ones hang on the message "Reading all physical volumes. This may take a while..." We have waited over 7 days and still no booting. We have rebooted and same thing. Sometimes 1-2 will boot with an APIPA address which does us no good. On reboot, it hangs again on the message. A support case, 04796976, was opened. The tech added The Master Creator Image and System Report to the PXE booting and advised us to keep rebooting until the machines load the agent. One did successfully load but we are still left with three which refuse to load. We also do not want to have to load additional components in the PXE boot that we do not use since it requires an additional step to manually select. Any suggestions? We are needing this to be a full scale solution for our company...

0 Users found this helpful
Forum Support specialist
Posts: 0
Comments: 1748

Hello Andrea,

Welcome to Acronis forums!

Have you followed the troubleshooting steps listed in this KB article https://kb.acronis.com/content/47134 ?

Beginner
Posts: 1
Comments: 4

Yes...all those steps are have been checked and tried. The devices successfully see the PXE boot media, download the NBP file from the PXE server and move to the black screen and just hangs there.. The PXE server only has the Acronis Snap Deploy agent installed as the bootable component. 

Beginner
Posts: 1
Comments: 4

Here's the packet capture... once the client goes to the "Loading please wait..." the TFTP between server and client drop. 192.168.99.1 = Cisco SG-350 Switch w/DHCP server enabled. 192.168.99.5 = PXE Client. 192.168.99.9 = Acronis OS Server, PXE server, License server, etc. I have tried with a different DHCP server and an unmanaged switch and still the same results. 

 
No.    Time    Source    Destination    Protocol    Length    Info
167797    428.820784    192.168.99.9    192.168.99.5    TFTP    1474    Data Packet, Block: 59241
167798    428.821039    192.168.99.5    192.168.99.9    TFTP    60    Acknowledgement, Block: 59241
167799    428.821107    192.168.99.9    192.168.99.5    TFTP    1474    Data Packet, Block: 59242
167800    428.821361    192.168.99.5    192.168.99.9    TFTP    60    Acknowledgement, Block: 59242
167801    428.821441    192.168.99.9    192.168.99.5    TFTP    1368    Data Packet, Block: 59243 (last)
167802    428.821693    192.168.99.5    192.168.99.9    TFTP    60    Acknowledgement, Block: 59243
167803    428.824098    192.168.99.5    192.168.99.9    TFTP    81    Read Request, File: FED7E0F07, Transfer type: octet, tsize=0, blksize=1428
167804    428.826622    192.168.99.9    192.168.99.5    TFTP    67    Option Acknowledgement, blksize=1428, tsize=371
167805    428.826866    192.168.99.5    192.168.99.9    TFTP    72    Error Code, Code: Option negotiation failed, Message: User aborted the transfer
167806    428.829609    192.168.99.5    192.168.99.9    TFTP    73    Read Request, File: FED7E0F07, Transfer type: octet, blksize=1428
167807    428.832248    192.168.99.9    192.168.99.5    TFTP    57    Option Acknowledgement, blksize=1428
167808    428.832566    192.168.99.5    192.168.99.9    TFTP    60    Acknowledgement, Block: 0
167809    428.832740    192.168.99.9    192.168.99.5    TFTP    417    Data Packet, Block: 1 (last)
167810    428.833324    192.168.99.5    192.168.99.9    TFTP    60    Acknowledgement, Block: 1
167811    430.781766    Cisco_8d:d8:c6    Broadcast    ARP    60    Who has 192.168.99.6? Tell 192.168.99.1
167812    433.082289    Cisco_8d:d8:c6    Broadcast    ARP    60    Who has 192.168.99.6? Tell 192.168.99.1
167813    435.081634    Cisco_8d:d8:c6    Broadcast    ARP    60    Who has 192.168.99.6? Tell 192.168.99.1
167814    437.032322    fe80::568a:baff:fe8d:d8c6    ff02::1:2    DHCPv6    108    Information-request XID: 0xa304ba CID: 00030001548aba8dd8c6 
167815    438.351184    192.168.99.9    192.168.99.1    HTTP    922    GET /cs4dae4a75/mts/polling/wcd?{MemoryLogTable&count=10&filter=(logNo%3C2147483600)} HTTP/1.1 
167816    438.353067    Cisco_8d:d8:c6    Broadcast    ARP    60    Who has 192.168.99.9? Tell 192.168.99.1
167817    438.353075    Dell_2a:a2:56    Cisco_8d:d8:c6    ARP    42    192.168.99.9 is at a4:4c:c8:2a:a2:56
167818    438.353924    192.168.99.9    192.168.99.255    NBNS    92    Name query NB WPAD<00>
167819    438.354106    192.168.99.9    224.0.0.251    MDNS    70    Standard query 0x0000 A wpad.local, "QM" question
167820    438.354444    192.168.99.9    224.0.0.251    MDNS    70    Standard query 0x0000 AAAA wpad.local, "QM" question
167821    438.355641    192.168.99.1    192.168.99.9    TCP    60    80 → 52662 [ACK] Seq=11129 Ack=6653 Win=2360 Len=0
167822    438.359608    192.168.99.1    192.168.99.9    TCP    60    [TCP Window Update] 80 → 52662 [ACK] Seq=11129 Ack=6653 Win=4096 Len=0
167823    438.363020    192.168.99.1    192.168.99.9    TCP    316    80 → 52662 [PSH, ACK] Seq=11129 Ack=6653 Win=4096 Len=262 [TCP segment of a reassembled PDU]
167824    438.410077    192.168.99.9    192.168.99.1    TCP    54    52662 → 80 [ACK] Seq=6653 Ack=11391 Win=64800 Len=0
167825    438.427810    192.168.99.1    192.168.99.9    HTTP/XML    352    HTTP/1.1 200 OK 
167826    438.472612    192.168.99.9    192.168.99.1    TCP    54    52662 → 80 [ACK] Seq=6653 Ack=11689 Win=64502 Len=0
167827    439.118353    192.168.99.9    192.168.99.255    NBNS    92    Name query NB WPAD<00>
167828    439.368914    192.168.99.9    224.0.0.251    MDNS    70    Standard query 0x0000 AAAA wpad.local, "QM" question
167829    439.369204    192.168.99.9    224.0.0.251    MDNS    70    Standard query 0x0000 A wpad.local, "QM" question
167830    439.871101    192.168.99.9    192.168.99.255    NBNS    92    Name query NB WPAD<00>
167831    440.881973    Cisco_8d:d8:cf    LLDP_Multicast    LLDP    126    MA/54:8a:ba:8d:d8:c6 MA/54:8a:ba:8d:d8:cf 120 SysN=switch8dd8c6 
167832    441.354262    192.168.99.9    192.168.99.1    HTTP    862    GET /cs4dae4a75/mts/device/timestamp_mib.xml?[rlEventsMaskTableVT]Query:rlEventsMaskPollerId=3 HTTP/1.1 
167833    441.355735    192.168.99.1    192.168.99.9    TCP    60    80 → 52662 [ACK] Seq=11689 Ack=7461 Win=3288 Len=0
167834    441.373421    192.168.99.1    192.168.99.9    TCP    316    80 → 52662 [PSH, ACK] Seq=11689 Ack=7461 Win=3288 Len=262 [TCP segment of a reassembled PDU]
167835    441.376844    192.168.99.1    192.168.99.9    TCP    1484    80 → 52662 [ACK] Seq=11951 Ack=7461 Win=3288 Len=1430 [TCP segment of a reassembled PDU]
167836    441.376844    192.168.99.1    192.168.99.9    HTTP/XML    560    HTTP/1.1 200 OK 
167837    441.376925    192.168.99.9    192.168.99.1    TCP    54    52662 → 80 [ACK] Seq=7461 Ack=13887 Win=64800 Len=0
167838    441.382481    192.168.99.9    192.168.99.1    HTTP    806    GET /cs4dae4a75/mts/device/labeldb.xml HTTP/1.1 
167839    441.382793    192.168.99.9    192.168.99.1    TCP    66    52684 → 80 [SYN] Seq=0 Win=64240 Len=0 MSS=1460 WS=256 SACK_PERM=1
167840    441.382940    192.168.99.9    192.168.99.1    HTTP    806    GET /cs4dae4a75/mts/device/nostamp.xml HTTP/1.1 
167841    441.386228    192.168.99.1    192.168.99.9    TCP    60    80 → 52684 [SYN, ACK] Seq=0 Ack=1 Win=4096 Len=0 MSS=1440
167842    441.386267    192.168.99.9    192.168.99.1    TCP    54    52684 → 80 [ACK] Seq=1 Ack=1 Win=64240 Len=0
167843    441.386634    192.168.99.9    192.168.99.1    HTTP    816    GET /cs4dae4a75/mts/device/authenticate_user.xml HTTP/1.1 
167844    441.388223    192.168.99.1    192.168.99.9    TCP    60    80 → 52661 [ACK] Seq=8889 Ack=3065 Win=2592 Len=0
167845    441.389687    192.168.99.1    192.168.99.9    TCP    60    80 → 52662 [ACK] Seq=13887 Ack=8213 Win=4096 Len=0
167846    441.406098    192.168.99.1    192.168.99.9    TCP    316    80 → 52662 [PSH, ACK] Seq=13887 Ack=8213 Win=4096 Len=262 [TCP segment of a reassembled PDU]
167847    441.422621    192.168.99.1    192.168.99.9    TCP    1484    80 → 52662 [ACK] Seq=14149 Ack=8213 Win=4096 Len=1430 [TCP segment of a reassembled PDU]
167848    441.422621    192.168.99.1    192.168.99.9    TCP    624    80 → 52662 [PSH, ACK] Seq=15579 Ack=8213 Win=4096 Len=570 [TCP segment of a reassembled PDU]
167849    441.422675    192.168.99.9    192.168.99.1    TCP    54    52662 → 80 [ACK] Seq=8213 Ack=16149 Win=64800 Len=0
167850    441.441328    192.168.99.1    192.168.99.9    TCP    1054    80 → 52662 [PSH, ACK] Seq=16149 Ack=8213 Win=4096 Len=1000 [TCP segment of a reassembled PDU]
167851    441.441379    192.168.99.9    192.168.99.1    TCP    54    52662 → 80 [ACK] Seq=8213 Ack=17149 Win=63800 Len=0
167852    441.455947    192.168.99.1    192.168.99.9    TCP    1054    80 → 52662 [PSH, ACK] Seq=17149 Ack=8213 Win=4096 Len=1000 [TCP segment of a reassembled PDU]
167853    441.460477    192.168.99.1    192.168.99.9    TCP    60    [TCP Window Update] 80 → 52661 [ACK] Seq=8889 Ack=3065 Win=4096 Len=0
167854    441.476890    192.168.99.1    192.168.99.9    TCP    316    80 → 52661 [PSH, ACK] Seq=8889 Ack=3065 Win=4096 Len=262 [TCP segment of a reassembled PDU]
167855    441.483159    192.168.99.1    192.168.99.9    TCP    1484    80 → 52661 [ACK] Seq=9151 Ack=3065 Win=4096 Len=1430 [TCP segment of a reassembled PDU]
167856    441.483211    192.168.99.9    192.168.99.1    TCP    54    52661 → 80 [ACK] Seq=3065 Ack=10581 Win=64800 Len=0
167857    441.483353    192.168.99.1    192.168.99.9    HTTP/XML    575    HTTP/1.1 200 OK 
167858    441.488228    192.168.99.1    192.168.99.9    TCP    648    80 → 52684 [PSH, ACK] Seq=1 Ack=763 Win=3334 Len=594 [TCP segment of a reassembled PDU]
167859    441.507687    192.168.99.9    192.168.99.1    TCP    54    52662 → 80 [ACK] Seq=8213 Ack=18149 Win=64800 Len=0
167860    441.509263    192.168.99.1    192.168.99.9    HTTP/XML    269    HTTP/1.1 200 OK 
167861    441.538271    192.168.99.9    192.168.99.1    TCP    54    52684 → 80 [ACK] Seq=763 Ack=595 Win=63646 Len=0
167862    441.538271    192.168.99.9    192.168.99.1    TCP    54    52661 → 80 [ACK] Seq=3065 Ack=11102 Win=64279 Len=0
167863    441.539955    192.168.99.1    192.168.99.9    HTTP/XML    60    HTTP/1.1 200 OK 
167864    441.540025    192.168.99.9    192.168.99.1    TCP    54    52684 → 80 [ACK] Seq=763 Ack=596 Win=63646 Len=0
167865    441.540223    192.168.99.9    192.168.99.1    TCP    54    52684 → 80 [FIN, ACK] Seq=763 Ack=596 Win=63646 Len=0
167866    441.542243    192.168.99.1    192.168.99.9    TCP    60    80 → 52684 [ACK] Seq=596 Ack=764 Win=3334 Len=0
167867    441.553424    192.168.99.9    192.168.99.1    TCP    54    52662 → 80 [ACK] Seq=8213 Ack=18364 Win=64585 Len=0
167868    443.482361    Cisco_8d:d8:c6    Broadcast    ARP    60    Who has 192.168.99.6? Tell 192.168.99.1
167869    445.482861    Cisco_8d:d8:c6    Broadcast    ARP    60    Who has 192.168.99.6? Tell 192.168.99.1
167870    448.271546    Cisco_8d:d8:c6    Broadcast    ARP    60    Who has 192.168.99.6? Tell 192.168.99.1
167871    449.366642    192.168.99.9    192.168.99.1    HTTP    922    GET /cs4dae4a75/mts/polling/wcd?{MemoryLogTable&count=10&filter=(logNo%3C2147483600)} HTTP/1.1 
167872    449.368215    Cisco_8d:d8:c6    Broadcast    ARP    60    Who has 192.168.99.9? Tell 192.168.99.1
167873    449.368223    Dell_2a:a2:56    Cisco_8d:d8:c6    ARP    42    192.168.99.9 is at a4:4c:c8:2a:a2:56
167874    449.369488    192.168.99.1    192.168.99.9    TCP    60    80 → 52662 [ACK] Seq=18364 Ack=9081 Win=3228 Len=0
167875    449.375502    192.168.99.1    192.168.99.9    TCP    316    80 → 52662 [PSH, ACK] Seq=18364 Ack=9081 Win=3228 Len=262 [TCP segment of a reassembled PDU]
167876    449.423837    192.168.99.9    192.168.99.1    TCP    54    52662 → 80 [ACK] Seq=9081 Ack=18626 Win=64323 Len=0
167877    449.439685    192.168.99.1    192.168.99.9    HTTP/XML    352    HTTP/1.1 200 OK 
167878    449.487046    192.168.99.9    192.168.99.1    TCP    54    52662 → 80 [ACK] Seq=9081 Ack=18924 Win=64025 Len=0
167879    451.151483    Cisco_8d:d8:c6    Broadcast    ARP    60    Who has 192.168.99.6? Tell 192.168.99.1
167880    453.963577    0.0.0.0    255.255.255.255    DHCP    324    DHCP Discover - Transaction ID 0x2b0f951b
167881    453.980442    0.0.0.0    255.255.255.255    DHCP    336    DHCP Request  - Transaction ID 0x2b0f951b
167882    457.022485    0.0.0.0    255.255.255.255    DHCP    324    DHCP Discover - Transaction ID 0x798c4271
167883    457.039647    0.0.0.0    255.255.255.255    DHCP    336    DHCP Request  - Transaction ID 0x798c4271
167884    460.083324    0.0.0.0    255.255.255.255    DHCP    324    DHCP Discover - Transaction ID 0x5a3d6c78
167885    460.100469    0.0.0.0    255.255.255.255    DHCP    336    DHCP Request  - Transaction ID 0x5a3d6c78
167886    460.356760    192.168.99.9    192.168.99.1    HTTP    922    GET /cs4dae4a75/mts/polling/wcd?{MemoryLogTable&count=10&filter=(logNo%3C2147483600)} HTTP/1.1 
167887    460.358810    Cisco_8d:d8:c6    Broadcast    ARP    60    Who has 192.168.99.9? Tell 192.168.99.1
167888    460.358821    Dell_2a:a2:56    Cisco_8d:d8:c6    ARP    42    192.168.99.9 is at a4:4c:c8:2a:a2:56
167889    460.359977    192.168.99.1    192.168.99.9    TCP    60    80 → 52662 [ACK] Seq=18924 Ack=9949 Win=2360 Len=0
 
Beginner
Posts: 1
Comments: 4

Created a basic PE image and it still hangs before failing. Wireshark shows TFTP data is being passed and then POOF....

 

Source    Destination    Protocol    Length    Info
192.168.99.5    192.168.99.9    TFTP    60    Acknowledgement, Block: 215710
192.168.99.9    192.168.99.5    TFTP    1453    Data Packet, Block: 215711 (last)
192.168.99.5    192.168.99.9    TFTP    60    Acknowledgement, Block: 215711
192.168.99.5    192.168.99.9    TFTP    103    Read Request, File: \EFI\Microsoft\Boot\Policies\UnlockToken.pol, Transfer type: octet, tsize=0
192.168.99.9    192.168.99.5    TFTP    63    Error Code, Code: File not found, Message: 
192.168.99.9    192.168.99.5    TFTP    61    Error Code, Code: File not found, Message: File not found
    Cisco_8d:d8:ce    LLDP_Multicast    LLDP    142    MA/54:8a:ba:8d:d8:c6 MA/54:8a:ba:8d:d8:ce 120 SysN=switch8dd8c6 

Cisco_8d:d8:ce    CDP/VTP/DTP/PAgP/UDLD    CDP    191    Device ID: 548aba8dd8c6  Port ID: gi8  
 

Forum Moderator
Posts: 187
Comments: 6088

Hello Andrea,

at this point I'd recommend opening a support ticket for the more in-depth investigation. Please let me know if you need any assistance with raising a ticket. 
If you've already contacted support, we'd be grateful for sharing the outcome with the community!