Raid (Disksuite) issue w/ Solaris10

On boot I am getting:
WARNING: md: failed to open. open error on /dev/dsk/c5t2d0s0
This array was in use and was working.
I checked c5t2d0s0 using #format->analyze (non-destructive read test) and it came back with 0 errors.
#metastat is reporting "State: unavailable". And doing "metastat -i" as it suggests doesn't change anything
d1002: Soft Partition
Device: d100
State: Okay
Size: 578813952 blocks (276 GB)
Extent Start Block Block count
0 201326688 578813952
d100: RAID
State: Unavailable
Invoke: metastat -i
Interlace: 32 blocks
Size: 782219520 blocks (372 GB)
Original device:
Size: 782220032 blocks (372 GB)
Device Start Block Dbase State Reloc Hot Spare
c0t1d0s0 330 No - Yes
c2t1d0s0 330 No - Yes
c3t1d0s0 330 No - Yes
c4t1d0s0 330 No - Yes
c5t1d0s0 330 No - Yes
c0t3d0s0 330 No - Yes
c4t3d0s0 330 No - Yes
c3t3d0s0 330 No - Yes
c5t3d0s0 330 No - Yes
c2t3d0s0 330 No - Yes
c2t2d0s0 330 No - Yes
c5t2d0s0 330 No - Yes
d1001: Soft Partition
Device: d100
State: Okay
Size: 67108864 blocks (32 GB)
Extent Start Block Block count
0 134217792 67108864
metadb
flags first blk block count
a m p luo 16 8192 /dev/dsk/c3t0d0s3
a p luo 16 8192 /dev/dsk/c0t0d0s3
a p luo 16 8192 /dev/dsk/c3t1d0s3
a p luo 16 8192 /dev/dsk/c0t1d0s3
a p luo 16 8192 /dev/dsk/c5t1d0s3
a p luo 16 8192 /dev/dsk/c2t1d0s3
a p luo 16 8192 /dev/dsk/c6t16d0s3

Check the order of the drivers you load in /etc/system......
it could be that you preload the md driver BEFORE your storage system is loaded

Similar Messages

P45 Platinum Raid 1 issues Intel vs Jmicron ?

I have been experiencing intermittent problems with Raid 1 installation using the Intel Controller.
Several problems were definitely due to HD errors and I have had two failed drives swapped out over the last six months.
However after the last drive replacement things seemed to be stable for several weeks before problems started to emerge again.
The interesting thing is that the problem had switched to the oldest drive in the system which until now had been completely stable and I'm now wondering if it’s an Intel Raid related issue rather than the drives.
What’s Happening:
I boot and both drives are recognised by the Bios.
Both drives show up in the Raid Bios screen
Once booted into windows one of several things happen.
1) Once drive is not visible and is reported in the Intel Raid Console as missing. Reboot and its back in a rebuild state
2) Windows boot proceeds normally and then one of the drives (always the same one) will go off line and be reported as missing. reboot and again the drive will be visible in the Bios and Raid Bios screen and be marked for rebuild
Once the drive has rebuilt it may be stable for hours or days or disappear again during the rebuild.
Drives are Maxtor STM31000340AS and a Seagate ST41000340AS, so essentially the same drive and both running the latest firmware updates.
Interestingly the port numbers reported in the Intel Raid Console for the drives is different from that reported in the Bios discovery and the Raid BIOS.
It is now always the Maxtor drive that goes offline where as previously it was always the Seagate. I’m now starting to wonder if its actualy a raid Bios/Console issue rather than the drives.
Has anyone else experienced similar problem in a Raid 1 configuration ?
I had been thinking about moving both drives over onto the JMicron Raid Controller but was uncertain if this can be done as a straight swap or if it’s likely screw up any data on the disks.
Again any experiences of advice would be welcome.

