Mirrored RAID degraded, upper slice shows "failed" but drive passes verify

Hello,
I have a mid 2010 Mac Mini running Mountain Lion and Server. The Mirrored RAID is showing degraded and that the upper slice has failed. However, doing a verify of the drive does not report any problems.
Is there a way to determine if this is just a RAID management issue? I've considered rebooting into single user mode and running fsck but not sure what else it will tell me?
Is it safe for me to click on the slice that is showing "failed" and hit rebuitd? (after verifying a good back up of course). I started down this path but didn't like the warning OS X provided; it was not crystal clear which physical drive it would erease the data from.
Thanks,
Tim

I meant to add that boot up reports:
AppleRAIDSet: addMember() detected expired sequenceNumber (1) for member _______big id_____
AppleRAID::restartSet - restarting set "Harddrive name" (______another big id_____)
CoreStorage: fsck_cs has finished for group " ______yet another big id________" with status 0x00
CoreStorageFamily::unlockVEKs) failed to unwrap the vek, status = e00002bc
- Tim

Similar Messages

MacMini Mirror RAID degradated, 2nd slice failed

I have a Mac Mini Server Late 2012, with the following specs:
- 2.3 GHZ I7
- 10 GB RAM (1x2 GB, 1x8 GB)
- Dual 1 TB HD 5.400 RPM
- OSX Maverick 10.9.5
- Mirror RAID
Apparently an error with OwnCloud caused the disk to get almost full. I found the problem, deleted the files and then ran disk utility and, for my surprise, I found the raid hd (serverhd) marked as "degradated" and the 2nd disk marked as "failed":
Running diskutil on terminal confirms that the 2nd slice as "failed":
My questions are:
1. Does the failed status on disk1s2 means that the disk PHYSICALLY failed or that the data in the disk doesn't match with the one in the 1st disk?
2. If this is a data failure, how can I rebuild the data in the 2nd disk? By selecting the failed disk in disk utility and hitting Rebuild?
TIA
Victor Espina

I finally solved this issue:
1. Made a full copy of server's HD in a external disk using CCC
2. Changed boot drive to use the external disk. In theory, this was not needed but I prefered to boot from a different disk just in case.
3. Once booted from the external disk, when to Disk Utility and "demote" the failed disk from the RAID array.
4. Using Disk Utility, I reformated the failed disk and added again to the RAID set (to do this, select first the RAID set and then drag & drop the disk from the left panel)
5. Once the disk was added to the RAID set, I pressed Rebuild and waited until de RAID set was rebuilt.
6. Then I set the HD as the boot drive and restarted the server
Thanks all for your help on this.
Victor Espina

Destroyed mirror RAID (1), Want to get data, but how?

I had a degraded mirrored RAID set that was functioning in its degraded state - reads and writes were no problem.
I thought that if I used DiskUtility to destroy the RAID, it would convert the drives to normal drives, and I would have access to each individually, but this was not the case. I also thought the data was backed up, but this was not the case.
I used the minus sign in the RAID tab DiskUtility to destroy the RAID. There are now 2 drives, but neither is able to be mounted:
bash-3.2# diskutil list
/dev/disk0
#: TYPE NAME SIZE IDENTIFIER
0: GUIDpartitionscheme *698.6 Gi disk0
1: EFI 200.0 Mi disk0s1
/dev/disk2
#: TYPE NAME SIZE IDENTIFIER
0: GUIDpartitionscheme *698.6 Gi disk2
1: EFI 200.0 Mi disk2s1
2: Apple_HFS 698.3 Gi disk2s2
If I try to verify the first disk:
bash-3.2# diskutil verifyDisk disk0
Error encountered attempting to verify/repair disk0: Unrecognized filesystem (-9958)
but if I try to mount it, it thinks the mount is successful, but nothing new shows up on the Desktop, nor with "df"
bash-3.2# diskutil mountDisk disk0
Volume(s) mounted successfully
in reality, the drive is NOT "mounted successfully."
disk2 is in worse shape, as the OS is not even fooled into thinking it is mountable:
bash-3.2# diskutil mountDisk disk2
One or more volume(s) failed to mount
So I am trying to put my recovery efforts toward disk0.
Any ideas on how to mount the drive and get data off of it?

I had the same issue a few months back.
1 drive of my mirroed raid died. So I took the working drive out of that box and put it in a FW enclosure. It mounted fine. However after converting it back to a regular volume it would not mount. I tried everything thing I exhausted google searches.
the only fix was to reinitialise the drive. Luckily I had the data backed up elsewhere.

