Slate 21 Pro ongoing sleep problems that can't be resolved

I just bought a slate 21 pro after hearing about sleep related issues, but was encouraged by various reports of solutions in the form of a replacement unit with upgraded scalar firmware, not using keyboard/mouse, not connecting an hdmi in device and/or using a bluetooth keyboard.
I'm sad to say that none of those things reliably resolves the problem of the unit going to sleep and requiring a power cord pull to get it back.
My unit was replaced by HP with a scalar 3.7 unit, I've tried it with and without a keyboard, with and without a bluetooth keyboard, with and without an external pc plugged into the hdmi, with and without the 4.3 security update etc. Both the original and the replacement still have sleep issues.
HP stopped responding to my case updates after the original replacement, but they were right on top of me when I was one day late returning the original product...with the hilarious suggestion that they'd charge me nearly $600 if I didn't promptly return it.
I'm going to try calling in when I have a chance tomorrow, hoping to get a real person that might actually look into this. I'm also hoping it doesn't turn into a constant return carousel where they keep sending me the same device with the same defect. I've had this problem on rare occasion with other android devices and it generally gets resolved with a firmware fix.
In the meanwhile, for any other prospective purchasers...you'll either have to leave the unit in 'daydream' mode where its on (and the screen) all the time to the tune of 26 watts and likely shortened screen life. None of the supposed 'fixes' seem to fix it for me. Abandon hope, all ye who enter here.
I'll update if anything gets better. If there are any HP folks who want to chime in here that'd be great. Seems they've stopped responding on the other threads

My friend,
Try the new version 4.4.2 which is just started to upgrade in my country, Turkiye.
Rgds

Similar Messages

Drive has a hardware problem that can't be repaired?

I have had a Lacie 1TB 7200RPM external drive for about 3 years now. In the last two days I got this message when I went into disk utility. "drive has a hardware problem that can't be repaired". I was able to back up all the info off of the drive.
Is this a drive problem or a hardware problem. I am using esata and an esata card. Not sure what the card is.
Any diagnostics.
I ran a verify and repair permissions and was told the drive is OK.

