Mirrored RAID 1 becomes degraded?

I have (2) G-Tech 2TB drives set up as RAID 1 (mirrored). On the mirrored drive, I have numerous folders with assets for my edit, including a set of folders for FCP which includes a Capture Scratch folder. Initially P2 media was "log and transfered" into this folder within FCP. No problems.
But when I targeted this folder (G-Tech RAID>FCP>Capture Scratch) to capture additional video into, or even capture on another drive and then drag and drop into this same folder, the RAID set, in each occasion, became "degraded" (as indicated in Disk Utility) and is, for the second time. in the process of "rebuilding RAID slice", which takes 22 hours!
Any ideas as to why this is happening?
I am thinking that I should create a new folder outside my FCP Capture scratch and copy new assets into this folder instead?
I am using FCP6.02 QT7.4.5 DU10.5.6 MacOS10.4.11
Thanks in advance for your reply

Yes. Verification with the GUI tool is the first step. But... hmm, if you are dropping communications with the card, that is not a good sign. Make sure you have a backup and then try a PMU reset on the system. Maybe there is something wacky in the power manager. Then try any/all of these from Terminal to get more information:
raidutil list status
raidutil list eventinfo
raidutil list raidsetinfo
This should provide feedback. If these commands fail, then I fear that the card is not responding. Do you have AppleCare? It might be time to call for a replacement card.
Hope this helps

Similar Messages

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.

Mirrored RAID set has degraded following power outage.

Hello,
Following a recent power outage our Mac Pro running Leopard OSX Server with 2 x 1TB discs in a Mirroring RAID configuration (with an installed RAID card) developed a 'severe error' message.
The Raid Set R0-1 has a Viable (degraded) status.
Drive One (or bay 1) is 'Good' and 'Assigned'
Drive Two is 'Good' but with the State - 'Roaming'
Also, the events display describes the failure of a drive 3 (there isn't one) and that the R0-1 is Degraded and no spare is available.
So, we're a little confused.
1. Is the Drive 2 no longer part of the RAID mirror (i.e. Roaming)
OR
2. Something more significant has happened hence the bogus Drive 3 message?
Any suggestions or advice would be much appreciated as always.
Thanks
Steve

Yes. Verification with the GUI tool is the first step. But... hmm, if you are dropping communications with the card, that is not a good sign. Make sure you have a backup and then try a PMU reset on the system. Maybe there is something wacky in the power manager. Then try any/all of these from Terminal to get more information:
raidutil list status
raidutil list eventinfo
raidutil list raidsetinfo
This should provide feedback. If these commands fail, then I fear that the card is not responding. Do you have AppleCare? It might be time to call for a replacement card.
Hope this helps

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

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

Raid 10 showing degraded, but both raid 0's are fine.

So 4 x 1TB black caviars.
2 sets of stripped, then mirrored together to make the raid 10.
Both stripped raid sets are fully online, just the raid 1, is showing up as degraded.
There is no rebuild option in disk utililty 13.
How do I go about via the terminal getting the raid 1 (a mirror of the stripped sets) to rebuild?

Also, Apple seems to call your setup RAID 0+1.
The bad news, as always, is that it appears you cannot just tell it to rebuild. You have to tear the array apart or add new blank drives, then you can rebuild it after that.
My experience with Apple Raids (now a bit dated) was that drives that had marginal blocks requiring too many retries cause a Mirrored array to become Degraded, sometimes dumping the drive that was too slow (or sometimes not). You may want to add at least one new drive and re-Zero [write Zeroes to get spares substituted] the one you replace, then prepare to do that again when/if it Degrades again. Keep careful track of what has been done to each drive!

How do I add a new drive to a degraded MIRRORED RAID set?

My mirrored raid said it was degraded because one of the drives had a failure.
Today I unplugged the faulty drive and inserted a new one.
So far so good.
I erased the new drive.
Then I went into disk utility and followed the instructions in the help about RAID but I cannot see how to add this new drive to the RAID.
I'm confused.
1) The data is all on the RAID (the good, original slice) so can I add a new slice?
2) how do I do it?
Many thanks