Thanks for the replies guys.
I have tried changing the SATA cables for the new types with the locking clips and ensured that there are no major bends in them, with no improvement.
I have also tested the integrity of the drives with Seagate’s test software using both the short and long tests, which show no problems when connected as IDE or ACHI (won’t allow me to test in RAID mode).
No problems reported but the drive still goes offline when reconnected in RAID mode. Which is partly what has made me wonder if there is a problem with the RAID BIOS, Drivers of Console Software.
Coupled with the fact that the drive which was being affected by the disconnections suddenly changed to one which had been stable for months and the drive that had previously caused problems has now become stable.
I’m also running the latest drivers and Intel Matrix Storage Console 8.8.0.1009, although I’m a little concerned by the number of outstanding bugs that are listed in the release notes, just indicates a poor product with almost 40 unresolved issues.
Currently I’m using standard RAID settings in the BIOS for the Intel ports with the Jmicron controller set to IDE but nothing connected.
The drives are essentially identical apart from the model number strings and the labels on the drives, both are at the equivalent level of drive firmware. Originally they were two Maxtor drives one of which failed with a hardware problem and was replaced by the Seagate equivalent, which is the same hardware and software with just the manufacturers branding being different.
Over the weekend I isolated the drive that was having problems, reformatted completely, performed a BIOS reset, re-added and rebuilt the drive into the RAID array.
So far its only been two days but things have been stable so far, although I have had periods of weeks without a problem before it reappears.
Sliksta, when you suggested updating the BIOS were you suggesting one of the Beta BIOS’s ? As I’m currently on the latest official release .