Do this:
Drive Partition and Format
1. Open Disk Utility in your Utilities folder.
2. After DU loads select your hard drive (this is the entry with the mfgr.'s ID and size) from the left side list. Click on the Partition tab in the DU main window.
3. Under the Volume Scheme heading set the number of partitions from the drop down menu to one. Click on the Options button, set the partition scheme to GUID then click on the OK button. Set the format type to Mac OS Extended (Journaled.) Click on the Apply button and wait until the process has completed.

This drive has a hardware problem that can't be repaired

Hello all! I'm using a late 2009 27" iMac (2.8 GHz, 12 GB Ram). I've been noticing a lot of insanely slow speed lately, mostly in opening new folders or restarting. I ran the Disk Utility and it maked my internal 1TB drive as "This drive has a hardware problem that can't be repaired". Thankfully I have a 2tb backup external that has all my data on it, but now it's time to decide what to do.
1. Try and reformat my hard drive and reinstall the backup
2. Replace the drive with a new internal drive (and look for the best solution... thinking either a hybrid drive, SSD+internal or a 7200 RPM drive)
3. Throw my iMac into the sea.
4. Cry
So basically my question is:
Is my drive dead and should i even try to help it? (I don't qualitfy for the TB repair from Apple and my Applecare is up)
What are the best performance upgrades for an internal. 7200 internal? 7200 Hybrid? both an SSD and an internal drive?
Thank you in advance.

You will have to see what the SMART report is for the drive in Disk Utility. If it says "Verified" then the drive should be OK. All you need do is repartition and reformat the drive. On the other hand if DU reports the drive has an I/O problem then the drive is probably bad.
Initially why not just try this:
Drive Preparation
1. Boot from your Snow Leopard Installer Disc. After the installer loads select your language and click on the Continue button. When the menu bar appears select Disk Utility from the Utilities menu.
2. After DU loads select your hard drive (this is the entry with the mfgr.'s ID and size) from the left side list. Note the SMART status of the drive in DU's status area. If it does not say "Verified" then the drive is failing or has failed and will need replacing. SMART info will not be reported on external drives. Otherwise, click on the Partition tab in the DU main window.
3. Under the Volume Scheme heading set the number of partitions from the drop down menu to one. Click on the Options button, set the partition scheme to GUID then click on the OK button. Set the format type to Mac OS Extended (Journaled.) Click on the Partition button and wait until the process has completed.
4. Select the volume you just created (this is the sub-entry under the drive entry) from the left side list. Click on the Erase tab in the DU main window.
5. Set the format type to Mac OS Extended (Journaled.) Click on the Security button, check the button for Zero Data and click on OK to return to the Erase window.
6. Click on the Erase button. The format process can take up to several hours depending upon the drive size.
7. Quit DU when formatting has completed. Install Snow Leopard.

My iMac says this drive has a hardware problem that can't be repaired

Hi my iMac DIsk utility reports that the Macintosh disk has problems that can not be repaired.
Is this a false alarm, or I do need to go to an apple store and get it replaced.

OSX Lion. Did not have any real issues. Just was trying to update to OSX Maverick, and it refuses to install because of this issue.
Then I went to the utility and it says S.M.A.R.T has determined that my Macintosh HD has problems that cannot be repaired. Backup your data soon and replace the disk.
Following is the exact OS
Software OS X 10.8.5 (12F45)
Following are the details
Hardware Overview:
Model Name:          iMac
Model Identifier:          iMac12,2
Processor Name:          Intel Core i5
Processor Speed:          3.1 GHz
Number of Processors:          1
Total Number of Cores:          4
L2 Cache (per Core):          256 KB
L3 Cache:          6 MB
Memory:          4 GB
Boot ROM Version:          IM121.0047.B1F
SMC Version (system):          1.72f1

I downloaded OS Mountain Lion 10.8... and when I was getting ready to install I get "This disk has S.M.A.R.T. errors. This disk has a hardware problem that can't be repaired. I have read some of the same comments below. Why?

I was trying to install OS X Mountain Lion 10.8... and I got an error saying, "This disk has S.M.A.R.T. errors. This disk has a hardware problem that can't be repaired. I saw several other questions below of people having the same or similar problems. Does this mean that my hard drive is about to crash? I plan to head to the place I purchased and have it checked out. I backed up my data a couple of days ago. Any comments?

Yes, S.M.A.R.T. is a built-in diagnostic on the hard drive, and it is reporting a problem that may cause it to fail.
You can see the same status in Disk Utility, and possibly get more info. Run Disk Utility and select the DRIVE in the sidebar. Be sure to select the DRIVE and not the volume indented below it. At the bottom of the window, there is a field for S.M.A.R.T. Status. If there is no problem, it should say Verified.
You can also do a Get Info on the drive (File -> Get Info) in Disk Utility, and the Info window provides more detailed information (toward the bottom) about what is being checked.

Yosemite won't install due to a "S.M.A.R.T. drive problem that can't be repaired."

After downloading Yosemite successfully, it won't install due to a "S.M.A.R.T. drive problem that can't be repaired." It says to back up as much as possible and replace the drive. Everything works flawlessly with Mavericks. What gives??

If you are getting a S.M.A.R.T. error then you should be more worried about losing everything on your drive then about upgrading your Mac OS. Regardless of if you are running Mac OS, Linux, or Windows, you should never just disregard such a drive error. S.M.A.R.T. is designed to give you a warning that your drive is statistically having far more errors than normal and should be backed up immediately and typically replaced.
In your case, it's likely a coincidence that your drive is failing at the time you are attempting to upgrade to Yosemite. You should stop what you are doing, backup your drive (if you don't already have the backups that you should prior to any OS upgrade), and replace the hard drive prior to moving forward.
To make it clear, your hard drive is likely going to fail soon and you may lose everything on it at any moment. This failure has nothing to do with Yosemite or any Mac OS. All hard drives fail at some point. Hopefully this S.M.A.R.T. notice has given you the opportunity to solve a major problem before it gets worse.

I cannot find the next and previous button in iTunes get info menu? Is there anyone that has also experienced this problem that can help me please

I cannot find the next and previous button in iTunes get info menu?
Is there anyone that has also experienced this problem that can help me please
I have the lates version of Itunes

I have managed to figure out how to solve this problem, after looking around I saw a lot of people kept saying makesure it is list view however this still did not work, I found the only way for me get these buttons back was to change the Movie to a TV Show and only then did the "Next" and "Previous" button appear. Right Click> Get Info > Options > Media Kind and then Select TV Show, this is extremely inconvienent but the only way that I found that has worked so far.
Hope this works for you too!!

When updating to Mountain Lion I get this measageThis disk has S.M.A.R.T. errors. This disk has hardware problem that can't be repaired. Back up as much data as possible and replace the disk.

When updating to Mountain Lion I get this measage
This disk has S.M.A.R.T. errors. This disk has hardware problem that can’t be repaired. Back up as much data as possible and replace the disk.
never had this before download of Mountain Lion.

As others have stated, this is a potentially catastrophic event. Consider yourself lucky, as hard drives usually just fail wihtout warning. Your disk could die at any time. This is a mechanical / physical failure, not software related.
Going forward, I would suggest utilizing a utility that monitors SMART status, which you obviously don't have, such as SpeedTools.

"This disk has S.M.A.R.T. errors. This disk has a hardware problem that can't be repaired

THis is the error message I get when I try to install lion on a mid-2010 iMac 27". "This disk has S.M.A.R.T. errors. This disk has a hardware problem that can't be repaired. Back up as much of the data as possible and replace the disk"
However, when I run disk utility, it says that the disk is fine. What should I do?
thanks in advance
A.

Disk Utility checks the disk directory that keeps track of all your files. S.M.A.R.T. status checks some hardware stuff and attempts to warn you before the disk just flat-out dies. The directory can still be fine on a failing disk but don't count on it staying that way if you continue to write to the failing disk. Make a miniumun of one copy of your data on the failing drive immediately. Two or more copies would be much better. Having only one reliable copy of your data is very unwise.
You can use Carbon Copy Cloner (donationware) or Super Duper! (free and paid versions) to make a bootable clone of your failing drive to use as one of your copies. In System Preferences > Startup Disk select the clone as your startup drive. You can use the clone for your work until you can get your Mac in to have the hard drive replaced. When you get your Mac back Setup Assistant will be equally happy to restore all of your data from a Time Machine backup or a clone.

Is Final Cut Pro the only software that can open video .MXF files for Macs?

Hello,
Many thanks in advance for your attention.
Trying to find software that will edit .MXF Video Files to work with Mac.
As the edit is simple, prefer iMovie, but happy if the Conversion software only works with FCExpress (or even FCPro if that is the only alternative).
1. If it matters, .MXF (Material Exchange Format) Video files came from shooting on a Panasonic 500 P2. Originally downloaded onto a Windows system, using Adobe Premiere.
2. I just want to see and convert some of the shots I did for my Reel, etc., but I have a Mac.
3. I have iMovie HD, iMovie 09, and FCExpress (which I don't know how to use that well).
4. When I attach an External HD with backup files of all the footage shot, they show up named as .MXF files. They appear as VLC files (VLC icon), but the suffix is .MXF.
5. When I try to play them as VLC files, they won't play. It seems they start to play, but then the VLC software quits.
6. So I have tried downloading some software on the Internet that Google says converts .MXF files.
I tried: iSkysoft Video Converter, AVCWare Mac Video Converter, MPEG Streamclip, and a couple others. They all seem to have basically the same conversion setups, but when I click to pick one .MXF file, none of them recognize it. (The file in my Browse window is greyed out).
7. MoyaVideo Converter for Mac recognizes the .MXF file, but when I hit the "conversion" button - I tried a couple different settings, all it seems to convert is the first frame. Even if the .MXF file says a clip is 123MB or 43 seconds long, etc.
8. I can't even watch the clip in Preview. Press Play and it is just the first frame.
9. I have read elsewhere in these forums, some people touting conversion software from a company in Germany - mfxformac. I am fine with paying for conversion software, but $500?
10. And I have read elsewhere that only Final Cut Pro has a codec that will open .MXF files. If this is so, why do the above companies claim to have software that opens .MXF files for Mac?
11. Isn't there a further problem if I can't even see the video using VLC? Or is that because I am using Mac and need FCPro with the right codec?
Anyone's help would be greatly appreciated.

MXF files from P2 can only be imported using FCP. iMovie can't, nor FCE...if you are talking about APPLE software. Avid deals with MXF files natively. But FCP will ONLY import them if the entire P2 card structure is intact. Please tell me that you have the entire P2 card backups. If not, then it won't work. If you do...then here is the process for importing into FCP:
P2 Workflow with FCP 6
3. I have iMovie HD, iMovie 09, and FCExpress (which I don't know how to use that well).
Then you need someone to provide you with QT files of this footage. None of them work with P2.
NONE of the converters you listed will work... Sorry.
9. I have read elsewhere in these forums, some people touting conversion software from a company in Germany - mfxformac. I am fine with paying for conversion software, but $500?
That software is to get it to work with Final CUt Pro natively. What it doesn't do is convert the footage to QTs. There is also Raylight and Calibrated...but again, they are for FCP.
P2 is a professional format, and to use it you need professional software. iMovie won't work...nor will FCE. If you need to work with it in those formats, you need to have someone import the files and convert them to AIC (Apple Intermediate Codec).
HD Log might work...but not sure what QT format it converts to. A demo is available.
http://www.imagineproducts.com/index.php?mainpage=product_info&cPath=1&productsid=4&zenid=b2buo1aguk3cplmg23jn05aai7
Shane

Mid-2010 Macbook Pro 13" Sleep Problems

Recently, whenever my Macbook goes to sleep, it is unresponsive when I try to wake it up. I have to hold down the power button for a few seconds and force quit it with no indication that it is off, however, when I press the power button again, it turns on. But it doesn't turn on how it normally should. It does a double-take startup. The disk drive (or whatever it is that makes the sound at the startup) makes the sound and the screen pops up white, but after about a second, it goes out, almost as if it force quit itself, but after about another second, it turns on normally and since I put in a Samsung SSD about 3 months ago, it boots right up in a matter of seconds.
So far, this kind of stuff has been tolerable but probably not good for my computer.
But the worst case happened tonight when I put my Macbook into sleep mode. I was gone for about an hour and 20 minutes and when I got back to my computer and opened up the lid, it was pretty hot and the fans were probably running between 4000 and 5000 rpm. All this was happening when the computer was supposed to be in sleep mode and again, when I opened it up nothing appeared on the screen and it was unresponsive. This time when I force quit, I knew when it worked because I could here the fans turn off. I manually clicked Sleep this time, but I think this happened a few days ago too when I simply closed the lid to put it in sleep mode, however the computer wasn't running this hot.
I'm hoping it isn't the Logic Board and just maybe a software issue, but I have a strong feeling it isn't the software. I'm running Mavericks 10.9.5 so I'm hoping that an upgrade to Yosemite might fix it, but I doubt it.
I've already had to replace the battery, logic board, disk drive, trackpad, and I'm on my 3rd hard drive, and this computer is only 4 and a half years old. Thankfully, Apple Care covered most of the costs and basically none of the issues were due to my neglect, but it is out of warranty now. I would like to think I just got a bad computer right out of the box.

Here is the Console Log from the event I mentioned:
12/1/14 10:12:12.000 PM kernel[0]: Opened file /var/vm/sleepimage, size 1073741824, partition base 0x0, maxio 2000000 ssd 1
12/1/14 10:12:12.000 PM kernel[0]: hibernate image major 1, minor 0, blocksize 4096, pollers 5
12/1/14 10:12:12.000 PM kernel[0]: hibernate_alloc_pages act 77766, inact 63980, anon 46689, throt 0, spec 25243, wire 60358, wireinit 36014
12/1/14 10:12:12.000 PM kernel[0]: hibernate_setup(0) took 0 ms
12/1/14 11:34:34.000 PM kernel[0]: hibernate_page_list_setall(preflight 0) start 0xffffff80346f1000, 0xffffff8034726000
12/1/14 11:34:34.000 PM kernel[0]: hibernate_page_list_setall time: 94 ms
12/1/14 11:34:34.000 PM kernel[0]: pages 271737, wire 61704, act 33386, inact 39, cleaned 0 spec 10, zf 44669, throt 0, compr 42810, xpmapped 40000
12/1/14 11:34:34.000 PM kernel[0]: could discard act 44499 inact 19273 purgeable 114 spec 25233 cleaned 0
12/1/14 11:34:34.000 PM kernel[0]: WARNING: hibernate_page_list_setall skipped 96949 xpmapped pages
12/1/14 11:34:34.000 PM kernel[0]: hibernate_page_list_setall found pageCount 182618
12/1/14 11:34:34.000 PM kernel[0]: IOHibernatePollerOpen, ml_get_interrupts_enabled 0
12/1/14 11:34:34.000 PM kernel[0]: IOHibernatePollerOpen(0)
12/1/14 11:34:34.000 PM kernel[0]: encryptStart 14000
12/1/14 11:34:34.000 PM kernel[0]: bitmap_size 0xe028, previewSize 0x6c8620, writing 179644 pages @ 0x6ea648
12/1/14 11:34:34.000 PM kernel[0]: booter start at 5399 ms smc 0 ms, [6, 0, 0] total 1386 ms, dsply 473, 38 ms, tramp 283 ms
12/1/14 11:34:34.000 PM kernel[0]: hibernate_machine_init: state 2, image pages 60529, sum was 27699e7c, imageSize 0x18f15000, image1Size 0x6598000, conflictCount 324, nextFree 1d6
12/1/14 11:34:34.000 PM kernel[0]: hibernate_page_list_discard time: 110 ms, discarded act 44499 inact 19273 purgeable 114 spec 25233 cleaned 0
12/1/14 11:34:34.000 PM kernel[0]: hibernate_newruntime_map time: 0 ms, IOHibernatePollerOpen(), ml_get_interrupts_enabled 0
12/1/14 11:34:34.000 PM kernel[0]: IOHibernatePollerOpen(0) 23 ms
12/1/14 11:34:34.000 PM kernel[0]: hibernate_machine_init reading
12/1/14 11:34:34.000 PM kernel[0]: PMStats: Hibernate read took 2563 ms
12/1/14 11:34:34.000 PM kernel[0]: hibernate_machine_init pagesDone 181443 sum2 d28892fc, time: 2563 ms, disk(0x20000) 117 Mb/s, comp bytes: 307064832 time: 398 ms 735 Mb/s, crypt bytes: 311939072 time: 1894 ms 157 Mb/s
12/1/14 11:34:34.000 PM kernel[0]: Wake reason: EHC1 OHC1 EHC2 OHC2 (User)
12/1/14 11:34:34.000 PM kernel[0]: AirPort_Brcm43xx::powerChange: System Wake - Full Wake/ Dark Wake / Maintenance wake
12/1/14 11:34:34.000 PM kernel[0]: Previous Sleep Cause: 5
12/1/14 11:34:34.000 PM kernel[0]: Previous Shutdown Cause: 3
12/1/14 11:34:34.000 PM kernel[0]: NVRM: 0x702a called in D3
12/1/14 11:34:34.000 PM kernel[0]: NVRM: 0x7037 called in D3
12/1/14 11:34:34.000 PM kernel[0]: com_apple_driver_AppleUSBCardReaderUMC:: Stop::Controller Reset
12/1/14 11:34:34.000 PM kernel[0]: wlEvent: en1 en1 Link DOWN virtIf = 0
12/1/14 11:34:34.000 PM kernel[0]: AirPort: Link Down on en1. Reason 8 (Disassociated because station leaving).
12/1/14 11:34:34.583 PM WindowServer[89]: CGXDisplayDidWakeNotification [3966319317291]: posting kCGSDisplayDidWake
12/1/14 11:34:34.604 PM WindowServer[89]: handle_will_sleep_auth_and_shield_windows: Reordering authw 0x7fad0957ec70(2000) (lock state: 3)
12/1/14 11:34:34.629 PM configd[17]: network changed: v4(en1-:149.160.140.151) v6(en1:2001:18e8:2:28c2:f000::244) DNS! Proxy SMB-
12/1/14 11:34:34.631 PM configd[17]: setting hostname to "Aarons-MacBook-Pro.local"
12/1/14 11:34:34.646 PM WindowServer[89]: handle_will_sleep_auth_and_shield_windows: err 0x0
12/1/14 11:34:35.000 PM kernel[0]: considerRebuildOfPrelinkedKernel prebuild rebuild has expired
12/1/14 11:34:35.000 PM kernel[0]: USBMSC Identifier (non-unique): 000000009833 0x5ac 0x8403 0x9833, 2
12/1/14 11:34:35.757 PM UserEventAgent[11]: Captive: CNPluginHandler en1: Inactive
12/1/14 11:34:35.758 PM configd[17]: network changed: v6(en1-:2001:18e8:2:28c2:f000::244) DNS- Proxy-
12/1/14 11:34:36.000 PM kernel[0]: IOBluetoothUSBDFU::probe
12/1/14 11:34:36.000 PM kernel[0]: IOBluetoothUSBDFU::probe ProductID - 0x8213 FirmwareVersion - 0x0207
12/1/14 11:34:36.000 PM kernel[0]: **** [IOBluetoothHostControllerUSBTransport][start] -- completed -- result = TRUE -- 0xe400 ****
12/1/14 11:34:36.000 PM kernel[0]: **** [BroadcomBluetoothHostControllerUSBTransport][start] -- Completed -- 0xe400 ****
12/1/14 11:34:36.000 PM kernel[0]: [IOBluetoothHCIController][staticBluetoothHCIControllerTransportShowsUp] -- Received Bluetooth Controller register service notification -- 0xe400
12/1/14 11:34:36.000 PM kernel[0]: [IOBluetoothHCIController::setConfigState] calling registerService
12/1/14 11:34:36.000 PM kernel[0]: **** [IOBluetoothHCIController][protectedBluetoothHCIControllerTransportShowsUp] -- Connected to the transport successfully -- 0xcd40 -- 0x1800 -- 0xe400 ****
12/1/14 11:34:36.000 PM kernel[0]: **** [IOBluetoothHostControllerUSBTransport][SuspendDevice] -- Suspend -- suspendDeviceCallResult = 0x0000 (kIOReturnSuccess) -- 0xe400 ****
12/1/14 11:34:40.923 PM digest-service[414]: digest-request: uid=0
12/1/14 11:34:40.924 PM digest-service[414]: digest-request: init request
12/1/14 11:34:40.934 PM digest-service[414]: digest-request: init return domain: 149-160-140-151 server: AARONS-MACBOOK-PRO indomain was: <NULL>
12/1/14 11:34:41.031 PM digest-service[414]: digest-request: uid=0
12/1/14 11:34:41.031 PM digest-service[414]: digest-request: init request
12/1/14 11:34:41.035 PM digest-service[414]: digest-request: init return domain: MACBOOKPRO-EE1C server: AARONS-MACBOOK-PRO indomain was: <NULL>
12/1/14 11:34:41.172 PM eapolclient[464]: en1 STOP
12/1/14 11:34:41.749 PM Apple80211Agent[491]: [EAPOLControl.c:178] EAPOLControlAuthInfoIsValid(): Ignoring SaveCredentialsOnSuccessfulAuthentication since no credentials were specified
12/1/14 11:34:41.761 PM eapolclient[492]: en1 START uid 501 gid 20
12/1/14 11:34:41.000 PM kernel[0]: MacAuthEvent en1 Auth result for: 6c:f3:7f:bb:c0:e0 MAC AUTH succeeded
12/1/14 11:34:41.000 PM kernel[0]: wlEvent: en1 en1 Link UP virtIf = 0
12/1/14 11:34:41.000 PM kernel[0]: AirPort: Link Up on en1
12/1/14 11:34:41.000 PM kernel[0]: en1: BSSID changed to 6c:f3:7f:bb:c0:e0
12/1/14 11:34:41.979 PM eapolclient[492]: en1 PEAP: successfully authenticated
12/1/14 11:34:42.000 PM kernel[0]: AirPort: RSN handshake complete on en1
12/1/14 11:34:42.000 PM kernel[0]: flow_divert_kctl_disconnect (0): disconnecting group 1
12/1/14 11:34:43.284 PM DashboardClient[494]: 10.4-style NSNumberFormatter method called on a 10.0-style formatter, which doesn't work. Break on _NSNumberFormatter_Log_New_Methods_On_Old_Formatters to debug. This message will only be logged once.
12/1/14 11:34:43.000 PM kernel[0]: SMC::smcReadKeyAction ERROR TC0H kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff800b4c3000
12/1/14 11:34:43.000 PM kernel[0]: SMC::smcReadKeyAction ERROR TC1D kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff800b4c3000
12/1/14 11:34:43.000 PM kernel[0]: SMC::smcReadKeyAction ERROR TCAH kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff800b4c3000
12/1/14 11:34:43.000 PM kernel[0]: SMC::smcReadKeyAction ERROR TCBH kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff800b4c3000
12/1/14 11:34:43.000 PM kernel[0]: SMC::smcReadKeyAction ERROR TG0P kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff800b4c3000
12/1/14 11:34:43.000 PM kernel[0]: SMC::smcReadKeyAction ERROR TA0P kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff800b4c3000
12/1/14 11:34:43.000 PM kernel[0]: SMC::smcReadKeyAction ERROR TH0P kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff800b4c3000
12/1/14 11:34:43.000 PM kernel[0]: SMC::smcReadKeyAction ERROR TO0P kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff800b4c3000
12/1/14 11:34:43.000 PM kernel[0]: SMC::smcReadKeyAction ERROR TH1P kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff800b4c3000
12/1/14 11:34:43.000 PM kernel[0]: SMC::smcReadKeyAction ERROR TH2P kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff800b4c3000
12/1/14 11:34:43.000 PM kernel[0]: SMC::smcReadKeyAction ERROR TH3P kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff800b4c3000
12/1/14 11:34:43.000 PM kernel[0]: SMC::smcReadKeyAction ERROR Th0H kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff800b4c3000
12/1/14 11:34:43.000 PM kernel[0]: SMC::smcReadKeyAction ERROR Th2H kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff800b4c3000
12/1/14 11:34:43.000 PM kernel[0]: SMC::smcReadKeyAction ERROR TG0H kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff800b4c3000
12/1/14 11:34:43.000 PM kernel[0]: SMC::smcReadKeyAction ERROR TG1H kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff800b4c3000
12/1/14 11:34:43.000 PM kernel[0]: SMC::smcReadKeyAction ERROR TG0D kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff800b4c3000
12/1/14 11:34:43.000 PM kernel[0]: SMC::smcReadKeyAction ERROR Tp1C kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff800b4c3000
12/1/14 11:34:43.000 PM kernel[0]: SMC::smcReadKeyAction ERROR Tp0C kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff800b4c3000
12/1/14 11:34:43.000 PM kernel[0]: SMC::smcReadKeyAction ERROR TB3T kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff800b4c3000
12/1/14 11:34:43.000 PM kernel[0]: SMC::smcReadKeyAction ERROR TN1P kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff800b4c3000
12/1/14 11:34:43.000 PM kernel[0]: SMC::smcReadKeyAction ERROR TN0H kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff800b4c3000
12/1/14 11:34:43.000 PM kernel[0]: SMC::smcReadKeyAction ERROR TM0S kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff800b4c3000
12/1/14 11:34:43.333 PM WindowServer[89]: _CGXSetWindowHasKeyAppearance: Operation on a window 0x16 requiring rights kCGSWindowRightOwner by caller Dashboard
12/1/14 11:34:43.000 PM kernel[0]: SMC::smcReadKeyAction ERROR TM1S kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff800b4c3000
12/1/14 11:34:43.000 PM kernel[0]: SMC::smcReadKeyAction ERROR TM2S kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff800b4c3000
12/1/14 11:34:43.000 PM kernel[0]: SMC::smcReadKeyAction ERROR TM3S kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff800b4c3000
12/1/14 11:34:43.000 PM kernel[0]: SMC::smcReadKeyAction ERROR TM4S kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff800b4c3000
12/1/14 11:34:43.000 PM kernel[0]: SMC::smcReadKeyAction ERROR TM5S kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff800b4c3000
12/1/14 11:34:43.000 PM kernel[0]: SMC::smcReadKeyAction ERROR TM6S kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff800b4c3000
12/1/14 11:34:43.000 PM kernel[0]: SMC::smcReadKeyAction ERROR TM7S kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff800b4c3000
12/1/14 11:34:43.000 PM kernel[0]: SMC::smcReadKeyAction ERROR TM8S kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff800b4c3000
12/1/14 11:34:43.000 PM kernel[0]: SMC::smcReadKeyAction ERROR TM9S kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff800b4c3000
12/1/14 11:34:43.000 PM kernel[0]: SMC::smcReadKeyAction ERROR TMAS kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff800b4c3000
12/1/14 11:34:43.000 PM kernel[0]: SMC::smcReadKeyAction ERROR TMBS kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff800b4c3000
12/1/14 11:34:43.000 PM kernel[0]: SMC::smcReadKeyAction ERROR TMCS kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff800b4c3000
12/1/14 11:34:43.342 PM WindowServer[89]: _CGXSetWindowHasMainAppearance: Operation on a window 0x16 requiring rights kCGSWindowRightOwner by caller Dashboard
12/1/14 11:34:43.000 PM kernel[0]: SMC::smcReadKeyAction ERROR TMDS kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff800b4c3000
12/1/14 11:34:43.000 PM kernel[0]: SMC::smcReadKeyAction ERROR TMES kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff800b4c3000
12/1/14 11:34:43.000 PM kernel[0]: SMC::smcReadKeyAction ERROR TMFS kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff800b4c3000
12/1/14 11:34:43.000 PM kernel[0]: SMC::smcReadKeyAction ERROR TM0P kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff800b4c3000
12/1/14 11:34:43.000 PM kernel[0]: SMC::smcReadKeyAction ERROR TM1P kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff800b4c3000
12/1/14 11:34:43.000 PM kernel[0]: SMC::smcReadKeyAction ERROR TM2P kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff800b4c3000
12/1/14 11:34:43.000 PM kernel[0]: SMC::smcReadKeyAction ERROR TM3P kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff800b4c3000
12/1/14 11:34:43.000 PM kernel[0]: SMC::smcReadKeyAction ERROR TM4P kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff800b4c3000
12/1/14 11:34:43.000 PM kernel[0]: SMC::smcReadKeyAction ERROR TM5P kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff800b4c3000
12/1/14 11:34:43.000 PM kernel[0]: SMC::smcReadKeyAction ERROR TM6P kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff800b4c3000
12/1/14 11:34:43.000 PM kernel[0]: SMC::smcReadKeyAction ERROR TM7P kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff800b4c3000
12/1/14 11:34:43.000 PM kernel[0]: SMC::smcReadKeyAction ERROR TM8P kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff800b4c3000
12/1/14 11:34:43.000 PM kernel[0]: SMC::smcReadKeyAction ERROR TM9P kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff800b4c3000
12/1/14 11:34:43.000 PM kernel[0]: SMC::smcReadKeyAction ERROR TMAP kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff800b4c3000
12/1/14 11:34:43.000 PM kernel[0]: SMC::smcReadKeyAction ERROR TMBP kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff800b4c3000
12/1/14 11:34:43.000 PM kernel[0]: SMC::smcReadKeyAction ERROR TMCP kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff800b4c3000
12/1/14 11:34:43.000 PM kernel[0]: SMC::smcReadKeyAction ERROR TMDP kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff800b4c3000
12/1/14 11:34:43.000 PM kernel[0]: SMC::smcReadKeyAction ERROR TMEP kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff800b4c3000
12/1/14 11:34:43.000 PM kernel[0]: SMC::smcReadKeyAction ERROR TMFP kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff800b4c3000
12/1/14 11:34:43.000 PM kernel[0]: SMC::smcReadKeyAction ERROR Tm0P kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff800b4c3000
12/1/14 11:34:43.000 PM kernel[0]: SMC::smcReadKeyAction ERROR TS0C kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff800b4c3000
12/1/14 11:34:43.000 PM kernel[0]: SMC::smcReadKeyAction ERROR TW0P kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff800b4c3000
12/1/14 11:34:43.000 PM kernel[0]: SMC::smcReadKeyAction ERROR Tp0P kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff800b4c3000
12/1/14 11:34:43.000 PM kernel[0]: SMC::smcReadKeyAction ERROR TA0S kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff800b4c3000
12/1/14 11:34:43.000 PM kernel[0]: SMC::smcReadKeyAction ERROR TA1S kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff800b4c3000
12/1/14 11:34:43.000 PM kernel[0]: SMC::smcReadKeyAction ERROR TA2S kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff800b4c3000
12/1/14 11:34:43.000 PM kernel[0]: SMC::smcReadKeyAction ERROR TA3S kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff800b4c3000
12/1/14 11:34:43.000 PM kernel[0]: SMC::smcReadKeyAction ERROR TA1P kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff800b4c3000
12/1/14 11:34:43.000 PM kernel[0]: SMC::smcReadKeyAction ERROR Tp1P kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff800b4c3000
12/1/14 11:34:43.000 PM kernel[0]: SMC::smcReadKeyAction ERROR Tp2P kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff800b4c3000
12/1/14 11:34:43.000 PM kernel[0]: SMC::smcReadKeyAction ERROR Tp3P kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff800b4c3000
12/1/14 11:34:43.000 PM kernel[0]: SMC::smcReadKeyAction ERROR Tp4P kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff800b4c3000
12/1/14 11:34:43.000 PM kernel[0]: SMC::smcReadKeyAction ERROR Tp5P kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff800b4c3000
12/1/14 11:34:43.000 PM kernel[0]: SMC::smcReadKeyAction ERROR TC0H kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff800b4c3000
12/1/14 11:34:43.000 PM kernel[0]: SMC::smcReadKeyAction ERROR TC1D kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff800b4c3000
12/1/14 11:34:43.000 PM kernel[0]: SMC::smcReadKeyAction ERROR TCAH kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff800b4c3000
12/1/14 11:34:43.000 PM kernel[0]: SMC::smcReadKeyAction ERROR TCBH kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff800b4c3000
12/1/14 11:34:43.000 PM kernel[0]: SMC::smcReadKeyAction ERROR TG0P kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff800b4c3000
12/1/14 11:34:43.000 PM kernel[0]: SMC::smcReadKeyAction ERROR TA0P kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff800b4c3000
12/1/14 11:34:43.000 PM kernel[0]: SMC::smcReadKeyAction ERROR TH0P kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff800b4c3000
12/1/14 11:34:43.000 PM kernel[0]: SMC::smcReadKeyAction ERROR TO0P kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff800b4c3000
12/1/14 11:34:43.000 PM kernel[0]: SMC::smcReadKeyAction ERROR TH1P kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff800b4c3000
12/1/14 11:34:43.000 PM kernel[0]: SMC::smcReadKeyAction ERROR TH2P kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff800b4c3000
12/1/14 11:34:43.000 PM kernel[0]: SMC::smcReadKeyAction ERROR TH3P kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff800b4c3000
12/1/14 11:34:43.000 PM kernel[0]: SMC::smcReadKeyAction ERROR Th0H kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff800b4c3000
12/1/14 11:34:43.000 PM kernel[0]: SMC::smcReadKeyAction ERROR Th2H kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff800b4c3000
12/1/14 11:34:43.000 PM kernel[0]: SMC::smcReadKeyAction ERROR TG0H kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff800b4c3000
12/1/14 11:34:43.000 PM kernel[0]: SMC::smcReadKeyAction ERROR TG1H kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff800b4c3000
12/1/14 11:34:43.000 PM kernel[0]: SMC::smcReadKeyAction ERROR TG0D kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff800b4c3000
12/1/14 11:34:43.000 PM kernel[0]: SMC::smcReadKeyAction ERROR Tp1C kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff800b4c3000
12/1/14 11:34:43.000 PM kernel[0]: SMC::smcReadKeyAction ERROR Tp0C kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff800b4c3000
12/1/14 11:34:43.000 PM kernel[0]: SMC::smcReadKeyAction ERROR TB3T kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff800b4c3000
12/1/14 11:34:43.000 PM kernel[0]: SMC::smcReadKeyAction ERROR TN1P kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff800b4c3000
12/1/14 11:34:43.000 PM kernel[0]: SMC::smcReadKeyAction ERROR TN0H kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff800b4c3000
12/1/14 11:34:43.000 PM kernel[0]: SMC::smcReadKeyAction ERROR TM0S kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff800b4c3000
12/1/14 11:34:43.000 PM kernel[0]: SMC::smcReadKeyAction ERROR TM1S kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff800b4c3000
12/1/14 11:34:43.000 PM kernel[0]: SMC::smcReadKeyAction ERROR TM2S kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff800b4c3000
12/1/14 11:34:43.000 PM kernel[0]: SMC::smcReadKeyAction ERROR TM3S kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff800b4c3000
12/1/14 11:34:43.000 PM kernel[0]: SMC::smcReadKeyAction ERROR TM4S kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff800b4c3000
12/1/14 11:34:43.000 PM kernel[0]: SMC::smcReadKeyAction ERROR TM5S kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff800b4c3000
12/1/14 11:34:43.000 PM kernel[0]: SMC::smcReadKeyAction ERROR TM6S kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff800b4c3000
12/1/14 11:34:43.000 PM kernel[0]: SMC::smcReadKeyAction ERROR TM7S kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff800b4c3000
12/1/14 11:34:43.000 PM kernel[0]: SMC::smcReadKeyAction ERROR TM8S kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff800b4c3000
12/1/14 11:34:43.000 PM kernel[0]: SMC::smcReadKeyAction ERROR TM9S kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff800b4c3000
12/1/14 11:34:43.000 PM kernel[0]: SMC::smcReadKeyAction ERROR TMAS kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff800b4c3000
12/1/14 11:34:43.000 PM kernel[0]: SMC::smcReadKeyAction ERROR TMBS kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff800b4c3000
12/1/14 11:34:43.000 PM kernel[0]: SMC::smcReadKeyAction ERROR TMCS kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff800b4c3000
12/1/14 11:34:43.000 PM kernel[0]: SMC::smcReadKeyAction ERROR TMDS kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff800b4c3000
12/1/14 11:34:43.000 PM kernel[0]: SMC::smcReadKeyAction ERROR TMES kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff800b4c3000
12/1/14 11:34:43.000 PM kernel[0]: SMC::smcReadKeyAction ERROR TMFS kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff800b4c3000
12/1/14 11:34:43.000 PM kernel[0]: SMC::smcReadKeyAction ERROR TM0P kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff800b4c3000
12/1/14 11:34:43.000 PM kernel[0]: SMC::smcReadKeyAction ERROR TM1P kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff800b4c3000
12/1/14 11:34:43.000 PM kernel[0]: SMC::smcReadKeyAction ERROR TM2P kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff800b4c3000
12/1/14 11:34:43.000 PM kernel[0]: SMC::smcReadKeyAction ERROR TM3P kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff800b4c3000
12/1/14 11:34:43.000 PM kernel[0]: SMC::smcReadKeyAction ERROR TM4P kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff800b4c3000
12/1/14 11:34:43.000 PM kernel[0]: SMC::smcReadKeyAction ERROR TM5P kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff800b4c3000
12/1/14 11:34:43.000 PM kernel[0]: SMC::smcReadKeyAction ERROR TM6P kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff800b4c3000
12/1/14 11:34:43.000 PM kernel[0]: SMC::smcReadKeyAction ERROR TM7P kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff800b4c3000
12/1/14 11:34:43.000 PM kernel[0]: SMC::smcReadKeyAction ERROR TM8P kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff800b4c3000
12/1/14 11:34:43.000 PM kernel[0]: SMC::smcReadKeyAction ERROR TM9P kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff800b4c3000
12/1/14 11:34:43.000 PM kernel[0]: SMC::smcReadKeyAction ERROR TMAP kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff800b4c3000
12/1/14 11:34:43.000 PM kernel[0]: SMC::smcReadKeyAction ERROR TMBP kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff800b4c3000
12/1/14 11:34:43.000 PM kernel[0]: SMC::smcReadKeyAction ERROR TMCP kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff800b4c3000
12/1/14 11:34:43.000 PM kernel[0]: SMC::smcReadKeyAction ERROR TMDP kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff800b4c3000
12/1/14 11:34:43.000 PM kernel[0]: SMC::smcReadKeyAction ERROR TMEP kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff800b4c3000
12/1/14 11:34:43.000 PM kernel[0]: SMC::smcReadKeyAction ERROR TMFP kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff800b4c3000
12/1/14 11:34:43.000 PM kernel[0]: SMC::smcReadKeyAction ERROR Tm0P kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff800b4c3000
12/1/14 11:34:43.000 PM kernel[0]: SMC::smcReadKeyAction ERROR TS0C kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff800b4c3000
12/1/14 11:34:43.000 PM kernel[0]: SMC::smcReadKeyAction ERROR TW0P kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff800b4c3000
12/1/14 11:34:43.000 PM kernel[0]: SMC::smcReadKeyAction ERROR Tp0P kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff800b4c3000
12/1/14 11:34:43.000 PM kernel[0]: SMC::smcReadKeyAction ERROR TA0S kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff800b4c3000
12/1/14 11:34:43.000 PM kernel[0]: SMC::smcReadKeyAction ERROR TA1S kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff800b4c3000
12/1/14 11:34:43.000 PM kernel[0]: SMC::smcReadKeyAction ERROR TA2S kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff800b4c3000
12/1/14 11:34:43.000 PM kernel[0]: SMC::smcReadKeyAction ERROR TA3S kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff800b4c3000
12/1/14 11:34:43.000 PM kernel[0]: SMC::smcReadKeyAction ERROR TA1P kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff800b4c3000
12/1/14 11:34:43.000 PM kernel[0]: SMC::smcReadKeyAction ERROR Tp1P kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff800b4c3000
12/1/14 11:34:43.000 PM kernel[0]: SMC::smcReadKeyAction ERROR Tp2P kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff800b4c3000
12/1/14 11:34:43.000 PM kernel[0]: SMC::smcReadKeyAction ERROR Tp3P kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff800b4c3000
12/1/14 11:34:43.000 PM kernel[0]: SMC::smcReadKeyAction ERROR Tp4P kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff800b4c3000
12/1/14 11:34:43.000 PM kernel[0]: SMC::smcReadKeyAction ERROR Tp5P kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff800b4c3000
12/1/14 11:34:46.080 PM configd[17]: network changed: DNS* Proxy
12/1/14 11:34:46.080 PM UserEventAgent[11]: Captive: [CNInfoNetworkActive:1655] en1: SSID 'IU Secure' making interface primary (cache indicates network not captive)
12/1/14 11:34:46.081 PM UserEventAgent[11]: Captive: CNPluginHandler en1: Evaluating
12/1/14 11:34:46.083 PM UserEventAgent[11]: Captive: en1: Not probing 'IU Secure' (cache indicates not captive)
12/1/14 11:34:46.084 PM UserEventAgent[11]: Captive: CNPluginHandler en1: Authenticated
12/1/14 11:34:46.090 PM configd[17]: network changed: v4(en1!:149.160.140.195) DNS+ Proxy+ SMB+
12/1/14 11:34:46.109 PM configd[17]: setting hostname to "149-160-140-195.dhcp-bl.indiana.edu"
12/1/14 11:34:47.185 PM apsd[78]: Unrecognized leaf certificate
12/1/14 11:34:50.353 PM CalendarAgent[161]: [com.apple.calendar.store.log.ICS] [ICS Error for file: BEGIN:VCALENDAR
VERSION:2.0
There was an extremely long list of iCal Events on here due to the entire 82 game Indiana Pacers schedule.
12/1/14 11:34:50.371 PM CalendarAgent[161]: [com.apple.calendar.store.log.ICS] [Invalid address property:CN=Pacers Schedule 2014-2015]
12/1/14 11:34:50.371 PM CalendarAgent[161]: [com.apple.calendar.store.log.ICS] [Invalid address property:CN=Pacers Schedule 2014-2015]
12/1/14 11:34:50.371 PM CalendarAgent[161]: [com.apple.calendar.store.log.ICS] [Invalid address property:CN=Pacers Schedule 2014-2015]
12/1/14 11:34:50.372 PM CalendarAgent[161]: [com.apple.calendar.store.log.ICS] [Invalid address property:CN=Pacers Schedule 2014-2015]
12/1/14 11:34:50.372 PM CalendarAgent[161]: [com.apple.calendar.store.log.ICS] [Hit Max ICS log messages for file! (200)]
12/1/14 11:34:50.373 PM CalendarAgent[161]: [com.apple.calendar.store.log.ICS] [Invalid address property:CN=Pacers Schedule 2014-2015]
12/1/14 11:34:51.223 PM digest-service[414]: digest-request: uid=0
12/1/14 11:34:51.224 PM digest-service[414]: digest-request: init request
12/1/14 11:34:51.228 PM digest-service[414]: digest-request: init return domain: MACBOOKPRO-EE1C server: 149-160-140-195 indomain was: <NULL>
12/1/14 11:34:51.248 PM digest-service[414]: digest-request: uid=0
12/1/14 11:34:51.248 PM digest-service[414]: digest-request: init request
12/1/14 11:34:51.257 PM digest-service[414]: digest-request: init return domain: 149-160-140-195 server: 149-160-140-195 indomain was: <NULL>
12/1/14 11:34:51.409 PM sandboxd[268]: ([495]) netbiosd(495) deny mach-lookup com.apple.networkd
12/1/14 11:34:52.024 PM AirPlayUIAgent[230]: 2014-12-01 11:34:52.024264 PM [AirPlayUIAgent] Changed PIN pairing: no
12/1/14 11:34:52.029 PM AirPlayUIAgent[230]: 2014-12-01 11:34:52.029266 PM [AirPlayUIAgent] Changed PIN pairing: no
12/1/14 11:34:52.690 PM AddressBookSourceSync[482]: *** -[IADomainCache init]: IA domains cache couldn't be read.
12/1/14 11:34:52.691 PM AddressBookSourceSync[482]: -[IAPluginManager allAListPlugins] [546] -- *** warning: we're on the slow path.
12/1/14 11:34:59.544 PM configd[17]: network changed: v4(en1:149.160.140.195) v6(en1+:2001:18e8:2:28c2:f000::244) DNS! Proxy SMB
12/1/14 11:35:05.517 PM Console[505]: setPresentationOptions called with NSApplicationPresentationFullScreen when there is no visible fullscreen window; this call will be ignored.
12/1/14 11:35:06.850 PM WindowServer[89]: disable_update_timeout: UI updates were forcibly disabled by application "Console" for over 1.00 seconds. Server has re-enabled them.
12/1/14 11:35:07.004 PM WindowServer[89]: common_reenable_update: UI updates were finally reenabled by application "Console" after 1.15 seconds (server forcibly re-enabled them after 1.00 seconds)
12/1/14 11:35:09.487 PM com.apple.SecurityServer[15]: Killing auth hosts
12/1/14 11:35:09.487 PM com.apple.SecurityServer[15]: Session 100026 destroyed
12/1/14 11:35:09.491 PM com.apple.SecurityServer[15]: Session 100027 created
12/1/14 11:35:11.470 PM netbiosd[495]: name servers down?
12/1/14 11:35:15.465 PM loginwindow[58]: CoreAnimation: warning, deleted thread with uncommitted CATransaction; set CA_DEBUG_TRANSACTIONS=1 in environment to log backtraces.

How do I recover data from my macbook pro with a disk that can't be repaired?

I'm in need of a data recovery solution. My Macbook pro (17") running OS X Mountain Lion won't boot and is stuck on the gray startup screen with the apple icon and spinning gear and disk utility states "Error: Utility can't repair this disk. Back up as many of your files as possible, reformat the disk, and restore your backed-up files." Unfortunately, I don't have a back up and don't know how to access or back up the data on my drive. Mounting it to another computer as an external drive via firewire did not work. Does anyone know of any solutions to extract the data from my macbook pro hard drive before I reformat it? Any help would be greatly appreciated.

Hi there
I really am sorry about your problem. I have opened up my help centre and it too states '[...]back up as much of your data as possible, reformat the disk, reinstall OS X, and then restore your backed-up data'. It then says: If you continue to have problems with your disk, it may be physically damaged and need to be replaced.
I just noticed it says reinstall OS X. If it says this then this indicates a rather serious computing problem.
Help centre also states: If Disk Utility reports “overlapped extent allocation” errors, two or more files occupy the same space on your disk, and at least one of them is likely to be corrupted. [The next step is the following] Check each file in the list of affected files. [added by me]
A damage disk causes files to be corrupted. Also you can repair a disk by deleting corrupt files (i.e. one can still use a damaged disk providing it has been repaired). Disk Utility is able to help to repair corruption problems but not if your program files have become corrupted due to large-scale damaged disk.
I understand why you want to connect to another hard disk because you want to extract your files and I would probably do the same. I am on a 13-inch Macbook Pro trying to solve your problem.

Billing Problem that can't seemed to be resolved by anyone

So I started a family plan with Verizon about 2 weeks ago. We got a two iPhone 5s ($550) and a single iPhone6($650), price per the Verizon website. We got charged for the equivalent of 2 iPhone6 and 1 iPhone5, $100 overcharged. I called Verizon to get this problem resolved, they informed me that since I started my plan through a retailer, I need to go to a Verizon store to resolve my problem. I went to the Verizon store, they agreed my bill was incorrect, but told me they weren't able to change it because I started the plan through a retailer who wasn't a Verizon store. I call Verizon back, tell them what the Verizon brick and mortar store told me, and they told me they aren't able to correct it, and that I should contact the store directly.
I call the store where I started the plan, the customer rep remembered me and I told him my problem, he said it must have been a mistake, and that he'd look into the problem for me. 3 days later, no call back, I call them. I get the store manager, who tells me that the billing was correct, that they charged me less for one and more for the other to balance the cost. WHAT?! Now I understand that retail stores can jack up the prices of the phones and the cost might not be the same as advertised on the Verizon website, but the sales rep admitted the mistake, and the way the manager explained the inconsistent bill simply makes no sense. The sales rep admitted he made a mistake, the manager wouldn't correct the bill. She offered me $100 store credit to offset the difference. Useless, I did the deal in LA, but live in San Diego.
Seems like no one can/want to help me, a mistake was made but I'm paying for it.

This is entirely with the store you bought it from. Go to the corporate office customer relations for that company. I have to agree with Verizon here, there is not much they can do.

After downloading Firefox onto my pc I have been unable to open my AOL. Saw online that others have had this problem. Can it be resolved? If not I need to remove Firefox.

I was having trouble with downloads on Explorer and in the process of resolving the issue with Microsoft support over the phone we tested the solution by downloading itunes and firefox. That was two days ago and I have not been able to open my AOL from the icon on my screen. Explorer is ok and I can access AOL through that search engine. I read online that others have had the same problem after downloading Firefox.

Clear the cache and the cookies from sites that cause problems.
"Clear the Cache":
*Tools > Options > Advanced > Network > Cached Web Content: "Clear Now"
"Remove Cookies" from sites causing problems:
*Tools > Options > Privacy > Cookies: "Show Cookies"
Start Firefox in <u>[[Safe Mode|Safe Mode]]</u> to check if one of the extensions (Firefox/Tools > Add-ons > Extensions) or if hardware acceleration is causing the problem (switch to the DEFAULT theme: Firefox/Tools > Add-ons > Appearance).
*Do NOT click the Reset button on the Safe mode start window or otherwise make changes.
*https://support.mozilla.org/kb/Safe+Mode
*https://support.mozilla.org/kb/Troubleshooting+extensions+and+themes
See also:
*http://kb.mozillazine.org/Error_loading_websites
You can try to reset (power off/on) the router.

Disk utility states: This drive has hardware problem that can't be repaired, backup and replace disk.

iMac is within warrenty.

quince88 wrote:
Sorry running 10.6.8, did everthing except Restore Vol, including Tech Tool Deluxe with Drive Hardware test 'Failed' and under Disk Utility S.M.A.R.T. status 'Failing.' I am in Thailand so off to the Apple people on Sat. Thanks for the help.
I think that is a wise choice!
Good luck and btw I hope you have a good backup, if you do use Setup Assistant to restore so you can pick up from where you left off. You should use Pondini's Snow Leopard Setup Assistant tips it will show exactly what needs to be done. If the Apple people are going to install SL for you make sure you give them your backup so they can restore for you.

Slate 21 Pro ongoing sleep problems that can't be resolved

Similar Messages

Maybe you are looking for