Install on a Thunderbolt RAID volume

Are there any pitfall when using a Thunderbolt RAID volume as startup disk?
The setup would be a Mac mini connected to an ARC-8050 Thunderbolt RAID with RAID6 level.
I want a setup with low Recovery Time if the Mac mini has a hardware failure.
So the plan is that if the Mac mini has a failure i just replace it with the second Mac mini and boot from the RAID volume.
Is this a good idea?

Loosec;
I see that you have a handle on the dmraid package, recently upgraded I see.
I have an application for raid that does not involve booting with raid, data system only.
I desire to generate an archive for pacman using a raid array for purposes of install speed.
My first attempts used mdadm techniques and provided a software raid of hde and hdg drives which did not produce an improved hdparm read speed.
What changes to dmraid procedures will provide a non-bootable raid0 system which will archive pacman packages and provide combined raid read speed at least 50% greater than the normal 40MB/sec.?
Performance figures for raid0 with dmraid haven't been available in the forums. Perhaps these are disappointing?
Basically, how to make a raid0 system with dmraid but not make it bootable?
EDIT: Solved my problem with mdadm and mke2fs, fstab entry and /mnt/md entry.
Last edited by lilsirecho (2008-03-14 07:50:00)

Similar Messages

[SOLVED] Problems installing on Intel Matrix Raid / FAKE RAID

Using Intel Rapid Storage Technology - Option ROM - 11.0.0.1339
I've created a:
RAID0(Stripe) Strip 32KB Size 214.3GB Status Normal Bootable Yes
Volume which I want to install Arch on.
I've gone through this all the way to a successful install using Fedora (if that is of any help whatsoever)?
So, with Arch, I have read and tried:
https://wiki.archlinux.org/index.php/In … e_RAID_set
As soon as I do a UEFI or BIOS install of Arch and run lsblk I get:
sda-
md126
sdb-
md126
(and using gdisk can create ef00 200M partition and root such as: md126p1 md126p2)
Once I follow https://wiki.archlinux.org/index.php/In … e_RAID_set, and, do:
# modprobe dm_mod
# dmraid -ay
[ 39.383447] device-mapper: table: 254:1 striped: Couldn't parse stripe destination
RAID set "isw_dejgjdecda_SSD" was not activated
ERROR: device "isw_dejgjdecda_SSD" could not be found
I am hoping I may end my story here and someone will reply something along the lines of "well, that's because....", and I can continue on my determined attempt to install Arch on this RAID Volume.
However, obviously, I have not just given up at this point, so, some more info just in case it helps:
I can access /dev/md126 in gdisk and use gdisk fully
I can mount/pacstrap/genfstab/chroot/
Then - problems arise - I cannot seem to get the install to boot after having tried either UEFI or BIOS boot using Syslinux, Gummiboot & Grub - always used GPT for the Array by the way.
Any ideas? Is there a module to load? I'm still a newbie guys, so, apologies for any glaring mistakes....
Thank you all very much for any help with this.
Frazer.
Last edited by frazer (2014-07-10 11:20:04)

Replying per your email request. I have hardly zero experience with fakeraid. I ran one for a few weeks but then discovered zfs and never looked back. Sorry dude.

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.

Guide to Installing XP on a Raid Enabled (AHCI) ThinkStation S10

