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.

Similar Messages

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.

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.

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.

SATA Raid 0 and Overclocking Issues. Help!

I'm building out a machine that doesn't seem to want to overclock in the slightest bit. I think my Serial ATA RAID 0 array seems to be the problem with OC'ing. Each time I change the CPU FSB settings, when I boot up, it tries to detect my array. Then it reboots after it fails.
Does anyone know what's going on? Someone mentioned PCI Bus settings to me...???
On Anandtech they OC'd this chip to 2.6 Ghz (290x9) with an 8.3%+ in voltage. I can't even get to 220.
Any help would be much appreciated.
Thanks!
======================
System Setup:
Athlon 64 3000+ Socket 939
K8N Neo2 Platinum
2 Hitatchi 80 gig SATA HD's
Leadtek Winfast 6600 GT (AGP)
Zalman CNPS7000B-AlCu Heatsink
Seasonic Super Tornado 400W PS

Ok, I switched it to SATA 3/4 and then I couldn't boot. I kept getting some error which would cause it to boot again. It happened right after it detected the array successfully. The warning message happened so fast the first couple times I didn't even notice it. It would flash some sort of blue screen like error (only it was a black screen) and then reboot itself.
Frustrated, I decided to start from scratch again. I wiped out the discs and re-created the RAID 0 Array and put my WinXP CD back in. Now while setting up WinXP I hang at the "Setup is starting Windows" screen.
It won't go anywhere from that. It happens after I copy over the RAID Driver and Controller from the Floppy. It copies more files after that and then hangs...
I also reset the CMOS with the jumper settings, un-did and re-did my SATA connections, even unplugged the little MB battery... :(
Any suggestions? This is so frustrating.
TIA.

SATA RAID and K92A Platinum

OK Guy’s
I need your assistance here. I just purchased a MSI K92A Platinum motherboard and having the darnest time setting up RAID 0 (or any RAID period). Before I go any further this is my setup.
SATA 1 Western Digital WD2500JS 250GB SATA
SATA 2 Western Digital WD2500JS 250GB SATA
SATA 3 LITE-ON 20X DVD SATA MODEL LH-20A1S
SATA 4 Western Digital WD2500JS 250GB SATA
SATA 5
SATA 6
Floppy drive installed
Memory: Kingston Hyper 2GB 1066 (x2)
Processor: AMD 6400+ (3.2)
Video: Ge Force 8800 GTX
In the basic (CMOS) screen I see all my drives. When I move to the advance screen and select RAID. All the drives including my DVD disappear from the basic (CMOS) screen. In the RAID utility, I see all three hard drives (minus the DVD drive). I created my RAID 0 with two of the drives and left the last drive free for future use. The problem arises when I reboot and try to use my DVD drive with Windows VISTA. After the initial boot from the Windows CD, I followed the on screen instruction by selecting the install tab. It would prompt me for my license number and move to the next screen. After that it would return with the error unable to find DVD/CDROM (no further installation possible). Just remember it had booted off the CD in the first place. Not sure what is the problem. Unfortunately I can’t install WINDOWS on a RAID drive until I figure out why when I select RAID that my DVD is not seen correctly after booting .
All things being equal, I have no problem installing WINDOWS without defining a RAID device on this motherboard. All the drives are seen including my DVD. A little history I just came from using an ASUS MSN-SLI Deluxe motherboard and I did not have any of these problems. At this point is seems ASUS had the easiest RAID utility. Final note, hardware is good and tested. Any response would be greatly appreciated.
Thanks in advance
Richard

No, you can use as many as you would like. It's just that RAID 0 with three drives is not possible on the Promise controller (red ports), as it has only two ports. Therefore you will need to use the SB600 controller, which is somewhat picky about SATA RAID drivers...
Anyway, the Promise controller is already disabled. Set your SB600 controller to RAID in your BIOS, then enter the FastBuild utility using CTRL + F when prompted. Build the array to your likings and save the settings, then boot from your Vista DVD. If you're lucky the drivers from the MSI CD (for Vista) will work. Otherwise you will have to start trying SB600 SATA RAID drivers from other manufacturers, those from DFI are known to work quite well.

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

ITunes for Win XP, RAID 5 Array

Hi,
I have iTunes on WinXP, and it is causing issues with my raid array. I have an Adaptec 2820 SATA Raid card running the Radi 5 array. My music and "My Documents\My Music"
folders are on this this array.
EVERY time i open itunes, it works for a few minutes and then locks up my computer. then the raid array starts complaining and everything is frozen. On reboot the raid card claims a disk has been dropped form the array. I then go into the raid management software and it finds the disk and puts it back. It then takes 4 hours to rebuild tha array, which is kindof annoying.
This consistently happens. And i have verified it is just this controller as i installed an older 3Ware card and did not have the issue.
HAs anyone seen this or have any suggestions?
Thanks
Mike
Windows XP Pro

I am having a similiar problem. I just purchased a new computer with a raid array. I don't have any problems with the smaller ipods, but when the itunes library tries to update for my daugthers 30gb ipod, it freezes up part way thru and crashes one of the drives. I can rebuild but have yet to get the itunes library refreshed.
Desparate for help!!!!

[Solved] Move Software RAID 5 Array From NAS To Arch

Edit: I probably never had a problem at all, the error in dmesg probably just scared me, because after I disconnected it I noticed that /dev/d127 was 8.1 TB, the exact size of my RAID array node in my NAS which was /dev/md0, I just overlooked it. I reconnected it to my pc and mounted /dev/md127 to /mnt/raid and got this wonderful sight!
[bran@ra ~]$ ls /mnt/raid
data lost+found meta sys
[bran@ra ~]$ ls /mnt/raid/data/
data ftproot module _NAS_Media _NAS_Piczza_ _NAS_Recycle_RAID _P2P_DownLoad_ stackable _SYS_TMP TV USBHDD
download htdocs Movies _NAS_NFS_Exports_ NAS_Public nzbget-downloads PLEX_CONFIG sys tmp USBCopy
I bought a Thecus N4520 a few months ago and it's ok but programs crash a lot and they're hard to debug, apps have to be updated manually and the whole thing is moderately underpowered. I'm trying to move the software RAID 5 array from the NAS to my desktop, the kernel seems to detect that there is a RAID array but all these drives aren't part of it. I'm pretty new to RAID and I'm just getting my feet wet with it.
When I try to assemble the RAID array, it just tells me that it isn't an md array. How can I get it to build my array?
[bran@ra ~]$ sudo mdadm --assemble /dev/sdb /dev/sdc /dev/sdd /dev/sde
mdadm: device /dev/sdb exists but is not an md array.
Found this little chunk of info in dmesg, it says that the md devices have unknown partition tables.
[ 3.262225] md: raid1 personality registered for level 1
[ 3.262483] iTCO_wdt: Intel TCO WatchDog Timer Driver v1.10
[ 3.262508] iTCO_wdt: Found a Patsburg TCO device (Version=2, TCOBASE=0x0460)
[ 3.262585] iTCO_wdt: initialized. heartbeat=30 sec (nowayout=0)
[ 3.262933] md/raid1:md126: active with 4 out of 4 mirrors
[ 3.262961] md126: detected capacity change from 0 to 536850432
[ 3.263272] RAID1 conf printout:
[ 3.263274] --- wd:4 rd:4
[ 3.263276] disk 0, wo:0, o:1, dev:sdc3
[ 3.263276] disk 1, wo:0, o:1, dev:sdb3
[ 3.263277] disk 2, wo:0, o:1, dev:sdd3
[ 3.263278] disk 3, wo:0, o:1, dev:sde3
[ 3.263501] md: bind<sde4>
[ 3.264810] md: bind<sdb2>
[ 3.268262] async_tx: api initialized (async)
[ 3.272632] md: raid6 personality registered for level 6
[ 3.272636] md: raid5 personality registered for level 5
[ 3.272637] md: raid4 personality registered for level 4
[ 3.272905] md/raid:md127: device sdb2 operational as raid disk 1
[ 3.272908] md/raid:md127: device sde2 operational as raid disk 3
[ 3.272910] md/raid:md127: device sdd2 operational as raid disk 2
[ 3.272911] md/raid:md127: device sdc2 operational as raid disk 0
[ 3.273211] md/raid:md127: allocated 0kB
[ 3.273241] md/raid:md127: raid level 5 active with 4 out of 4 devices, algorithm 2
[ 3.273243] RAID conf printout:
[ 3.273244] --- level:5 rd:4 wd:4
[ 3.273245] disk 0, o:1, dev:sdc2
[ 3.273246] disk 1, o:1, dev:sdb2
[ 3.273247] disk 2, o:1, dev:sdd2
[ 3.273248] disk 3, o:1, dev:sde2
[ 3.273273] md127: detected capacity change from 0 to 8929230716928
[ 3.273322] RAID conf printout:
[ 3.273326] --- level:5 rd:4 wd:4
[ 3.273329] disk 0, o:1, dev:sdc2
[ 3.273331] disk 1, o:1, dev:sdb2
[ 3.273332] disk 2, o:1, dev:sdd2
[ 3.273360] disk 3, o:1, dev:sde2
[ 3.283617] md126: unknown partition table
[ 3.309239] md127: unknown partition table
[ 3.312660] md: bind<sdb4>
[ 3.318291] md/raid1:md124: not clean -- starting background reconstruction
[ 3.318296] md/raid1:md124: active with 4 out of 4 mirrors
[ 3.318333] md124: detected capacity change from 0 to 10736291840
[ 3.318385] RAID1 conf printout:
[ 3.318391] --- wd:4 rd:4
[ 3.318395] disk 0, wo:0, o:1, dev:sdc4
[ 3.318398] disk 1, wo:0, o:1, dev:sdb4
[ 3.318402] disk 2, wo:0, o:1, dev:sdd4
[ 3.318405] disk 3, wo:0, o:1, dev:sde4
[ 3.319890] md124: unknown partition table
[ 3.323462] md: bind<sde1>
[ 3.338094] md/raid1:md125: active with 4 out of 4 mirrors
[ 3.338225] md125: detected capacity change from 0 to 2146414592
[ 3.338253] RAID1 conf printout:
[ 3.338258] --- wd:4 rd:4
[ 3.338262] disk 0, wo:0, o:1, dev:sdc1
[ 3.338266] disk 1, wo:0, o:1, dev:sdb1
[ 3.338268] disk 2, wo:0, o:1, dev:sdd1
[ 3.338271] disk 3, wo:0, o:1, dev:sde1
Here's my full dmesg
mdadm.conf
# The designation "partitions" will scan all partitions found in /proc/partitions
DEVICE partitions
ARRAY /dev/md127 metadata=1.2 name=(none):0 UUID=d1d14afc:23490940:a0f7f996:d7b87dfb
ARRAY /dev/md126 metadata=1.2 name=(none):50 UUID=d43d5dd6:9446766e:1a7486f4:b811e16d
ARRAY /dev/md125 metadata=1.2 name=(none):10 UUID=f502437a:d27d335a:d11578d5:6e119d58
ARRAY /dev/md124 metadata=1.2 name=(none):70 UUID=ea980643:5c1b79e8:64f1b4cb:2462799b
Last edited by brando56894 (2014-04-21 22:51:01)

Sorry I numbered them to show the flow of information, this was also just a place for me to store info as I worked through it. I managed to get it to work by creating a partition that takes up the whole drive and is actually 22 GB larger than all the other drives (since I found out that the had root, swap and home partitions that are no longer needed).
I should be able to resize the other partitions without a problem, correct? They're EXT4. Should I unmount the raid array and do them individually, remount the array, let it sync and do the next? Or just unmount the array, resize all of them, mount it and let it sync?

Need help with formatting a software RAID 5 array with xfs

Hi,
i'm tying to format a software RAID 5 array, using the xfs filesystem with the following command:
# mkfs.xfs -v -m 0.5 -b 4096 -E stride=64,stripe-width=128 /dev/md0
but all I get is the attached error message. It works fine when I use the ext4 filesystem. Any ideas?
Thanks!
http://i.imgur.com/cooLBwH.png
-- mod edit: read the Forum Etiquette and only post thumbnails http://wiki.archlinux.org/index.php/For … s_and_Code [jwr] --

Sorry I numbered them to show the flow of information, this was also just a place for me to store info as I worked through it. I managed to get it to work by creating a partition that takes up the whole drive and is actually 22 GB larger than all the other drives (since I found out that the had root, swap and home partitions that are no longer needed).
I should be able to resize the other partitions without a problem, correct? They're EXT4. Should I unmount the raid array and do them individually, remount the array, let it sync and do the next? Or just unmount the array, resize all of them, mount it and let it sync?

Kernel Panic when using a new RAID 5 array

I recently set up a new Sans Digital 5 disk 7.2TB hardware RAID 5 array that's connected to a Sonnet Tempo-X eSATA 4+4 PCI-X card which has been updated to the latest drivers. The same card supports a number of JBOD enclosures that run as mirrored RAIDs under SoftRAID 4.0. My system is a 2.7Ghz DP Tower.
Upon trying to copy to the new RAID 5 volume I encountered a kernel panic and system freeze complete with wailing fans. After a few system restarts and a call to Sans Digital I tried to connect the RAID via USB upon the recommendation of tech support. Rather than causing a crash while copying I received an error message in the copy progress window that said that some files were locked and the process could not be completed and the RAID was no longer mounted in the finder.
I called Sans Digital back and they said it was probably a defective enclosure. I have just received a new one and have put that into service. All seemed fine until, when I was 30GB into a 900GB copy, the system froze. I have also tried to copy fewer files (400GB) and still get a Panic. When the RAID is idle there does not seem to be a problem. The last time the problem occurred the copy progress bar hung but the system did not fully lock up. The LEDs on the front panel of the RAID enclosure were flickering rapidly but no data was copying from my other drive. I turned off the RAID and was able to use my mouse again and restart my machine with a normal restart.
My system is running OS 10.5.8. When the RAID is off my computer runs fine.
Not sure what to try next. Any help would be appreciated - Thank you.

Hi-
I'd be interested to know if Sonnet has any comments regarding the issue.
In Utilities/Console/Logs, there should be some indication of what is occurring when the crashes occur.

Snow Leopard Installer Not Seeing RAID 5 Array

I currently have a Mac Pro with Leopard installed on an internal RAID 5 array. When I run the 10.6 installer to upgrade the only install disk choices I see are two external USB drives. The RAID 5 array is not in the list of possible install drives. Any idea what might be wrong here?

The fact it asked if you want to create RAID5 = Apple Pro RAID card was BTO and is present. Open it up, Apple's RAID card is there likely. And uses iPass so that your drive sleds connect to the controller rather than the motherboard Intel AHCI.
http://support.apple.com/kb/HT1346
http://www.apple.com/support/macpro/
Photo: http://support.apple.com/kb/HT3514
RAID5 capacity - http://support.apple.com/kb/TA24883
RAID5 discussion from before (myself, mbean, poster)
http://discussions.apple.com/thread.jspa?messageID=8446960
MaxConnect SAS/SATA Link for Mac Pro (iPass)
http://www.maxupgrades.com/istore/index.cfm?fuseaction=category.display&category _id=332
Apple Mac Pro RAID Card is an SAS controller
http://blogs.computerworld.com/applemac_pro_raid_card_is_an_sascontroller

Error in SATA RAID 0 array

Similar Messages

Maybe you are looking for