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.

Similar Messages

RAID Admin and Disk Utility show different sizes

Hello all,
I have tried searching through these forums for a resolution to this, but did not really find one. Here is my situation:
I have an XServe Dual G4 in a branch office. It has attached to it an XServe RAID. Last week, when I was down working in the office I added a new drive to the RAID. The lower channel on the RAID had 4 172GB drives in it, and I added a 5th and and told RAID admin to resize the RAID.
The next day, the RAID was finished resizing. RAID admin was reporting that the array was now 690GB. However, after rebooting the server and RAID multiple times, Disk Utility in OS X is still showing that the Volume on the RAID is only 517GB.
So, I have a couple of questions:
1. How is it possible that by adding a 172GB drive to a RAID 5 array that was about 520GB I ended up with an array that is 690 GB? That would imply that there is no parity (since 690 - 520 = 170 and the drive I added in was 172GB).
2. How do I get the server to see the additional space? The server is at the newest version of the OS and the RAID it as the newest version of the firmware.
Please help.
Mac OS X (10.4.8)

I've run into the same issue with a newer PPC XServe. However, after I tried to reformat, I still only show up with the orginal size, and not the new size, even after I restarted the server and XRAID.
Did you have any success with your reformat?

Recommended RAID 0 scsi disk subsystem

I just ordered CS4 and I need to upgrade system. Can someone give me an example of a "RAID 0 scsi disk subsystem' I'm not sure what that is. I found 1 TB RAID 0 Lacie drives. Is that what I need? Thanks.

Going back a few decades, I had all SCSI drives (no RAID back then), because they were bigger and much, much faster, than other HDDs and connections.
Times have changed greatly and SATA II is so very close in speed, or faster, plus the cost of SCSI raw drives and their usually smaller size make their use questionable, at best.
Now, for some discussions on RAID with Premiere, Harm, Jim, Bill and others have contributed to many threads on these forums. A quick search for "RAID" ought to bring up many of those.
Hunt

Momentus I/O issues on Disk to Disk copy....

Posted this on the Seagate forums as well so don't flame me...
After installing the Momentus XT ST95005620AS I have been struggling with getting a successful bootable OS copy completed. Seems like most of the folks on the Seagate forum are having various issues but not identical to my problem so I figured I would post the details.
Here is the process I have gone thru and the results.
Installed the Drive (Shipped with SD22 Firmware)
Drive boots, is recognized, can be partitioned with HFS+ and formatted with Zero's successfully
Since I am doing a cloning operation I prepared the SOURCE drive by verifying and repairing permissions and also verified and repaired any disk issues w/ Disk Utility.
Attempted to use ASR to do a block copy from my external Firewire backup OS Clone to the Momentus XT drive. The copy works fine until about 70% and then fails with a Disk i/o error (This was done at the command line booted off the Apple OS X Install DVD)
Booted off of my external Firewire drive I attempted file level clone with Carbon Copy Cloner and I get random failures with the below dmesg output:
disk0s2: I/O error.
0 Level 3 ReadUID 0 http://Facility com.apple.system.fs ErrType IO ErrNo 5 IOType Read PBlkNum 4500640 LBlkNum 3 FSLogMsgID 2112865867 FSLogMsgOrder First
0 Level 3 ReadUID 0 http://Facility com.apple.system.fs DevNode /dev/disk0s2 MountPt /Volumes/Untitled FSLogMsgID 2112865867 FSLogMsgOrder Last
disk0s2: I/O error. 0 Level 3 ReadUID 0 http://Facility com.apple.system.fs ErrType IO ErrNo 5 IOType Read PBlkNum 4500640 LBlkNum 3 FSLogMsgID 2112865867 FSLogMsgOrder First 0 Level 3 ReadUID 0 http://Facility com.apple.system.fs DevNode /dev/disk0s2 MountPt /Volumes/Untitled FSLogMsgID 2112865867 FSLogMsgOrder Last
After these errors occur my system is pretty much crashed. I do this same clone nightly with my OEM Hitachi and it works perfectly. So I am suspecting either incompatibilities with the EFI Firmware / APM / Drive problems / etc.
I reformatted with zero's and upgraded to SD23. Drive was significantly faster on writes but failed during the clone process once again.
Is there something I am missing? Added my SATA controller / Drive info from System Profiler below if that helps.
Cheers,
Chris
Environment: Macbook Pro 15 Inch, EFI 1.7 Firmware OS X 10.6.4
Here is the SATA Info:
NVidia MCP79 AHCI:
Vendor: NVidia
Product: MCP79 AHCI
Link Speed: 3 Gigabit
Negotiated Link Speed: 3 Gigabit
Description: AHCI Version 1.20 Supported
ST95005620AS:
Capacity: 500.11 GB (500,107,862,016 bytes)
Model: ST95005620AS
Revision: SD23
Serial Number: 5YX00JTR
Native Command Queuing: Yes
Queue Depth: 32
Removable Media: No
Detachable Drive: No
BSD Name: disk0
Rotational Rate: 7200
Medium Type: Rotational
Partition Map Type: GPT (GUID Partition Table)
S.M.A.R.T. status: Verified
Volumes:
Untitled:
Capacity: 499.76 GB (499,763,888,128 bytes)
Available: 486.99 GB (486,993,702,912 bytes)
Writable: Yes
File System: Journaled HFS+
BSD Name: disk0s2
Mount Point: /Volumes/Untitled

