Notebook cannot see an external drive: what checks should you consider before deeper diagnostics?
-
AThe cables are attached firmly
-
BThe external drive has been pre-loaded with the appropriate software
-
CThe external drive was attached before the computer was on
-
DThe external drive is turned on
-
EAll of the above
Answer
Correct Answer: All of the above
Explanation
Introduction / Context:When a notebook fails to recognize an external drive (USB, Thunderbolt, or eSATA), the fastest resolution often comes from a structured basic checklist. Many incidents are caused by connection, power, or driver issues rather than hardware failure.
Given Data / Assumptions:
- External storage enclosure or portable drive is being connected.
- Operating system normally supports plug-and-play storage.
- No explicit error message is provided yet.
Concept / Approach:Always begin with fundamentals: physical connections, power state, and required software. Some enclosures require external power or a Y-cable for adequate current. Others need a vendor driver or encryption utility to expose volumes. Hot-plugging order can matter for certain legacy interfaces or older operating systems; replugging after boot sometimes triggers enumeration properly.
Step-by-Step Solution:
Confirm the drive's power switch (if present) is ON and the activity LED illuminates.Check cable seating, try a different USB/Thunderbolt port, and replace the cable if possible.Install any required device software or unlock utilities; verify the file system is recognized.Reboot and reconnect; check Disk Management for uninitialized or offline disks.Verification / Alternative check:Test the drive on a second computer. If it is recognized there, the issue may be OS drivers, security policies, or insufficient power on the original notebook port.
Why Other Options Are Wrong:Each individual option addresses a real and common cause; since all are relevant, the combined choice that includes all of them is correct.
Common Pitfalls:Using unpowered hubs for 2.5 inch spinning drives, overlooking disk initialization, and ignoring encrypted volumes that require software to mount.
Final Answer:All of the above