MAC PRO (Early 2008) RAID CARD ISSUE - SYSTEM FREEZEHello (hopefully someone can shed some light on my issue) I own as above a MAC PRO (Early 2008) this has a RAID card installed along with two 15k.7 cheetah hdd (320gb) and a spare drive, (which i m

Hello (hopefully someone can shed some light on my issue)
I own as above a MAC PRO (Early 2008) this has a RAID card installed along with two 15k.7 cheetah hdd (320gb) and a spare drive, (which i made a regular drive)
a while ago i had to replace the RAID card battery, so i did this, over a year later the same thing happened again, but as previous just left it and the system seemed fine for ages, until last night i was working in PHOTOSHOP and everything just froze and the screen kind of appeared GREEN, could not do a single thing. So restarted the mac, this time grey screen for ages and a message appeared, (macs version of blue screen) (see attached).
I restarted the machine and this time a flashing question mark folder!
could not do a thing.
so i found my copy of snow leopard and got the computer to run this and at least launch the DISK UTILITY and (Interestingly in the drop down menu RAID UTILITY was also in the menu) but it did not matter which utility i used the (RAID or DISK) neither could see any of drives, just the dvd drive.
so looked around on you tube and various forums and discovered if i take out the RAID CARD and re-plug the main lead from the RAID card back in to the LOGIC BOARD I would be reverting the MAC to a normal regular non-RAID computer.
After performing this HARDWARE task and inserting all three HDD, and running the DISK utility from the drop down menu via the SNOW LEOPARD disc.
(interestingly since the RAID card had been removed the RAID UTILITY from the drop down menu no longer appeared). running disk utility I can now only see the regular (spare) hdd and DVD Drive, but the two RAID HDD , again, still do not show up DISK UTILITY?
O.K. so i could chuck out the RAID card (AND RAID HDD) and just go with a regular set-up, and run a back restore from Time Machine on a NEW hdd purchased.
but what is wrong with the RAID, is the card at fault or are both HDD used for the RAID knackered? can i perform any tests, to see whats what?
thanks for your help in advanced.

hello people, the issue was in fact the GRAPHICS card nothing to do with the HDD or RAID system ( although this did cause issues with the RAID system it basically lost its way) below is my replay to another similar problem some one else had!
working in photoshop and then everything stopped working and the lot froze! only option was to force shutdown (via button).
and try to restart, hoping all was fine, this was not the case :-(
I had the added issue of the RAID card system, that i have, this was confused to say the lease and would not behave or work, causing the start up to hang.
so i thought the HDD must be bust and the root cause. ( but soon learnt it was not the cause )
...bought a new HDD removed the RAID card and replugged the cable from RAID card into LOGIC board, ( making the computer act like any normal non-RAID system). I managed to install the OSX, using the snow leopard disk way. once the mac was running, i started to notice the screen would flicker and started to see 'artefacts'. so i started to reveal my symptoms to the web and forums and soon discovered that my graphics card could be the issue all along?.
(nvidia geforce 8800gt 2x dvi).
I read up on that a fix, could be either A. reply the thermal paste, as the card could be over heating or B. stick the card in the oven trick.
Tried option A. first and nothing still issues, so last night took the plunge carried out option B. and ta da it worked! i even managed to run
from my new HDD my lasted install OS X, absolutely fine. I then thought, maybe i could repair my RAID so replugged all the HARDWARD back in and
carried out a disk repair and disk permissions on drives( took a small amount of time), via the SNOW LEOPARD disc - (Disk utilities) and this worked and now have my system working as it was just over 6 days ago.
what was the cost to get this? bought a new hdd so 40.00gbp and thermal paste and cleaner kit ( your still need to do this ) search video card trick on you tube.
and renew thermal paste, approx 15.00gbp, technically i don't need the new HDD, but it was all part of the trial and error way i went. ( i do have extra storage as a result!)"

[RAID 0 issue] - K7N2 Delta ILSR:how can i save my RAID-0 SATA DISK datas

Hi all, as a new member, i have to underlign the fact that this forums' members are very active and helpful ( personally, i thank the front usb issue post author ).
I've an XP on a single SATA RAID-0 disk ( Promise Fasttrak 3xx duno ), since a few days, i think that the DRAM controller is KO because the mobo doesn't accept DDRAM anymore ( DDRAM is OK on other PC ). The Mboard makes long & regular beeps and i have no Video ( no BIOS & no POST ), the D-bracket indicates no memory module or memory damaged ( case 4, led 4 is the only green ).
If u have an idea to help me..
If there's nothing more to do, how can i recover the HDD's datas ? They are very important..i've heard that the disk should be plugged on the same raid chipset ( the better is the same Mboard )
Please can you help, and sorry for my French-english
EDIT: I'll fulfill w/ more specs this WE.

Just plugging/unplugging the memory somethime solves the problem. You could have had a bad insertion or just dust in the slot. Good luck with your working computer
I already answered your RAID concerns. RAID0 with only 1 HDD is no RAID at all, just a software trick to force the controler to use the drive.
Quote from: frenchy2k1 on 02-April-05, 04:15:32
If your drive is raid0, but only 1 drive, it is no RAID at all, so it should work like any disk on any computer and be recognized normally.

RAID 1 Issue - One array becomes two

All:
I have setup a RAID 1 array with two identical segate SATA 150 drives. This was a clean install, and everything went without a hitch. My problem is this: after a week or so, I would boot the PC and The BIOS RAID array would say "Error--Degraded." It took a long time to boot, but was fine and when I got into Windows, my C:\ drive was joined by a D:\drive (the second Seagate.)
I shut down, rebooted, and went into the RAID BIOS. The second drive had magically gained its own array (non-bootable), which I deleted. The PC booted fine with a healthy RAID array, and all was well.
Until it happened again a day later. And again. And again. Basically, the array doesn't stay stable for more than a couple days. I even swapped out the drives with Seagate as they were clicking. The new ones are good, but the problem still occurs.
I have not experienced any data loss, but am mystified as to what is going on here...Any help would be greatly appreciated!
Thank You,
Michael Tschirret
MSI K8N Neo2 Platinum Edition v 1.40
Athlon 64 3200+
1 GB DDR 2700 SDRAM (2 512MB sticks)
2 HDD 160GB|Seagate Barracuda 7200.7 Sata 150
1 WD 100GB External IDE hard drive
Sony CD-R/RW DVD +/- R/RW
TDK CD-R/RW
1 Floppy drive
SB Audigy 2 ZS Platinum
eVGA GeForce 6800GT

I'm having the same problem, except I am using 4 hdds in RAID 0+1. one drive dropped out and the machine crawls now. Could it be an issue with SATAI vs SATAII? I have 4 Seagate Barracuda 120GB drives, but they were purchased over a two year period, so I suspect their firmwares vary a bit...
Any help would be much appreciated.
BTW, I have the latest BIOS installed (v1.B)

RAID blocking issues with the new d2 quadra

I just bought 2 of the newest 500GB d2 quadras and I attempted to set up a level 1 RAID with them daisy chained to my imac via firewire 800 and using disk utility. When I went to set the RAID Block size to 256k and create the RAID I got the screen of death. I then restarted and it did it again on start up. I unplugged the drives and started the computer back up and tested each one individually. I reformatted and tried again, same thing happened.
I took them into the apple store and it happened again on their computers. We tested other Block configurations (32k, 64k, 128k) and they all worked except 256k. The genius's didn't know what the problem could be. A Leopard issue, hard drive issue, or what else.....
Is anyone else having this issue? Should I be worried that there is an issue with one of the drives I am trying to RAID and return and get a new drive, or should I just set the block to 128k and not worry. I am pro photographer and am going to be storing and accessing RAW files in large amounts on these drives. What are the benefits and drawbacks for 128k formatting and 256k formatting?
Any advice would be great! Thanks!

marisaholmes, welcome to the Apple Boards,
This board is for the discussion of a specific piece of Apple Hardware called the Xserve RAID. I think there is probably a more appropriate board for this question where you are more likely to find an answer.
Sorry, hope this helps,
=Tod

X-58 Marvell Raid 1 Issue

Hello all,
I'm new to the forum, and pretty new to the high performance computer world. This is my first build and my first new computer in 9 years so my ignorance level is high.
Up until today the new machine worked fine. After trying to load Office 2010 the computer took a very long time to shut down and then would not reboot. The Marvell setup shows a degraded array, with 1 HDD out. Under "Free Physical Disks" it shows simply PD 8 for the missing drive; When I highlight this I'm presented the option to "Erase RAID Config Data". Then the warning about damaging the array on this disk comes up.
My first question is should I go ahead and erase the RAID configuration on this drive?
I'm trying to avoid having to reload the whole thing, but if that's what it takes, better now than later.
I see there have been some issues with the Marvell RAID system. Would I be better off to move the HDD's to 1 and 2 and use the Intel drivers? If so, will I lose the array when I move them?
By the way, I'm running Windows 7 Ultimate.
Thanks in advance...
Ed

Are the HDD's the WD SATA 6Gb/s drives? if so, they would perform best on the Marvell controller I would think. Possibly a bios update may help, as well as an update to the Marvell if a more current version is available. I'm not 100% positive, but it seems some SATA 6Gb/s WD's of a certain revision group needed a firmware update.
Quote
Would I be better off to move the HDD's to 1 and 2 and use the Intel drivers? If so, will I lose the array when I move them?
I believe the array would be lost. Also, if they are the 6Gb/s drives, they would need to be jumpered to work on the ICH10R.

Can we make a sticky for the RAID shutdown issue?

Hi guys - I'm new to the forum...
I'm experiencing the hanging shutdown issue with my K8N Neo4 Platinum board and SATA Raid 0 in XP. I've searched the forum for answers, but think it would be a good idea if someone made a sticky of this as its a popular problem.
If not - has anyone got a final fix?
I've got version 1.B bios with 6.70 nVidia drivers - still no joy!

I have two k8n neo 4 platinums that are doing the same thing.
I installed a clean drive & a basic windows install (no dedicated drivers) & flashed the bios to 1.c. Same issues. Msi says it is a hardware compatability issue , I say BS!
After speaking with Nvidia they supplied newer driverd than the 6.70. The problem went away. However these drivers are not stable. I am having other issues. And am still working with Nvidia to solve them.

Raid Battery issues....

I keep getting a warning for my Raid battery...saying write cache temp. disabled due ti insufficient battery charge.....Restarting does nothinng...Leaving system on for 72hours does nothing......

Does this RAID enclosure have a Battery itself that needs replacing, or is it the Mac's Battery? Is there a UPS involved?
a hardware RAID controller may carry a dedicated battery-powered write-back cache of its own, thereby allowing for efficient operation that is also relatively safe. Fortunately, it is possible to avoid such problems with a software controller by constructing a RAID with safer components; for instance, each drive could have its own battery or capacitor on its own write-back cache, and the drive could implement atomicity in various ways, and the entire RAID or computing system could be powered by a UPS, etc.
http://en.wikipedia.org/wiki/RAID
Mac Pro Raid Card - Battery issues...
http://www.mac-forums.com/forums/other-hardware-peripherals/157895-mac-pro-raid- card-battery-issues.html
The RAID card reconditions its battery from time-to-time. During the interval when the battery is discharged, it may report that the RAID cache is disabled (and you are enduring longer writes because of that). It should charge up and start using the write cache again within a few hours.
https://discussions.apple.com/thread/2684029?start=0&tstart=0

K8N Neo2 Platinum RAID Boot Issue...

Hi everyone,
I am running two WD 120gb drives in single-drive mode. Everything is working fine. My issue is that every time I boot, I have to wait nearly 10 seconds for a message that says 'Detecting Array' just before it loads WinXP. The thing is, I have RAID disabled in the BIOS. How do I get rid of this annoying boot message?
Any help would be appreciated!

Quote from: JayBee on 21-November-05, 05:01:29
The are still making the K8N Neo2- F which is the same thing except no firewire and one gigabyte lan instead of two lans. Otherwise, same mobo with same bios. MSI 7025.
or if you´re lucky and your reseller has them in stock..that was my case wus supposed to change my cpu cooler(amd athlon 64 3500+(venice) ) removed everything...to note...I did this with another friend..so after a little while when all the things were on place I hade to take a number 2, when I got back the comp was all fixed and my friend asks me to start it..I start it and nothing happens..turns out that he had used all of the copper paste and drenched the socket and the spu...so i tested the cpu and it had survived, but the motherboard was all dead..so I rma´d it as u guys say and I got the same modell back and everything worlks perfectly...and as for my friend...he has two blue eyes @ the moment :P

P6n sli platinum (raid setup "issues")

got 2# 320 gig seagates formated and ready (sata)
the system was up and running fine on 1 hard drive and windows xp-pro
reformated 1st hard drive and want to re-install XP but in raid O now...............
I am booting from my floppies, when instructed to hit F6 to install raid controllers off another floppy....
the damn system won't allow me...... I hit f6 quite a bit and can never get into the installation of the raid controllers?
any ideas?

I can remember having a similar issue when I installed a RAID system for the first time. It turned out to be the keyboard. I had a MS keyboad and it turns off the F-Keys on defult. There is a function key toggle button just to the right of the f-keys. you need to hit it as soon as the bios shows up on the screen. then you should be able to get the F6 key to work.
also, make sure you have the raid turned on for your drives in the system bios, then you need to activate the raid volume in the raid bios.
hope this helps.

P6N SLI Platinum (MS-7350) Bootable Raid Array issues

Attempting to install XP on bootable SATA Raid after text portion of install on reboot receive error message.
"A disk read error occured"
Manual has incorrect dir structure x:\nvidia\system\c55+mcp51\raid <-- does not exist
there is a sataraid folder under xp subfolder which appears to contain the storage controller drivers.
Additionally have attempted to download the sataraid drives from the website with the problem
During the Windows text install it does appear to see the drives as I can format them and install the setup files accordingly but it shows both drives which set to striping I would expect to see only one drive as listed in the bios "Sata Raid XXX.XX"
These drives are good I have tested them on another system without an issue.

Quote from: garley on 04-May-07, 09:41:59
Alrighty,
So just to recap,
You have two Disks you are trying to setup as Raid 0? (What size drives?/ model?)
You have them connected to sata connector 1 and 3, No other drives connected?
Cdrom as master on Secondary IDE Controller and Primary disabled in the bios?
SataRaid is set as the 1st boot device in boot sequence and CDrom second, Third device disabled.
And you have the same drivers I used from Nvida.
Right. They are WD Raptor 150 GB ADFD 10,000 RPM drives.
Correct. SATA1,3. No other HDD's installed.
DVD on IDE2 connection on Mainboard...shows up as Secondary IDE Master in BIOS. I had the Primary IDE Master set on "not installed", and it shows up as "not detected" in the BIOS.
I HAD the boot sequence as: DVD, RAID, disabled. I changed the boot sequence to Raid, DVD, disabled, did the "save and exit" and it went to a black screen with the cursor blinking. So I powered off wit the power button, waited 15 sec, then powered back on with the power button...same thing...black screen with blinking cursor. If I set the order back to DVD, SATA, disabled, I get back to the point I was where I started, that is: bios showing everything right, but xp install showing two drives. I don't know why it gives the black screen when the RAID is set to first boot since it is supposed to skip it if it doesn't work and move on to the next in line, which would be the DVD.

Raid card issue - missing drive

I have bought some new Mac Pro 2010 Dual 2.93GHZ Xeon (6 core) machine, with Raid Card and 4 2TB drives and then set up a Raid 1 and a Raid 0 on the machine striped for safe&speed as I use the machine for video editing and motion graphics. From the first day, I have issues with 3 machines (out of 5): the raid keeps failing. Both raids work fine, then without warning the Raid Set falls over. Every time it has fallen over, it is usually when the drives and the Raid are not being used. It commonly gives me this type of error - Drive 3:5000cXXXXXXXXXXXXXXXXXXXXX failure detected - Primary disk port unusable, previous drive status was inuse, followed by Drive 3:5000cXXXXXXXXXXXXXXXX missing - Previous drive status was inuse. The drive (Bay 2 usually) in realy mising from RAID UTILITY Tool. After reboot the drive reappears and I can make it Spare, in order to rebuild the volume. In the first instance I thought it's about Power Management, but even after disabling HDD power off, I have the same situation.
Apple dealer is still looking at one machine, but... Did anyone meet similar behaviour?

I'm having the exact same problem, or at least really similar.
I thought I'd configure everything as RAID-0, all brand new drives. Those shouldn't crash very fast.
Big mistake of course... But the weird thing is, in the RAID_Utility it says all the drives are "green" smart: checked and status: good. But it removed one of the disks from my raid. Is there any way I can "plug" that drive back into my raid set? Because the drive is ok, but it's just de-coupled from the set....
ty!

890GXM-G65 RAID 5 Issues (SB850)

Hi all
Hopefully you guys can help me, I am hours and hours into this by now. My 890GXM-G65 does not want to cooperate with me to make a 3x4TB RAID 5 array using Seagate ST4000DM000 HDDs. I can get it to build the array and it will show up in windows/RAIDXpert, I am able to do a quick format and it shows up in explorer. So far so good. Start to transfer data and within ~1 min RAIDXpert tells me the array went critical or it will BSOD with AHCIx64.sys as the error and DRIVER_IRQL_NOT_LESS_OR_EQUAL. If I reboot the drive on port 3 is now shown as a single disk but it is there again and I can re-create the array. RAIDXpert will show port 3 as disconnected if it does not BSOD and will re-appear after a reboot, but as a single disk just like when it does BSOD.
Interestingly if I delete the Logical Drive and reboot, the single disk will come up as a failed array, as if it somehow got split off into its own Logical Drive, but it will not show as an LD when the main 2 disk part still exists.
I have tried switching the drive around to isolate if it is a particular drive, but no matter what drive is connected it is always port 3 that is lost.
I have tried different cables, no luck.
I have tried replacing the motherboard, no luck (yes I actually have a spare board, lol).
I have even tried replacing the CPU as this one is somewhat old and abused, no luck.
I have re-installed windows, no luck.
I have tried a different PSU, no luck
I have tried different RAM, no luck
When I switch the controller to AHCI mode in the BIOS I am able to do a full format on each individual drive just fine so I believe the drives to be fine
In RAID mode trying to use as individual drives, when I begin to transfer data to the drive on port 3 the drive simply disappears until a reboot.
At this point I am completely confused, does the SB850 not support 4TB drives? Before the reinstall I tried with 3x 500GB drives and it would still crash the system, but it would not kick a drive out of the array as consistently. I have not had a BSOD since the windows reinstall however, only the RAIDXpert telling me the array failed.
Does anyone have any advice or ideas at all? I am completely baffled at this point to where I am looking at replacing the whole system or getting a RAID card, only issue is I only have the PCI slot free to put a card into.
Here is the entire spec list
Proc: AMD Phenom II x6 1090T
Mobo: MSI 890GXM-G65
RAM: 16GB Corsair Vengeance 1866
GPU: Visiontek LP HD 7750
PSU: Seasonic 300W Gold TFX
SSD: 128GB Samsung 830
HDD: 3x 4TB Seagate ST4000DM000
Optical: Silverstone Slim BD-R
Add-Ins: ASUS PCE-AC66 Wireless
Silverstone EC-04 USB 3.0 Card
Rosewill RC-120 SATA 150 card
Case: In-Win BL040.300TB3LF Low Profile mATX
Yes there is a ton of stuff packed into a very small space.

Looks like I'm the only one with this issue
I did some experimenting, basically trying different SSD make/model but otherwise keeping setup identical. Instead of Kingston V300 I attached Samsung 840 Pro 120GB to this system hoping that it could be SSD-controller specific problem. Unfortunately nothing has changed - I still have grave issues with waking up from S3 sleep. Now I'm inclined to believe that this is the problem with RAID controller on motherboard rather than Kingston drive issue. Too bad, I like this motherboard but looks like I have to start thinking about replacing it with something else. Guess I would be looking at some other vendor/chipset then.

XServe 2006 RAID Card Issues

Basically, I was gifted (some gift!) a Late 2006 XServe 2.0GHz Dual QX, with 4 GB RAM, and basically was told 'It does not boot. We give up.'
So heres what I have found so far..
It has an Apple Raid Card (don't ask me much more than that, or ill have to tear it apart again). But the 10.4.10 Install disk doesnt show the Raid card or drives (SATA Apple Drive Module 80.0). So is my card toast? Not supported by 10.4? Need a direction to run at because this thing is starting really get under my skin.
If I use a SATA Drive bay via USB (WD 80GB Drive), the disk appears, but the Server won't last long before it Kernel Panics, but it works during Installation Media Verification..
In the meantime, Ill tear apart the server again (Only a few minutes) and get the Raid Card ID.

An easy way to see if it's a raid card is on the part of the RAID/Backplane you can see when you slide the top cover off, if it has 2 chips with silver heatsinks on it's a RAID card if it's 1 chip it's a backplane. The RAID Card also has a small connection for a RAID battery..
as for why it doesn't work.. Have a look at the following
1) Do the drives light up when you start the machine.. You should see a green light (always on) and a blue activity light which should flash.
2) If it doesn't then there is an orange ribbon cable that goes from the RAID/Backplane to the logic board. Make sure this is properly connected and doesn't have any breaks in it.
The RAID card will work in a non raid configuration so you don't need to get rid of it if you don't want to. An easy option to check the server would be to install 10.6 or Lion on a USB stick and start the server up for it by plugging it in and holding down the ALT key when you power on the server. From the system profiler you should be able to see if it recognises the RAID card (Hardware RAID) and also if it passes it's diagnostics test.
There are of course a lot of things that could be wrong with it.. You can remove the RAID/Backplane board and start the server up from USB/Firewire to narrow down your testing.. One thing the 2006/2008 servers are pretty cheap on eBay in working form so you might find it better to get one from there. The 2009's hold their value a lot more as you can still install the current OS on them..
Hope that helps
Beatle

Raid (Disksuite) issue w/ Solaris10

Similar Messages

Maybe you are looking for