Hi,
That's big iron, yeah, could be kswapd then.
Read these two threads and maybe search forums/google/bugzilla.
kswapd causing cpu spin on big RAM/SMP machines?
System Lockups
Check kswapd regularly after heavy I/O processing.

How do you setup RAID 10 with Disk Utility?

I read a post that indicated a Mac Pro user created two mirrors and then striped them with Disk Utility to create a RAID 10.
I tried this but Disk Utiity will not allow me to stripe the two mirrors. I tried dragging and using the "+" button. In each case no RAID 10 could be created.
Could someone list the exact procedure for creating a RAID 10 using Disk Utility?
Thank you

I have Mac OS X Build 8K1124 and I believe that came with my Mac Pro as I've not required a Mac OS X update via Software Update.
Now, I have to honest, I'm not entirely sure that was the exact process. As you can appreciate I don't have another 4 drives to try this again so I'll do my best here.
It's definitely right up until the part of making the mirrors and unmounting them, that I know for sure. What I don't remeber is what I had selected to get to the RAID tab to create the Stripe Set. I believe I had one of the mirror partitions selected, that is, either "disk5" or "disk6", which brought up the RAID tab that then allowed me to create the stripe set.
I then created the set and then dragged the mirrors (I believe disk5 and disk6) into the set.
If you can't do this can you let me know how your situation deviates?

P6N Diamond: RAID ISSUES!

Hi,
I recent purchased a P6N Diamond, no matter what i do (and yes the bios has been updated), when i enable the RAID on either the ports 1-5 or the mirror on 6 & 7, the motherboard comes up wit an error for each raid device saying "no enough memory to copy PCI option ROM", besides the obvious gramatical & spelling errors through out the BIOS and Manual hehe... this problem is really annoying me.
Heres some more info
1.Product Type: P6N Diamond
2.BIOS version: 1.2
3.External VGA Type: 7800GTX, 8600GS, 8600GS, 8600GS (4 video cards running 7 monitors)
4.CPU Type: Intel Quad Core 6600
5.Memory Type: 4x1G G.Skill (Dual Channel Mode, 2x2 Matched pairs)
6.Power Supply Type: 950w Thermaltake
7.Operating System: XP PRO
8.Problem Description: RAID ISSUE
Every time i enable raid in the bios, it says
'no enough memory to copy PCI Option ROM'
I require all the onboard LAN/Sound etc
and i also have 1xPCI IDE controller and 1xPCI raid controller for extra HDD space.
Please help
Thanks in advance;
Michael T

Copied from another site:
Quote
The cause of the problem is that in order to be PC Compatible, the Option Rom space is limited to 128K. This is true for any motherboard with PC compatible BIOS.
In the common configurations, a newer AGP card (such as a Geforce 4) will require 64K of option ROM space, so you have only 64K of option ROM space left to work with. Many SCSI, NIC with PXE, IDE RAID etc. can easily use another 40-64K of option ROM space.
By design the option ROM should shrink down to a smaller run time code after the initialization code has run. For example, some Adaptec cards will require 32K to initialize. Then they shrink down to 12K at run time; whereas some Geforce 4 cards require 64K to initialize and never release it. Please check with the device manufacturer for the latest firmware upgrade or ask if they have a smaller option ROM available. Again, this is a limitation of the PC compatible specifications and not a failure of the motherboard BIOS.
So it's the four video cards causing the problem.

