Announcement

Collapse
No announcement yet.

HDD's and optical drives not recognized when posting a new build.

Collapse
This topic is closed.
X
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

    HDD's and optical drives not recognized when posting a new build.

    I have purchased and am waiting for a case speaker to see if I can get a better understanding of what is going on. About a week to wait.

    The computer posts and I can get a BIOS onscreen. Selecting Defaults does not assist the boot.

    Both SSD's have OS's installed, Win 7 and Kubuntu 13.10, and although both are indicated in the BIOS boot order, neither are recognized when boot is attempted.

    One of two optical drives is recognized in the BIOS boot order, but it is not recognized when attempting to make a fresh install of an OS.

    How do I get the optical drives mounted properly without access to an operating system?

    Or, how do I fresh install an operating system in the new build.

    I am aprehensive about updating the BIOS prior to receiving help; I am not sure I could do it anyway without access to the Internet.

    This is my fourth build, so I am not completely inexperienced, nonetheless, I am currently stymied and need help.

    What should I do next? Thanks.

    ***Things have changed a bit. In furthing my efforts to solve my problem, I noticed that my attempts to make any changes to the BIOS were rejected. I then found a place where setting of passwords for Administrator and User were made. Thinking that I might open the BIOS as Administrator and thereby make changes that take affect, I set passwords for both Administrator and User.

    The next time I restarted the computer, the opening screen is a login screen. However, my mouse is no longer active after the restart nor is the keyboard. Therefore, I am unable to make the login entry because it remains inactive. Access to the BIOS is now barred, too. Can these and my other problems be overcome? Thanks. Sorry about screwing things up more.;(


    SABERTOOTH 990FX R2.0 Motherboard
    Serial No.: DBM0AD810298
    Part No.: 90-MIBJA0-GcAAY0VZ
    Check Number: 8172

    GSKILL ARES 2ea 8gb sticks total 16gb
    F3-1866C 10D-16GAB
    DDR3- 1866 cl 10- 11 - 10-30 1.50v
    PC3- 14900 8Gx2 intel XMP ready
    2013 Mar 13112100227678
    Located in the 2nd and 4th Slots

    PROCESSOR
    FX 8350 8-CORE Black Edition
    4.0 GHz, 16.0 MB Total Cache
    SN# 9N51932A30266

    XFX R7850 DOUBLE DISSAPATION
    Model No.: FX – 785A – CD
    Part No.: FX – 785A – CDFC
    DD RADEON 7850 860M 2GB D5 2XmDP HDMI
    2XDVI
    S/N: O1Y070019

    BFG Power Supply 800W

    256GB SSD
    128GB SSD
    TB SATA 6GB/s HDD
    TB SATA 3GB/s HDD (Not currently recognized in BIOS)

    2ea DVDRW SATA

    7ea Case Fans

    ZALMAN CPU Cooler
    Last edited by Shabakthanai; Feb 07, 2014, 03:11 PM. Reason: Things have changed a little.

    #2
    Hm. The only way I know of to reset a firmware password is to disconnect the AC power and remove the CMOS battery on the motherboard. Wait a minute or two to let any capacitors discharge. Now reassemble. Is the password gone?

    If this doesn't work, you may need to contact the motherboard manufacturer. Or start Googling.

    Comment


      #3
      Thanks Steve,

      Before getting your reply, I found a solution. You are correct and thanks. Sorry for wasting your and others time.

      Comment


        #4
        It's never a waste of time, don't worry. Glad you're back up and running.

        Comment


          #5
          Originally posted by Shabakthanai View Post
          Thanks Steve,

          ...I found a solution.
          For the benefit of others, what was that solution?
          Windows no longer obstructs my view.
          Using Kubuntu Linux since March 23, 2007.
          "It is a capital mistake to theorize before one has data." - Sherlock Holmes

          Comment


            #6
            At first, I read his answer to be that he found something that was the same as what I recommended -- removing the CMOS battery. You're right, though; it would be good to know if that was it or if there was some other solution.

            Comment

            Working...
            X