I don't recommend the Apple hardware RAID card, and it doesn't work with off the shelf drives. If you are using drives in RAID, first make sure they are RAID Edition or lacking that Enterprise. Same make/model/firmware.
If using Seagate, avoid anything prior to 7200.12 series. If WD the RE2/3 series.
Rebuilds are slow, and one reason why I recommend 3 drives, even if you lose one you are covered still.
Of course just having two backups per volume is more important and comes first; mirrors are great for live editing and recording (audio) but otherwise... I'd stick to stripe and redundant backups. Only if you need 24/7. Otherwise, forget mirror.

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.

Degraded mirrored raid- won't rebuild

I've had 2 500 gig drives mirrored. When I set up the drives I did not check "automatically rebuild".
I just discovered ( not too long after installing Leopard) that one slice was "damaged" and the raid was degraded. I tried to rebuild, but got an error message that said disk utility was unable to recognize the filesystem. I finally erased the "damaged" drive, verified it and am ready to try rebuilding the set, but don't want to lose data from the remaining drive from the original raid.
How should I proceed?
Thanks-
Ford

Well I'm sure VERY few people have multiples of EVERYTHING. I still have my data.
All I want to do is mirror a fresh drive with the other drive that was part of a mirrored raid set. That should be possible... it seems...
Please don't admonish me for not having more backups. I have a total of 1.25 terabytes of HD space with a lot of redundancy.

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

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

Mirrored RAID drive removal.

I have 3 drives in my Xserve G5. 1 is 80GB and running as the system drive. the other 2 are 500GB drives which are both mirrored. I want to sacrifice the data redundancy and gain the extra 500GB for storage. I do not have a location to store the 400+GB of data that is stored on the mirrored RAID while I delete the raid. Is there a way to delete the RAID and then recover the data from one of the 2 drives and then format one of them to be blank? So far from what I am reading deleting a RAID set will make me lose my data I think... I am running the raid through Disk Utility as a software RAID.

Chris
If you delete the RAID1 with disk utility you will lose the data, I can only think of one way to do this-
Pull one of the RAID drives and let the RAID become degraded, data will still be there on one drive
Insert the pulled drive and format with disk utility
Transfer all data from degraded RAID to freshly formatted single drive
Once transferred, delete degraded RAID and format drive to use as extra space
Now doing this without a backup would be very dangerous, and I would suggest that all data should be moved to another drive before doing any of this.
I use software RAID configs all the time and would not recommend that anyone run a server without some form of redundancy, they have saved mine and my client's bacon many times.
Regards
Ed

Creating a mirrored raid set with a hard drive that already has data on it.

I have a hard drive that I keep my photos on, and want to create a mirrored raid set that includes this drive, with its data, and another drive. How can I do this without erasing the drive with my photos on them? I am running 10.7.5 if that matters.
Thanks for any help.

Creating a Mirrored RAID reformats the drive and loads a substantial RAID driver and some tables onto it. When completed, the drive is inherently a member of a RAID set, and will continue to be so even if moved to another Mac.
because of this, you cannot create a RAID directly on a standard drive that contains data already in any reasonable, risk-free way.
To amplify what The Hatter has said above, Mirrored RAID is not Backup. Mirrored RAID only increases mean time to repair to keep a drive failure from becoming a Data Disaster. You still need a Backup. Mirrored RAID does not protect you from deletions from user error, crazy software, or "just because".
I run a mirrored RAID in my Home Server, which contains all the Users files for everyone in the Household. And I also recognize (after being burned by it) that Mirrored RAID is helpful, but not a sufficient Backup by itself. I back up the Users Drive automatically to an External drive using Time Machine. [So what I am advising is not just theoretical, I am living what I am advising.]
With WD Black 1TB and other very good drives in the under US$100 range, there is really no reason NOT to invest in several drives for such an undertaking.

Disk Utility gives error and does not rebuild mirrored RAID