Disk Utility RAID Issue

I'm trying to determine if the problems that I'm encountering are a software issue or a hardware issue.
I'm setting up a Mac Pro with Leopard and have four Maxtor 6G160E0 160GB hard drives that I'm trying to set up as two Mirrored drive sets. Everything seemed to go fine, created the two mirror sets, installed Leopard, configured and tested two user accounts and Office 2004, then updated everything to the latest version. When done I shut it down planning on moving it to it's final home tonight.
But, when I turned it on both mirror sets were degraded - all four drives were still recognized as RAID slices but came up as failed in the RAID tab. I saw no errors reported in the log so I assumed that those two drives were faulty. I shut down, moved the good drives to bays 1 & 2 and rebooted.
First reboot gave me a prohibition symbol instead of the usual Apple. Powered down and on and it booted fine but the second drive came up as a failed RAID slice. Rebooted again and both were fine.
I reinstalled the two "failed" drives and reformatted them - both reformatted fine and mounted without problems. I unmounted the new partition just in case, but, when I tried to rebuild the RAIDs I get the following in the error log:
11/1/07 7:26:00 PM Disk Utility[141] Preparing to erase : “Untitled”
11/1/07 7:26:00 PM Disk Utility[141] Partition Scheme: GUID Partition Table
11/1/07 7:26:00 PM Disk Utility[141] 1 volume will be created
11/1/07 7:26:00 PM Disk Utility[141] Name : “Untitled”
11/1/07 7:26:00 PM Disk Utility[141] Size : 149.1 GB
11/1/07 7:26:00 PM Disk Utility[141] Filesystem : Mac OS Extended (Journaled)
11/1/07 7:26:00 PM Disk Utility[141] Creating partition map.
11/1/07 7:26:03 PM Disk Utility[141] Formatting disk1s2 as Mac OS Extended (Journaled) with name Untitled.
11/1/07 7:26:06 PM Disk Utility[141] Erase complete.
11/1/07 7:26:12 PM Disk Utility[141] Unmount of “Untitled” succeeded
11/1/07 7:26:31 PM Disk Utility[141] Rebuilding RAID
11/1/07 7:26:31 PM Disk Utility[141] Filesystem: Mac OS Extended (Journaled)
11/1/07 7:26:31 PM Disk Utility[141] RAID type: Mirrored RAID Set
11/1/07 7:26:31 PM Disk Utility[141] RAID set name: “Yorktown”
11/1/07 7:26:31 PM Disk Utility[141] RAID set status before rebuild: “”
11/1/07 7:26:31 PM Disk Utility[141] RAID chunk size: 32K (default)
11/1/07 7:26:31 PM Disk Utility[141] Mirror Auto Rebuild: Disabled (default)
11/1/07 7:26:31 PM Disk Utility[141] 2 members
11/1/07 7:26:31 PM Disk Utility[141] RAID Slice (disk0s2) - Online
11/1/07 7:26:31 PM Disk Utility[141] Maxtor 6G160E0 Media (disk1) - New
11/1/07 7:26:32 PM Disk Utility[141] Error rebuilding RAID: Unrecognized Filesystem.
11/1/07 7:26:33 PM Disk Utility[141] RAID failed: Unrecognized Filesystem.
I'm at a loss at the moment. I am leaning towards bad drives, but FOUR bad drives all at once is suspicious.
I've searched for similar issues and found none so I thought I'd check here and see if anyone had any ideas.

G'day Zeekm,
Thank you for that. I did this and it seems to work. The Disk Utility GUI does not seem to work.
Hope this helps some one,
#Checked the RAID status
root# diskutil checkRAID
RAID SETS
===============================================================================
Name: Server_HD
Unique ID: 7E31E20E-F53D-4D76-AD37-139C4E1440AB
Type: Mirror
Status: Degraded
Size: 1000070610944 B
Device Node: disk2
Apple RAID Version: 2
# Device Node UUID Status
0 disk1s3 BAC72F86-B05F-4B0F-97D3-58A6207E7DFA Failed
1 disk0s3 2BFB55BB-EFF9-438C-A1F9-A8ED7A93D385 Online
===============================================================================
#Told it to resync
root# diskutil repairMirror disk2 disk1s3
Note: Syncing data between mirror partitions can take a very long time.
Note: The mirror should now be repairing itself. You can check its status using 'diskutil listRAID'.
temp:~ root# diskutil listRAID
RAID SETS
===============================================================================
Name: Server_HD
Unique ID: 7E31E20E-F53D-4D76-AD37-139C4E1440AB
Type: Mirror
Status: Degraded
Size: 1000070610944 B
Device Node: disk2
Apple RAID Version: 2
# Device Node UUID Status
0 disk1s3 9D955C85-7EC0-4E92-848A-62D9F7C12EED 0% (Rebuilding)
1 disk0s3 2BFB55BB-EFF9-438C-A1F9-A8ED7A93D385 Online
===============================================================================
Hope this helps,
Cheers,
Arthur

