Slow Restore from Firewire 800 to Raid 0 SSD

Discussion in 'Mac mini' started by jmcgeejr, Aug 10, 2011.

  1. jmcgeejr macrumors 6502

    jmcgeejr

    Joined:
    Oct 7, 2010
    Location:
    Seattle, WA
    #1
    Anyone else having these issues? I am sitting on almost 2 hours for about 115GB restore (only at 45% right now), it seems to be stalling every once in a while I dont see activity on my external drive, which I have never had problems with before. I am using 2 Crucial C300 SSD's in Raid 0. I am doing a restore from Time Machine FYI. Cheers.
     
  2. MJL, Aug 10, 2011
    Last edited: Aug 10, 2011

    MJL macrumors 6502a

    Joined:
    Jun 25, 2011
    #2
    I have just put an Intel X25M G2 80 Gb into my 2010 Mac Mini (bought a few weeks before the release of the 2011 model) and because of the nature of my activities have been spending the larger part of the past three weeks experimenting with backups, restores and dual booting with Windows 7. (require OS X only 2 - 5% of the time).

    I've found issues with the SSD with Windows 7 build in backup / restore, with Paragon Partition Manager, with Winclone under Snow Leopard.

    I would not even dare to use CopyCatX on the SSD due to the way a SSD operates. (Am afraid I might brick the SSD with CopyCatX). In order to understand this remark you have to know how a SSD operates and why this is possible, in short: A SSD needs unused memory cells to operate so if you use some restore software that writes to every cell (as with CopyCatX) then these cells are not available. You - might - get away with it if you have over provisioned your drive sufficiently but I am not going to try this out, not confident enough about that it - might - work.

    I do not know enough about how Time Machine operates but it might be that it is as simple as that it does not like to restore to something that operates in Raid 0.

    I have difficulty understanding why you want to use RAID 0, with two SSD in there I would have thought RAID 1 is more usefull or otherwise using it as just two simple SSD's with one the OS and the other the data to speed up things?

    PS Under windows at least when using SSD in RAID then the TRIM commands do not work. Don't know under OS X. (hence my remark as using them as two seperate disks)

    edit: Giving it some more thought: With Raid 0 you are relying on the internal Garbage Collection of the SSD to free up cells, if you had lots of data on it and doing a restore then it will be slow depending on how the Crucial does the emptying out of cells before writing to them. IF you insist on using the RAID 0 (which I now strongly advise against, far better to split OS and data disks) then before doing the restore you have to break the RAID, then do an erase, reinstating RAID and then do the restore.

    Peace
     

Share This Page