After having a HDD fail on a mirrored RAID I replaced the HDD and attempted to rebuild. Disk Utility reports via Console that it can not find an Apple Boot partition to check size and then fails to repair the RAID. Details follow.
Mac OS X v.10.4.8 Server
Power Mac G3 (Blue & White)
512MB RAM
20GB ATA HDD – boot device on internal ATA bus
4x 160GB ATA HDDs - setup in RAID scheme on Sonnet ATA/133 PCI card
RAID configured using Mac OS X v.10.4.8's Disk Utility and is an Apple RAID version 2.
RAID scheme <from "diskutil checkRAID" cmd>:
Welcome to Darwin!
[myserver:~] myadminuser% diskutil checkRAID
RAID SETS
Name: Mirror_2
Unique ID: 5FF8AD5F-0892-482D-B430-C7069D63AFD2
Type: Mirror
Status: Online
Device Node: disk3
Apple RAID Version: 2
# Device Node UUID Status
0 disk0s3 1FB48B00-3E52-4C29-8F05-2ED8BDAE4544 Online
1 disk6s3 BF2E69C6-698E-4D6A-A2A9-FE8CDAD8A7B1 Online
Name: Mirror_1
Unique ID: B448A09D-EC10-41EE-BA45-4D4071A88EA5
Type: Mirror
Status: Degraded
Device Node: disk5
Apple RAID Version: 2
# Device Node UUID Status
1 disk2s3 09AD5705-CF67-48B3-8E31-79983BD4781A Online
0 disk4s3 23EB1952-8B18-4400-A6FE-22C2F707C097 Failed
Name: StorageRAID1
Unique ID: 2B8349AB-F553-4FD2-8440-C575791DA858
Type: Stripe
Status: Online
Device Node: disk7
Apple RAID Version: 2
# Device Node UUID Status
0 disk3 5FF8AD5F-0892-482D-B430-C7069D63AFD2 Online
1 disk5 B448A09D-EC10-41EE-BA45-4D4071A88EA5 Online
I configured this RAID scheme (two two drive mirrors striped together) according to this kbase document: http://docs.info.apple.com/article.html?artnum=304377
As shown in the above "diskutil checkRAID" output I have a failed HDD. So I replaced the HDD with another 160GB cold spare. I added the new drive to the mirror "Mirror_1" also known as disk5 and hit rebuild. Received the normal message that all data on the new drive I was adding would be erased.
I then receive the following error immediately in the Console Log:
Rebuilding RAID "Mirror_1"
2006-12-15 23:50:24.741 DiskManagementTool [375] WARNING: Could not find Apple Boot partition to check it's size, skipping disk5s-1s.
Rebuilding RAID slice "disk4s3"
Just to stem some confusion, the device ID disk4s3 has been used by the system for both the old failed HDD and the new replacement HDD.
The result of this attempted rebuild is I end up with all the data from Mirror_1 on the new HDD but the new HDD is not successfully added to the RAID, therefore Mirror_1 is still degraded and my problem not resolved.
I ran the appropriate rebuild cmd from both the GUI Disk Utility as described and from the CLI "diskutil repairMirror disk5 disk4s3" but no joy.
Any help would be greatly appreciated. This volume houses a large amount of important data including user home directories so while some offline time may be required data loss would not be very acceptable.
Thanks in advance and I will be happy to provide more information as necessary.

I guess doing it in Terminal would fail too:
diskutil repairMirror disk5 disk4

Re-create a mirrored RAID after restoring backup

