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.

Similar Messages

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

OSX Lion Disk Utility won't verify/repair RAID volumes

SInce I upgraded to Lion (now at 10.7.4) I can't use the Disk utility to verify or repair the disk catalog (disk first Aid) on apple soft RAID volumes. These volumes were created in 10.6 use the Apple RAID feature of disk utility.
I have one striped and one concatenated volume - neither will work. Press the button and the progress bar flashes for a fraction of a second, then nothing. no error, no message in the window - just no repsonse. Works fine on non raid volumes in the same disk enclosure -Firmtek Seritek/5PM, with seritek 2ME4-E sata card.
Not sure I really want to recreate and recopy the drives....
Any ideas? Seaches haven't turned up this specific issue.

A quick search in these forums for permissions or *permissions problem* reveals many posts the past four months.
In a nutshell, repairing permissions w/Leopard takes anywhere from 10-40 minutes, depending on what's installed and what's contained in /Library/Receipts/bom/. The repair permissions operation has changed in Leopard. The stalled progress bar is an unresolved bug (they haven't figured out how to make it work whilst it's checking or rebuilding the a.receiptdb, in /Library/Receipts/db/. To see what's really going on, open that folder in a Finder window, select list view, launch Disk Utility, select your boot volume, and click on repair permissions. Watch the Finder window flash files that are being read and checked against the current a.receiptdb file. That's what's taking all the time and freezing the progress bar. Once that's finished, the progress bar starts moving and the permissions are being checked and repaired. Also note, that you won't get any *they were repaired* message back for any that are noted to be incorrect.

Target Disk Mode with RAID Volume and Macbook Pro

I just received a MBP which I today intended to use to pull a netrestore image off our lab server. The latter is a Mac Pro with 2 RAID 1 arrays. I started the Mac Pro in target disk mode, hooked it up to the MBP and was expecting to see the RAID volumes to show up in the finder. Unfortunately nothing happened. I then started the disk utility only to find out that the volumes are shown but are not accessible.
Doing the same thing using our backup server (running OS X 10.4.8 server) works like a charm.
Is it possible that MBPs and/or the non-server version of OS X don't support target disk volumes off RAID arrays?
I used the same MBP as a target disk mode slave today and that, too, worked.

Hello BK:
Welcome to Apple discussions.
This knowledge base article will, perhaps, give you more information:
http://docs.info.apple.com/article.html?artnum=58583
Barry

Z77A-GD65: Disks shown but not selectable on creating a RAID volume

Mainboard: Z77A-GD65
CPU: Intel Core i7 3770K
RAM: 2x Corsair DDR3-1600 XMS3 4GB
HDDs: 2x Seagate Barracuda SATA3 7200.12 6GB/s
Upgraded System with new MB etc. yesterday and removed the old HDD.
After enabling RAID in BIOS, I went to the RAID settings with Ctrl+I. The RAID setup displays both HDDs with correct description and storage size, but when I was trying to create a new RAID volume the "disc selection" option is not selectable unless "Recovery" is chosen as RAID level. On RAID level "Recovery" both disks are selectable but no RAID volume is created during the process. When RAID level 0 or 1 is chosen still the correct size of the potential volume is calculated by the RAID setup.
Additionally, I tried the same procedure with both "RAID hot-plug" enabled and disabled in BIOS.
The HDDs are plugged into SATA-ports 1+2. No OS installed yet.

After several unsuccessful attempts of formatting and partitioning the disks, I installed the OS. Subsequent use of the thereafter installed Intel Rapid Storage Technology (IRST) enabled me to created the RAID volume under Windows, which is now additionally shown on the IRST page after the POST screen.
So the RAID volume creation worked, but it still takes me wonder why I haven't been able to do this after the POST screen in the first place .
Well, problem still kind of solved.

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.

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.

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.

Apple DU vs SoftRAID's drivers for RAID volumes, performancewise?

Hi,
For some time I have been using SoftRAID's (http://www.softraid.com/) drivers (v. 4.0.7) for an OS+apps SSD and my users' accounts on a 2*2TB RAID0 (WD Caviar Blacks) volume. At present the User volume is about 50% full (2 of 4TB).
I am considering to make the users' accounts volume a 2*3TB RAID1 (Hitachis) for safety reasons. My questions to the knowledgable people in this forum are:
1) I am aware that a RAID1 will be slower than a RAID0 volume. But will an Apple DU RAID1 or a SoftRAID RAID1 volume likely be faster?
2) Using SoftRAID's drivers on disks/volumes prohibits use of some troubleshooting utilities such as iPartition, DriveGenius, etc. Hence, is it adviseable to put SoftRAID drivers also on non-RAID volumes, such as my SSD boot volume?
I am hoping somebody with experience in these things can advise.
Thanks.