I spent a long time attempting to install Windows XP on my ThinkStation S10 with Raid 5 enabled. This post will detail exactly how to accomplish this process.
Method 1: Using F6 Option During XP Installation (Note: I could not personally get this method to work, therefore, I can’t confirm it.)
1) Download the appropriate Raid drivers for your operating System from lenovo’s support site (ie: “Intel Matrix Storage Manager (RAID) driver for Windows XP”)
2) Copy the files to a floppy disk (highly preferable) or USB drive. If you don’t have a floppy drive on your machine you will have to do the following:
2a) Boot into the BIOS by tapping F1. Navigate to Startup Sequence and move “Diskette Drive A” to the “Excluded from Boot Order” category. Make sure the USB devices are included in the boot order and in the right order. Also, make sure PCI SCSI: Intel VOL01 (this should correspond to your raid volume) is not excluded from the boot order.
For example, my startup sequence is the following:
1: IDE HDD
2: PCI SCSI: Intel VOL01 (this should correspond to your raid volume)
2: IDE CD
3: USB CD
4: USB FDC
5: USB Key
6: USB LS120
7: PCI BEV: P3-HL-DT-STDVD-RAM GSA-H60
3) Enter the BIOS (tap F1) and set the following.
Devices --> IDE Drives Setup --> SATA Raid Enabled: Enabled.
Devices --> IDE Drives Setup --> Native Mode Operation: Automatic
4) After the first Lenovo splash screen, there is a black screen which lists all your hard drives, hit ctrl-I to enter Intel Matrix Storage Manager. Here you can delete and create your raid volumes. Mine was setup with my computer so I left it alone. For more information on configuring your raid volume look for the following documentation on lenovo’s support site: Hardware Maintenance Manual (HMM) - ThinkStation S10.pdf --> Chapter 7. Installing and configuring RAID
Note: Record the information on the top right hand of the screen (ie: ICH 9 and the version number) This information may be needed this when installing the raid driver.
5) Reboot with the inserted XP installation disk. At the very beginning of the windows install process a message on the bottom bar will say "Press F6 if you need to install a third party SCSI or RAID driver." (Be alert to not miss this message.)
5a) Insert the USB stick and follow the instructions, it should ask you to hit “s” to specify additional device.
Note: When I tried this it did not detect my USB stick and wanted a floppy. Maybe someone can confirm how this works? Below are the exact instructions from the “Intel Matrix Storage Manager (RAID) driver for Windows XP (32-bit) - ThinkStation S10” driver readme.txt file.
[Quote]
5.3 Pre-Installation Using the F6 Method.
Note: The Steps 1 and 2 can be skipped if you use the F6 Floppy
      disk utility provided by Intel. This utility can also be
      downloaded from the following website. These methods
      are applicable to systems configured for RAID or
      AHCI mode.
    http://downloadfinder.intel.com/scripts-df/Product_Filter.asp?
    ProductID=2101
1. Extract all driver files from the installation package.
    See section 7.2 for instructions on extracting the
    files.
2. Create a floppy* containing the following files in the root
    directory:
    iaAhci.inf, iaAhci.cat,
    iaStor.inf, iaStor.cat,
    iaStor.sys, and
    TxtSetup.oem.
* Note: For Windows Vista you can use a floppy, CD/DVD or USB.
3. For Windows XP or later operating systems:
    - At the beginning of the operating system installation,
     press F6 to install a third party SCSI or RAID driver.
    - When prompted, select 'S' to Specify Additional Device.
    - Continue to step 5.
4. For Windows Vista:
    - During the operating system installation, after selecting the
     location to install Vista, click Load Driver to
install a third
     party SCSI or RAID driver.
    - Continue to step 5.
5. When prompted, insert the media (floppy, CD/DVD
or USB) you
    created in step 2 and press Enter.
6. At this point you should be presented with a selection
    for one of the following depending on your hardware
    version and configuration:
    - Intel(R) 82801IR/IO SATA RAID Controller (Desktop ICH9R)
    - Intel(R) 82801IR/IO SATA AHCI Controller (Desktop ICH9R)
    - Intel(R) 82801HEM SATA RAID Controller (Mobile ICH8M-E)
    - Intel(R) 82801HEM SATA AHCI Controller (Mobile ICH8M-E)
    - Intel(R) 82801HBM SATA AHCI Controller (Mobile ICH8M)
    - Intel(R) 82801HR/HH/HO SATA RAID Controller (Desktop ICH8R)
    - Intel(R) 82801HR/HH/HO SATA AHCI Controller (Desktop ICH8R)
    - Intel(R) 631xESB/632xESB SATA RAID Controller (Workstation ESB2)
    - Intel(R) 82801GHM SATA RAID Controller (Mobile ICH7RM)
    - Intel(R) 82801GBM SATA AHCI Controller (Mobile ICH7M)
    - Intel(R) 82801GR/GH SATA RAID Controller (Desktop ICH7R/DH)
    - Intel(R) 82801GR/GH SATA AHCI Controller (Desktop ICH7R/DH)
7. Highlight the selection that is appropriate for the
    hardware in your system and press Enter.
8. Press Enter again to continue. Leave the floppy disk in
    the system until the next reboot as the software will
    need to be copied from the floppy disk again when setup
    is copying files.
