Jump to content

Search the Community: Showing results for tags 'RAID'.

More search options

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


  • InsanelyMac Lounge
    • Front Page News and Rumors
    • Reader News and Reviews
    • Forum Information and Feedback
  • OSx86 Project
    • New Releases and Updates
    • New Users Lounge
    • Developers Corner
    • Tutorials (The Genius Bar)
    • Technical FAQ
    • Installation
    • Post-Installation
    • DSDT and SSDT
    • Hardware Components and Drivers
    • Desktops
    • Notebooks
    • Netbooks
    • Tablets
    • MacMod of the Month
    • Multi-booting and Virtualisation
  • International
    • Your Language
    • Deutsch
    • Español
    • Français
    • Italiano
    • Português
    • Русский
  • Apple World
    • Mac OS X
    • Apple Computers and Hardware
    • iOS Devices
    • Mac Applications
    • Mac Programming and Development
    • iOS Programming and Development
    • Mac Gaming
    • Mac Accessories
  • Discuss and Learn
    • Windows Discussion
    • *nix
    • Apple Opinions and Discussion
    • The Great Debates
    • Internet(s), Servers, and Networks
    • Buying Thoughts, Reviews, and Recommendations
    • Mods and Overclocking
    • The Big Issues [Real Life]
  • Everything Else
    • Creativity
    • Thunderdome (Random Stuff)
    • Laughs
    • The Marketplace


  • Kexts
    • Graphics Cards
    • Audio
    • LAN and Wireless
    • Other
  • Kernels
  • Bootloaders
  • DSDTs
    • Patches
  • Pandora
  • Apps
  • Miscellaneous
  • Customization

Find results in...

Find results that contain...

Date Created

  • Start


Last Updated

  • Start


Filter by number of...


  • Start




Website URL