As a follow-up on my thread http://discussions.apple.com/thread.jspa?threadID=833779&tstart=0 :
On a XServe G5 with OS X Server 10.4.8 and a two-drive mirrored RAID I do backups by cloning the RAID onto an other disk (in bay three) using Intego's Personal Backup X4.
Now it may happen that there is some kind of data loss or an other emergency case that urges me to boot from the cloned HD. I would do this by simply removing the HD in bay one and replacing it with the clone, then restart the server (second HD of the RAID1 remains in bay two).
The information I got until yet says that the mirrored RAID is then broken and needs to be completely re-build. Is this correct so far ? I originally assumed that the clone "remembers" that it was part of a RAID system before and rebuilds automatically with the second HD still in place. Very likely wrong ?
So if I need to rebuild the clone from scratch, which steps do I follow exactly ? As far as I understand I have two choices:
(1)
Via command line (as root): diskutil createRAID mirror <set name> Journaled HFS+ <device identifier disk1> <device identifier disk2>
<set name>: Would be volume name of the RAID to create, right ?
<device identifier disk1/2>: What is this and how to determine ?
(2)
Via disk utility: Select one disk (first line on the left disk/volume list, e.g. "76,2 GB Hitachi 123ABC"), click in "RAID" tab, do settings.
Then drag & drop each harddisk from the left to the right list (again, the first line of each disk entry). Finally creating the RAID by clicking at the button "Generate".
I'm not sure, although I would likely handle this with the disk utility, it appears easier to me using the diskutil command in terminal. But maybe I simply lack of explaining the GUI... let me know how to post images and I will add some screenshots here.
Well, if my proceedings are too complex and there is something easier, please let me know. I'm open for everything.

>This part of my question originally referred to the fact that when booting from the cloned backup in bay one while still having the second disk of the old RAID in bay two, it could occur that the OS rebuilds the RAID by using the data on the remaining mirror disk in bay two, couldn't ? This would be not desired, because the data on that disk would be no longer usable. So just for clarification, not that we have a misunderstanding in this point.
I see what you're getting at, and I don't believe it's an issue.
Given three disks, disk0, disk1 and disk2, where disk0 and disk1 are mirrored and that mirror fails, the OS will not rebuild the mirror using disk1 and any other disk. It won't arbitrarily choose any disk in the system to rebuild on - you have to specifically mark as disk as usable, either by enabling auto-rebuild and adding a spare disk to the array, or by using 'repairMirror' and specifying the disk to use.
In any case, if you reboot the system from disk2, there is no way it will rebuild the array using that disk since that disk is the active boot drive and can not be unmounted (which is necessary before being added to an array).
So, no, there is no chance that the system will auto-rebuild the working half of the mirror with your backup disk.
>Okay, let's summarize... I would follow this procedure in order to boot from the cloned backup and build a new RAID:
1. Remove both disks from the XServe.
2. Insert the cloned backup disk and boot.
3. Open terminal, su root, execute:
diskutil enableRAID disk0
diskutil repairMirror disk0 disk1
This is not correct.
When you 'enableRAID disk0' the OS will create a new, virtual disk (likely 'disk2'). This is the mirror array (currently consisting of only one drive), and it is this virtual disk that you need to specify as the mirror to be repaired.
So, given disk0 and disk1 as being the physical disks in the server, the steps are more likely to be:
<pre class=command>diskutil enableRAID disk0</pre>
(this creates a new, virtual disk2)
<pre class=command>diskutil repairMirror disk2 disk1</pre>
(this adds physical disk1 to the degraded mirror disk2)
When complete disk2 will be a mirror RAID consisting of disk0 and disk1.
>When using "diskutil enableRAID", I cannot determine the label of the RAID as I would do with "diskutil createRAID" (in command line manual this is referred to "setname"). Which setname does my "new" RAID system get, a default one ?
You know, I have no idea
I've never noticed this before. If I think about it, I'd guess that the setname is based on the source disk name.
>> If you add a drive to a RAID it gets reformatted, so it doesn't matter what's
on it.
Even if it was part of the RAID system before (the original disk in bay two) ? It could still have the RAID information on it and try to rebuild RAID when getting mounted, couldn't ?
No. See my comments above. The OS won't auto-rebuild unless a) the RAID is set to auto-rebuild and b) there is a spare disk in the array. If either of those two conditions are not true then the disk acts as a degraded mirror and can be reformatted/reallocated as you like.

Mirrored RAID 1 becomes degraded?

Similar Messages

Maybe you are looking for