[/Quote]
6) Install XP as normal and everything should work properly.
Note: If there are any corrections or additions feel free to PM me or reply to the thread and I will update this post.
Message Edited by kalensk on 08-11-2008 02:57 AM

Method 2: Using nLite to Integrate the Drivers into the XP Install Disk
1) nLite can’t use .exe drivers, rather it needs the un-archive drivers containing the .inf (setup information) file. Therefore, right click on the .exe and select “Extract To…” or “Extract Here” (Note: You will need 7-Zip or WinRar to do this).
1a) When un-archiveing the “Intel Matrix Storage Manager (RAID) driver for Windows XP” you will reach a file with an .IMA extension (ie: F32.IMA). This is an image file so you will need mounting software like Alcohol 52% (Free Edition), UltraISO, Daemon Tools, etc. to extract the .inf file.
1b) Simply install and run any of the above mounting software and open the .IMA file and copy the contents to a folder.
2) Download nLite and follow the guide.
2a) Insert the Windows XP CD and right click “explorer” and copy the files over to a new folder called XP_Source. Then Start nLite and point to the directory where you have XP_Source.
2b) During the “Task Selection” screen select “Integrate Drivers” and “Create a Bootable ISO”
2c) On the “Integrate Drivers” screen click the “insert” tab and search the for the .inf file in the folder where the raid driver is located.
2d) Follow the rest of the nLite setup to your liking until you have the opportunity to make an ISO on the “Create a Bootable ISO” screen. Select the “Make ISO” button and save the file on your computer. Next, burn the ISO to a CD using burning software such as InfraRecorder, CDBurnerXP, Nero, etc.
3) Without loading the CD, boot your system and tap F1 to enter the BIOS. Enable RAID and the following settings:
Devices --> IDE Drives Setup --> SATA Raid Enabled: Enabled.
Devices --> IDE Drives Setup --> Native Mode Operation: Automatic
4) While in the BIOS navigate to Startup Sequence and make sure PCI SCSI: Intel VOL01 (this should correspond to your raid volume) is not excluded from the boot order.
For example, my startup sequence is the following:
1: IDE HDD
2: PCI SCSI: Intel VOL01 (this should correspond to your raid volume)
2: IDE CD
3: USB CD
4: USB FDC
5: USB Key
6: USB LS120
7: PCI BEV: P3-HL-DT-STDVD-RAM GSA-H60
5) Select F10 to save and exit.
6) After the first Lenovo splash screen, there is a black screen which lists all your hard drives, hit ctrl-I to enter Intel Matrix Storage Manager. Here you can delete and create your raid volumes. Mine was setup with my computer so I left it alone. For more information on configuring your raid volume look for the following documentation on lenovo’s support site: Hardware Maintenance Manual (HMM) - ThinkStation S10.pdf --> Chapter 7. Installing and configuring RAID
7) Reboot the machine with the customized Windows XP CD with the integrated drivers and Install XP as normal.
Note: If there are any corrections or additions feel free to PM me or reply to the thread and I will update this post.
Message Edited by kalensk on 08-11-2008 02:58 AM

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.

Installing OSX on new Raid setup

HI Everyone,
i have four internal 250 Gb hard drives, i switched the startup dick to an external so I could set up the raid.
I set up a stripped raid consisting of two mirrored raids per the Apple database. it seems to work in as much as my four disks that showed up on my desktop previously show up as one with a capacity of 465 Gb.
so in theory, it looks like i have successfully made the RAID. Disk utility says it is online.
so, my question is, i tried to install OSX on the RAID and it says that it can not install OSX on this disk?
is there a trick I am missing?
I TRULY appreciate your help and comments

Are these drives all set up using the GUID partition map? Did you erase the drives before setting up the RAID? Are you trying install OS X using the OS X Installer Disc One that came with the computer? Have you tried cloning the system from your external drive?
How to Clone Using Restore Option of Disk Utility
1. Open Disk Utility from the Utilities folder.
2. Select the backup or destination volume from the left side list.
3. Click on the Erase tab in the DU main window. Set the format type to Mac OS Extended (journaled, if available) and click on the Erase button. This step can be skipped if the destination has already been freshly erased.
4. Click on the Restore tab in the DU main window.
5. Select the backup or destination volume from the left side list and drag it to the Destination entry field.
6. Select the startup or source volume from the left side list and drag it to the Source entry field.
7. Double-check you got it right, then click on the Restore button.
8. Select the destination drive on the Desktop and press COMMAND-I to open the Get Info window. At the bottom in the Ownership and Permissions section be sure the box labeled "Ignore Permissions on this Volume" is unchecked. Verify the settings for Ownership and Permissions as follows: Owner=system with read/write; Group=admin with read/write; Other with read-only. If they are not correct then reset them.
For added precaution you can boot into safe mode before doing the clone.

