Mars Raid-10 status degraded

Hi
My CS-Mars 110 had crashed for some unknown reason. After reload the device works fine but there is an error with the raid-10 which shows a status of "Degraded", please see attached file.
Is there a way to solve this problem?
Thanks

Hi
[pnadmin]$ model
mars110
local
extension
[pnadmin]$ pndbusage
Current partition started on Tue Dec 18 19:10:01 CET 2007 and uses 6.93% of its available capacity.
Switching to next partition is estimated for Tue Apr 19 14:00:51 CET 2022.
9 empty partitions are available for storage
[pnadmin]$ raidstatus
Adapter Information:
Product Name : Intel(R) RAID Controller SROMBSAS18E
Firmware Version : 1.03.00-0211
BIOS Version : MT30
Adapter RaidType Status Stripe Size Cache
a0 Raid-10 Degraded 64kB 1427649MB Enabled
PD Status Size & Block Model Serial#
p0 Unconfigured(good) 476940MB [0x3a386030 Sectors] ATA ST3500630NS K 9QG0SASJThis Drive IsForeign.
p1 Online 476940MB [0x3a386030 Sectors] ATA ST3500630NS K 9QG0SA5M
p2 Online 476940MB [0x3a386030 Sectors] ATA ST3500630NS K 9QG69XW1
p3 Online 476940MB [0x3a386030 Sectors] ATA ST3500630NS K 9QG0QTT9
p4 Unconfigured(good) 476940MB [0x3a386030 Sectors] ATA ST3500630NS K 9QG0H8R3This Drive IsForeign.
p5 Online 476940MB [0x3a386030 Sectors] ATA ST3500630NS K 9QG677HW

Similar Messages

WSA RAID Status: Degraded

Hi,
I Have the next status on WSA
RAID Status:
Degraded
Any idea how to get Optimal ?

Hello Oscar,
Please try rebooting the appliance and leave it for a day for the raid to rebuild. If the raid still does not re-build there might be a possible disk issue, kindly open a TAC case.
Regards,
Puja

Drive status shown Unconfigured bad and Raid 10 volume degraded

Cisco UCS C200 M2 server one of the drive is showing Unconfigure bad and raid 10 volume degraded with long beeps and solid umber light. First I thought the hard drive is bad and replaced it with new one of same type. Did wait for rebulid for 5 days. Beep did not stop. Againg I looked in to the server and found the above status. Please refer the screen shot for more clarification of the error.
I was gong through Cisco documentation wherein I came across same type of error with bug and I am not sure its the same and is it is I did not understand the workaround I mean what to upgrade is it BIOS or firmware etc.

Mohammed,
What the bug is trying to say is that in a newer version (1.4(3c)) the behavior changes and the Physical Drive which was removed and inserted back shows the status "Missing" instead of showing up as "Unknown" under the Virtual Drive tab in CIMC as this is Unconfigured Bad drive and not part of the RAID group.
Now, the best you can do here is to monitor your system using CIMC, which is the tool we have to monitor/manage the C-Series server instead of vSphere itself.
To get rid of this behavior, you will have to enter into the WebBIOS (Control+H or C or M < Depends on what RAID controller you have), make the disk unconfig good, then make it only "online" so the disk can be part of the array again.
You may find out what is the sequence of keys you have to hit to ge to the controller during the server boot:
http://www.cisco.com/c/en/us/td/docs/unified_computing/ucs/c/hw/C200M1/install/c200M1/RAID.html
"Watch for the prompt for your controller during verbose boot:
•The prompt for LSI controller card utility is Ctrl-H.
•The prompt for the mezzanine-style controller cards is Ctrl-C.
•The prompt for the onboard Intel ICH10R controller utility is Ctrl-M. "
Note-1: It is important you first check that the disk has no errors before you try to re-add it to the array, cause if that is the case the disk will probably fail and data loss can occur.
Note-2:Once in WebBIOS, you can also disable the beeping alarm and here is the document that shows how that can be done from WebBIOS (note that this will be the interface if you had to press Ctrl+H, otherwise it will look different) or also, you can use MegaCLI to disable the alarm, and the below link also includes the necessary command:
http://www.cisco.com/c/en/us/support/docs/servers-unified-computing/ucs-c-series-rack-servers/116106-problem-ucs-lsi-beeps.html
In case you don't know how to set up CIMC in your C200, here is the link with images and the example, look for the C200 to get the correct steps/cabling:
http://www.cisco.com/c/en/us/support/docs/servers-unified-computing/ucs-c200-m1-high-density-rack-mount-server/111455-setup-cimc-c-series.html
I hope this helps.
Rate ALL helpful answers
-Kenny

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.

