220-902 question 77 discussion


A technician installed a second hard drive in a computer. Upon restart, a message appears
statinG. primary drive 0 not found. Press F1 to continue." Which of the following should the
technician check FIRST?

  • A. That NTLDR and boot.ini are not missing
  • B. Proper drive installation (e.g. cables/jumpers)
  • C. If computer can boot into safe mode
  • D. If the BIOS boot settings are correct
Created 1 year ago by deefff


why would it not be bios settings? from the way it's worded, it SOUNDS like the tech didn't specify which partition was primary because its a SECOND drive that is being installed. checking the boot sequence would be my first guess rather than the physical cables ( ie I would make sure the boot sequence was correct FIRST before I started to take the computer apart and check jumpers. Doesn't that make more sense? What am I missing here??


Xanax bro Xanax


Im in the same spot as you


I agree with you.


The question is poorly stated (and to confused people). Since there are no indication of the bios being modified, you have to assume that the tech disconnected the cables (change jump) by mistake. I also answered checking the bios first but since they want you to take the test again, this is their wording of the question.


Since problem states that the issue happen after the installation of the second hard drive, you can probably assume the first hard drive was working right before the installation of the second drive. So it is likely that the tech disconnected cables for the first drive during the installation of the second drive. Hence, answer B.


Hard drive could've been accidentally put on a master jumper instead of a slave during install.


It falls in line with the "check the simple and obvious first" mantra. :)


If the second drive cables were connected right, the initial message," primary drive 0 not found" would not display.


Since the technician has just installed a second drive, he could have left one or more cable loose during the process or misconfigured the jumper...


boot settings wouldnt matter here, it cant find drive so maybe its not connected or jumped


such amateurism from the technician... and he will be fired more quickly than the time to find a solution to the drive jumper problems :D


This really makes more since when you start getting further into networking in general and dealing with the TPC/IP and OSI models which state to always start with layer one, the physical layer when troubleshooting devices.


I have to start of by asking who has installed an IDE hard-drive lately? SATA doesn't use jumpers but many of the mother-boards on the market require the "Primary" boot drive be plugged into a specific SATA port on the board. If nothing was changed and the second drive was installed and simply not activated in bios, most systems would still boot but the drive wouldn't be recognized by the OS.


Since they're installing a second drive, I'm assuming most new drives come with the jumper already set to MA. Assuming the HDD already in the machine is also set to MA, wouldn't that cause the conflict described?