Lacie 200 GB FW400 Power Supply
I was doing some negative scanning the other day using my Nikon Super Coolscan 9000 and accidentally turned on my one of my Lacie drives at the time, which the Nikon scanner doesn't like. Every time it happens, the scanner stops in its tracks.
Anyways, this time, I noticed that the Lacie drive didn't power up all the way and just kind of got stuck and stuttered on the power up. I shut it down using the blue button on the front and kept on scanning, figuring a reboot when I was done would fix all, but it didn't.
The drive kept refusing to start up, even after I changed firewire cables and ports. I had given up when I got one last idea... I took the power supply from another of my Lacie drives and hooked it up to the drive in question and it worked. I took the power supply from the drive in question and hooked it up to a drive I knew to be good and the drive wouldn't power on, repeating the behavior of the previous drive.
So my question... is there anywhere I can get a replacement power supply for my Lacie drive? If anyone is wondering, yes, the drive failed once before - it's four years old - but Data Rescue II and Disk Utility resurrected everything that was on it.
Hi willscarlett-
If the drive is still under warranty LaCie will replace the power supply at no charge.
You can also order the power supply directly from LaCie for around $20. I use several LaCie drives, have been burned by a bad power supply or two, and now keep an extra one around just in case.
Luck-
-DaddyPaycheck
Similar Messages
-
LaCie DVD-burner and iBook power supply problem
Hello guys!
I bought recently external LaCie DVD burner (USB). I experienced problem connecting it to iBook. It suppose to be possible to be powered up from USB but only possible way to power up burner only via external power supply. Is there is any possibility to adjust power in iBook so burner will work. I'v checked possibility to use it only powered form USB on MacBook of my friend - it works smooth only from single USB...
Thanks for any suggestions,
Ivanhttp://discussions.apple.com/message.jspa?messageID=3006257#3006257
Look here for answer -
sorry, don't know where else to post this.
i have an external LaCie D2 optical drive and after about 5 years of (more or less) continuous operation, the power supply brick died. obviously no power to the drive and clicking noise from the brick.
i understand nothing lasts forever and already ordered a replacement.
i was just wondering if getting 5 years out of such brick is a decent lifespan.
thanksmine died a month ago after just 30 months.
Seems they may be getting less reliable then.
Thankfull for the 3 year warranty as it was covered and they set me a replacement.
Was so worried it was the drive itself. -
Dead Power Supply and LaCie Portable HD?
Here's my problem:
I coordinate a lab that has 8 400-MHz G4's. Four of the computers have just died over the past few months; no power at all when trying to start them.
I've already tried changing batteries and pressing the PRAM button, but that hasn't help. So it seems that there may be a problem with the power supply dying.
But here's the catch: It seems that the computers lose power when I connect a LaCie 80 GB portable Firewire hard drive to them. I was running one of the G4's today when said portable hard drive attached. I turned the computer off, then tried to start it up again. No power!
I know this has to be more than a coincidence, since it has happened once before. And now I'm thinking that is probably why the other computers died too.
Has anyone else had this problem occur? Or is this just my imagination?Is the LaCie drive able to work with any computer for a sufficient period of time?
It sounds like there may be an electrical problem with the external drive that is causing some damage when plugging it into a computer's firewire port. -
Does using two bus powered external devices MacBook Pro 13" put too much strain on the power supply?
Will daisy chaining two bus powered external devices put too much strain on my 2011 MacBook Pro 13" power supply? Specifically I would like use ProTools with a LaCie bus powered hard disc and a Digidesign Mbox 2 Pro which is also bus powered with firewire.
Hi rrlavigne,
The biggest difference between the two machines in maximum RAM capacity. The white MacBook is limited to 4GB, whereas the MacBook Pro will support 8GB of RAM. While the cost of RAM is prohibitory right now (to go to 8GB), to have that flexibility in the future will very much be worth it... especially considering you intend to install Logic.
Other than that, I think in terms of "raw performance" the machines are very equally matched. You're paying for the unibody design, backlight keyboard, SD card and new battery technology for that $200 premium (in addition to the slight CPU bump). -
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. -
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. -
Where can I get a new power supply for my HP Pavillian 761C ?
I can't believe how difficult it is to find HP parts. The HP website is worthless for finding ant parts! where do I go to find a new power supply for my HP Pavillian 761C ?
Hi,
Your PC has a 200 watt power suppy. Try this link. The posted price is $9.94.
HP DV9700, t9300, Nvidia 8600, 4GB, Crucial C300 128GB SSD
HP Photosmart Premium C309G, HP Photosmart 6520
HP Touchpad, HP Chromebook 11
Custom i7-4770k,Z-87, 8GB, Vertex 3 SSD, Samsung EVO SSD, Corsair HX650,GTX 760
Custom i7-4790k,Z-97, 16GB, Vertex 3 SSD, Plextor M.2 SSD, Samsung EVO SSD, Corsair HX650, GTX 660TI
Windows 7/8 UEFI/Legacy mode, MBR/GPT -
Registering a 65w power supply? Where? How?
Just had not one but TWO G4 17'" powerbook power supplies go dead on me within the span of two weeks. The first one shorted out totally and left charred plastic and burn marks right where the cord the plugs into the computer meets the power brick. However the second literally caught fire in front of my eyes!
I was working on my laptop when suddenly everything shut down. I was confused at first but then I noticed the burning electric smell. When I glanced down at the power supply I saw blue sparks and tiny flames coming from where the cord meets the brick (computer side). I immediately unplugged my laptop first and then killed the power surge strip. The cord was totally burnt to a crisp. Gnarly...and good thing I was home when it happened!!!
Anyway, took it down to the Apple store where I got surprised looks from the staff but long story short my applecare was expired and they didn't have any 65w power supplies to "swap out" with me since all the new books use the 85w standard. Needing my computer desperately, I swallowed my bitterness and plunked down the $90 to get a new power supply. (Personally I find that price outrageous...especially since I recently had a problem with a LaCie drive and they sent me a new power supply free of charge without any hassle whatsoever!)
So I am using the one cord to power the two machines currently and I tried to register the darn thing in case this one decides to ignite but on the registration page I can't find any product listing for the power supply...or other apple peripherals for that matter. Its funny too because the Apple store staff made a huge deal of telling me to register the plug and I can't find a way to do it. I own many Apple products and they are all registered but it seems I am lost when registering something simple like a plug.
Can anyone out there help me or provide a link?
*I tried the normal registration link and there is no category for this product.
thanks!yeah, I figured I would simply call AppleCare or take it back to the store and have them explain how to register online...since they said I could specifically register the power supply online.
also just to clarify things, the cords were not damaged but they were 3 years old. the litlle plastic flange nubs that are near where the cord from the laptop enters the brick were still intact. in fact, that is what MELTED and got all crispy and black. it seemed to me the problem was that the plug was somehow damaged INSIDE the plastic sleeve right where it entered the power brick.
I agree to never wrap the cord around the brick though. One thing that I must say to people who bought the G4 17" books when they first came out and are still using the same power supply, please take note of how hot the brick gets. Right before all this grief happened I started to notice that the brick was getting VERY warm (dare I say hot?) to the touch. I never once noticed any physical damage to the wires or connector...as far as I was concerned the power supplies were slightly less white but there were no visible signs that they were going to ignite.
At this point it is too dificult to determine the factors that may have caused both power supplies to catch fire, so I won't speculate. However, my new power supply is plugged into the same outlet as the other two and working fine. It is also much much much much much much cooler to the touch than my old power supplies.
My advice: if your G4 powerbook power supply is too hot for you to hold it in your hand it may be time to take advantage of AppleCare and trade it in for a new one OR go to your nearest Apple Store and plunk down $90. Your choice! -
I have the top of the line PowerMac G5 from 2005. I had recently been having shutdowns for no reason. Not knowing these systems I called Apple that led me to going to being sent to the Apple store. I undid all the connections to my mac, took out my main hard drive , put this 50 pd giant on a dolly and wheeled it through a mall to the Apple store. After waiting a long time the AG put it up on the desk and said it was either the power supply or the logic board and that they dont fix them . He handed me a list of "Apple Approved Repair Servicers" and said goodbye.
I went home and watched lots of video's on how to change your own 600w power supply. How to remove the processors to get to the supply. At 200 dollars I was going to do it myself, I'm that way. I stripped the machine down to the watercololed processor that was totally pristine. Not a singlle leak anywhere. Everything was immaculate. Then I came across and article on the PMU. Power Management Utility and how it can become corrupt. How it causes havoc coupled with the Energy Saver Utility that allows the power button to put the computer to sleep. Then it dawned on me, I had noticed that pressing the power button resulted in an instant shut down. There was no 5 second wait. That was what had happened, it must be.
Long story short I reset the PMU. Power Management Utility. It no longer did a instant shut off and I disabled the "allow power button to put the computer to sleep". No moore shut downs, this runs perfectly. You would think that would be the first thing a AG would do but apparently not. I think I will go back there and mention it. Would be good to try first before suggesting the rest.Great work on your part, & thanks for the post/tip!
-
Imac G5, Can I use a power supply from a G4 Q-silver (rewired connector)?
I've got a G5 Imac with a blown PS, and I'm thinking of modifying a G4 Quicksilver power supply for use as the power source for a 20" Imac G5. Yeah, I know it sounds a bit weird, but hey, I was given this Imac G5 (1st Gen. 1.8GHz) for free. It's missing the back cover, and the PS is shot. So if I blow it up it no major loss. It's a project!
I have determined that the original PS is shot and needs to be replaced. I don't really want to drop $140 for a replacement PS, as I would also have purchase the back cover for another $40 + shipping. Go figure, right? It appears that most of those power suppies tend to fail early, anyway.
During my checks of the Imac internals, I also noted that during the "power on" tests, using the old power supply, I would get the second indicator light on the motherboard to flash for just a moment. According to Apple, this indicates that the motherboard is probably good, and that the power supply is bad as it's only providing a momentary voltage spike during the start up faze, before the power drains from the PS. Then it quits. So I thought, is it possible to use the QS power supply, only modifying (rewire) the main 22 pin connector voltages so they match the Imac's pinout? Both connectors are 22 pin and most of the pinout voltages match up the same. There would appear to be only two major connectors that would need to be rewired. So can I use a modified QS power supply to power my Imac?
A couple of extra notes about this Imac:
1) There is no back or stand with this Imac, it just the main guts. So I would need to build a suitable enclosure to maintain proper air flow, and use the QS power supply outside the Imac. That wouldn't appear to be a big problem.
2) My biggest concern is this. The QS power supply uses 28v for the start circuits, versus 24v for the G5 Imac PS. Would this make a significant difference, and if so, why? I'm assuming it will, but it an area I'm unsure of with the Imac. Any thoughts or experiance in this area here would be greatly appreciated.
3) Hey, if worse comes to worse, I can always purchase the extra parts and rebuild the Imac for around $200-$300 US, and it would still be a deal (at least I think so). However, at present this is just a pet project, and if it goes south (doesn't work), it's not like I'm out some major $$$$.
Thanks in advance!I have no idea whether your ideas would work, but go to xlr8yourmac.com for some ideas. If you decide to purchase parts, try [http://www.synaptech.com/catalog> and also look at [http://www.jimwarholic.com/2008/07/how-to-repair-apple-imac-g5.php] for tips.
Let us know what you end up doing, -
What power supply????????---Help!!!!!!
Building new system,,,,,K8Nneo4 platinum SLi----with two 6800GT's and AMD64 4000+,,,,,WHAT POWER SUPPLY DO I NEED?????
Actually, you really do need to do your homework first. Go to takaman's Power Supply Calculator and figure out HOW MANY AMPS YOU NEED ON EACH RAIL. Watts mean nothing as many manufacturers make distorted claims anyways. And they also test their PSU's at 25c. At 50c many of those cheap 550w PSU's output will actually drop to something like 250w!! Check THIS out.
Here's the [H]ardOCP list of Un-reccomended and Unscrupulous Power Supply Companies:
Achieve
Aerocool
Allied
Aspire
Codegen
Coolmax
Demon
Deer
Devanni.
Dynapower
Eagle
E-power (except Tagan series)
InWin
JustPC
Kingwin
L&C
Linkworld
MGE,
PCMICS
Power-Man
Powmax
Power-Up
Raidmax
Thermaltakes (low end ones, butterflies are fine, and some enlight models, the TT category depends)
Turbo
Ultra-X (yes, the pretty looking ones, they are made by a low-quality Chinese company that starts with "Young". Can't get much more generic than that!!!)
X-superalien
X-treme
syar2003 gave you the best info you could have regarding a PSU for a SLI system. My personal recommendation? PC Power & Cooling Turbo Cool 510 SLI. The Enermax EG701AX-VE would be a good choice also, but for $25 more the PCP&C TC 510 SLI is definitely the top choice.
Look at it this way, you're going to have to spend $200 for a good SLI PSU anyways, why not get the best. I mean, it's just the most important component in your computer. If you're gonna spend $2000 - $3000 on your new Rig, do you really want to risk all that valuable hardware on some cheap PSU?
Anyone could buy that cheap PSU for their sweet new SLI Rig, but, they better have a fire extinguisher and $2000 handy when they've OC'd their new AMD64 4000+ and those two sweet 6800GT's and their cheap PSU bursts into flames.
We all like to get the best for as little as possible, but the PSU is NOT the component anyone should want to cut costs on.
Go over to The [H]ardOCP Power Supplies Forum and read the Stickies there.
Tons of extremely valuable info the on PSU's. Good Luck & Good Hunting. -
IMac broken, Power Supply replacement?
My 13 months iMac G5 20" 2GHz shut down all the time.. mostly within 10 minutes after booting.
A friend of mine had the same problem 2 months ago. Apple replaced his Power Supply for free since the guaranty is 12 months.
My machine is one month past guaranty, 13 months old and therefor Apple wants $200 to fix my computer!!
As I can see my iMac ain't covered by the iMac Repair & Extentionprogram since mine is a 2GHz.. My seriealnumber starts with W8519XXXXXX..
Does W8435xxxxxx - W8522xxxxxx mean that all serialnumbers between these two are convered by this program?
http://www.apple.com/support/imac/repairextensionprogram/
How can Apple charge me $200 for a obious production fault?!
iMac G5, 2GHz, 20" Mac OS X (10.4.7)All serial numbers within the numbers listed should be covered, and your number seems to fall in that category. However, if yours is not a Rev A , Apple may feel that your problem is not the one they are dealing with. They do specifically state:
"Some second generation iMac G5 computers have serial numbers that fall within the upper band of the ranges listed below. Only first generation iMac G5 computers are affected by this program."
I would call them again and try, politely, to point out that not only did your warranty just expire, but that your serial number is among the affected ones and your problem is one of the ones the extension program addresses.
Good luck,
Miriam
Rev A 20" iMac G5, 15"iMac G4, 15"iMac G3 DVD Mac OS X (10.4.7) -
Power supply spark...fried mobo?
Hey my frieed with a K8N Neo is having a problem..everything was working fine in his pc for 11 months...one day his powersupply sparked and the computer would not boot. No lights, no fans, nothing.
So he set in a replacement for a power supply and recived a new one. After plugging in everything the computer would still do nothing, no lights fans etc. Do you think the motherboard is fried? I've checked all the jumpers and they are fine.
His specs are:
Athlon 64 3200
MSI K8N Platinum
X-Infinity case
512 Geil Ram
Thermaltake 420W purepower (W0009R)
120 GB Hard drive
ThanksGildan,
You asked the following:
btw, how do u do (4)? (which was how to read voltages on motherboard with voltage multimeter (VMM).
Fiirst thing to do is to read and understand following thoroughly:
VMM USAGE INFORMATION
Many troubleshooting procedures require that you measure voltage and resistance. You take these measurements by using a handheld Digital Multi-Meter (DMM). The meter can be an analog device (using an actual meter) or a digital-readout device. The DMM has a pair of wires called test leads or probes. The test leads make the connections so that you can take readings. Depending on the meter's setting, the probes measure electrical resistance, direct-current (DC) voltage, or alternating-current (AC) voltage.
Usually, each system-unit measurement setting has several ranges of operation. DC voltage, for example, usually can be read in several scales, to a maximum of 200 millivolts (mv), 2v, 20v, 200v, and 1,000v. Because computers use both +5 and +12v for various operations, you should use the 20v maximum scale for making your measurements. Making these measurements on the 200mv or 2v scale could "peg the meter" and possibly damage it because the voltage would be much higher than expected. Using the 200v or 1,000v scale works, but the readings at 5v and 12v are so small in proportion to the maximum that accuracy is low.
If you are taking a measurement and are unsure of the actual voltage, start at the highest scale and work your way down. Most of the better meters have autoranging capability: The meter automatically selects the best range for any measurement. This type of meter is much easier to operate. You just set the meter to the type of reading you want, such as DC volts, and attach the probes to the signal source. The meter selects the correct voltage range and displays the value. Because of their design, these types of meters always have a digital display rather than a meter needle.
CAUTION: Whenever using a multimeter to test any voltage that could potentially be 110v or above, always use one hand to do the testing, not two. Either clip one lead to one of the sources and probe with the other, or hold both leads in one hand.
If you are holding a lead in each hand and accidentally slip, you can very easily become a circuit, allowing power to conduct or flow through you. When the power is flowing from arm to arm, the path of the current is directly across the heart. Hearts have a tendency to quit working when subjected to high voltages. They're funny that way.
I prefer the small digital meters; you can buy them for only slightly more than the analog style, and they're extremely accurate, as well as much safer for digital circuits. Some of these meters are not much bigger than a cassette tape; they fit in a shirt pocket. Radio Shack sells a good unit (made for Radio Shack by Beckman) in the $25 price range; the meter is a half-inch thick, weighs 3 1/2 ounces, and is digital and autoranging as well. This type of meter works well for most, if not all, PC troubleshooting and test uses.
CAUTION: You should be aware that many analog meters can be dangerous to digital circuits. These meters use a 9v battery to power the meter for resistance measurements. If you use this type of meter to measure resistance on some digital circuits, you can damage the electronics, because you essentially are injecting 9v into the circuit. The digital meters universally run on 3 to 5v or less.
Now that you have a nice shiny DIGITAL VMM make sure that you read its manual to understand out it works. Practice taking reading on household batteires and the likes first. Once you are confident and have confirmed that you have the proper lead in the neg/pos connector of your multimeter you are now ready to take some reading from your motherboard. Remember to always ground yourself first to dissipate static electricity, Put the black lead sensor against the case and then use the red lead sensor to carefully probe various points on your motherboard. Be very careful to only touch one point (soldering point, chipset leg, or a motherboard trace) at a time. You want to absolutely avoid short circuiting two such points. As long as you only touch one single point at a time you will be safe and get good reading were voltage is present. I usually use a gator clip connector to affix the black lead to the case, leaving me one hand for flashlight or magnifying glass and other to handle red VMM lead.
Here is how to get a Vddr reading on a MS-7025 Neo2 platinum: http://xtremesystems.org/forums/showthread.php?p=583463
(Put red lead sensor on green dot)
Here is how to get a Vcore reading on a MS-7025 Neo2 platinum: http://www.xtremesystems.org/forums/attachment.php?attachmentid=23902&stc=1
Your Board layout may be slightly different but just keep looking for something similar near your RAM and CPU. Remember to always use only the red lead sensor while being extremely careful to only touch only one spot at a time.
Have fun, -
What kind of Power Supply to buy for my Power Mac G5?
Hello!
After trying several things, and poking around several forums on the net I have become convinced that my Power Mac G5 needs a new Power Supply. My big question is how do I know what kind of Power Supply to get for it?
My computer is one of the last of the Power Mac G5's with Motorola chips; it has the dual 2.7 GHz processor core. I know the install will be tricky, but I feel confident I can do it.
The Apple store doesn't sell these Power Supplies any more, and our other local Apple repair store said they'd have to "match up the serial numbers" in order to find a new Power Supply... but they also wanted to charge me $200. (I'm a poor high school science teacher and would rather do it myself.)
Any words of wisdom/explanations on how to find the right type of Power Supply for my computer would be greatly appreciated!!!B_Free wrote:
Thank you both, Mac Man JW & Old Comm Guy!
My problem has been that the computer won't start at all. When I press the button on the front panel, I hear the click of a relay (like normal) but then nothing happens... no fans spinning up, no hard drive spinning up... silence.
When I open the side panel and press the button, I can see that the 2 cooling fans twitch just a little bit but they immediately stop. The only other thing I can see is that the red LED 7 light comes on, and according to everything I've read that light means 'contact an Apple representative.'
This started about 2 weeks ago. Hadn't had any trouble before then... if there were any warning signs I sure didn't see them.
If you think it might be something else I'm definitely willing to listen!
Did you check the liquid cooling system inside your G5 for leaks? That can make your G5 not start up as well. Look at this link: http://www.everymac.com/systems/apple/powermac_g5/faq/powermac-g5-liquid-cooling -info-leaks-issues.html
Maybe you are looking for
-
Not seeing content in mail folders
I use default mail with a hotmail account. I have folders but none of the messages appear when you click on a particular folder. When I use my PC you can see info in the folders.
-
Firefox 4 - Opening in a new window puts a second windows frame around the firefox browser window
Using Firefox 4 in Windows 7 I have customised the position of tabs (Tabs on top) and which toolbar items I would like to see. The first window I open of firefox 4 always has the configuration as I set it. Whenever I open a new window of firefox eith
-
Idocs knowledge for SAP MM consultant
Let me know what level of Idocs knowledge is required for a SAP MM consultant
-
I have an applet (javax.swing.JApplet) running with textarea. I am updating the text area for each successful process. When the application is running, if any other window is opened, then minimised, the applet window will have the print of the opened
-
Restriction to the number of forwards in one request?
is it true, that the number of forwards you can do in one request is restricted? someone told me, that ther is a restriction of 2 or 3 forwards since the servlet spec 2.2. he told me further, that only the servlet engines, which follow the spec stric