Mirrored RAID not mounting/not showing as RAID (Disk Utility)

I have 2 Lacie Firewire Disks set up as a mirrored RAID (created by Disk Utility). I've been using this setup for about a year with no issues. But today I tried mounting the RAID and I got this msg twice (one for each drive)...
"Disk Insertion - The disk you inserted was not readable by this computer."
It then asks if I want to Initialize, Ignore or Eject. If I leave this msg up for a bit it eventually just goes away. But the disks never load.
I opened up Disk Utilities to check and see if the drives were listed and they are, but the RAID is NOT listed. All of the first aid options are greyed out. I tried to mount each disk but they will not mount, I assume because the RAID info has been lost?
Is there a way for me restore the RAID or at least get my info off of the drives? They contain a large photo library that cannot be replaced.
Powerbook G4 Aluminium 1.33gthz Mac OS X (10.4.7)

I never technically fixed the RAID. I used the program Data Rescue mentioned above to look at the drives and pull my data off of them. What I found was one of the drives was in perfect order, and the other drive had stopped recording data MONTHS ago. Basically the RAID became un-paired and stopped working correctly, and only one of the drives was saving the data. It freaked me out at first because the drive I decided to recover first was the one that was missing data. But I then looked at the 2nd drive and it had all my data on it, and I was able to recover it.
Anyway, Data Rescue worked perfectly. Now I just have the drives running independently. But I am staying away from the apple software RAIDs for now, as I did some reading and they seem to not be so trustworthy.
Also, Data Rescue takes quite a bit of time to pull all your data off, especially when you have a couple hundred gigs of data. Hopefully this helps.
Sam

SWIM Jobs show failed but all images are in flash

I performed a software distribution on two different 3750 switch stacks using LMS 4.2.3 over a WAN link.
The Job Report shows this:
Copying c3750-ipbaselmk9-tar.122-55.SE4.tar from Software Repository to tftp-specific directory.
Copied successfully to C:/CSCOpx/tftpboot/rep_sw_3381422663941666305
Loading image file to flash device : rep_sw_3381422663941666305 --> flash1:c3750-ipbaselmk9-tar.122-55.SE4.tar using TFTP
Error loading image to Flash. See C:\CSCOpx\files\rme\jobs\swim\5373\3750Stack_telnet.log for the output from the device on which the image transfer failed.
Image Copy Operation Failed
Device is unlocked.
Device Upgrade Result : Failed
However, when I look at the flash on both stacks, the IOS image with the correct filesize, folders, etc. all looks right. The show boot shows it will boot to the correct image. The telnet.log file shows all the files being copied and just ends after the last file (the .bin image).
Does anyone know why this might report as failed even though the files are in flash?
I have not yet reloaded either switch as they are in production.
Thanks.

OK I reloaded one of the stacks and it came up fine.
Could this error be due to the fact that the upgrade was done over a WAN link and I did not put exec-timeout 0 0 on the line vty?

TestStand One step failed but UUT Passed

TStand 2.01, OS 2000, report format Txt.
My test run OK, the step failed (STEP:LBH_LeakP, Measurement[0]). However, at the top, the UUT status = passed. Please help it should be failed
Attachments:
[0401132261610001][3_1_04].txt ‏24 KB

Trout00 -
Check to see if the option "Step Failure Causes Sequence Failure" is set for this step on the Run Options tab of the Step Properties dialog box. If it is set and the failure is not propagating, please attach an example sequence that causes the behavior that you are referencing.
Scott Richardson (NI)
Scott Richardson
National Instruments

How to recover data from failed drive that's part of mirrored raid

Hi Guys,
hope to get help from someone knowledgeable out there. I have a macpro and recently experienced a failed drive. I set up that failed drive as part of a mirrored raid, this set is not my primary drive and so my computer is stilling up and running but now am wondering how I access the data from the mirrored drive. Should the mirrored drive automatically mount on my desktop whereby I would be able to access the files? This is my first drive failure and I was under the impression having a mirror would duplicate my data and allow me to access it in situations like this. I'm a bit of novice in this area and not sure if the data is truly on the "mirror" or if there are things I need to do.
I launched disk utility and was able to see the mirrored drive and I selected "mount" drive but it would not mount; I then selected "verify" and got "unrecognizeable filesystem" Is this normal? Am I suppose do something to get access to the mirrored drive? Do I install a new drive in place of the failed drive and expect the raid to rebuild automatically whereby I then see the data?
Your help is much appreciated.

