PC Recovery After Disk Crash
PC Recovery After Disk Crash
Section titled “PC Recovery After Disk Crash”The disk broke or Windows won’t load — the algorithm depends on how serious the problem is. In most cases, deploying the reference image via IZI Boot is sufficient. If the disk is physically dead — replace first, then image.
This page is an emergency guide. Before reading, make sure you have a current image on the NAS or in the cloud — without it, fast recovery is impossible.
Diagnosis: Determine the Cause
Section titled “Diagnosis: Determine the Cause”Before acting, determine what exactly broke.
| Symptom | Likely Cause | Recovery Path |
|---|---|---|
| PC powers on but Windows won’t load (blue screen, “Disk boot failure”) | OS damaged, boot sectors damaged | Deploy image via PXE or USB |
| PC powers on, IZI client does not start | Agent damaged or removed | Reinstall the IZI client |
| PC won’t power on at all | Hardware problem (power, RAM, motherboard) | Hardware diagnostics |
| Clicking/grinding sounds from disk during operation | Mechanical HDD failure | Replace disk, then image |
| PC powers on but disk not visible in BIOS | Physical drive failure | Replace disk, then image |
| PC froze mid-session, reboot loop after restart | FS corruption from forced shutdown | Deploy image |
Path A: Recovery via PXE (Recommended with IZI Boot Configured)
Section titled “Path A: Recovery via PXE (Recommended with IZI Boot Configured)”If PXE is configured and NAS is available — this is the fastest path. No physical access to the PC required.
Step 1. Verify the PC in CRM
Section titled “Step 1. Verify the PC in CRM”Open the Devices section in the CRM. Find the PC. If it’s showing “Offline” — that’s normal with a broken system.
Note the device UUID — you’ll need it after recovery.
Step 2. Power On the PC (WoL or Physically)
Section titled “Step 2. Power On the PC (WoL or Physically)”If Wake-on-LAN is configured — power on the PC from the CRM: Hall section → device card → Power On.
If WoL is not configured — press the power button physically.
Step 3. PC Boots Over the Network
Section titled “Step 3. PC Boots Over the Network”With PXE properly configured, the PC — finding no working OS on disk — automatically boots over the network from the IZI Boot Recovery environment.
If the PC doesn’t boot over the network — check BIOS: boot order must include “Network Boot” or “PXE Boot.”
Step 4. Deploy the Image
Section titled “Step 4. Deploy the Image”In the IZI Boot Recovery environment:
- Select the recovery image from the list (images are pulled from NAS automatically).
- Confirm deployment — all data on the disk will be overwritten with the image.
- Wait for completion — 15–30 minutes with Gigabit Ethernet and image on NAS.
Step 5. Enter UUID on First Start
Section titled “Step 5. Enter UUID on First Start”After deployment, the PC reboots and Windows starts. the IZI client asks for the device UUID — enter the UUID from the CRM (Step 1).
The PC will appear in the Devices section with “Active” status.
Step 6. Verify Operation
Section titled “Step 6. Verify Operation”- Launch a test session in the Hall section
- Verify that several games launch
- Check that disk protection is enabled (shield icon is green)
Path B: Recovery via USB (PXE Not Configured)
Section titled “Path B: Recovery via USB (PXE Not Configured)”If PXE is not configured — use a bootable USB drive.
Step 1. Prepare the IZI Boot Recovery USB
Section titled “Step 1. Prepare the IZI Boot Recovery USB”On a working PC, create a bootable IZI Boot Recovery USB — the tool is available in Devices → Download → IZI Boot Recovery USB. USB drive of 8 GB or more.
Step 2. Boot from the USB
Section titled “Step 2. Boot from the USB”Insert the USB into the broken PC. In BIOS, select USB boot (typically F8, F11, or F12 at startup for boot device selection — depends on motherboard manufacturer).
Step 3. Specify the Image Source
Section titled “Step 3. Specify the Image Source”In the IZI Boot Recovery menu, specify the image path:
- SMB (NAS): enter the NAS address and path to the images folder
- Local on USB: if the image was copied to the USB in advance
Steps 4–6 — Same as Path A
Section titled “Steps 4–6 — Same as Path A”Wait for deployment, enter UUID, verify operation.
Path C: Physical Disk Replacement
Section titled “Path C: Physical Disk Replacement”If the disk is mechanically dead (clicking sounds, not visible in BIOS) — replace the drive first, then follow Path A or B.
Step 1. Replace the Drive
Section titled “Step 1. Replace the Drive”Power off the PC, remove the failed disk, install a new one. The drive type (SATA SSD, NVMe M.2) must match the connector on the motherboard.
Step 2. Boot via PXE or USB
Section titled “Step 2. Boot via PXE or USB”The new disk contains nothing — use PXE (Path A) or USB (Path B) to deploy the image.
Steps 3–5 — Same as Paths A/B
Section titled “Steps 3–5 — Same as Paths A/B”After image deployment, the PC works as if nothing happened — UUID is preserved in the CRM.
Prevention: How to Reduce Downtime During Emergencies
Section titled “Prevention: How to Reduce Downtime During Emergencies”- Always keep a current image on the NAS — an outdated image loses games installed over the past months
- Configure PXE on all PCs during initial setup — takes 5 minutes per machine
- Enable WoL — recovery without physical access to the machine
- Monitor: Real-Time PC Monitoring shows disk degradation before failure
Related
Section titled “Related”- IZI Boot: What It Is and How It Works — PXE and image mechanism
- Reference Image: Creation, Maintenance, Updates — how to keep the image current
- Real-Time PC Monitoring — early signs of disk problems
- Disk Protection
See Also
Section titled “See Also”Frequently asked questions
The PC won't boot — how do I tell if it's the disk or something else?
Try booting from a USB drive with a live system (e.g., Hiren's BootCD or Ubuntu Live). If the USB boots — the problem is the disk or Windows. If USB doesn't boot — hardware problem (RAM, motherboard, power). Additional sign of a disk problem: clicking or grinding sounds when the PC powers on.
I have an image but PXE is not configured — how do I recover?
Create a bootable USB drive with the IZI Boot Recovery tool. Boot the PC from the USB, specify the path to the image on the NAS or copy the image to the USB. Details — in the IZI emergency recovery documentation.
After recovery the PC doesn't appear in the CRM — why?
The image contains the IZI client configuration, but the device UUID is stored in the CRM. After deploying the image, enter the UUID of this specific PC on first launch. If you don't remember the UUID — find it in the CRM Devices section → PC card.
Can I recover a PC without a NAS — image is only in the cloud?
Yes, but it takes longer. Over a 100 Mbps connection, a 50 GB image deploys in 1–2 hours. Make sure the internet channel isn't occupied by other PCs during recovery — otherwise it takes even longer.
Do I need to re-pair the PC with the CRM after replacing the disk?
The UUID in IZI is tied to the device in the CRM, not the physical disk. After replacing the disk and deploying the image, the PC registers with the same UUID — no additional CRM actions needed.