Switching RAID volumes between servers

If I have two Xserve G5s with mirrored RAID arrays, how easy is it to "switch" the hard drives from one server to another, and the entire operating system along with them while retaining the RAID array?
Is it as easy as removing the hard drives and putting them in the new Xserve or do I have to rebuild the array? If so, how?
My servers have the hardware RAID card, what are the advantages over software RAID?

I have been reading through the many posts to see if someone had the same question I did.... and this one comes close. The only response however is based on the hardware RAID. I would like to know if you can move an Apple Software (disk utilities) mirrored set of drives (Boot Volume) from one G4 Xserve to another of similar model.
I have just received a spare Xserve G4 dual processor (1 GHz). My other xServes are all single 1 GHz processors. I wanted to take advantage of the extra processor for one of the machines. Then, if one of the Xserves fails I want to just pull the two drives (mirrored) out of the failed computer and put them in the spare machine.
Does Apple software RAID store everything on the drives themselves or does it write something to PRAM of the Xserve or similar for the drive ID's?
xServe 64 1 Ghz Single Processor   Mac OS X (10.4.6)  

Similar Messages

  • Moving volumes between servers

    First, I'm new at this, so allow for my ignorance.
    Second, we are ARCHIVING data on StorEdge L3500s and sometime in the next 10 months intend to upgrade to L7000s.
    The issue: we have two L3500s on different LANs. ServerA has volumes labeled from AWR101 through AWR198 and is on 196.201.xxx.xxx. ServerA archives data from clientA. ServerB has volumes labeled from AWR201 through AWR298 and is on 198.144.xxx.xxx. ServerB ARCHIVES data from clientX. ClientA is not recognized on ServerB's LAN and clientX is not recognized on ServerA's LAN. How can I get ServerB to recognize and retrieve data from a volume from ServerB?
    For example, volume AWR101 contains archived file /var/log/syslog from clientA. I load AWR101 to slot 01 on ServerB (after removing the ServerB's volume) and am able to inventory it so the MOUNT display at slot 01 indicates AWR101* (the * appears to be the key problem here). However I cannot mount nor retrieve the file to ServerB, either by application or via command level.
    After retrieving the data to ServerB, the intent is to eventually load AWR101 back to ServerA. And have ServerA (and ServerB) able to "recognize" the volume that was originally in its slot 01.
    I appreciate any assistance.
    Ed

    It would be easier if I knew what archival software you were using to backup to tape. The naming convention looks like something I'd use for Veritas Netbackup. In either case, you could simply move the volume(s) involved with particular backup image, and import the volume into Server B's database.
    This is quite a bit more complex with HSM software like SAMFS(Netbackup and EBU have the same function).
    After that point, the library slot can be whatever you want it to be, as long as you have the archival/backup software gather the tape inventory from the library, and update the software database with it's contents. The volume will still be in the database as long as the retention policy has not expired.

  • Migrating RAID volume disks between T2000s

    I understand that migrating RAID volumes between T2000s is not supported, as specified in http://docs.sun.com/source/819-2549-12/ontario-volume_man.html which states "Volume migration (relocating all RAID volume disk members from one Sun Fire T2000 chassis to another) is not supported. If this operation must be performed, please contact Sun Service.". If I understand this correctly, it is because the LSI hardware RAID controller writes some controller-specific or system-specific information to the disks when it creates a RAID volume.
    I need to move disks between T2000 systems, and I do not need to preserve data on the disks. Is it sufficient to simply remove the RAID volume from the disks (i.e. raidctl -d), then move them to the new T2000 system? There has been some suggestion within my company that the disks need to be completely reformatted, but I haven't been able to locate any requirement to reformat the disks in either Sun documentation or these forums.

    I don't believe we came to a conclusion on this issue. I will check with my team and get back to you. We may have an opportunity to rebuild a T2000 system in the next few weeks, and, if so, we'll gather the data and report back.

  • Raid Volumes Randomly Dismounting

    Okay first a warning .. this is going to be a long post!
    Overview: When my raid is connected through my Fibre Channel Switch it randomly dismounts.
    Specifics:
    Xserve G5 (10.4.7) with the LSI Dual-Channel 2GB Fibre Channel PCI-X HBA & Fibre Channel Utility 2.0
    Xserve RAID - Each side with its own Raid 5 , hot spare - no masking & latest firmware
    Exabyte Magnum 224 FC
    Qlogic Sanbox 5200 Series (12 port) - Latest Firmware (configured with two zones (port not WWN) ; Zone 1: Port 1 HBA, Both Xraid | Zone 2: Port 0 HBA, Exabyte
    Background : This used to ALL work! Recently we began to experience drastic slow downs when writing to the raid and common sense not working free space, which was the problem, was the last thing I checked. Before that though I tried swapping cables, replacing the raid controller, redoing zoning, straight connect - Obviously none of this was the issue. *note here: at this point I am using an identical Fibre Channel Card in my Xserve from my G4 - a careless maneuver broke the Apple installed card whilst it was laying on a table.*
    When I got things working (made room on the volume) I happened to be in a configuration the circumvented the switch.. raid directly into the host and things , as said, worked fine. The next night I took the systems down to put everything on the switch again to allow a back-up to be ran. Now is when the current behavior begins. Randomly and without recognizable patterns both raid volumes would dismount from the host. Checking Raid Admin shows the volumes as being in order and all lights are green.
    This time I fear my switch has gone and after time spent with Qlogic (and zilliions of different configurations) a new switch is sent out in the mean time back to a straight connection and things are working fine. New switch arrives, is configured, and immediately problem persists. Qlogic/Apple suggest the midplane on the raid is bad (even though it works straight through). I happen to have a brand new in box XRAID (with current firmware) so I set that up put in the drives from the old raid and the problem persists again when plugged into the switch. Direct to host things work fine.
    So I read some documentation on Apple and Fibre channel and made a few changes to HBA ports and Switch Port Settings and came to the following scenario... Volumes stayed mounted through an entire work day, but after a brief time into a backup the volumes unmounted.
    Here is some more specific info about my exact setup as it last failed...
    ZONE 1 (zoned by port not WWN)
    Switch Ports 0, 1, 2
    HBA Port 1 into Switch Port 0
    Raid into Switch Ports 1, 2
    All ports are identifying themselves to switch as switch topology
    HBA port configured as Topology: Point-to-Point, Speed: 2Gb/s
    SW Port 0 configed as State: Online, Speed: auto, Type: Detect, I/O Stream Guard: Enable, Device Scan: Disable
    SW Port 1, 2 configed as State: Online, Speed: auto, Type: Detect, I/O Stream Guard: Auto, Device Scan: Enable
    ZONE 2 (zoned by port not WWN)
    Switch Ports 8, 9
    HBA Port 0 into Switch Port 9
    Exabyte into Switch Port 8
    Port 8 identifying as Loop topology, 9 as switch
    HBA port configured as Topology: Auto, Speed: Auto
    SW Port 8 configed as State: Online, Speed: auto, Type: Detect, I/O Stream Guard: Auto, Device Scan: Enable
    SW Port 9 configed as State: Online, Speed: auto, Type: Detect, I/O Stream Guard: Enable, Device Scan: Disable
    I realize that some of these settings, particularly those on the HBA are different between ports, but we have tried virtually every combination (I think)
    Around the time of the backup job system.log on the host has these entries:
    Mar 7 17:55:41 files kernel[0]: FusionMPT: Notification = 5 (External Bus Reset) for SCSI Domain = 3
    Mar 7 17:55:41 files kernel[0]: FusionMPT: External Bus Reset for SCSI Domain = 3
    Mar 7 17:55:41 files kernel[0]: FusionMPT: Notification = 7 (Link Status Change) for SCSI Domain = 3
    Mar 7 17:55:41 files kernel[0]: FusionFC: Link is down for SCSI Domain = 3.
    Mar 7 17:55:41 files kernel[0]: FusionMPT: Notification = 8 (Loop State Change) for SCSI Domain = 3
    Mar 7 17:55:41 files kernel[0]: FusionFC: Loop Initialization Packet for SCSI Domain = 3.
    Mar 7 17:55:41 files kernel[0]: FusionMPT: Notification = 9 (Logout) for SCSI Domain = 3
    Mar 7 17:55:41 files kernel[0]: FusionMPT: Notification = 7 (Link Status Change) for SCSI Domain = 3
    Mar 7 17:55:41 files kernel[0]: FusionFC: Link is active for SCSI Domain = 3.
    Mar 7 17:55:41 files kernel[0]: FusionMPT: Notification = 6 (Rescan) for SCSI Domain = 3
    Mar 7 17:55:41 files kernel[0]: FusionMPT: Notification = 5 (External Bus Reset) for SCSI Domain = 3
    Mar 7 17:55:41 files kernel[0]: FusionMPT: External Bus Reset for SCSI Domain = 3
    Mar 7 17:55:41 files kernel[0]: FusionMPT: Notification = 7 (Link Status Change) for SCSI Domain = 3
    Mar 7 17:55:41 files kernel[0]: FusionFC: Link is down for SCSI Domain = 3.
    Mar 7 17:55:41 files kernel[0]: FusionMPT: Notification = 8 (Loop State Change) for SCSI Domain = 3
    Mar 7 17:55:41 files kernel[0]: FusionFC: Loop Initialization Packet for SCSI Domain = 3.
    Mar 7 17:55:41 files kernel[0]: FusionMPT: Notification = 9 (Logout) for SCSI Domain = 3
    Mar 7 17:55:41 files kernel[0]: FusionMPT: Notification = 7 (Link Status Change) for SCSI Domain = 3
    Mar 7 17:55:41 files kernel[0]: FusionFC: Link is active for SCSI Domain = 3.
    Mar 7 17:55:41 files kernel[0]: FusionMPT: Notification = 6 (Rescan) for SCSI Domain = 3
    Mar 7 17:55:41 files kernel[0]: FusionMPT: Notification = 5 (External Bus Reset) for SCSI Domain = 3
    Mar 7 17:55:41 files kernel[0]: FusionMPT: External Bus Reset for SCSI Domain = 3
    Mar 7 17:55:41 files kernel[0]: FusionMPT: Notification = 7 (Link Status Change) for SCSI Domain = 3
    Mar 7 17:55:41 files kernel[0]: FusionFC: Link is down for SCSI Domain = 3.
    Mar 7 17:55:41 files kernel[0]: FusionMPT: Notification = 8 (Loop State Change) for SCSI Domain = 3
    Mar 7 17:55:41 files kernel[0]: FusionFC: Loop Initialization Packet for SCSI Domain = 3.
    Mar 7 17:55:41 files kernel[0]: FusionMPT: Notification = 9 (Logout) for SCSI Domain = 3
    Mar 7 17:55:41 files kernel[0]: FusionMPT: Notification = 7 (Link Status Change) for SCSI Domain = 3
    Mar 7 17:55:41 files kernel[0]: FusionFC: Link is active for SCSI Domain = 3.
    Mar 7 17:55:41 files kernel[0]: FusionMPT: Notification = 6 (Rescan) for SCSI Domain = 3
    Mar 7 17:55:41 files kernel[0]: FusionMPT: Notification = 5 (External Bus Reset) for SCSI Domain = 3
    Mar 7 17:55:41 files kernel[0]: FusionMPT: External Bus Reset for SCSI Domain = 3
    Mar 7 17:55:41 files kernel[0]: FusionMPT: Notification = 7 (Link Status Change) for SCSI Domain = 3
    Mar 7 17:55:41 files kernel[0]: FusionFC: Link is down for SCSI Domain = 3.
    Mar 7 17:55:41 files kernel[0]: FusionMPT: Notification = 8 (Loop State Change) for SCSI Domain = 3
    Mar 7 17:55:41 files kernel[0]: FusionFC: Loop Initialization Packet for SCSI Domain = 3.
    Mar 7 17:55:41 files kernel[0]: FusionMPT: Notification = 9 (Logout) for SCSI Domain = 3
    Mar 7 17:55:41 files kernel[0]: FusionMPT: Notification = 7 (Link Status Change) for SCSI Domain = 3
    Mar 7 17:55:41 files kernel[0]: FusionFC: Link is active for SCSI Domain = 3.
    Mar 7 17:55:41 files kernel[0]: FusionMPT: Notification = 6 (Rescan) for SCSI Domain = 3
    Mar 7 17:55:42 files kernel[0]: FusionMPT: Notification = 5 (External Bus Reset) for SCSI Domain = 3
    Mar 7 17:55:42 files kernel[0]: FusionMPT: External Bus Reset for SCSI Domain = 3
    Mar 7 17:55:42 files kernel[0]: FusionMPT: Notification = 7 (Link Status Change) for SCSI Domain = 3
    Mar 7 17:55:42 files kernel[0]: FusionFC: Link is down for SCSI Domain = 3.
    Mar 7 17:55:42 files kernel[0]: FusionMPT: Notification = 8 (Loop State Change) for SCSI Domain = 3
    Mar 7 17:55:42 files kernel[0]: FusionFC: Loop Initialization Packet for SCSI Domain = 3.
    Mar 7 17:55:42 files kernel[0]: FusionMPT: Notification = 9 (Logout) for SCSI Domain = 3
    Mar 7 17:55:42 files kernel[0]: FusionMPT: Notification = 7 (Link Status Change) for SCSI Domain = 3
    Mar 7 17:55:42 files kernel[0]: FusionFC: Link is active for SCSI Domain = 3.
    Mar 7 17:55:42 files kernel[0]: FusionMPT: Notification = 6 (Rescan) for SCSI Domain = 3
    Mar 7 17:55:42 files kernel[0]: disk4s3: I/O error.
    Mar 7 17:55:42 files kernel[0]: FusionMPT: Notification = 5 (External Bus Reset) for SCSI Domain = 3
    Mar 7 17:55:42 files kernel[0]: FusionMPT: External Bus Reset for SCSI Domain = 3
    Mar 7 17:55:42 files kernel[0]: FusionMPT: Notification = 7 (Link Status Change) for SCSI Domain = 3
    Mar 7 17:55:42 files kernel[0]: FusionFC: Link is down for SCSI Domain = 3.
    Mar 7 17:55:50 files kernel[0]: s3: I/O error.
    =======
    Then followed by a ton of various I/O errors
    =======
    Mar 7 17:56:42 files kernel[0]: disk4s3: I/O error.
    Mar 7 17:56:42 files kernel[0]: disk4s3: I/O error.
    Mar 7 17:56:42 files kernel[0]: disk4s3: I/O error.
    Mar 7 17:56:42 files kernel[0]: FusionMPT: Notification = 6 (Rescan) for SCSI Domain = 3
    Mar 7 17:56:42 files kernel[0]: disk4s3: I/O error.
    Mar 7 17:56:42 files kernel[0]: disk4s3: I/O error.
    =======
    Finally by media not present errors which end the log
    =======
    Mar 7 17:56:42 files kernel[0]: disk4s3: media is not present.
    Mar 7 17:56:42 files kernel[0]: disk4s3: media is not present.
    Mar 7 17:56:42 files kernel[0]: disk4s3: media is not present.
    Mar 7 17:56:42 files kernel[0]: disk4s3: media is not present.
    Mar 7 17:56:42 files kernel[0]: disk4s3: media is not present.
    Mar 7 17:56:42 files kernel[0]: disk4s3: media is not present.
    Mar 7 17:56:42 files kernel[0]: disk4s3: media is not present.
    Mar 7 17:56:42 files kernel[0]: disk4s3: media is not present.
    Mar 7 17:56:42 files kernel[0]: disk4s3: media is not present.
    Mar 7 17:56:42 files kernel[0]: disk5s3: media is not present.
    Mar 7 17:56:42 files kernel[0]: jnl: dojnlio: strategy err 0x6
    Mar 7 17:56:42 files kernel[0]: jnl: end_transaction: only wrote 0 of 8192 bytes to the journal!
    Mar 7 17:56:42 files kernel[0]: jnl: close: journal 0x4c21bb4, is invalid. aborting outstanding transactions
    Mar 7 17:56:42 files kernel[0]: disk4s3: media is not present.
    Mar 7 17:56:42 files kernel[0]: disk4s3: media is not present.
    Mar 7 17:56:42 files kernel[0]: disk4s3: media is not present.
    Mar 7 17:56:45 files kernel[0]: jnl: close: journal 0x4c21c98, is invalid. aborting outstanding transactions
    And that folks is it.. I'm up for any and all suggestions, questions, comments etc.. I'm absolutely desperate here!
    Please, please does anyone have any ideas what's going on here.
    Thanks,
    James Nierodzik

    Hi Roger, thanks for the reply.
    Throughout the battles I did try cables that were not in the scenario to no avail so I don't think it's a cablling issue though I suppose it still could be.
    Well into the backup was last night's failure point.. days previous, when through the switch, it had failed at periodic points throughout the day. I could not tie those periods to greater than normal I/O demand though.
    As for cooling the components are kept in a well circulated room that is kept 24x7 at 62 degrees with an alarm on the cooling unit so I am about as certain as can be that cooling is not a factor.

  • Communication between servers on different FIs

    Just want to verify communication between UCS servers on same chassis but having active vNICs on different FIs (Diagram attached). I suppose all commuication between server-A & server-B will happen through Layer 2 switch as server-A will generate an ARP request for Server-B, that will be passed over to FI-A and then to L2 switch down to FI-B, where server-B will respond back with it's MAC that will then be passed to Server-A via FI-B to L2 switch to FI-A.I don't expect any traffic between servers A & B be routed via firewall? Is there anything I need to be careful about in this design? Going forward we will have multiple subinterfaces on the firewall for different VLANs and all servers will use Firewall as default gateway.

    you may want to look at the throughput of your firewall for server-server traffic in different VLANs. If your L2 switch is 10G but your firewall is only 1G then you could have a potential bottle neck.

  • UCSM 2.1 Local disk configuration policy and raid volumes

    Hi!
    If i use Any configuration as local disk configuration policy and do the raid settings directly to the RAID-cards, am i able to have two raid volumes on C-series under UCSM management?
    What i would like to do with C240M3 with 6 local disks: 2 disk raid1 and 4 disk raid0
    So i would use:
    "Any Configuration—For a server configuration that carries forward the local disk configuration without any changes."
    As UCS servers Raid guide indicates:
    "Maximum of One RAID Volume and One RAID Controller in Integrated Rack-Mount Servers
    A rack-mount server that has been integrated with Cisco UCS Manager can  have a maximum of one RAID volume irrespective of how many hard drives  are present on the server. "
    Is this paragraph limitation of GUI not able to set several volumes or hard fact without "Any configuration" workaround?

    I did some testing about this issue:
    Changed Local Disk Configuration to "Any Configuration"
    Two virtual disks can be created from Raid card's WebBIOS
    These disks are visible to RedHat Installation.
    UCSM shows Any configuration for the Storage Local Disk policy
    Actual Disk Configuration has faulty information - WebBios is the only place to check the RAID status?
    Next step: I'll do the same for the production

  • Lost volumes between raidutil and diskutil

    Suddently the Xserve (Xeon early 2008, 10.5.8) show the "?" at the boot.
    I've set up an other OS X Server on an external drive.
    None of the four volumes from the internal drives mount anymore.
    I assume the server has restarted after a long power failure that outrun the UPS.
    At first I thought the raid controller has failed BUT RAIDUtil shows every disks and volumes with the green OK dot.
    DiskUtil or disk utilities don't show any of the raid5 volumes.
    What happened to the volumes between RAIDUtil and Diskutil ?
    Is there a "deep" command to make them back ?
    PLease HELP !

    LEt me show the cli :
    TestXserve:~ root# raidutil list driveinfo
    Drives Raidset Size Flags
    Bay #1 RS1 931.51GB IsMemberOfRAIDSet:RS1 IsReliable
    Bay #2 RS1 931.51GB IsMemberOfRAIDSet:RS1 IsReliable
    Bay #3 RS1 931.51GB IsMemberOfRAIDSet:RS1 IsReliable
    TestXserve:~ root# raidutil list raidsetinfo
    Total Avail
    Raidsets Type Drives Size Size Comments
    RS1 RAID 5 1,2,3 1.78TB 0.00MB No tasks running
    TestXserve:~ root# raidutil list
    Device Name Device Type Device URL
    0 AppleRAIDCard AppleRAIDCard x-raid-device://localhost/AppleACPIPlatformExpert/PCI0@0/AppleACPIPCI/RP01@1C/I OPCI2PCIBridge/SAS@0/AppleRAIDCard#AppleRAIDCard
    TestXserve:~ root# raidutil list status
    Apple raidutil version: 1.2.0
    General Status: Good
    Battery Status: Charged
    Controller #1: Hardware Version 1.00/Firmware M-2.0.3.3
    Write Cache enabled
    Volume Status Type Drives Size Comments
    R1V1 Is Viable RAID 5 1,2,3 50.00GB Condition: Good
    R1V2 Is Viable RAID 5 1,2,3 50.00GB Condition: Good
    R1V3 Is Viable RAID 5 1,2,3 1024.00GB Condition: Good
    R1V4 Is Viable RAID 5 1,2,3 701.52GB Condition: Good
    TestXserve:~ root# diskutil list
    /dev/disk0
    #: TYPE NAME SIZE IDENTIFIER
    0: GUIDpartitionscheme *465.8 Gi disk0
    1: EFI 200.0 Mi disk0s1
    2: Apple_HFS Black Leo Server 46.6 Gi disk0s2
    3: Microsoft Basic Data AXDEFI3X104 37.2 Gi disk0s3
    4: Apple_HFS Black Data 186.1 Gi disk0s4
    5: Apple_HFS Black Snow 93.1 Gi disk0s5
    6: Apple_HFS Black Xtra 102.0 Gi disk0s6
    TestXserve:~ root#
    Last command Diskutil does not show any other devices aprt from my external "Black ..." disk.

  • XServe Raid volume corruption

    Hi peoples, My RAID volume has corruption and I have had trouble making an image using Disk Utility. I finally completed what looks like a good copy using sudo ditto -V /Volumes/data/ /Volumes/1TB/
    I am about to destroy the RAID and recreate but before I do I want to ask your opinion on a strange size difference between the source and the destination. The destination has a larger more realistic size than the source when I Get Info on the folders. Is this a symptom of a dodgy volume?

    You've likely already took the plunge, but Get Info does not always tell the whole truth when selecting a set of folders. This is a cause of permissions. To get an accurate comparison, use sudo du -H /path/to/source and sudo du -h /path/to/destination. This ensures you will read every file. Also, du will report all files so if you capture the output you can diff the result of both to see if there is discrepancy.
    Hope this helps. Good luck with the volume.

  • Xraid - raid volume backup procedure question, need input...

    If I have an xraid with two sets raid volumes, 2.5 TBs each, that I use for alternating backup. Am I eventually going to loose the fiber channel card, raid volumes, or xraid by switching out the raid volumes? I will have volume A in for a few weeks to a month then take out the drives/raid volume and put in volume B for about the same amount of time. I place the drives in the same spots/ side of the xraid. Each drive is labeled and place in the same spot each time. Everything has been working perfectly for a couple years but recently an apple specialist has told me that it's not a good idea. And that in time I am likely to damage/loose my fiber channel card, raid volume or xraid? That I am confusing the raid connection by changing drives.

    Actually, this all started with our xserve failing. The hardware and procedures I put in place worked perfectly. The xraid backup etc. Retrospect did it's job also. we were able to recover everything now I'm looking to improve our downtime and put a new xserve in place. Retrospect apparently worked because it was on the xraid. The recovery from firewire drives as a backup system is low and painful and can there's also a chance that you have to rebuild the retrospect file. The apple certified folks were impressed, no issues. And I don't power it down that often, once a month average, maybe. What I do want to implement in retrospect is a working backup. Not that we will work off of it but if that was in place then we'd be up and running sooner.

  • Problems attaching RAID volume to Time Capsule USB

    I just got an Icy Dock RAID enclosure and two discs to go with it. I want to attach it to my time capsule and use it as both a network disc and as another back up disc adding extra capacity to my Time Capsule.
    I set the dip settings on the back of the enclosure (necessary or not I don't know) and plugged it directly into my laptop. I opened up Apple's disc utility and created a RAID volume. That new RAID volume mounted and I could even go into Time machine setup and see it as a choice for a backup volume. So far so good but I still want the connivence of my wireless backups.
    So I ejected the enclosure and plugged it into the Time Capsule's USB connection. It didn't show up as a backup volume or as a network drive. Going into the disc tab of the Time Capsule setup utility I do see the two drives within the enclosure but have no option to erase them or mount them. They just show up as their raw selves as if I hadn't even initialized them into the raid partition.
    Now if I dismount the enclosure and plug it back into my computer and break apart the raid volume into two separate discs and plug it back into the time capsule I see each of those appear both as a network volume and an option for backup.
    Now of course I could use it that way but I'd prefer to have some redundancy that's why I got the enclosure in the first place. Any ideas how I can get the RAID volume to mount? Or somehow get redundancy using the two discs? If it requires command line instructions I'm OK with that I just don't have any idea of where to start.
    Thanks,
    peat

    So just in case somebody else runs into this problem I wanted to post what I discovered. I had to reformat the drives I installed in the enclosure. Once I did that they were seen as separate drives by my computer and by the time capsule.
    I did what I shouldn't have done which is use software to create a RAID drive. These software created RAID drives don't mount on the time capsule as the following thread notes.
    http://discussions.apple.com/thread.jspa?messageID=9996146
    What I should have done and eventually did do is format the drives correctly, set the dip switches for RAID 1, push the reset button on the back of the RAID enclosure and create a hardware RAID device. This hardware device now looks and feels like one drive. It mounts up as a network drive on the time capsule no problem.
    Furthermore now that it's a visible network drive I can select it in time machine preferences and use it as my destination drive for time machine backups. It hasn't fully backed up yet but it certainly seems to be working so I think this would contradict the previous post. I am able to hang a drive off my time capsule and "extend" the capacity of my time capsule. I didn't copy over the sparse bundle file so time capsule's starting all over again but I suspect I could have copied it and continued with incremental backups.

  • I am using Photoshop CS5 on a new iMac with a wireless keyboard.  I used to be able to hit F11 to perform a custom sharpening action but now the F11 key is the volume control key and I have tried everything to disable or switch the volume key. I have also

    I am using Photoshop CS5 on a new iMac with a wireless keyboard.  I used to be able to hit F11 to perform a custom sharpening action but now the F11 key is the volume control key and I have tried everything to disable or switch the volume key. I have also tried assigning other function keys to initiate the action. Is there a simple solution to this? What am I missing?

    Try unmounting the volume on your iMac using Disk Utility. Then mount it again. You may need to reboot the laptop or relaunch its Finder process (using the Force Quit window) after remounting the drive on your iMac. Remember that no process may be accessing any files on the drive you plan to unmount, or the unmount will fail. Unmounting and remounting an external drive on my iMac made it become visible on my MacBook Pro after it had disappeared.

  • Can't enable ACLs on a RAID volume

    Hi all,
    I have OSX 10.4.11 running on an Xserve G5 ppc. There are 2 Xserve RAID volumes attached by fibre channel.
    I've been having issues recently with permissions: some users are creating or modifying files/folders and other users in the same group are then unable to access them. Viewing the permissions shows that group access is set to 'None'. I can correct this in the 'Sharing' section of WGM but that doesn't resolve the underlying issue.
    I want to use ACLs to control access to data on the 2 RAID volumes, one of which also contains the users' network accounts. Unfortunately the 'Enable Access Control Lists' tick box is greyed out so I cannot activate them. On the other RAID volume all three tick boxes are available.
    Why might this be?
    John.

    Found the answer. The volume was not correctly formatted. I copied the data, reformatted the volume, copied back the data and enabled ACLs.

  • Setting up a RAID 0 between the Mini's internal HD and an external

    Would it be possible to set up a RAID 0 between two hard drive, one being the internal drive of the MacMini and the other being an external firewire drive?
    Would these two drive have to be configured outside of the computer in external enclosure and then one transplanted into the mac mini, or will the operating system allow this to be set up between the two drive?

    Yes you can RAID the internal Mac mini 2.5" hard drive with a FireWire external, but a striped RAID set is always limited by the speed of the slowest drive and the size of the smallest drive.
    As such I would not expect much of a performance gain and you would have to erase your internal drive to create the striped RAID set while booting from a 3rd drive to setup the RAID0.
    Using a FW boot drive will give you increased performance. You can see details here:
    http://www.amug.org/amug-web/html/amug/reviews/articles/wiebetech/max/
    Or if you really want to speed up the Mac mini read about the AMUG Super-mini project which uses 3.5" SATA hard drives. It was tested in single and RAID0 configurations on the internal ATA/100 IDE bus of the Mac mini
    http://www.amug.org/amug-web/html/amug/reviews/articles/addonics/mini/
    Michael

  • Mounting Xserve Raid Volumes

    I'm relatively new to Xserve RAID and I hope this isn't a topic that's already been covered.
    If I unmount (or eject) a RAID volume, how do I re-mount it. Other than rebooting the system.
    The RAID volumes don't appear in /etc/fstab. Where exactly does the system store the volume which are to be mounted at boot.
    Thanks..
    -- Bob

    You might see the volumes in disk utility, and you can remount them from there.
    Otherwise, you could unplug and re-plug the cable, and they'll show up, if you have physical access.

  • Resize raid volumes?

    Hello,
    I have a raid 5 (hardware) on my pro. With two raid volumes. Now i have change of mind with the size of those volumes. I know i can resize partitions, but is there also a way that i can resize a partion and give the free space to a diverent raid volume? (so can i resize the raid volumes?)
    Thank you for the help
    Edgar

    Unless the RAID software you are using permits it, then no. While the RAID is in tact you cannot alter the volumes that make up the array. You first have to delete the array which will in turn delete the data stored on the array.
    This is one of the main reasons why RAIDs should be structured with drives, not partitions on drives.

Maybe you are looking for