Access to SATA RAID-5 array without an MSI motherboard?

I have (had) an MSI K8N Diamoond Plus motherboard, and used it to create a bootable SATA RAID-5 array of three 300Gb Western Digital disks. Two years later, the motherboard developed a serious problem with the memory access, and now it won't POST beyond the memory initialization. So it's fried. I've tried multiple memory modules in multiple configs, and nothing helps.
OK, no problem, new motherboard and I'm good to go. Only this isn't an MSI motherboard, and it's an Intel chipset. So, the RAID array isn't recognized.
Are there any software tools that can reconstruct the RAID array when running on a non-nvidia chipset motherboard? Is there any other solution besides buy a new MSI motherboard?
And, if I have to get a new MSI motherboard to solve this, what's the cheapest currently available motherboard that would be compatible with the RAID established on the original K8N Diamond Plus?

Quote from: cameradv on 23-January-08, 00:07:27
Well, I'm not 100% sure which controller was doing the RAID. I'm thinking the SIL, but I beleive it was nvidia software drivers in windows that re-constructed the RAID-5 once when I replaced a drive. Can you buy a standalone nVidia RAID controller, anyway?
You were using Nvidia RAID, with Silicon can't do RAID5.

Similar Messages

Moving SATA RAID 0 array

Any tips on how to move a SATA RAID 0 array between machines? Is it possible? Array was set up on an NF3 chipset. Can it be moved to an NF4 or 5, or even an Intel or Promise? If it includes the boot partition can you use Win XP Pro repair console to install correct Win XP drivers, asuming the array can be installed?
scott s.

sorry for not getting back sooner, but thanks for input. That makes me feel a litlle better, but with all the RAIdDproblems I see on the boards, it makes me wonder if RAID is worth the hassle.
scott s.

Error in SATA RAID 0 array

Did anyone had any problems with the MSI board utility that configures the sata drives in RAID arrays
I have two drives that worked fine for tree months and now when I start the system get a message from the RAID config utility telling me one of the drives has a problem.
I went through formattingand reinstalling everything and the array worked well for some time then I got the same error.
Next thing I've tried was to start the system with only the good drive connected. No surprise I got the message that the array was bad. The I connected the second drive, restarted the system and the RAID utility told that the drives were OK but the array was not, but asked if the two disks belong to the original array. I answer YES and get the array functional again and the system boots with no problems.
Next boot everything starts all over again with the RAID utility stating a bad disk.
Any ideas ???

Generally, bad sectors can be blocked off so they are ignored during a format. However, you're running a RAID which functions best with identical drives.
It's unusual to have bad sectors on drives these days which inclines me to think that "heat" is what may have led to the bad sectors.
In your case, you are better off to RMA the drives but since you have the array up again, I would recommend using it to determine if your system temps may have led to the bad sectors.
If temperature is an issue in your system, you could plug new drives back in and end up having the same results after a short time.
Then again, your situation may just be a fluke and you just got a bad drive. Either way, RMA.

K8N Neo2 SATA Raid problem finally solved

Hi guys,
finally got my SATA Raid 0 array to work.
Problem was that XP didn't find a correct array on installation although i used F6
to load drivers from disk. Sometimes it didn't detect any hard disk, sometimes
it showed two hd's and an array and so...
The whole spectrum of errors mentioned here over the last days and weeks...
I tried different bios like 1.1, 1.2, 1.2b5, 1.3b5 and i got the newest drivers
directly from nvidia as mentioned in some other thread. Nothing worked.
One should think that nvidia would have the latest drivers... but that was the
major fault.
As mentioned in a different thread i downloaded the unified nforce drivers from
nvidia's homepage and extracted the ide drivers to a floppy. I used these drivers
in all of my attempts and it never worked..
Yesterday i downloaded the MSI Nvidia nForce3 System Drivers package 5.03 from
http://www.msi.com.tw/program/support/download/dld/spt_dld_detail.php?UID=607&kind=1
and compared the version numbers to the files from the nvidia package.
The relevant files nvatabus.sys and nvraid.sys are version 5.10.2600.412 from
nvidia while the MSI versions are 5.10.2600.446 !!
I put these files on the disk, set up my bios (default 1.1) from scratch, started XP installation,
hit F6, loaded the new drivers and voila... one 230 gb array ready for installation
Took me FOUR days to figure this out. THANK YOU MSI support team,
wherever you are.... (definitely not working on an updated hp)
So to put it in one line:
What really worked for me were the drivers from the MSI nforce3 driver package 5.03
No messing around with beta bios, no voltage tweaking or SATA 3/4 preferred
or DIMM Slot preferred crap.
Of course you have to set up an raid array as described in rsheppicks raid setup guide
Only thing about bios versions is that only in bios 1.1 i got an array shown in the
hard disk boot priority list
So i hope this helps you guys out there that are having troubles setting up SATA Raid.

