220-1002 · Question #125
A technician has just finished installing a secondary OS on a workstation. After rebooting the computer, the technician receives the following error: No OS found. The technician confirms the…
The correct answer is C. An incompatible partition is marked as active. The BIOS/firmware hands off control to whichever partition is flagged as 'active' (the bootable partition). If the wrong partition - such as the new secondary OS's partition or a partition without a valid boot sector - is marked active, the firmware cannot locate a valid boot…
Question
A technician has just finished installing a secondary OS on a workstation. After rebooting the computer, the technician receives the following error:
No OS found. The technician confirms the boot.ini file is correct. Which of the following is MOST likely causing this error?
Options
- AThe computer has GRUB Legacy installed
- BWindows Startup services are not running
- CAn incompatible partition is marked as active
- DAn unsupported version of Windows is installed
How the community answered
(59 responses)- A5% (3)
- B10% (6)
- C68% (40)
- D17% (10)
Explanation
The BIOS/firmware hands off control to whichever partition is flagged as 'active' (the bootable partition). If the wrong partition - such as the new secondary OS's partition or a partition without a valid boot sector - is marked active, the firmware cannot locate a valid boot loader and throws 'No OS found.' Since boot.ini is confirmed correct, the boot configuration data itself is not the culprit. GRUB Legacy would present a GRUB menu or a GRUB error, not 'No OS found.' Windows Startup services are loaded post-boot and cannot cause a pre-OS error. An unsupported Windows version would typically produce a different, more specific error message during setup, not a 'No OS found' at boot time.
Topics
Community Discussion
No community discussion yet for this question.