Even with a mirror, you still need a backup.
Along with Disk Utility, you still need 3rd party (TechTool Pro 5, Disk Warrior 4.1.1+).
And if you like to use RAID and esp mirror RAID, consider
http://www.softraid.com which is a step above (the pdf guide, manual you can download and they have a demo, so worth the read). SoftRAID can also import/convert an Apple RAID to its own format which has been known to recover drives and data.

Mirro Raid can you use a single 4TB disk with 2 partitions for mirrored raid ?

Hello,
I have a new 4TB hardrive.
After lots of reading, i was thinking that i could partician the drive to 2 (2TB) Then create mirror raid.
Essentially thinking that i would have photos on one of the (2TB particions) and they would mirror on the other ?? as a double copy storage.
I can partician okay and the try to drag the two particians onto the "mirror raid set" and ithe following message displays :
"Can't add Seagate expansion disk" to the raid set because another volume from this disk is already part of the RAID set"
I'm now thinking i need to purchase another 4tb hardrive for this to work ?
Or if you "mirror raid set" is it actually particioning the drive and creating a copy ?
Forgive me... i'm not really very up skilled with disk utility, and basically just don't understand.
Looking forward to some help and advise
warm regards Tracy Gr

It doesn't make any sense to mirror on the same drive. The idea behind mirroring is that should one disk in the raid set fail your data is safe on the other disk. Mirroring to partitions, if it's even possible, would only bring you disaster when the drive fails because you would lose the complete raid set and all of your data. If you insist on mirroring buy another drive.

Service Pack Update Upgrade Status showing failed

I have SharePoint 2010 Server. I upgraded the same to SP2. In upgrade status it shows failed but once I run command
(get-spserver $env:computername).NeedsUpgrade.
It shows false. How to check if patch is successful?
Please remember to mark the replies as answers or vote as helpful if they help.

Hi,
From your description, my understanding is that upgrade status shows failed when you upgrade SharePoint, but when you run PowerShell Command, it shows “false”.
Have you run the SharePoint Configuration wizard again after the status shows failed, then check if it will show successful status?
As upgrade status is failed, you should check if there are some error message in your USL log.
In addition, you could check the version of SharePoint if it is upgraded to the correct version number.
Best Regards
Vincent Han
TechNet Community Support

Testing a Mirrored RAID

I created a mirrored RAID out of 2 500GB LaCie FW drives. It appears to have been successful and I loaded about 100GB of info onto it. They are connected to a G4 dual 1.25 running 10.4.x.
How can I test it out to be sure that the 2 drives are, indeed, mirroring themselves? Can I somehow inspect the contents of each of the individual drives, apart from the RAID?
I'd had to count on the redundancy and then find out that it was not working correctly.
Typomarx
G5 dual 2.0 Mac OS X (10.3.9)

I not mirroring my local drive.
I have an external FW drive that I put my jobs/important files on. This IS my back-up.
I work on them on my local drive and then copy them to the FW drive when I've finished.
I'm mirroring THAT drive so that my jobs are all backed up on a redundant drive.
As needed, I recall jobs from that Jobs "server", work on them locally and then recopy them back to the "server." Truly a poor man's server.
If I'm working on a job on my local drive and my Mac craps out and takes the file with it -- it should not affect my jobs and back-ups at all.
Or so I'm hoping.
Then if one of the RAID disks craps out, I haven't lost everything. I have the other one which contains a complete record.
I can than fix/replace the faulty disk and be on my merry way.
Does this sound reasonable?
Typomarx

New iMac 750 GB Hard Drive Fail Smart Drive Test - Glitch or Problem

