damaged "AutoWake.plist" - what to do?

should I call Apple Care on this one? Is this something to worry about.

for the last few weeks, I keep getting these weird buggy crashes.

so I restarted with the install disc and ran disk utility ... it found errors, but said that it fixed them, and then re-started - but kept getting the same buggy crashes.

so I went to the next step - I installed OS 10.6 on another hard drive, then restarted with that, attached the original startup drive (the one I'm trying to fix) and fixed it with diskwarrior.

It gave me a report, which I'll post below, but I believe that this is the key part "

File: "com.apple.AutoWake.plist"!
Detected that Property List data is damaged and cannot be repaired.!
Unexpected character u at line 1!
Location: "M4/Library/Preferences/SystemConfiguration/"!

could "com.apple.AutoWake.plist" be causing those crashes?

what can I do about it?

should I call apple care?

Full report below -
thanks!

-----

(actually let me post this now ... to see if anyone knows what to do about the plist issue, which I suspect is that problem.. will figure out a way to post a more legible version of the full report shortly...)

DiskWarrior scanned the disk named "M4" checking all files and folders for damage and potential compatibility problems.! !

Permissions:!
! Started verify/repair permissions on disk7s2 M4!
Permissions differ on "usr/share/derby", should be drwxr-xr-x , they are lrwxr-xr-x !
Repaired "usr/share/derby"! Warning: SUID file "System/Library/CoreServices/RemoteManagement/ARDAgent.app/Contents/MacOS/ARDAg ent" has been modified and will not be repaired! Finished verify/repair permissions on disk7s2 M4! ! ! Disk: "M4"! The Property List data was checked in 17,916 files.! The Resource Data was checked in 30,742 files.! The maximum Folder Depth on this disk is 28. This does not exceed the maximum recommended depth.! The System Symbolic Link Files were checked and no problems were found.! Location: "Desktop"! ! File: "com.apple.AutoWake.plist"! Detected that Property List data is damaged and cannot be repaired.! Unexpected character u at line 1! Location: "M4/Library/Preferences/SystemConfiguration/"! !

File: "dictionary jacket jkt.jpg"! Detected that the resource header is damaged and cannot be repaired! Location: "M4/Users/unclefreeds/Pictures/iPhone photos/"! ! File: "WF dictionary cover YES.jpg"! Detected that the resource header is damaged and cannot be repaired! Location: "M4/Users/unclefreeds/Pictures/CD Cover JPGs/"! ! File: "WF dictionary cover YES.jpg"! Detected that the resource header is damaged and cannot be repaired! Location: "M4/Users/unclefreeds/Library/Mail/IMAP-wfriedwald@imap.gmail.com/[Gmail]/Trash .imapmbox/ Attachments/186218/2.1/"! ! File: "WF dictionary cover YES.jpg"! Detected that the resource header is damaged and cannot be repaired! Location: "M4/Users/unclefreeds/Library/Mail/IMAP-wfriedwald@imap.gmail.com/[Gmail]/Trash .imapmbox/ Attachments/186218/2/"! ! Explanations:! ! Folder Depth: This number indicates how many folders are nested inside each other. If a disk contains only three folders and Folder A is inside Folder B and Folder B is inside Folder C, then this disk has a maximum folder depth of three. Folders nested too deeply can cause software compatibility problems.! ! Permissions: This is the part of the directory information for files and folders that records ownership, what type of access, if any, other users have, and designates whether a file is a system file with a special purpose. Files and folders that make up a Mac OS X installation must have specific user permissions for proper startup and operation.! ! Property List: This is a standard file format for storing data and is often used to store preferences. The names of these files normally end with a .plist file extension. Corrupt property list files can cause system instability.! ! Resource Data: This is an older file format for storing data and was often used to store preferences. The names of
these files normally end with a .rsrc file extension. Corrupt resource data files can cause system instability.! ! System Symbolic Link Files: These are files used by the operating system that are similar to aliases. If these files are damaged it may prevent startup or cause system instability.! ! Time: 3/19/10 12:35:13 PM! DiskWarrior Version: 4.1.1 - RR111297

MacPro; 2 x 3 MHz Quad-Core Intel Xeon; 16 GB RAM, Mac OS X (10.6.1), World's Largest iTunes library (too big too count!)

Posted on Mar 19, 2010 9:51 AM

Reply
12 replies

Mar 19, 2010 9:55 AM in response to WillFriedwald2

Often DW and other preference file checkers will report such errors because the plist in question is not standard format. Usually the errors are meaningless. However, you can verify if it's a problem by simply deleting the plist file.

However, if the computer is crashing (you did not describe precisely what happens when it crashes) then checking the console log using the Console application in the Utilities folder as well as the CrashReporter log may reveal what has caused the crash.

Mar 19, 2010 10:02 AM in response to Kappy

* Is it safe to just delete the plist in question? this won't hurt the system or anything?

* the crashes are strange: one program stops responding - sometimes I can force quit at that point and prevent the whole system from crashing - but then usually another program freezes, then the finder, then I can't do anything but a forced (power button) restart...

It's been happening at least once a day for a while, but this is the first time I brought out diskWarrior since it started....

thanks!

w

Mar 19, 2010 10:30 AM in response to WillFriedwald2

Yes, it's safe. You will lose any configuration for auto awake, but when you do configure it a new plist file will be created.

From what you are describing the problem is not likely one DW or any disk utility will fix. The problem may be due to corrupted preference, cache, log, and/or font cache files or some application incompatibility or simply a corrupted system.

You need to provide more information on the nature of these crashes/freezes. Are there kernel panics? Check your console and CrashReporter logs for information on what may be happening at the moments just preceding a crash.

Mar 19, 2010 10:51 AM in response to Kappy

oof! - if DiskWarrior & Disk Utility can't fix it then I'm in trouble!

anyhow, deleted the offending plist file (but saved it on another hard drive ... out of harm's way... where it can't affect anything, I hope!)

if it happens again (of course, I am hoping that it will NOT!) I will check the console... and let you know...

thanks for the input...

will

---

PS: I deleted the offending file, as mentioned above. (There were also a few copies of a JPEG that DW didn't like, four copies of the same picture. I deleted all of those two... moved one copy to picasa for safekeeping...)

I ran DW yet again - and here is the report - is there anything else that might be a red flag? cause for concern? otherwise I guess I will put the original startup drive backin (the one I just repaired) and start up with it - see what happens...

thanks again...

----

DiskWarrior scanned the disk named "M4" checking all files and folders for damage and potential compatibility problems.

Permissions:


Started verify/repair permissions on disk7s2 M4
Permissions differ on "usr/share/derby", should be drwxr-xr-x , they are lrwxr-xr-x
Repaired "usr/share/derby"
Warning: SUID file "System/Library/CoreServices/RemoteManagement/ARDAgent.app/Contents/MacOS/ARDAg ent" has been modified and will not be repaired
Finished verify/repair permissions on disk7s2 M4

Disk: "M4"
The Property List data was checked in 17,915 files.
The Resource Data was checked in 30,738 files.
The maximum Folder Depth on this disk is 28. This does not exceed the maximum recommended depth. The System Symbolic Link Files were checked and no problems were found. Location: "Desktop"

Message was edited by: WillFriedwald2

Message was edited by: WillFriedwald2

Mar 20, 2010 2:48 AM in response to WillFriedwald2

sad to say the bugginess has not stopped...

when I began using my "repaired" regular startup drive again, I can't get my eSATA drives to mount properly.

Before the "repair" the eSATA drives worked fine - now they're giving me a hard time -

not sure what to do about that? reinstall a new driver from silicon image?

not sure if I shouldn't just start "building" a whole new start up drive from the ground up. Essentially I keep everything on the start up drive EXCEPT the iTunes library, which is way too big...

frustrated!

not sure, now, how to use the console utility...

thanks again for help...

will

PS: just now - turned on system - tried to mount eSATA drives - when that didn't work I started typing this message - now it looks like the finder has stopped responding. Frustrating, yes -

will probably have to force re-start again... maybe will have to put my three eSATA drives in USB cases for the time being. Frustrating!

Message was edited by: WillFriedwald2

Mar 20, 2010 11:05 AM in response to WillFriedwald2

I know we talked privately via e-mail, but for the benefit of anyone looking for a solution, I'll post my comments here too in case someone else finds them useful.

It sounds to me like the hard drive might be starting to fail. The next thing I would do (after making a backup copy of the drive) is get a utility of some kind that will read the S.M.A.R.T. data from the drive to see how many errors have been recorded. That info will tell you if it is the drive failing or not. Lot's of S.M.A.R.T. errors means the hardware is dying soon.

Only owning a Mac for only 3 days, I'm not that familiar with how to actually do that on OSX, but I'm sure there are some utilities available to do this.

Mar 22, 2010 1:37 PM in response to gkmeyer

Am not sure if I should start a new thread or continue with this one, but here's the latest:

Okay - as you can see, I was having problems with Drive A - so I restarted with Drive B, and while Drive B was the start-up, I used Disk Util and DiskWarrior to repair Drive A.

then I re-started with Drive A...

NOW, to make it more confusing, ever since this problem with switching drives, I started having issues with my eSATA drives... never before, even throughout these other crashes...

however, today, I go back to starting with the cleaned up & repaired Drive A.

I do NOT turn on the eSATA drives - just to make sure that's not part of the problem (although it may be...)

I'm doing fine from about 8 AM to 4 PM...

then, here's what happens - the same kind of crash as before. I find something interesting on a website (in firefox) I start to copy the URL for my friends David & Greg..

then in the middle of copying that ULR (CRTL-C) it freezes - I notice that the finder doesn't respond. the finder is frozen. I can't switch from one program to another. There's what you might call limited functionality - using F3 (I forget what that's called?) I get all the open windows in the finder and I can switch between them, but I can't do anything.

Anyhow, that's the crash that happens. I restarted with yet a third drive (Drive C) which I had made last night... (a superduper copy of Drive A)

how can I access the console info - do I get it from Drive A somehow (do I have to restart with Drive A as the startup drive?)

Thanks!

w

Mar 28, 2010 7:16 AM in response to WillFriedwald2

I also have the error "System/Library/CoreServices/RemoteManagement/ARDAgent.app/Contents/MacOS/ARDAg ent" which may be nothing which is how I found this thread.

Anyway, notice you are running 10.6.1 when .2 is available. It's page 1 stuff to update when problems occur. Worth a try.

The other obvious one is back-up your data, properly erase the internal disk and re-install it all. Long winded sure, but you've lost a load of time already and a clean install of the OS and your apps is always a good way to spring clean and loose all the extra bits you run that may contribute to your problem.

Disk Utility checks SMART status as does Onyx (get it from MacUpdate). Onyx will clear out a load of crap too. Just use the 'automation' button after it has started up and done the SMART check. Tick all the boxes and leave it to work. Back-up user data first.

Just an aside, I have a quad core also and it's just an odd machine, this MacBook runs better with the feel of everything, may be a model issue, maybe check out if there is a know problem specific to that model.

This thread has been closed by the system or the community team. You may vote for any posts you find helpful, or search the Community for additional answers.

damaged "AutoWake.plist" - what to do?

Welcome to Apple Support Community
A forum where Apple customers help each other with their products. Get started with your Apple Account.