Found 9 results

  1. mauriziopasotti

    Raid Hardware Prove su strada.

    concordo con Fabio, con Snow e la P6T montare e smontare i dischi induceva spesso errori.... e sistema fermo... ho abbandonato passando a ML con un SSD.... Uso pero il Raid hardware della mia Asus Sabertooth x58. La Asus Sabertootx58 ha a bordo oltre il controller Sata Intel ICH10R con 6 porte 3Gb/s, anche il controller Marvell 9128 PCIe SATA con 2 porte 6Gb/s. Il Marvell permette di essere perfettamente utilizzato, oltre come controller per due dischi Sata, anche come controller RAID 0 o Raid 1. Il menu di configurazione è facilmente raggiungibile premendo CTRL + M al boot del bios. Semplicissimo nei suoi parametri, vi permette di selezionare i due dischi da utilizzare e che tipo di Raid (1 o 0 ) desiderate, con F10 salvate e uscite. Ai nostri hack il disco risultante (Raid 0 o Raid 1) viene visto come un unico disco anche da Utility Disco. Con il Raid 0 sfrutterai i dischi contemporaneamente per leggere e scrivere i dati, le prestazioni saranno migliori. Se perdi un disco perdi tutti i dati! Con il Raid 1 le prestazioni non migliorano ma la sicurezza sì. Infatti se si rompe un disco non perdi i dati perché sono stati scritti anche sugli altri. Ho testato ambedue le modalità Raid, Simulando la rottura di uno dei due dischi in modalità Raid 1 e verificando la funzionalità del restante senza individuare problemi. Ho anche verificato l'incremento di prestazioni del Raid 0 e devo dirvi che ci si allinea con gli SSD (circa 220/240 Mb/s W/R) Altra cosa che forse interessa di più a tutti noi è la piena compatibilità con i bootloader del mondo Hacintosh Chameleon e Enoch. Sicuramente meno tortuoso da dover gestire che un Raid software di Mac con …montare e smontare i dischi... come detto sopra….. Una nota, se aggregate in raid dischi di grandi dimensioni (io l'ho testato con due dischi da 1 Tb Sata 6Gb/s) incapperete nell'errore "boot 0" all'avvio. Avviene per la differenza di dimensione dei settori del disco …… Fabio71 ha fatto una F.A.Q. che risolve brillantemente questo problema. http://www.insanelymac.com/forum/topic/285021-risolvere-lerrore-boot-0/ Portebbe essere interessante aggiungere altre esperienze e "Prove su strada" di altri utenti con altri controller ... e problemi. Buon Raid a tutti! Maurizio
  2. Hello, good people! I just successfully installed 10.8.3 on a i7-2600k/Gigabyte Z68XP-UD3 (BIOS v. 10, "Touch BIOS") using a USB 3 external HDD and everything works just fine, except for one annoying thing: this computer have also Windows 7, installed on a RAID array using two SSD disks, and when i try to boot it from Chameleon, i get a "no bootmngr" message. I have to resort to hit F12 and change the boot order to access Windows. How do i solve this? RAID is not a realm where i really feel comfortable. Another question, albeit related to the first: if i clone the OSX installation from the external HDD to an internal one, will it be able to boot, despite SATA mode being set as RAID? Or OSX and Windows RAID arrays cannot share the same space? t! All the besr
  3. Hello, First off, I have been around the hackintosh scene casually for a while so I'm not completely new. I own an MSI GT683r-242us, which has an intel i7 2630qm processor and two 500gb hdd. Now, currently my two hard drives are striped in RAID 0 configuration with two partitions, one containing my Windows 7 install, and the other is blank storage. This stripe is set up as an MBR partition table. For me, I am forced to run mac on an external hard drive. Here is what i'd like to know: Is it possible for me to access the storage partition of this set up so I can install OSX natively onto my internal hard drives? Is there a way to get disc utility to see the two partitions the my windows machine sees, instead of 3 different drives that are of inconsistent size when compared to the real partitions. Furthermore, if anyone knows a way to backup my windows OS by mirror imagining it so i can disable RAID and use the two hdds independently, (basically, i dont want to have to reinstall everything[possibly norton ghost? i dont know how it works tho])) Thanks a bundle in advance.
  4. This guide is for setting up Apple software RAID-0 on any SATA controller or combination of controllers that support booting into OSX. A few things to keep in mind, first being that I am not responsible for any loss of data, loss of hair, or hardware damages if they were to occur. RAID-0 is built for speed and that's about it, so if you care about data parity this is not for you. RAID-0 will stripe your data across 2 or more drives, which means if any one of them fails, you will loose your data. Time Machine or other backup is highly recommended. While in the past RAID-0 helped to speed up the physical limitations caused by older rotational hard disks, on SSD drives with their faster read/write speeds, It is usually the SATA port of the controller that becomes the bottle neck, and splitting that bandwidth up can have dramatic results for some people. Picking which controller or controllers to use is a major factor in what your final results will be, and any controller that is buggy, ejects drives randomly or causes any headaches now, don't use it or you'll probably regret it. Although I don't recommend swapping your configured RAID array drives around to different ports, one benefit of software RAID is you can with little chance of a problem, unlike HW RAID where it's bound to that controller. So... pre-setup: First we need something to put onto our array once we make it, and using the Mountain Lion Installer to do a clean install to your RAID, will result in an installation failure when the installer complains about not being able to make a recovery partition on a RAID. I've been able to instead restore from a Time Machine backup onto the new array by booting into the Mountain Lion Installer, but others have received the same Recovery Partition error when trying this as well. You also wan't to only make your Mountain Lion RAID while booted into Mountain Lion, as Lion or older versions will not know how to properly make the kernel caches and the array will not be bootable. So you'll need an extra drive with Mountain Lion installed. Boot into that drive. Let's-Go: Build array in disk utility. When prompted, choose whatever block size you want to use, default value recommended. Here's how it should look, I enabled Disk Utility to show hidden partitions not normally visible. Now use CarbonCopyCloner or similar to clone your working Mountain Lion install over to the RAID array. Chameleon will need to be installed to each drives hidden "boot OSX" partition along with /Extra on each and kernel cache will be built on each. OSX cannot boot without kernel cache, i.e. -f, or will get error "mach_kernel not found". In /Extra folder of each "boot OSX" partition, in org.chameleon.boot.plist, you must include additional kernel flag rd=uuid boot-uuid="UUID of your RAID array here, use Disk Utility and select array then Get Info" Get UUID here: Most the boot process takes place from the cache, then once the soft raid kexts are loaded, system can then find the array to finish booting, without this you will get "still waiting on root device" Here is my entire org.chameleon.Boot.plist so you can get an idea of how it should look: As mentioned, Chameleon, along with your Extra folder and updated org.chameleon.Boot.plist all need to be installed onto the boot helper partitions, which are hidden by default and called "Boot OS X", I have seen them without space too like "Boot OSX". They are not striped and are not part of the RAID array, making them readable by the BIOS and by Chameleon. To install Chameleon to the "Boot OS X" helper partitions, First find out the disk # for each one using Terminal and diskutil command and make note of the Disk #, the partition #'s will always follow the same layout where "Boot OS X" will be partition 3( s3 ): diskutil list Make note of the disk # for each drive that will make up your array ( rdiskX ) where X is the drive # Rather than run the Chameleon installer, install the 3 needed Chameleon boot files manually. They are; boot, boot0 and boot1h. If you have Chameleon package installer, they can be extracted to the desktop with Pacifist, or if you grab the binary you can just copy them right over. Either way, put them on the desktop for now along with Extra folder and edited org.chameleon.Boot.plist inside of it along with usual contents like DSDT. The last bit will all be done in terminal. For demonstration purposes, I assume my first hard drive of the array is rdisk1 and the 2nd is rdisk2, substitute with your own BSD drive number obtained via diskutil above. cd to desktop: cd ~/Desktop enter root sudo -s install boot0 to MBR, we don't need to worry about partition # here, just the disk #: fdisk -f boot0 -u -y /dev/rdisk1 fdisk -f boot0 -u -y /dev/rdisk2 Then to install boot1h dd if=boot1h of=/dev/rdisk1s3 dd if=boot1h of=/dev/rdisk2s3 then need to mount one of the helper partitions to copy our remaining files over, and once done, unmount it then repeat the process for the 2nd helper partition: diskutil mount disk1s3 cp boot /Volumes/Boot\ OS\ X/ cp -R Extra /Volumes/Boot\ OS\ X/ diskutil unmount disk1s3 Be sure to unmount the Boot OS X partition before mounting the next one, because if 2 are mounted at the same time, the system will rename one of them to Boot OS X 1, possibly causing some problems for you. Repeat for other partition, will condense into short version cause this post is getting long: diskutil mount disk2s3 cp boot /Volumes/Boot\ OS\ X/ cp -R Extra /Volumes/Boot\ OS\ X/ diskutil unmount disk2s3 Here's what mounted Boot OSX partition should look like: Now you can have either drive listed as your boot device in BIOS, and pick either Boot OSX partition from Chameleon's boot menu, and your RAID will boot either way. That's it, if done right you should have working, bootable RAID-0. Optimizing: Picking which controllers to put your drives on will largely depend on your hardware. Keep in mind, since they are both read and written to at the same time, your bandwidth will be limited to that of your slowest connection, but since they are both reading and writing at the same time, the combined load on that bus can also be a factor. So as an example, I have Intel SATA 2, Marvell SATA 3 on-board and PCIe 2.0 x1 ASMedia SATA 3 card. With a single SSD hooked up, the ASMedia is the faster of the three, but when using both drives of the array on that same ASMedia card, there is almost no increase in performance, because a single SATA 3 connection running full tilt is enough to use all the bandwidth available via the x1 PCIe 2.0 connection. The Marvell, which normally falls in between the ASMedia and the Intel, suffers from similar over saturation with both drives, so putting both on the Intel SATA 2 control is actually faster due to it's overall bandwidth. What ended up being the best for me, was to split that bandwidth by putting 1 drive on the ASMedia controller and the second on the Marvell Controller, allowing both to run at the full speed of the slowest link, so both are running at what would be the Marvell's max speed with just one drive. The difference in read speeds is pretty dramatic, where both drives together on any of the controller's would max at around 500mb/s, this combination will max out at 800mb/s and has added benefit of leaving Intel controller available for other uses like a possible Windows Hardware RAID. iCloud, iMessage or other Apple server login errors: This should not be needed as it was fixed in Chameleon 2+ years ago, but I have seen a few instances in ML where it's been required and even a bit more common on a RAID-0 setup. Chances are if your having trouble logging into iCloud, the Appstore or any other apple run services, this is not the reason why and following the usual how-to for iCloud fix will be what is required, but if everything else has been set up perfectly and you are still having issues logging into iCloud, follow the pictures and see if it helps Open IORegistryExplorer Copy to Text Edit then get your ethernet MAC address Changes will need to be applied to org.chameleon.Boot.plist in both your Boot OS X partitions Now after rebooting, if done right you should now see this disclaimer #2: Everything in this guide, I read somewhere, sometime, someplace at some point and did not invent any of it myself. Most the words used can also be found in any English dictionary, with only a few exceptions patent pending such as the word "the", which I will be registering as trademarked once the paperwork arrives, until which time I will permit it's use as open source under the GNU general public license.
  5. Hola, tengo una duda: Mi placa tiene 2 puertos SATA blancos con especificación Sata 600. Tengo 3 discos que tendria que conectar, 2 para hacer un Raid 0 y un SSD con el sistema. La duda es si conecto el Raid 0 a dos puertos de 300 y el SSD al de 600 o lo monto al reves. Actualmente tengo dos discos de 250Gb a los SATA normales en Raid 0 y el SSD al de 600, pero he pedido dos discos de 2T a 600 y ahora me faltaria un conector. Algún entendido que pueda recomendarme se agradece. Un saludo.-
  6. Hey there guys, i got this LSI 3ware (Escalade) 9550SX(U)-8LP Controller here and i thought about tinkering around with it. Because of the specs of the mainboard i am using, i am not yet sure if i can switch to a different controller card, also hey, i got this one here already... it'd be just awesome to be able to use it. For the moment i have the system running halfway smoothly and it will be still some days until my next task (the gfx card, also not that easy on this mobo...) is up, so i was wondering... Has anyone tried this particular model? Any chance on info, or that someone got it to work yet? I've seen some threads regarding various alike cards, but then when following their steps it doesn't seem to be fruitful. What i have done so far is to try to get it to work was to look through various posts indicating that installing the codeset 9.5.3 in addition with the AMCC3ware9000.kext (or better said the AMCC3ware900064.kext) would do the trick as it is said that most of the ids are alike. Oh, the id for this particular card is 13c1:1003 I'm not quite keen with all this to be honest, but then i tried out osx86 every now and then for some time and achieved most of my selfset goals, but this time it might be a little over my head... So uhm, thanks for your input!
  7. jimmyco2008

    AppleAHCIPort.kext (for RAID)

    Version 1.0 (only version)


    This modified AppleAHCIPort.kext makes it possible to Hackintosh laptops and desktops that are locked in RAID SATA mode. I've personally only tested it with the HP m6-1045dx laptop, which uses a classic locked BIOS and HM77 "Panther Point" chipset paired with the Ivy Bridge i5. Based on the nature of the kext, I would say this can work with other computers, just give it a go! ------------------------ Why do I need this kext? If your SATA-connected hard drive isn't being detected by the OS X installer and you have no control over SATA mode in BIOS/EFI (ie, IDE, RAID, AHCI modes). Common with the latest (2012 at least and newer) HP laptops, probably the trend for many OEMs these days. ------------------------ Install via Kext Wizard, probably a good idea to rebuild cache/repair permissions (also via Kext Wizard) while you're at it! Thanks to eep357 for making this file!
  8. I've built a hackintosh running Mountain Lion Server and installed a HighPoint RAID 640L card in it. I've also added 4 x 4TB ST4000DM000 hard drives. All had been running fine for about a year, but now I've got RAID errors happening: B 0 W 08/12/15 08:56:25 Array 'RAID_5_0' rebuilding failed. B 0 I 08/12/15 10:54:45 Array 'RAID_5_0' rebuilding started. B 0 E 08/12/15 18:50:05 Disk 'ST4000DM000-1F2168-Z301RJK9' at Controller1-Channel3 failed. B 0 W 08/12/15 18:50:05 Array 'RAID_5_0' rebuilding failed. B 0 E 08/28/15 16:06:43 Device 'ST4000DM000-1F2168-Z302EG2Y' at Controller1-Channel1 SMART test result: FAILED! B 0 E 08/28/15 16:06:43 Device 'ST4000DM000-1F2168-Z301RJ27' at Controller1-Channel2 SMART test result: FAILED! B 0 E 08/28/15 16:06:43 Device 'ST4000DM000-1F2168-Z301RJK9' at Controller1-Channel3 SMART test result: FAILED! B 0 E 08/28/15 16:06:43 Device 'ST4000DM000-1F2168-Z302EFL6' at Controller1-Channel4 SMART test result: FAILED! More: http://pastebin.com/cGkp9Vg8 Obviously there is a lot of data on the drives and ideally I should just pull that stuff off now, but what I am concerned about is if this is just a false positive, because I've scanned the drives for SMART errors on another machine and it's not found anything wrong. Could this be a false warning? At this point I'd appreciate some advice - in the mean time I'll be pulling data off of it like there's no tomorrow
  9. I'm looking at installing a PCIe RAID controller to give myself h/w RAID in my Mac Pro. I cannot use the existing sata bay wiring as the SFF-8087 connector wont reach the PCIe card. Not a problem as I can use a separate SFF-8087 to SATA breakout cable. The issue lies with the power. The OEM wiring has the power and data into a single connector, I have not been able to identify or find a cable that would work as a standalone. It looks like a standard ATX P4 power plug on the motherboard that breaks out into 4x sata power. Any suggestions? thanks!