Greetings!
I have a new 24" imac with 750 GB hard drive which has had problems out of the box (system crashing several times a day/unable to re-start/application crashes/general sluggishness).
Five re-installs of Leopard (upgrade/clean install/install and erase)in five weeks when I finally used the latest version of Drive Genius and TechTool Pro (4.6.1). Both claimed hard drive problems. Specifically, TechTool Pro reported smart drive failure (see report below, please).
This seemed to confirm my suspicions that something was flawed with my iMac from the start.
I have returned the computer for a new hard drive.
The Apple-approved repair shop says they've installed a new 750 GB had drive sent by Apple and when they run TechTool Pro, they get the same smart drive failure report. The techie claims this is either a glitch with TechTool Pro, or with the hard drive, but that I have nothing to worry about.
What's your opinion?
Many thanks for taking the time to read this.
SMART
Saturday, December 29, 2007 1:18:12 AM US/Pacific
S.M.A.R.T. Self-Checks <Failing!>
Model: ST3750640AS Q
Mount Point: /dev/disk0
Capacity: 698.64 GB
Writable: Yes
Ejectable: No
Removable: No
Bus: Serial ATA
Bus Location: Internal
Revision: 3.BTH
Serial Number: 5QD2JVNE
disk0s2: Ma
disk0s3: Pa
disk0s4: Peppi
S.M.A.R.T. stands for Self-Monitoring Analysis and Reporting Technology. This test checks and reports on the status of the S.M.A.R.T. routines built into your drive. These routines monitor important drive parameters as your drive is operating. An examination and analysis of these parameters can aid in the prediction of drive failure. This will allow you to back up your data before your drive fails and the data becomes inaccessible.
S.M.A.R.T. Self-Checks
Attribute Normal Worst Threshold Status
1 Read Raw Error Rate
100 253 6 Okay
3 Spin Up Time
95 92 0 Okay
4 Start/Stop Count
100 100 20 Okay
5 Reallocated Sectors
100 100 36 Okay
7 Seek Error Rate
78 60 30 Okay
9 Power On Hours
100 100 0 Okay
10 Spin Retry Count
100 100 97 Okay
12 Power Cycle Count
100 100 20 Okay
187 Unknown
100 100 0 Okay
189 Unknown
100 100 0 Okay
190 Unknown
41 37 45 Failing!
194 Temperature
59 63 0 Okay
195 HW ECC Recovered
63 61 0 Okay
197 Current Pending Sector Count
100 100 0 Okay
198 Off-Line Scan Uncorrectable Sector Count
100 100 0 Okay
199 Ultra DMA CRC Error Count (Rate)
200 200 0 Okay
200 Write Error Count
100 253 0 Okay
202 DAM Error Count
100 253 0 Okay
S.M.A.R.T. Self-Checks <Failing!>
Tests Completed
Threshold levels are exceeded occasionally. You should consider backing up your data from the hard drive. You should continue to check the hard drive for failures.
S.M.A.R.T. Self-Checks <Failing!>
-end-

Greetings, all!
This has been my first posting, despite having owned 5 Macs over twelve years - which goes to show you how reliable they are, most of the time.
I am very impressed with the thoughtful responses, and I really, really appreciate you taking the time to respond.
Here's an update since my last posting. I picked up my repaired(?) iMac from the Apple-approved repair shop. The technician's report said (referring to the original hard drive Seagate ST3750640AS Q) "The drive has passed and boots into the OS without issue. Confirmed the smart status of the hard drive shows failed, but this is for an unknown attribute. This may not really indicate the drive is failing, but could be a possibility. Since all of the other tests have passed, I feel it is best to replace the drive under warranty for the customer.
About the new hard drive, the technician wrote: I have run a third-party smart utility on the (new, replaced) hard drive again and I have found that it is failing with the same error. The Apple test shows the smart status as OK.
I have researched this error and I have found that this attribute appears to be for temperature. Since both drives showed the exact same error, this attribute can be safely ignored for smart status. I was not able to replicate any issues with this machine other than the smart status failure so I do not think there is any other hardware failing in this machine.
If the customer continues to have issues, I would recommend reinstalling the OS one more time. If the issue still persists after this, then the customer should bring in the computer when issues are still happening so we can try to determine the cause of the problem better.
At first, my iMac was performing much better, but as I began to migrate data from back-up, I was not able to connect/re-establish my iphoto library, or re-establish my Apple mail accounts( both of which I have done countless times in the past without hassle).
I decided to run Apple's Disk utility which reports it cannot repair the new drive.
Just prior to my original posting, I had sent a copy of my posting to Micromat (TechTool Pro) asking for their opinion/advice.
Their response was: The SMART routines are built into the hard drive by the drive manufacturer. They are proprietary and different for each drive manufacturer. TechTool Pro just reads the status of the built-in SMART parameters and reports their status. Basically, a threshold exceeded indicates that the drive has exceeded what the manufacturer thinks are proper operating parameters for it and it may be getting close to failing. For an interpretation of the seriousness of a specific attribute failure you would need to contact the drive manufacturer. A failure is a warning to be sure to keep good backups and consider replacing the drive. If you get a SMART failure on a drive that is under warranty, the drive manufacturer will typically replace the drive.
Following are two links that might be of interest:
http://www.ariolic.com/activesmart/docs/glossary.html
http://www.ariolic.com/activesmart/docs/smart-attribute-meaning.html
I also took your (Looby) advice and called Seagate. (I also visited their web site, which recommends replacement of their hard drive under these circumstances!)
Within a couple of minutes, the tech person agreed that this is a serious concern and I should replace the drive.
Regarding Wiil's post, Apple's Disk utility says: smart status verified.
The SmartReporter utility reports the smart status is OK.
The SmartUtility application says:smart status failed. ID: #190 Unknown attribute.
For all other posters, this was not a New Egg purchase, which was not relevant to my post. Thank you just the same.
I've left a message for the Apple-approved store and will ask for another drive, and that, if possible, it be tested before I bring my iMac in to reduce the inconvenience.
I'm also wondering if I should switch to a 500 GB hard drive, although that would defeat the purpose of buying the larger drive for all the video I work with ( I have another 2 Terabytes storage with external drives).
Any further comments welcome - and thank you all again for taking the time!

