Different capacity of array in RAID Admin as in Disk Utility

I've an XRAID controlled by XServe PPC with MacOSX 10.3.9.
In Lower Controller I've two arrays:
4x500GB drive=1,4TB RAID5,
2x500GB drive=0,931GB RAID0.
1x500GB drive as HotSpare.
I've expanded RID5 Set with 5th Drive (RAIDAdmin->Advanced->Expansion) - initialization take about 50 hours (but not the time is a problem).
My problem is that - after initialization RAIDAdmin shows that this Array has 1.82TB Capacity but Disk Utility show that this volume has only 1.4TB. I can format this volume, I can partition but I'm limited to this 1.4TB.
I've restarted Controler, restartet whole RAID, restarted ma XServe - but it give nothing. I've also do so: slice'ing and back - merging this Array. The same situation.
What should I do to have the right capacity?

The disk format comes from Disk Utility when you initialize it. When the raw RAID is created it is just raw storage that could be any format. When you create a partition in Hard Disk Utility is when the type of disk is chosen.
Mac OS Extended is HFS+. Unless you're doing disk heavy work like video editing or capture you probably want Journaling. I would stay away from Case sensitivity unless you're specifically working with Unix machines - especially on earlier OS X versions.
I'm a little confused from your post about where you are in the initialization process - it sounds like you've started it already. With 500GB drives expect it to take in the ~30 hours range. If you choose "Use RAID now" you've be able to format and use your during that 30+ hour initialization process but certainly not at anything like full RAID 5 speeds. If you can wait I would wait, but many people use it that way. Once your RAID is ready it should show up as the full size when you go to partition it.
HTH,
=Tod

Similar Messages

Xserve Raid not recognized by Disk Utility

My Xserve Raid is recognized when I run the RaidAdmin utility. I can create new arrays everything shows up without any problems. I updated the firmware for the Xserve Raid using just the ethernet connection to administer it. Changed the card and the cables that are used to connect the Raid server to a G5 server, but it still does not get recognized by Disk Utility. I am at a loss of what to do next. I have green lights for everything....no problems showing up in RaidAdmin. Please, please help....

Hello
I have the exact same problem: after updating java and rebooting the server, the raid array is no longer visible. Everything is green, no errors in the log files, fibre channel is up and running, BUT: the array does not show with any SCSI address. LUN masking is off. Server is at 10.5.8 (intel). The array was mounting just fine before the reboot (and all before that). I've plugged the fibre channel into a PPC server, same thing: link ok, no SCSI. I'm reconditioning the drive at the moment, but it should still be visible.
Any help greatly appreciated.

How do you break a RAID 1 created in Disk Utility and retain data?

Good Morning all !!
Quick subject question.
Background: I have 2-3 TB of important data that i use only rarely. I purchased two 4TB external drives. I could not use a 2 drive raid enclosure because of the fan noise in the studio. I selected 800 firewire fanless enclosures. The technican talked me into using the Disk Utility Raid 1 in Mountain Lion OS.
Problem: I only plug them in when needed probably once a week. The raid rebuilds every time I use the raid. That takes about a day. This arrangement is less than ideal.
Question: Can I break the raid and still have the data intact on 2 separate drives? Of coarse I would do it when they a rebuilt.
Thanks.
Mike

Good Morning all !!
Quick subject question.
Background: I have 2-3 TB of important data that i use only rarely. I purchased two 4TB external drives. I could not use a 2 drive raid enclosure because of the fan noise in the studio. I selected 800 firewire fanless enclosures. The technican talked me into using the Disk Utility Raid 1 in Mountain Lion OS.
Problem: I only plug them in when needed probably once a week. The raid rebuilds every time I use the raid. That takes about a day. This arrangement is less than ideal.
Question: Can I break the raid and still have the data intact on 2 separate drives? Of coarse I would do it when they a rebuilt.
Thanks.
Mike

Disk utility doesn't show xServe RAID Array