Apple Raid Card: Raid-1 volume degrading

Hello,
I have 2 Raid-1 volumes running on a late 2009 mac pro with an Apple raid card. The second Raid volume has degraded now 3 times in the last 2 1/2 weeks. Raid utility is saying that the drive is damaged but when I shutdown, pull the drive out of the bay and push it back in and then restart it says that the drive is good. After assigning it as a spare the Volume rebuilds and lasts about a week until the same thing starts all over again. Perhaps the drive is somehow damaged but it seems more like a connection problem. If this is a familar issue to anyone and someone has a suggestion it would be greatly appreciated.

Maybe you need to do a full surface scan for bad or weak failing sectors.
Next time it drops out (or whenever you decide to remove it manually).
Use Disk Utility to Initialize with Write Zeroes option. This takes several hours.
If it completes without any error messages at all, it should then be good to use.
If Bad Blocks are found, they will generally be spared out by this process, and the drive can be good to use for a while, but is likely to fail within 6 months. You should consider moving it to light-duty or occasional use, such as backups.
Sometimes the Initialization will fail. If the drive is still under warranty, return it to the manufacturer for a refund/replacement. Original Apple drives have a one-year warranty, same as your Mac. Manufacturer warranties are often (but not always) 3 years or more.

Message appears Raid-1 is degrade in Qosmio F30-111

hello,
sorry for my english.
I have a problem with my notebook when turn on show me a massage "Raid-1 is degrade" and cant use the recovery cd why show me this massage again. I can run windows xp mce.
help me please.
thankss

Hi, I have a similar problem. The way I got round it was to remove one of the hard drives and then run the product recovery disk with only one hard drive in the system. But the next problem I had was that after running the product recovery when the windows set up started a blue screen with a lot of Jargon came out. Maybe someone can help out from there cos I'm stuck

RAID status: degraded or failed? is there help?

We are using mac os sever 10.4.3. When we recently restarted the servers we noticed that 2 drives on each of the servers has yellow warning lights showing on the moitor software but not on the actual drives themselves. We have 2 servers one a G4 and the other a G5. The G4 has 2 drives and both are registering yellow, the G5 has 4 drivers with 2 registering yellow. The monitor says the drives are "degraded" but everything seems to be transferring and backing up fine. Should we do a backup and use Disk Utility to repair the degraded/damaged drives?
Mac OS Server Mac OS X (10.4.3) Processor 2 GHz G5 Memory 2 GB

You must have RAID 1 mirrored drives setup then and are running from the working disk of the mirrored pair.
Ofcourse you should fix these types of problems/failing disks.
Having recent backups is always a good thing. A RAID doesn't save you from human errors but it should prevent "downed" servers.
Your supposed to be able to repair a degraded mirror from within Disk Utility but I have only done it from the CLI (Terminal) diskutil.
If you do a : sudo diskutil checkraid
What do you get?
If the servers are updated from 10.3.x you can (if not done already) also update the RAID version from the older ver. 1 to ver. 2 available from 10.4.0-> using the command:
sudo diskutil convertraid

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

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

Need help with RAID Card and degraded Raid-5 errors

Dear all,
I recently purchased a used Apple RAID card for my 2008 Mac Pro 8-Core. The installation went smooth, the card was immediately recognized and the battery reconditioned within one night.
So I started setting up a Raid Set with the 4 identical drives which I already used before as a software Raid. But each time the Raid Level-5 Volume is created, somewhat later the status turns red and the Raid is listed as "degraded"!
A closer look at log reveals:
+19:42:54 Drive carrier 00:01 inserted+
+19:42:27 Background task aborted: Task=Init,Scope=DRVGRP,Group=RS1+
+19:42:27 Degraded RAID set RS1 - No spare available for rebuild+
+19:42:26 Degraded RAID set RS1+
+19:42:22 Drive carrier 00:01 removed+
+15:10:57 Created volume “R1V1” on RAID set “RS1”+
So it seems that the drive from Bay 1 somehow gets lost (removed) a few hours after the volume is being created and anysoon later it's being "reinserted"...
Of course, the drive is NOT removed, nobody touched the Mac Pro! Also I did the same procedure 3 times and the result was always the same.
I also tried setting up JBOD and different RAID levels which do all work without a problem. Only when choosing RAID5 (what I intentionally bought the card for), the problem reappears
Anyone any solution or hint for me concerning this problem? Many thanks in advance!

