Computing.Net > Forums > Disk Operating System > Sil RAID Controller in SATA mode

Computer Problems? Computing.Net has over 1,000,000 posts about all things technology related! Over 90% answered within 24 hours! Click here to start participating now! Also, be sure to check out the New User Guide.

Sil RAID Controller in SATA mode

Reply to Message Icon

Name: Earballs
Date: February 21, 2009 at 16:12:57 Pacific
OS: WHS/2003
CPU/Ram: AMD 3200 (754 pin)
Product: Self built / Asus k8n-e deluxe
Subcategory: General
Comment:

This is a bit difficult to explain. I'll try to be as clear as possible.

I recently turned my old K8N-E Deluxe into a Windows Home Server.

Board specs: http://www.asus.com/products.aspx?l...

I have the OS installed on an 80GB IDE drive. It's the Primary IDE Master. (No optical installed)

There are 6 SATA ports. 2 ports are controlled by the chipset. They are labeled SATA1 and SATA2. I have two 250GB SATA drives plugged in here. They are the Third and Fourth IDE Masters.

There are 4 sil controlled ports labeled RAID1, RAID2, RAID3, RAID4. No disks are plugged in here at the moment, but I need to add more storage.

The system runs fine at this point. I'm not sure if a little history needs to be explained at this point, it might matter.

This machine was my main rig a couple years ago. I used two 250GB drives in RAID1 for my storage/back-ups. I had another external 250GB I used to back-up the RAID1. When I built the home server I used one of the RAID1 drives and the back-up drive. I wanted to retain a current copy of my RAID1 in case the Windows Home Server didn't behave.

I want to add the other (ex-RAID1) drive to my system in the sil controlled port. I updated the bios, installed the newest drivers, but I can't see the drive in Windows. I have the internal IDE enabled for the other 2 SATA drives. I have tried all the bios settings I can. I think. The sil is set to SATA MODE. I tried the RAID OPTION ROM to enabled with all the ports RAID mode to disabled. I also tried the ROM disabled, which removes the option to set the ports individually.

I can see the drive in the bios. It does not show up as "fifth IDE master" (not sure what it should be really) area like I assume it should. It shows up in the "Disk Drives" list which determines disk boot priority. The name of the drive is 02:60 WDC WD2500YD-01NVB1. This was the name of the other half of the RAID1 in the old system I think. (it's been a while though)

I was curious if the RAID was still holding onto the drive because it recognized it from the past. I F4'd into the RAID utility (after setting it to RAID mode in the bios) to see if it was seen as half a RAID. It wasn't clear, but it let me delete a RAID set. There was only the one drive listed. The drive is now listed as a logical and physical drive in that utility. Before that it was just a physical. The drive still isn't recognized in Windows.

There is an option to do a low level format on the drive in the RAID utility, but I wasn't sure the logic of letting that particular utility do it.

I plugged the drive into another computer and booted to my WinXP disc. I saw no partitions.

I'm not computer illiterate, but also no guru. I could really use a push in the right direction here. I don't want to replace this motherboard and processor just to use the SATA ports.

If I left off some more relevant information trying to explain that other stuff, I apologize. Just let me know what you need. Thanks for your time.




Sponsored Link
Ads by Google
Reply to Message Icon

Related Posts

See More







Post Locked

This post is quite old and has been locked from receiving new replies. Please create a new posting instead.


Go to Disk Operating System Forum Home


Sponsored links

Ads by Google


Results for: Sil RAID Controller in SATA mode

Setup.exe cannot run in dos mode www.computing.net/answers/dos/setupexe-cannot-run-in-dos-mode/11007.html

Help:Firewire through PCMCIA in Dos www.computing.net/answers/dos/helpfirewire-through-pcmcia-in-dos/13981.html

problem in dos mode www.computing.net/answers/dos/problem-in-dos-mode/13463.html