[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.

B-Series Disk details RAID rebuild issues after disk removal

Hi,
after removing and reinserting one disk from a RAID-1 on our B-Series blades for testing, the disk details for the reinserted disk will not be fully shown.
Only the disk itself gets detected and "Presence" shows "equipped" (see attached screenshot).
It also doen not look like the RAID would be rebuilt.
So does anyone know how to:
* Get all disk details again.
* (Automatically) reinitialize the RAID rebuild.
* Monitor the RAID status.
* Be notified of a RAID failure.
Ralph

Hi,
not very happy with the fact that UCSM doesn't display a disk or RAID status.
Any chance that we might see that in an upcoming release?
We are using ESX 4.0 U2, RHEL 6 and W2K8 R2.
Hope that MegaRAID tools would work and can be queried by SNMP (or so).
I found out how to get the disk data again and get rid of the following warning that obviously comes with not getting the disk details:
Description:
* Server sys/chassis-1/blade-6 does not fullfill Service profile vmw66 due to incompatible-number-of-local-disks
* ID: 828447
* Cause: server-failed
* Code: F0337
Solution -> re-aknowledge the server...
Any chance that this might be a bug (in 1.4.1i)?
edit: Seems that has been around for a while:
-> http://terenceluk.blogspot.com/2010/12/fixing-cisco-ucs-b-series-raid-1-mirror.html
Ralph

WAAS Raid or Hard disk failure

I encounter the issue to bring up the WAE-612-K9, and stay on the Raid controller screen with booting in loop.
On the Raid Controller screen, it displays the below message and seems detecting the Hard drive. Afte waiting around a few minutes, it will boot from the BIOS again.
===
Adaptec Serial Attached SCS (SAS) BIOS V1.2-1 1706
(c) 1998-2006 Adaptec, Inc. All Rights Reserved.
<<< Press <Ctrl><A> fro Adaptec SAS/SATA Configuration Utility! >>>
Ctrl #00: AIC-9405 SAS/SATA at PCI Slot:00, Bus:03, Dev:04, Func:00
Serial Number = ORG
RAID Support: Disabled
95
=====
Can anyone share your thought and the configuration screen of BIOS and RAID controller for reference?
Thanks.

Hi
We faced similar issue and recovered by making the device to default factory settings.
Insert the recovery CD and follow below instruction
Installer Main Menu:
1. Configure Network
2. Manufacture flash
3. Install flash cookie
4. Install flash image from network
5. Install flash image from cdrom
6. Install flash image from disk
7. Recreate RAID device (WAE-674/7341/7371 only)
8. Wipe out disks and install .bin image
9. Exit (Eject and reboot)
Choice [0]:
Make sure that you select following option exactly in this order: 2, 3, 5, 7, 8 (twice), and 9".
Regards,
Bala

RAID 5 and Disk utility problems - wrong volume size for formatting

Hi ..
I seem to have an odd problem with setting up our new RAID 5 solution. We just bought the SR6600 with seperately bought Western Digital 750Gb servergrade SATA disks.
Through the console I configured the RAID set to be RAID5 with a total capacity of 2750Gb and with a volumeset of 3000Gb (4 discs capacity and 1 disc parity).
Here's the problem:
When I'm trying to format the new volume for HFS+ usage, I open Disk Utility and it shows the volume, but the capacity is only 750Gb - similar to 1 disc's capacity. I find this odd and I've searched all over the net for a solution and answer.
Please advice if anyone know of any management software, explaination, etc.
Much appreciated, thanks!

I've run into the same issue with a newer PPC XServe. However, after I tried to reformat, I still only show up with the orginal size, and not the new size, even after I restarted the server and XRAID.
Did you have any success with your reformat?

Can a RAID created by Disk Utility be connected to another Mac?

Hi There,
We're looking to upgrade our workstation storage (4x workstations) and have recently had issues with third-party RAID cards and third-party RAID enclosures.
If we were to purchase a JBOD enclosure and use Disk Utility to create the RAID, would the RAID be recognised on different Macs if the enclosures were moved around? I realise performance would suffer compared with dedicated hardware RAID.
The main reason for using disk utility is that the smaller 4-5 disk enclosures don't seem to have RAID 10 and we've noticed a rebuild issue with 2 of our RAID 5 enclosures. After reseraching online, it turns out to be an issue inherent with RAID 5/6 (bad sectors causing issues on rebuild).
So we're thinking of buying enclosures with JBOD, then using Disk Utility to create RAID 10.
Hope that makes sense, any help or suggestions would be much appreciated.
Cheers
Ben

Grabbed a JBOD enclosure today and discovered that RAIDs made on one Mac are recognised on other Macs.

Xserve RAID issues

Here's the situation -
We have an Xserve RAID (left side full) with 2.27TB capacity and one hot spare. The RAID has been "un-mounting" itself. When connected, it does not appear in Disk Utility nor does it register as connected to the FC controller. A reboot of the Xserve RAID resolves the problem - until it happens again. Average 1-2 days between reboot (it's happened twice.)
Any thoughts or suggestions as to what might be happening?

The first question always is - What do the logs say?
I would look for fibre channel messages as well as any drive messages - especially LIP messages. If your fibre is constantly renegotiating it can cause issues like this.
Also how does the fibre card and RAID appear in the System Profiler and what does the Fibre Utility say about your connectivity?
Do you have cables to replace and/or swap them with to eliminate them from the equation?
Just some places to start,
=Tod

RAID Issue

I’m having a issue that is of grave concern to me regarding my backup RAID.
I bought a large 12 TB RAID - Mercury QX2 from OWC. I partitioned it into 6 volumes and I recently erased one volume. What is concerning me now is the way the drive appears in Disk Utility. It USED to display it like this.
QX2
    QX2_Projects
    QX2_Samples
    QX2_Storage
    and so on listing each volume.
Now, QX2_540GB does NOT appear as a volume in the Finder at all!
If you have a look at the screenshot you will see that the partitions QX2_540GB and QX2_Projects are appearing as Drives, not volumes. I don’t know why it is doing this and I would like to know if this is safe or not. I would be fine erasing and reformatting the entire drive as it’s basically a clone of each of my hard drives in my mac pro but I would prefer not to.
When I select the QX2_540GB drive OR volume, it repairs EACH and EVERY volume in the QX2 drive which is rather bizarre!
I would greatly appreciate any suggestions!

Darn...Well, good luck. I haven't had issues like that, so...
But yes, you can Raid the two towers separately, then Raid them together into a Raid 50...not that i know how to do that. Hmm...I think you need a Rocket Raid for that. I seem to recall that we had that.
But there are advantages to raid striping all the drives...faster throughput for high end HD. What format are you working with? It might be more than you need. Simply raiding the towers separately would be enough for uncompressed HD.
Sorry I can't be more help.
Shane

"Could not find RAID" error in Disk Utility

Hello,
I could really use some help as this problem is causing me lots of headaches. I have two 500GB MyBook hard-drives connected to my MacBook Pro via two USB's. I had them setup as a mirrored RAID, and they were working properly for quite sometime. However over the past few weeks I noticed they were always in a degraded state, and Disk Utility would always rebuild them. However after the rebuild they would still have the status of "Degraded" and the next time Disk Utility opened it would start the rebuilding process yet again.
So I moved all the data on the drives to a backup, and I stopped the mirrored RAID. After erasing the data on the drives individually I attempted to setup the mirror again. However after the mirror had just about finished, and it was to the point of "bringing the RAID online" I always get an error that states "Creating RAID set failed", "Creating RAID set failed with the error: Could not find RAID.".
I'm hoping someone smarter than myself in this area can lend me some time and assistance to solving this issue.
Thanks,
Paul

Well. No one really came to my rescue with this question. Turned out to be a Finder issue. After reinstalling the operating system everything started working again with Disk Utility.
Later,
Paul

RAID Issues - Standby Disk

Similar Messages

Maybe you are looking for