One drive completely broke down later. Replaced that drive and since the problem's gone!

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

Raid Card Constantly Degrades Volumes - Mac Pro

I just got a new Mac Pro with Raid card. I of course purchased hard drives separately, rather than apples inflated rate. I picked up four 750 GB Samsung F1 Raid (F1R) edition drives from OWC thinking it would work well with my system.
No matter what raid level I choose, within a day or two it says one of drives were removed and then it says replaced within 15 seconds, causing the entire raid set to be degraded. I believe it might just be these drives go into a lower power standby mode and aren't as responsive as the raid card wants them to be....hence it declares them "removed." This means no matter what I have tried I am constantly changing raid levels hoping one will fair better than another and wasting 10+ hours initializing and reinstalling.
Any hints, can I make the raid card less sensitive through firmware update or something? I'm kind of bummed I have these four nice drives and the best option seems to be use them as individual JBOD drives.
Please help.

I had gone through this same process numerous times (though I was hoping for RAID 5). Apple officially says that they don't "support non-apple drives," though you would hope many work anyways. I believe my problem at least is probably due to the firmware on my hard drives not responding in the time frame the apple RAID card expects. So, I doubt your RAID card is faulty (though I greatly wish someone would post a solution to our problems).
After you give up trying to use RAID completely, you can erase all your RAID sets....select only one of the disks to create a set with, select the JBOD (Just a Bundle of Disks) mode. Repeat for all of your hard drives, create an individual volume on each, and install OS X. You will now be set up in a standard 4 separate hard disk mode with no RAID protection. However, you still utilize your RAID card so you get the added benefits of a large disk i/o cache (256 MB I believe) and a battery backup for your write operations. Not what I paid for but at least something that works. Be sure to set at least one of the disks for time machine to use as a backup (so you get something for data protection). Hope this helps, it took me awhile to decide to ditch RAID and think logically to get it working at least.
Please can anyone help solve our problems? Please!

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!

TD100 VMWare ESXi 3.5 U4 RAID health status

Hi,
i am using a TD100 (6429) with an 8k RAID adapter with VMWare ESXi 3.5 U4. The system is working fine with one exception:
I can not monitor the health status of my 8k RAID. It wont show up on the health status page in the VM client. Therefore the only way to check the status would be to look at the front lights of the server itself. That does not seem to be a good solution since it is out of sight in the server room.
In the VM forums i just found that some kind of CIM would be needed.
Is there any way to resolve this issue?

welcome to the forum!
the following document should help in using VMWare with IBM Director and ServeRAID Manager:
http://www-03.ibm.com/support/techdocs/atsmastr.nsf/WebIndex/WP101047
ThinkStation C20
ThinkPad X1C · X220 · X60T · s30 · 600

RAID Issues - Standby Disk

I am running a PowerMac G4 with the two disks configured as a single mirrored Raid disk.
Today, the system will not boot; unable to find a disk to boot from.
Restarted system from the 10.4 install CD and using the Disk Utility I have discoverd the following:
1. Running first aid, no problems found.
2. Looking at the Raid Option, the following is displayed:
a. Raid Disk status - Degraded
b. Disk 1 Status - Standby
c. Disk 2 Status - no problem.
I started the process of rebuilding the Disk 1 and I am waiting for it to completed (over 100GBs of info storage on system).
I have several questions>
1. Why doesn't the system continue to run from a single disk - Disk 2? Does one have to do something?
2. I cannot find any information about running a system with Raid disks (software version). What do these status name mean - standy, degraded, etc. and what do you solve these issues/problems?
Steve

good question - now if someone who only provide an answer
I just set up a mirrored FW Raid and made the array bootable. It booted but I can not tell which drive is actaully booting and which is the mirror
1. I can't tell if the second (mirror) drive is being written to or NOT (No volume info is available/provided in disk utility). So how does one actually tell if the mirrored RAID is actually writing.
2. If (when) Drive A (a startup drive) fails, how does one boot from the other?
IMO, Apple needs to do a MUCH better job of explaining their RAID utility and it's use.

Mars Raid-10 status degraded

Similar Messages

Maybe you are looking for