Power supply related log entries?
(This question was posted all day yesterday, with no replies, in the iMac G5 forum. Perhaps someone here will have some idea what these logs mean in this situation.)
I recently had the PSU and the Logic Board replaced (two tries to get it right) for the sudden shutdown/ defective capacitor issue. Everything, fingers crossed, seems to be functioning properly, at least, so far. But, now that I'm completely paranoid about this issue, I've noticed log entries "AppleSMU -- shutdown cause = 1" or "AppleSMU -- shutdown cause = 2" (at least, not the dreaded = -110) in the log just after bootup. I know these are often related to the PSU issue and, since my shutdowns have been normal, I don't understand why they are appearing or what they mean.
Here's the latest log from after an SMU reset. (Rebooted after that and only got the usual "shutdown cause =1.") The message in question is in bold. Should I be thinking of a corrupted cache, or is this a possible indication that the latest PSU is also on the way out? My shutdowns (as well as everything else, +so far+) appear to be normal, but this entry "localhost kernel[0]: AppleSMU -- shutdown cause = -110," is the log I was getting from when the computer was shutting down all the time, which is very strange. Thanks for any help.
Nov 19 23:23:14 Macintosh-3 shutdown[644]: SHUTDOWN_TIME: 1258690994 83525
Nov 19 23:23:14 Macintosh-3 com.apple.loginwindow[27]: Shutdown NOW!
Nov 19 23:23:14 Macintosh-3 com.apple.loginwindow[27]: System shutdown time has arrived^G^G
Nov 19 23:23:14 Macintosh-3 mDNSResponder mDNSResponder-176.3 (Jan 27 2009 14:51:59)[26]: stopping
Nov 19 23:23:14 Macintosh-3 com.apple.SystemStarter[20]: Stopping HP Trap Monitor
Nov 19 23:23:14 Macintosh-3 com.apple.SystemStarter[20]: Stopping HP IO Monitor
Nov 19 23:23:14 Macintosh-3 com.apple.usbmuxd[18]: stopping.
Nov 20 06:56:40 localhost kernel[0]: Darwin Kernel Version 9.8.0: Wed Jul 15 16:57:01 PDT 2009; root:xnu-1228.15.4~1/RELEASE_PPC
Nov 20 06:56:34 localhost com.apple.launchctl.System[2]: /dev/disk0s3 on / (hfs, local, journaled)
Nov 20 06:56:37 localhost com.apple.launchctl.System[2]: launchctl: Please convert the following to launchd: /etc/mach_init.d/dashboardadvisoryd.plist
Nov 20 06:56:37 localhost com.apple.launchd[1] (com.apple.usbmuxd): Unknown key for boolean: EnableTransactions
Nov 20 06:56:37 localhost com.apple.launchd[1] (org.cups.cupsd): Unknown key: SHAuthorizationRight
Nov 20 06:56:37 localhost com.apple.launchd[1] (org.ntp.ntpd): Unknown key: SHAuthorizationRight
Nov 20 06:56:37 localhost com.apple.launchd[1] (org.x.privileged_startx): Unknown key for boolean: EnableTransactions
Nov 20 06:56:39 localhost kextd[12]: 428 cached, 0 uncached personalities to catalog
Nov 20 06:56:40 localhost kernel[0]: standard timeslicing quantum is 10000 us
Nov 20 06:56:40 localhost kernel[0]: vmpagebootstrap: 313347 free pages and 14333 wired pages
Nov 20 06:56:40 localhost kernel[0]: migtable_maxdispl = 79
Nov 20 06:56:40 localhost kernel[0]: 103 prelinked modules
Nov 20 06:56:40 localhost kernel[0]: Loading security extension com.apple.security.TMSafetyNet
Nov 20 06:56:40 localhost kernel[0]: calling mpopolicyinit for TMSafetyNet
Nov 20 06:56:40 localhost kernel[0]: Security policy loaded: Safety net for Time Machine (TMSafetyNet)
Nov 20 06:56:40 localhost kernel[0]: Loading security extension com.apple.nke.applicationfirewall
Nov 20 06:56:40 localhost kernel[0]: Loading security extension com.apple.security.seatbelt
Nov 20 06:56:40 localhost kernel[0]: calling mpopolicyinit for mb
Nov 20 06:56:40 localhost kernel[0]: Seatbelt MACF policy initialized
Nov 20 06:56:40 localhost kernel[0]: Security policy loaded: Seatbelt Policy (mb)
Nov 20 06:56:40 localhost kernel[0]: Copyright (c) 1982, 1986, 1989, 1991, 1993
Nov 20 06:56:40 localhost kernel[0]: The Regents of the University of California. All rights reserved.
Nov 20 06:56:40 localhost kernel[0]: MAC Framework successfully initialized
Nov 20 06:56:40 localhost kernel[0]: using 6553 buffer headers and 4096 cluster IO buffer headers
Nov 20 06:56:40 localhost kernel[0]: AirPort_Brcm43xx::probe: 02956680, 0
Nov 20 06:56:40 localhost kernel[0]: AppleKauaiATA shasta-ata features enabled
Nov 20 06:56:40 localhost kernel[0]: DART enabled
Nov 20 06:56:40 localhost kernel[0]: FireWire (OHCI) Apple ID 52 PCI now active, GUID 001124fffe343a86; max speed s400.
Nov 20 06:56:40 localhost kernel[0]: mbinit: done
Nov 20 06:56:40 localhost kernel[0]: Security auditing service present
Nov 20 06:56:40 localhost kernel[0]: BSM auditing present
Nov 20 06:56:40 localhost kernel[0]: rooting via boot-uuid from /chosen: 06DF991F-E8CC-32A4-B78C-1791214651DE
Nov 20 06:56:40 localhost kernel[0]: Waiting on <dict ID="0"><key>IOProviderClass</key><string ID="1">IOResources</string><key>IOResourceMatch</key><string ID="2">boot-uuid-media</string></dict>
*Nov 20 06:56:40 localhost kernel[0]: AppleSMU -- shutdown cause = -110*
Nov 20 06:56:40 localhost kernel[0]: wl0: Broadcom BCM4320 802.11 Wireless Controller
Nov 20 06:56:40 localhost kernel[0]: 4.170.25.8.2Got boot device = IOService:/MacRISC4PE/ht@0,f2000000/AppleMacRiscHT/pci@3/IOPCI2PCIBridge/k2-sat a-root@C/AppleK2SATARoot/k2-sata@0/AppleK2SATA/ATADeviceNub@0/AppleATADiskDriver /IOATABlockStorageDevice/IOBlockStorageDriver/WDC WD800JD-40GBB2 WDC WD800JD-40GBB2/IOApplePartitionScheme/Untitled@3
Nov 20 06:56:40 localhost kernel[0]: BSD root: disk0s3, major 14, minor 2
Nov 20 06:56:40 localhost kernel[0]: AppleSMU::PMU vers = 0x000d004c, SPU vers = 0x15, SDB vers = 0x01,
Nov 20 06:56:40 localhost kernel[0]: Jettisoning kernel linker.
Nov 20 06:56:40 localhost kernel[0]: Resetting IOCatalogue.
Nov 20 06:56:40 localhost kernel[0]: Matching service count = 1
Nov 20 06:56:40 localhost kernel[0]: Matching service count = 3
Nov 20 06:56:40: --- last message repeated 4 times ---
Nov 20 06:56:40 localhost kernel[0]: Matching service count = 4
Nov 20 06:56:40 localhost kernel[0]: NVDANV30HAL loaded and registered.
Nov 20 06:56:40 localhost kernel[0]: PowerMac8,1: stalling for module
Nov 20 06:56:42 localhost bootlog[40]: BOOT_TIME: 1258718192 0
Nov 20 06:56:42 localhost fseventsd[31]: bumping event counter to: 0x1d08d5e (current 0x0) from log file '0000000001d0337a'
Nov 20 06:56:43 localhost kernel[0]: IPv6 packet filtering initialized, default to accept, logging disabled
Nov 20 06:56:46 localhost kernel[0]: Matching service count = 1
Nov 20 06:56:46 localhost DirectoryService[36]: Launched version 5.7 (v514.25)
Nov 20 06:56:47 localhost kernel[0]: PowerMac81SystemFansCtrlLoop::calculateNewTarget() linkedControl not ready
Nov 20 06:56:47 localhost /System/Library/CoreServices/loginwindow.app/Contents/MacOS/loginwindow[27]: Login Window Application Started -- Threaded auth
Nov 20 06:56:47 localhost rpc.statd[22]: statd.notify - no notifications needed
Nov 20 06:56:47 localhost kernel[0]: UniNEnet: Ethernet address 00:11:24:34:3a:86
Nov 20 06:56:48 localhost kernel[0]: AirPort_Brcm43xx: Ethernet address 00:0a:95:f4:79:08
Nov 20 06:56:49 localhost iStatLocalDaemon[45]: Waiting for connections on port 5204.
Nov 20 06:56:50 localhost mDNSResponder mDNSResponder-176.3 (Jan 27 2009 14:51:59)[26]: starting
Nov 20 06:56:50 localhost com.apple.usbmuxd[18]: usbmuxd-176 built for iTunesNine on Jul 20 2009 at 13:06:53, running 32 bit
Nov 20 06:56:51 localhost com.paceap.pacesupport[44]: kextload: extension /System/Library/Extensions/PACESupportFamily.kext/Contents/PlugIns/PACESupportL eopard.kext is already loaded
Nov 20 06:56:52 localhost /usr/sbin/ocspd[67]: starting
Nov 20 06:56:55 localhost loginwindow[27]: Login Window Started Security Agent
Nov 20 06:56:57 localhost kernel[0]: AirPort: Link Down on en1
Nov 20 06:56:57 localhost kextd[12]: writing kernel link data to /var/run/mach.sym
Nov 20 06:56:58 Macintosh-3 configd[38]: setting hostname to "Macintosh-3.local"
Nov 20 06:56:59 Macintosh-3 kernel[0]: AirPort: Link Up on en1
Nov 20 06:56:59 Macintosh-3 kernel[0]: SetCryptoKey T: len 16, idx 0
Nov 20 06:56:59 Macintosh-3 kernel[0]: SetCryptoKey R: len 32, idx 2
Nov 20 06:57:02 Macintosh-3 com.apple.SystemStarter[20]: PACESupport - launchd already started us
Nov 20 06:57:02 Macintosh-3 com.apple.SystemStarter[20]: Starting HP IO Monitor
Nov 20 06:57:02 Macintosh-3 com.apple.SystemStarter[20]: Starting HP Trap Monitor
Nov 20 06:57:26 Macintosh-3 SecurityAgent[82]: NSExceptionHandler has recorded the following exception:\nNSRangeException -- * -[NSCFArray objectAtIndex:]: index (0) beyond bounds (0)\nStack trace: 0x39dbc 0x9329a4ec 0x92303c00 0x92303c38 0x90448180 0x709c8 0x5bee4 0x6edd8 0x637b4 0x649c4 0x6c678 0x9140c358 0x9140c28c 0x9144dc94 0x9144c0f4 0x914092dc 0x74764 0x913dc680 0x913498d8 0x11e14 0x2db0
Nov 20 06:57:33 Macintosh-3 authorizationhost[81]: MechanismInvoke 0x12d5f0 retainCount 2
Nov 20 06:57:34 Macintosh-3 SecurityAgent[82]: MechanismInvoke 0x101660 retainCount 1
Nov 20 06:57:34 Macintosh-3 SecurityAgent[82]: NSSecureTextFieldCell detected a field editor ((null)) that is not a NSTextView subclass designed to work with the cell. Ignoring...
Nov 20 06:57:34 Macintosh-3 SecurityAgent[82]: NSExceptionHandler has recorded the following exception:\nNSRangeException -- * -[NSCFArray objectAtIndex:]: index (0) beyond bounds (0)\nStack trace: 0x39dbc 0x9329a4ec 0x92303c00 0x92303c38 0x90448180 0x709c8 0x5bee4 0x6edd8 0x637b4 0x68368 0x774a4 0xe068 0x14200 0x13f64 0xdb58 0x9047f8f0 0x9227426c 0x92296634 0x900bbb18 0x900bb93c 0x900bb77c 0x91350248 0x9134fc00 0x913498a0 0x11e14 0x2db0
Nov 20 06:57:34 Macintosh-3 loginwindow[27]: Login Window - Returned from Security Agent
Nov 20 06:57:34 Macintosh-3 SecurityAgent[82]: MechanismDestroy 0x101660 retainCount 1
Nov 20 06:57:34 Macintosh-3 authorizationhost[81]: MechanismDestroy 0x12d5f0 retainCount 2
Nov 20 06:57:34 Macintosh-3 loginwindow[27]: USER_PROCESS: 27 console
Nov 20 06:57:34 Macintosh-3 com.apple.launchd[1] (com.apple.UserEventAgent-LoginWindow[80]): Exited: Terminated
Nov 20 06:57:34 Macintosh-3 com.apple.launchctl.Aqua[110]: launchctl: Couldn't stat("/etc/machinit_peruser.d"): No such file or directory
Nov 20 06:57:34 Macintosh-3 com.apple.launchd[107] (com.apple.AirPortBaseStationAgent): Unknown key for boolean: EnableTransactions
Nov 20 06:57:34 Macintosh-3 com.apple.launchd[107] (org.x.startx): Unknown key for boolean: EnableTransactions
Nov 20 06:57:35 Macintosh-3 com.apple.launchd[1] (com.apple.aslmanager): Throttling respawn: Will start in 2 seconds
Nov 20 06:57:42 Macintosh-3 /System/Library/CoreServices/coreservicesd[51]: SFLSharePointsEntry::CreateDSRecord: dsCreateRecordAndOpen(.... Public Folder) returned -14135
Nov 20 06:57:49 Macintosh-3 SystemUIServer[125]: MenuCracker 2.0 (/Library/Application Support/iStat local/extras/MenuCracker.menu)\n See http://sourceforge.net/projects/menucracker\n MenuCracker is now loaded. Ready to accept new menu extras. Ignore the failure message that follows.
Nov 20 06:57:49 Macintosh-3 SystemUIServer[125]: failed to instantiate and get the principal class of bundle: NSBundle </Library/Application Support/iStat local/extras/MenuCracker.menu> (loaded)
Nov 20 06:57:49 Macintosh-3 SystemUIServer[125]: MenuCracker: Allowing "iStatMenusCPU".
Nov 20 06:57:49 Macintosh-3 SystemUIServer[125]: MenuCracker: Allowing "iStatMenusDisks".
Nov 20 06:57:50 Macintosh-3 SystemUIServer[125]: MenuCracker: Allowing "iStatMenusMemory".
Nov 20 06:57:50 Macintosh-3 SystemUIServer[125]: MenuCracker: Allowing "iStatMenusNetwork".
Nov 20 06:57:50 Macintosh-3 SystemUIServer[125]: MenuCracker: Allowing "iStatMenusTemps".
Message was edited by: WZZZ
Similar Messages
-
Storage Tek 6140 - Power supply event
Goodmorning,
I found an event during my routine checks relating to a tray power supply.
The event is:
Severity: Major
Date: 14-Jan-2010 4.02.14
Actionable: No
+Description: Jan 14 04:02:14 GALAXY Tray.3 (Power Supply): [ID 0x280D] NOTICE: Drive tray component failed or removed +
Data: Drive tray component failed or removed
Component: Tray.3 (Power Supply)
Type: Log
Info:
Event Code: 57.20.461
Aggregated Yes
As a probable cause I have this info:
This event was triggered by a logfile entry that a component has
failed.
A corresponding StateChangeEvent should have also been triggered.
And as a recommended action I have:
+1. Follow the Recommended Action in the corresponding+
StateChangeEvent.
+2. If no StateChangeEvent is present. Follow the appropriate Service+
Procedure for replacing the indicated component.
After this log, another info is mentioned in CAM events:
Monitor device event:
Severity: Minor
Date: 14-Jan-2010 9.26.45
Actionable: No
Description: Finished monitoring run for device. Completed with 0 event(s).
Data: Monitoring device GALAXY
Gathering log messages for GALAXY
No events created for GALAXY
Creating health messages for GALAXY
Saving GALAXY data...
Finished saving GALAXY data.
+ +
Component: GALAXY
Type: MonitorDeviceEvent
Info:
Event Code: 57.69.16
Aggregated No
Galaxy is the name of my storage tek. I checked the health status of the tray and it is OK. Also led status is green.
I would say if the first event can be alarming also after the second event.
ThanksHi.
1. Disk should be work normal. In case failure - should be replaced by hotspare automaticaly.
2. You can't clear this alarm. You cant' install base FW on this disk. ( CAM can't do downgrade FW).
For clear alarm you can install latest CAM + patches and Install Baseline FW on Array ( Arrays).
I don't remember from CAM 6.6 or 6.7 CAM don't set alarm in case disk firmware mismatch.
3. CAM don't have own password database. It use system password database. Change password for user on system where CAM is installed.
( In case Solaris - passwd <username>
Regards. -
Power supply fan dead - help? (400mhz AGP G4)
Hello!
Unfortunately, my PowerMac G4, a 400mhz, AGP Sawtooth model, has a dead fan.
Over the last few weeks, I've noticed that my G4 has been running quite hot. I figured it was due to the hot dorm room that it's being used in. Then, I noticed that when it booted up, it would occasionally make a vibrating, or rattling noise - I figured the fan was wobbling. Since air was comming out of the fan opening at the top, I didn't worry about it.
Today, I used the "Temperature Monitor" widget to check the temperature of my SMART Hard drive (the G4 itself is not sensed). It was 133 degrees!!! This is the bay on the back-right, just under the CPU fan. I looked at the fan again - not much airflow. I pulled out a flashlight and pointed it in, and the Fan that's inside the power supply unit is dead.
So, how can I fix it? It's far far too hot, so it's not usable until I can cool it off. The first idea I had was to take a particularly powerful desk fan, and make a paper "tube" that connects both to the G4 and back of the fan - so it'll pull the hot air out. Needless to say, this is not a good log-term plan as it's easy to fall apart and will have leaks, but it works for now. I realize you can buy power supplies, but for ~$100, it's far too much for the old G4.
Second idea: The fan is inside the "non-user servicable" power supply, but it's also next to the back of the G4 - right inside what appears to be a panel that holds the power supply in. At the very least, I'd like to make sure that the cable is attached and not loose, but I have to open the back. Is that possible or safe? If so, can I replace the fan?
My third idea was to attach an extra fan to the inside of the G4, on the outside of the power supply - pushing in. Unfortunately, the IDE cable from the DVD drive is in the way, and there's not much room for a fan. Plus, there's no fan power supply. Is it possible to convert an ATA power plug (there are 7!) to a fan-power supply? I'd require a small circuit and a lot of resistors, obviously! If so, what would I need to do to convert it?
Thanks a bunch,
-Dan
15" 1.67 Powerbook G4 (Jan 2005), 400 mhz AGP Sawtooth G4 Mac OS X (10.4.8) 4G Clickwheel and 5G Vid iPods, 2G iPod shuffleThanks!
Interesting, this "Piggy back power adapter" will allow me to plug the fan into one of the ATA/IDE cables? Or do you mean the extra port on the power supply? (it has one plug for the outlet>G4, then another to support something like a monitor or similar) The G4 has a DVD burner, but no ZIP drive, so this is quite do-able if it uses the ATA power.
When you say "lower rear", do you mean at the bottom? Below the power supply, to the right of the PCI slots? If so, this is the inflow for the CPU fan! I can understand mounting it outside the current outflow-vent for the dead power supply fan, although I'm not sure the best way to proceed with attaching the fan.
Another question: what tools and supplies will I need? I may need to remove the plastic cover on the back of the G4 - the one that is outside the power supply - as there's a gap between the gray plastic and metal chassis that lets air from outside the machine come in. The screws for this cover use a funky, hexagonal screwdriver. If I need to take this cover off, what kind of screwdriver will I need? Also, should the fan not include screws/etc, what's the best method to attach it? Glue?
Secondly, to cut a hole in the G4, will I need some variety of drill? I don't have one, so i'll have to borrow one... Since there's nothing in the ZIP slot, I can run a cable out through here (assuming it's long enough), and make a new bezel to keep the airflow inside intact.
Ah! One other (somewhat related) question: my USB 2 card includes a power adapter, for use when several un-powered devices (flash drives) are attached. It works just fine with a flash drive and a small media reader, but it's slow to sense the drives - I think it's low on power. Unfortunately, this power plug uses the same variety of plug as the floppy disk drives found on many win-boxes - of which the G4 possesses none. Is there an adapter/cable for this purpose?
Thanks, this is a HUGE help, I appreciate it.
-Dan -
Hi all - My mac pro 1,1 has an enigmatic problem. It's quad-core, 3Ghz, running OS X 10.7.5. The problem began some months back, when running HD video conferences, HD streaming videos and some other graphics-moderate (I won't say intense) uses, such as slide shows in Just Looking. My machine has an ATY, RadeonX1900 card and 2 monitors - both Apple displays, one being 30 inch 2560x1600, the other being 24 inch 1920x1200.
When I start those types of graphics-moderate apps, after about 5 minutes, something would crash (the monitors making a noise as it did) and the displays would both go black. The power did not appear to be fully cut off from the monitors. I think that the underlying applications, however, did not crash. So, I could still hear and speak to people during video conferences, and I could hear the sound tracks of videos.
Attempts to restart the computer and get the monitors back did not immediately work to undo the problem, if done straight away. The only way to correct the problem (so as to have the monitors work) was to wait for a few minutes and then restart.
After a lot of puzzled looking at console logs (and I confess that I am not an expert), I ran into a blank.
But, because of the timing of the crashes (after ~5minutes use) and restarts (after some minutes wait), I reasoned that the problem might be temperature related.
Once on that path of thought, I found this article:
http://worldtv.com/blog/guides_tutorials/fixing_an_overheating_mac_pro_no_expens e_required.php
I installed both Temperature Monitor and SMCFanControl. And I experimented, and got interesting results:
Now to the puzzling bit: SMCFanControl shows that the speed of the Power Supply Fan doesn't vary much, even if I use SMCFanControl to ramp fan speeds right up. All of the other fans react to SMCFanControl, going up to and above 2500rpm when commanded. But the Power Supply Fan does not. Having watched it for a few days now, the Power Supply Fan, according to AFCFanControl, never varies outside of a range from about 600-640 rpm, regardless of what I do with AFCFanControl.
Also (and not surprisingly), whenever the graphics-moderate apps run, when I ramp all the fan speeds up using SMCFanControl, Temperature Monitor shows that the all of the temperatures within the machine plummet, except in the power supply locations. Power Supply Location 2 is the worst affected. Because the Power Supply Fan does not react as the other fans do, the "crashes" still occur.
I could post some screen shots of the read outs of SMCFanControl and Temperature Monitor, although I think I have covered the key points in this post.
It seems that the Power Supply Fan is still working, but does not respond to increased loads.
Instinctively, I'm worried that if that's right, it might be a hard problem to fix. Any suggestions? Help! I would really appreciate them!
Cheers
PThanks for your response Grant. I had already read about, and I think excluded, dust in graphics card/fan/assembly as a cause. The entire inside of the computer, including the graphics card/fan/assembly, is as clean as a whistle. It looks clean. I've cleaned the dust out every now and then (including a few days ago). Also, my undersanding (derived from the article, linked in my first post) is that I might expect to see high temperatures in the Northbridge and memory module B if the graphics card was overheating. According to Temperature Monitor, however, locations do not increase in temperature when I run the relevant apps. Finally, the graphics card/assembly does not feel too hot to touch.
It is strange that SMCFanControl lists the Power Supply Fan as being software controllable, if that fan is not. Still, your comments are consistent with my observations, as the fan simply does not respond to software control.
There are two upsides: First, I've something of a work-around. I've worked out what temperature must be achieved in Power Supply Location 2 for a crash to occur, and I can watch that location in Temperature Monitor, terminating the process before that treshold is reached. Of course, that's not ideal. Second, ramping all the other fans up does significantly delay the onset of the problem, and makes recovery time much quicker.
Is there any donwside to peridically ramping up the other fans when running the relevant apps? Given that it causes all of the other locations to cool significantly, could this lessesn the life expecancy of the mahcine? (I don't want to run the fans up all the time - that's like sitting next to a jet ready for take off!)
Also, a correction to my first post: Yesterday, with all the other fans running on full and running an HD streaming video, the Power Supply Fan did, eventually, slowly, come up to ~740rpm, which is much higher than the ~640rpm maximum I had previously seen, and this may have aided delaying the onset of the problem.
I'm not sure where this leaves me? The problem might now be able managed. Well, sort-of. But it's not eliminated. -
TS3694 iPhone 5.....during update to iOS 7 I have lost the power supply (blackout)
this issue , happen to my iPhone 5.....during update to iOS 7 I have lost the power supply (blackout)
Sudden screen : USB pointing to iTunes . it shows that it need a restore and update .. after downloading the software
and extracting .. found Error1 at the point Verify firmware . AGAIN AND
and this is the log ..
2014-08-11 15:46:30.611 [4472:1648]: restore library built Feb 12 2014 at 16:27:17
2014-08-11 15:46:30.611 [4472:1648]: iTunes: iTunes 11.3.1.2
2014-08-11 15:46:30.611 [4472:1648]: iTunes: Software payload version: 11D257 (option key)
2014-08-11 15:46:30.611 [4472:1648]: iTunes: Using MobileRestore state machine
[13:47:25.0555] Changing state from 'Idle' to 'Restoring'
[13:47:25.0555] device software does not support nonce generation
[13:47:25.0555] requested restore behavior: Erase
[13:47:25.0570] requested variant: Erase
[13:47:25.0570] amai: AMAuthInstallBundleCopyBuildIdentityForVariant: No baseband chipid reported. Will match Build Identity based on ap chipid and boardid only.
[13:47:26.0553] amai: _AMAuthInstallBundleCreateServerRequestDictionary: withApTicket is False
[13:47:26.0553] amai: _AMAuthInstallBundleCreateServerRequestDictionary: not personalizing "RestoreLogo"
[13:47:26.0553] amai: _AMAuthInstallBundleCreateServerRequestDictionary: not personalizing "RestoreDeviceTree"
[13:47:26.0553] amai: _AMAuthInstallBundleCreateServerRequestDictionary: not personalizing "RestoreKernelCache"
[13:47:26.0553] amai: _AMAuthInstallBundleCreateServerRequestDictionary: not personalizing "RestoreRamDisk"
[13:47:26.0553] amai: _AMAuthInstallBundleCreateServerRequestDictionary: not personalizing "iBEC"
[13:47:26.0553] amai: _AMAuthInstallBundleCreateServerRequestDictionary: personalizing "iBSS" Digest = "<CFData 061FEA80 [7161907C]>{length = 20, capacity = 20, bytes = 0x<<<<<<<<<<<<<<<<<<UDID>>>>>>>>>>>>>>>>>>}"
[13:47:26.0553] amai: _AMAuthInstallBundleCreateServerRequestDictionary: not personalizing "KernelCache"
[13:47:26.0553] amai: _AMAuthInstallBundleCreateServerRequestDictionary: not personalizing "BatteryLow1"
[13:47:26.0553] amai: _AMAuthInstallBundleCreateServerRequestDictionary: not personalizing "BatteryLow0"
[13:47:26.0553] amai: _AMAuthInstallBundleCreateServerRequestDictionary: personalizing "LLB" Digest = "<CFData 061FD2E0 [7161907C]>{length = 20, capacity = 20, bytes = 0x<<<<<<<<<<<<<<<<<<UDID>>>>>>>>>>>>>>>>>>}"
[13:47:26.0553] amai: _AMAuthInstallBundleCreateServerRequestDictionary: not personalizing "iBoot"
[13:47:26.0553] amai: _AMAuthInstallBundleCreateServerRequestDictionary: not personalizing "DeviceTree"
[13:47:26.0553] amai: _AMAuthInstallBundleCreateServerRequestDictionary: not personalizing "BatteryCharging1"
[13:47:26.0553] amai: _AMAuthInstallBundleCreateServerRequestDictionary: not personalizing "AppleLogo"
[13:47:26.0553] amai: _AMAuthInstallBundleCreateServerRequestDictionary: not personalizing "BatteryPlugin"
[13:47:26.0569] amai: _AMAuthInstallBundleCreateServerRequestDictionary: not personalizing "BatteryFull"
[13:47:26.0569] amai: _AMAuthInstallBundleCreateServerRequestDictionary: not personalizing "BatteryCharging0"
[13:47:26.0569] amai: _AMAuthInstallBundleCreateServerRequestDictionary: not personalizing "RecoveryMode"
[13:47:26.0569] amai: _AMAuthInstallBundleCreateServerRequestDictionary: using UniqueBuildID <CFData 0BA32F38 [7161907C]>{length = 20, capacity = 20, bytes = 0x<<<<<<<<<<<<<<<<<<UDID>>>>>>>>>>>>>>>>>>}
[13:47:26.0569] amai: AMAuthInstallRequestSendSync: SSO function returned NULL, SSO disabled.
[13:47:26.0569] amai: AMAuthInstallDebugWriteObject: debug object written: file://localhost/C:/Users/Dell/AppData/Local/Temp/Per2046.tmp/amai/debug/tss-re quest.plist
[13:47:27.0068] amai: tss_submit_job: HttpQueryInfo returned 200
[13:47:27.0286] amai: AMAuthInstallRequestSendSync: received tss response (server version: 2.1.0)
[13:47:27.0286] amai: AMAuthInstallDebugWriteObject: debug object written: file://localhost/C:/Users/Dell/AppData/Local/Temp/Per2046.tmp/amai/debug/tss-re sponse.plist
[13:47:27.0318] amai: _AMAuthInstallBundlePopulatePersonalizedBundle: no entry in manifest found for "Diags"
[13:47:27.0333] <DFU Device 0562C260>: production fused device
[13:47:27.0333] requested restore behavior: Erase
[13:47:27.0333] device software does not support nonce generation
[13:47:27.0349] WinDFU::OpenDFUDevice: path: \\?\USB#VID_05AC&PID_1227#{B8085869-FEB9-404B-8CB1-1E5C14FA8C54}\0000#93126bb7
[13:47:27.0349] WinDFU::OpenDeviceByPath: \\?\USB#VID_05AC&PID_1227#{B8085869-FEB9-404B-8CB1-1E5C14FA8C54}\0000#93126bb7
[13:47:27.0364] <DFU Device 0562C260>: operation 0 progress 2
[13:47:27.0380] <DFU Device 0562C260>: operation 0 progress 5
[13:47:27.0396] <DFU Device 0562C260>: operation 0 progress 8
[13:47:27.0411] <DFU Device 0562C260>: operation 0 progress 10
[13:47:27.0427] <DFU Device 0562C260>: operation 0 progress 13
[13:47:27.0442] <DFU Device 0562C260>: operation 0 progress 16
[13:47:27.0458] <DFU Device 0562C260>: operation 0 progress 18
[13:47:27.0474] <DFU Device 0562C260>: operation 0 progress 21
[13:47:27.0489] <DFU Device 0562C260>: operation 0 progress 24
[13:47:27.0505] <DFU Device 0562C260>: operation 0 progress 26
[13:47:27.0520] <DFU Device 0562C260>: operation 0 progress 29
[13:47:27.0536] <DFU Device 0562C260>: operation 0 progress 32
[13:47:27.0552] <DFU Device 0562C260>: operation 0 progress 34
[13:47:27.0567] <DFU Device 0562C260>: operation 0 progress 37
[13:47:27.0583] <DFU Device 0562C260>: operation 0 progress 40
[13:47:27.0598] <DFU Device 0562C260>: operation 0 progress 42
[13:47:27.0614] <DFU Device 0562C260>: operation 0 progress 45
[13:47:27.0630] <DFU Device 0562C260>: operation 0 progress 48
[13:47:27.0645] <DFU Device 0562C260>: operation 0 progress 50
[13:47:27.0661] <DFU Device 0562C260>: operation 0 progress 53
[13:47:27.0676] <DFU Device 0562C260>: operation 0 progress 56
[13:47:27.0692] <DFU Device 0562C260>: operation 0 progress 59
[13:47:27.0708] <DFU Device 0562C260>: operation 0 progress 61
[13:47:27.0723] <DFU Device 0562C260>: operation 0 progress 64
[13:47:27.0739] <DFU Device 0562C260>: operation 0 progress 67
[13:47:27.0754] <DFU Device 0562C260>: operation 0 progress 69
[13:47:27.0770] <DFU Device 0562C260>: operation 0 progress 72
[13:47:27.0786] <DFU Device 0562C260>: operation 0 progress 75
[13:47:27.0801] <DFU Device 0562C260>: operation 0 progress 77
[13:47:27.0817] <DFU Device 0562C260>: operation 0 progress 80
[13:47:27.0832] <DFU Device 0562C260>: operation 0 progress 83
[13:47:27.0848] <DFU Device 0562C260>: operation 0 progress 85
[13:47:27.0864] <DFU Device 0562C260>: operation 0 progress 88
[13:47:27.0879] <DFU Device 0562C260>: operation 0 progress 91
[13:47:27.0895] <DFU Device 0562C260>: operation 0 progress 93
[13:47:27.0910] <DFU Device 0562C260>: operation 0 progress 96
[13:47:27.0926] <DFU Device 0562C260>: operation 0 progress 99
[13:47:27.0926] WinDFU::UploadData: EOF, cbRead: 554
[13:47:27.0942] <DFU Device 0562C260>: operation 0 progress 100
[13:47:27.0942] WinDFU::UploadData: ZLP
[13:47:27.0957] WinDFU::FinalizeDfuUpdate: GetStatus: status: 0, state: 6
[13:47:27.0957] WinDFU::ProcessUpdateState: status.bState == DFU_STATE_MANIFEST_SYNC
[13:47:27.0957] WinDFU::FinalizeDfuUpdate: GetStatus: status: 0, state: 7
[13:47:27.0957] WinDFU::ProcessUpdateState: status.bState == DFU_STATE_MANIFEST, PollTimeout: 3000
[13:47:30.0968] WinDFU::FinalizeDfuUpdate: GetStatus: status: 0, state: 8
[13:47:30.0968] WinDFU::ProcessUpdateState: status.bState == DFU_STATE_MANIFEST_WAIT_RESET
[13:47:30.0968] WinDFU::ResetDevice: resetting...
[13:47:31.0046] WinDFU::FinalizeDfuUpdate: success
[13:47:31.0046] <DFU Device 0562C260>: DFU succeeded
[13:47:31.0046] Finished DFU Restore Phase: Successful
[13:47:31.0218] DFU mode device disconnected
[13:47:31.0218] Device removed when in state Restoring, moving device to transition state
[13:47:31.0218] Changing state from 'Restoring' to 'Transitioning'
[13:47:31.0218] Creating timer to monitor transition
[13:47:32.0175] DFU mode device connected
[13:47:32.0175] Transitioning device returned, continuing restore.
[13:47:32.0175] Canceling timer
[13:47:32.0175] Changing state from 'Transitioning' to 'Restoring'
[13:47:32.0175] AppleDevice::GetDeviceID: failed for iBoot
[13:47:32.0175] requested restore behavior: Erase
[13:47:32.0175] requested variant: Erase
[13:47:32.0175] amai: AMAuthInstallBundleCopyBuildIdentityForVariant: No baseband chipid reported. Will match Build Identity based on ap chipid and boardid only.
[13:47:33.0033] amai: _AMAuthInstallBundleCreateServerRequestDictionary: withApTicket is True
[13:47:33.0033] amai: _AMAuthInstallBundleCreateServerRequestDictionary: personalizing "RestoreLogo" Digest = "<CFData 061FDC70 [7161907C]>{length = 20, capacity = 20, bytes = 0x<<<<<<<<<<<<<<<<<<UDID>>>>>>>>>>>>>>>>>>}"
[13:47:33.0033] amai: _AMAuthInstallBundleCreateServerRequestDictionary: personalizing "RestoreDeviceTree" Digest = "<CFData 061FE378 [7161907C]>{length = 20, capacity = 20, bytes = 0x<<<<<<<<<<<<<<<<<<UDID>>>>>>>>>>>>>>>>>>}"
[13:47:33.0033] amai: _AMAuthInstallBundleCreateServerRequestDictionary: personalizing "RestoreKernelCache" Digest = "<CFData 0B9D5148 [7161907C]>{length = 20, capacity = 20, bytes = 0x<<<<<<<<<<<<<<<<<<UDID>>>>>>>>>>>>>>>>>>}"
[13:47:33.0033] amai: _AMAuthInstallBundleCreateServerRequestDictionary: personalizing "RestoreRamDisk" Digest = "<CFData 0B9D5190 [7161907C]>{length = 20, capacity = 20, bytes = 0x<<<<<<<<<<<<<<<<<<UDID>>>>>>>>>>>>>>>>>>}"
[13:47:33.0049] amai: _AMAuthInstallBundleCreateServerRequestDictionary: personalizing "iBEC" Digest = "<CFData 0B9D51D8 [7161907C]>{length = 20, capacity = 20, bytes = 0x<<<<<<<<<<<<<<<<<<UDID>>>>>>>>>>>>>>>>>>}"
[13:47:33.0049] amai: _AMAuthInstallBundleCreateServerRequestDictionary: personalizing "iBSS" Digest = "<CFData 0B9D5220 [7161907C]>{length = 20, capacity = 20, bytes = 0x<<<<<<<<<<<<<<<<<<UDID>>>>>>>>>>>>>>>>>>}"
[13:47:33.0049] amai: _AMAuthInstallBundleCreateServerRequestDictionary: personalizing "KernelCache" Digest = "<CFData 0B9D5268 [7161907C]>{length = 20, capacity = 20, bytes = 0x<<<<<<<<<<<<<<<<<<UDID>>>>>>>>>>>>>>>>>>}"
[13:47:33.0049] amai: _AMAuthInstallBundleCreateServerRequestDictionary: personalizing "BatteryLow1" Digest = "<CFData 0B9D52B0 [7161907C]>{length = 20, capacity = 20, bytes = 0x<<<<<<<<<<<<<<<<<<UDID>>>>>>>>>>>>>>>>>>}"
[13:47:33.0049] amai: _AMAuthInstallBundleCreateServerRequestDictionary: personalizing "BatteryLow0" Digest = "<CFData 0B9D52F8 [7161907C]>{length = 20, capacity = 20, bytes = 0x<<<<<<<<<<<<<<<<<<UDID>>>>>>>>>>>>>>>>>>}"
[13:47:33.0049] amai: _AMAuthInstallBundleCreateServerRequestDictionary: personalizing "LLB" Digest = "<CFData 0B9D5340 [7161907C]>{length = 20, capacity = 20, bytes = 0x<<<<<<<<<<<<<<<<<<UDID>>>>>>>>>>>>>>>>>>}"
[13:47:33.0049] amai: _AMAuthInstallBundleCreateServerRequestDictionary: personalizing "iBoot" Digest = "<CFData 0B9D5388 [7161907C]>{length = 20, capacity = 20, bytes = 0x<<<<<<<<<<<<<<<<<<UDID>>>>>>>>>>>>>>>>>>}"
[13:47:33.0049] amai: _AMAuthInstallBundleCreateServerRequestDictionary: personalizing "DeviceTree" Digest = "<CFData 0B9D53D0 [7161907C]>{length = 20, capacity = 20, bytes = 0x<<<<<<<<<<<<<<<<<<UDID>>>>>>>>>>>>>>>>>>}"
[13:47:33.0049] amai: _AMAuthInstallBundleCreateServerRequestDictionary: personalizing "BatteryCharging1" Digest = "<CFData 0B9D5418 [7161907C]>{length = 20, capacity = 20, bytes = 0x<<<<<<<<<<<<<<<<<<UDID>>>>>>>>>>>>>>>>>>}"
[13:47:33.0049] amai: _AMAuthInstallBundleCreateServerRequestDictionary: personalizing "AppleLogo" Digest = "<CFData 0B9D5460 [7161907C]>{length = 20, capacity = 20, bytes = 0x<<<<<<<<<<<<<<<<<<UDID>>>>>>>>>>>>>>>>>>}"
[13:47:33.0049] amai: _AMAuthInstallBundleCreateServerRequestDictionary: personalizing "BatteryPlugin" Digest = "<CFData 0B9D54A8 [7161907C]>{length = 20, capacity = 20, bytes = 0x<<<<<<<<<<<<<<<<<<UDID>>>>>>>>>>>>>>>>>>}"
[13:47:33.0049] amai: _AMAuthInstallBundleCreateServerRequestDictionary: personalizing "BatteryFull" Digest = "<CFData 06266350 [7161907C]>{length = 20, capacity = 20, bytes = 0x<<<<<<<<<<<<<<<<<<UDID>>>>>>>>>>>>>>>>>>}"
[13:47:33.0049] amai: _AMAuthInstallBundleCreateServerRequestDictionary: personalizing "BatteryCharging0" Digest = "<CFData 06266398 [7161907C]>{length = 20, capacity = 20, bytes = 0x<<<<<<<<<<<<<<<<<<UDID>>>>>>>>>>>>>>>>>>}"
[13:47:33.0049] amai: _AMAuthInstallBundleCreateServerRequestDictionary: personalizing "RecoveryMode" Digest = "<CFData 062663E0 [7161907C]>{length = 20, capacity = 20, bytes = 0x<<<<<<<<<<<<<<<<<<UDID>>>>>>>>>>>>>>>>>>}"
[13:47:33.0049] amai: _AMAuthInstallBundleCreateServerRequestDictionary: using UniqueBuildID <CFData 064698C8 [7161907C]>{length = 20, capacity = 20, bytes = 0x<<<<<<<<<<<<<<<<<<UDID>>>>>>>>>>>>>>>>>>}
[13:47:33.0064] amai: AMAuthInstallRequestSendSync: SSO function returned NULL, SSO disabled.
[13:47:33.0064] amai: AMAuthInstallDebugWriteObject: debug object written: file://localhost/C:/Users/Dell/AppData/Local/Temp/Per2046.tmp/amai/debug/tss-re quest.plist
[13:47:33.0298] amai: tss_submit_job: HttpQueryInfo returned 200
[13:47:33.0501] amai: AMAuthInstallRequestSendSync: received tss response (server version: 2.1.0)
[13:47:33.0501] amai: AMAuthInstallDebugWriteObject: debug object written: file://localhost/C:/Users/Dell/AppData/Local/Temp/Per2046.tmp/amai/debug/tss-re sponse.plist
[13:47:33.0501] amai: _AMAuthInstallBundleInstallPersonalizedEntry: entry "iBSS" has been previously personalized; skipping it
[13:47:33.0501] amai: _AMAuthInstallBundleInstallPersonalizedEntry: entry "LLB" has been previously personalized; skipping it
[13:47:33.0517] amai: _AMAuthInstallBundlePopulatePersonalizedBundle: no entry in manifest found for "Diags"
[13:47:33.0532] <DFU Device 0BA2A9D8>: production fused device
[13:47:33.0532] requested restore behavior: Erase
[13:47:33.0532] amai: AMAuthInstallBundleCopyBuildIdentityForVariant: No baseband chipid reported. Will match Build Identity based on ap chipid and boardid only.
[13:47:33.0532] AppleDevice::GetDeviceID: failed for iBoot
[13:47:33.0532] WinDFU::OpenDFUDevice: path: \\?\USB#VID_05AC&PID_1227#{B8085869-FEB9-404B-8CB1-1E5C14FA8C54}\0000#ca28221e
[13:47:33.0532] WinDFU::OpenDeviceByPath: \\?\USB#VID_05AC&PID_1227#{B8085869-FEB9-404B-8CB1-1E5C14FA8C54}\0000#ca28221e
[13:47:33.0564] <DFU Device 0BA2A9D8>: operation 0 progress 0
[13:47:33.0579] <DFU Device 0BA2A9D8>: operation 0 progress 1
[13:47:33.0595] <DFU Device 0BA2A9D8>: operation 0 progress 2
[13:47:33.0626] <DFU Device 0BA2A9D8>: operation 0 progress 3
[13:47:33.0642] <DFU Device 0BA2A9D8>: operation 0 progress 4
[13:47:33.0657] <DFU Device 0BA2A9D8>: operation 0 progress 5
[13:47:33.0688] <DFU Device 0BA2A9D8>: operation 0 progress 6
[13:47:33.0704] <DFU Device 0BA2A9D8>: operation 0 progress 7
[13:47:33.0735] <DFU Device 0BA2A9D8>: operation 0 progress 8
[13:47:33.0751] <DFU Device 0BA2A9D8>: operation 0 progress 9
[13:47:33.0766] <DFU Device 0BA2A9D8>: operation 0 progress 10
[13:47:33.0798] <DFU Device 0BA2A9D8>: operation 0 progress 11
[13:47:33.0813] <DFU Device 0BA2A9D8>: operation 0 progress 12
[13:47:33.0844] <DFU Device 0BA2A9D8>: operation 0 progress 13
[13:47:33.0860] <DFU Device 0BA2A9D8>: operation 0 progress 14
[13:47:33.0876] <DFU Device 0BA2A9D8>: operation 0 progress 15
[13:47:33.0907] <DFU Device 0BA2A9D8>: operation 0 progress 16
[13:47:33.0922] <DFU Device 0BA2A9D8>: operation 0 progress 17
[13:47:33.0954] <DFU Device 0BA2A9D8>: operation 0 progress 18
[13:47:33.0969] <DFU Device 0BA2A9D8>: operation 0 progress 19
[13:47:33.0985] <DFU Device 0BA2A9D8>: operation 0 progress 20
[13:47:34.0016] <DFU Device 0BA2A9D8>: operation 0 progress 21
[13:47:34.0032] <DFU Device 0BA2A9D8>: operation 0 progress 22
[13:47:34.0063] <DFU Device 0BA2A9D8>: operation 0 progress 23
[13:47:34.0078] <DFU Device 0BA2A9D8>: operation 0 progress 24
[13:47:34.0094] <DFU Device 0BA2A9D8>: operation 0 progress 25
[13:47:34.0125] <DFU Device 0BA2A9D8>: operation 0 progress 26
[13:47:34.0141] <DFU Device 0BA2A9D8>: operation 0 progress 27
[13:47:34.0172] <DFU Device 0BA2A9D8>: operation 0 progress 28
[13:47:34.0188] <DFU Device 0BA2A9D8>: operation 0 progress 29
[13:47:34.0203] <DFU Device 0BA2A9D8>: operation 0 progress 30
[13:47:34.0234] <DFU Device 0BA2A9D8>: operation 0 progress 31
[13:47:34.0250] <DFU Device 0BA2A9D8>: operation 0 progress 32
[13:47:34.0281] <DFU Device 0BA2A9D8>: operation 0 progress 33
[13:47:34.0297] <DFU Device 0BA2A9D8>: operation 0 progress 34
[13:47:34.0312] <DFU Device 0BA2A9D8>: operation 0 progress 35
[13:47:34.0344] <DFU Device 0BA2A9D8>: operation 0 progress 36
[13:47:34.0359] <DFU Device 0BA2A9D8>: operation 0 progress 37
[13:47:34.0390] <DFU Device 0BA2A9D8>: operation 0 progress 38
[13:47:34.0406] <DFU Device 0BA2A9D8>: operation 0 progress 39
[13:47:34.0422] <DFU Device 0BA2A9D8>: operation 0 progress 40
[13:47:34.0453] <DFU Device 0BA2A9D8>: operation 0 progress 41
[13:47:34.0468] <DFU Device 0BA2A9D8>: operation 0 progress 42
[13:47:34.0500] <DFU Device 0BA2A9D8>: operation 0 progress 43
[13:47:34.0515] <DFU Device 0BA2A9D8>: operation 0 progress 44
[13:47:34.0531] <DFU Device 0BA2A9D8>: operation 0 progress 45
[13:47:34.0562] <DFU Device 0BA2A9D8>: operation 0 progress 46
[13:47:34.0578] <DFU Device 0BA2A9D8>: operation 0 progress 47
[13:47:34.0593] <DFU Device 0BA2A9D8>: operation 0 progress 48
[13:47:34.0624] <DFU Device 0BA2A9D8>: operation 0 progress 49
[13:47:34.0640] <DFU Device 0BA2A9D8>: operation 0 progress 50
[13:47:34.0671] <DFU Device 0BA2A9D8>: operation 0 progress 51
[13:47:34.0687] <DFU Device 0BA2A9D8>: operation 0 progress 52
[13:47:34.0702] <DFU Device 0BA2A9D8>: operation 0 progress 53
[13:47:34.0734] <DFU Device 0BA2A9D8>: operation 0 progress 54
[13:47:34.0749] <DFU Device 0BA2A9D8>: operation 0 progress 55
[13:47:34.0780] <DFU Device 0BA2A9D8>: operation 0 progress 56
[13:47:34.0796] <DFU Device 0BA2A9D8>: operation 0 progress 57
[13:47:34.0812] <DFU Device 0BA2A9D8>: operation 0 progress 58
[13:47:34.0843] <DFU Device 0BA2A9D8>: operation 0 progress 59
[13:47:34.0858] <DFU Device 0BA2A9D8>: operation 0 progress 60
[13:47:34.0890] <DFU Device 0BA2A9D8>: operation 0 progress 61
[13:47:34.0905] <DFU Device 0BA2A9D8>: operation 0 progress 62
[13:47:34.0921] <DFU Device 0BA2A9D8>: operation 0 progress 63
[13:47:34.0952] <DFU Device 0BA2A9D8>: operation 0 progress 64
[13:47:34.0968] <DFU Device 0BA2A9D8>: operation 0 progress 65
[13:47:34.0999] <DFU Device 0BA2A9D8>: operation 0 progress 66
[13:47:35.0014] <DFU Device 0BA2A9D8>: operation 0 progress 67
[13:47:35.0030] <DFU Device 0BA2A9D8>: operation 0 progress 68
[13:47:35.0061] <DFU Device 0BA2A9D8>: operation 0 progress 69
[13:47:35.0077] <DFU Device 0BA2A9D8>: operation 0 progress 70
[13:47:35.0108] <DFU Device 0BA2A9D8>: operation 0 progress 71
[13:47:35.0124] <DFU Device 0BA2A9D8>: operation 0 progress 72
[13:47:35.0139] <DFU Device 0BA2A9D8>: operation 0 progress 73
[13:47:35.0170] <DFU Device 0BA2A9D8>: operation 0 progress 74
[13:47:35.0186] <DFU Device 0BA2A9D8>: operation 0 progress 75
[13:47:35.0217] <DFU Device 0BA2A9D8>: operation 0 progress 76
[13:47:35.0233] <DFU Device 0BA2A9D8>: operation 0 progress 77
[13:47:35.0248] <DFU Device 0BA2A9D8>: operation 0 progress 78
[13:47:35.0280] <DFU Device 0BA2A9D8>: operation 0 progress 79
[13:47:35.0295] <DFU Device 0BA2A9D8>: operation 0 progress 80
[13:47:35.0326] <DFU Device 0BA2A9D8>: operation 0 progress 81
[13:47:35.0342] <DFU Device 0BA2A9D8>: operation 0 progress 82
[13:47:35.0358] <DFU Device 0BA2A9D8>: operation 0 progress 83
[13:47:35.0389] <DFU Device 0BA2A9D8>: operation 0 progress 84
[13:47:35.0404] <DFU Device 0BA2A9D8>: operation 0 progress 85
[13:47:35.0436] <DFU Device 0BA2A9D8>: operation 0 progress 86
[13:47:35.0451] <DFU Device 0BA2A9D8>: operation 0 progress 87
[13:47:35.0467] <DFU Device 0BA2A9D8>: operation 0 progress 88
[13:47:35.0498] <DFU Device 0BA2A9D8>: operation 0 progress 89
[13:47:35.0514] <DFU Device 0BA2A9D8>: operation 0 progress 90
[13:47:35.0529] <DFU Device 0BA2A9D8>: operation 0 progress 91
[13:47:35.0560] <DFU Device 0BA2A9D8>: operation 0 progress 92
[13:47:35.0576] <DFU Device 0BA2A9D8>: operation 0 progress 93
[13:47:35.0607] <DFU Device 0BA2A9D8>: operation 0 progress 94
[13:47:35.0623] <DFU Device 0BA2A9D8>: operation 0 progress 95
[13:47:35.0638] <DFU Device 0BA2A9D8>: operation 0 progress 96
[13:47:35.0670] <DFU Device 0BA2A9D8>: operation 0 progress 97
[13:47:35.0685] <DFU Device 0BA2A9D8>: operation 0 progress 98
[13:47:35.0716] <DFU Device 0BA2A9D8>: operation 0 progress 99
[13:47:35.0716] WinDFU::UploadData: EOF, cbRead: 1116
[13:47:35.0732] <DFU Device 0BA2A9D8>: operation 0 progress 100
[13:47:35.0732] WinDFU::UploadData: ZLP
[13:47:35.0748] WinDFU::FinalizeDfuUpdate: GetStatus: status: 0, state: 6
[13:47:35.0748] WinDFU::ProcessUpdateState: status.bState == DFU_STATE_MANIFEST_SYNC
[13:47:35.0748] WinDFU::FinalizeDfuUpdate: GetStatus: status: 0, state: 7
[13:47:35.0748] WinDFU::ProcessUpdateState: status.bState == DFU_STATE_MANIFEST, PollTimeout: 3000
[13:47:38.0758] WinDFU::FinalizeDfuUpdate: GetStatus: status: 0, state: 8
[13:47:38.0758] WinDFU::ProcessUpdateState: status.bState == DFU_STATE_MANIFEST_WAIT_RESET
[13:47:38.0758] WinDFU::ResetDevice: resetting...
[13:47:38.0836] WinDFU::FinalizeDfuUpdate: success
[13:47:38.0836] <DFU Device 0BA2A9D8>: DFU succeeded
[13:47:38.0836] Finished DFU Restore Phase: Successful
[13:47:39.0039] DFU mode device disconnected
[13:47:39.0039] Device removed when in state Restoring, moving device to transition state
[13:47:39.0039] Changing state from 'Restoring' to 'Transitioning'
[13:47:39.0039] Creating timer to monitor transition
[13:47:41.0674] Recovery mode device connected
[13:47:41.0674] Transitioning device returned, continuing restore.
[13:47:41.0674] Canceling timer
[13:47:41.0674] Changing state from 'Transitioning' to 'Restoring'
[13:47:41.0684] requested restore behavior: Erase
[13:47:41.0684] requested variant: Erase
[13:47:41.0684] amai: AMAuthInstallBundleCopyBuildIdentityForVariant: No baseband chipid reported. Will match Build Identity based on ap chipid and boardid only.
[13:47:42.0512] amai: _AMAuthInstallBundleCreateServerRequestDictionary: withApTicket is False
[13:47:42.0512] amai: _AMAuthInstallBundleCreateServerRequestDictionary: not personalizing "RestoreLogo"
[13:47:42.0512] amai: _AMAuthInstallBundleCreateServerRequestDictionary: not personalizing "RestoreDeviceTree"
[13:47:42.0512] amai: _AMAuthInstallBundleCreateServerRequestDictionary: not personalizing "RestoreKernelCache"
[13:47:42.0512] amai: _AMAuthInstallBundleCreateServerRequestDictionary: not personalizing "RestoreRamDisk"
[13:47:42.0512] amai: _AMAuthInstallBundleCreateServerRequestDictionary: not personalizing "iBEC"
[13:47:42.0512] amai: _AMAuthInstallBundleCreateServerRequestDictionary: entry "iBSS" has been previously personalized; skipping it
[13:47:42.0528] amai: _AMAuthInstallBundleCreateServerRequestDictionary: not personalizing "KernelCache"
[13:47:42.0528] amai: _AMAuthInstallBundleCreateServerRequestDictionary: not personalizing "BatteryLow1"
[13:47:42.0528] amai: _AMAuthInstallBundleCreateServerRequestDictionary: not personalizing "BatteryLow0"
[13:47:42.0528] amai: _AMAuthInstallBundleCreateServerRequestDictionary: entry "LLB" has been previously personalized; skipping it
[13:47:42.0528] amai: _AMAuthInstallBundleCreateServerRequestDictionary: not personalizing "iBoot"
[13:47:42.0528] amai: _AMAuthInstallBundleCreateServerRequestDictionary: not personalizing "DeviceTree"
[13:47:42.0528] amai: _AMAuthInstallBundleCreateServerRequestDictionary: not personalizing "BatteryCharging1"
[13:47:42.0528] amai: _AMAuthInstallBundleCreateServerRequestDictionary: not personalizing "AppleLogo"
[13:47:42.0528] amai: _AMAuthInstallBundleCreateServerRequestDictionary: not personalizing "BatteryPlugin"
[13:47:42.0528] amai: _AMAuthInstallBundleCreateServerRequestDictionary: not personalizing "BatteryFull"
[13:47:42.0528] amai: _AMAuthInstallBundleCreateServerRequestDictionary: not personalizing "BatteryCharging0"
[13:47:42.0528] amai: _AMAuthInstallBundleCreateServerRequestDictionary: not personalizing "RecoveryMode"
[13:47:42.0528] amai: _AMAuthInstallBundleCreateServerRequestDictionary: nothing to be done
[13:47:42.0528] iBoot build-version = iBoot-1940.10.58
[13:47:42.0528] iBoot build-style = RELEASE
[13:47:42.0528] requested restore behavior: Erase
[13:47:42.0528] amai: AMAuthInstallBundleCopyBuildIdentityForVariant: No baseband chipid reported. Will match Build Identity based on ap chipid and boardid only.
[13:47:42.0528] requested restore behavior: Erase
[13:47:42.0528] amai: AMAuthInstallBundleCopyBuildIdentityForVariant: No baseband chipid reported. Will match Build Identity based on ap chipid and boardid only.
[13:47:42.0543] unable to open device_map.txt: No such file or directory
[13:47:42.0543] found device map entry for 0x00008950 0x00000002. boardConfig=n42ap platform=s5l8950x
[13:47:42.0543] _AMRestoreCopyDeviceMapPlistEntryForHardware: firmwareDirectory not in options
[13:47:42.0543] AMDeviceIoControl: GetOverlappedResult failed
[13:47:42.0543] AMDeviceIoControl: pipe stall
[13:47:42.0543] USBControlTransfer: error 31, usbd status c0000004
[13:47:42.0543] command device request for 'getenv radio-error' failed: 2008
[13:47:42.0543] radio-error not set
[13:47:42.0543] unable to open device_map.txt: No such file or directory
[13:47:42.0543] <Recovery Mode Device 0555AEB8>: production fused device
[13:47:42.0543] requested restore behavior: Erase
[13:47:42.0543] amai: AMAuthInstallBundleCopyBuildIdentityForVariant: No baseband chipid reported. Will match Build Identity based on ap chipid and boardid only.
[13:47:42.0543] requested restore behavior: Erase
[13:47:42.0543] amai: AMAuthInstallBundleCopyBuildIdentityForVariant: No baseband chipid reported. Will match Build Identity based on ap chipid and boardid only.
[13:47:42.0543] interface has 1 endpoints, file pipe = 1
[13:47:42.0543]
[13:47:42.0543] <Recovery Mode Device 0555AEB8>: operation 4 progress -1
[13:47:42.0606] unable to open device_map.txt: No such file or directory
[13:47:42.0606] found device map entry for 0x00008950 0x00000002. boardConfig=n42ap platform=s5l8950x
[13:47:42.0606] _AMRestoreCopyDeviceMapPlistEntryForHardware: firmwareDirectory not in options
[13:47:42.0606] requested restore behavior: Erase
[13:47:42.0606] amai: AMAuthInstallBundleCopyBuildIdentityForVariant: No baseband chipid reported. Will match Build Identity based on ap chipid and boardid only.
[13:47:42.0606] requested restore behavior: Erase
[13:47:42.0606] amai: AMAuthInstallBundleCopyBuildIdentityForVariant: No baseband chipid reported. Will match Build Identity based on ap chipid and boardid only.
[13:47:42.0606] <Recovery Mode Device 0555AEB8>: operation 42 progress -1
[13:47:42.0606] requested restore behavior: Erase
[13:47:42.0621] amai: AMAuthInstallBundleCopyBuildIdentityForVariant: No baseband chipid reported. Will match Build Identity based on ap chipid and boardid only.
[13:47:43.0651] <Recovery Mode Device 0555AEB8>: operation 5 progress -1
[13:47:43.0994] unable to open device_map.txt: No such file or directory
[13:47:43.0994] found device map entry for 0x00008950 0x00000002. boardConfig=n42ap platform=s5l8950x
[13:47:43.0994] _AMRestoreCopyDeviceMapPlistEntryForHardware: firmwareDirectory not in options
[13:47:43.0994] AMDeviceIoControl: GetOverlappedResult failed
[13:47:43.0994] AMDeviceIoControl: pipe stall
[13:47:43.0994] USBControlTransfer: error 31, usbd status c0000004
[13:47:43.0994] command device request for 'getenv ramdisk-delay' failed: 2008
[13:47:45.0616] <Recovery Mode Device 0555AEB8>: operation 6 progress -1
[13:47:46.0630] <Recovery Mode Device 0555AEB8>: operation 7 progress -1
[13:47:46.0942] <Recovery Mode Device 0555AEB8>: operation 8 progress -1
[13:47:46.0958] unable to open device_map.txt: No such file or directory
[13:47:46.0958] found device map entry for 0x00008950 0x00000002. boardConfig=n42ap platform=s5l8950x
[13:47:46.0958] _AMRestoreCopyDeviceMapPlistEntryForHardware: firmwareDirectory not in options
[13:47:46.0958] <Recovery Mode Device 0555AEB8>: operation 9 progress -1
[13:47:46.0958] <Recovery Mode Device 0555AEB8>: Recovery mode succeeded
[13:47:46.0958] Finished Recovery Restore Phase: Successful
[13:47:48.0409] Recovery mode device disconnected
[13:47:48.0409] Device removed when in state Restoring, moving device to transition state
[13:47:48.0409] Changing state from 'Restoring' to 'Transitioning'
[13:47:48.0409] Creating timer to monitor transition
[13:47:52.0895] RestoreOS mode device connected
[13:47:52.0895] Transitioning device returned, continuing restore.
[13:47:52.0905] Canceling timer
[13:47:52.0905] Changing state from 'Transitioning' to 'Restoring'
[13:47:52.0905] <Restore Device 05577800>: operation 44 progress -1
[13:47:52.0905] requested restore behavior: Erase
[13:47:52.0905] requested variant: Erase
[13:47:52.0905] amai: AMAuthInstallBundleCopyBuildIdentityForVariant: No baseband chipid reported. Will match Build Identity based on ap chipid and boardid only.
[13:47:53.0777] amai: _AMAuthInstallBundleCreateServerRequestDictionary: withApTicket is False
[13:47:53.0777] amai: _AMAuthInstallBundleCreateServerRequestDictionary: not personalizing "RestoreLogo"
[13:47:53.0777] amai: _AMAuthInstallBundleCreateServerRequestDictionary: not personalizing "RestoreDeviceTree"
[13:47:53.0777] amai: _AMAuthInstallBundleCreateServerRequestDictionary: not personalizing "RestoreKernelCache"
[13:47:53.0777] amai: _AMAuthInstallBundleCreateServerRequestDictionary: not personalizing "RestoreRamDisk"
[13:47:53.0777] amai: _AMAuthInstallBundleCreateServerRequestDictionary: not personalizing "iBEC"
[13:47:53.0777] amai: _AMAuthInstallBundleCreateServerRequestDictionary: entry "iBSS" has been previously personalized; skipping it
[13:47:53.0777] amai: _AMAuthInstallBundleCreateServerRequestDictionary: not personalizing "KernelCache"
[13:47:53.0777] amai: _AMAuthInstallBundleCreateServerRequestDictionary: not personalizing "BatteryLow1"
[13:47:53.0792] amai: _AMAuthInstallBundleCreateServerRequestDictionary: not personalizing "BatteryLow0"
[13:47:53.0792] amai: _AMAuthInstallBundleCreateServerRequestDictionary: entry "LLB" has been previously personalized; skipping it
[13:47:53.0792] amai: _AMAuthInstallBundleCreateServerRequestDictionary: not personalizing "iBoot"
[13:47:53.0792] amai: _AMAuthInstallBundleCreateServerRequestDictionary: not personalizing "DeviceTree"
[13:47:53.0792] amai: _AMAuthInstallBundleCreateServerRequestDictionary: not personalizing "BatteryCharging1"
[13:47:53.0792] amai: _AMAuthInstallBundleCreateServerRequestDictionary: not personalizing "AppleLogo"
[13:47:53.0792] amai: _AMAuthInstallBundleCreateServerRequestDictionary: not personalizing "BatteryPlugin"
[13:47:53.0792] amai: _AMAuthInstallBundleCreateServerRequestDictionary: not personalizing "BatteryFull"
[13:47:53.0792] amai: _AMAuthInstallBundleCreateServerRequestDictionary: not personalizing "BatteryCharging0"
[13:47:53.0792] amai: _AMAuthInstallBundleCreateServerRequestDictionary: not personalizing "RecoveryMode"
[13:47:53.0792] amai: _AMAuthInstallBundleCreateServerRequestDictionary: nothing to be done
[13:47:53.0792] requested restore behavior: Erase
[13:47:53.0792] amai: AMAuthInstallBundleCopyBuildIdentityForVariant: No baseband chipid reported. Will match Build Identity based on ap chipid and boardid only.
[13:47:53.0792] device did not return saved USB log
[13:47:53.0792] device did not return saved panic log
[13:47:53.0792] previous restore failed with exit status 0x100
[13:47:53.0792] connected to service com.apple.mobile.restored
[13:47:53.0808] using protocol version 13
[13:47:53.0808] unable to open device_map.txt: No such file or directory
[13:47:53.0808] board config = n42ap
[13:47:53.0808] no value returned for BootArgs
[13:47:53.0824] _copyDeviceProperty() failed for restore bootargs
[13:47:53.0824] no value returned for MarketingPartNumber
[13:47:53.0824] _copyDeviceProperty() failed for mpn
[13:47:53.0824] requested restore behavior: Erase
[13:47:53.0824] amai: AMAuthInstallBundleCopyBuildIdentityForVariant: No baseband chipid reported. Will match Build Identity based on ap chipid and boardid only.
[13:47:53.0839] value query for 'HardwareModel' returned 'N42AP'
[13:47:53.0839] <Restore Device 05577800>: operation 28 progress -1
[13:48:10.0360] previous restore failed: re:INF@ 145] created partition 1 as 'Effaceable'
[13:48:10.0360] [nand_part_core:INF@ 145] created partition 2 as 'NVRAM'
[13:48:10.0360] [nand_part_core:INF@ 145] created partition 3 as 'Firmware'
[13:48:10.0360] [nand_part_core:INF@ 145] created partition 4 as 'Filesystem'
[13:48:10.0360] [nand_part_core:INF@ 157] published partition 4
[13:48:10.0360] [nand_part_core:INF@ 145] created partition 5 as 'System Config'
[13:48:10.0360] [nand_part_core:INF@ 145] created partition 6 as 'Diagnostic Data'
[13:48:10.0360] [nand_part_core:INF@ 145] created partition 7 as 'Bad Block Table'
[13:48:10.0360] com.apple.AppleFSCompressionTypeZlib load succeeded
[13:48:10.0360] [nand_part_core:INF@ 157] published partition 7
[13:48:10.0360] AppleSamsungSerial: Identified Serial Port on ARM Device=uart1 at 0x32600000(0x82cc6000)
[13:48:10.0360] L2TP domain init
[13:48:10.0360] L2TP domain init complete
[13:48:10.0360] PPTP domain init
[13:48:10.0360] AppleSwissPPNFTL started with IOFlashStoragePartition provider
[13:48:10.0360] [NAND] _FindFlashMediaAndKeepout:601 physical nand block offset 1
[13:48:10.0360] AppleNANDFTL registered[NAND] start:356 this 0x85e41800 PROVIDER=0x85f2a400 flashMedia=0x85f2a400
[13:48:10.0360] [NAND] WMR_Start:149 Apple PPN NAND Driver, Read/Write
[13:48:10.0360] [NAND] WMR_Start:174 FIL_Init [OK]
[13:48:10.0360] AppleSamsungSerial: Identified Serial Port on ARM Device=uart3 at 0x32800000(0xde3b4000)
[13:48:10.0360] virtual bool AppleDisplayPipe::start_hardware(IOService *), auto-detect chip
[13:48:10.0360] [NAND] WMR_Open:371 VFL_Open [OK]
[13:48:10.0360] Scaler 0 enableDeviceClock(true,HALF_CLOCK_INDEX) = 0x0
[13:48:10.0360] Scaler 0 enableDeviceClock(true,FULL_CLOCK_INDEX) = 0x0
[13:48:10.0360] Scaler 0 enableDevicePower(true,0,HALF_CLOCK_INDEX) = 0x0
[13:48:10.0360] Scaler 0 enableDeviceClock(false,FULL_CLOCK_INDEX) = 0x0
[13:48:10.0360] void AppleDisplayPipe::setupVideoDownscalingLimits(): minimum-frequency property not found, using getClockFrequency(0) instead.
[13:48:10.0360] Scaler 1 enableDeviceClock(true,HALF_CLOCK_INDEX) = 0x0
[13:48:10.0360] Scaler 1 enableDeviceClock(true,FULL_CLOCK_INDEX) = 0x0
[13:48:10.0360] Scaler 1 enableDevicePower(true,0,HALF_CLOCK_INDEX) = 0x0
[13:48:10.0360] Scaler 1 enableDeviceClock(false,FULL_CLOCK_INDEX) = 0x0
[13:48:10.0360] AppleMultitouchN1SPI: successfully started
[13:48:10.0360] AppleH4CamIn::start - back camera expected
[13:48:10.0360] AppleH4CamIn::start - front camera expected
[13:48:10.0360] AppleH4CamIn::power_off_hardware
[13:48:10.0360] AppleAP3DSH::probe found device with ID: 0x3f
[13:48:10.0360] AppleAP3DSH::handleStart _calibrationMatrix [64699 -1892 -370] [-1570 65035 -244] [849 465 63854]
[13:48:10.0360] AppleAP3DSH::handleStart _calibrationOffsets [518853 -714699 -1661621]
[13:48:10.0360] AppleAP3DSH::handleStart - No calibration inverse matrix or the data is invalid, Compute locally
[13:48:10.0360] AppleAP3DSH::handleStart _calibrationInverseMatrix [66427 1929 393] [1599 66087 261] [-895 -507 67257]
[13:48:10.0360] AppleAP3DSH::handleStart _odr400HzSampleInterval = 2440
[13:48:10.0360] AppleH4CamIn::setPowerStateGated: 0
[13:48:10.0360] AppleCS35L19Amp: could not allocate control 395
[13:48:10.0360] AppleD1972PMUPowerSource: AppleUSBCableDetect 1
[13:48:10.0360] AppleD1972PMUPowerSource: AppleUSBCableType USBHost
[13:48:10.0360] AppleSynopsysOTGDevice::gated_handleUSBCableConnect cable connected, but don't have device configuration yet
[13:48:10.0360] AppleD1972PMUPowerSource: AppleUSBCableDetect 0
[13:48:10.0360] AppleD1972PMUPowerSource: AppleUSBCableType Detached
[13:48:10.0360] AppleSynopsysOTGDevice::gated_handleUSBCableConnect cable connected, but don't have device configuration yet
[13:48:10.0360] AppleMultitouchN1SPI: detected HBPP. driver will be kept alive
[13:48:10.0360] AppleD1972PMUPowerSource: AppleUSBCableDetect 1
[13:48:10.0360] AppleD1972PMUPowerSource: AppleUSBCableType USBHost
[13:48:10.0360] AppleSynopsysOTGDevice::gated_handleUSBCableConnect cable connected, but don't have device configuration yet
[13:48:10.0360] display-scale = 2
[13:48:10.0360] display-rotation = 0
[13:48:10.0360] found applelogo at /usr/share/progressui/[email protected]
[13:48:10.0360] found display: primary
[13:48:10.0360] display: 640 x 1136
[13:48:10.0360] found PTP interface
[13:48:10.0360] AppleSynopsysOTGDevice - Configuration: PTP
[13:48:10.0360] AppleSynopsysOTGDevice Interface: PTP
[13:48:10.0360] AppleSynopsysOTGDevice - Configuration: iPod USB Interface
[13:48:10.0360] AppleSynopsysOTGDevice Interface: USBAudioControl
[13:48:10.0360] AppleSynopsysOTGDevice Interface: USBAudioStreaming
[13:48:10.0360] AppleSynopsysOTGDevice Interface: IapOverUsbHid
[13:48:10.0360] AppleSynopsysOTGDevice - Configuration: PTP + Apple Mobile Device
[13:48:10.0360] AppleSynopsysOTGDevice Interface: PTP
[13:48:10.0360] AppleSynopsysOTGDevice Interface: AppleUSBMux
[13:48:10.0360] AppleSynopsysOTGDevice - Configuration: PTP + Apple Mobile Device + Apple USB Ethernet
[13:48:10.0360] AppleSynopsysOTGDevice Interface: PTP
[13:48:10.0360] AppleSynopsysOTGDevice Interface: AppleUSBMux
[13:48:10.0360] AppleSynopsysOTGDevice Interface: AppleUSBEthernet
[13:48:10.0360] AppleSynopsysOTGDevice::gated_registerFunction Register function USBAudioControl
[13:48:10.0360] IOAccessoryPortUSB::start
[13:48:10.0360] virtual bool AppleUSBDeviceMux::start(IOService *) build: Jun 11 2014 20:11:28
[13:48:10.0360] init_waste
[13:48:10.0360] AppleSynopsysOTGDevice::gated_registerFunction Register function AppleUSBMux
[13:48:10.0360] AppleSynopsysOTGDevice::gated_registerFunction Register function USBAudioStreaming
[13:48:10.0360] AppleSynopsysOTGDevice::gated_registerFunction Register function IapOverUsbHid
[13:48:10.0360] AppleSynopsysOTGDevice::gated_registerFunction Register function AppleUSBEthernet
[13:48:10.0360] AppleSynopsysOTGDevice::gated_registerFunction Register function PTP
[13:48:10.0360] AppleSynopsysOTGDevice::startUSBStack Starting usb stack
[13:48:10.0360] IOReturn AppleUSBDeviceMux::setPropertiesGated(OSObject *) setting debug level to 7
[13:48:10.0360] AppleBCMWLANCore::init(): IO80211-46 Jun 11 2014 20:10:03
[13:48:10.0360] [NAND] WMR_Open:420 FTL_Open [OK]
[13:48:10.0360] [NAND] _publishServices:642 FTL capabilities: 0x00000001
[13:48:10.0360] [NAND] _ppnvflGetStruct:3469 Checking borrowed blocks - count: 23 max_count: 23
[13:48:10.0360] [NAND] _fetchBorrowedList:881 number of borrowed blocks 16
[13:48:10.0360] [nand_part_core:INF@ 157] published partition 0
[13:48:10.0360] [nand_part_core:INF@ 157] published partition 1
[13:48:10.0360] [nand_part_core:INF@ 157] published partition 2
[13:48:10.0360] [nand_part_core:INF@ 157] published partition 3
[13:48:10.0360] [nand_part_core:INF@ 157] published partition 5
[13:48:10.0360] [nand_part_core:INF@ 157] published partition 6
[13:48:10.0360] 000828.945879 wlan.N[0] AppleBCMWLANCore::start(): Starting with MAC Address: <<<mac address>>>
[13:48:10.0360] 000828.946182 wlan.N[1] AppleBCMWLANCore::setPowerStateGated(): powerState 1, fStateFlags 0x20, dev 0xc476b000 (this 1, provider 0)
[13:48:10.0360] 000828.946197 wlan.N[2] AppleBCMWLANCore::setPowerStateGated(): Received power state change before driver has initialized, ignoring
[13:48:10.0360] IO80211Peer::addPhyStatistics Phy stats started for addr <<<mac address>>>
[13:48:10.0360] IO80211Peer::addPhyStatistics Tx Completion stats started for addr <<<mac address>>>
[13:48:10.0360] IO80211PeerManager::initWithInterface cant add monitoring timer
[13:48:10.0360] Started logging for intf
[13:48:10.0360] IO80211PeerManager::initWithInterface: inited peer manager
[13:48:10.0360] IO80211Interface::init peerManager=0x87cb8800
[13:48:10.0360] start:156
[13:48:10.0360] start:156
[13:48:10.0360] AppleARMBacklight::start: No AAP function
[13:48:10.0360] [effaceable:INIT] found current generation, 90, in group 1
[13:48:10.0360] [effaceable:INIT] started
[13:48:10.0360] [effaceable:INIT] started
[13:48:10.0360] AppleUSBDeviceMux::handleConnectResult new session 0x888ade70 established 62078<-lo0->49152 62078<-usb->4608
[13:48:10.0360] void AppleUSBDeviceMux::handleMuxTCPInput(mbuf_t) received reset, closing 0x888ade70
[13:48:10.0360] recv(9, 4) failed: connection closed
[13:48:10.0360] unable to read message size: -1
[13:48:10.0360] could not receive message
[13:48:10.0360] AppleUSBDeviceMux::handleConnectResult new session 0x888ade70 established 62078<-lo0->49153 62078<-usb->4864
[13:48:10.0360] AppleUSBDeviceMux::handleConnectResult new session 0x888adec8 established 62078<-lo0->49154 62078<-usb->5120
[13:48:10.0360] AppleUSBDeviceMux::handleConnectResult new session 0x888ade18 established 62078<-lo0->49155 62078<-usb->5376
[13:48:10.0360] void AppleUSBDeviceMux::handleMuxTCPInput(mbuf_t) received reset, closing 0x888adec8
[13:48:10.0360] recv(13, 4) failed: connection closed
[13:48:10.0360] unable to read message size: -1
[13:48:10.0360] could not receive message
[13:48:10.0360] void AppleUSBDeviceMux::handleMuxTCPInput(mbuf_t) received reset, closing 0x888ade18
[13:48:10.0360] recv(14, 4) failed: connection closed
[13:48:10.0360] unable to read message size: -1
[13:48:10.0360] could not receive message
[13:48:10.0360] AppleUSBDeviceMux::handleConnectResult new session 0x888ade18 established 62078<-lo0->49156 62078<-usb->5632
[13:48:10.0360] void AppleUSBDeviceMux::handleMuxTCPInput(mbuf_t) received reset, closing 0x888ade70
[13:48:10.0360] recv(9, 4) failed: connection closed
[13:48:10.0360] unable to read message size: -1
[13:48:10.0360] could not receive message
[13:48:10.0360] AppleUSBDeviceMux::handleConnectResult new session 0x888ade70 established 62078<-lo0->49157 62078<-usb->5888
[13:48:10.0360] void AppleUSBDeviceMux::handleMuxTCPInput(mbuf_t) received reset, closing 0x888ade70
[13:48:10.0360] recv(9, 4) failed: connection closed
[13:48:10.0360] unable to read message size: -1
[13:48:10.0360] could not receive message
[13:48:10.0360] AppleUSBDeviceMux::handleConnectResult new session 0x888ade70 established 62078<-lo0->49158 62078<-usb->6144
[13:48:10.0360] void AppleUSBDeviceMux::handleMuxTCPInput(mbuf_t) received reset, closing 0x888ade70
[13:48:10.0360] recv(9, 4) failed: connection closed
[13:48:10.0360] unable to read message size: -1
[13:48:10.0360] could not receive message
[13:48:10.0360] AppleUSBDeviceMux::handleConnectResult new session 0x888ade70 established 62078<-lo0->49159 62078<-usb->6400
[13:48:10.0360] void AppleUSBDeviceMux::handleMuxTCPInput(mbuf_t) received reset, closing 0x888ade70
[13:48:10.0360] recv(9, 4) failed: connection closed
[13:48:10.0360] unable to read message size: -1
[13:48:10.0360] could not receive message
[13:48:10.0360] AppleUSBDeviceMux::handleConnectResult new session 0x888ade70 established 62078<-lo0->49160 62078<-usb->6656
[13:48:10.0360] void AppleUSBDeviceMux::handleMuxTCPInput(mbuf_t) received reset, closing 0x888ade70
[13:48:10.0360] recv(9, 4) failed: connection closed
[13:48:10.0360] unable to read message size: -1
[13:48:10.0360] could not receive message
[13:48:10.0360] AppleUSBDeviceMux::handleConnectResult new session 0x888ade70 established 62078<-lo0->49161 62078<-usb->6912
[13:48:10.0360] void AppleUSBDeviceMux::handleMuxTCPInput(mbuf_t) received reset, closing 0x888ade70
[13:48:10.0360] recv(9, 4) failed: connection closed
[13:48:10.0360] unable to read message size: -1
[13:48:10.0360] could not receive message
[13:48:10.0360] AppleUSBDeviceMux::handleConnectResult new session 0x888ade70 established 62078<-lo0->49162 62078<-usb->7168
[13:48:10.0360] unrecognized key 'BootArgs' in value query
[13:48:10.0360] failed to handle value query for key 'BootArgs', sending back empty response
[13:48:10.0360] void AppleUSBDeviceMux::handleMuxTCPInput(mbuf_t) received reset, closing 0x888ade70
[13:48:10.0360] recv(9, 4) failed: connection closed
[13:48:10.0360] unable to read message size: -1
[13:48:10.0360] could not receive message
[13:48:10.0360] AppleUSBDeviceMux::handleConnectResult new session 0x888ade70 established 62078<-lo0->49163 62078<-usb->7424
[13:48:10.0360] unrecognized key 'MarketingPartNumber' in value query
[13:48:10.0360] failed to handle value query for key 'MarketingPartNumber', sending back empty response
[13:48:10.0360] void AppleUSBDeviceMux::handleMuxTCPInput(mbuf_t) received reset, closing 0x888ade70
[13:48:10.0360] recv(9, 4) failed: connection closed
[13:48:10.0360] unable to read message size: -1
[13:48:10.0360] could not receive message
[13:48:10.0360] AppleUSBDeviceMux::handleConnectResult new session 0x888ade70 established 62078<-lo0->49164 62078<-usb->7680
[13:48:10.0360] void AppleUSBDeviceMux::handleMuxTCPInput(mbuf_t) received reset, closing 0x888ade70
[13:48:10.0360] recv(9, 4) failed: connection closed
[13:48:10.0360] unable to read message size: -1
[13:48:10.0360] could not receive message
[13:48:10.0360] client protocol version 13
[13:48:10.0360] *** UUID 4B2AC217-7071-EC47-8945-EB5E2188BE49 ***
[13:48:10.0360] Restore options:
[13:48:10.0360] UUID => <CFString 0x19315c0 [0x2f3ad0]>{contents = "4B2AC217-7071-EC47-8945-EB5E2188BE49"}
[13:48:10.0360] MinimumSystemPartition => <CFNumber 0x1931510 [0x2f3ad0]>{value = +1660, type = kCFNumberSInt64Type}
[13:48:10.0360] SystemPartitionSize => <CFNumber 0x1930f50 [0x2f3ad0]>{value = +1660, type = kCFNumberSInt64Type}
[13:48:10.0360] SystemPartitionPadding => <CFBasicHash 0x192f3c0 [0x2f3ad0]>{type = mutable dict, count = 5,
[13:48:10.0360] entries =>
[13:48:10.0360] 2 : <CFString 0x1931540 [0x2f3ad0]>{contents = "128"} = <CFNumber 0x1931570 [0x2f3ad0]>{value = +1280, type = kCFNumberSInt64Type}
[13:48:10.0360] 3 : <CFString 0x1930f20 [0x2f3ad0]>{contents = "16"} = <CFNumber 0x192f3f0 [0x2f3ad0]>{value = +160, type = kCFNumberSInt64Type}
[13:48:10.0360] 4 : <CFString 0x192ede0 [0x2f3ad0]>{contents = "32"} = <CFNumber 0x1931250 [0x2f3ad0]>{value = +320, type = kCFNumberSInt64Type}
[13:48:10.0360] 5 : <CFString 0x1931960 [0x2f3ad0]>{contents = "8"} = <CFNumber 0x192ed50 [0x2f3ad0]>{value = +80, type = kCFNumberSInt64Type}
[13:48:10.0360] 8 : <CFString 0x1931180 [0x2f3ad0]>{contents = "64"} = <CFNumber 0x1931950 [0x2f3ad0]>{value = +640, type = kCFNumberSInt64Type}
[13:48:10.0360] }
[13:48:10.0360]
[13:48:10.0360] entering load_sep_os
[13:48:10.0360] device has no sep
[13:48:10.0360] entering partition_nand_device
[13:48:10.0360] device supports boot-from-NAND
[13:48:10.0360] nand device is already partitioned
[13:48:10.0360] entering wait_for_storage_device
[13:48:10.0360] Searching for NAND service
[13:48:10.0360] Found NAND service: IOFlashStoragePartition
[13:48:10.0360] NAND initialized. Waiting for devnode.
[13:48:10.0360] entering clear_remap_variable
[13:48:10.0360] executing /usr/sbin/nvram
[13:48:10.0360] entering format_effaceable_storage
[13:48:10.0360] effaceable storage is formatted, clearing it
[13:48:10.0360] effaceable storaged cleared
[13:48:10.0360] entering ramrod_probe_media
[13:48:10.0360] device partitioning scheme is GPT
[13:48:10.0360] find_filesystem_partitions: storage=/dev/disk0s1 system=/dev/disk0s1s1 data=/dev/disk0s1s2
[13:48:10.0360] executing /sbin/fsck_hfs
[13:48:10.0360] AppleD1972PMUPowerSource: limiting USB input current to 390 mA (measured 462 mA)
[13:48:10.0360] ** /dev/rdisk0s1s1
[13:48:10.0360] Executing fsck_hfs (version hfs-277.10.5).
[13:48:10.0360] ** Checking Journaled HFS Plus volume.
[13:48:10.0360] ** Detected a case-sensitive volume.
[13:48:10.0360] The volume name is Sochi11D257.N42OS
[13:48:10.0360] ** Checking extents overflow file.
[13:48:10.0360] ** Checking catalog file.
[13:48:10.0360] ** Checking multi-linked files.
[13:48:10.0360] ** Checking catalog hierarchy.
[13:48:10.0360] ** Checking extended attributes file.
[13:48:10.0360] ** Checking volume bitmap.
[13:48:10.0360] ** Checking volume information.
[13:48:10.0360] ** Trimming unused blocks.
[13:48:10.0360] ** The volume Sochi11D257.N42OS appears to be OK.
[13:48:10.0360] executing /sbin/mount_hfs
[13:48:10.0360] mount_hfs: Could not create property for re-key environment check: No such file or directory
[13:48:10.0360] /dev/disk0s1s1 mounted on /mnt1
[13:48:10.0360] entering check_for_restore_log
[13:48:10.0360] found restore log (size = 28347)
[13:48:10.0360] entering unmount_filesystems
[13:48:10.0360] error unmounting '/mnt2': Invalid argument
[13:48:10.0360] entering clean_NAND
[13:48:10.0360] NAND format complete
[13:48:10.0360] entering ramrod_probe_media
[13:48:10.0360] find_filesystem_partitions: storage=/dev/disk0 system= data=
[13:48:10.0360] entering format_storage_for_LwVM
[13:48:10.0360] entering ramrod_probe_media
[13:48:10.0360] device partitioning scheme is GPT
[13:48:10.0360] unexpected partition 'LwVM' - skipping
[13:48:10.0360] find_filesystem_partitions: storage=/dev/disk0s1 system= data=
[13:48:10.0360] entering create_filesystem_partitions
[13:48:10.0360] User specified system partition size, skipping firmware extras size.
[13:48:10.0360] system partition padding size is: 167772160 bytes
[13:48:10.0360] unable to open : No such file or directory
[13:48:10.0360] creating 2 partitions
[13:48:10.0360] creating encrypted data partition
[13:48:10.0360] entering ramrod_probe_media
[13:48:10.0360] device partitioning scheme is GPT
[13:48:10.0360] find_filesystem_partitions: storage=/dev/disk0s1 system=/dev/disk0s1s1 data=/dev/disk0s1s2
[13:48:10.0360] wipe entire partition: 1 (old = 0 new = 1820)
[13:48:10.0360] block size for /dev/disk0s1s1: 4096
[13:48:10.0360] /sbin/newfs_hfs -s -v System -J /dev/disk0s1s1
[13:48:10.0360] executing /sbin/newfs_hfs -s -v System -J /dev/disk0s1s1
[13:48:10.0360] Initialized /dev/rdisk0s1s1 as a 2 GB case-sensitive HFS Plus volume with a 8192k journal
[13:48:10.0360] block size for /dev/disk0s1s2: 4096
[13:48:10.0360] /sbin/newfs_hfs -s -v Data -J -P /dev/disk0s1s2
[13:48:10.0360] executing /sbin/newfs_hfs -s -v Data -J -P /dev/disk0s1s2
[13:48:10.0360] Initialized /dev/rdisk0s1s2 as a 13 GB case-sensitive HFS Plus volume with a 8192k journal
[13:48:10.0360] entering ramrod_probe_media
[13:48:10.0360] device partitioning scheme is GPT
[13:48:10.0360] find_filesystem_partitions: storage=/dev/disk0s1 system=/dev/disk0s1s1 data=/dev/disk0s1s2
[13:48:10.0360] entering mount_filesystems
[13:48:10.0360] executing /sbin/fsck_hfs
[13:48:10.0360] ** /dev/rdisk0s1s1
[13:48:10.0360] Executing fsck_hfs (version hfs-277.10.5).
[13:48:10.0360] ** Checking Journaled HFS Plus volume.
[13:48:10.0360] ** Detected a case-sensitive volume.
[13:48:10.0360] The volume name is System
[13:48:10.0360] ** Checking extents overflow file.
[13:48:10.0360] ** Checking catalog file.
[13:48:10.0360] ** Checking multi-linked files.
[13:48:10.0360] ** Checking catalog hierarchy.
[13:48:10.0360] ** Checking extended attributes file.
[13:48:10.0360] ** Checking volume bitmap.
[13:48:10.0360] ** Checking volume information.
[13:48:10.0360] ** Trimming unused blocks.
[13:48:10.0360] ** The volume System appears to be OK.
[13:48:10.0360] executing /sbin/mount_hfs
[13:48:10.0360] mount_hfs: Could not create property for re-key environment check: No such file or directory
[13:48:10.0360] /dev/disk0s1s1 mounted on /mnt1
[13:48:10.0360] executing /sbin/fsck_hfs
[13:48:10.0360] ** /dev/rdisk0s1s2
[13:48:10.0360] Executing fsck_hfs (version hfs-277.10.5).
[13:48:10.0360] ** Checking Journaled HFS Plus volume.
[13:48:10.0360] ** Detected a case-sensitive volume.
[13:48:10.0360] The volume name is Data
[13:48:10.0360] ** Checking extents overflow file.
[13:48:10.0360] ** Checking catalog file.
[13:48:10.0360] ** Checking multi-linked files.
[13:48:10.0360] ** Checking catalog hierarchy.
[13:48:10.0360] ** Checking extended attributes file.
[13:48:10.0360] ** Checking volume bitmap.
[13:48:10.0360] ** Checking volume information.
[13:48:10.0360] ** Trimming unused blocks.
[13:48:10.0360] ** The volume Data appears to be OK.
[13:48:10.0360] executing /sbin/mount_hfs
[13:48:10.0360] mount_hfs: Could not create property for re-key environment check: No such file or directory
[13:48:10.0360] /dev/disk0s1s2 mounted on /mnt2
[13:48:10.0360] entering resize_system_partition_to_options
[13:48:10.0360] User specified system partition size, skipping firmware extras size.
[13:48:10.0360] Found SystemPartitionPadding value of 167772160 bytes
[13:48:10.0360] Erasing system partition prior to resize operation.
[13:48:10.0360] block size for /dev/disk0s1s1: 4096
[13:48:10.0360] /sbin/newfs_hfs -s -v System -J /dev/disk0s1s1
[13:48:10.0360] executing /sbin/newfs_hfs -s -v System -J /dev/disk0s1s1
[13:48:10.0360] Initialized /dev/rdisk0s1s1 as a 2 GB case-sensitive HFS Plus volume with a 8192k journal
[13:48:10.0360] executing /sbin/fsck_hfs
[13:48:10.0360] ** /dev/rdisk0s1s1
[13:48:10.0360] Executing fsck_hfs (version hfs-277.10.5).
[13:48:10.0360] ** Checking Journaled HFS Plus volume.
[13:48:10.0360] ** Detected a case-sensitive volume.
[13:48:10.0360] The volume name is System
[13:48:10.0360] ** Checking extents overflow file.
[13:48:10.0360] ** Checking catalog file.
[13:48:10.0360] ** Checking multi-linked files.
[13:48:10.0360] ** Checking catalog hierarchy.
[13:48:10.0360] ** Checking extended attributes file.
[13:48:10.0360] ** Checking volume bitmap.
[13:48:10.0360] ** Checking volume information.
[13:48:10.0360] ** Trimming unused blocks.
[13:48:10.0360] ** The volume System appears to be OK.
[13:48:10.0360] executing /sbin/mount_hfs
[13:48:10.0360] mount_hfs: Could not create property for re-key environment check: No such file or directory
[13:48:10.0360] /dev/disk0s1s1 mounted on /mnt1
[13:48:10.0360] Trying to resize system partition to 1908408320 bytes aka 1820 MB
[13:48:10.0360] entering adjust_partition_preflight
[13:48:10.0360] partition:0 requiredSize=465920
[13:48:10.0360] no change in size
[13:48:10.0360] Successfully resized the system partition
[13:48:10.0360] entering maximize_data_partition
[13:48:10.0360] entering adjust_partition_preflight
[13:48:10.0360] partition:1 requiredSize=<<<<<IMEI>>>>>>6
[13:48:10.0360] maximizing data partition to 13946060799 bytes
[13:48:10.0360] entering adjust_partition_preflight
[13:48:10.0360] partition:1 requiredSize=3404800
[13:48:10.0360] no change in size
[13:48:10.0360] Successfully resized data partition to consume free blocks
[13:48:10.0360] The system partition now has a total HFS+ capacity of 1820 MB
[13:48:10.0360] entering ramrod_probe_media
[13:48:10.0360] device partitioning scheme is GPT
[13:48:10.0360] find_filesystem_partitions: storage=/dev/disk0s1 system=/dev/disk0s1s1 data=/dev/disk0s1s2
[13:48:10.0360] entering unmount_filesystems
[13:48:10.0360] entering ramrod_ticket_update
[13:48:10.0360] looking up root ticket hash
[13:48:10.0360] device tree ticket-hash: <CFData 0x1930040 [0x2f3ad0]>{length = 20, capacity = 20, bytes = 0x<<<<<<<<<<<<<<<<<<UDID>>>>>>>>>>>>>>>>>>}
[13:48:10.0360] ticket_hash: <<<<<<<<<<<<<<<<<<UDID>>>>>>>>>>>>>>>>>>
[13:48:10.0360] received valid ticket (2741 bytes)
[13:48:10.0360] entering restore_images
[13:48:10.0360] Successfully marked device node /dev/rdisk0s1s1 as static data
[13:48:10.0360] executing /usr/sbin/asr -source asr://localhost:12345 -target /dev/disk0s1s1 -erase -noprompt --chunkchecksum --puppetstrings
[13:48:10.0360] void AppleUSBDeviceMux::handleConnectResult(struct BulkUSBMuxSession *, errno_t) new session to port 12345 failed: 61
[13:48:10.0360] void AppleUSBDeviceMHello gamavranje,
Thanks for using Apple Support Communities.
The icons you're seeing on your iPhone indicate it is in recovery mode. Please plug your iPhone into your computer, and restore it with iTunes.
If you can't update or restore your iOS device
http://support.apple.com/kb/HT1808
Use iTunes to restore your iOS device to factory settings
http://support.apple.com/kb/HT1414
Take care,
Alex H. -
Troubleshooting power supply failures
I'm branching out this thread as a continuation of <http://discussions.apple.com/thread.jspa?threadID=2418851> since the topic has evolved and the subject is no longer accurate.
I have a 2.1GHz iMac G5 (iSight) that does not boot reliably and sometimes goes into deep sleep and can't be awakened. I have ruled out software and RAM issues, leaving power supply and logic board as the likely suspects. I'm leaning towards the power supply. I'd like more info on the symptoms of power supply failures and see if my symptoms are consistent with it.
*Reasons to believe it's the power supply:*
• symptoms are consistent with the computer not getting enough power.
• it's a more common failure.
• Computer has 4+ years of continuous usage.
• the left side of the vent had been warm lately (that fan pushes air over the HD then the PSU)
*Reasons to believe it's the power supply:*
• visual inspection showed no damaged capacitors (although there could be hidden damage)
• in my previous experience with power failures, the Mac shut down completely, not half way.
*Reasons to believe it's the logic board:*
• problem triggered by adding RAM (although that's not the only trigger and removing the RAM didn't • instantly solve the issue. Timing may have been a coincidence)
*Reasons to believe it's not the logic board:*
• It passed all the Apple hardware and Techtool Pro tests.FYI, you can access them in /private/var/logs, but you need to use a utility to show invisible files first.
The last system.log entry is
May 8 13:19:33 eric kernel[0]: IOPMSlotsMacRISC4::determineSleepSupport has canSleep true
So it looks like it went into sleep normally, but couldn't wake up or shut down without recording any more log entries.
windowserver.log had a few errors 20 minutes earlier:
May 08 12:56:56 [66] Server is starting up
May 08 12:57:00 [66] CGXMappedDisplayStart: Unit 0: boot screen
May 08 12:57:00 [66] CGXMappedDisplayStart: Unit 0: no display alias property
May 08 12:57:00 [66] CGXMappedDisplayStart: Unit 1: no display alias property
May 08 12:57:00 [66] AGCAttach: Couldn't find any matches
May 08 12:57:00 [66] CGXPerformInitialDisplayConfiguration
May 08 12:57:00 [66] Display 0x4271440: MappedDisplay Unit 0; Vendor 0x610 Model 0x9c51 S/N 0; online enabled built-in (0,0)[1680 x 1050], base addr 0xb0018000
May 08 12:57:00 [66] Display 0x3f003d: MappedDisplay Unit 1; Vendor 0xffffffff Model 0xffffffff S/N -1; offline enabled (2704,0)[1 x 1], base addr 0xb0018000
May 08 12:57:03 [66] GLCompositor: GL renderer id 0x00021802, GL mask 0x00000003, accelerator 0x0000281b, unit 0, caps 0x00000003, vram 128 MB
May 08 12:57:03 [66] GLCompositor: GL renderer id 0x00021802, GL mask 0x00000003, texture units 8, texture max 2048, viewport max {2656, 2656} extensions 0x0000000f
May 08 12:57:22 [66] kCGErrorFailure: CGXDisableUpdate: UI updates were forcibly disabled by application "Finder" for over 1 second. Server has re-enabled them.
May 08 12:57:22 [66] kCGErrorFailure: Set a breakpoint at CGErrorBreakpoint() to catch errors as they are returned
fsck_hfs.log shows the disk is fine:
/dev/rdisk0s3: fsck_hfs run at Sat May 8 12:56:40 2010
/dev/rdisk0s3: fsck_hfs run at Sat May 8 12:56:55 2010
/dev/rdisk0s3: ** /dev/rdisk0s3 (NO WRITE)
/dev/rdisk0s3: ** Root file system
/dev/rdisk1s3: fsck_hfs run at Sat May 8 12:56:55 2010
/dev/rdisk1s3: ** /dev/rdisk1s3 (NO WRITE)
/dev/rdisk1s3: QUICKCHECK ONLY; FILESYSTEM CLEAN
/dev/rdisk1s3: fsck_hfs run at Sat May 8 12:57:06 2010
/dev/rdisk1s3: ** /dev/rdisk1s3 (NO WRITE)
/dev/rdisk1s3: QUICKCHECK ONLY; FILESYSTEM CLEAN -
Power Supply Fan Always Runs Full Throttle - Mac Pro (Early 2008)
My Mac Pro has been almost flawless since I purchased it new in February 2008. I did not purchase the AppleCare because I rather naively assumed at the time that my shiny new Mac Pro was an invincible machine. (I was seduced by Apple after all!) Well, that was when I was younger (about 2.5 years ago) and before I knew about the actual cost of things like Logic Boards and Apple Power Supplies... Now the $250 AppleCare lifeline seems like a bargain!
The Problem:
1 week after installing Windows 7 64-bit to a separate internal hard drive using boot camp 3.1, my Mac Pro was playing music from the local iTunes library in Snow Leopard when the power supply fan revved up to 2760 rpm! I immediately tried rebooting the machine, resetting the PRAM and SMC several times, but the fans continue to throttle up to almost 2800 rpm within seconds of powering on the Mac.
I have run the Apple Hardware Test several times and every time it generates the same error code within 1 loop of either the extended or regular test:
4SNS/1/40000001: lp0C-0.000
An Apple Support technician was kind enough to "sneak" me a little bit of information about the error code. He told me the message is Logic Board Sensor related and could be caused by a faulty Logic Board, Sensor Board (Ambient Board?), Power Supply or possibly a faulty sensor that might be repairable.
Emotion:
Other than my 6 month old daughter eyeing the Mac Pro with the same suspicion she reserves for the Dyson vacuum cleaner, the computer still works fine--it hasn’t crashed in either Windows 7 64-bit or Snow Leopard and I haven’t noticed any unusual behavior. I had one other problem with this computer about 1 year ago when I installed Vista using boot camp. About a week after the Vista install, the OEM ATI HD 2600 XT completely died and I replaced it with a GTX 285.
I have grown a little suspicious about the efficiency of boot camp in the Windows environment, but perhaps the 2 separate boot camp installs and subsequent hardware failures are coincidence or related to the hardware issue I am yet to resolve...?
Hopefully, someone in the Apple community will offer guidance to a swift and economical solution!
Thank you in advance for your time.
Some Data:
iStat Pro Info
CPU
User: 0%
Nice: 0%
Sys: 0%
Idle: 100%
TEMPs (in Fahrenheit) - There was no entry for Power Supply Temp in iStat!
HD1: 90
HD2: 90
HD3: 92
HD4: 92
CPUA: 88
CPUA: 86
CPUB: 88
CPUB: 86
Ambient: 76
Expansion Slots: 94
HD Bay1: 83
HD Bay2: 83
HD Bay3: 83
Hd Bay4: 81
Mem Bank A1: 106
Mem Bank A2: 99
Mem Bank A3: 99
Mem Bank B1: 92
Mem Bank B2: 92
Mem Bank B3: 94
Mem Module A1: 130
Mem Module A2: 126
Northbridge: 106
FAN SPEED (rpm)
Power Supply: 2760
Exhaust: 600
CPU Fan: 500
HD/Expansion: 800
Hardware Overview
Model Name: Mac Pro
Model Identifier: MacPro3,1
Processor Name: Quad-Core Intel Xeon
Processor Speed: 2.8 GHz
Number Of Processors: 2
Total Number Of Cores: 8
L2 Cache (per processor): 12 MB
Memory: 2 GB
Bus Speed: 1.6 GHz
Boot ROM Version: MP31.006C.B05
SMC Version (system): 1.25f4I had the same problem. The solution was replacing the Power Supply.
Because i had Apple Care there where no costs. -
Power Supply Status Changed - every 12 seconds
Server Monitor shows all green for all components, but the log shows a red message every 12 seconds "Power Supply Status Changed". The power is coming through an APC UPS device, which also appears to be working fine. Any ideas?
Xserve G5 Dual Mac OS X (10.4.5)Last night I got an Email:
Subject: Server Problem Notification
A problem has been detected on this server.
============================================================
Status Summary
Reason(s) for notification:
Power
Server:
Host : geekho
Model : RackMac3,1
Uptime : 17952 minutes
OS version : Mac OS X Server 10.4.6 (8I127)
Processor : 1 x 2000 MHz
Memory : 2048 MB
BootROM : $0005.17f2
Serial : QP6170FQSLX
Memory:
Memory Slot "DIMM0/J11" : 1024MB, ECC DDR SDRAM, PC3200U-30330
Memory Slot "DIMM1/J12" : 1024MB, ECC DDR SDRAM, PC3200U-30330
Drives:
Drive 1 (disk0) : Normal
Drive 2 (disk1) : Normal
Network:
en0 ( active) : Normal
Sensors:
CPU 1 Power : 12.55 watts
1.5v : 1.49 volts
3.3v Trickle : 3.30 volts
5v : 5.04 volts
12v Trickle : 12.06 volts
1.2v : 1.18 volts
Behind the DIMMs : 52.00 C
1.8v : 1.80 volts
System Bus IO VDD : 1.46 volts
PCI Slots : 45.00 C
DDR IO : 2.63 volts
DDR IO Sleep : 2.63 volts
3.3v : 3.30 volts
3.3v Sleep : 3.28 volts
5v Sleep : 5.07 volts
12v : 12.00 volts
System Controller Vcore : 1.71 volts
1.5v Sleep : 1.51 volts
1.2v Sleep : 1.18 volts
Between the Processors : 34.00 C
CPU 1 Internal : 46.02 C
CPU 1 12v : 0.94 amps
CPU 1 Vcore : 1.27 volts
CPU 1 Core : 9.89 amps
System Controller Internal : 55.75 C
CPU 1 Ambient : 38.00 C
System Controller Ambient : 44.00 C
CPU 1 Inlet : 30.00 C
CPU 2 Inlet : 27.50 C
Controls:
CPU A1 : 3973 RPMs
CPU A2 : 3988 RPMs
CPU A3 : 4002 RPMs
CPU B1 : 3992 RPMs
CPU B2 : 4017 RPMs
CPU B3 : 3982 RPMs
System Controller : 5585 RPMs
PCI Slot : 3890 RPMs
Clock Slew :
Security:
Enclosure Intrusion : No
============================================================
I don't see anything wrong (CPU power?), and the Server Monitor app shows all green lights and everything "Normal" except CPU Core amps at 7 amps peaking to 10.25 or so, which it calls "High".
What (if anything) is wrong, and what (if anything) should/could I do to fix it? Is this related to the original problem?
Thanks! -
Shock Therapy - An Athlon64 / FX Power Supply Guide
I used to make a hardware list of all the components I would like to incorporate in my next
computer build. Normally...at the bottom of that list would be the power supply, not that I
didn't think it was important, it's just that my other hardware was so interesting! Today, power supplys
seem to take a back seat to blazing-speed CPU's, Dual-Cored processors, glitz and glamour
video cards...not to mention supersonic, heat-sinked RAM and modular, gizmoe'd PSU's promising not
only over-achiever specifications, but eye-candy as well. The lowly PSU....tucked up somewhere inside
it's dark and lonely loft....effortlessly supplying us with the energy required for important 3D imaging
or just funning with the latest games.
What a power supply does is rather simple. It converts your office or home's socketed electricity to
usable 3.3v, 5.0v and 12.0v energy...that's all. A power supply that cannot efficiently do this will-
over time-cause computer crashes, continuous reboots and shutdowns, and worse...expensive component damage.
And now, with faster processors such as AMD's Athlon64 and FX line of CPU's, never has there been a time, when
choosing the right power supply is so important! This article is written for those using these high-powered CPU's!
Well...Do we have your attention!?
If you are experiencing these problems, or still scratching your head over that last RMA....could be
your PSU is trying to tell you something.
To begin with, a power supply's ratings refer to its maximum output under ideal conditions. No power
supply is 100% efficient. In high-quantity manufacturing, power supplys may not put out any more than 60% of
their advertised specifications. In any PSU, that rating can be further reduced by the effects of heat
and electro-magnetic radiation. That's where "switching" power supplys come in. A switching power supply draws
only as much current that is needed from the AC input. Buying a hefty PSU with this feature will guarantee
that you will be paying no more for electric service, than you would with a cheaper, less powerful unit.
One of the most common causes of power supply inefficiency, and ultimately failure is dirt. Dust and
foreign materials can cause the beginning of the end for a power supply, by attacking the fan first.
It begins by slowing the fan down...thus creating heat through friction, then ultimately burning it out.
PSU's with high-quality ball bearing fans are a must. They are far more durable, and not as likely to
become noisier as time goes by.
As a general rule...a failing PSU will usually emit abnormal sounds, followed by unstable voltage readings....
then the computer crashes or lock-ups, with random shutdowns, and sometimes...refusal to even power-up.
If you think your power supply is on its last leg...better to deal with it now, or face the more serious dilemmas later on.
APM (Advanced Power Management)
APM is a feature originally developed by partners, Microsoft and Intel. It relates to a systems ability
to utilize different states in regards to a systems utilization of power. On, Off, Standby and Suspend
are examples...these are BIOS features, not PSU functions. APM only requires of the power supply, the
function to turn power on or off through an electrical signal, and the presence of stand-by voltage.
All ATX power supplys are required to incorporate this feature. However, if some components in a computer
are not APM-compliant, your system may encounter errors or freezes when going into hibernate or stand-by
modes.
ACPI (Advanced Control Power Interface)
It's the latest power management control that was developed by a conglomeration of IT corporations. This interface
is O.S. derived, rather than BIOS, and all ATX power supplys should be ACPI-compliant. You should not have to be
concerned about this feature.
Line-Conditioning Circuitry
A power supply component that helps control power levels, spikes and surges in
the most unreliable of home sockets.
EMI Filter
This circuitry smooths the fluctuations of incoming AC currents, also known
as Electro-Magnetic Interference - EMI filters are usually found in higher-end power supplys.
PFCC
Power Factor Correction Circuitry...smooths out sudden, initial spikes in power
delivery - reducing amplitude and preventing circuit overloads.
Connectors
There are five main connectors found on the latest version ATX power supply.
1) ATX main power connector - 20-pin, 24-pin, and 20 to 24-pin adapter.
2) ATX 12v power connector (4-pin to CPU)
3) Molex peripheral power connector
4) Floppy power connector
5) Serial ATA power connector
On newer SLI-certified power supplys, you'll find two 6-pin video card connectors.
Know What You Need
When purchasing a power supply, make sure your parts list is all-inclusive...know ahead of time, what you expect to
install in your system. You should also visit the motherboard manufacturer's site, as well as the CPU's. Most of the
products will have specifics regarding power supply requirements needed for that specific component. Unfortunately, you
really won't know how well the PSU performs until it is installed and running your system (hopefully!) This is the main reason we
recommend the most popular brands - power supplys that have shown a duration of manufacturing quality over the years. Those are
as follows: Antec, Enermax, OCZ, PC Power and Cooling, Tagan, and a few newcomers such as SeaSonic and Silverstone are
worth looking into.
If you believe you have found the PSU of choice, remember this: AMD recommends a minimum 350 watt power supply to run
Athlon64 and FX CPU's. To that, add the 30% for power lost to heat, and the subsequent electro-magnetic radiation. Hold on with that
calculator...throw in an additional 40% to 60% for the "potential" inaccuracies of specifications inherent in mass-produced electronics.
Pay special attention to outputs on either single, or dual rail +12v lines. A motherboard, CPU, and graphics card can consume up to
150 watts alone - before hooking up your remaining components. If running an SLI configured board, look for a PSU that is certified
to run that configuration...there's only a few PSU's that lay claim to that!
Broken down, you can look at it this way: An Athlon64/FX processor can use up to 90 watts off the +12v rail. High performance RAM
can take in about 25 watts for each stick of 256MB system memory from the +3.3v line. PCI cards will use about 10 watts each, while
an AGP video card can consume about 50 precious watts alone from the +5v or +12v. Hard drives? A 7,200 RPM drive...about 15 watts
each, taken from the +5v and +12v rail. Finally, but not absolutely is the optical drives...robbing about 20 watts each, also from
the +5v and +12v lines. So you see....not only is the +12v amp ratings of concern, but also the +5v line!
In doing the math...on a system incorporating an Athlon64 (say a 4000+), 2 sticks of high-end RAM, 2 or 3 PCI cards, 1 mid-to-high
end AGP video card, 2 ~ 7,200 RPM hard drives, and a couple of CD/RW or DVD/RW opticals...you're looking at a "base" requirement of 270 to 325 watts. That's for a running system...now figure boot-up loads, 30% for heat and radiation bleed-off, then a 40% safety factor for manufacturing inconsistencies...you've got a power supply in the 450 to 520 watt range!
Modular Power Supplys:
The pins that are used for the modular plugs are not very good at passing current. It's basically electrical resistance between the male and female components, and voltage "drops" are likely. In real world events, they will become loose, dirty, corrosive, and eventually burn. You can figure about 10% less efficiency with a modular power supply.
Now you can understand how manufacturing "tolerances" that are inaccurate by 40% to 60%, can have such a devastating effect on
the performance of your new system. If you follow these simple guidelines, bearing in mind the hardware you will be using, and what
your intended use of the computer is for...then it will be one less dramatic incident when pushing the power button for the first time!
Here's a neat little tool....a bit out of date - that can give you a basic idea of what you'll need in a PSU.
You can apply the percentages above, for an even more accurate assesment of your PSU requirements!
http://www.jscustompcs.com/power_supply/Power_Supply_Calculator.php?cmd=AMDQuote
In doing the math...on a system incorporating an Athlon64 (say a 4000+), 2 sticks of high-end RAM, 2 or 3 PCI cards, 1 mid-to-high
end AGP video card, 2 ~ 7,200 RPM hard drives, and a couple of CD/RW or DVD/RW opticals...you're looking at a "base" requirement of 270 to 325 watts. That's for a running system...now figure boot-up loads, 30% for heat and radiation bleed-off, then a 40% safety factor for manufacturing inconsistencies...you've got a power supply in the 450 to 520 watt range!
Well, except the CPU, my system has all that you mentioned there (I even have 3 optical drives). And my 350W PSU has been rock solid for more than a year (BeQuiet, = Tagan, IIRC). I don't think a 4000+ needs 100W more than my 3200+ . And that link you posted says that the minimum recommended PSU for my system is 506W xD. Come on.
Oh, and in the place I work there are 6 amd64 with GeForce 6800 GT and 2GB RAM with 380W Antec PSUs. All 100% stable, of course.
I would only go for >400W if I wanted to do extreme OC (with overvolting), or SLI. Otherwise, a good brand 350W PSU is more than enough. -
Choosing the Right Power Supply
First things first. If you've got a poor-quality and/or faulty power supply, nothing else you do will work to solve your problems. Stick to the basics before you go further...The short answer is to buy a hi-powered, brand name supply, like the new ENERMAX line (430 W or higher) or ANTEC True550. Almost nothing else will do with today's computers. In over 30 years of electronic/computer service, I have found that 85% or more of problems were power-related.
If you want to know more, read on...
Choosing The Right Power Supply
If you’re reading this, there’s a good chance that one of my colleagues or I believe that you could be experiencing problems with your power supply, based upon the symptoms you mentioned in your post, and provided you with this link. Relax, you’re not alone. In 30 years of electronic and computer troubleshooting, I’d say that the majority of the electronic, mainframe, mini, and microcomputer problems I’ve diagnosed and repaired were with the basic power the problematic device was receiving. The symptoms often included random reboots, crashing, the BSOD, lockups, etc.
(As the national support technician for few major computer service companies, working US Defense contracts, I was often the person that had to fly in and correct the problem, or “walk through” the on-site technician as he closely followed my instructions. I achieved success in my career by carefully reading the manuals, knowing where to go for more information that was otherwise unavailable to me, and/or systematically troubleshooting until the problems were discovered and repaired. I never had the option of giving up.)
The most overlooked component when building or upgrading a PC is the power supply unit (PSU). Some people use their old case and PSU when they upgrade. Some use the PSU that came with their new case. Some people even buy a new PSU. And most inexperienced builders all make the same mistake: The PSU that they’re trying to use is simply inadequate for the job.
Suppose you’re upgrading to a new motherboard, CPU, ram, and video card, but still using the old case and PSU. It’s most likely that you’re upgrading in order to build a machine that is more powerful, faster, has a more colorful display, can number-crunch more quickly, play the latest games, etc. These gains in performance all have one thing in common: They require more raw power. However, have you thought about where that power comes from?
Suppose you’re building a new system with a new case and PSU. Has it occurred to you that the company that you bought the case/PSU from might make more money if they skimp on the supply, even if the supply has a large wattage rating? Most bulk power supply manufacturers don’t make good PSU’s. They use older, cheaper technology, and slap on labels that represent the PSU’s peak outputs, and not their continuous output rating. These companies are intentionally misleading you in order to sell you an inferior product. Brands I avoid when building/repairing my friends’ and family’s computers: Allied, Q-Tec, Chieftech, and many others.
For those of you who bought a power supply separately, did you know that you’re only supposed to run a power supply continuously at 30-70% (with 50% being optimal) of its continuous rating for maximum efficiency (which means less heat to you)? Most inexperienced builders either buy PSU’s that are matched to their equipment’s continuous power usage, or ones that are even less powerful than they need. Why? Because they’re trying to save money.
I mean, what’s the fun in a power supply? You don’t get any games with it, there’s no more storage, hardly ever any more bells and whistles, etc. A power supply is boring, and it’s supposed to be, because it’s supposed to provide a stable, reliable platform upon which the rest of the equipment can easily access the amount of power it needs, and when it’s needed. In almost EVERY review of powers supplies, the same point is stressed: Better safe than sorry.
But what does safe vs sorry mean? It can mean that you don’t have to waste money on the wrong PSU in the first place, but it can also mean that you don’t have to replace your expensive ram, CPU, video card, etc. NEEDLESSLY, or because your cheap PSU destroyed them. What? A cheap power supply can wreck your computer? YES IT CAN. A cheap power supply can cause thermal damage, not only from the heat it produces, but also the heat it can create in your components as well. RAM is especially sensitive to heat, and there’s RAM in your CPU, your video cards, and, well, your RAM too. A cheap switching power supply, run at its maximum, or peak, continuously can also destroy components by creating RF (Radio Frequency) signals on your power rails, signals which the components on your peripheral devices were not equipped to handle in the first place.
So this begs the question, how does one choose the right power supply? I’ll illustrate this using my own PC as the example. This is my setup that I use for video processing:
K7N2G-ILSR
Athlon 2500+ Barton @ 2125Mhz
AMD Retail Heatsink/Fan
2 - 512MB DDR333 w/Thermaltake Spreaders (slot 1&3)
MSI TV@nywhere Video Capture
ATI Radeon 9600
120GB Maxtor DiamondMax Plus 9 SATA
30GB Quantum IDE
TEAC DV-W50E DVD/CD-R/W
BTC DVD-ROM Drive
Artec CD-R/W
Using this Power Supply Calculator link:
http://www.jscustompcs.com/power_supply/
I plug in all my equipment values, but some of this can be a little tricky. For example, since I often run the CPU like an XP 3000, I choose the 3000 as my processor; it’s the same chip run at the faster rate. I also choose the ATI Radeon video card, and I select the RAM wattage for 2 sticks of DDR. I also choose every card I have, like my video capture card, but I also select the boxes for the separate cards that correspond to the functions that my ILSR provides as well (and that I use), like sound, USB, Firewire, NIC, etc. Although I use the onboard SATA controller, I don’t select the SCSI PCI card, because, in truth, I’ve probably made up for it by selecting all the other corresponding devices, including cards that the motherboard replaces. I check the boxes for the fans and drives I use, and I’m done, right?
Not yet.
I just remembered that I plan to upgrade soon, so I go back and change the values to reflect my impending changes. I mean, I want to make sure that I have enough power to begin with so that I don’t have to replace the power supply again, right?
Ok. Done. I look at the bottom and see that it tells me that I need a 468 watt PSU. So a 480 watt supply will do, right? Wrong.
Remember that, for efficiency, long-life, and less heat, you want your actual power consumption to fall between 30-70% of the PSU’s rating, so add 30% (minimum) to the 468, and you get 468 + (468*.30)= 608 Watts! Holy Cow!
However, I’d only need a 608-Watt supply if I was using all the devices at once, and I don’t. But, in truth, with video and audio processing, I often get close when I process, burn, and monitor at the same time. (Hardcore gamers also get close a lot, as they blast the sound and push that video to its limits.) So, let’s take off 10% (maximum) of 608, for a total of 541 Watts.
I need a 550 Watt supply, but not just ANY 550 watt PSU. I need a supply that can give me enough power on the critical 3.3, 5, and 12V rails combined. I also want a supply from a trusted, name-brand manufacturer, so I start hitting the many online reviews. Here are just two from Tom’s Hardware:
http://www6.tomshardware.com/howto/20030609/index.html
http://www6.tomshardware.com/howto/20021021/index.html
Read these in their entirety. I didn’t post them because they’re pretty links.
In the end, I chose Antec, because they’ve got the reputation, the recommendation, and because the Antec True550 has better specs than the rest of the 550 Watt competition. I also bought it from a reputable company I found on Pricegrabber.com, for the lowest price I could find, $95.00 shipped to my door. (In truth, I wanted two mini-redundant supplies, like the hospitals and military use, but they were too expensive.)
The result? Not only are the random reboots, crashing, the BSOD, lockups, etc., gone like magic, but I also now have “peace of mind” in that whatever might happen to my equipment in the future, I know almost for certain that the PSU is NOT the problem. I also bought an UPS, because the East Coast Blackout proved to me that even the Antec True550 isn’t going to provide me any power for emergency shutdown if it doesn’t get its power from somewhere.
Even if your problem doesn’t lie in the PSU completely, it gives you a GREAT platform for troubleshooting further. If you’re not reasonably certain that the supply is the cause, borrow one, or buy one that you can return once you’ve solved the problem. But, above all else, BUY THE RIGHT SUPPLY before you do anything else! Otherwise, you could be plugging and unplugging components, buying and blowing up expensive memory, and causing even further damage, until you give up or die.
I mean, I assume you built your own system to enjoy “more bang for your buck,” right? What’s the fun of a random reboot in the middle of Unreal Tournament 2003?
William Hopkins
Former Staff Sergeant, USAF
B.A., B.S., with Honors
The University of California, San Diego
[email protected]
P.S. It should be noted that while Enermax, ThermalTake, Zalman, Fortron, and others make great PSU’s, and I compared and considered them, the Antec still won out overall in my critical evaluation, like it did in so may others’ reviews. You’d probably be ok if you went with another reputable manufacturer as listed above, but pick a supply that gives you at least 230 watts on the 3.3 and 5V lines combined, and still meets the 30% criteria as stated above. Remember, if the manufacturers don’t give you maximum combined specs up front, they’re untrustworthy right off the bat. With power supplies, you definitely end up getting what you pay for. Don’t say nobody warned you.
P.P.S. Update! After recent developments, it looks like Enermax is the leader, but only the latest line of PSU's.Ok, as an electrical engineer...I have to step in here! LOL
First, these amp rating are for 2 +12 rails. That is why you see a protection of around 15-18A on the +12 rail. That means each Rail is allowed up to 18A lets say for the new Enermax 1.2 version like the one I have.
Now, Lets say 18A for 12V....well as you know the Abit NF7-S uses the 12V for powering the CPU.
Lets say you have a Barton like me and you want it stable at around 2.4-2.5Ghz. You will have to put lets say around 2V to the cpu to get it stable at that kinda speed, specially if you have high FSB like I do. So 12V * 18Amps = 216W ....well the converter on the NFS-7 is really bad, its loss on the step down convertion is probably around 25% along with the PSU lost cuz its not running at 25oC (another 15%)....you will actually only get around 100-120W for the CPU.
Now, if you go into Sandra and see how much a Barton eats up at 2.4Ghz you will see its around 110Watts.
So, if you wanna push more, dont even think about it! Prime Power test fails and your +12 rail will drop as low as 11.60 Volts.
Now, lets say you got yourself a AMD 64 bit chip and you wanna overclock it....I bet it will need more than 110Watts.
So, what im saying is, dont buy nothing less than a 500 Watt PSU!
You really need around 20-22 A on the main +12 along with really really good cooling on the case and PSU so it is running at a 100%.
http://forums.amdmb.com/showindex.php?s=&threadid=287828
i found this quite interesting especially the bit re the power loss turning the 12v into 1.6v or what ever cpu needs -
Power supply vs. logic board? turns off in sleep mode.
My imac g5 (2004 - 1st generation?) is either turning completely off or going into some un-wake-up-able mode after it's put to sleep. (I have to switch off/on the power strip and turn the computer on all over again.) And sometimes if it's sleeping (power light pulsing on front) it may or may not wake from sleep by pushing the power button. Often touching a key in that circumstance will cause it to crash, so I've quit using that altogether as a method of waking it up. I've reset the SMU a number of times throughout the past few months and it has not cleared up this problem.
Last night after I put it to sleep it switched in to the un-wake-up-able mode. I could still hear something running (not a fan, just an electrical hum) where it seems like it's crashed and can't shut itself off. I had to turn off the power and try to turn the computer back on. It wouldn't respond the first couple times. Then the power light glowed for a while but it still didn't turn on completely. After a few more minutes I tried again. Maybe I held the power button for too long, but I heard a long single beep, the fans whirred, and then everything started up as usual.
I've read a number of threads seemingly related to these issues, but am now not clear about whether this is a power supply issue or a logic board issue. I have yet to open the back and check for bulging capacitors. Just thought I'd ask here first.I am having a very close issue too (posted also in a more recent thread about power button not functioning). My old iMac G5 20 inches got a power supply that went bad two years ago. I had it replaced and all went fine until two weeks ago.
My wife was using it, while I was away: machine shut down with a 'pop!' sound.
She tried to start it up again, but after pressing the button a couple of times - the last one longer - she had a long strong peep. The machine went on for a while and then off again. Scared, she left it off.
After checking, no reported issue seems to fit to the problems shown: power supply is working; logic board too. The machine is working fine, but on sleep, it dies out. While doing tasks, at undetermined times, it shuts down with a 'pop!'. Sometimes you can restart it immediately. Sometimes you can't and have to wait one or more hours. No evidently bad caps on board, led check returns 1 (no 2 flashing or attempting to turn on) with dead computer, otherwise all working fine. Hardware test also passed. Console messages have nothing relevant or clearly understandable to offer.
Still can't figure out a solution. Many user are pretty fast in suggesting to bringing the machine to Apple. Unfortunately not all around the world we have/need cars. And getting the 20 kg of iMac by feet/metro to the shop it ain't such a nice walk. When I fried the power supply, there was no sufficiently large box on sale to pack the computer and have it send to the shop. I had to wait for the technician - on a convenient day - do drop by and take it (and he knew he was going to repair it)!
Will post, if I have further developments. -
IMac G5 20" power supply problem
The power supply on my 20" G5 recently fried. Somehow I had the activity monitor showing that the "FaxJobMgr" was using about 70% of my cpu. I had had that problem before and the computer was very warm. I quit that process but shortly after that there was an acrid smell that I ultimately found was coming from the power supply. When I re-started everything came up to the desktop but then it shut down just as if the plug were pulled. I see that there were many issues with the power supply on this first generation G5. I took it to the Apple Store and they say it is the power supply AND there appears to also be damage to the logic board. $734. I'm wondering if maybe its only the power supply and they are just being cautious that there might be damage to the logic board so just replace it or buy a new computer. I thought I might try to replace the power supply only, but then that seems to be about a $120 that might be gone. Any thoughts would be greatly appreciated. Thanks
Generally speaking, the defects which affect a logic board and power supply in that family of products are similar, but there typically exists no causal link between them. It is possible to have a logic board affected by the defective electrolytic capacitor issue, a defective power supply, or both.
You can readily determine if the logic board is defective by examining the clusters of capacitors on the logic board for bloating, distended tops or leakage. If they exhibit such symptoms, your logic board can be repaired for $ 189.00 by contacting this company.
You may also need to replace the power supply, thought that determination is best made once the logic board as been verified as good or bad, and replaced, if you elect to do so. Power supplies for this product family generally cost roughly $ 139.00, and are user replaceable. Replacing the supply in a unit which exhibits the defective capacitor issue will not correct the logic board related problem, and may—under relatively rare circumstances—cause the eventual failure of the replacement supply.
*I may receive compensation as a result of parts or services being ordered by users specified at the link shown in this message. -
I have an iMac G5 that has already been affected (2.5 years ago) by the power supply issue. A few days ago, I was on my iMac, and it turned off and won't turn back on. I called the Apple customer relations line and they told me that I was SOL and its not even a month after the three year marker from the purchase date. I've read on other messages that some people have had Apple replace their power supply for free even after the three years, but they told me that I would have to pay for it myself. Does anyone know how I could get it fixed? If not, what would it cost and is it even worth it? Will the power supply just keep failing?
-AmandaI think it depends entirely on the representative spoken to, the stock available at that particular moment, the chemistry between the the tech and the Apple customer and perhaps the phase of the moon.
-
Powermac G5 Squeals, from power supply?
About for the last month I have been hearing squealing from my G5 2.7 Dual in the morning and over my lunch break. The odd thing is it never does it in the evening when I get home from work. This leads me to believe its temperature related because my heat is around 67 until I get home from work which is then 72. Another thing I have noticed is it will squeal whether the computer is on or off. I have put my ear beside the G5 and sounds like it is emitting from the bottom where the power supply is. I am a consumer electronics technician and have the same symptoms on TV's with noisy coils in the power supply, that is helping my theory on the power supply. Has anyone else had this problem or am I one of the few instances, also any help would be appreciated?
Try running SystemLoad once.
http://www.bresink.com/osx/SystemLoad.html
You might try turning off NAP to get rid of the noise.
http://www.macosg.com/group/viewtopic.php?t=2946
-Bmer
Mac Owners Support Group
Join Us @ MacOSG.com
An Apple User Group
MacOSG Podcast >>
Disclaimer required by Apple Discussions Terms of Use: MacOSG - a non-profit Apple User Group - may receive some form of compensation, financial or otherwise, from my recommendation or link. -
Excessive log entries with buffalo linkstation
Hi all,
I am getting excessive log entries on my MacBook Pro (OS 10.6.7) that appear to be related to my Buffalo LinkStation HD-CELU2 external drive. This drive is connected to my Airport Extreme (latest firmware) via USB and acts as my iTunes (10.2.2) library, which also serves as the music source for a Sonos digital music system. A sample of the log entries follow:
4/18/11 8:15:22 PM com.apple.launchd[1] (jp.buffalo.NASPower) Throttling respawn: Will start in 60 seconds
4/18/11 8:15:39 PM com.apple.launchd.peruser.501[131] (jp.buffalo.NASPower[6798]) posix_spawn("/Library/PrivilegedHelperTools/NasNavigator2.app/Contents/MacOS/Na sNavigator2", ...): No such file or directory
4/18/11 8:15:39 PM com.apple.launchd.peruser.501[131] (jp.buffalo.NASPower[6798]) Exited with exit code: 1
4/18/11 8:15:39 PM com.apple.launchd.peruser.501[131] (jp.buffalo.NASPower) Throttling respawn: Will start in 60 seconds
It says that a file isn't found, and that could be because I uninstalled NASNavigator in an attempt to get rid of these extraneous log entries. Uninstalling the software seems to have only resulted in changing the messages (to "no such file"), not reducing or ending them.
This log entry is constant; it occurs even when the computer has no need to access the Buffalo hard drive. It makes it very hard to diagnose any other issues because it both clutters the log and causes it to only recall a couple of hours worth of log info.
Thanks in advance!Ho everyone, just registered as I have a Bold 9900 and am considering a Playbook with the new OS2. Does anyone know whether I will be able to get it to talk to my Buffalo Linkstation. think its a Pro Duo 2 and is about 2-3 years old.
Maybe you are looking for
-
How to execute availability check against delivery date in purchase order
Hi all In MD04, I know that "available date = delivery date in purchase order + GR processing time" & "GR date = delivery date in purchase order". When I execute availability check in production order, I will get material's committed date = available
-
How to fix blue screen of death of windows xp with a bootcamp hard drive
i have a macbook with intel 2 duo core with 4gb ram and 1tb hard drive with lepord on it i bootcamped the hard and installed windows xp and now i am gettind a blue screen of death. so i know there repair utlite on windows xp disc when you boot to it
-
Images, Thumbnails, byte[ ] and BLOB
Hi guys, This is what I have to do: User selects image from disk and i'm putting it into DB (IBM DB2 8.0). That's clear. No problem. But I need that image as a thumbnail as well (I have to show images as thumbnails for each Item). I have a DB table I
-
How can I install a custom ringtone to my iPhone 6 Plus
I want to install and use custom ringtones that did not transfer from my old Android to my new iPhone. How can I get my old ringrtones (not from the iStore) onto my new phone and then assign them to my contacts?
-
Hi, I have a connection between a measurement roboter and LabVIEW. I transmit the data above an TCP connection (for example the coordinate plane of the sensor). I have different ports to transmit the data. Is it possible to save the transmitted data