OK now! Dag, I was going crazy. I had two brand new Raptors and was trying to hook them up in a RAID 0 config. I am no dummy. It would hang at detecting arrays. I could not figure it out for the life of me. I will not talk about all of the combos that I tried. My buddy told me to try datalifeguard from WD. I did. Well, one HD showed no serial number in the extended test. An error message popped up. Said the drive was not working. So, Newegg sends me a dead drive and wastes days and days out of my life. I hooked up the one good drive just now. What do I see? For the first time in my life, I am seeing the raid bios! This almost cost me a divorce. Seriously though, the wife would come in and rub my shoulders like a fighter after a few hours of getting my azz whipped by this new rig. I am now going to make the floppy with the newer drivers like was done here. Just incase. I am in Raid bios now in the other room. Time to go set up XP on one drive for now. I refuse to wait for the RMA'ed second Raptor.

Oracle Ent. Linux drivers for HP Smart Array B110i Sata Raid Controller

Trying to install Oracle Ent. Linux (OEL) release 4 update 8 on HP DL 180 G6 server. Where we can find OEL drivers for the sata raid controller ?
(HP Smart Array B110i Sata Raid Controller)
Thanks in advance.

The HP support side shows a Linux certification matrix at: http://h18000.www1.hp.com/products/servers/linux/hplinuxcert.html
From there you can also download the necessary drivers and instructions or use HP smartstart CD which prepares the system for the OS you need to install. Oracle Enterprise Linux is binary compatible with RHEL. You will need to click on "Archive" to see support for Enterprise Linux version 4 and older.
Also interesting should be Red Hat Enterprise Linux Technical Exceptions at
http://h18000.www1.hp.com/products/servers/linux/supportmatrix/rhel/exceptions/rhel-exceptions.html

Configuring 2 SATA drives for an OS X RAID 1 array & also for OS 9.