I have a new (to me) xServe RAID box and I'm stuck, the stays lights are green the fiber link light is green on the RAID and not lit on the PCI card but shows up as green in the fiber link section of the settings tool but the RAID array doesn't show up in Disk Utility so I can't format the drives.
I set up the disks as Enhanced JBOD using RAIDadmin and I've deleted and created it a couple of times, I'm just not sure what else I should try, I've read the manual but. Can't find any suggestions of what's going wrong.
Thanks

If you have tried restarting a few times and it still doesn't show up I'm afraid you are gonna have to go back in and check the connections. I know they just slot into the carriage, but possibly it is not in tight. I can only suggest you open it up and check everything thoroughly. If after a thorough check, if it still does not mount you may want to take the hard drive back and swap it. Are you sure it was only a hard drive failure in the first place? I only ask this because WD hard drives have quite a solid reputation.

XServe RAID disks not showing up in Disk Utility

I have a new (to me) xServe RAID box and I'm stuck, the stays lights are green the fiber link light is green on the RAID and not lit on the PCI card but shows up as green in the fiber link section of the settings tool but the RAID array doesn't show up in Disk Utility so I can't format the drives.
I set up the disks as Enhanced JBOD using RAIDadmin and I've deleted and created it a couple of times, I'm just not sure what else I should try, I've read the manual but. Can't find any suggestions of what's going wrong.
Thanks

Port 1: Link Established
2Gps
Point to point
Status light green
In the system Profiler I'm not sure what you're asking for, I'm running 10.5.8 standard not server.
the fibre channel shows link established 2Gps and cable type copper but nothing else, the disks & RAID controller don't show up anywhere I've looked.
RAID Admin shows the JBOD disks as online and lists the LUNs etc.
System looks fine, only error is missing second power supply.

Array showing up twice in Disk Utility.

