Right where to start
My girlfriends laptop has been acting odd for a while.
No sleep (unless you manually ask it) when plugged into the mains.
TimeMachine not working at all
Fans running fast and machine hot all the time.
Now, quitting the process "powerd" seems to fix the sleep issue (though I bet this is only temporary).
Using pmset -g log in terminal I see that a PID PreventUserIdleSystemSleep assertion is being constantly created and released when an external drive is present. The utility creating these is "com.apple.diskmanagementd"
These stop when the external drive (used for TM) is removed. TM itself just seems to hang, or roll over to the next hour after the present hour failed to do anything. Forcing back up now crashes the menu bar.
Digging further, I used the console to see if there are any log files associated with TM. Perhaps I could see what timemachine is trying to do and what is stopping it.
Well.... open console, search for backupd... nothing. Not a single entry. However, the log file appears to be getting absolutely stuffed full of the same two logs over and over. So many infact that these are going over the 500 logs per second limit. These are:
kernel: hfs: set link count-1 on vol=MacintoshHD
kernel: hfs: clear hardline bit on vol=MacintoshHD
its just constant, even with no other drives or peripherals plugged in. Multiples per second and its got something to do with the machines main hard drive.
Something is up. I am guessing backupd can't even write to the log file because of the above thing spamming the hell out it. In activity monitor the root processes syslogd and mtmd are collectively using about 120 % CPU.
I can see why syslogd is using so much, it is being hammered. But what is mtmd? a quick browse suggests that it is the local snap shot feature of TM (which apparently makes quick snapshots whether you like it or not.). Some suggest switching this off in TM options. But I can't see those options.
Someone else suggested mtmd is a spotlight indexing thing linked to TM.
Another suggestion was to boot into safe mode and repair the disk, then boot normally, see whats what. I will try that shortly once she has backed up all her work.
has anyone got any ideas? The HDD isnt about to pop is it?
My girlfriends laptop has been acting odd for a while.
No sleep (unless you manually ask it) when plugged into the mains.
TimeMachine not working at all
Fans running fast and machine hot all the time.
Now, quitting the process "powerd" seems to fix the sleep issue (though I bet this is only temporary).
Using pmset -g log in terminal I see that a PID PreventUserIdleSystemSleep assertion is being constantly created and released when an external drive is present. The utility creating these is "com.apple.diskmanagementd"
These stop when the external drive (used for TM) is removed. TM itself just seems to hang, or roll over to the next hour after the present hour failed to do anything. Forcing back up now crashes the menu bar.
Digging further, I used the console to see if there are any log files associated with TM. Perhaps I could see what timemachine is trying to do and what is stopping it.
Well.... open console, search for backupd... nothing. Not a single entry. However, the log file appears to be getting absolutely stuffed full of the same two logs over and over. So many infact that these are going over the 500 logs per second limit. These are:
kernel: hfs: set link count-1 on vol=MacintoshHD
kernel: hfs: clear hardline bit on vol=MacintoshHD
its just constant, even with no other drives or peripherals plugged in. Multiples per second and its got something to do with the machines main hard drive.
Something is up. I am guessing backupd can't even write to the log file because of the above thing spamming the hell out it. In activity monitor the root processes syslogd and mtmd are collectively using about 120 % CPU.
I can see why syslogd is using so much, it is being hammered. But what is mtmd? a quick browse suggests that it is the local snap shot feature of TM (which apparently makes quick snapshots whether you like it or not.). Some suggest switching this off in TM options. But I can't see those options.
Someone else suggested mtmd is a spotlight indexing thing linked to TM.
Another suggestion was to boot into safe mode and repair the disk, then boot normally, see whats what. I will try that shortly once she has backed up all her work.
has anyone got any ideas? The HDD isnt about to pop is it?