Change Thunderbolt Disk Sleep Time

Hi, so I have a new iMac with a LaCie d2 Thunderbolt being used with Time Machine. Since the LaCie is a little loud (in comparison with the super silent iMac), I want OS X to put it into standby mode sooner than it already does.
I know I should be able to just open terminal and use "pmset -a disksleep" to change this time (default 10, I'd probably make it 5), but to my understanding this is for all hard drives (external and internal). Is there anyway to specify this command to only external disks or, better yet, only time machine disks?
Finally, if there isn't a way to only set this for the external drive, would it cause any problem to just set disksleep to 5? I'd prefer I could just get my external to immediatly sleep once the backup is done, so maybe I could spend some time to write a script to do that, but I wouldn't know what to do.

The OSX controls the HDD. In System Preferences>Energy Saver you do have this option:
Ciao.

Similar Messages

I want to change the disk sleep time

I want to change the disk sleep time

The OSX controls the HDD. In System Preferences>Energy Saver you do have this option:
Ciao.

How to change DVD player sleep time

I have some DVDs that I like to repeatedly play video clips from. However, I'm having a problem with the DVD player going to sleep before the clip finishes, resulting in a very noticeable delay and message "waking up DVD player" when the time comes to repeat the clip. How do I change the DVD sleep parameter(s) to prevent this annoying behavior?

Anyone? Anyone?

Disk Sleep times not accurate

Not wanting my external drives to spin down every ten minutes (actually eight minutes), I reset the the disk sleep interval with the sudo pmset command or with TextWrangler. Oddly enough, I found that this works but is not accurate. Setting the time for 30 minutes would allow my disks to spin down after only 23 minutes. At a 60 minute setting, they would spin down in about 44 minutes. They seem to spin down anywhere from 70% to 80% of the value set. Has anyone else experienced this? Anyone know why?

Not wanting my external drives to spin down every ten minutes (actually eight minutes), I reset the the disk sleep interval with the sudo pmset command or with TextWrangler. Oddly enough, I found that this works but is not accurate. Setting the time for 30 minutes would allow my disks to spin down after only 23 minutes. At a 60 minute setting, they would spin down in about 44 minutes. They seem to spin down anywhere from 70% to 80% of the value set. Has anyone else experienced this? Anyone know why?

Problem changing startup disk one time

My main OS is 10.8.5 but have second hard drive with OS 10.6.8 on it for use with older applications. I've never had trouble rebooting in 10.6.8 when necessary by holding down the option key. Suddenly it doesn't work; the computer just hangs with a gray screen. Nothing has really changed in my setup in the few weeks since I've last rebooted in 10.6.8. I've verified both startup disks and repaired permissions on both.
Alfred
Mac Pro 2 x 2.4 GHz 6-core Intel Xeon
12GB RAM

Yes to both questions. Since posting my question, I tried resetting the PRAM (in 10.8.5) and the result was that the computer wouldn't start in either OS; it would just get to the gray screen and hang. I found an Apple document that suggested remedies. Starting while holding down command-R or shift didn't work. Then I unplugged all my peripherals and the computer started normally. I followed the procedure of reconnecting one peripheral at a time (rebooting each time) and didn't find the culprit. I then went to the next procedure: adding them one at a time (again rebooting each time) and this didn't find the problem either. Now I can reboot normally in either my preferred 10.8.5 or the alternative 10.6.8, but I'm a little uneasy since I don't know what the problem was and never really fixed or changed anything.

Changing backup disk after time machine restore

I recently had to get a new harddrive and used my time machine back up to restore all the data i had. Now however when i plug the time machine in to do another back up it starts a new "time machine backup disk" instead of just using the disk that it was using. Is there any way to manually set it to update this older backup disk?

Not at this point. If you had used Setup Assistant or Migration Assistant to restore your data, you would have been given that option. TM will still do a full copy of all your files either way. The main difference is that old snapshots from the previous backup will never be automatically deleted. You'll have to do that yourself, through the TM interface, if necessary.

Changed Hard Disk for Time Machine

I have a question, I've searched and can't find the answer (maybe I'm just not good at searching).
I ran out of room on my external HD for time machine backups, so I added another external HD and changed the time machine location to the new HD. I did not copy any backup files to the new HD, I figured that I'd just keep the old ones on the old HD and start from scratch.
I am using an old iMac G5 that has one (yes, one) USB2.0 port, the other USB ports are the old, slow ones. I have the new HD plugged into the USB2.0 port and the old HD plugged into one of the other ones.
Then I selected "back up now," and it's been backing up for more than 12 hours and it's only about 1/3 of the way done according to the progress report (37.4 GB of 96.9 GB).
Question -- does time machine automatically copy my old back up from the old HD to the new HD? That's the only thing that I can think of that would make this back up so slow. It shouldn't take 12 hours to back up 37 GB, right?

Thanks. I think I need to just wait until it's done and then check things out. I let it run all day while I was at work, and it's another 1/3 of the way to the end. I don't want to stop it and then find out that I just need to let it run its course.
Here is the backup log from the time machine widget:
Backing up to: /Volumes/Backup/Backups.backupdb
2010-06-22 18:33:57.446 FindSystemFiles[1245:713] Querying receipt database for system packages
2010-06-22 18:34:02.962 FindSystemFiles[1245:713] Using system path cache.
2010-06-22 18:34:03.335 FindSystemFiles[1250:713] Querying receipt database for system packages
2010-06-22 18:34:04.293 FindSystemFiles[1250:713] Using system path cache.
Event store UUIDs don't match for volume: Storage Central
Event store UUIDs don't match for volume: Alternate Storage
No pre-backup thinning needed: 116.45 GB requested (including padding), 376.49 GB available
Copied 11 files (0 bytes) from volume Storage Central.
Event store UUIDs don't match for volume: Storage Central

Adjusting Hard Disk Sleep?

Is there a way to adjust the default time when I've enabled "put the hard disk(s) to sleep when possible"? The default time seems very short to me, and would love to extend it to a half hour or so before they go to sleep.
Thanks!

yes, it's possible. install TextWrangler and open the file /library/preferences/systemconfiguration/com.apple.PowerManagement.plist in textWrangler. change the entry for Disk Sleep Timer from 10 to 30 and save. you'll have to provide your admin password. then restart and the disk sleep timer will be set to 30 minutes. you can adjust that number to whatever you want of course.

Setting Disk Sleep Timers problems with FCP4.5?

Still experiencing trouble when Printing-To-Tape projects that are over 30 min in length. It usually stops at around 26 minutes. I head something about Disk Sleep Timers. I checked my Mac under About This Mac>More Info>Power...I found that my Disk Sleep Timer is set to 10 minutes and System Sleep Timer is set to 180 minutes. Could this be the problem? Should I reset my Disk Sleep Timer to a longer time? If so, how can I do this?
Also, other mentioned something about Journaling on the disks? What is that? Should they be on or off? How can I check. Please help.

Luis,
You will want to set your sleep to never, screen savers to None, and disk spindown to never.
This is a way to set the disks to never:
In Terminal type:
sudo pmset spindown x
then type your pass word
x=the number of minutes that you want till your drive spins down.
0 is never
More info on using pmset here:
http://developer.apple.com/documentation/Darwin/Reference/ManPages/man1/pmset.1. html
And I found this here
http://www.thexlab.com/faqs/sbbod.html
Do a command f and search for "pmset" that is where i first found this.
Note that this is a more 'controlled' way of Putting the hard disk to sleep than possible in
system preferences>energy saver>sleep>Put the hard disk to sleep when possible
In that situation, checked means x=10 and unchecked means, not 0 but 180 minutes.
Also, there are some utilities with a graphical interface that will do this as well.
Good luck.
x

Is it possible to boot or Time Machine restore from an external Thunderbolt disk drive?

(There are several questions - search for "?".)
I purchased a Seagate Backup Plus for Mac Desktop Drive 3 TByte with default USB 3.0 interface, and also acquired the Seagate Thunderbolt Adapter for Backup Plus Desktop Drives and Thunderbolt cable.
I do a redundant backup to the Seagate Drive using both Carbon Copy Cloner (nightly) and Time Machine (hourly) using its Thunderbolt adapter. BTW: One never knows when Time Machine will choke - see discussion titled, "UPDATED: Serious Time Machine bug on Mountain Lion", which I had; Rest In Peace Pondini (James Lewis Pond).
Booting from the external Seagate Backup Plus via Thunderbolt inteface from System Preferences -> Startup Disk:
I select the Time Machine OS X, 10.8.5 Startup Disk (Thunderbolt attached drive), click Restart, confirm my choice, the computer reboots, however, it reboots from the internal Macintosh HD OS X, 10.8.5, NOT the selected external Thunderbolt drive. The SSD drive was used as the Startup Drive, not the selected external Time Machine volume as indicated by the display free disk space command (df(1)) and seeing that the Macintosh HD OS X, 10.8.5 volume is mounted as root. That is very deceptive in that both the internal and external drives will appear in the same manner from a GUI point of view! OS X doesn't even inform me that it did not boot off the selected volume. This is the first half of the problem, that is, Is it possible to boot from an external Thunderbolt disk drive? In my case, the answer is deceptively No. Can anybody else boot off a Thuderbolt attached disk drive? Note that if I remove the Thunderbolt adapter, and attach the drive via its USB 3.0 cable, the MBP boots off the external Seagate Backup Plus just fine, as is expected.
Booting from the external Seagate Backup Plus via Thunderbolt inteface from boot-time "Option - Select startup disk" method:
When I restart the MBP using the startup Option key to select the startup volume, the externally connected Seagate drive ONLY SHOWS UP if it is attached with the USB 3.0 cable, not when it is attached with via the Thunderbolt interface. Can anyone else boot off a Thunderbolt drive with the startup Option key sequence? At least the MBP doesn't deceive me in this case - I know right away that the external Thunderbolt drive is not an option when connected as such.
Time Machine restore from the external Seagate Backup plus via Thunderbolt interface from the "command-R - Recovery Parition" method:
After booting from the recovery partition, I attempt to perform a Time Machine restore from the Thunderbolt connected Seagate Backup drive. When Time Machine attempts to present me with a viable backup Time Machine volume, the external Thunderbolt drive is never offered as an option. So I switch the Time Machine volume to use its USB 3.0 interface, and then Time Machine displays that drive as an option, and the MBP proceeds with the restoration as expected. The interesting thing to note is that while booted in the recovery partition via the Thuderbolt cable, the MBP Disk Utility may be selected, and the Thunderbolt attached drive may be operated on just fine. Can anybody else restore their MBP using Time Machine and the Recovery Partition via the Thunderbolt interface?
This is also a big problem for me in that I am forced to restore my MBP via Carbon Copy Cloner using the USB 3.0 interface, because I cannot even boot off that volume's Thunderbolt interface. Of course, the option may be that I could use yet another eternal USB 3.0 drive, boot from it, and then use Carbon Copy Cloner to restore the Macintosh HD via the aforementioned drive connected by a Thunderbolt cable, but that is less than ideal and not elegant, so I'm not going there.
Another side issue is that the commercially available program, TechTool Pro 7's eDrive, which I installed on the Time Machine volume, will not boot off that eDrive as advertised, but I won't got through those steps here, because that would be beyond the scope of this issue, however, I must say, It does not work either when the Time Machine volume is connected via the Thunderbolt interface, but works just fine when connected via the USB 3.0 interface.

If this helps anybody else make a decision about whether to consider Apple because of Apple's superior customer service:
Apple sells this entire line of drives right in their store, from 1TB to 4TB. I spent 1 and 1/2 hours, yesterday, confirming that the 3TB model IS NOT 100% Thunderbolt compliant. A MBP cannot boot, nor can it Time Machine restore from this drive, though EVERYTHING about the drive is normal.
Apple's South Coast Plaza store management had at least two responses to me personally about how to proceed:
1. Buy a different drive from another drive manufacturer, and to attempt to return the drive to COSTCO. A lead genius suggested going with GTech drives, for instance.
2. Wait for Seagate to fix their problem.
I told Apple management in the store that the drive is advertised as Mac Compatible (see picture) and that it is advertised as being a Thunderbolt drive (see picture). I pressed management that my purchasing decsion to get the best possible MBP Retina was based on the availablity of Inexpensive Devises (raID), and that not having this complete compatibility is a show-stopper for my needs, and that I wanted a refund. Their response? They needed to talk with "Merchendising" to see if they are on or off the hook for these kind of 3rd party assertions, and would get back to me.
I am not holding my breath.
Note: I do not hold this against the Geniuses that helped me, nor against the management I've dealt with, nor the upper level engineers that I've corresponded with through Apple Care - their problem solving skills were helpful - although I could have arrived at similar conclusions given enough $$$. (For instance, try a Lacie TB drive and see if that works - we did, and it did not work. Or, we have a different TB cable and a different TB adapter, let's try those - we did, and it did not work.) I blame myself for not doing enough homework before going with Apple's solutions.

Where did the sleep timer go in IOS 5? It's been changed to "stop playing"

When previously using the sleep timer, I would set a time and then choose for the device to "sleep" at the end of the time. Now the choice has been changed to "Stop Playing." This is a huge problem because it does not sleep the device; it only stops the music from playing. Because the music app continues to run, battery life is profoundly shortened. I verified this at the Genius Bar when I noticed my battery life dropped from several hours per charge to about 1.5 hours. Can a sleep timer be used in some other manner now?

What was the answer when you asked at the Genius Bar?

I am changing to a larger hard drive on my Mac. Can I copy the Aperture library from my backup disk running Time Machine without loosing anything?

I am installing a larger harddrive on my Mac. Can I copy the Aperture library from my backup disk running Time Machine without loosing anything? I am getting help migrating everything else on to the new harddrive, but since copying the 350Gb Aperture library takes a lot of time, I am planning to do that part myself.

I found the following information on Time Machine help about restoring Aperture library from TM
Restoring Your Aperture System
If you buy a new computer or use another system at a different location and want access to the Aperture library, you can install Aperture and then transfer the library from your vault (on your backup disk) to the other computer. If you experience equipment failure or other unexpected events, such as fire or weather-related damage to your equipment, you can easily restore the entire library to your new computer from a backup disk.
HideTo restore the entire library from an external backup disk
Restoring Your Aperture System
If you buy a new computer or use another system at a different location and want access to the Aperture library, you can install Aperture and then transfer the library from your vault (on your backup disk) to the other computer. If you experience equipment failure or other unexpected events, such as fire or weather-related damage to your equipment, you can easily restore the entire library to your new computer from a backup disk.
HideTo restore the entire library from an external backup disk
If you buy a new computer or use another system at a different location and want access to the Aperture library, you can install Aperture and then transfer the library from your vault (on your backup disk) to the other computer. If you experience equipment failure or other unexpected events, such as fire or weather-related damage to your equipment, you can easily restore the entire library to your new computer from a backup disk.
HideTo restore the entire library from an external backup disk
Connect the hard disk drive that contains the most up-to-date vault to your computer and open Aperture.
Choose File > Vault > Restore Library.The Restore Library dialog appears.
Choose the vault you want to use to restore your library from the Source Vault pop-up menu.If the vault doesn’t appear in the Source Vault pop-up menu, choose Select Source Vault from the Source Vault pop-up menu, navigate to the vaults location in the Select Source Vault dialog, then click Select.
Click Restore, then click Restore again.

Mac Sleep Timer (through 'Energy Saver' in System Preferences) won't work

Hello,
I have a MacBook (13-inch, Mid 2009) running Mac OS X Snow Leopard 10.6.3,
and it has been installed with the latest software updates possible.
(The latest update is the 'Security Update 2010-003')
Previously I was using Mac OS X Leopard 10.5 on my MacBook,
and I can vaguely remember the timed computer sleep through Energy Saver would work.
That is, when the counter's time matches the amount of time I specified (e.g. 10 minutes), the computer enters sleep mode and displays a pulsing power light.
After upgrading to Snow Leopard I can barely remember the scheduled computer sleep will work as I don't really notice how it sleeps / I will shut down my MacBook before I go to bed.
==========
However, last night I was really tired and slept in front of my MacBook unconsciously.
When I woke up, I found that my MacBook didn't display a pulsing power light but a continuously-growing power light.
I tapped the trackpad and the display turned on, so I knew that my MacBook didn't go to sleep a whole night.
*What that means is that the Sleep Timer (through 'Energy Saver' in System Preferences) won't work.*
But the timed display sleep DOES work.
==========
After spending a whole day Googling,
I found that there are plenty of people suffering the same problem as me, although their Macs and OSs vary.
I also found an official support page from Apple concerning the related issue:
Mac OS X: Why your Mac might not sleep or stay in sleep mode
http://support.apple.com/kb/HT1776
I tried the following methods but still can't resolve the problem:
_- boot my MacBook in safe mode_
_- use the 'Disk Utility' to repair Disk Permissions through booting my MacBook from the Mac OS X Snow Leopard Installation DVD_
_- reset NVRAM (Intel-based) (as PRAM is used by PowerPC-based Macs)_
_- reset SMC (System Management Controller)_
NONE of the above-mentioned methods can resolve the problem.
Althought I am sure that the Spotlight isn't indexing the hard drive, and I just start my computer and do nothing and wait for the scheduled computer sleep, the scheduled computer sleep just won't work.
In the other Mac forum, I saw someone suggest installing an application called PleaseSleep:
http://www.dragonone.com/products/macosx/pleasesleep/
It works.
But I really want to find out what caused this problem as this is a function shipped with Mac which is expected to work normally.
What's more, Apple is claiming to be a green Apple, right?
==========
Here's the log taken from 'Console':
- Sleep by closing the lid of my MacBook:
Apr 18 13:21:05 Michael-Leungs-MacBook loginwindow[25]: loginwindow SleepWakeCallback WILL sleep
Apr 18 13:21:05 Michael-Leungs-MacBook PleaseSleep[288]: Sleep notification received from the system
Apr 18 13:21:07 Michael-Leungs-MacBook configd[37]: network configuration changed.
Apr 18 13:23:21 Michael-Leungs-MacBook loginwindow[25]: loginwindow SleepWakeCallback will power on, Currenttime:4/18/2010 1:23:21.028 PM - Waketime:4/18/2010 1:23:19.410 PM = Deltatime:1.618421972
Apr 18 13:23:21 Michael-Leungs-MacBook loginwindow[25]: handleUnlockResult, Currenttime:4/18/2010 1:23:21.579 PM - Waketime:4/18/2010 1:23:19.410 PM = Deltatime:2.169138968
Apr 18 13:23:23 Michael-Leungs-MacBook configd[37]: Sleep: Success - AC 98 - Clamshell Sleep
Apr 18 13:23:23 Michael-Leungs-MacBook configd[37]: Wake: Success - AC 98 - EC LID0
Apr 18 13:23:23 Michael-Leungs-MacBook configd[37]: Hibernate Statistics
Apr 18 13:23:23 Michael-Leungs-MacBook PleaseSleep[288]: Wake notification received from the system
- Sleep by manually clicking the Apple logo in the upper left corner of the screen -> 'Sleep':
Apr 18 13:31:46 Michael-Leungs-MacBook loginwindow[25]: loginwindow SleepWakeCallback WILL sleep
Apr 18 13:31:46 Michael-Leungs-MacBook PleaseSleep[288]: Sleep notification received from the system
Apr 18 13:31:49 Michael-Leungs-MacBook configd[37]: network configuration changed.
Apr 18 13:32:04 Michael-Leungs-MacBook loginwindow[25]: loginwindow SleepWakeCallback will power on, Currenttime:4/18/2010 1:32:04.033 PM - Waketime:4/18/2010 1:32:02.720 PM = Deltatime:1.313067079
Apr 18 13:32:04 Michael-Leungs-MacBook loginwindow[25]: handleUnlockResult, Currenttime:4/18/2010 1:32:04.589 PM - Waketime:4/18/2010 1:32:02.720 PM = Deltatime:1.869303048
Apr 18 13:32:06 Michael-Leungs-MacBook configd[37]: Sleep: Success - AC 98 - Software Sleep
Apr 18 13:32:06 Michael-Leungs-MacBook configd[37]: Wake: Success - AC 98 - OHC1
Apr 18 13:32:06 Michael-Leungs-MacBook configd[37]: Hibernate Statistics
Apr 18 13:32:06 Michael-Leungs-MacBook PleaseSleep[288]: Wake notification received from the system
- Sleep by manually pressing control + eject, and the press 'Sleep':
Apr 18 13:34:17 Michael-Leungs-MacBook loginwindow[25]: loginwindow SleepWakeCallback WILL sleep
Apr 18 13:34:17 Michael-Leungs-MacBook PleaseSleep[288]: Sleep notification received from the system
Apr 18 13:34:46 Michael-Leungs-MacBook loginwindow[25]: loginwindow SleepWakeCallback will power on, Currenttime:4/18/2010 1:34:46.080 PM - Waketime:4/18/2010 1:34:44.720 PM = Deltatime:1.360466003
Apr 18 13:34:46 Michael-Leungs-MacBook loginwindow[25]: handleUnlockResult, Currenttime:4/18/2010 1:34:46.564 PM - Waketime:4/18/2010 1:34:44.720 PM = Deltatime:1.844347000
Apr 18 13:34:46 Michael-Leungs-MacBook configd[37]: PMConnection AirPort configd plug-in com.apple.powermanagement.applicationresponse.slowresponse 566 ms
Apr 18 13:34:46 Michael-Leungs-MacBook configd[37]: bootpsessiontransmit: bpf_write(en0) failed: Network is down (50)
Apr 18 13:34:46 Michael-Leungs-MacBook configd[37]: DHCP en0: INIT transmit failed
Apr 18 13:34:46 Michael-Leungs-MacBook configd[37]: PMConnection IPConfiguration com.apple.powermanagement.applicationresponse.slowresponse 567 ms
Apr 18 13:34:46 Michael-Leungs-MacBook configd[37]: network configuration changed.
Apr 18 13:34:48 Michael-Leungs-MacBook configd[37]: Sleep: Success - AC 98 - Software Sleep
Apr 18 13:34:48 Michael-Leungs-MacBook configd[37]: Wake: Success - AC 98 - OHC1
Apr 18 13:34:48 Michael-Leungs-MacBook configd[37]: Hibernate Statistics
Apr 18 13:34:48 Michael-Leungs-MacBook PleaseSleep[288]: Wake notification received from the system
- Sleep by _turning on the application called 'PleaseSleep' based on the settings from 'Energy Saver'_:
Apr 18 13:37:22 Michael-Leungs-MacBook PleaseSleep[288]: Application is enabled
Apr 18 13:37:29 Michael-Leungs-MacBook System Preferences[1136]: * AGCAttach() failed
Apr 18 13:37:31 Michael-Leungs-MacBook [0x0-0x58058].com.apple.systempreferences[1136]: Couldn't find any matches.
Apr 18 13:38:23 Michael-Leungs-MacBook PleaseSleep[288]: Checking sleep conditions...
Apr 18 13:38:23 Michael-Leungs-MacBook PleaseSleep[288]: Going to sleep...
Apr 18 13:38:23 Michael-Leungs-MacBook loginwindow[25]: loginwindow SleepWakeCallback WILL sleep
Apr 18 13:38:23 Michael-Leungs-MacBook PleaseSleep[288]: Sleep notification received from the system
Apr 18 13:38:56 Michael-Leungs-MacBook loginwindow[25]: loginwindow SleepWakeCallback will power on, Currenttime:4/18/2010 1:38:56.042 PM - Waketime:4/18/2010 1:38:54.720 PM = Deltatime:1.321902931
Apr 18 13:38:56 Michael-Leungs-MacBook loginwindow[25]: handleUnlockResult, Currenttime:4/18/2010 1:38:56.571 PM - Waketime:4/18/2010 1:38:54.720 PM = Deltatime:1.850627959
Apr 18 13:38:56 Michael-Leungs-MacBook configd[37]: PMConnection AirPort configd plug-in com.apple.powermanagement.applicationresponse.slowresponse 707 ms
Apr 18 13:38:56 Michael-Leungs-MacBook configd[37]: bootpsessiontransmit: bpf_write(en0) failed: Network is down (50)
Apr 18 13:38:56 Michael-Leungs-MacBook configd[37]: DHCP en0: INIT transmit failed
Apr 18 13:38:56 Michael-Leungs-MacBook configd[37]: PMConnection IPConfiguration com.apple.powermanagement.applicationresponse.slowresponse 708 ms
Apr 18 13:38:56 Michael-Leungs-MacBook configd[37]: network configuration changed.
Apr 18 13:38:58 Michael-Leungs-MacBook configd[37]: Sleep: Success - AC 98 - Software Sleep
Apr 18 13:38:58 Michael-Leungs-MacBook configd[37]: Wake: Success - AC 98 - OHC1
Apr 18 13:38:58 Michael-Leungs-MacBook configd[37]: Hibernate Statistics
Apr 18 13:38:58 Michael-Leungs-MacBook PleaseSleep[288]: Wake notification received from the system
- If I disable 'PleaseSleep' and only depend on the non-working 'Energy Saver', nothing happens.
==========
Looking forward to your replies! Thanks in advance!

Found this discussion by googling "com.apple.systempreferencescouldn't find any matches"...
One month ago I bought a brand new Macbook Pro 13", and after a couple of weeks I realized it wasn't sleeping on its own when it should, per the system preferences. (I did sleep when I chose "Sleep" in the menus or closed it... It just wouldn't sleep on its own, while open.) What was extra frustrating was that it was intermittent... It would sleep on its own maybe 1/3 of the time, but other times it would NEVER go to sleep. I deleted PowerManagement.plist, reset the SMC, etc... No luck.
I took it to the "geniuses" at the Apple Store, and the guy took all of five minutes trying to diagnose the problem. When my MBP wouldn't sleep on its own, he promptly replaced it with a new one. That was nice, but I actually would have preferred that he diagnosed and fixed it. (I think the store was so swamped with people coming in for service that day that they were doing anything they could to close cases and get customers out of there ASAP.)
Now, sitting here with my 48-hour-old MBP, I still have the problem. The other one was so new that I had barely put anything on it yet. The only applications I had put on it were MS Office for Mac 2011, Firefox, Chrome, and Adobe Flash Player. I've put Office and Flash Player on this one, but not yet Firefox or Chrome. That's it. No other customization or fancy business.
I looked into the Console just now, and I see the "Couldn'tfind any matches" entry popping up again and again. The last three seemed to pop upright around the time when my MBP should have gone to sleep on its own, but not down to the second, so it's hard to definitively point at that and say it's it for sure.
They need to fix this!!

Trouble with LaCie disk and time machine

HI everyone,
I've been having trouble with using time machine to back-up to my 1 TB LaCie drive (purchased 5/12, unfornuately I was dumb and didn't register the drive and no longer have the box with the serial number and there is no serial number on my drive. The only problem I had up until the end of August was that every so often the LaCie drive (using my FW 800 port) would unmount after waking up from sleep.
The end of August the drive unmounted for no reason while I was on the computer doing a task. Could not get the LaCie drive remounted (rebooting, etc. etc.) To make a long story short, ended up calling apple care who took me through resetting my SMC and PRAM to no avail. Was booted to higher level of support who walked me through trying to repair my drive using the disk utiltiy. When that didn't work, she walked me through erasing and reformatting the LaCie drive and starting a new time machine back-up. Every thing ok until about ten days ago.
Last week, when I woke my iMac up from sleep, I got an error saying that the disk was not ejected properly and I could not mount the drive. Restarting did nothing, the disk did not mount. Shutting down and rebooting seemed to solve the problem and the disk was mounted. Every so often I've had the problem with the disk unmounting after waking up from sleep before. So, I changed my energy sleep preferences. At the end of the day when I am done, I'd unmount the LaCie drive before putting the Mac to sleep using the apple menu.
Today I came in to start my day, plugged the drive in and it would not mount. Tried rebooting nothing. Went into the disk utility, at first the LaCie drive passed the disk verify (6:26:25 and 6:26:38). Then I went into repair disk on the indented drive at 6:27:13, I wasn't sure what it is was doing, thinking that it had hung, I stopped the repair at 6:27:24. Exited disk utility, and the LaCie drive mounted. But I was getting a read only error when I tried to back-up using time machine. So, I went back into disk utility at 6:27:35, when I verified the disk (indented disk), I got an error saying the disk need to be repaired. After several minutes the disk could not be repaired. So, I erased and reformatted the drive. Ran a time machine back-up and it seemed to back-up everything on my hard drive. Just ran another verify disk and it passed.
Is the drive failing? Have some other back-ups of my documents, my address book, iCal and am going to make a backup of some of my pref files and important e-mail files and am going to do some more back-ups after I am done.
Have reached out to the women at apple care whom I talked to last August, but don't expect to hear back from her for at least 24 hours.
Here is my disk utility log
2013-11-07 06:26:25 -0500: Verifying partition map for “LaCie”
2013-11-07 06:26:25 -0500: Starting verification tool:
2013-11-07 06:26:25 -0500: Checking prerequisites
2013-11-07 06:26:25 -0500: Checking the partition list
2013-11-07 06:26:25 -0500: Checking for an EFI system partition
2013-11-07 06:26:25 -0500: Checking the EFI system partition’s size
2013-11-07 06:26:25 -0500: Checking the EFI system partition’s file system
2013-11-07 06:26:25 -0500: Checking all HFS data partition loader spaces
2013-11-07 06:26:25 -0500: Checking Core Storage Physical Volume partitions
2013-11-07 06:26:25 -0500: The partition map appears to be OK
2013-11-07 06:26:25 -0500:
2013-11-07 06:26:25 -0500:
2013-11-07 06:26:38 -0500: Verifying partition map for “LaCie”
2013-11-07 06:26:38 -0500: Starting verification tool:
2013-11-07 06:26:38 -0500: Checking prerequisites
2013-11-07 06:26:38 -0500: Checking the partition list
2013-11-07 06:26:38 -0500: Checking for an EFI system partition
2013-11-07 06:26:38 -0500: Checking the EFI system partition’s size
2013-11-07 06:26:38 -0500: Checking the EFI system partition’s file system
2013-11-07 06:26:38 -0500: Checking all HFS data partition loader spaces
2013-11-07 06:26:38 -0500: Checking Core Storage Physical Volume partitions
2013-11-07 06:26:38 -0500: The partition map appears to be OK
2013-11-07 06:26:38 -0500:
2013-11-07 06:26:38 -0500:
2013-11-07 06:27:13 -0500: Disk Utility started.
2013-11-07 06:27:21 -0500: Verifying and repairing partition map for “LaCie”
2013-11-07 06:27:21 -0500: Starting repair tool:
2013-11-07 06:27:21 -0500: Checking prerequisites
2013-11-07 06:27:21 -0500: Checking the partition list
2013-11-07 06:27:21 -0500: Checking for an EFI system partition
2013-11-07 06:27:21 -0500: Checking the EFI system partition’s size
2013-11-07 06:27:21 -0500: Checking the EFI system partition’s file system
2013-11-07 06:27:23 -0500: Checking all HFS data partition loader spaces
2013-11-07 06:27:24 -0500: Reviewing boot support loaders
2013-11-07 06:27:24 -0500: Checking Core Storage Physical Volume partitions
2013-11-07 06:27:24 -0500: Updating Windows boot.ini files as required
2013-11-07 06:27:24 -0500: The partition map appears to be OK
2013-11-07 06:27:24 -0500:
2013-11-07 06:27:24 -0500:
2013-11-07 06:27:35 -0500: Verifying volume “LaCie”
2013-11-07 06:27:35 -0500: Starting verification tool:
2013-11-07 06:27:35 -0500: Checking file system2013-11-07 06:27:35 -0500: Error: This disk needs to be repaired. Click Repair Disk.2013-11-07 06:27:35 -0500:
2013-11-07 06:27:35 -0500: Disk Utility stopped verifying “LaCie”: This disk needs to be repaired. Click Repair Disk.
2013-11-07 06:28:05 -0500:
2013-11-07 06:28:13 -0500: Verify and Repair volume “LaCie”
2013-11-07 06:28:13 -0500: Starting repair tool:
2013-11-07 06:28:13 -0500: Checking file system2013-11-07 06:28:13 -0500: Volume repair complete.2013-11-07 06:28:13 -0500: Updating boot support partitions for the volume as required.2013-11-07 06:35:05 -0500: Stopped by user
2013-11-07 06:44:56 -0500: Disk Utility started.
2013-11-07 06:45:20 -0500: Verifying volume “LaCie”
2013-11-07 06:45:20 -0500: Starting verification tool:
2013-11-07 06:45:20 -0500: Checking file system2013-11-07 06:45:20 -0500: Checking Journaled HFS Plus volume.
2013-11-07 06:45:20 -0500: Checking extents overflow file.
2013-11-07 06:45:20 -0500: Checking catalog file.
2013-11-07 06:45:59 -0500: Missing thread record (id = 5057741)
2013-11-07 06:46:06 -0500: Checking multi-linked files.
2013-11-07 06:46:19 -0500: Checking catalog hierarchy.
2013-11-07 06:46:38 -0500: Invalid directory item count
2013-11-07 06:46:38 -0500: (It should be 0 instead of 4)
2013-11-07 06:46:38 -0500: Invalid volume directory count
2013-11-07 06:46:38 -0500: (It should be 166840 instead of 166841)
2013-11-07 06:46:38 -0500: Checking extended attributes file.
2013-11-07 06:47:05 -0500: Checking multi-linked directories.
2013-11-07 06:48:10 -0500: Checking volume bitmap.
2013-11-07 06:48:12 -0500: Checking volume information.
2013-11-07 06:48:12 -0500: The volume LaCie was found corrupt and needs to be repaired.
2013-11-07 06:48:12 -0500: Error: This disk needs to be repaired. Click Repair Disk.2013-11-07 06:48:12 -0500:
2013-11-07 06:48:12 -0500: Disk Utility stopped verifying “LaCie”: This disk needs to be repaired. Click Repair Disk.
2013-11-07 06:48:12 -0500:
2013-11-07 06:50:02 -0500: Verify and Repair volume “LaCie”
2013-11-07 06:50:02 -0500: Starting repair tool:
2013-11-07 06:50:02 -0500: Checking file system2013-11-07 06:50:02 -0500: Checking Journaled HFS Plus volume.
2013-11-07 06:50:02 -0500: Checking extents overflow file.
2013-11-07 06:50:02 -0500: Checking catalog file.
2013-11-07 06:50:41 -0500: Missing thread record (id = 5057741)
2013-11-07 06:50:48 -0500: Checking multi-linked files.
2013-11-07 06:51:02 -0500: Checking catalog hierarchy.
2013-11-07 06:51:20 -0500: Invalid directory item count
2013-11-07 06:51:20 -0500: (It should be 0 instead of 4)
2013-11-07 06:51:20 -0500: Invalid volume directory count
2013-11-07 06:51:20 -0500: (It should be 166840 instead of 166841)
2013-11-07 06:51:20 -0500: Checking extended attributes file.
2013-11-07 06:51:47 -0500: Checking multi-linked directories.
2013-11-07 06:52:55 -0500: Checking volume bitmap.
2013-11-07 06:52:56 -0500: Checking volume information.
2013-11-07 06:52:56 -0500: Repairing volume.
2013-11-07 06:52:56 -0500: Missing directory record (id = 5057741)
2013-11-07 06:52:56 -0500: Look for missing items in lost+found directory.
2013-11-07 06:53:10 -0500: Rechecking volume.
2013-11-07 06:53:10 -0500: Checking Journaled HFS Plus volume.
2013-11-07 06:53:10 -0500: Checking extents overflow file.
2013-11-07 06:53:10 -0500: Checking catalog file.
2013-11-07 06:53:16 -0500: Incorrect number of thread records
2013-11-07 06:53:22 -0500: Checking multi-linked files.
2013-11-07 06:53:35 -0500: Checking catalog hierarchy.
2013-11-07 06:53:53 -0500: Invalid directory item count
2013-11-07 06:53:54 -0500: (It should be 5 instead of 6)
2013-11-07 06:53:54 -0500: Invalid volume directory count
2013-11-07 06:53:54 -0500: (It should be 166844 instead of 166842)
2013-11-07 06:53:54 -0500: Invalid volume file count
2013-11-07 06:53:54 -0500: (It should be 1056326 instead of 1056321)
2013-11-07 06:53:54 -0500: Checking extended attributes file.
2013-11-07 06:54:20 -0500: Checking multi-linked directories.
2013-11-07 06:55:25 -0500: Checking volume bitmap.
2013-11-07 06:55:26 -0500: Checking volume information.
2013-11-07 06:55:26 -0500: Repairing volume.
2013-11-07 06:58:06 -0500: Rechecking volume.
2013-11-07 06:58:06 -0500: Checking Journaled HFS Plus volume.
2013-11-07 06:58:06 -0500: Checking extents overflow file.
2013-11-07 06:58:07 -0500: Checking catalog file.
2013-11-07 06:58:12 -0500: Incorrect number of thread records
2013-11-07 06:58:18 -0500: Checking multi-linked files.
2013-11-07 06:58:31 -0500: Checking catalog hierarchy.
2013-11-07 06:58:50 -0500: Invalid volume directory count
2013-11-07 06:58:50 -0500: (It should be 166844 instead of 166842)
2013-11-07 06:58:50 -0500: Invalid volume file count
2013-11-07 06:58:50 -0500: (It should be 1056326 instead of 1056321)
2013-11-07 06:58:50 -0500: Checking extended attributes file.
2013-11-07 06:59:17 -0500: Checking multi-linked directories.
2013-11-07 07:00:22 -0500: Checking volume bitmap.
2013-11-07 07:00:24 -0500: Checking volume information.
2013-11-07 07:00:24 -0500: Repairing volume.
2013-11-07 07:03:03 -0500: Rechecking volume.
2013-11-07 07:03:03 -0500: Checking Journaled HFS Plus volume.
2013-11-07 07:03:03 -0500: Checking extents overflow file.
2013-11-07 07:03:04 -0500: Checking catalog file.
2013-11-07 07:03:09 -0500: Incorrect number of thread records
2013-11-07 07:03:15 -0500: Checking multi-linked files.
2013-11-07 07:03:29 -0500: Checking catalog hierarchy.
2013-11-07 07:03:47 -0500: Invalid volume directory count
2013-11-07 07:03:47 -0500: (It should be 166844 instead of 166842)
2013-11-07 07:03:47 -0500: Invalid volume file count
2013-11-07 07:03:47 -0500: (It should be 1056326 instead of 1056321)
2013-11-07 07:03:47 -0500: Checking extended attributes file.
2013-11-07 07:04:14 -0500: Checking multi-linked directories.
2013-11-07 07:05:19 -0500: Checking volume bitmap.
2013-11-07 07:05:20 -0500: Checking volume information.
2013-11-07 07:05:20 -0500: The volume LaCie could not be repaired after 3 attempts.
2013-11-07 07:05:21 -0500: Volume repair complete.2013-11-07 07:05:21 -0500: Updating boot support partitions for the volume as required.2013-11-07 07:05:21 -0500: Error: Disk Utility can’t repair this disk. Back up as many of your files as possible, reformat the disk, and restore your backed-up files.2013-11-07 07:05:21 -0500:
2013-11-07 07:05:21 -0500: Disk Utility stopped repairing “LaCie”: Disk Utility can’t repair this disk. Back up as many of your files as possible, reformat the disk, and restore your backed-up files.
2013-11-07 07:05:21 -0500:
2013-11-07 07:09:45 -0500: Disk Utility started.
2013-11-07 07:11:45 -0500: Preparing to erase : “LaCie”
2013-11-07 07:11:45 -0500:     Partition Scheme: GUID Partition Table
2013-11-07 07:11:45 -0500:     1 volume will be erased
2013-11-07 07:11:45 -0500:         Name        : “LaCie”
2013-11-07 07:11:45 -0500:         Size        : 999.86 GB
2013-11-07 07:11:45 -0500:         File system    : Mac OS Extended (Journaled)
2013-11-07 07:11:45 -0500: Unmounting disk
2013-11-07 07:11:45 -0500: Erasing
2013-11-07 07:11:54 -0500: Initialized /dev/rdisk1s2 as a 931 GB HFS Plus volume with a 81920k journal
2013-11-07 07:11:54 -0500: Mounting disk
2013-11-07 07:11:54 -0500: Erase complete.
2013-11-07 07:11:54 -0500:
2013-11-07 10:38:00 -0500: Disk Utility started.
2013-11-07 10:38:12 -0500: Verifying volume “LaCie”
2013-11-07 10:38:12 -0500: Starting verification tool:
2013-11-07 10:38:14 -0500: Checking file system2013-11-07 10:38:14 -0500: Checking Journaled HFS Plus volume.
2013-11-07 10:38:14 -0500: Checking extents overflow file.
2013-11-07 10:38:14 -0500: Checking catalog file.
2013-11-07 10:38:29 -0500: Checking multi-linked files.
2013-11-07 10:38:29 -0500: Checking catalog hierarchy.
2013-11-07 10:38:41 -0500: Checking extended attributes file.
2013-11-07 10:39:04 -0500: Checking multi-linked directories.
2013-11-07 10:39:31 -0500: Checking volume bitmap.
2013-11-07 10:39:32 -0500: Checking volume information.
2013-11-07 10:39:32 -0500: The volume LaCie appears to be OK.
2013-11-07 10:39:32 -0500: Repair tool completed:
2013-11-07 10:39:32 -0500:
2013-11-07 10:39:32 -0500:

I just got a call back from the upper level support person at apple care who had been advising me on my trouble with time machine and my LaCie 1 TB FWD. I had sent her much of the same verbiage as I posted here. As some of you have probably figured out, the verdict is that the drive is probably failing. She says this because I have had to do two erase and reformats. She thought that the intermitant problem that I have had with the drive unmounting when my iMac wakes from sleep could be related to the drive failing.
In the meantime I have a secondary back-up (not using time machine) and the LaCie 1 TB FWD is working for the moment.
Thanks to all who read all my verbiage.
And in the meantime, I've learned something. I marked this question as solved. But I'm open to other things to try.
Message was edited by: njtreehugger minor edits and update

Remote disk and time machine?

i have my external hard drive attached to my airport extreme and all my computers, mac and windows, play nice and can copy files to and from it but i have partitioned the hard drive to allow for space for time machine to work but time machine wont find it or if it does refuses to use it as a disk. does time machine work with remote disks?

heay,
I had the same issue with an exteral 250Gb USD WD disk....
I found the solution to my issue in the following manner.
1) the disk/partition must be formated "OS X extended" format.
2) you should be able to use you the Disk/Partition with TM while connected directly to the MAC. (this is just to make sure TM works fine.
3) connect the disk to the airport extreme via USB.
4) mount the the disk on the desktop
5) go to TM preferences and change the backup disk to the disk/partition you just mounted.
6) Activate the TM "status info" in the menu bar
7) turn TM "ON" (DO NOT ATTEMPT TO RUN TM, or you'll have to do the entire procedure from scratch)
8) close the TM preferences.
9) unmount the disk from your desktop (use the the eject button on the shared devices tap in the finder)
10) restart the MAC (you don't need to do this... but this is just to make sure that the disk is unmounted completely)
11) once the boot-up is completed, go to the TM status icon and choose "backup now"
You must make sure that the disk and or partitions you want to use with TM are never mounted before or during the TM process.
As long as the disk/partition is mounted TM will not function.
if you need to use the disk for other purposes than TM wait until TM has done its first run... then you can mount and unmount freely... TM is very sensitive to this "mount" issue.
Note that sometimes TM will fail to funtion... this is not a big problem...
you just need to make sure the disk/partition is unmounted and then run the TM back from the menu bar.
Also note that your first backup will most likely take a very very very very very long time to be completed. just leave the MAC on a make sure it does not fall sleep.
try the above and the let me know if it works or not...
www.gekko-systems.com

Change Thunderbolt Disk Sleep Time

Similar Messages

Maybe you are looking for