My mirrored RAID config shows degraded

My simple mirror RAID set is noted as degraded in Disk Utility, and one of the drives is doing frequent drive arm recalibrations. This drive set contains all my iTunes and iPhoto files. Time to replace a drive or two?
I'll copy the data to my desktop drive but then what?
- How do I diagnose which drive is the bad one?
- How do I know that in fact there is a bad one? Hard error or correctable soft error?
- How do I integrate a replacement drive in the set?
RAID Utility 1.0 and SoftRAID do not seem to apply to 10.3.9.
Searched the knowledgebase but no joy.
Any and all help w/b appreciated.
Regards, Mike

Well, I've tried just about every combination of Terminal/diskUtil(TR), Disk Utility(DU), reboot, and mount/re-mount that I can think of.
But it always comes to this:
1 - after the mirror is apparently rebuilt (before reboot) - DU reports both drives as degraded and TR checkmirror reports both OK. (Next, Pick 2, 3, or 4 for next step
2 - then rebooting OS X, TR checkmirror reports slice 0 as OK and slice 1 0%, and DU immediately starts rebuilding disk1s3 (disk 1 slice 3 - see how drive formatting breaks down from TR list). wash, rinse, repeat - see 1 (Oddly TR checkmirror shows both disks OK shortly after rebuild begins but well before completion.)
3 - After reboot and starting DU, it starts rebuilding immediately with no chance to cancel, I initially forced DU to stop by turning off the bad drive (it crashed actually with no disk error msg). Restarting DU and selecting the bad drive before the mirror (good half) mounted allowed me to reinitialize the bad drive. Then, selecting the mounted mirror and dragging the re-inited drive to the RAID box, I was able to select rebiuld and try it again. (Note - in the raid box after dragging the initialized drive, the good drive's status was "Forming" - I have no idea whether this was good or bad.) wash, rinse, repeat - see 1.
4 - After rebooting and skipping DU, using TR repairmirror gave same results (again TR checkraid noted both drives OK before completion). I eventually learned to wait until the drive busy lights (red glow surrounding the power on lite when writing) stopped - a couple of more hours. wash, rinse, repeat - see 1.
At this point I'm out of ideas/procedures. I guess the next step is to try to delete the mirror set, re-init both drives (to zeros), remirror them, and copy backup folders to the mirror.
Some notes for Mac developers in case they peruse this forum:
1. Please provide a desktop message when the mirror mounts if the mirror is degraded or when it goes bad during operations. Also report which drive(s) is(are) the culprit(s).
2. Provide the serial numbers in the diskutil list output. Also provide which disks are participating in the mirror as well as their status.
3. Provide better documentation of terms and processes. For example, to stop forcing a DU crash, I figured out that if I turned off the good mirror drive so it wouldn't mount, the bad drive would mount (dimmed) but could then be selected for re-inititlization.
4. Provide a cancel button on DU rebuilding progress box and include a time remaining bar.
This is pretty basic stuff. If Xserve is to go big time, RAID needs to be more robust in operation, and much more friendly to repair.
I have no idea how long I was operating with my data unprotected.
Any and all ideas welcome.
Thanks, Mike

Xserve - Mirrored RAID Failed? Degraded? Confused...

Hi,
Can anyone shed some light on this situation please? Disk utility tells me one thing and Server Monitor tells me another.
I have an X-Serve with 3 drives and a Mirrored RAID Set running 10.5.8.
Server Monitor is showing a yellow status for disk 1 and disk 2. Raid Status: Degraded (Mirror) Pre-failure Warning: No Warnings
Disk Utility on the other hand shows that the Mirrored RAID sets are Degraded because disk2s4 = Failed and disk2s2 = Failed.
Running disk utility commands in terminal also show disk2s4 and disk2s2 as Failed.
I have not yet tried to Rebuild or eject / reconnect the disk. The only thing I've really done is some research and rebooted the server.
It sounds like disk 2 has failed. Is there any way to confirm it's dead? Are there any serious risks of trying to rebuild?
Thanks.
- F4st

I'm not sure why you think you're seeing conflicting information…
Server Monitor is showing a yellow status for disk 1 and disk 2. Raid Status: Degraded (Mirror) Pre-failure Warning: No Warnings
OK, So Server Monitor says the RAID is in a degraded state…
Disk Utility […] shows that the Mirrored RAID sets are Degraded because disk2s4 = Failed and disk2s2 = Failed
Running disk utility commands in terminal also show disk2s4 and disk2s2 as Failed
I don't see this is anything different. All three methods are telling you disk2 has failed and your mirror is relying on disk1 for all activity.
Is there any way to confirm it's dead?
Umm.. you mean other than Server Monitor, Disk Utility.app and diskutil?
Face it, it's dead. It's had it.
Are there any serious risks of trying to rebuild?
Sure. If the disk is dead, it's entirely possible that rebuilding the array on that disk will fail. You run the risk of a problem on disk1 and then all your data is gone.
My advice: Replace disk2 as soon as possible. If not sooner.

Offline Disc In Degraded Mirrored RAID Set

I have a 2 disc (300GB each) mirrored RAID set that has worked fine up until recently. One slice appeared failed so I attempted to rebuild it. 7 hours later it still showed up as failed. I attempted a rebuild once more and the same result. I then shut everything down and re-booted my whole system. Now the RAID set is still degraded but the slice now shows up as offline as opposed to failed.
I checked the connections and it's all connected fine.
I have run First Aid several times and no repairs were necessary.
Anyway I can get this back 'online'?
If not, can I delete it, repair it and if it's repaired add it back to the RAID set?

It sounds like one of the drives in the mirrored set has lost its mind (i.e., failed).
This is exactly the situation Mirrored RAID is good for.
Remove the failed drive, insert your spare drive of the same or larger size, and assign it as a spare. Then you should be able to get the RAID to rebuild onto the spare and bring it up to date in the next half-a-day or so. Then the mirror will show as working again.
Make sure your Backup is up-to-date. A second failure now (before the array has rebuilt) will give you data loss.

Really Ignore Degraded Mirror RAID ?

Hi, I just became responsible for a studio with a RAID system -- I'm new to this so please bear with me.
Server Monitor shows that 2 drives are degraded. It seems that these are slices of a Type 1 (Mirror) RAID set. The symptoms match the following linked document exactly (which says Server Monitor may erroneously report degraded status of Journaled drive, and you can ignore if Disk Utility says it's OK):
http://docs.info.apple.com/article.html?artnum=107406
However, I can't say for sure that Disk Utility is giving me a green light on this RAID set. Disk Utility (the GUI application) says the RAID set and the slices are degraded. But Disk Verify comes through fine. Also "diskutil checkRAID" says that Status is Degraded but that both disks in set are "OK".
So do I worry about this or not?
Any and All Help Much APPRECIATED!

I have seen this issue on a couple of Xserve's
This is how I went about fixing-
Get someone in front of Xserve
Identify which one the 2 drives is NOT working IE- no blue activity light
Pull that drive and break RAID
Insert drive
Rebuild mirror, see this article for info-
http://docs.info.apple.com/article.html?artnum=106987
There is a way to rebuild the mirror in Disk Utility, I cannot find any info from Apple on this but i have used a few times.
On one Xserve I have done this at least 3 times, I have completely rebuilt the RAID and re-installed the OS and it still does it occasionally.
Ed

Mirrored RAID degraded, upper slice shows "failed" but drive passes verify

Similar Messages

Maybe you are looking for