What would cause a BIOS to see SATA drives, but not the RAID management software?

Discussion in 'General Hardware' started by Brad, Aug 3, 2007.

  1. Brad

    Brad Moderator Political User Folding Team

    Messages:
    2,280
    Location:
    Cary, NC
    I have two 74GB 10K RPM drives that I want to set up in a RAID1. According to the BIOS the drives can be seen and the SATA ports are enabled, but when I get to the RAID configuration software (Silicon Image) the drives are not installed....

    Can someone help me please?
     
  2. Aprox

    Aprox Moderator Political User

    Messages:
    2,737
    Location:
    California, USA
    So while in the Raid Configuration, when you go to create array they do not show up? Unless you have an array already configured the config software will not show the drives, except in the create array menu.
     
    Shamus MacNoob likes this.
  3. Brad

    Brad Moderator Political User Folding Team

    Messages:
    2,280
    Location:
    Cary, NC
    If I go to "Create Array" it says that there are not enough disks to create the array.
     
  4. trainmaster77

    trainmaster77 Moderator Political User Folding Team

    Messages:
    509
    Location:
    St. Louis/Chicago
    did you load a different driver for them? Silicone Image is on my mobo ..but i use the nvidia raid ports. The first time i installed sata drives i did exactly that ..loaded silicone image when i wanted the nvidia ones.

    Just a thought.
     
  5. Brad

    Brad Moderator Political User Folding Team

    Messages:
    2,280
    Location:
    Cary, NC
    There is no where to add drivers though. This is what comes up immediately after getting out of the initial boot-up screen.
     
  6. LeeJend

    LeeJend Moderator

    Messages:
    5,291
    Location:
    Fort Worth, TX
    This post seems familiar. As I recall from the last post the drives were plugged into the wrong set of SATA ports to work with the RAID installation program. But I'm old and senile and my memory and other critical body parts are going...
     
  7. Brad

    Brad Moderator Political User Folding Team

    Messages:
    2,280
    Location:
    Cary, NC
    I haven't changed my hardware configuration. I had a boot sector virus and had to clear out and start over again
     
  8. LeeJend

    LeeJend Moderator

    Messages:
    5,291
    Location:
    Fort Worth, TX
    Ahh, so you re-wrote the boot sector to remove the virus. That means foot print and volume data is no longer the same.

    Windows will not recognize the disk after doing this because a Windows DRM footprint has been removed. You need to do a format and partition just like with a new HD out of the box.
     
  9. Brad

    Brad Moderator Political User Folding Team

    Messages:
    2,280
    Location:
    Cary, NC
    Yes, I understand that. The problem lies in the fact that the RAID management software--which gets loaded before windows--doesn't even see the drives
     
  10. LeeJend

    LeeJend Moderator

    Messages:
    5,291
    Location:
    Fort Worth, TX
    Format the drives individually from the windows CD then go back and build the raid. I should have been more specific.
     
  11. Brad

    Brad Moderator Political User Folding Team

    Messages:
    2,280
    Location:
    Cary, NC
    OK, I will try that
     
  12. Brad

    Brad Moderator Political User Folding Team

    Messages:
    2,280
    Location:
    Cary, NC
    I tried reformatting the drives and the drives themselves are seen by windows under the Silicon Image controller, but if I go into the Silicon Image Manager, the drives do not show. Weirdest thing I have ever seen. Well, I have seen weirder at a certain entertainment venue in Tijuana but I digress
     
  13. LordOfLA

    LordOfLA Godlike!

    Messages:
    7,027
    Location:
    Maidenhead, Berkshire, UK
    update the motherboard bios and try again.
     
  14. Electronic Punk

    Electronic Punk Administrator Staff Member Political User Folding Team

    Messages:
    18,590
    Location:
    Copenhagen, Denmark
    May well have overlooked a bios option?