Does anyone know if a configuration like this might work in a G4 AGP Graphics "Sawtooth"?
• A SATA controller card that supports RAID 1, such as one of the FirmTek SeriTek cards at the below links:
[http://eshop.macsales.com/item/Firmtek/SATA1V4>
[http://eshop.macsales.com/item/Firmtek/SATA1EVE22>
• Two 500 GB, 640 GB, or 1 TB SATA drives.
• Partitioning 200 GB of each drive for use by OS 9 when booting directly into it.
• Using the two drives in a RAID 1 array when booted into OS X.
• Not installing a 3rd-party RAID software utility for OS 9.
Specifically, does anyone know what would happen when one boots into OS 9? Would the two drives simply be seen as two separate 200 GB partitions?

Hi-
Would the two drives simply be seen as two separate 200 GB partitions?
That is how it should work.
Go one better, and find SoftRAID 2.2 and RAID the 2 200 GB partitions for use in OS 9.

Confused about SATA RAID and SATA DVD

I'm planning to build a system based on the P965 Platinum board and I'm considering implementing a RAID 0 array. However, I have read of many problems with RAID and SATA DVD writers. Are most problems just due to BIOS problems or are there more inherent problems? Are people successfully running this board with a RAID array and SATA DVD? Can you boot from the SATA DVD drive?
If I have a pair of drives in a RAID array, can I add further hard drives that will not be in a RAID array? I won't trust RAID for all my data and I don't want to use mirroring.
I'm confused and I can't seem to find any definitive answers on this.
Thanks
Teresa

Quote
Thanks Maesus. Will the drive from an AHCI machine only work in another machine set up with AHCI?
Teresa, yes but not always, this AHCI is driver bound. And because this AHCI is driver bound, it makes it hard to change from IDE to AHCI for a IDE driver installed OS, as the OS doesn't have AHCI driver installed. So when you change to AHCI setting in the BIOS, the OS refuse to load further. AHCI is driver bound, and it is also controller/chipset bound. If you installed an OS with AHCI settings enabled in an AMD system, you may not run that in an AHCI Intel system. Vice versa.
Quote from: Teresa on 20-May-07, 19:51:36
I ask this because there's a thread here that gives instructions on how to turn on AHCI after Win XP has been installed. That tends to suggest that AHCI makes a difference to an operating system install.
This is only because the OS installer doesn't have AHCI driver built-in. If you slip-streamed your OS installer with AHCI drivers, your OS installation will go smoothly.
Quote
Or is it a case that the disk's data can still be read on another machine without AHCI but it can't be used to run Win XP? I just need to know that I can pull my data hard disk out of my system and access it on another older machine that doesn't have ACHI.
Yes, the disk's data still can be read anywhere else. Just that it cannot be used to boot up to WinXP, if that WinXP doesn't have AHCI driver installed.
Quote
Hopefully one day soon I'll reach a critical threshold of knowledge and actually start ordering the parts for my build.
Teresa
Let's make it simple. Treat IDE, AHCI and RAID-0 as different HDD drivers. WinXP has IDE driver built-in. Vista should have all drivers built-in. IDE and AHCI data structure is the same. However, RAID-0 data structure stored in the HDD is different and is controller-bound.
For AHCI mode installed HDD, you can read in IDE mode without single issue.
For IDE mode installed HDD, you can also read in AHCI mode without issue, provided AHCI drivers are installed upfront.
For RAID-0 installed HDD, you cannot read in IDE or AHCI mode, and you may not be able to read in other different controller/chipset systems even though you set them as RAID-0 exactly.

Can I set up a RAID 1 Array by adding a drive to an existing install?

Hi All:
I have a K8N Neo2 with a 160GB Seagate SATA drive on it, and just bought an identical drive that I want to use for a RAID 1 array. My question is this: Do I need to do a complete reformat with the OS in order to setup RAID 1? With my old system and Ultra ATA drives, you could always add a drive, but I don't see any way to load the nVidia RAID driver after Windows has already been loaded.
Is this possible, and if so, what are the steps? I've enabled RAID for both SATA drives and can get into the RAID Bios, but beyond that, I'm lost. Also, I must have inadvertently setup an array, because it shows that I have one. I can boot into Windows if I turn off RAID in the BIOS, but would love to be able to install without a clean format.
Any help would be greatly appreciated!
Thanks,
Michael Tschirret

Michael,
You can create a RAID 1 Array, just make sure that the Drive with the Data is the Master and not the Mirror. You can have the RAID Controller build the image (Sync the Drives), and then you should be mirrored before you even boot back into Windows. The OS will not know the difference.
Take Care,
Richard

RAID 0 array of SSDs: not a bad idea, but not easy

I thought you all might find this interesting, and in any case, I'd enjoy hearing feedback as you might also audit these conclusions based on your own expertise with PC systems.
I'm pushing technology to the furthest limits at all times, because I'm grinding through highly compressed 28 Mbps AVCHD 1080p footage while applying numerous layers of GPU-accelerated effects, onto multiple tracks and camera angles inside the Adobe Premiere Pro CS6 workflow. We all know that one of the critical ingredients to surviving in that context is disk access speed (complementing CPU power, which for me is an Ivy Bridge 3770K overclocked to 4.4 GHz) -- and this is one area where a RAID 0 array of SSDs actually results in meaningful performance gains. For people playing games, not so much.
The dilemma, taking my Gigabyte GA-Z77X-UD5H motherboard as a typical example, was this: I wanted my RAID 0 SSD array (two PNY XLR8's comprising half a gigabyte) to co-exist with my Vertex 3 SSD boot disk. The typical Z77 motherboard only has two Intel SATA-III ports, and those ports are the only ones (to my knowledge) that offer native TRIM, while the supplementary Marvell SATA-III ports do not. Since junk collection (of the kind that supplements any modern SSD's own internal junk collection) is more critical on the boot drive, and is almost useless on a mostly read-only drive, I didn't have the option to move my Vertex 3 SSD boot disk over to those Marvell SATA-III ports. In the meantime, I did try out the RAID 0 SSD array on those Marvell SATA-III ports, which are supposed to provide a theoretical headroom of 1.2 GB/s (i.e., 600 MB/s x 2), but I got a stunningly offensive, ridiculous, laughable 350 MB/s or so read rate -- from a RAID 0 SSD array! Those PNY XLR8's are rated at around 500 MB/s read speeds on their own!
Bottom line, I felt that the optimal compromise was this: move the boot SSD onto the Intel SATA-II ports, hitting up against the bottleneck of 300 MB/s (whereas the drive normally performed at around 500 MB/s on the SATA-III port). Then, assign the RAID 0 array to the two native Intel SATA-III ports. No joke, in that configuration, using ATTO Benchmark, I got over 1.2 GB/s read speeds. That's a godsend for constantly pulling multiple compressed HD video source files (many of them over 1 gigabyte in size) into any complex video editing workflow.
I haven't found conclusive proof, but I suspect that the motherboard's Marvell SATA-III controller is grabbing (for life) onto a singlular PCI-E x1 lane, leaving way less bandwidth than necessary to live up to even one single 600 MB/s SATA port spec, let alone the aggregate of several SATA-III ports. Does that sound right? And moreover, what moron would engineer things this way, calling a port SATA-III when it performs sub-SATA-II?
I also suspect that this is fairly typical on today's best Ivy Bridge motherboards. Thoughts? We are all obviously trying to avoid the clutter of adding a dedicated RAID card, which would probably underperform in comparison to the native Intel controller anyway.

Alex DeJesus wrote:
So, is anything being done about the Marvel ports on newer motherboards?? Is it a firmware issue? I would like to put this behind me at some point. I find it hard to believe this topic hasn't come up before.
I'd like to get two RAID 0 arrays on four SATA 6 GBs ports for storage and another RAID 0 of SSD for system and programs
The only way to get more RAIDable 6Gb/s ports is to either get yourself a RAID card which in the case of your Z77 MB is not practical (it will cause your GPU x16 slot to operate at x8) or get the Asrock Z77 Extreme11 MB which has an on-board LSI SAS 2308 controller which interfaces to a PCIe 3.0 bus via a PCIe extender PLX 8747 bridge chip

Xserve SSD OS drive Raid 5 array - What if SSD OS drive is corrupt or fails

Xserve SSD OS Drive option with Raid 5 array - What if SSD OS drive fails or the OS becomes corrupted? Could you just re install the os and then upload all of your server settings and it would be able to talk to the raid array and be good to go?
Additionally if the os is in the raid 5 and becomes corrupted and you are not able to get the os to boot would the raid 5 data not be able to be accessed? Or could you just reinstall the os on the array and be ok?
This would be the same if the os is inside a software mirror set?
Thanks in advance!!!

Hi
If you're asking can OSX Server be reinstalled without a reformat the answer would be no. This assumes you're using the OSX Server Installer DVD. Assuming no other hardware issues you should be able to access any/all data on any of the Drives using Target Disk Mode and another mac. This will at least allow a transfer of important data to another source. Having said that you should be keeping back-ups anyway.
You can export Server Admin's configuration as a series of property lists. You can export Users, Groups and Computer Lists from WorkGroup Manager. You can archive the whole of the LDAP database - which will contain everything except home folder information - using Server Admin.
I'm not sure if this is still the case but one of Apple's Best Practice tips was to setup and configure the Server exactly as you wanted it first. Once you're happy use any one of probably half a dozen methods to make a Bootable cloned backup. A free built-in method would be to boot from an appropriate Installer Disk and save the Server OS as a .dmg to a connected USB or Firewire disk. Or use something like CarbonCopyCloner to do regular scheduled clones to an externally attached drive.
My 2p.
Tony

Mounting a RAID 0 array that's already been made (OS X RAID - Arch)

Hey, I'm trying to access my two-disk RAID 0 array that I've been using in OS X (within the same desktop computer). I've been reading the arch wiki about RAID, but it seems many of the recommended steps may erase all data on my array. Would jumping to building the array (https://wiki.archlinux.org/index.php/RA … _the_Array) work for solving this problem? And how would I know what specific settings to use?
If it would just be easier to make an array from Arch that is also compatible with OS X, that would be an option as well.

Agree with syar - It's not just a matter of the RAID either - the chances of being able to boot into Windows with or without RAID is slim on a different mobo as the OS uses a load of device drivers and other stuff specific to your particular installation.

Moving MSI K8N Neo RAID.0 array to new MOBO (from Nforce4 Ultra + Sil3114!)

Hi folks!, my MSI K8N Neo4 Platinum is GONE , and I had 5 disks on it:
Disk 1: No RAID - OS - WinXP installed
Disk 2+3: RAID.0 on Nforce4 Ultra MCP controller (onboard)
Disk 4+5: RAID.0 on Sillicon Image Sil3114 controller (onboard)
Questions are:
1- Anyone knows if ANY CURRENT MSI motherboards model is RETRO COMPATIBLE with the legacy NFORCE4 controllers (with AMD CPU)?
-> In case not, any solution to access the RAID from the NForce4?
2- Since I think no current motherboards have Sillicon RAID controllers (if you know of any, please tell me), anyone knows any PCI controller to attach to the new motherboard COMPATIBLE with the Sil3114? (I read that the new Sillicon controllers are generally compatible with the old ones), so I can access the Disk 4+5.
Thank you!
Luis

Quote from: claudermilk on 21-August-09, 08:28:58
I feel your pain. I'm also interested in a mobo with a compatible nVidia controller. In my case, it's only a dead drive that was on the 3114 controller (OS) while the nVidia is full with a 0+1 array. Unfortuately Windows refuses every drive I offer it on the 3114.
I'm thinking on doing this, what do u think? :
1- For the Nforce4 array: Nvidia offical tech support said me that all new NVIDIA RAID controllers (both NFORCE/GEFORCE) are backwards-compatible with legacy controllers like the NFORCE4 Ultra I had, so in theory, a new one should "understand" the RAID array coinfiguration metadata stored on the disks, and no information would be lost. This is as long as the RAID BIOS version of both old and new MB is 9.xx...
So in this case I'l buy a new MB with a Geforce 8200 chipset (ASUS M3N78-VN with a Phenom II 710).
The only worry is how to verify WHICH RAID BIOS version I had on the defunct MB... any idea? Is the RAID BIOS inside the MB BIOS?
2- For the Sil3114 array: I'm buying a Lycom ST-127 PCI host and connecting it on the Geforce 8200 new MB, which essentially contains the same chipset brain as the original Silicon Image 3114 I had on the MSI MB.
In this case, I'd have the same logic controller for that array...
All disks are SATA.
Any thoughts? I'll keep you posted!
Thanks, :D
Luis

[SOLVED] Kernel cant rebuild RAID 1 array with mdadm

I am trying to setup a raid 1 array. My problem is that the kernel doesn't assemble the array after reboot and says that it cant find /dev/md1
I've chrooted in the new environment from the existing installation on the old disk and added the mdadm hook and it 'compiled' (mkinitcpio -p kernel26) with the /etc/mdadm.conf. I've added all the stuff to fstab. I have a / and a separate /boot array. The /boot array was created with --metadata=0.90 because grub cant access partitions with newer style metadata.
I added the array info to /etc/mdadm.conf and ran mkinitcpio -p kernel26 with the mdadm hook. The hook ran and printed a notice that it would get the array info from /etc/mdadm.conf, so I guess that worked.
After I reboot and set the drive with the array as the first boot device in the BIOS, grub starts up with one additional entry that I added before:
timeout 5
default 0
color light-blue/black light-cyan/blue
title Arch on RAID
root (hd1,0)
kernel /boot/vmlinuz26 root=/dev/md1 md=0,/dev/sda3,/dev/sdb3 vga=792
initrd /boot/kernel26.img
# (0) Arch Linux
title Arch Linux
root (hd0,0)
kernel /boot/vmlinuz26 root=/dev/disk/by-uuid/8b19e18d-9beb-49da-83f1-b29284b8d6e1 ro vga=792
initrd /boot/kernel26.img
# (1) Arch Linux
title Arch Linux Fallback
root (hd0,0)
kernel /boot/vmlinuz26 root=/dev/disk/by-uuid/8b19e18d-9beb-49da-83f1-b29284b8d6e1 ro
initrd /boot/kernel26-fallback.img
The first entry is the one that should load the new mdadm enabled kernel and it works...it loads some kernel, but I'm not sure if its the right one since it cant 'find' /dev/md1 witch was added as a hook before.
I'm a little suspicious since /boot is a separate drive in my situation, so technically the kernel would be on /vmlinux26, not /boot/vmlinuz26. Ive tried all different combinations of root (hd0,0, hd0,1, ...) and with or without /boot, but no luck. hd1,0 is the only one that works.
/etc/mdadm.conf:
DEVICE partitions
ARRAY /dev/md0 metadata=0.90 UUID=a5db7993:bc310e03:a0504988:dd22e85f
ARRAY /dev/md1 metadata=1.2 name=scorpion:1 UUID=7e20d1a8:4382351d:56d4cac8:d65a45b8
/etc/fstab:
devpts /dev/pts devpts defaults 0 0
shm /dev/shm tmpfs nodev,nosuid 0 0
/dev/md1 / ext4 defaults 0 1
/dev/md0 /boot ext2 defaults 0 1
/dev/sdb1 swap swap defaults 0 0
The array assembles just fine on my existing installation:
[root@scorpion krt]# mdadm -A /dev/md0 /dev/sdb2
mdadm: /dev/md0 has been started with 1 drive (out of 2).
[root@scorpion krt]# mdadm -A /dev/md1 /dev/sdb3
mdadm: /dev/md1 has been started with 1 drive (out of 2).
[root@scorpion krt]# mount /dev/md1 /mnt/root/
[root@scorpion krt]# mount /dev/md0 /mnt/root/boot/
[root@scorpion krt]# mount --bind /sys /mnt/root/sys/
[root@scorpion krt]# mount --bind /proc /mnt/root/proc
[root@scorpion krt]# mount --bind /dev /mnt/root/dev
[root@scorpion krt]# chroot /mnt/root/
[root@scorpion /]#
I was trying to get this going all yesterday, but no luck.
Can anyone help me figure it out? I'm desperate here.
Last edited by KRTac (2010-08-05 17:58:01)

If you use separate partition for /boot then you definetely should put /vmlinuz26 not /boot/vmlinuz26.
And under root hd(x,y) you should put your /boot partition number.
If interested here is the output of few commands on my up and running machine with RAID 1 /boot + grub:
http://pzt.me/hzvta
http://pzt.me/c2xz1
http://pzt.me/9gbqx

K9A2 Platinum Sata Raid Problems

I could not get my 2 500 gb seagate 7200.11 drives to work on the sb600 raid controller, in raid 1 (set to raid mode in bios). I'd set it up and it would remain functional until I formatted it and put stuff on it. Then when I restarted, it says critical and can't locate the second drive, but it shows up in the list of definable drives. My older 200 gb seagates 7200.9 in the same setup do not have this problem. I finally got my 500s working by hooking them up to the promise controller instead. (Although no longer a current problem, I wouldn't mind knowing what would cause this for future occasions.)
My new problem is, I had to unhook all but the drive I wanted to install Windows XP on (A separate 120 JBOD configured drive) so I could get it to be C:/. This all went fine. However when I hooked up the 500s again, Windows XP would not boot, the screen just stayed black, with them not hooked up, it boots just fine, with the 200s as well. When running the Windows XP setup again, the 500s appear as C:/ instead of the 120 in the disk select screen of the install. It's like the 500s took over the drive letter when they are hooked up and thus can't load. Is there some way to stop it from doing this or am I completely off on this.
My computer spec is:
K9A2 Platinum
AMD X2 6000
2*2gb OCZ PC6400
ATI Radeon 3870
700 Watt OCZ PSU
Update: Installing XP ignoring the fact its not C: fails. It copies all the files onto it, then after restarting I get a black screen.
Another Update: On a whim I tried disabling the SB600 raid and set it to AHCI instead as I read that other people were having problems with it and it all works perfectly now. It's too bad this doesn't work, but I'll just put the 200s back in my old computer instead.

I'm having the exact same problem you did. Same Mobo. Except I started off with Promise RAID 1 because when I tried using SB600 RAID, my SATA DVD drive would not function in Vista Ultimate x64. So I had my Raid 1 configured on Promise T3 with BIOS 2.8.1030.0021 using 2 320GB drives. One of them Seagate, one WD, both 3GB/s transfer, only difference was that Seagate has 16MB cache, while the WD has 8MB. But both drives worked fine in the array for some time, and then after doing some updates from Windows Updates now the Raid config shows that encountered a critial status, "A disk member of an array has failed or is not responding", "Problem is detected with Array : 1". And when I go to the see the Array status it shows the Seagate drive on ID channel 1, but for the 2nd drive it shows questions marks all the way through the item line. I checked the drive, it seems fine. And even when I go to define a second Array, it shows the WD available on channel ID 3. So it definitely see both drives, but how do I re-add that WD drive that it doesn't see to my earlier defined array without loosing data on my Seagate drive?

I tried to overclock and the Raid 0 Array failed

Is there any way to get my Athlon 64 3200+ Clawhammer to 2.2 Mhz without ruining my Raid 0 array? I don't know how to OC on these boards.

Quote
Originally posted by Negator
I just set it to 67, and I have a SATA controller card I can use if I need to.
This was your problem. With it at 66mhz the PCI/AGP speed up when you change the FSB/Memory/HTT speed :-)
With it at 67 it locks the PCI/AGP so this will make your pci based sata controller not freak out. So now move your computer to 215fsb and lets see what happens. If it won't post or load windows then loosen the timings quite far and try again if it works then bingo you know what to do tightin the timings up until you get to what you consider to be good :-)

Access to SATA RAID-5 array without an MSI motherboard?

Similar Messages

Maybe you are looking for