Softraid always worked with TTPro and Disk Warrior, and never needed the others, and I wouldn't let iPartition touch someone else's.
Apple mirror I rate as weaker, doesn't use a stripe read, doesn't alert to I/O errors. don't they mention in features their implementation of mirror rebuilds and faster background rebuilds when needed?
Personally, a good backup sets and clones. Mirror if you use three rdives so even under a failure you still have two and it can do background rebuild. Otherwise, dont' use mirror. 3TB mirrors are huge long and slow to copy. Really think you need to worry about hardware drive failure, huh?
I've used SoftRAID from 2.2.1 days a decade ago. They support is one of if not the best I have had the pleasure to deal with and help me through as well as given me an education.

802.11n Base using USB Raid Volumes?

Hi All,
Got the new Airport base station, pulled out the old one, factory defaulted my three other Airport Express base stations, and then joined them as WDS extenders. All is good. Won't be testing throughput yet all I am still all PPC.
Bought the new base station for the USB disk sharing as I have computers all over the home and this was going to be great to facilitate sharing!
Before it arrived, I purchased a new USB eBOX-U Eight (8) drive enclosure from Firewire Depot (as reviewed by AMUG).
Very nice box for $265. Loaded six new 400GB (newegg.com @ $105/ea.) and a couple of old misc. drives. Formated top two as raid 0, next two as raid 0 and then mirrored the two together (I just went through the worst hard disk crash I've ever had with a stripped 0 volume, I never want to go through this again - 100% data loss).
Anyways, last 2 400GB drives as mirrored raid.
Fire the puppy up and for an overnight backup device, it's perfect. I couldn't use it for encoding video but for going to bed and letting my computer backup cheaply and safely, I am delighted!
So now I'm ready for the new Airport base station, I can share these massive, safe drives over the wireless network and get all of my computers backed-up.
Nope.
The base station refuses to recognize the Macintosh-formated arrays, it only sees one drive and that unusable.
Any ideas? I can't find any prohibitions to such a configuration.
JP
G5 Quad Mac OS X (10.4.8)

Why doesn't the new base station support Mac software RAID volumes? I can't believe there aren't more people up in arms over this missing functionality. A Mac product not supporting a Mac software configuration? Seems downright silly.

Xserve RAID volume maintenance

A new client has an Xserve RAID (firmware 1.5) in which the first 7 drive modules are populated, and configured into a 1.01 TB Level 5 array. This array has been in use for (estimated) 2.5 to 3 years (based on the power-on hours of the component hard drives). As far as my client knows, no maintenance has been performed on the RAID volume. Should we be using the First Aid feature of Disk Utiliity or something like Disk Warrior on this volume? The Xserve RAID is connected (via Fiber) to a Power Mac G4 (Mirrored Drive Doors) running Mac OS X Server 10.3.9. Please advise.

Are they having problems with the RAID that you think requires maintenance?
FWIW I've got several XServe RAIDs in my network, some of them the same age as this one, and I've never done anything to it in terms of maintenance or housekeeping.
If you're not having problems with it, I wouldn't worry.

Name : leopard Type : Volume Disk Identifier : disk1s2 Mount Point

Early in October, after installing SL and the first upgrade, I began experiencing colour flashes on transitions on slideshow projects created in iMovie '09. I contacted Apple Support and began working with one of the technicians. She reported that after viewing a short sample slideshow/movie that I sent her, Apple engineers concluded that something in SL was interfering with the video card. So far, no fix from Apple.
One workaround suggested by a reader on these support discussions was to install Leopard on an external drive and work with iMovie from there. My contact person helped me connect and set up the external drive. She also talked me through steps that allowed me to continue using iMovie '09, my photos in iPhoto, and the iTunes Music Library on my internal drive to build my slideshows and have all of this 'show up' on the external drive. Really, all I was doing on the external drive was using iMovie to export my project and create a *.mov file.
Until three days ago, I hadn't tried to access the external drive for about a month and I found that I couldn't. I called Apple Support again for help. In the end, the person I was working with suggested that he would get in touch with my first contact to see if written instructions could be sent to me so that I could repeat her process. At the same time, he suggested I ask for help here. When I first noticed the problem, the icon for the external drive was on my desktop; today it isn't. Below is the information that is relevant (I hope).
*+From Disc Utility: Information on External Drive+*
Name : leopard
Type : Volume
Disk Identifier : disk1s2
Mount Point : Not mounted
File System : Mac OS Extended (Journaled)
Connection Bus : USB
Device Tree : IODeviceTree:/PCI0@0/USB7@1D,7
Writable : Yes
Universal Unique Identifier : CED756E6-8A72-33BB-B79B-469908923E54
Capacity : 999.16 GB (999,157,620,736 Bytes)
Owners Enabled : No
Can Turn Owners Off : Yes
Can Be Formatted : Yes
Bootable : Yes
Supports Journaling : Yes
Journaled : No
Disk Number : 1
Partition Number : 2
*+Information from First Aid/Repair Disc+*
Invalid node structure
The volume leopard could not be verified completely.
Error: Disk Utility can’t repair this disk. Back up as many of your files as possible, reformat the disk, and restore your backed-up files.
*+Information at bottom of Disc Utility Window:+*
Mount Point : Not mounted Capacity : 999.16 GB (999,157,620,736 Bytes)
Format : Mac OS Extended (Journaled) Available : -
Owners Enabled : - Used : -
Number of Folders : - Number of Files : -
I have no idea what is wrong or what to do now. I do know that the first thing is to reformat the drive, but I don't know how to do that. The second thing will be to install all the upgrades so that both internal and external drives are exactly the same - that I can manage! The third thing is to figure out how to get back to the original set up.
If anyone can help or point me to sites that will tell me how to do any or all of this, I will be most appreciative.

{quote:}I wanted help with two things: (1) getting the external HD back up and (2) reestablishing the connections that had been made so that iMovie, iPhoto, and iTunes pointed back to those applications and libraries on the internal HD. In other words, before I lost the connection to the external HD, when I clicked on iMovie on the external HD, what opened was iMovie on the internal HD, with all of my projects available. Same with the other two.{quote}
To be honest I'm not sure why you were opening an Applications from the External HD and pointing it to the Library on the Internal HD? Seem's like it would be a lot simpler and easier just to open and run everything right from the Internal HD. Some folk's will open and run the Application from there Internal HD and then point it to the Library on the External HD, but you need to be very careful doing so because if the external HD fails then you lose your data.
{quote:}Until about 3 hours ago, I couldn't use Disk Utility to erase the external HD and start over because the icon wasn't showing in the Devices panel. I have been at this all day and finally the icon did appear and I erased the external drive. After 4 attempts to reinstall Leopard OS, that, too finally worked. I have now reinstalled iLife '09 and all of the necessary upgrades.{quote}
Not sure why you lost the connection to the External HD, could be just a bad connection or a early warning sign for a failing drive?
{quote:}I knew that if I erased the external HD I would lose all of the connections I had between the two drives. That was why I was hoping for a way to fix it without erasing. So now I need help with (2) above: reestablishing those connections. I'm afraid I don't understand partitioning - what it is or what it does. If you have time to explain it to me, I will certainly give it a try.{quote}
I think you need to run everything from your Internal HD and only use the External HD as a backup drive either with Time Machine or on the great advise of elmac using SuperDuper.
As for Partitioning and Formatting I can give you some article's to study, but would suggest not fussing or experimenting unless you had a second External HD to play around with.
Dennis

Hardware raid boot disks on m5000

Is it possible to configure a raid 1 on boot disks to this machine?
The M5000 has the LSI 1064 controller and it seems to be possible..
After booting from dvd (boot cdrom -s):
# raidctl -c -r 1 c0t0d0 c0t1d0
Creating RAID volume will destroy all data on spare space of member disks,
proceed (yes/no)? y
Operation not support with volume of this level.
The controller is in GOOD state...
# raidctl -S
0 "LSI_1064"
0.0.0 GOOD
0.1.0 GOOD
3 "LSI_1064"
# format
Searching for disks...done
AVAILABLE DISK SELECTIONS:
0. c0t0d0 <SUN146G cyl 14087 alt 2 hd 24 sec 848>
/pci@0,600000/pci@0/pci@8/pci@0/scsi@1/sd@0,0
1. c0t1d0 <SUN146G cyl 14087 alt 2 hd 24 sec 848>
/pci@0,600000/pci@0/pci@8/pci@0/scsi@1/sd@1,0
Any ideas?
Many thanks,
Mauro.

I configured mirror boot disk using Solaris Volume Manager...

Xserve RAID won't RAID in disk utility

I have a XServe RAID that won't RAID in disk utility. The XServe is fully populated and there are two arrays created. Both of those arrays show up in disk utility and will only be partitioned with an Apple Partition Map. If I try to partition them GUID, that partition fails (system formatter failed). Once, I partition them APM, two volumes show up on the desktop. Then, I try to create a software RAID with those two volumes and I can not get the volumes to RAID together. The error message in disk utility says (RAID can not be modified). I have checked the system log and it says something about a socket error or that it can not bind. Does anyone have any ideas on why I can not create this RAID?
My end goal is to have 2 hardware RAID 5's and put a striped RAID set on top of that to have one large volume for Final Cut video editing.
I'm using a Mac Pro with Atto Celerity 42ES fibre card.
Thanks

This may be a little too late, but maybe it will help. I'm not sure why this happens. I reinstalled my server, and I could not access the drives, even though they showed up in disk utility (as a blank file).
Here is what I did to fix it:
1. Open up Disk Utility
2. Make a disk image of the drive you want to mount, save this somewhere accessible (i saved it on another one of my RAID drives)
3. Erase the disk, it should then mount and be accessible
4. Restore the image onto the drive.
Cheers!

"Create" button dim when attempting to setup mirrored RAID in Disk Utility.

I'm trying to setup a mirrored RAID in Disk Utility (v10.5.6) in MacOS 10.4.11 on a PowerMac G5. I've got the System and all of my files on a 500 GB Seagate internal drive and I've added a blank 500 GB Western Digital internal drive to be the mirror. When I boot from the Seagate drive and run Disk Utility, I can follow all of the instructions for setting up a mirrored RAID (except the last instruction):
1) Launch disk utility.
2) Select my boot drive.
3) Click on the RAID tab.
4) Enter a RAID Set Name and select a Volume Format (Mac OS Extended Journaled).
5) Drag a drive or volume to the set. Okay, I actually have a problem here, because if I drag the boot volume or drive to the set, nothing happens (it doesn't appear in the selection box). So I drag the blank volume to the set and it shows up in the selection box.
6) Select RAID type (RAID Slice).
7) Click the "Create" button.
That's the step that I can't complete; the "Create" button is dimmed (grayed out, disabled). My boot drive isn't partitioned (it has just one volume), I've run Disk Utility to repair Disk Permissions before I attempted to set up the RAID, and both drives are formatted as "Mac OS Extended Journaled." The only potential cause I can think of is that the two drives I'm using, though they're both 500 GB drives, are from different manufacturers. I can't imagine that would make a difference though.
Why is the "Create" button dimmed?
Any help would be GREATLY appreciated!
Thanks,
Scott

Hi there,
Thanks for your help!
Your explanation makes sense. I've just recovered from a hard drive failure and although I'd backed up most of the files the night before, I still lost a day's worth of email and several days worth of other files. Mirroring appealed to me because then I'd always have a completely up-to-date copy of everything, but your bad experiences with it give me pause.
Is there another backup strategy you can recommend that would give me really up-to-date backups of my entire boot volume?
Thanks again!
Scott

Migrating RAID volume disks between T2000s

Similar Messages

Maybe you are looking for