[Solved] Guide of Resolving VMWare Inaccessible Boot Device Error
Are you facing the frustrating VMWare inaccessible boot device error? This article discovers effective solutions to resolve this issue and get your virtual machine up and running smoothly.
The Error of VMware Inaccessible Boot Device
VMware Inaccessible Boot Device is an error encountered in virtualized environments running VMware software. When this error occurs, administrators are unable to access the boot device, leading to the inability to boot the virtual machine. This error often arises due to issues with drivers, particularly the failure to install the necessary driver for the VMware Virtual disk SCSI Disk Device.
What Should You Note When Fixing VMware Inaccessible Boot Device
- Backup data: Before attempting any troubleshooting steps, make sure to back up your virtual machine data.
- Follow a systematic approach: Approach the troubleshooting process in a systematic manner. Start with simple solutions, such as restarting the virtual machine, and gradually move towards more advanced troubleshooting steps if necessary.
- Verify configuration settings: Double-check the virtual machine's configuration settings, including the virtual disk and SCSI controller configuration.
- Stay up-to-date: Regularly check for updates, patches, and new releases provided by VMware, as they often contain bug fixes and enhancements that can resolve compatibility issues.
- Reinstall VMware Tools: Reinstall or update VMware Tools on the affected virtual machine.
- Validate storage connectivity: Verify the connectivity between the virtual machine and the storage where the virtual disk is located. Check for any connectivity issues or misconfigurations that might be causing the boot device to become inaccessible.
How to Fix VMware Inaccessible Boot Device Step by Step
After upgrading a Windows virtual machine's virtual hardware to version 7, you may see a blue screen error containing the message:
0x0000007B (inaccessible boot device)
1. Upgrade VMware Tools, then reboot to confirm that the upgrade is successful.
2. Take a snapshot of the virtual machine as a backup.
3. Power off the virtual machine, upgrade the virtual hardware, and power on the virtual machine.
4. Log in to the virtual machine. The drivers in the Device Manager are not installed automatically.
5. Open Explorer and go to C:\Windows\System32\drivers.
6. Change ownership from TrustedInstaller to Administrators for disk.sys and pci.sys, then add Administrators with Full control permissions to the ACL for these files.
7. Keep the Explorer window open and use a new one to navigate to C:\Windows\inf.
8. Use a third Explorer window to navigate to C:\Windows\System32\DriverStore\FileRepository.
There is a long list of folders there. You need the disk.inf_* and machine.info_* folders.
9. From the disk.inf_* folder, copy disk.inf to C:\Windows\inf.
10. From the disk.inf_* folder, copy disk.sys to C:\Windows\System32\drivers.
11. From the machine.inf_* folder, copy machine.inf to C:\Windows\inf.
12. From the machine.inf_* folder copy pci.sys to C:\Windows\System32\drivers.
13. Locate and install the driver software. Confirm in Device Management that the drivers have been successfully installed.
14. Update the driver for VMware Virtual disk SCSI Disk Device. Browse to C:\Windows\System32\DriverStore\FileRepository for a search including subfolders.
15. Repeat steps 2-15 for the other devices that are listed as Unknown device in the Device Manager.
16. Reboot the virtual machine.
Backing up your VM is essential and necessary. This ensures that your data remains safe in case any unforeseen issues occur during the fixing process.
The centralized VMware backup software - AOMEI Cyber Backup supports VMware ESXi 6.0 and later versions. It contains more useful features to relieve your burden, such as scheduled backup, centralized management, full or incremental option, etc.
AOMEI Cyber Backup supports not only virtual machine backup but also SQL Server database backup.
Agentless Backup: Create complete and independent image-level backup for VMware ESXi VMs.
Role Assignment: Allows one administrator to create sub-accounts with limited privileges.
Email Notification: Send email notification when the task is completed or abnormal.
Multiple Storage Destinations: Back up to local folders or NAS (folders shared via the SMB protocol).
Automated Execution: Automate virtual machine protection and notified by email.
Restore from Any Point: Restore entire VM from any backed up restore points.
*You can choose to install this VM backup software on either Windows or Linux system.
How to Automate VM Backup Using AOMEI Cyber Backup
1. Bind Devices: Launch AOMEI Cyber Backup web client, navigate to Source Device > VMware > + Add VMware Device to add vCenter or Standalone ESXi host as the source device. And then click … > Bind Device.
2. Create Backup Task: Navigate to Backup Task > + Create New Task, and then set it up according to your needs.
- Device: cover multiple VMs on the host in one backup task.
- Target: selecting to back up to a local path, or to a network path. Used paths will be saved in Favorite Storage for handy selection.
- Schedule: choosing to perform full, differential or incremental backup, and automate execution daily, weekly or monthly according to the frequency you specified.
- Backup cleanup: Configure a retention policy to auto delete old backup files and save storage space.
3. Start Backup: Click Start Backup and select Add the schedule and start backup now or Add the schedule only.
Created backup tasks will be listed and monitored separately for progress checking, editing and restoring.
This article introduces how to overcome the VMWare Inaccessible Boot Device error and ensure seamless virtual machine operations. This comprehensive guide offers step-by-step solutions to prevent VMware boot device issues. Please explore our guide now to maximize your VMWare backup solution and maintain uninterrupted system performance.