I have an odd problem.
We have a XServ RAID (XSR) that had two 4 disk arrays(raid5, one on each controller (Disk 1-4 on controller 1, and disk 8-11 on controller 2) Working great for almost 2 years. Last week we filled out our XSR with 6 more drives (3 on each controller) When I create 2 new arrays (one 3 disk RAID 5 comprising disk 5-7 on controller 1 and one 3 disk RAID 5 comprising disk 12-14 on controller 2) they show up twice in Disk Utility. I see the 2 701GB arrays that have been working fine for 2 years, each one shows up once. The 2 new 476GB arrays are showing up twice (2 times each for each array for a total of 4 476GB arrays). This shows up in disk utility on any computer connected to the fibre switch, and only the new arrays are duplicated so it isn't a zoning issue with the switch.
Any ideas?
Thanks!
XServ RAID 250gb disks Mac OS X (10.3.2)
Dual 1.8 G5 Mac OS X (10.4.3)
Dual 1.8 G5 Mac OS X (10.4.3)

I ran into Doug Cunningham at the DV Expo and he said to use the "Repair Lun Map" in RAID Admin... Worked!!!
Thanks!

Disk Utility Says System RAID Degraded - Does this mean what I think it is?

Hi All
I have a Mirrored RAID Set for my System Drive - being two 931.5 GB Hitachi Drives. This Mirrored RAID Set I have called System RAID. If I click on the RAID Slice in the Disk Utility it says that the "System RAID" is Degraded, and under this [tabbed in] it says 931.2 GB - RAID Slice (disk0s2) Failed with the other under that saying 931.2 GB - RAID Slice (disk1s2) with no comment it has failed [obviously].
So if this essentially means my the first drive in my RAID set has failed then I will lose all data if the second fails also, is this correct?
So what should my next step be? Should I shut down the machine until I can purchase a spare drive to replace the currently damaged one? AND most importantly, HOW do I replace the drive and have it rebuild as the new second drive without erasing / losing data - IE what is the protocol now??
Please your immediate assistance is GREATLY APPRECIATED!
OH and AHH I've just seen in System Profiler that a 2 GB RAM chip appears to have failed
DIMM Riser A/DIMM 4:
Size: 2 GB
Type: DDR2 FB-DIMM
Speed: 800 MHz
Status: ECC Errors
ECC Correctable Errors: 1
Manufacturer: 0x7F61
Part Number: 0x000000000000000000000000000000000000
Serial Number: 0x00000000
What is going on!!

Hi Kappy<
I am trying to migrate user data from a RAID - 1 slice from my old PowerMac G4 running OS X 10.4.11 to my new MacBook Pro running OS X 10.5.4 by reading a mirror RAID slice from my old Mac that is mounted in an external drive enclosure and connected by FireWire.
The problem is that the new Mac cannot read the old Mac disk, it never shows up on the desktop, or comes up as available when trying to use Migration Assistant. Then, if I go into Disk Utility, the external RAID slice shows up briefly with a locked yellow padlock beside it, then I suddenly get the window shade of death, and have to hold down the power button to reset/restart my MacBook.
Why can my new computer not read my old computers disk, and how can I change permissions, or make the old drive readable by the new mac.
Regrettably I am away from the original Desktop, and cannot load the old drive back into it, connect the two machines and migrate that way. My only option for reaching my necessary data is to retrieve it off the drive I have with me.
Thanks in advance for any help you can offer.

Rebuilding a Mirrored Raid using Disk Utility

I have a mirrored raid set up via disk utility. For some reason one drive was switched off recently so the 2 drives are now out of sync. Disk utility now says the raid is 'Degraded' with one of the slices marked as 'failed'
I can ignore this as the drive appears fine on the desktop. But I need it to be working correctly as a fully operating RAID.
If I click 'rebuild' it gives a warning saying 'Rebuilding a RAID set will destroy all information on the replacement disk “RAID Slice”.
SO- I'm assuming rebuild will correct the error and make it work but I'm concerned about this warning about destroying data! I assume it will simply copy everything from Drive A to the 'degraded' Drive B??
Thanks for any suggestions.

"SO- I'm assuming rebuild will correct the error and make it work but I'm concerned about this warning about destroying data! I assume it will simply copy everything from Drive A to the 'degraded' Drive B??"
This should indeed be the way it goes but since i do not have enough experience with that kind or RAID setup i strongly suggest backing up / cloning drive A to an external before doing the rebuild... just in case.

Adding new raid with different capacity drives on opposite side

hi,
I have an Xserve raid G4 with two sides of 7 bays. Currently one side is filled up with 7 250 gb Apple drives making a 1.37TB raid 5 and the other side is all empty. I just purchased 7 Apple 500gb drives and was wondering if I can combine the 2 sides into one raid 5 or because of the different capacity drives, must I have 2 raid 5s? I am thinking the latter.
(I have done a search for an answer to this question and couldn't find a similar question. So, let me apologize if this is redundant info here.)
Thanks

The two sides are completely independent, so regardless of the size of the drives you cannot combine the drives on the left side in the same hardware-based RAID array with drives on the right hand side.
It is, however, perfectly valid to have an array of 250GB drives on the left, with a separate array of 500GB drives on the right.
That said, once you have two (or more) arrays, you can combine them into a single volume on the desktop using software RAID to concatenate the multiple volumes.
If you decide to install the 500GB drives on the same side to incorporate them in the existing array then they will be treated as 250GB drives and the additional capacity will be lost.

Raid Admin 1.5 - Recognize Array button not active

Hi all,
just updated to RaidAdmin 1.5, updated firmware on both controllers to 1.5 version.
I have 6 disks on which should be my lost array. Suddenly 'Recognize Array' button in utilities is not active.
Any idea?
Leos.

ok. The whole story:
Few month ago, I had RAID 3 schema on 6 disks. I did firmware update on my XRaid. This update WAS SUCCESSFUL. After XRaid restart, I lost my array. I didn't have backup. After unsuccessful local Apple support, I tried 3rd party companies to reascue my data. Noone helped me. I managed help from Apple in US, I sent my disks to them (quite expencive, I am from Czech Republic.). They recovered raid set on my disks to RAID 3 schema on 5 disks only - don't understand this. So I called them back a and I sent disks again, with detailed desription how it must be. Thay sayed OK and sent me back 6 disks, with no raid set schema - 6 unassigned to any array. And as a bonus, one of them was failed. So, now I have 6 disks, Apple claims, that raid schema is on disks (but i cannot see it on my raid - I realy tried everything - swapping possitions, controllers, cables .....). So when Raid Admin 1.5 brings this new function - recognize array, I started thinkink, that I have one more chance to recover my data back. But situation is as I described in first topic....

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?

RAID Admin doesn't see RAID array

Had to do a complete reinstall of all software and Xserve RAID has disappeared from RAID Admin. Have read a LOT more about this problem on this and other forums. I'm certain the company that set the system up for me left the RAID in DHCP mode. Wish I had known better 12 hours ago.
I tried the ping trick detailed in other threads, but I only get a "127.0.0.1" response. What am I doing wrong?
CPU plugged directly into upper RAID controller. Airport off. No other network connections. All lights are green. RAID functions fine otherwise. Tried with G5 and iBook with same results.

You said the Raid functions fine. I assume you meant that the volumes mount fine? Does that include the iBook seeing the volume(s) via the Ethernet?
If that's the case, then the host is serving up the raid volumes fine, which happens solely via the fibre channel connection.
2 things to check:
1. Since it sounds like the RAID was setup by somebody else, you might want to make sure that the upper controller on the RAID also has the Ethernet cable connected to it, not just the Fibre cable. This is a requirement for the admin software.
2. If it is, make sure that it connected to a switch that is on the same network segment as the computers that you try to run the admin software on.
This can be tricky if you have multiple switches with VLAN's assigned to certain ports as it may not be so obvious...
Worst case scenario is to reset the controller back to its default setting. A paper clip will do the job...
Xserve G5 Mac OS X (10.4.3)

RAID Admin reality check -- this software needs serious work

Folks: This is a combination rant about RAID Admin 1.5 (on OSX 10.3.9) and plea for any suggestions for things I may have missed.
RAID Admin -- an utterly crucial tool for responsibly administering an X Serve RAID, itself offered for use in mission critical applications. But RAID Admin is just one frustration after another.
1. Can't start due to broken Java or somesuch. As reported by several others elsewhere, and experienced herre, some QT upgrade breaks ability to launch RA. Thee's a "solution" of rolling back QT -- doesn't work. There's a command-line workaround for launching, but if this is really broken Java, how can you trust other functions of RA? Anyhow, we're running it from console of X Server with non-recent-QT.
2. Finding the RAID Array is totally hit or miss. (And BTW -- don't get hosed by the little feature that it's not sufficient to have the RAID hooked up by fiber... you also have to have the ethernet cables connected). Sometines RA finds the nearby RAIDs by itself, sometimes it finds one of two, sometimes none... figure on entering the IP addresses by hand.
3. Serious memory leak. Leave RA running for a few hours and it ***** up >100% CPU (on dual G4), huge amount of memory, and is almost completely unresponsive (apparently due to huge disk activity to swap virtual memory). Example: after 12 hours uses 372 Meg of real memory and 1.3 G of VM. Quit and restart fixes the problem... but do you really want to do that in midst of lengthy admin operation?
4. Array Conditioning: Seems like a great idea -- but how can you tell whether it's doing anything useful? It generates errors to the event window showing bad blocks.... OK great... what do they mean? Is it fixing them? Where is its output? Maybe we could learn that from the docs....
5. Oh right... no docs. Still stuck on RA 1.2 docs. No mention of Array Conditioning found anywhere in Help, or at apple.com... except to advertise that the feature exists.
Graham

William, thanks for your response, comments inline below:
I have not personally experienced any of the first 3
issues you note. And I've run RAID Admin on 30-40
different systems, and monitored 100+ RAIDs, over the
past 3 years.
... it is good to hear a general level of satisfaction...
Are you experiencing this on just one system --
have you ever tried another machine?
What do you mean? We have one X Serve, and one RAID, and that's the one we need to admin. How would we introduce another machine into the scenario?
I'd suggest that your Java installation has
serious issues.
Why would you suggest that? As I noted, the Java-suspected issue was not on the machine that I reported the rest of the problems on. It simple obliges us not to use RAID Admin remotely (and conveniently) since all the remote machines are up to date with updates including QT.
Also note, it's impossible for RAID Admin to have a
leak. Java has a garbage collector. Therefore, if
there's a leak, it's a JVM problem, and not a RAID
Admin problem.
That line of argument would be correct if the leak was due to orphaned objects -- ie: objects no longer refered to and not garbage collected. There's nothing to stop a program in whatever language just consuming more and more memory because the programmer neglected to throw away unneeded objects.
However, since posting, the Array Conditioning operation has completed, and I've noticed that the memory eating behavior has stopped. I've posted a correction on this.
For #4 and #5, I'd suggest reading the Kbase article
which details the updates and what they're good for:
http://docs.info.apple.com/article.html?artnum=302780
Where on that page are you seeing info that addresses 4 and 5? This is in fact the one page I was refering to: it advertises the feature, but where are the docs?
I'd suggest you figure out what's wrong
with your Java installation.
No reason to suspect Java on the server, where we are running RAID Admin.
I posted some command-line options which will
give diagnostic output in other threads,
... that could be useful, could you be more specific about where you posted them, and do they cover the result of Array Conditioning?
Thanks again for your answers,
Graham

Xserve RAID Admin Tool 1.5.1 not quite working

I have an Xserve RAID that's currently at firmware 1.3.2/1.26a according to Xserve RAID Admin Tool 1.5.1. However, when I try to upgrade the firmware to 1.5.1 via the RAID Admin Tool 1.5.1, it just doesn't do anything--it accepts the .xfb file and then...nothing. Quitting out of the the Admin Tool and restarting still shows the firmware at 1.3.2/1.26a. Same thing if I shut down and restart the Xserve RAID from the RAID Admin tool. Any tips? There's nothing stored on the RAID system yet (the array hasn't even been created--it's a blank system) and nothing is attached to it either (I've just plugged in the ethernet links to format it first before I start attaching an Xserve G5 to it). Also, even though the lower controller is showing green and I have an ethernet cable plugged into it, I can't get any info out of it nor can I configure it with an IP address. Only the top controller seems to allow some configuration such as IP address.

Okay, I've solved the problem.
Basically, the issue was that the lower controller wasn't seated right despite it showing a green light in RAID Admin. When I went to visually inspect it, I noticed that despite what RAID Admin 1.5.1 claimed, its light wasn't even on, let alone green. And since the lower controller handles slots 8-14 of an Xserve RAID and my slots 8-14 are totally unpopulated (empty) at the moment, it was never noticed. Now that I've reseated the lower controller, everything is visually showing green across the board and the firmware upgrade is proceeding as expected and it has upgraded the firmware from 1.3.2/1.26a to 1.5.1/1.5.1c complete with autorestart of both upper and lower controller modules.
Basic lesson learned: RAID Admin lies. If possible, visually inspect the box itself!
Thanks to all who responded.

Unknown Raid 5 Array after Raid controller replaced

Hello,
I had a raid controller fail during the week, and after shutting the xraid down and installing the new controller, all the drives in the array are now amber.
In Raid Admin 1.5 the array does not show up, only all 6 member drives with an amber warning and 'Type: Unknown Array'.
I used the 'Recognize Array' utility to try and fix this, however whilst each drive shows as being recognized as being part of a Raid 5 set, it will not recreate it.
Am I completely screwed? or is there some other way to get this to repair/recognize?
Any tips would be greatly appreciated.
Thanks
Mark

Due to time restrictions on getting the xraid back online, had to recreate the raid and restore data from backup.
No fix found.

Different capacity of array in RAID Admin as in Disk Utility

Similar Messages

Maybe you are looking for