Member Avatar for Gandaf

Yesterday I posted a thread about my new barebones kit and how I got a msg to make a backup SATA disk. After reading some technical info from a few websites I am thinking I need to ask a "dumb" question now.
When I was re-booting for the first time in the loop I got caught up in I had the new MB disk in my CD drive. The new info I have been reading got me to thinking. Am I getting caught up in that loop because I have that disc in the drive?
I originally put the disc in because it asked for drivers and that was where they were. I didn't think leaving the disc in the drive would cause any problems and I wanted to read the disc to see what else I might need after I got up and running. Now I think that leaving the disc in might be why I am getting caught up in the loop. I think the computer thinks I am trying to start from scratch with the disc in!
I know I should just try and pull the disc out and boot the machine and see what happens, which when I am done making a fool of myself here and quit thinking out loud I will do just that!
I just thought it never hurts to much to think out loud on these boards and see what kind of help is out there at the same time. I hope someone else has the urge to think out loud too!

  • 3 Contributors
  • 2 Replies
  • 82 Views
  • 13 Hours Discussion Span
  • Latest Post Latest Post by caperjack

Dani AI

Generated

Short follow-up that ties the quick replies from and into a few practical checks for a new barebones build like described. The symptom set points to two common areas: which device the firmware is set to boot from, and whether the storage controller mode requires extra drivers during OS setup. Verifying those two things will usually show whether the system is trying to run an installer or simply not seeing the SATA disk.

Basic steps to reduce variables:

  1. Enter the motherboard firmware (BIOS/UEFI) and confirm which devices appear on the SATA list and what the boot order is. Use the one-time boot menu if you want a single-boot test without changing settings permanently.
  2. Check the storage-controller mode (often labelled AHCI/IDE/RAID). Older installers may need a third-party driver for AHCI; alternatively, switching to the controller's compatibility/IDE mode can let older setup programs see the drive. On Windows XP-era installs the installer expects mass-storage drivers supplied early in setup (the classic "F6" path) or integrated into the install media.
  3. Hardware checks: reseat power and SATA cables, try another SATA port, and test with just the target disk connected.

If firmware changes are required, consult the motherboard manual for exact keys and terminology. For background on AHCI and why some installers need drivers, see the AHCI overview and a short guide to changing boot order: AHCI overview and .

Recommended Answers

All 2 Replies

Member Avatar for dcc

If the disc is a bootable disc...yeah.

Member Avatar for caperjack

whats the big deal ,just remove the disk and boot the computer

Be a part of the DaniWeb community

We're a friendly, industry-focused community of developers, IT pros, digital marketers, and technology enthusiasts meeting, networking, learning, and sharing knowledge.