Adding a second IDE/ATA hard disk with a single IDE channel: If the first drive remains the boot device (master), how should the second drive be configured?

Difficulty: Easy

Correct Answer: as a slave

Explanation:


Introduction / Context:
On legacy PCs with a single IDE/ATA channel (one ribbon cable with two connectors), two devices can coexist as master and slave. Proper jumper configuration avoids bus contention and ensures the system boots from the intended drive.


Given Data / Assumptions:

  • Only one IDE channel is available (Primary IDE).
  • The existing hard drive will remain the boot (master) device.
  • A second hard drive is being added on the same cable.


Concept / Approach:
IDE requires one device be designated master and the other slave when sharing a channel. The boot order is governed by BIOS settings and device roles. Therefore, the new drive should be jumpered as slave (or set to Cable Select if both devices and cable support CS, but the canonical answer for exams is to select “slave”).


Step-by-Step Solution:

Check the first drive's jumper: ensure it is set to master.Set the second drive's jumper to slave per its label.Attach both to the same 40-pin ribbon (positioned master at end, slave at middle, unless CS is used).Enter BIOS to verify detection and boot order with the master first.


Verification / Alternative check:
BIOS autodetect should show two devices on Primary IDE. The OS should present the second drive as an additional disk once partitioned and formatted.


Why Other Options Are Wrong:

  • as a master: Conflicts with the existing master on the same channel.
  • as a secondary/as a primary: Not valid jumper roles; those terms refer to channels, not device roles.
  • as auto-select: Not a standard jumper role; Cable Select is different and requires CS-capable hardware/cable.


Common Pitfalls:
Leaving both drives as master, mixing Cable Select with fixed master/slave jumpers, or connecting the master to the middle connector while using non-CS mode.


Final Answer:
as a slave

Discussion & Comments

No comments yet. Be the first to comment!
Join Discussion