Take the 2-minute tour ×
Ask Different is a question and answer site for power users of Apple hardware and software. It's 100% free, no registration required.

Recently I have decided that since Mac does such a nice job for indexing the files, I will store many files on the Mac, so I bought a 6TB Thunderbolt external drive which is in RAID 0 Strip mode, and another 2 external drives that are 4TB each, and use them as the RAID 1 mirror mode.

The iMac is 1 year old, so it is still using USB 2.0, but the drive using Thunderbolt is fast.

However, if I just right click an image on a website and choose "Save Image As", now I have to wait 30 seconds for the drives to "wake up", before the "Save As" will pop out the window to let me click the "Save" button at all to save the file. Since some Mac can now boot up in 25 seconds, I need to wait a longer time than the boot up time just to save an image, which 99.99% of the time is by default just on the Mac's internal hard drive, under ~/Downloads.

Is there a way to improve this? I also turned off the "Put the hard drive to sleep when possible" in the System Preferences, but it is still doing the same thing. For example, if the "Save Image As" can let me choose the "Downloads" folder, and just to wake the other drives up when I do select to look into them.

One method I can think of is, write a shell script that will ls /Volumes/WD6TB and ls /Volumes/WD4TB (the drives' names), just to wake the drives up whenever I start using this iMac. Or else if there is a way to cause the screensaver to wake up the drives whenever there is a mouse move or keyboard action, wake the display (which it can do), and wake the hard drives, that will be a good solution too.

share|improve this question
    
Why not save the files to a folder your internal drive and write a script to write them to the external and delete them from the internal at the end of the day. –  Richard May 6 '13 at 10:20
1  
no, it is already intended to be saved to the internal drive. It is the window that lets you click "Save" to save the file that takes 30 seconds to become ready –  動靜能量 May 6 '13 at 11:20
    
Right, because the drive isn't mounted or it its mounted it's not spinning. If you save it to the mounted, running drive it will be immediate. –  Richard May 6 '13 at 13:08
1  
NO - the Save button is NOT READY for you to click on, NOT UNTIL 30 seconds later. –  動靜能量 May 7 '13 at 12:25

1 Answer 1

The save button is checking all mounted drives, and will spin them up.

Your only way I can think of to do this is to prepare a couple of scripts.

See the man page for diskutil. If the mount point (diskname) is BigFatDisk

then to unmount the disk it would be something like

diskutil unmount BigFatDisk

Now to keep everything sync'd to BFD you would run a script now and then

diskutil mount BigFatDisk rsync flags local disk BFD diskutil unmount BigFatDisk

A second option is to replace the disks in the BFD enclosure with hybrid disks. These have an SSD chunk and a spinning rust chunk, and are ideally suited for this.

A third option is to let your disks spin whenever the machine is awake? The amount of power they use is small, and increasingly MTBF times are being given as X spinups, not X hours. A hard drive 2 years ago used 5-7 watts. I'm sure it's better now. So let's use 5. That works out to 40 kWhr per year, roughly. At 15 c per kWh that's 6 bucks/year. Seems to me that this is pretty cheap compared to the hassles you have now.

I have set my computer to turn the screens off after 20 minutes idle time, but never to turn off the CPU or spin the drives down.

share|improve this answer

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.