Software RAID issue

I have just installed 2-200 GB seagate hd's into my machine and set them up as a software raid 0. Also installed is the original 80 GB drive and a Hitachi 160 GB drive. The two new drives functioned long enough for me to copy all of my raw digital home video.
Now, when I try to boot the grey Apple screen comes up and the machine hangs. When I disconnect the drives, it boots right up.
I thought maybe my power supply was giving up the ghost until I reconnected them and successfully rebooted with Drive Genius 1.2. I rebuilt the raid set (maintaining all data) and rebooted into OSX successfully. Woohoo!
But not so fast. Next reboot started the same thing. And now Drive Genius has no effect.
I really dont wan't to lose the data on these drives. Is there a problem with the software raid in 10.4.7? Any ideas of other things to try? Help?!?!
Thanks,
Andy
G4 1.25DP FW800   Mac OS X (10.4.7)  
G4 1.25DP FW800   Mac OS X (10.4.7)  

Possibly a couple things that "aren't quite right" with your setup.
SoftRAID 3.5 supports mirror for boot drive, but not with stripped.
The two IDE buses are not identical, making for some slight problems with RAID on the two.
You really can't RAID if both drives are together in one drive cage on the same IDE bus.
You need a PCI controller to RAID in MDD. Most people at this point in time opt for Serial ATA drives and controller. If you want a bootable SATA drive...
http://www.firmtek.com/seritek
If you must boot from stripped RAID (not always a good idea and may not offer much actually in real world performance, check www.barefeats.com for some tests for one).
A dedicated boot drive for OS/Apps and use other drives for media, data, scratch, even for /users.
Two ATA drives on the same bus, have to share the bus, contend for I/O.
You can create a stripe raid with Disk Utility and boot.
I assume that you read the SoftRAID QuickStart and Manual which really are helpful. There are a number of sites etc that can go into more about RAID.