WinXP PRO install issue with SATA RAID floppy on P45D3

Hello,
My objective is to set up 2 RAID volumes (one in RAID0 + one in RAID1) using Intel RAID Matrix Manager.
After having enabled RAID mode on BIOS, created the 2 RAID volumes and pressed F6 at the beginning of WinXP PRO installation without any problem, I am stuck when one file from Intel SATA RAID driver floppy needs to be written on the disk.
The problem appears after having confirmed the partition I want to install WinXP on. I got the following message:
"Cannot write iaStor.sys" . And I have to cancel the installation.
I do not know where this file has to be written ... Additionally, this file was perfectly read (and written somewhere) just after having pressed "S" and provided the floppy during the first phase of WinXP installation.
Any suggestion to help me ?
Thanks
My config (partial):
- P45 D3 Platinum with E8500 Dual Core
- 2G DDR3
- 2x 500G SATA2 HDD

Quote from: didierpilon
How did you solved this ?
I Googled and found this page which was very useful (the blue text is a link; you can click on it).
In fact I already knew how to do it using nLite (which I normally use), but now I tried their F6 floppy advice for educational purposes and that worked as well!
Key is that the files have to be present twice, on different locations on the floppy...

Our XServe-RAID volume does not mount anymore...

Our XServe-RAID volume does not mount anymore.
On /var/log/system.log I could find the following.
Feb 22 09:52:29 ogre kernel: jnl: open: journal magic is bad (0xf433f != 0x4a4e4c78)
Feb 22 09:52:29 ogre kernel: hfs: early jnl init: failed to open/create the journal (retval 0).
It appears the the journaling is badly screwed.
I tryed to disable the journaling with no success.
Here is what I get.
ogre:/var/log root# diskutil disablejournal disk2s3
The selected journaling request does not appear to be valid
After some googling I foud this :
--- QUOTE ---
The more serious problem occurs when the contents of the journal file are corrupted in such a way that the operating system does not proceed to mount the volume. Fortunately, this problem is extremely rare (I have seen three reports of corrupted journal files at the MacFixIt Forums and Apple Discussion Forums since journaling was introduced).
Starting the journaling process is one of the first things that happens when a volume is recognized by the operating system. There appears to be no way to intervene in single-user mode before the journal file is examined. A message about �bad journal magic� appears. Unfortunately, every tool that can turn off journaling requires that the volume already be mounted.
If the Macintosh can boot under Mac OS 9, dealing with a corrupted journal file involves restarting under Mac OS 9 and using a utility (such as our free TechTool Lite 3.0.4) to make visible these two invisible files at the root level of the volume:
/.journal
/.journalinfoblock
Once these files are made visible, they can be deleted. Mac OS 9 does not support journaling, and recognizes nothing special about these files. Neither of these files can be seen in Terminal or in single-user mode in Mac OS X, because they are considered part of the disk directory.
If the Macintosh cannot boot under Mac OS 9, but the drive has Mac OS 9 drivers installed, the drive can be put into a Macintosh that can boot under Mac OS 9, or an ATA/IDE drive can be put into a suitable FireWire enclosure.
The possibility that you may need to remove these two journaling files under Mac OS 9 is a good reason for making sure that all volumes you use have Mac OS 9 drivers installed. The drivers must be installed when the drive is formatted.
--- [END] QUOTE ---
Well, my disk is part of a RAID 5 matrix.... so the solution proposed does not work.
Does any one of you has any idea ?
XServe Mac OS X (10.3.9)

I've seen an article about volumes not mounting and was wondering if this relates to your problem;
http://discussions.apple.com/thread.jspa?messageID=1239224&#1239224
The thread doesn't refer to journalling but may be of use?
HTH

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.

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.

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.

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

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.

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.

Install on a Thunderbolt RAID volume

Similar Messages

Maybe you are looking for