Similar Messages

  • Software RAID Failure - my experience and solution

    I just wanted to share this information with the iCloud community.
    I searched a bit and did not find much information that was useful with regard to my software RAID issue.
    I have 27 inch Mid 2011 iMac with SSD and Hard drive which has been great.
    I added an external hard drive (I think if I mention any brand name the moderator will delete this post) which includes an nice aluminum case with two 3 TB hard drives within it, and it has a big blue light on the front and is connected via Thunderbolt. This unit is about 2 years old and I have it configured in a 3 TB mirrored RAID (RAID 1) via a software RAID configured via Mac OS Disk Utility. 
    I had at one point a minor glitch which was fixed using another piece of software (again if I mention a brand the moderator will delete this post) which is like a 'Harddrive Fighter' or similar type name LOL.   So otherwise that RAID has served me well as a site for my Time Machine back up and Aperture Vault, etc.  (I created a 1.5 TB Sparse bundle for Time Machine so that the backup would not use the entire 3 TBs)
    I recently purchased a second aluminum block of drives, and set that up as a 4 TB RAID 1.
    Each of the two RAIDs are set with the option of “Automatically rebuild RAID mirror sets” checked.
    I put only about 400 gb on the new RAID to let it sit for a ‘burning in period.’
    A few days ago the monitoring software from the vendor who sells the aluminum block of drives told me I had a problem.  One of the drives had “Failed.”   The monitoring software strangely enough does not distinguish the drives so you can figure out which pair had the issue, so I assumed it was the New 8 TB model.  Long story short, it was the older 6 TB model, but that does not matter for this discussion.
    I contacted the vender and this is part of their response.
    “This is an indication that the Disk Utility application in Mac had a momentary problem communicating with the drive mechanism. As a result, it marked that drive as "failed" in the header information. Unfortunately, once this designation is applied to a drive by the OS, the Disk Utility will thereafter refuse to attempt any further operations with that disk until the incorrect "failed" marker is manually cleared off the drive.”
    That did not sound very good to me…..back up killed by a SOFTWARE GLITCH?
    “The solution is to remove the corrupted volume header, and allow the generation of a new one….This command will need to be done for each disk in the array… (using Terminal)…
    diskutil zerodisk (identifier)
    …3. After everything is finished, you should be able to exit Terminal, and go back into the Disk Utility Application to re-configure the RAID array on the device.”
    Furthermore they said.
    “If the Disk Utility has placed a flag into the RAID array header (which exists on both drives) then performing this procedure on a single drive will not correct anything.”
    And…
    “When a drive actually does fail, it typically stops appearing in the Disk Utility application altogether. In that circumstance, it will never be marked "failed" by the Disk Utility, so the header erase operation is not needed.”
    This all sounded like a bad idea to me. And what does the Vendors RAID monitor software say then?  “Disk Really Really FAILED, check for a fire.”
    As I tried to figure out which drive was actually the bad RAID pair I stumbled on a solution.
    First I noted that the OS Disk Utility did NOT show a fault in the RAID. It listed both RAIDS as “Online.’ Thus no rebuilding was needed and it did not begin the rebuild process.
    The Vendors disk monitor software saw some fault, but Mac was still able to read and write to the RAID, both disks in the mirror.  I wrote a folder to the RAID and with various rebooting steps I pulled the “Bad” drive and looked at the “Good” Drive….the folder was there…I put the Bad drive back in and pulled the Good Drive and the folder was there on the “bad” drive.  So it wrote to both drives.  AND THE VENDORS MONITORING SOFTWARE SHOWED THE PREVIOUSLY LABELED ‘BAD’ DRIVE AS ‘GOOD’ AND THE MISSING DRIVE SLOT AS ‘BAD’.
    My stumbled FIX.   I moved a bunch of files off the failed RAID to the new RAID  but before I moved the sparse bundle, a folder of 500 gigs movies and some other really big folders the DISK UTILITY WINDOW (which I still had open) now showed that the RAID had a Defect and began rebuilding the mirror set itself, out of the blue!   I don't know why this happened.  But moving about 1/2 of the data off of it perhaps did something?  Any Ideas?
    This process took a few hours as best I can tell (let it run overnight) and the next day the RAID was fine and the Vendors RAID monitor did not show a fault any longer.
    So, the Vendors RAID monitoring software reporting a “FAILED” drive without any specific error codes to look up.  Perhaps they could have more info for the user on the specific fault?  The support line of the the Vendor said with certainty “the Volume Header is corrupted” and THE ONLY FIX is to completely ZERO THE DRIVE! This was not necessary as it turns out.
    And the stick in the eye to me…..
    “I've also sometimes seen the drives get marked as "failed" by the disk utility due to a shaky connection. In some cases, swapping the ends of the Thunderbolt cable will help with this. Something to try, perhaps, if your problems come back. “
    Ya Right…..
    Mike

    Follow up.
    After going through the Zeroing process and rebuilding the RAID set three times, with various configurations, LaCie finally agreed to repair the unit under warrantee.
    I tried swapping the power supplies and thunderbolt wires, tried taking the drive out of series with the newer big brother of it.  And it still failed after a few days.
    I just wanted to share more of what I learned with regard to rebuilding the RAID sets via the Terminal.  The commands can be typed partially and a help paragraph will come up to give VERY cryptic descriptions of the proper use of the commands.
    First Under terminal you can used the command "diskutil appleRAID list" to list those drives which are in the RAID.  This gives you the ID number for each physical drive. For example:
    AppleRAID sets (1 found)
    ===============================================================================
    Name:                 LaCie RAID 3TB
    Unique ID:            84A93ADF-A7CA-4E5A-B8AE-8B4A8A6960CA
    Type:                 Mirror
    Status:               Online
    Size:                 3.0 TB (3000248991744 Bytes)
    Rebuild:              manual
    Device Node:          disk4
    #  DevNode   UUID                                  Status     Size
    0  disk3s2   D53F6A81-89F1-4FB3-86A9-8808006683C2  Online     3000248991744
    -  disk2s2   E58CA8F5-1D2C-423A-B4BE-FBAA80F85879  Spare      3000248991744
    ===============================================================================
    In my situation with the failed RAID, I had an extra disk in this with the status of Missing/Failed. 
    The command is "diskutil appleRAID remove" and the cryptic help paragraph says:
    Usage:  diskutil appleRAID remove MemberDeviceName|MemberUUID
            RAIDSetVolumePath|RAIDSetDeviceName|RAIDSetUUID
    MemberDeviceName|MemberUUID  is the number listed in the "diskutil appleRAID List" command,  and
    RAIDSetVolumePath|RAIDSetDeviceName|RAIDSetUUID is the Device Node for the RAID which here is /dev/disk4.
    I used this command to remove the third entry (missing/failed), I did not copy the terminal window text on that one, so I cannot show the list of three disks.
    I could not get to remove the disk2s2 disk listed as SPARE, as it gave an error message:
    Michaels-iMac:~ mike_aronis$ diskutil appleraid remove E58CA8F5-1D2C-423A-B4BE-FBAA80F85879 /dev/disk4
    Started RAID operation on disk4 LaCie RAID 3TB
    Removing disk from RAID
    Changing the disk type
    Can't resize the file system on the disk "disk2s2"
    Error: -69827: The partition cannot be resized
    But I was able to remove it using the graphical interface Disk Utility program using the delete key.
    I then rebuilt the RAID set by dragging the second drive back into the RAID set.
    I could not get the command: "diskutil appleRAID update AutoRebuild 1 /dev/disk4" to work, because even though it was trying to execute it HUNG.  I put the two drives into my newer LaCie 2big as my attempt at further trouble shooting the RAID (this was not suggested by LaCie tech), rebuild the RAID and now I am going to leave it setup that way for a few days before I ship it back to just see if the old drives work fine in the new RAID box (thus proving the RAID box is the problem). I tried the AutoRebuild 1 command just now and it gave an error.
    Michaels-iMac:~ mike_aronis$ diskutil appleraid update autorebuild 1 /dev/disk4
    Error updating RAID: Couldn't modify RAID (-69848)
    Michaels-iMac:~ mike_aronis$
    In my haste to rebuild the RAID set for the third or forth time as LaCie led me through the testing this and test that phase, I forgot to click the "Auto Rebuild" option in the Disk Utility program.
    Question for the more experienced:
    As I was working on this issue, I notice that each time I rebooted and did work in the Terminal (with and without the RAID plugged in to the thunderbolt connection) I notice that the list of drives would change and my main boot drive would not stay listed as drive 0!  Some times it would be drive 0, sometimes the RAID would be listed as Drive 0.  It's strange to me...I would have thought the designation for Drive0 and Drive1 would always be my two build in drives (SSD and spinning drive).
    Mike

  • I have some questions regarding setting up a software RAID 0 on a Mac Pro

    I have some questions regarding setting up a software RAID 0 on a Mac pro (early 2009).
    These questions might seem stupid to many of you, but, as my last, in fact my one and only, computer before the Mac Pro was a IICX/4/80 running System 7.5, I am a complete novice regarding this particular matter.
    A few days ago I installed a WD3000HLFS VelociRaptor 300GB in bay 1, and moved the original 640GB HD to bay 2. I now have 2 bootable internal drives, and currently I am using the VR300 as my startup disk. Instead of cloning from the original drive, I have reinstalled the Mac OS, and all my applications & software onto the VR300. Everything is backed up onto a WD SE II 2TB external drive, using Time Machine. The original 640GB has an eDrive partition, which was created some time ago using TechTool Pro 5.
    The system will be used primarily for photo editing, digital imaging, and to produce colour prints up to A2 size. Some of the image files, from scanned imports of film negatives & transparencies, will be 40MB or larger. Next year I hope to buy a high resolution full frame digital SLR, which will also generate large files.
    Currently I am using Apple's bundled iPhoto, Aperture 2, Photoshop Elements 8, Silverfast Ai, ColorMunki Photo, EZcolor and other applications/software. I will also be using Photoshop CS5, when it becomes available, and I will probably change over to Lightroom 3, which is currently in Beta, because I have had problems with Aperture, which, until recent upgrades (HD, RAM & graphics card) to my system, would not even load images for print. All I had was a blank preview page, and a constant, frozen "loading" message - the symbol underneath remained static, instead of revolving!
    It is now possible to print images from within Aperture 2, but I am not happy with the colour fidelity, whereas it is possible to produce excellent, natural colour prints using its "minnow" sibling, iPhoto!
    My intention is to buy another 3 VR300s to form a 4 drive Raid 0 array for optimum performance, and to store the original 640GB drive as an emergency bootable back-up. I would have ordered the additional VR300s already, but for the fact that there appears to have been a run on them, and currently they are out of stock at all, but the more expensive, UK resellers.
    I should be most grateful to receive advice regarding the following questions:
    QUESTION 1:
    I have had a look at the RAID setting up facility in Disk Utility and it states: "To create a RAID set, drag disks or partitions into the list below".
    If I install another 3 VR300s, can I drag all 4 of them into the "list below" box, without any risk of losing everything I have already installed on the existing VR300?
    Or would I have to reinstall the OS, applications and software again?
    I mention this, because one of the applications, Personal accountz, has a label on its CD wallet stating that the Licence Key can only be used once, and I have already used it when I installed it on the existing VR300.
    QUESTION 2:
    I understand that the failure of just one drive will result in all the data in a Raid 0 array being lost.
    Does this mean that I would not be able to boot up from the 4 drive array in that scenario?
    Even so, it would be worth the risk to gain the optimum performance provide by Raid 0 over the other RAID setup options, and, in addition to the SE II, I will probably back up all my image files onto a portable drive as an additional precaution.
    QUESTION 3:
    Is it possible to create an eDrive partition, using TechTool Pro 5, on the VR300 in bay !?
    Or would this not be of any use anyway, in the event of a single drive failure?
    QUESTION 4:
    Would there be a significant increase in performance using a 4 x VR300 drive RAID 0 array, compared to only 2 or 3 drives?
    QUESTION 5:
    If I used a 3 x VR300 RAID 0 array, and installed either a cloned VR300 or the original 640GB HD in bay 4, and I left the Startup Disk in System Preferences unlocked, would the system boot up automatically from the 4th. drive in the event of a single drive failure in the 3 drive RAID 0 array which had been selected for startup?
    Apologies if these seem stupid questions, but I am trying to determine the best option without foregoing optimum performance.

    Well said.
    Steps to set up RAID
    Setting up a RAID array in Mac OS X is part of the installation process. This procedure assumes that you have already installed Mac OS 10.1 and the hard drive subsystem (two hard drives and a PCI controller card, for example) that RAID will be implemented on. Follow these steps:
    1. Open Disk Utility (/Applications/Utilities).
    2. When the disks appear in the pane on the left, select the disks you wish to be in the array and drag them to the disk panel.
    3. Choose Stripe or Mirror from the RAID Scheme pop-up menu.
    4. Name the RAID set.
    5. Choose a volume format. The size of the array will be automatically determined based on what you selected.
    6. Click Create.
    Recovering from a hard drive failure on a mirrored array
    1. Open Disk Utility in (/Applications/Utilities).
    2. Click the RAID tab. If an issue has occurred, a dialog box will appear that describes it.
    3. If an issue with the disk is indicated, click Rebuild.
    4. If Rebuild does not work, shut down the computer and replace the damaged hard disk.
    5. Repeat steps 1 and 2.
    6. Drag the icon of the new disk on top of that of the removed disk.
    7. Click Rebuild.
    http://support.apple.com/kb/HT2559
    Drive A + B = VOLUME ONE
    Drive C + D = VOLUME TWO
    What you put on those volumes is of course up to you and easy to do.
    A system really only needs to be backed up "as needed" like before you add or update or install anything.
    /Users can be backed up hourly, daily, weekly schedule
    Media files as needed.
    Things that hurt performance:
    Page outs
    Spotlight - disable this for boot drive and 'scratch'
    SCRATCH: Temporary space; erased between projects and steps.
    http://en.wikipedia.org/wiki/StandardRAIDlevels
    (normally I'd link to Wikipedia but I can't load right now)
    Disk drives are the slowest component, so tackling that has always made sense. Easy way to make a difference. More RAM only if it will be of value and used. Same with more/faster processors, or graphic card.
    To help understand and configure your 2009 Nehalem Mac Pro:
    http://arstechnica.com/apple/reviews/2009/04/266ghz-8-core-mac-pro-review.ars/1
    http://macperformanceguide.com/
    http://www.macgurus.com/guides/storageaccelguide.php
    http://www.macintouch.com/readerreports/harddrives/index.html
    http://macperformanceguide.com/OptimizingPhotoshop-Configuration.html
    http://kb2.adobe.com/cps/404/kb404440.html

  • Apple software RAID 0 not spinning down while not in use

    I have a G-Tech G-RAID w/ Thunderbolt, 8TB external enclosure.  It has two 4TB fujitsu drives in it, set up as RAID 0 with Apple's Disk Utility v13 (426) that ships with 10.8 Mountain Lion.  This is attached to a very cleanly installed Mid 2011 Mac Mini, which is acting as a media server.  There is basically no 3rd party software on it, because it's acting as a NFS filer server for streaming digital players around the house.
    However, I have the G-RAID set to spin down when possible in energy saver, and it's not.  It never spins down.  I have 4 external drives on this media server, ranging from USB to FW800 to the Thunderbolt drive, all from different manufacturers, and different sizes and models.  All the other drives spin down after 10 minutes.
    Not only is the checkbox "Put hard disks to sleep when possible" checked in Energy Saver, but a
    pmset -g
    reveals that the "disksleep" is set to 10 (min).
    In frustration, I have tried a lot of things including (but not limited to) removing all other hard drives and hardware, starting up with shift held (safe boot) and removing any software at all that I thought would be keeping the drive "alive."
    Finally I decided to start monitoring the drive with fs_usage, to see if I could suss out what is keeping this one drive alive.
    "fs_usage | grep DISKNAME" reveals that SystemUIServer is accessing the drive every minute, about seven times in a clump.  Considering that SystemUIServer is the peice of software that controls the little menu add-ons to the right of the menubar, I have spend a great deal of time trying to figure out what would use SystemUIServer that is accessing this drive.
    Now it's true that this drive is set up as a time machine drive, but I have disabled time machine, and spotlight, and still I get the same SystemUIServer accesses every minute.  Here is a fs_usage dump:
    orion:~ seanb$ sudo fs_usage | grep Betelgeuse
    Password:
    15:53:16  getattrlist       /Volumes/Betelgeuse     0.000029   SystemUIServ
    15:53:16  getattrlist       /Volumes/Betelgeuse     0.000011   SystemUIServ
    15:53:16  getattrlist       /Volumes/Betelgeuse     0.000017   SystemUIServ
    15:53:16  getattrlist       /Volumes/Betelgeuse     0.000010   SystemUIServ
    15:53:16  getattrlist       /Volumes/Betelgeuse     0.000008   SystemUIServ
    15:53:16  getattrlist       /Volumes/Betelgeuse     0.000010   SystemUIServ
    15:53:16  statfs64          /Volumes/Betelgeuse     0.000017   SystemUIServ
    15:54:16  getattrlist       /Volumes/Betelgeuse     0.000025   SystemUIServ
    15:54:16  getattrlist       /Volumes/Betelgeuse     0.000007   SystemUIServ
    15:54:16  getattrlist       /Volumes/Betelgeuse     0.000011   SystemUIServ
    15:54:16  getattrlist       /Volumes/Betelgeuse     0.000011   SystemUIServ
    15:54:16  getattrlist       /Volumes/Betelgeuse     0.000009   SystemUIServ
    15:54:16  getattrlist       /Volumes/Betelgeuse     0.000010   SystemUIServ
    15:54:17  statfs64          /Volumes/Betelgeuse     0.000014   SystemUIServ
    15:55:17  getattrlist       /Volumes/Betelgeuse     0.000062   SystemUIServ
    15:55:17  getattrlist       /Volumes/Betelgeuse     0.000013   SystemUIServ
    15:55:17  getattrlist       /Volumes/Betelgeuse     0.000024   SystemUIServ
    15:55:17  getattrlist       /Volumes/Betelgeuse     0.000010   SystemUIServ
    15:55:17  getattrlist       /Volumes/Betelgeuse     0.000009   SystemUIServ
    15:55:17  getattrlist       /Volumes/Betelgeuse     0.000010   SystemUIServ
    15:55:17  statfs64          /Volumes/Betelgeuse     0.000014   SystemUIServ
    As you can see, it's the same seven drive accesses every minute.  This is NOT occuring with any of my other drives.  Now, here comes my wild conjecture.  Is this something the system does because they are RAID slices?  Do OS X software RAID slices check themselves every minute? This seems to be preventing them from sleeping.
    Any help would be appreciated, I'm going nuts here.
    Sean

    The second column in your fs_usage report says that iStat Menus is what is accessing your disk (Istat64).  Disable iStat Menus and I bet your issue will go away.  I know there is a module in iStat Menus to monitor drive space, but if I recall correctly, even if that module is disabled, iStat has a habit of checking drives anyhow.  I remember hearing people getting rid of istat menus in order to allow their HDs to sleep propely.
    In fact, and easy way to test this would be to reboot your Mac with the shift key held down until you see your desktop load up.  This will prevent 3rd party add-ons from loading like iStat Menus. Let me know if that works.
    Unfortunatrly this is not the problem I am having, as I've booted with shift, and I still see the  "getattrlist" accesses in my fs_usage report.
    EDIT: stupid font made your report look like iStat when it was Lstat.  So what I said about iStat Menus is probably incorrect.  But using the shift key to boot could still lead you to the correct anwer.  I'm doing testing on my end as well. Let you know if I see anything that pertains to your issue.  (I got an Lstat entry in my fs_usage when I open the drive during testing, but I have not beeing getting them an regular intervals like you do.  I would still guess that you have 3rd party software that is checking on drives periodically, and that holding shift might suss that out.)
    Message was edited by: Cheule

  • Migrating Software RAID 1 ?!

    Hello all, i just installed my new SSD on which i'm doing a fresh install of my OS, although have now run into an issue with regaining the software raid 1 i had setup on 2 external drives with the old OS. Can i possibly migrate this raid 1 to the fresh OS??the drives are not coming up at all at the moment but if i boot the old OS disk they appear as normal.
    any help would be great
    thanks

    Did a bit more research, SCSI and storage use to be my hobby, and Mac Pro my passion. So I tried to dig into this further. SSD is very popular and people want to have 2 x SSDs along with 3-4 traditional mechanical hard drives. I just don't see going with an external type solution.
    Short answer: ain't gonna boot.
    You want a mirror - that should be fine.
    I was not familiar at all with one item, but I advise people to not put USB/FW cases on SATA controllers, too many problems and issues.
    *Raidon 4bay 19in 1ru esata enclusure*
    Like this?
    http://eshop.macsales.com/item/Raidon/SR4WBS2/
    Is the controller one of the very few that are bootable? most are not.
    To be bootable, the card would have to have Mac EFI firmware. Also, the EFI ROM version can "interfere" with support for cards and being bootable.
    There are always drivers and firmware when it comes to booting. It is suppose to be "driver-less." translation: built into OS X 10.5.x and later.
    NewerTech use Marvell chipset. I can say their 6G chipset which you can google and see who else uses them. I just picked up Marvell based 6G 2-port. So interested in why MINE is having trouble (conflicts with Sonnet Silicon Image most likely). I have a couple Sonnet cards, E4P and E2P, and there are drivers.
    the Caldigit Fasta-2E is not bootable with the Mac Pro. In addition, while most FirmTek controllers are bootable with the PowerMac G4 and G5, they are not bootable with the Apple Mac Pro. Bootable External drives Mac Pro?
    *NewerTech MAXPower eSATA 6G*
    +Does NOT support booting on any Macintosh platform.+
    http://eshop.macsales.com/item/Newer%20Technology/MXPCIE6GS2/
    Or this one,
    *eSATA 6G PCIe 2.0 RAID Capable Controller Card*
    http://eshop.macsales.com/item/Newer%20Technology/MXPCIE6GRS/
    http://www.newertech.com/products/pcieraidesata.php
    Reviewed here (and this should be req'd site to check also for Mac Pro owners)
    http://macperformanceguide.com/Reviews-MAXPowereSATA6G.html
    http://www.xlr8yourmac.com/IDE/NewerTech6GeSATA/Newertech6GeSataCard.html
    There is also FirmTek.
    http://firmtek.com/seritek/seritek-2me4-e/perform/
    http://eshop.macsales.com/item/Firmtek/SATAE6G/
    Highpoint has always depended on driver.
    Popular kit to install two SSDs in optical drive bay:
    http://eshop.macsales.com/item/Other%20World%20Computing/MM352A52MP9/
    External dual drive (SATA only, which is what I use and want for native SATA speeds)
    http://eshop.macsales.com/item/Other%20World%20Computing/MESATATBEK/?APC=XLR8You rMac09
    The ideal would be to boot off the two SSDs, and yes it would help to have a PCIe with internal ports, then use them in stripe RAID, not mirror (you can backup the OS and have a clone on external FW800; on sparse disk image of 100GB; on a small internal drive even), and when it changes.
    http://www.xlr8yourmac.com/IDE/SSDin_Mac_Pro/SSD_install_inMacPro.htm#storytop
    For an internal controller, HPT RR640 IF it was supported at all on Mac
    http://www.newegg.com/Product/Product.aspx?Item=N82E16816115077
    http://www.tweaktown.com/reviews/3309/highpointrocketraid_640_sata_6gb_s_4_port_pci_e_2_0controller/index.html
    http://www.bit-tech.net/hardware/2011/01/04/high-point-rocketraid-640-review/5
    To boot in 64-bit mode, all drivers and even some application plug-ins I believe have to be 64-bit, but not everything is 64-bit mode compatible.
    one SSD in optical drive bay for system
    no need to mirror
    no controller
    use the 2nd for scratch or an expensive off line backup
    If the SSD fails, swap out, use clone, rebuild and restore.
    No meed for mirror, AND disks writes are where SSDs can suffer and slow down.
    But DO consider SoftRAID 4.x, great support for SSDs and driver even for non-RAID, but their mirror RAID is a notch above.
    http://www.softraid.com
    I found Highpoint RR Quad on Apple Store:
    Is this compatible with the new 2010 Mac Pros? bootable?
    http://store.apple.com/us/product/H1113LL/A#compatibility
    I think you would get more mac pro owners to read and help in Mac Pro forum. And don't forget to stop by and check XLR8YOURMAC web site for news and tips about hardware upgrades and reports.

  • Software raid 1 drive(s) failed

    Curious on what to do with a RAID 1 Drive (s) failure? I've searched the community and cannot find similar issue/answers.
    Configuration:
    One 1TB OS & App Drive is fine
    Two 3TB RAID 1 Drives for Video scratch are fine
    Two 2TB RAID 1 Data Drives are my issue
         I'm using the software raid in OSX and it shows "2TB Data Drive/Mirrored Offline"
         Both drives have "Failed" next to them
    I have backup this Data Drive in Time Machine and a recent full back up to a single drive that is off site.  I believe I have a good back up strategy with Time Machine and offsite back ups via Voyager S3.  I guess we'll find out!
    My question is how do I find out if it's a HW issue or SW issue with this configuration ?  And then how to go about recovering them?
    Initially when I looked in Disk Utility it appeared that only one of the 2TB drives had "Failed" next to it but now after a reboot "Failed" is next to both drives.
    My initial hope was that one of the drives had failed and I'd be able to just replace that drive and the RAID System would rebuild from the other drive.
    Any assistance would be appreciated.
    Thanks

    TommyH wrote:
    My initial hope was that one of the drives had failed and I'd be able to just replace that drive and the RAID System would rebuild from the other drive.
    RAID 1 just copies the same data to two (or more) drives at the same time, it's only for mission critical data loss requirements where a drive failure during writing would be catastrophic. Like taking purchasing orders or getting a phone call from ET for example.
    RAID 0 is dangerous as the data path is separated to how many drives in the RAID 0 set, one drive glitches and all data is lost. But provides insane speeds.
    RAID 5 is a much more reliable, it combines many drives (4 or more for more speed) splitting the data path but also has redundancy factor that if a drive dies it can be replaced and the data is recovered from the other drives. Usually a RAID 5 is in a external enclosure with it's own cooling and hardware controllers, not software based RAID where your CPU is being overloaded.
    There are other forms of RAID some combinations like RAID 1+0, RAID 6, 10 and so forth, you can find out more about the more eclectic RAID types online.
    RAID 5 is more ideally suited to video requirements for data storage, with perhaps a RAID 0 as a scratch disk or a RAID 0 + 1 (the RAID 0 is mirrored to another RAID 0) if your going to take a while working on it that increases the potential of failure.
    Once the work is completed, it's sent to the RAID 5 where it's safe with it's redundancy and speed.
    http://eshop.macsales.com/shop/hard-drives/RAID/Desktop
    The thing to remmeber with the failed RAID 1 Data drive is the data is still on the drive, even though it failed and perhaps things are messed up a little on it on the directory. All the drive needs is to be told it's not part of a RAID 1 anymore, that it's a normal drive, a simple fix, but I don't know how to go about it.
    You have two drives and two chances to recover the data off off, simply disconnect one data drive and reboot, see if it will mount and or you can repair the drive in Disk Utility.
    If not pull one drive out and stick another blank one in there and download Data Rescue and simply recover the files to the new blank drive. DR works by simply reading the files themselve, not the file struture or anything else.
    Software RAID is unreliable, it depends upon the CPU. Opt to get a external RAID where it's based in hardware instead. Use eSATA if all possible.
    Also consider using backup software, like Carbon Copy Cloner which can be scheduled to make a backup of your data during the middle of the night. This way if something happens to either your boot drive or a data drive, the clone won't immediately copy the issue to the other drive like a RAID 1 does.
    Also Carbon Copy Cloner makes "hold option" bootable OS X boot drive clones, which TimeMachine doesn't.
    Also TM kicks in what, like once a hour? It's likely what caused your issue, CCC will work when you schedule it.  TM is for consumers, not video pro's like yourself.
    If you need even heavier iron as a external RAID setup and more expertise, then see these guys
    http://www.macgurus.com/

  • Failed Software Raid 1, trying to virtualize but getting I/O error failure

    I will try to summarize all what has happened and where I'm at now currently:
    Server is 2008 R2 (DC, exchange, IIS, SQL, etc) setup originally setup with software RAID 1.   At some point years ago the software RAID had failed and the second disk wasn't part of the mirror anymore and it was never fixed in disk management.
    Last week the server and wouldn't boot as the primary drive failed.  I selected secondary plex during startup just to see if that disk was still functioning, which to my suprise it did boot up but data was years old. 
    At that point, I inserted Windows 2008 R2 DVD and started System Recovery from previous backup onto secondary plex drive.  Once complete, the server was backup and running.  Changed the system startup variable to secondary plex so it would
    boot that drive if restarted.
    I am now trying to virtualize the server using disk2vhd in order to move it onto new hardware, however each time I try it fails with I/O error. I have re-tried multiple times stopping all major services to minimize I/O during disk2vhd, but still errors out
    about 3/4 way through.  I have run checkdisk and it repaired a few bad sectors on the secondary plex drive, yet still fails during disk2vhd.  I am currently running a defrag on the disk as it reported 36% defragmention and will try offline disk2vhd
    once complete using System Center VMM 2012 (not R2 as that's been removed - found that out the hard way!). 
    I'm worried this disk has underlying errors which is why it failed years ago and Windows broke the mirror and why it won't work with online disk2vhd.
    I have attached a picture of Disk Management which I find interesting as it shows Disk 0 as unknown (Not Initialized), Disk 1 having errors (can "Reactivate Disk" though unsure if that does anything destructive?), and then a missing disk at the
    bottom which I can also reactivate. I'm not sure if restoring the last working backup from disk 0 somehow messed up Disk 1 or confused it?  BIOS reports Disk 0 as 0MB so I'm thinking that drive is no good anymore. 
    I guess what I'm looking for with this post is any answer or suggestion as to why disk2vhd might be failing, whether an offline disk2vhd maybe a better successful option, and what (if anything) I should do in Disk Management with these drives in their current
    state. I don't have a replacement 500GB drive for the mirror and I don't plan on getting one as I already have a new Hyper-V 2012 Core server setup to replace this failing server.  I just can't seem to get it to virtualize using online disk2vhd and wondering
    if it has something to do with the current drive setup/situation?

    Hi,
    à
    I am now trying to virtualize the server using disk2vhd in order to move it onto new hardware, however each time I try it fails with I/O error.
    Would you please let me know the complete error message that you can get?
    Please refer to following article and check if can help you.
    Troubleshooting Disk Management
    à
    I guess what I'm looking for with this post is any answer or suggestion as to why disk2vhd might be failing, whether an offline disk2vhd maybe a better successful option
    In addition, this issue seems to be more related to Disk2vhd. I suggest that you should post the question in
    the Disk2vhd forum. I believe we will get a better assistance there.
    If anything I misunderstand or any update, please don’t hesitate to let me know.
    Hope this helps.
    Best regards,
    Justin Gu

  • Downside of a Software RAID ???

    Been researching RAIDs for my G5. External would work best for my workflow. I want it to ensure protection against drive failure at and to/fro jobsites.
    I've read about RAIDs on the discussions here and elsewhere.
    I feel like a Software RAID 1 would be adequate for my usage and this OWC product looks good. http://eshop.macsales.com/item/Other%20World%20Computing/MEFW912AL2/
    Is there a problem with SoftRAID versus hardware?
    I read that they take up processor speed.. is this significant on a G5 ??
    I like the size of the OWC enclosure versus the tray style hardware RAIDs like the Wiebetech. http://wiebetech.com/products/RAIDTech800.php
    Dual2 G5 & Powerbook G4   Mac OS X (10.4.4)  

    The first problem I see is going with a Firewire based RAID system, particularly on a G5. There are some speed issues with FW on a G5. Go to barefeats.com and do a search for G5 and firewire. Adding another drive to FW (even 800) saturates the bus so there is no real speed gain. You should be looking at SATA software RAIDs along with backups. I set mine up for speed so I run 4 drives with a RAID 0 setting. I am very fastidious about backing up. Whenever I add any new images I back them up. Whenever I work on a job, I back up afterwards. I am never more than a couple of hours without backing up. It only takes a few seconds to backup as I use SynchronizerPro and backup onto another RAID array which only comes on when I need to backup. When finally done with jobs they get backed up onto separate single hard drives. I do not use any other RAID than 0 because of my backup strategy. My feeling is I do not want to rely on a RAID 5 or whatever because they'll save me in case of a crash, but what would happen if I erased or overwrote something and then need it back. With my strategy I can go to my backup drives and reload them back onto my main drives.

  • Disk Utility Software RAID

    Hi everyone,
    I know how to create a Software RAID in Disk Utility. Let's say I do that with 2 identical FireWire drives. What happens or is the best practice when one drive fails? Will shutting down everything and then exchanging the bad drive with a new one issue an automatic rebuild like Hardware RAIDs can? Or will I have to rebuild it manually somehow? What if the RAID is the boot volume, will that make any difference in the procedure?
    Does anybody have experience with this and would like to share it?
    Thank you!
    Björn

    Hi, I am a bit confused. I just set up a mirrored RAID array with to Firewire 800 drives using two 500GB drives. Under the options button in the RAID setup was a box that you could check to automatically rebuild the array. Will this not do the job if one of the drives fails?
    Also, I have set Time Machine to use this as its backup drive. It is much faster to update than using the Time Capsule drive and cuts down on the local network traffic a lot. An added benefit seems to be that the files are written just like files on any other drive and are also accessible using the Finder.
    One last question. Do you know of any cons to this arrangement? I know using a RAID array for this is probably not really necessary, but I had the drives so I figured why not try it. Anyway, thanks in advance for your time.

  • Z77A G45 Raid issues?

    Good evening all,
    after I've made plenty of tests, i think i have a problem with the RAID controller. Tried with a single disk, or with a pair of HDD in software raid and all works like a charm. As soon as i configure a controller driven mirror i experience frequent blue screen with spontaneous reboot. At reboot the volume starts to rebuild.
    I run actually the latest BIOS, my CPU is a i5 3570k, no overclock, 1x SSD (samsung 840 pro) as boot disk and 2 hdd WD green 1,5 tb.
    Do someone else experience the same issue or have a tip?
    thks in advance,

    http://support.microsoft.com/kb/975453
    To resolve this issue, remove the RAID disk and then enable the RAID driver in the registry before you attach the RAID disk. To do this, follow these steps.
    Note Assume that Iastorv.sys is the driver that has to be enabled.
    Exit all Windows-based programs.
    Click Start, type regedit in the Start Search box, and then press ENTER.
     If you are prompted for an administrator password or for confirmation, type the password or provide confirmation.
    Locate and then click the following registry subkey:
    HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Iastorv
    In the details pane, right-click Start, and then click Modify.
    In the Value data box, type 0, and then click OK.
    On the File menu, click Exit to close Registry Editor.
    Install the RAID driver by using the installation media, or download and install the latest driver from the manufacturer's Web site.
    Shut down your computer and install the Raid disk in the computer.
    Restart your computer

  • Hello, I am getting a Kern Protection failure error message when trying to start up my Olympus DSS Player dictation software.  I have been using the software without issue for years until last month. I have uninstalled and reinstalled the software.

    Hello, I am getting a Kern Protection failure error message when trying to start up my Olympus DSS Player dictation software.  I have been using the software without issue for years until last month. I have uninstalled and reinstalled the software and don't recall installing any new software before the issue began.
    Any help would be greatly appreciated, I will post the error message below. Thanks.
    Process:    
    DSS Player [186]
    Path:       
    /Applications/DSS Player/DSS Player.app/Contents/MacOS/DSS Player
    Identifier: 
    com.olympus.DSSPlayerV7
    Version:    
    7.4.0 (0.1)
    Code Type:  
    X86 (Native)
    Parent Process:  launchd [98]
    Date/Time:  
    2013-11-23 11:44:03.999 +1100
    OS Version: 
    Mac OS X 10.6.8 (10K549)
    Report Version:  6
    Interval Since Last Report:     
    209192 sec
    Crashes Since Last Report:      
    4
    Per-App Interval Since Last Report:  273602 sec
    Per-App Crashes Since Last Report:   4
    Anonymous UUID:                 
    EDE95D54-CA0A-4ABC-8241-167C27AAFC1D
    Exception Type:  EXC_BAD_ACCESS (SIGBUS)
    Exception Codes: KERN_PROTECTION_FAILURE at 0x0000000007ff4005
    Crashed Thread:  0  Dispatch queue: com.apple.main-thread
    Thread 0 Crashed:  Dispatch queue: com.apple.main-thread
    0   com.OlympusSys.OlympusDSSFile
    0x005e1fa3 DSSFile_GetDSSIndexMark + 1091
    1   com.olympus.DSSPlayerV7  
    0x0004e5cf -[DSSFileManager setActive] + 61
    2   com.olympus.DSSPlayerV7  
    0x0004a939 -[DSSFileManager setFileInfo:needMusicInfo:] + 698
    3   com.olympus.DSSPlayerV7  
    0x000486f8 -[DSSFileManager initWithFilePath:needMusicInfo:] + 124
    4   com.olympus.DSSPlayerV7  
    0x00009470 -[DSSMainWindowController createFileInfosNew:folderId:] + 742
    5   com.olympus.DSSPlayerV7  
    0x0000ccd6 -[DSSMainWindowController updateFolderInfos:folderIds:] + 622
    6   com.olympus.DSSPlayerV7  
    0x00020bdb -[DSSMainWindowController awakeFromNib] + 3665
    7   com.apple.AppKit         
    0x0114e21c -[NSIBObjectData nibInstantiateWithOwner:topLevelObjects:] + 1646
    8   com.apple.AppKit         
    0x0114c1a4 loadNib + 257
    9   com.apple.AppKit         
    0x0114b7f7 +[NSBundle(NSNibLoading) _loadNibFile:nameTable:withZone:ownerBundle:] + 831
    10  com.apple.AppKit         
    0x0114b4ad +[NSBundle(NSNibLoading) loadNibFile:externalNameTable:withZone:] + 158
    11  com.apple.AppKit         
    0x011dafcb -[NSWindowController loadWindow] + 223
    12  com.apple.AppKit         
    0x01171f22 -[NSWindowController window] + 89
    13  com.apple.AppKit         
    0x013d6dbc -[NSWindowController showWindow:] + 36
    14  com.olympus.DSSPlayerV7  
    0x000035b4 -[DSSAppController applicationDidFinishLaunchingAfterShowSplashWindow] + 464
    15  com.olympus.DSSPlayerV7  
    0x000065d0 -[DSSAppController completeCheckRemoteConnWhenAppLaunch] + 86
    16  com.apple.Foundation     
    0x021b0738 __NSThreadPerformPerform + 705
    17  com.apple.CoreFoundation 
    0x032bc42b __CFRunLoopDoSources0 + 1563
    18  com.apple.CoreFoundation 
    0x032b9eef __CFRunLoopRun + 1071
    19  com.apple.CoreFoundation 
    0x032b93c4 CFRunLoopRunSpecific + 452
    20  com.apple.CoreFoundation 
    0x032b91f1 CFRunLoopRunInMode + 97
    21  com.apple.HIToolbox      
    0x02537e04 RunCurrentEventLoopInMode + 392
    22  com.apple.HIToolbox      
    0x02537af5 ReceiveNextEventCommon + 158
    23  com.apple.HIToolbox      
    0x02537a3e BlockUntilNextEventMatchingListInMode + 81
    24  com.apple.AppKit         
    0x0118e595 _DPSNextEvent + 847
    25  com.apple.AppKit         
    0x0118ddd6 -[NSApplication nextEventMatchingMask:untilDate:inMode:dequeue:] + 156
    26  com.apple.AppKit         
    0x011501f3 -[NSApplication run] + 821
    27  com.apple.AppKit         
    0x01148289 NSApplicationMain + 574
    28  com.olympus.DSSPlayerV7  
    0x0000257a _start + 216
    29  com.olympus.DSSPlayerV7  
    0x000024a1 start + 41
    Thread 1:  Dispatch queue: com.apple.libdispatch-manager
    0   libSystem.B.dylib        
    0x00f44382 kevent + 10
    1   libSystem.B.dylib        
    0x00f44a9c _dispatch_mgr_invoke + 215
    2   libSystem.B.dylib        
    0x00f43f59 _dispatch_queue_invoke + 163
    3   libSystem.B.dylib        
    0x00f43cfe _dispatch_worker_thread2 + 240
    4   libSystem.B.dylib        
    0x00f43781 _pthread_wqthread + 390
    5   libSystem.B.dylib        
    0x00f435c6 start_wqthread + 30
    Thread 2:
    0   libSystem.B.dylib        
    0x00f43412 __workq_kernreturn + 10
    1   libSystem.B.dylib        
    0x00f439a8 _pthread_wqthread + 941
    2   libSystem.B.dylib        
    0x00f435c6 start_wqthread + 30
    Thread 3:
    0   libSystem.B.dylib        
    0x00f43412 __workq_kernreturn + 10
    1   libSystem.B.dylib        
    0x00f439a8 _pthread_wqthread + 941
    2   libSystem.B.dylib        
    0x00f435c6 start_wqthread + 30
    Thread 0 crashed with X86 Thread State (32-bit):
      eax: 0x070a5400  ebx: 0x070a5c00  ecx: 0x001b4955  edx: 0x00000024
      edi: 0x07ff400e  esi: 0x00000000  ebp: 0xbfffdbc8  esp: 0xbfffdb60
       ss: 0x0000001f  efl: 0x00010217  eip: 0x005e1fa3   cs: 0x00000017
       ds: 0x0000001f   es: 0x0000001f   fs: 0x00000000   gs: 0x00000037
      cr2: 0x07ff4005
    Binary Images:
    0x1000 -   0x118fec +com.olympus.DSSPlayerV7 7.4.0 (0.1) /Applications/DSS Player/DSS Player.app/Contents/MacOS/DSS Player
      0x187000 -   0x187ff7  com.apple.Cocoa 6.6 (???) <5A785062-1ABB-2A54-BAAC-8FEF95275E05> /System/Library/Frameworks/Cocoa.framework/Versions/A/Cocoa
      0x18a000 -   0x484fef  com.apple.QuickTime 7.6.6 (1800) <D3538A45-5F4B-262A-06AB-64C1EBAC4A33> /System/Library/Frameworks/QuickTime.framework/Versions/A/QuickTime
      0x530000 -   0x5aafff  com.apple.audio.CoreAudio 3.2.6 (3.2.6) <156A532C-0B60-55B0-EE27-D02B82AA6217> /System/Library/Frameworks/CoreAudio.framework/Versions/A/CoreAudio
      0x5dc000 -   0x5e5fff +com.OlympusSys.OlympusDSSFile 1.3 (1.01) /Library/Frameworks/OlympusDSSFile.framework/Versions/A/OlympusDSSFile
      0x5ec000 -   0x5ecff7  com.apple.Carbon 150 (152) <2539A94A-34D9-45CB-8F3E-AD53149E0BD5> /System/Library/Frameworks/Carbon.framework/Versions/A/Carbon
      0x5ef000 -   0x5efff7  com.apple.CoreServices 44 (44) <51CFA89A-33DB-90ED-26A8-67D461718A4A> /System/Library/Frameworks/CoreServices.framework/Versions/A/CoreServices
      0x5f7000 -   0x85dff7  com.apple.security 6.1.2 (55002) <E88E133F-5FB3-446F-B753-2B8AD577B46A> /System/Library/Frameworks/Security.framework/Versions/A/Security
      0x93a000 -   0xa77fe7  com.apple.audio.toolbox.AudioToolbox 1.6.7 (1.6.7) <423BDE4D-5082-B6CA-BB2C-E22A037235A4> /System/Library/Frameworks/AudioToolbox.framework/Versions/A/AudioToolbox
      0xae7000 -   0xae8ff7  com.apple.audio.units.AudioUnit 1.6.7 (1.6.7) <93EC71F1-4D4E-F456-8EFE-32E7EFD7A064> /System/Library/Frameworks/AudioUnit.framework/Versions/A/AudioUnit
      0xaed000 -   0xb39fff +com.yourcompany.yourcocoaframework ??? (1.44) /Library/Frameworks/OlympusDeviceManager.framework/Versions/A/OlympusDeviceMana ger
      0xbe1000 -   0xc3eff7  com.apple.framework.IOKit 2.0 (???) <3DABAB9C-4949-F441-B077-0498F8E47A35> /System/Library/Frameworks/IOKit.framework/Versions/A/IOKit
      0xc5e000 -   0xda1fef  com.apple.QTKit 7.7 (1800) <9DD27495-3020-0928-B3F2-D418C336E163> /System/Library/Frameworks/QTKit.framework/Versions/A/QTKit
      0xe58000 -   0xec2fe7  libstdc++.6.dylib 7.9.0 (compatibility 7.0.0) <411D87F4-B7E1-44EB-F201-F8B4F9227213> /usr/lib/libstdc++.6.dylib
      0xf1d000 -  0x10c4ff7  libSystem.B.dylib 125.2.11 (compatibility 1.0.0) <2DCD13E3-1BD1-6F25-119A-3863A3848B90> /usr/lib/libSystem.B.dylib
    0x1146000 -  0x1a29ff7  com.apple.AppKit 6.6.8 (1038.36) <A353465E-CFC9-CB75-949D-786F6F7732F6> /System/Library/Frameworks/AppKit.framework/Versions/C/AppKit
    0x1ec5000 -  0x1ff3fe7  com.apple.CoreData 102.1 (251) <87FE6861-F2D6-773D-ED45-345272E56463> /System/Library/Frameworks/CoreData.framework/Versions/A/CoreData
    0x2057000 -  0x2057ff7  com.apple.ApplicationServices 38 (38) <EAF1BC8C-4FD4-4300-B8F7-4B24E49125E2> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Application Services
    0x205f000 -  0x2139fff  com.apple.DesktopServices 1.5.11 (1.5.11) <800F2040-9211-81A7-B438-7712BF51DEE3> /System/Library/PrivateFrameworks/DesktopServicesPriv.framework/Versions/A/Desk topServicesPriv
    0x2184000 -  0x23f5fef  com.apple.Foundation 6.6.8 (751.63) <69B3441C-B196-F2AD-07F8-D8DD24E4CD8C> /System/Library/Frameworks/Foundation.framework/Versions/C/Foundation
    0x2503000 -  0x2827fef  com.apple.HIToolbox 1.6.5 (???) <21164164-41CE-61DE-C567-32E89755CB34> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/HIToolbox.fra mework/Versions/A/HIToolbox
    0x2967000 -  0x2cd2ff7  com.apple.QuartzCore 1.6.3 (227.37) <E323A5CC-499E-CA9E-9BC3-537231449CAA> /System/Library/Frameworks/QuartzCore.framework/Versions/A/QuartzCore
    0x2da2000 -  0x2dacffb  com.apple.speech.recognition.framework 3.11.1 (3.11.1) <7486003F-8FDB-BD6C-CB34-DE45315BD82C> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/SpeechRecogni tion.framework/Versions/A/SpeechRecognition
    0x2db5000 -  0x2dfbff7  libauto.dylib ??? (???) <29422A70-87CF-10E2-CE59-FEE1234CFAAE> /usr/lib/libauto.dylib
    0x2e08000 -  0x2f8afe7  libicucore.A.dylib 40.0.0 (compatibility 1.0.0) <60FF302E-5FAE-749B-BC70-0496DC2FBF2D> /usr/lib/libicucore.A.dylib
    0x2fec000 -  0x30ecfe7  libxml2.2.dylib 10.3.0 (compatibility 10.0.0) <BE7FCD73-03B5-25A4-FCA4-D4980F1488D6> /usr/lib/libxml2.2.dylib
    0x3110000 -  0x311efe7  libz.1.dylib 1.2.3 (compatibility 1.0.0) <33C1B260-ED05-945D-FC33-EF56EC791E2E> /usr/lib/libz.1.dylib
    0x3123000 -  0x3167ff3  com.apple.coreui 2 (114) <2234855E-3BED-717F-0BFA-D1A289ECDBDA> /System/Library/PrivateFrameworks/CoreUI.framework/Versions/A/CoreUI
    0x3186000 -  0x318fff7  com.apple.DiskArbitration 2.3 (2.3) <6AA6DDF6-AFC3-BBDB-751A-64AE3580A49E> /System/Library/Frameworks/DiskArbitration.framework/Versions/A/DiskArbitration
    0x3199000 -  0x3199ff7  liblangid.dylib ??? (???) <FCC37057-CDD7-2AF1-21AF-52A06C4048FF> /usr/lib/liblangid.dylib
    0x319d000 -  0x31afff7  com.apple.MultitouchSupport.framework 207.11 (207.11) <6FF4F2D6-B8CD-AE13-56CB-17437EE5B741> /System/Library/PrivateFrameworks/MultitouchSupport.framework/Versions/A/Multit ouchSupport
    0x31bc000 -  0x3269fe7  libobjc.A.dylib 227.0.0 (compatibility 1.0.0) <9F8413A6-736D-37D9-8EB3-7986D4699957> /usr/lib/libobjc.A.dylib
    0x327d000 -  0x33f8fe7  com.apple.CoreFoundation 6.6.6 (550.44) <F88C95CD-1264-782D-A1F5-204739847E93> /System/Library/Frameworks/CoreFoundation.framework/Versions/A/CoreFoundation
    0x34f0000 -  0x3cdf557  com.apple.CoreGraphics 1.545.0 (???) <1D9DC7A5-228B-42CB-7018-66F42C3A9BB3> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ CoreGraphics.framework/Versions/A/CoreGraphics
    0x3da7000 -  0x3f6afeb  com.apple.ImageIO.framework 3.0.6 (3.0.6) <AE641FAD-DF38-AE31-B45B-85AEE7AF3A45> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ ImageIO.framework/Versions/A/ImageIO
    0x3fc9000 -  0x402afe7  com.apple.CoreText 151.13 (???) <23F359DA-D845-5C50-4DF3-19E858CF2B2C> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ CoreText.framework/Versions/A/CoreText
    0x4062000 -  0x40fdfe7  com.apple.ApplicationServices.ATS 275.19 (???) <2E83B3E9-AF39-36FC-5D05-CC1E952098AB> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ ATS.framework/Versions/A/ATS
    0x4124000 -  0x41e0fff  com.apple.ColorSync 4.6.8 (4.6.8) <920DD017-8B41-7334-E554-A85DB99EBD5A> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ ColorSync.framework/Versions/A/ColorSync
    0x4217000 -  0x426aff7  com.apple.HIServices 1.8.3 (???) <1D3C4587-6318-C339-BD0F-1988F246BE2E> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ HIServices.framework/Versions/A/HIServices
    0x4295000 -  0x42a6ff7  com.apple.LangAnalysis 1.6.6 (1.6.6) <3036AD83-4F1D-1028-54EE-54165E562650> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ LangAnalysis.framework/Versions/A/LangAnalysis
    0x42b3000 -  0x435bffb  com.apple.QD 3.36 (???) <FA2785A4-BB69-DCB4-3BA3-7C89A82CAB41> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ QD.framework/Versions/A/QD
    0x4388000 -  0x439cffb  com.apple.speech.synthesis.framework 3.10.35 (3.10.35) <9F5CE4F7-D05C-8C14-4B76-E43D07A8A680> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ SpeechSynthesis.framework/Versions/A/SpeechSynthesis
    0x43aa000 -  0x43befe7  libbsm.0.dylib ??? (???) <B328FA0A-899C-4FC4-F2AC-2FDC08819CD2> /usr/lib/libbsm.0.dylib
    0x43c7000 -  0x43cafe7  libmathCommon.A.dylib 315.0.0 (compatibility 1.0.0) <1622A54F-1A98-2CBE-B6A4-2122981A500E> /usr/lib/system/libmathCommon.A.dylib
    0x43cd000 -  0x43d9ff7  libkxld.dylib ??? (???) <9A441C48-2D18-E716-5F38-CBEAE6A0BB3E> /usr/lib/system/libkxld.dylib
    0x43dd000 -  0x46fdff3  com.apple.CoreServices.CarbonCore 861.39 (861.39) <5C59805C-AF39-9010-B8B5-D673C9C38538> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/CarbonC ore.framework/Versions/A/CarbonCore
    0x4773000 -  0x481ffe7  com.apple.CFNetwork 454.12.4 (454.12.4) <DEDCD006-389F-967F-3405-EDF541F406D7> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/CFNetwo rk.framework/Versions/A/CFNetwork
    0x4884000 -  0x48c8fe7  com.apple.Metadata 10.6.3 (507.15) <74F05E64-2A68-BA10-CCD4-128D164E5A0F> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/Metadat a.framework/Versions/A/Metadata
    0x48ef000 -  0x49bafef  com.apple.CoreServices.OSServices 359.2 (359.2) <7C16D9C8-6F41-5754-17F7-2659D9DD9579> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/OSServi ces.framework/Versions/A/OSServices
    0x4a19000 -  0x4a99feb  com.apple.SearchKit 1.3.0 (1.3.0) <7AE32A31-2B8E-E271-C03A-7A0F7BAFC85C> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/SearchK it.framework/Versions/A/SearchKit
    0x4acd000 -  0x4b00ff7  com.apple.AE 496.5 (496.5) <BF9673D5-2419-7120-26A3-83D264C75222> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/AE.fram ework/Versions/A/AE
    0x4b18000 -  0x4bb5fe3  com.apple.LaunchServices 362.3 (362.3) <15B47388-16C8-97DA-EEBB-1709E136169E> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/LaunchS ervices.framework/Versions/A/LaunchServices
    0x4bf4000 -  0x4c1affb  com.apple.DictionaryServices 1.1.2 (1.1.2) <43E1D565-6E01-3681-F2E5-72AE4C3A097A> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/Diction aryServices.framework/Versions/A/DictionaryServices
    0x4c30000 -  0x4c3dff7  com.apple.NetFS 3.2.2 (3.2.2) <DDC9C397-C35F-8D7A-BB24-3D1B42FA5FAB> /System/Library/Frameworks/NetFS.framework/Versions/A/NetFS
    0x4c46000 -  0x4cfffe7  libsqlite3.dylib 9.6.0 (compatibility 9.0.0) <52438E77-55D1-C231-1936-76F1369518E4> /usr/lib/libsqlite3.dylib
    0x4d0d000 -  0x4d4aff7  com.apple.SystemConfiguration 1.10.8 (1.10.2) <50E4D49B-4F61-446F-1C21-1B2BA814713D> /System/Library/Frameworks/SystemConfiguration.framework/Versions/A/SystemConfi guration
    0x4d67000 -  0x4d8fff7  libxslt.1.dylib 3.24.0 (compatibility 3.0.0) <E761F29A-328B-29D9-3DF0-023F2C21E500> /usr/lib/libxslt.1.dylib
    0x4d9a000 -  0x4d9aff7  com.apple.Accelerate 1.6 (Accelerate 1.6) <3891A689-4F38-FACD-38B2-4BF937DE30CF> /System/Library/Frameworks/Accelerate.framework/Versions/A/Accelerate
    0x4d9d000 -  0x4dedfe7  libTIFF.dylib ??? (???) <AB182CEC-188A-F2BC-21E1-0059FD3B2598> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ ImageIO.framework/Versions/A/Resources/libTIFF.dylib
    0x4df9000 -  0x4dfdff7  libGIF.dylib ??? (???) <2251F789-B187-0837-6E38-A0E5C7C4FA3C> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ ImageIO.framework/Versions/A/Resources/libGIF.dylib
    0x4e02000 -  0x4e20fe7  libPng.dylib ??? (???) <6C0B95D7-9634-E044-0B79-F1DD56961C33> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ ImageIO.framework/Versions/A/Resources/libPng.dylib
    0x4e29000 -  0x4e2bff7  libRadiance.dylib ??? (???) <090420B3-CB65-9F7B-5349-D42F2F9693B6> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ ImageIO.framework/Versions/A/Resources/libRadiance.dylib
    0x4e2f000 -  0x4e53ff7  libJPEG.dylib ??? (???) <50E17B4D-63D6-24D3-702F-6A6E912A55EA> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ ImageIO.framework/Versions/A/Resources/libJPEG.dylib
    0x4e5a000 -  0x4f3afe7  com.apple.vImage 4.1 (4.1) <D029C515-08E1-93A6-3705-DD062A3A672C> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vImage.fr amework/Versions/A/vImage
    0x4f48000 -  0x4f48ff7  com.apple.Accelerate.vecLib 3.6 (vecLib 3.6) <ABF97DA4-3BDF-6FFD-6239-B023CA1F7974> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.fr amework/Versions/A/vecLib
    0x4f4b000 -  0x4f8dff7  libvDSP.dylib 268.0.1 (compatibility 1.0.0) <8A4721DE-25C4-C8AA-EA90-9DA7812E3EBA> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.fr amework/Versions/A/libvDSP.dylib
    0x4f96000 -  0x5005ff7  libvMisc.dylib 268.0.1 (compatibility 1.0.0) <595A5539-9F54-63E6-7AAC-C04E1574B050> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.fr amework/Versions/A/libvMisc.dylib
    0x500e000 -  0x5424ff7  libBLAS.dylib 219.0.0 (compatibility 1.0.0) <9D89FCB3-24C9-8FCF-DB49-27B184AC3222> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.fr amework/Versions/A/libBLAS.dylib
    0x5466000 -  0x589bff7  libLAPACK.dylib 219.0.0 (compatibility 1.0.0) <4D2F47EF-BD32-1E3C-6A0A-438896ADE2BE> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.fr amework/Versions/A/libLAPACK.dylib
    0x5a21000 -  0x5b23fe7  libcrypto.0.9.8.dylib 0.9.8 (compatibility 0.9.8) <EB34F049-D9E1-BF19-CF03-B26A0352D40C> /usr/lib/libcrypto.0.9.8.dylib
    0x5b77000 -  0x5b78ff7  com.apple.TrustEvaluationAgent 1.1 (1) <2D970A9B-77E8-EDC0-BEC6-7580D78B2843> /System/Library/PrivateFrameworks/TrustEvaluationAgent.framework/Versions/A/Tru stEvaluationAgent
    0x5b7c000 -  0x5c34feb  libFontParser.dylib ??? (???) <D2D0C922-5ED1-3AE9-6F99-707C74DF3E62> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ ATS.framework/Versions/A/Resources/libFontParser.dylib
    0x5cc4000 -  0x5cfeff7  libcups.2.dylib 2.8.0 (compatibility 2.0.0) <A6C207E3-7B42-926D-9C93-BE3F50B92496> /usr/lib/libcups.2.dylib
    0x5d0b000 -  0x5d2bfe7  libresolv.9.dylib 41.1.0 (compatibility 1.0.0) <8C2B5FA8-2469-21C7-D297-F95A0FFE5F19> /usr/lib/libresolv.9.dylib
    0x5d35000 -  0x5d35ff7  com.apple.vecLib 3.6 (vecLib 3.6) <FF4DC8B6-0AB0-DEE8-ADA8-7B57645A1F36> /System/Library/Frameworks/vecLib.framework/Versions/A/vecLib
    0x5d38000 -  0x5d42fe7  com.apple.audio.SoundManager 3.9.3 (3.9.3) <DE0E0EF6-8190-3F65-6BDD-5AC9D8A025D6> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/CarbonSound.f ramework/Versions/A/CarbonSound
    0x5d4a000 -  0x5d9aff7  com.apple.framework.familycontrols 2.0.2 (2020) <C96C8A99-A40C-8B9C-1FBA-A0F46AC92F17> /System/Library/PrivateFrameworks/FamilyControls.framework/Versions/A/FamilyCon trols
    0x5db2000 -  0x5e60ff3  com.apple.ink.framework 1.3.3 (107) <233A981E-A2F9-56FB-8BDE-C2DEC3F20784> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/Ink.framework /Versions/A/Ink
    0x5e8a000 -  0x5ea9ff7  com.apple.CoreVideo 1.6.2 (45.6) <EB53CAA4-5EE2-C356-A954-5775F7DDD493> /System/Library/Frameworks/CoreVideo.framework/Versions/A/CoreVideo
    0x5ec0000 -  0x5eceff7  com.apple.opengl 1.6.14 (1.6.14) <82622F67-E032-0BF6-A78D-50B346E8D0FD> /System/Library/Frameworks/OpenGL.framework/Versions/A/OpenGL
    0x5ed6000 -  0x5f07ff7  libGLImage.dylib ??? (???) <D18E2E76-DBF4-6930-039A-F66CA0D120B3> /System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/libGLImage.dyl ib
    0x5f0f000 -  0x5f30fe7  com.apple.opencl 12.3.6 (12.3.6) <B4104B80-1CB3-191C-AFD3-697843C6BCFF> /System/Library/Frameworks/OpenCL.framework/Versions/A/OpenCL
    0x5f39000 -  0x5f3dff7  IOSurface ??? (???) <D849E1A5-6B0C-2A05-2765-850EC39BA2FF> /System/Library/Frameworks/IOSurface.framework/Versions/A/IOSurface
    0x5f45000 -  0x5f88ff7  libGLU.dylib ??? (???) <6CC3CE6A-7024-C685-EADA-7F9DC27128E2> /System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/libGLU.dylib
    0x5f96000 -  0x5fa1ff7  libGL.dylib ??? (???) <3E34468F-E9A7-8EFB-FF66-5204BD5B4E21> /System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/libGL.dylib
    0x5fb0000 -  0x60bcfe7  libGLProgrammability.dylib ??? (???) <6167CEB0-D8D6-C4D9-DD74-49755ADB540F> /System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/libGLProgramma bility.dylib
    0x60db000 -  0x60deff7  libCoreVMClient.dylib ??? (???) <37F56237-4ABA-E5B5-968D-70FFE357E8E0> /System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/libCoreVMClien t.dylib
    0x60e3000 -  0x60e7ff7  libGFXShared.dylib ??? (???) <09540618-2ED1-72C4-61CB-938B35927568> /System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/libGFXShared.d ylib
    0x60ec000 -  0x616effb  SecurityFoundation ??? (???) <A8D248DE-8670-970D-39E3-A9738CFDBEE1> /System/Library/Frameworks/SecurityFoundation.framework/Versions/A/SecurityFoun dation
    0x61a5000 -  0x61aaff7  com.apple.OpenDirectory 10.6 (10.6) <C1B46982-7D3B-3CC4-3BC2-3E4B595F0231> /System/Library/Frameworks/OpenDirectory.framework/Versions/A/OpenDirectory
    0x61b2000 -  0x61b8fe7  com.apple.CommerceCore 1.0 (9.1) <521D067B-3BDA-D04E-E1FA-CFA526C87EB5> /System/Library/PrivateFrameworks/CommerceKit.framework/Versions/A/Frameworks/C ommerceCore.framework/Versions/A/CommerceCore
    0x61bf000 -  0x61d7ff7  com.apple.CFOpenDirectory 10.6 (10.6) <F9AFC571-3539-6B46-ABF9-46DA2B608819> /System/Library/Frameworks/OpenDirectory.framework/Versions/A/Frameworks/CFOpen Directory.framework/Versions/A/CFOpenDirectory
    0x61e8000 -  0x6235feb  com.apple.DirectoryService.PasswordServerFramework 6.1 (6.1) <136BFA48-D456-B677-3B5D-40A6946C3A09> /System/Library/PrivateFrameworks/PasswordServer.framework/Versions/A/PasswordS erver
    0x6251000 -  0x6273fef  com.apple.DirectoryService.Framework 3.6 (621.16) <5566E769-6459-78A7-DD2C-1D3068BD3932> /System/Library/Frameworks/DirectoryService.framework/Versions/A/DirectoryServi ce
    0x627d000 -  0x628dff7  libsasl2.2.dylib 3.15.0 (compatibility 3.0.0) <E276514D-394B-2FDD-6264-07A444AA6A4E> /usr/lib/libsasl2.2.dylib
    0x6294000 -  0x62d7ff7  com.apple.NavigationServices 3.5.4 (182) <8DC6FD4A-6C74-9C23-A4C3-715B44A8D28C> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/NavigationSer vices.framework/Versions/A/NavigationServices
    0x6300000 -  0x6302ff7  com.apple.securityhi 4.0 (36638) <E7D83480-77BB-72F9-72F3-AEE198CE589F> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/SecurityHI.fr amework/Versions/A/SecurityHI
    0x6307000 -  0x630ffeb +QualityPlay.dylib ??? (???) /Library/Application Support/OLYMPUS/DSSPlayer/lib/QualityPlay.dylib
    0x632b000 -  0x6333feb +StandardPlay.dylib ??? (???) /Library/Application Support/OLYMPUS/DSSPlayer/lib/StandardPlay.dylib
    0x635e000 -  0x6370fcf +LongPlay.dylib ??? (???) /Library/Application Support/OLYMPUS/DSSPlayer/lib/LongPlay.dylib
    0x6375000 -  0x6388fdf +DSSAES.dylib ??? (???) /Library/Application Support/OLYMPUS/DSSPlayer/lib/DSSAES.dylib
    0x638c000 -  0x6392fff  com.apple.CommonPanels 1.2.4 (91) <CE92759E-865E-8A3B-1488-ECD497E4074D> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/CommonPanels. framework/Versions/A/CommonPanels
    0x639a000 -  0x639dffb  com.apple.help 1.3.2 (41.1) <8AC20B01-4A3B-94BA-D8AF-E39034B97D8C> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/Help.framewor k/Versions/A/Help
    0x63a2000 -  0x6406fff  com.apple.htmlrendering 72 (1.1.4) <0D22B190-513B-7FF6-39FC-9D336285DE08> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/HTMLRendering .framework/Versions/A/HTMLRendering
    0x6428000 -  0x643dfff  com.apple.ImageCapture 6.1 (6.1) <B909459A-EAC9-A7C8-F2A9-CD757CDB59E8> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/ImageCapture. framework/Versions/A/ImageCapture
    0x6453000 -  0x646ffe3  com.apple.openscripting 1.3.1 (???) <2A748037-D1C0-6D47-2C4A-0562AF799AC9> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/OpenScripting .framework/Versions/A/OpenScripting
    0x647f000 -  0x64eafd7 +com.yourcompany.yourcocoaframework ??? (1.53) /Library/Frameworks/OlympusServiceProvider.framework/Versions/A/OlympusServiceP rovider
    0x657c000 -  0x65b9ff7  com.apple.CoreMedia 0.484.60 (484.60) <8FAB137D-682C-6DEC-5A15-F0029A5B226F> /System/Library/PrivateFrameworks/CoreMedia.framework/Versions/A/CoreMedia
    0x65d4000 -  0x6701ffb  com.apple.MediaToolbox 0.484.60 (484.60) <A7FE2739-64A7-40EB-A6E7-69FBCE3C87D4> /System/Library/PrivateFrameworks/MediaToolbox.framework/Versions/A/MediaToolbo x
    0x6765000 -  0x6c20ff7  com.apple.VideoToolbox 0.484.60 (484.60) <B53299EC-E30F-EC04-779D-29B7113CC14A> /System/Library/PrivateFrameworks/VideoToolbox.framework/Versions/A/VideoToolbo x
    0x6cc9000 -  0x6d10ffb  com.apple.CoreMediaIOServices 140.0 (1496) <DA152F1C-8EF4-4F5E-6D60-82B1DC72EF47> /System/Library/PrivateFrameworks/CoreMediaIOServices.framework/Versions/A/Core MediaIOServices
    0x6d31000 -  0x6dacfff  com.apple.AppleVAFramework 4.10.27 (4.10.27) <BFD2D1CA-535C-F16F-0EB5-04905ABD65CF> /System/Library/PrivateFrameworks/AppleVA.framework/Versions/A/AppleVA
    0x6f9d000 -  0x6fa8ff7  libCSync.A.dylib 545.0.0 (compatibility 64.0.0) <287DECA3-7821-32B6-724D-AE03A9A350F9> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ CoreGraphics.framework/Versions/A/Resources/libCSync.A.dylib
    0x6ff2000 -  0x6ff5ff7  libCGXType.A.dylib 545.0.0 (compatibility 64.0.0) <4D766435-EB76-C384-0127-1D20ACD74076> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ CoreGraphics.framework/Versions/A/Resources/libCGXType.A.dylib
    0x7c00000 -  0x7c3bffb  libFontRegistry.dylib ??? (???) <19ED5DE0-D3AF-B229-9193-35D58FE377E5> /System/Library/Frameworks/ApplicationServices.framework/Frameworks/ATS.framewo rk/Resources/libFontRegistry.dylib
    0x7e04000 -  0x7e37fff  libTrueTypeScaler.dylib ??? (???) <8ADB7D19-413E-4499-C874-13C383F97685> /System/Library/Frameworks/ApplicationServices.framework/Frameworks/ATS.framewo rk/Resources/libTrueTypeScaler.dylib
    0x7e43000 -  0x7e84ff7  libRIP.A.dylib 545.0.0 (compatibility 64.0.0) <80998F66-0AD7-AD12-B9AF-3E8D2CE6DE05> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ CoreGraphics.framework/Versions/A/Resources/libRIP.A.dylib
    0x7fef000 -  0x7ff0ff7 +com.olympus.DSSPlayerV7.LeopardSupportForDSSPlayer 1.1 (1.0) <2AAA1454-CEBA-AA58-0DA1-D8E02A7EDBB4> /Applications/DSS Player/DSS Player.app/Contents/Resources/Leopard.bundle/Contents/MacOS/Leopard
    0x1aed5000 - 0x1b3e7feb  com.apple.RawCamera.bundle 3.14.0 (646) <27962422-EA30-43CF-2B3E-E662BB4C46C7> /System/Library/CoreServices/RawCamera.bundle/Contents/MacOS/RawCamera
    0x20000000 - 0x20098fe7  edu.mit.Kerberos 6.5.11 (6.5.11) <F36DB665-A88B-7F5B-6244-6A2E7FFFF668> /System/Library/Frameworks/Kerberos.framework/Versions/A/Kerberos
    0x64b00000 - 0x64b07ff3  com.apple.print.framework.Print 6.1 (237.1) <F5AAE53D-5530-9004-A9E3-2C1690C5328E> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/Print.framewo rk/Versions/A/Print
    0x8fe00000 - 0x8fe4162b  dyld 132.1 (???) <39AC3185-E633-68AA-7CD6-1230E7F1CEF4> /usr/lib/dyld
    0xfa100000 - 0xfa192fe7  com.apple.print.framework.PrintCore 6.3 (312.7) <7410D1B2-655D-68DA-D4B9-2C65747B6817> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ PrintCore.framework/Versions/A/PrintCore
    0xffff0000 - 0xffff1fff  libSystem.B.dylib ??? (???) <2DCD13E3-1BD1-6F25-119A-3863A3848B90> /usr/lib/libSystem.B.dylib
    Model: MacBookPro7,1, BootROM MBP71.0039.B0B, 2 processors, Intel Core 2 Duo, 2.4 GHz, 4 GB, SMC 1.62f7
    Graphics: NVIDIA GeForce 320M, NVIDIA GeForce 320M, PCI, 256 MB
    Memory Module: global_name
    AirPort: spairport_wireless_card_type_airport_extreme (0x14E4, 0x8D), Broadcom BCM43xx 1.0 (5.10.131.42.4)
    Bluetooth: Version 2.4.5f3, 2 service, 19 devices, 1 incoming serial ports
    Network Service: AirPort, AirPort, en1
    Serial ATA Device: TOSHIBA MK2555GSXF, 232.89 GB
    Serial ATA Device: MATSHITADVD-R   UJ-898
    USB Device: Built-in iSight, 0x05ac  (Apple Inc.), 0x8507, 0x24600000 / 2
    USB Device: Internal Memory Card Reader, 0x05ac  (Apple Inc.), 0x8403, 0x26100000 / 2
    USB Device: BRCM2046 Hub, 0x0a5c  (Broadcom Corp.), 0x4500, 0x06600000 / 4
    USB Device: Bluetooth USB Host Controller, 0x05ac  (Apple Inc.), 0x8213, 0x06610000 / 5
    USB Device: IR Receiver, 0x05ac  (Apple Inc.), 0x8242, 0x06500000 / 3
    USB Device: Apple Internal Keyboard / Trackpad, 0x05ac  (Apple Inc.), 0x0236, 0x06300000 / 2

    Hi,
    Please review the link below, here is a useful article for you.
    Tips and Tricks for Deploying the Application Catalog in System Center 2012 Configuration Manager
    http://blogs.technet.com/b/configmgrteam/archive/2012/07/05/tips-and-tricks-for-deploying-the-application-catalog-in-system-center-2012-configuration-manager.aspx
    We
    are trying to better understand customer views on social support experience, so your participation in this
    interview project would be greatly appreciated if you have time.
    Thanks for helping make community forums a great place.

  • Software raid won't boot after updating to "mdadm" in mkinitcpio.conf

    After a power outage I've discovetred the config I was using (with raid in mkinitcpio.conf) no longer works, it's mdadm now - that's fine.  I've updated that and re-run mkinitcpio successfully, however my system is unable to boot from the root filesystem /dev/md2 like so:
    Waiting for 10 seconds for device /dev/md2 ...
    Root device '/dev/md2' doesn't exist. Attempting to create it.
    ERROR: Unable to determine major/minor number of root device '/dev/md2'.
    You are being dropped to a recovery shell
        Type 'exit' to try and continue booting
    /bin/sh: can't access tty; job control turned off
    [ramfs /]#
    As far as I can see from reading various threads and http://wiki.archlinux.org/index.php/Ins … AID_or_LVM I'm doing the right things now (although I'm not using lvm at all, which makes the installation document a little confusing).
    I think I've included all the appropriate bits of config here that should be working.  I assume I've missed something fundamental - any ideas?
    menu.lst:
    # (0) Arch Linux
    title  Arch Linux  [/boot/vmlinuz26]
    root   (hd0,0)
    kernel /vmlinuz26 root=/dev/md2 ro
    initrd /kernel26.img
    mkinitcpio.conf:
    HOOKS="base udev autodetect pata scsi mdadm sata filesystems"
    fstab:
    /dev/md1 /boot ext3 defaults 0 1
    /dev/md2 / ext3 defaults 0 1
    mdadm.conf
    ARRAY /dev/md1 level=raid1 num-devices=2 metadata=0.90 UUID=7ae70fa6:9f54ba0a:21
    47a9fe:d45dbc0c
    ARRAY /dev/md2 level=raid1 num-devices=2 metadata=0.90 UUID=20560268:8a089af7:e6
    043406:dbdabe38
    Thanks!

    Hi magec, that's quite helfpul - I've certainly got further.
    Before I was doing this to set up the chroot (which is what is suggested in the wiki article about setting up software raid):
    mdadm -A /dev/md1 /dev/sda1 /dev/sdb1
    mdadm -A /dev/md2 /dev/sda2 /dev/sdb2
    mount /dev/md2 /mnt
    mount /dev/md1 /mnt/boot
    mount -o bind /dev /mnt/dev
    mount -t proc none /mnt/proc
    chroot /mnt /bin/bash
    But based on your suggestion it's working better
    mdadm -A /dev/md1 /dev/sda1 /dev/sdb1
    mdadm -A /dev/md2 /dev/sda2 /dev/sdb2
    mount /dev/md2 /mnt
    mount /dev/md1 /mnt/boot
    mount -t proc none /mnt/proc
    mount -t sysfs none /mnt/sys
    mount -n -t ramfs none /mnt/dev
    cp -Rp /dev/* /mnt/dev
    chroot /mnt /bin/bash
    The boot is now getting further, but now I'm getting:
    md: md2 stopped.
    md: bind<sdb2>
    md: bind<sda2>
    raid1: raid set md2 active with 2 out of 2 mirrors
    md2: detected capacity change from 0 to 32218349568
    mdadm: /dev/md2 has been started with 2 drives.
    md2: Waiting 10 seconds for device /dev/md2 ...
    unknown partition table
    mount: mounting /dev/md2 on /new_root failed: No such device
    ERROR: Failed to mount the real root device.
    Bailing out, you are on your own. Good luck.
    /bin/sh: can't access tty; job contol turned off
    [ramfs /]#
    The bit that really confuses me is this:
    [ramfs /]# cat /proc/mdstat
    Personalities : [raid1]
    md2 : active raid1 sda2[0] sdb2[1]
    31463232 blocks [2/2] [UU]
    md1 : active raid1 sda1[0] sdb1[1]
    208704 blocks [2/2] [UU]
    unused devices: <none>
    [ramfs /]# mount /dev/md2 /new_root
    mount: mounting /dev/md2 on /new_root failed: No such file or directory
    [ramfs /]# ls /dev/md2
    /dev/md2
    [ramfs /]#
    So the array is up, the device node is there but it can't be mounted?  Very strange.
    Last edited by chas (2010-05-02 11:24:09)

  • Can you move a software raid 1 from one mac to another

    I have a 2 disc software raid 1 on my powermac and I want to move it to my mac pro. Does anyone know if I can do this?

    It appears that in Mac OS X 10.4, and again in the transition to 10.7, RAID format may have undergone dramatic changes. If you are trying to move a RAID array across those boundaries, you may not have the best results moving the drives directly.

  • [Solved] Move Software RAID 5 Array From NAS To Arch

    Edit: I probably never had a problem at all, the error in dmesg probably just scared me, because after I disconnected it I noticed that /dev/d127 was 8.1 TB, the exact size of my RAID array node in my NAS which was /dev/md0, I just overlooked it. I reconnected it to my pc and mounted /dev/md127 to /mnt/raid and got this wonderful sight!
    [bran@ra ~]$ ls /mnt/raid
    data lost+found meta sys
    [bran@ra ~]$ ls /mnt/raid/data/
    data ftproot module _NAS_Media _NAS_Piczza_ _NAS_Recycle_RAID _P2P_DownLoad_ stackable _SYS_TMP TV USBHDD
    download htdocs Movies _NAS_NFS_Exports_ NAS_Public nzbget-downloads PLEX_CONFIG sys tmp USBCopy
    I bought a Thecus N4520 a few months ago and it's ok but programs crash a lot and they're hard to debug, apps have to be updated manually and the whole thing is moderately underpowered. I'm trying to move the software RAID 5 array from the NAS to my desktop, the kernel seems to detect that there is a RAID array but all these drives aren't part of it. I'm pretty new to RAID and I'm just getting my feet wet with it.
    When I try to assemble the RAID array, it just tells me that it isn't an md array. How can I get it to build my array?
    [bran@ra ~]$ sudo mdadm --assemble /dev/sdb /dev/sdc /dev/sdd /dev/sde
    mdadm: device /dev/sdb exists but is not an md array.
    Found this little chunk of info in dmesg, it says that the md devices have unknown partition tables.
    [ 3.262225] md: raid1 personality registered for level 1
    [ 3.262483] iTCO_wdt: Intel TCO WatchDog Timer Driver v1.10
    [ 3.262508] iTCO_wdt: Found a Patsburg TCO device (Version=2, TCOBASE=0x0460)
    [ 3.262585] iTCO_wdt: initialized. heartbeat=30 sec (nowayout=0)
    [ 3.262933] md/raid1:md126: active with 4 out of 4 mirrors
    [ 3.262961] md126: detected capacity change from 0 to 536850432
    [ 3.263272] RAID1 conf printout:
    [ 3.263274] --- wd:4 rd:4
    [ 3.263276] disk 0, wo:0, o:1, dev:sdc3
    [ 3.263276] disk 1, wo:0, o:1, dev:sdb3
    [ 3.263277] disk 2, wo:0, o:1, dev:sdd3
    [ 3.263278] disk 3, wo:0, o:1, dev:sde3
    [ 3.263501] md: bind<sde4>
    [ 3.264810] md: bind<sdb2>
    [ 3.268262] async_tx: api initialized (async)
    [ 3.272632] md: raid6 personality registered for level 6
    [ 3.272636] md: raid5 personality registered for level 5
    [ 3.272637] md: raid4 personality registered for level 4
    [ 3.272905] md/raid:md127: device sdb2 operational as raid disk 1
    [ 3.272908] md/raid:md127: device sde2 operational as raid disk 3
    [ 3.272910] md/raid:md127: device sdd2 operational as raid disk 2
    [ 3.272911] md/raid:md127: device sdc2 operational as raid disk 0
    [ 3.273211] md/raid:md127: allocated 0kB
    [ 3.273241] md/raid:md127: raid level 5 active with 4 out of 4 devices, algorithm 2
    [ 3.273243] RAID conf printout:
    [ 3.273244] --- level:5 rd:4 wd:4
    [ 3.273245] disk 0, o:1, dev:sdc2
    [ 3.273246] disk 1, o:1, dev:sdb2
    [ 3.273247] disk 2, o:1, dev:sdd2
    [ 3.273248] disk 3, o:1, dev:sde2
    [ 3.273273] md127: detected capacity change from 0 to 8929230716928
    [ 3.273322] RAID conf printout:
    [ 3.273326] --- level:5 rd:4 wd:4
    [ 3.273329] disk 0, o:1, dev:sdc2
    [ 3.273331] disk 1, o:1, dev:sdb2
    [ 3.273332] disk 2, o:1, dev:sdd2
    [ 3.273360] disk 3, o:1, dev:sde2
    [ 3.283617] md126: unknown partition table
    [ 3.309239] md127: unknown partition table
    [ 3.312660] md: bind<sdb4>
    [ 3.318291] md/raid1:md124: not clean -- starting background reconstruction
    [ 3.318296] md/raid1:md124: active with 4 out of 4 mirrors
    [ 3.318333] md124: detected capacity change from 0 to 10736291840
    [ 3.318385] RAID1 conf printout:
    [ 3.318391] --- wd:4 rd:4
    [ 3.318395] disk 0, wo:0, o:1, dev:sdc4
    [ 3.318398] disk 1, wo:0, o:1, dev:sdb4
    [ 3.318402] disk 2, wo:0, o:1, dev:sdd4
    [ 3.318405] disk 3, wo:0, o:1, dev:sde4
    [ 3.319890] md124: unknown partition table
    [ 3.323462] md: bind<sde1>
    [ 3.338094] md/raid1:md125: active with 4 out of 4 mirrors
    [ 3.338225] md125: detected capacity change from 0 to 2146414592
    [ 3.338253] RAID1 conf printout:
    [ 3.338258] --- wd:4 rd:4
    [ 3.338262] disk 0, wo:0, o:1, dev:sdc1
    [ 3.338266] disk 1, wo:0, o:1, dev:sdb1
    [ 3.338268] disk 2, wo:0, o:1, dev:sdd1
    [ 3.338271] disk 3, wo:0, o:1, dev:sde1
    Here's my full dmesg
    mdadm.conf
    # The designation "partitions" will scan all partitions found in /proc/partitions
    DEVICE partitions
    ARRAY /dev/md127 metadata=1.2 name=(none):0 UUID=d1d14afc:23490940:a0f7f996:d7b87dfb
    ARRAY /dev/md126 metadata=1.2 name=(none):50 UUID=d43d5dd6:9446766e:1a7486f4:b811e16d
    ARRAY /dev/md125 metadata=1.2 name=(none):10 UUID=f502437a:d27d335a:d11578d5:6e119d58
    ARRAY /dev/md124 metadata=1.2 name=(none):70 UUID=ea980643:5c1b79e8:64f1b4cb:2462799b
    Last edited by brando56894 (2014-04-21 22:51:01)

    Sorry I numbered them to show the flow of information, this was also just a place for me to store info as I worked through it. I managed to get it to work by creating a partition that takes up the whole drive and is actually 22 GB larger than all the other drives (since I found out that the had root, swap and home partitions that are no longer needed).
    I should be able to resize the other partitions without a problem, correct? They're EXT4. Should I unmount the raid array and do them individually, remount the array, let it sync and do the next? Or just unmount the array, resize all of them, mount it and let it sync?

  • Adding A New Drive To A Software RAID 5 Array

    Edit 3: Just mounted the partitions and I can delete them because they contain nothing special. Is it safe to expand the 2nd partition of each drive to fill up the left over 22 GB?
    Edit 2: I just deleted all the partitions off of my new drive and created one partition, then added it to the array and it works just fine. My next question is, can I delete all the smaller partitions and expand /dev/sd[x]2 to reclaim all the space (about 70 GB)?
    One of my drives failed and Western Digital sent me a new drive, except it was an external drive instead of an internal drive, so I cracked it open and the label looked different. Turns out it's just refurbished and it's the same model as my other drives (WD Caviar Green 3 TB).
    I've read through the wiki article on Software RAID and created the partitions exactly the same as my other drives, but while creating the main 2.7 TB partition it says that the ending sector is out of range when it isn't. I'm new to all this so I have no idea what to do. From what I've read there normally aren't this many partitions per disk, correct? I also have md124, md125 and md126 for the other partitions. md127 is for the 2.7 TB partitions. I took the array out of my Thecus N4520. I have a 3 TB external drive and a 1TB internal, along with another 500 GB drive. Would I be better off at destroying the RAID set and creating a fresh RAID 5 set, considering I'm losing about 90 GB if I don't need the smaller partitions.
    /dev/sdc
    Disk /dev/sdc: 5860533168 sectors, 2.7 TiB
    Logical sector size: 512 bytes
    Disk identifier (GUID): 00636413-FB4D-408D-BC7F-EBAF880FBE6D
    Partition table holds up to 128 entries
    First usable sector is 34, last usable sector is 5860533134
    Partitions will be aligned on 2048-sector boundaries
    Total free space is 43941 sectors (21.5 MiB)
    Number Start (sector) End (sector) Size Code Name
    1 41945088 46139375 2.0 GiB FD00
    2 47187968 5860491263 2.7 TiB FD00 THECUS
    3 46139392 47187951 512.0 MiB FD00
    4 2048 20973559 10.0 GiB FD00 i686-THECUS
    5 20973568 41945071 10.0 GiB FD00
    /dev/sdd
    Disk /dev/sdd: 5860533168 sectors, 2.7 TiB
    Logical sector size: 512 bytes
    Disk identifier (GUID): C5900FF4-95A1-44BD-8A36-E1150E4FC458
    Partition table holds up to 128 entries
    First usable sector is 34, last usable sector is 5860533134
    Partitions will be aligned on 2048-sector boundaries
    Total free space is 43941 sectors (21.5 MiB)
    Number Start (sector) End (sector) Size Code Name
    1 41945088 46139375 2.0 GiB FD00
    2 47187968 5860491263 2.7 TiB FD00 THECUS
    3 46139392 47187951 512.0 MiB FD00
    4 2048 20973559 10.0 GiB FD00 i686-THECUS
    5 20973568 41945071 10.0 GiB FD00
    /dev/sde
    Disk /dev/sde: 5860533168 sectors, 2.7 TiB
    Logical sector size: 512 bytes
    Disk identifier (GUID): 2B5527AC-9D53-4506-B31F-28736A0435BD
    Partition table holds up to 128 entries
    First usable sector is 34, last usable sector is 5860533134
    Partitions will be aligned on 2048-sector boundaries
    Total free space is 43941 sectors (21.5 MiB)
    Number Start (sector) End (sector) Size Code Name
    1 41945088 46139375 2.0 GiB FD00
    2 47187968 5860491263 2.7 TiB FD00 THECUS
    3 46139392 47187951 512.0 MiB FD00
    4 2048 20973559 10.0 GiB FD00 i686-THECUS
    5 20973568 41945071 10.0 GiB FD00
    new drive: /dev/sdf
    Disk /dev/sdf: 5860467633 sectors, 2.7 TiB
    Logical sector size: 512 bytes
    Disk identifier (GUID): 93F9EF48-998D-4EF9-B5B7-936D4D3C7030
    Partition table holds up to 128 entries
    First usable sector is 34, last usable sector is 5860467599
    Partitions will be aligned on 2048-sector boundaries
    Total free space is 5813281700 sectors (2.7 TiB)
    Number Start (sector) End (sector) Size Code Name
    1 41945088 46139375 2.0 GiB FD00 Linux RAID
    2 47187968 47187969 1024 bytes FD00 Linux RAID
    3 46139392 47187951 512.0 MiB FD00 Linux RAID
    4 2048 20973559 10.0 GiB FD00 Linux RAID
    5 20973568 41945071 10.0 GiB FD00 Linux RAID
    when I type in 5860491263 as the end sector gdisk does nothing, just wants more input. If I type +2.7T it accepts it, but really it just creates a partition that's 1KB in size!
    I am able to create a 2.7 TB partition with an end sector of 5860467599, this won't screw anything up will it?
    Edit 1: just tried it and got this
    [root@ra /home/bran]# mdadm --add /dev/md127 /dev/sdf2
    mdadm: /dev/sdf2 not large enough to join array
    [root@ra /home/bran]# fdisk -l /dev/sdf
    Disk /dev/sdf: 2.7 TiB, 3000559428096 bytes, 5860467633 sectors
    Units: sectors of 1 * 512 = 512 bytes
    Sector size (logical/physical): 512 bytes / 4096 bytes
    I/O size (minimum/optimal): 4096 bytes / 4096 bytes
    Disklabel type: gpt
    Disk identifier: 93F9EF48-998D-4EF9-B5B7-936D4D3C7030
    Device Start End Size Type
    /dev/sdf1 41945088 46139375 2G Linux RAID
    /dev/sdf2 47187968 5860467599 2.7T Linux RAID
    /dev/sdf3 46139392 47187951 512M Linux RAID
    /dev/sdf4 2048 20973559 10G Linux RAID
    /dev/sdf5 20973568 41945071 10G Linux RAID
    Last edited by brando56894 (2014-04-28 00:47:29)

    Sorry I numbered them to show the flow of information, this was also just a place for me to store info as I worked through it. I managed to get it to work by creating a partition that takes up the whole drive and is actually 22 GB larger than all the other drives (since I found out that the had root, swap and home partitions that are no longer needed).
    I should be able to resize the other partitions without a problem, correct? They're EXT4. Should I unmount the raid array and do them individually, remount the array, let it sync and do the next? Or just unmount the array, resize all of them, mount it and let it sync?

Maybe you are looking for