Trouble booting up after power failure

After power failure(two hours), when booting up imac, just get a grey screen with blinking folder icon containing question mark.
I can hear clicking noise (hard drive?) that goes two or three clicks and then seems to give up.
How do I get it rebooted. Have disconnected and tried again with no result.

Sounds like the power failure may have fatally damaged the HD. Going forward use a UPS to protect your system, power surges can be very damaging to computers. You and try troubleshooting using Apple's Flashing question mark appears when you start your Mac but I think you may find the HD has failed. For confirmation you cal also run Apple Hardware Test in extended mode. Run AHT about 3x back to back and if it reports errors it's time to take the machine in for service.

Similar Messages

Imac will not boot up after power failure

Does anyone know why i have to unplug the power cable from the back of my imac after every power failure at my home to get the imac to boot up. I've tried resetting the surge protecter and unplugging there. However, the only option is to unplug the cord from the back of the monitor/imac before it will boot up. Any ideas or is this a known bug.

You're effectively resetting the SMC.
If you're getting that many power outages you need to be using a UPS (Uninteruptible Power supply), not just a surge protecter.
Power interruptions at the wrong time can cause directory damage or even physical damage to the Hard Drive if the heads were reading or wriing at the time.

IMac not booting up after power failure

work around for at home/personal users which should work, the OS try's to retrieve user authentication Info from the previous logged on user so disconnecting the network cable or disabling or turning off the WiFi/ wireless should do the trick, just make sure the power is fully drained or have the power cable or battery disconnected for 25-30seconds to ensure the power is drained from the system. For all those Domain Admins/Users enable do not write on the users directory so the OS doesn't recognize a user account to try and retrieve info, if you perform this the OS will just create a temp user profile folder and delete it when theirs a power failure and not try to look for it after the power failure when booting up not causing to give you the gray boot up splash screen and go right into OS X, hope this helps and good luck!

work around for at home/personal users which should work, the OS try's to retrieve user authentication Info from the previous logged on user so disconnecting the network cable or disabling or turning off the WiFi/ wireless should do the trick, just make sure the power is fully drained or have the power cable or battery disconnected for 25-30seconds to ensure the power is drained from the system. For all those Domain Admins/Users enable do not write on the users directory so the OS doesn't recognize a user account to try and retrieve info, if you perform this the OS will just create a temp user profile folder and delete it when theirs a power failure and not try to look for it after the power failure when booting up not causing to give you the gray boot up splash screen and go right into OS X, hope this helps and good luck!

Trouble booting up after HD failure - 1405-S171

I have a Satellite laptop, model 1405-S171. I think my hard drive just failed, but I don't seem to be able to boot up from the recovery CDs that came with my computer. Where can I find information on how to do that? I'm running Windows XP Home.
Here's the long version: I left my laptop on for a few hours, and when I came back to it I had a black DOS screen with the message "HDD password". I never had put in a hard drive password, so I had no idea what to put in. I tried rebooting, but it always came back to the "HDD password" message (after showing the "Toshiba" screen, but no "Windows" screens come up). I tried just hitting "enter", tried entering a password I'd written down on the cover of my "Resource Guide" when I got my computer, and a few others, but nothing worked.
I have the Toshiba system recovery discs I got with my computer, and put Disk 1 in the CD drive and rebooted. Same thing. I read in a forum to try holding down the "c" key when rebooting. The computer just beeped, and when the "HDD password" screen came up, the password field was full, like it had just entered a bunch of "c"s in the password line.
I read on a forum that some Toshiba laptops will give the "HDD password" message when the hard drive fails, and there are some rather involved ways to fix this, involving updating the BIOS software. I don't know if this is applicable to my computer, and even if it is, I can't apply it unless I can get it to boot up off of something else besides the hard drive.
I have an external hard drive, and I did a backup using Acronis True Image just a week ago, so I think I'm okay if I can get the computer to boot up.
I am not a super computer whiz, though, so if the solution is too involved, I will just probably have to take it to someone. I'd like to know if the information on how to deal with this is out there, so I can deal with it myself if its not too hard, or at least give a professional something to start with. I am resigned that if I want to use this computer again, I'll probably need to get a new hard drive, though.
Thanks
cdhans123

    Jim, administrator.    I hope that you get this.   You wrote :
All Toshiba laptops ship with the ability to run the system recovery process from a hard disk partition.
    Maybe they ship with this partition but after getting a 300 D with Vista and a free CD to upgrade to W 7, I did and I do not have that recovery partition. Not that I need it now that the upgrade CD is well kept and I can find it in a jiffy or two. On top of this, I image my Toshiba at least once/month.
          My question is : why would the free CD not make this recovery partition for the less knowledgeable users. Did I miss a step when using this free CD ? With an image, it is just as good if not better than the recovery partition, I do not go back to "out of the box" condition. I could have kept that partition but it would have been going backward and not in baby steps.
     Have a great day and thanks for your dedication here.           JP.

How to configure V240 auto-boot after power failure?

Hi!
How to configure automatic boot of V240 machine after power failure? After power gets resored, V240 remains in standby mode and one has to press button on front to power it up. It is not convinient because power failure can occur, for example, at night and the machine is not booted until the first user awakens :)

Uhh... I've found publicly accessible document http://docs.sun.com/source/817-5481-11/variables.html :
Looks like this variable controls auto-power-up behaviour:
sc_powerstatememory
The sc_powerstatememory variable enables you to specify the state of the host server as false (keep the host server off) or true (return the server to the state it was in when the power was removed). This is useful in the event of a power failure, or if you physically move the server to a different location.
For example, if the host server is running when power is lost and the sc_powerstatememory variable is set to false, the host server remains off when power is restored. If the sc_powerstatememory variable is set to true, the host server restarts when the power is restored.
The values for this variable are as follows.
true - "Remembers" the state of the host server when power was removed and returns the server to that state when power is reapplied.
false - Keeps the server off when power is applied.

Domain controller VMs using dynamic VHDx corrupt after power failure

Over the past couple of months I have experienced 4 dead 2008 R2 SP1 domain controllers after power failure on Hyper-V 2012 hosts. The domain controller VMs will start after power failure and have varying degrees of file system corruption. In each instance
the corruption has rendered the domain controller unusable. The problem has not occurred with every power failure, but in testing the failure rate has been over 10%.
The Hyper-v 2012 hosts are as follows:
Dell PowerEdge r720 with flash backed write cache on Raid controller
Dell PowerEdge T710 with battery backed write cache on Raid controller
Dell PowerEdge T310 with a single SATA hard drive and write cache disabled
Generic system with a single SATA hard drive and write cache disabled
The VM configuration experiencing corruption is as follows:
Each VM was created from a base 2008 R2 SP1 syspreped VHDx image template file (40 Gigs)
The image template was originally created as a VHD and was then converted to a VHDx
The VHDx file has 512k sectors instead of the native 512e of VHDx files (a result of VHD - VHDx conversion)
Each VM was assigned 1024 Meg RAM and 1 virtual processor
The domain controllers were created by promoting the base 2008 r2 install to a DC after base image deployment
Only one corrupt VM was not running the 2012 integration components. The rest were running current 2012 integration components
I have done extensive testing on this issue and the problem for me seems to revolve around the VHDx file format. I have managed numerous Hyper-v installations since the original 2008 server version was released and I have never seen corruption like this
until 2012 and VHDx.
For the past few days I have been testing fixed sized VHD VMs on a 2012 host and I have not been able to reproduce the data corruption issue. I seem to only be able to reproduce the problem when using dynamic VHDx files. I have not done any testing on 2012
hosts with fixed size VHDx files or dynamic VHD files.
It would be great to hear from anybody else experiencing similar issues so that we can compare notes and hopefully get to the bottom of this problem.

To be honest I was excited to see this fix released, but there are two problems.
1. The hotfix causes BSOD if you have VLANs with a teamed NIC configuration. I found this out the hard way on a production system. How in the world did this thing get through testing and into automatic updates?
2. The hotfix does not seem to resolve the issue in my test environment.
I opened up a case with support and they informed me that they would not provide support for this issue and that I had to open a case with premier support. Premier support informed me that I cannot open a case with them unless I sign a $50,000 per year service
contract. Is there anywhere to get support on this issue?

Reset TC with Original Settings after Power Failure

TC blinks yellow after power failure. How can I reset to original (before power failure) network settings?

Here you go: How to reset Time Capsule

Lenovo IdeaCentre Q180 behavior after power failure

Hi,
I need a computer which reboots itself after an power failure.
I didn't find anything about the behavior of the IdeaCentre Q180 in such case.
Does the IdeaCentre Q180 reboots itself after power failure or is it possible to enable this feature?
This behavior is very important for my new system.
Thank you for your answer.
Kind Regards,
Theodoor
Solved!
Go to Solution.

Hi theodoor, welcome to the forums,
I'm not personally aquainted with the Q180, but I had a look in the BIOS simulator and I'm pretty sure the function you're looking for is available in BIOS.
Please see attached picture, (too big to post), it will open in the same window so please click your browser back button to return to this site.
Andy ______________________________________
Please remember to come back and mark the post that you feel solved your question as the solution, it earns the member + points
Did you find a post helpfull? You can thank the member by clicking on the star to the left awarding them Kudos Please add your type, model number and OS to your signature, it helps to help you. Forum Search Option T430 2347-G7U W8 x64, Yoga 10 HD+, Tablet 1838-2BG, T61p 6460-67G W7 x64, T43p 2668-G2G XP, T23 2647-9LG XP, plus a few more. FYI Unsolicited Personal Messages will be ignored.
Deutsche Community Comunidad en Español English Community Русскоязычное Сообщество
PepperonI blog
Attachments:
q180power.png ‏155 KB

RE1000 power light blinking after power failure

I've tried the 8 sec reset and the 30-30-30 reset but can't get the light to stop blinking and so can't connect to the unit. It was working fine before the power went out. Any suggestions?

I had the same issue after a power outage today. I online live chat with an agent for about 15 minutes until he provided me three options all about that I would have to pay extra to get it replaced or fixed because mine was just out of warranty yesterday. I was lucky enough because mine RE1000 was not dead completely. I followed the instructions in this community and restored its service successfully.
Here is what I did.
1. Reset the extender by 30-30-30 method. The LED still blinked after reset.
2. Turned off wifi on my laptop and assign a static IP on my laptop: 192.168.1.x. Ping RE's default gateway 192.168.1.1 with an Ethernet connection. It returned good result.
3. Log on Web Admin Page and I was prompted to upload its firmware. Followed the screen instruction to upload the firmware that I already downloaded previously. Waited until everything was finished and it rebooted. Volla. It was back to life.
I guess it might have lost the firmware somehow after power failure. Is there a battery inside the extender to power the flash rom?
Here are few instructions I followed up:
http://kb.linksys.com/Linksys/ukp.aspx?vw=1&docid=ca96fc48798d43489b4d16f9d77c14f9_Guidelines_in_Man...
http://kb.linksys.com/Linksys/ukp.aspx?pid=80&vw=1&articleid=25153
http://kb.linksys.com/Linksys/ukp.aspx?vw=1&docid=7e4956723e074191bdf33777314ddfd8_3998.xml&pid=80&r...
Cisco/Linksys/Berkin, you **bleep**. It is not that easy to rob my money what I earn by hard work.
Thanks for all advice and good luck.

PowerMac won't boot after power failure during install

Hi, sorry if this has been asked. I searched, but I'm not quite sure how to phrase it.
I bought a used PowerMac from craigslist and went to install a newer version of OSX. I had a power failure in the middle of the install and now the computer won't boot up. How do I go back to a fresh re-install and get the computer to boot up?
Much appreciated!

Did you use a retail install DVD? If you used a gray disc from another model Mac, that could be a problem.
Because of the power failure, suggest you reset the PMU. How long was the power Off? You may need to replace the PRAM battery.
Resetting Cuda/PMU on Power Mac G5, Power Mac G4, Power Macintosh G3
http://docs.info.apple.com/article.html?artnum=86760
 Cheers, Tom

My Windows 2000 machine has trouble booting up after instaling PCI-6503 card

After I installed the card in my Dell Desktop has trouble booting up. I have to pull the power cable out and then reconnect for it to come up.

Hello;
The best way to go about that is to completely uninstall the NI-DAQ driver you have installed on that machine, turn the computer of and remove the board from it.
You then reintall NI-DAQ, and put the board back. If the same behavior shows, the best bet is to search for some other peace of Software/Hardware currently installed on the machine that might be conflictant with NI-DAQ.
Regards
Filipe A.
Applications Engineer
National Instruments

Database startup issue after power failure

Hello, I am hoping someone might have some ideas for me on this issue. We had a power failure over the weekend and I was not alerted in time to shut down my DB server gracefully. I am running a 10g (10.2.0.4.0) standard database on RHEL 5. When power was restored I booted the server and noticed the database did not start (I have a startup script in init.d), I tried running dbstart manually and that did not work either. Below is the entries in my startup.log file and sqlnet.log file, I cannot figure out what is causing the 12514 error, as everything was working fine before the power failure. Interestingly though I am able to start the DB by running dbca and making a minor config change that requires a restart, dbca is somehow able to start the DB. Any ideas would be greatly apprieciated. Thanks!
STARTUP.LOG
/u01/app/oracle/product/10.2.0/db_1/bin/dbstart: Starting up database "DBS"
Sat Dec 4 15:33:12 PST 2010
SQL*Plus: Release 10.2.0.4.0 - Production on Sat Dec 4 15:33:12 2010
Copyright (c) 1982, 2007, Oracle. All Rights Reserved.
SQL> ERROR:
ORA-12514: TNS:listener does not currently know of service requested in connect
descriptor
SQL> ORA-12514: TNS:listener does not currently know of service requested in connect descriptor
SQL>
/u01/app/oracle/product/10.2.0/db_1/bin/dbstart: Database instance "DBS" warm started.
SQLNET.LOG
Fatal NI connect error 12514, connecting to:
(DESCRIPTION=(ADDRESS=(PROTOCOL=TCP)(HOST=oraserver.domain.com)(PORT=1521))(CONNECT_DATA=(SERVER=DEDICATED)(SERVICE_NAME=DBS.domain.com)(CID=(PROGRAM=sqlplus)(HOST=oraserver)(USER=oracle))))
VERSION INFORMATION:
TNS for Linux: Version 10.2.0.4.0 - Production
TCP/IP NT Protocol Adapter for Linux: Version 10.2.0.4.0 - Production
Time: 01-OCT-2009 17:19:10
Tracing not turned on.
Tns error struct:
ns main err code: 12564
TNS-12564: TNS:connection refused
ns secondary err code: 0
nt main err code: 0
nt secondary err code: 0
nt OS err code: 0

Mohammed Taj wrote:
Why do you suggest starting the db before the listener?
I always start db first then after listener.
Well, there's a good strong justification ....
because if you start listener then that time there is no db services to register, and lsnrctl services will show (no services ....) msg. Ok, so I have this startup script. One line starts the listener, the very next line starts the database. So in the few seconds between the listener starting and the database starting and fully opening, I am exposed to the possibility that someone might try to connect and get "ORA-12514: TNS:listener does not currently know of service requested in connect descriptor". That's opposed to the error they would have gotten a couple of seconds earlier, that would have said .... "ORA-12541: TNS:no listener"
Or I use your startup script. One line starts the database, the next line starts the listener. A full minute later the instance gets itself registered with the listener. So in the time between starting the listener and the database making as second - this time successful - attempt to register with the listener, I am exposed to the risk of someone making a connection attempt and getting "ORA-12514: TNS:listener does not currently know of service requested in connect descriptor". And again, this is as opposed to if they had been just a few seconds earlier and gotten ""ORA-12541: TNS:no listener"
or else if you want to start listener first then edit the listener.ora file and add the sid (few lines) then user will not receive the above mention error.In which case I start the listener first, it now knows about the instance without the instance self registering ... but it still has to wait for the instance to come up before it can service a connection request. How is that any different from NOT listing the SID_LIST, starting the listener, then starting the database and allowing the database to self-register? You are not eliminating anything from the user's end .. simply changing the error message they would get.

IMovie video project I made has no audio working after power failure

I have spent about a week stitching together family movies by ripping them to Apple tv format, then use a software program called MPEG streamclip to create a DV version which take about 24 gb a piece, I put 12 hours worth into iMovie which has taken a ton of space etc. So I created a project and am now about 1h 35 min in and this is getting small 3-5 clips of my son who is 7 months and my wife and myself b/c were going to England on Friday so I was created a nice movie for my new in laws and family I am meeting for the first time. So I had a saved file and iMovie was open and I had a power failure. I opened iMovie freaking out and then saw all the footage and the project still there so I was extremely thankful b/c of the 7 dvds I created due to space limitation once I imported I deleted the original (i have the original dvd but it takes about 6 hours to take from DVD to Apple TV format, then about 2 hours to export to DV and then another 1 hour to import into iMovie so each dvd took a full day for me due to work etc)
Anyway whats now happened is there is no audio on either the project or the original footage that has been imported, again about 12 hours of footage and a project thats 1 hr 35 mins. Whats strange is all other projects and imported video the sound and video works perfect. THis is the only one and of course its the most important one. ANY SUGGESTIONS WILL BE APPRECIATED.
If needed I will start over and do as much as I can but of course I am praying there is a simple solution.
Thanks.
newest iMovie, newest OSX etc if that helps

Thought you could use this info about getting FireWire to work!
First, you should always Repair Permissions in Disk Utility before and after any update; I would do that now. If you installed your update with FireWire plugged in, your Mac may not recognize it anymore.
Try resetting your FireWire ports by disconnecting all FW devices, shut down your Mac and unplug it from AC power (wall socket) for 30 minutes. plug it back in and try FW.
If that did'nt work, first run the Disk Repair as shown in Apple doc.#106214 before the next step. Then, download the combo update from this site (yours may be corrupt), not Software Update, disconnect all firewire + USB devices except keyboard + mouse, Repair Permissions, re-install update, Repair Permissions again + try. Yours is the 10.4.10 Combo update ( PPC, not for Intel systems). Others reading, download the Combo that applies to your system.
If that still did'nt get it Zap the PRAM. While restarting Mac hold down the following key combo Command-Option-P-R. Keep holding those keys down till you hear the second start-up chime, then release.
For those of you with Macs that are not PowerBooks or iBooks, a bad internal battery can cause FireWire to not be recognized, so make sure it's good! Also, here is Apple doc.#88338 on getting FireWire to work.
Cheers!
DALE

Vista got corrupt after power failure. sfc reports error and Event log service is unable to start itself.

Hi,
After a sudden power failure, I guess vista file system is corrupt.   I am able to start vista in normal mode, but it seems there are errors like Event Log service unable to start itself, when I start IE, it closes automatically ,
Norton antivirus does not start itself. and so on.
After Bing search, I went to safe mode and executed sfc /scannow and it reported error as below.
"Windows resource protection found corrupt files but was unable to fix some of them"
Unfortunately I am unable to upload log file, so I am pasting CBS.log content here....   Please advice.
Some parts of logs are removed due to limit of 60000 characters.
Please advice.
Regards
2014-07-07 14:55:57, Info                  CBS    Loaded Servicing Stack v6.0.6002.18005 with Core: C:\Windows\winsxs\x86_microsoft-windows-servicingstack_31bf3856ad364e35_6.0.6002.18005_none_0b4ada54c46c45b0\cbscore.dll
2014-07-07 14:55:58, Info                  CSI
00000001@2014/7/7:09:25:58.062 WcpInitialize (wcp.dll version 0.0.0.5) called (stack @0x6e9c8a50 @0x7147854e @0x714563a1 @0x341392 @0x341ed4 @0x3417cb)
2014-07-07 14:55:58, Info                  CSI
00000002@2014/7/7:09:25:58.156 WcpInitialize (wcp.dll version 0.0.0.5) called (stack @0x6e9c8a50 @0x714ae7b6 @0x71490f93 @0x341392 @0x341ed4 @0x3417cb)
2014-07-07 14:55:58, Info                  CSI
00000003@2014/7/7:09:25:58.187 WcpInitialize (wcp.dll version 0.0.0.5) called (stack @0x6e9c8a50 @0x73981a0d @0x73981794 @0x34360b @0x342be3 @0x3417cb)
2014-07-07 14:55:58, Info                  CBS    NonStart: Checking to ensure startup processing was not required.
2014-07-07 14:55:58, Info                  CBS    NonStart: Windows is in Safe Mode.
2014-07-07 14:55:58, Info                  CSI    00000004 IAdvancedInstallerAwareStore_ResolvePendingTransactions (call 1) (flags = 00000004, progress = NULL,
phase = 0, pdwDisposition = @0x2dfe70
2014-07-07 14:55:58, Info                  CBS    NonStart: Success, startup processing not required as expected.
2014-07-07 14:55:58, Info                  CSI    00000005 CSI Store 4780952 (0x0048f398) initialized
2014-07-07 14:56:03, Info                  CSI    00000006 [SR] Verifying 100 (0x00000064) components
2014-07-07 14:56:03, Info                  CSI    00000007 [SR] Beginning Verify and Repair transaction
2014-07-07 14:56:10, Info                  CSI    00000008 Repair results created:
POQ 0 starts:
     0: Move File: Source = [l:192{96}]"\SystemRoot\WinSxS\Temp\PendingRenames\ca20037dc599cf01650000007806a403._0000000000000000.cdf-ms", Destination = [l:104{52}]"\SystemRoot\WinSxS\FileMaps\_0000000000000000.cdf-ms"
    1: Move File: Source = [l:218{109}]"\SystemRoot\WinSxS\Temp\PendingRenames\aa070f7dc599cf01660000007806a403.program_files_ffd0cbfc813cc4f1.cdf-ms", Destination = [l:130{65}]"\SystemRoot\WinSxS\FileMaps\program_files_ffd0cbfc813cc4f1.cdf-ms"
    2: Move File: Source = [l:244{122}]"\SystemRoot\WinSxS\Temp\PendingRenames\6aca137dc599cf01670000007806a403.program_files_common_files_d7a65bb2f0e854e7.cdf-ms", Destination = [l:156{78}]"\SystemRoot\WinSxS\FileMaps\program_files_common_files_d7a65bb2f0e854e7.cdf-ms"
    3: Move File: Source = [l:278{139}]"\SystemRoot\WinSxS\Temp\PendingRenames\2a8d187dc599cf01680000007806a403.program_files_common_files_microsoft_shared_818c5a0e45020fba.cdf-ms", Destination = [l:190{95}]"\SystemRoot\WinSxS\FileMaps\program_files_common_files_microsoft_shared_818c5a0e45020fba.cdf-ms"
    4: Move File: Source = [l:286{143}]"\SystemRoot\WinSxS\Temp\PendingRenames\4ab11f7dc599cf01690000007806a403.program_files_common_files_microsoft_shared_ink_3c86e3db0b3b254c.cdf-ms", Destination = [l:198{99}]"\SystemRoot\WinSxS\FileMaps\program_files_common_files_microsoft_shared_ink_3c86e3db0b3b254c.cdf-ms"
    5: Move File: Source = [l:292{146}]"\SystemRoot\WinSxS\Temp\PendingRenames\aa12227dc599cf016a0000007806a403.program_files_common_files_microsoft_shared_ink_en_7a951cedcb9a5105.cdf-ms", Destination = [l:204{102}]"\SystemRoot\WinSxS\FileMaps\program_files_common_files_microsoft_shared_ink_en_7a951cedcb9a5105.cdf-ms"
    6: Move File: Source = [l:162{81}]"\SystemRoot\WinSxS\Temp\PendingRenames\aa28487dc599cf016b0000007806a403.$$.cdf-ms", Destination = [l:74{37}]"\SystemRoot\WinSxS\FileMaps\$$.cdf-ms"
    7: Move File: Source = [l:208{104}]"\SystemRoot\WinSxS\Temp\PendingRenames\6aeb4c7dc599cf016c0000007806a403.$$_ehome_40103e2da1d
2014-07-07 14:56:10, Info                  CSI    121de.cdf-ms", Destination = [l:120{60}]"\SystemRoot\WinSxS\FileMaps\$$_ehome_40103e2da1d121de.cdf-ms"
POQ 0 ends.
2014-07-07 14:56:10, Info                  CSI    00000009 [SR] Verify complete
2014-07-07 14:56:11, Info                  CSI    0000000a [SR] Verifying 100 (0x00000064) components
2014-07-07 14:56:11, Info                  CSI    0000000b [SR] Beginning Verify and Repair transaction
2014-07-07 14:56:19, Info                  CSI    0000000c Repair results created:
POQ 1 starts:
POQ 42 ends.
2014-07-07 14:58:29, Info                  CSI    000000b1 [SR] Verify complete
2014-07-07 14:58:30, Info                  CSI    000000b2 [SR] Verifying 100 (0x00000064) components
2014-07-07 14:58:30, Info                  CSI    000000b3 [SR] Beginning Verify and Repair transaction
2014-07-07 14:58:38, Info                  CSI    000000b4 Repair results created:
POQ 43 starts:
     0: Move File: Source = [l:192{96}]"\SystemRoot\WinSxS\Temp\PendingRenames\4a5ad3d4c599cf01391100007806a403._0000000000000000.cdf-ms", Destination = [l:104{52}]"\SystemRoot\WinSxS\FileMaps\_0000000000000000.cdf-ms"
    1: Move File: Source = [l:162{81}]"\SystemRoot\WinSxS\Temp\PendingRenames\4a5ad3d4c599cf013a1100007806a403.$$.cdf-ms", Destination = [l:74{37}]"\SystemRoot\WinSxS\FileMaps\$$.cdf-ms"
    2: Move File: Source = [l:234{117}]"\SystemRoot\WinSxS\Temp\PendingRenames\cadfdcd4c599cf013b1100007806a403.$$_help_windows_en-us_b594929e73669c5e.cdf-ms", Destination = [l:146{73}]"\SystemRoot\WinSxS\FileMaps\$$_help_windows_en-us_b594929e73669c5e.cdf-ms"
    3: Move File: Source = [l:228{114}]"\SystemRoot\WinSxS\Temp\PendingRenames\2a41dfd4c599cf013c1100007806a403.$$_help_help_en-us_91e6e7979a9bf9c6.cdf-ms", Destination = [l:140{70}]"\SystemRoot\WinSxS\FileMaps\$$_help_help_en-us_91e6e7979a9bf9c6.cdf-ms"
    4: Move File: Source = [l:214{107}]"\SystemRoot\WinSxS\Temp\PendingRenames\ea0ef7d4c599cf013d1100007806a403.$$_apppatch_1143992cbbbebcab.cdf-ms", Destination = [l:126{63}]"\SystemRoot\WinSxS\FileMaps\$$_apppatch_1143992cbbbebcab.cdf-ms"
    5: Move File: Source = [l:218{109}]"\SystemRoot\WinSxS\Temp\PendingRenames\ea241dd5c599cf013e1100007806a403.program_files_ffd0cbfc813cc4f1.cdf-ms", Destination = [l:130{65}]"\SystemRoot\WinSxS\FileMaps\program_files_ffd0cbfc813cc4f1.cdf-ms"
    6: Create Directory: Directory = [l:48{24}]"\??\C:\Program Files\MSN", Attributes = 00000080
POQ 43 ends.
2014-07-07 14:58:38, Info                  CSI    000000b5 [SR] Verify complete
2014-07-07 14:58:38, Info                  CSI    000000b6 [SR] Verifying 100 (0x00000064) components
2014-07-07 14:58:38, Info                  CSI    000000b7 [SR] Beginning Verify and Repair transaction
2014-07-07 14:58:43, Info                  CSI    000000b8 Repair results created:
POQ 44 starts:
     0: Move File: Source = [l:192{96}]"\SystemRoot\WinSxS\Temp\PendingRenames\eac6f0d7c599cf01a31100007806a403._0000000000000000.cdf-ms", Destination = [l:104{52}]"\SystemRoot\WinSxS\FileMaps\_0000000000000000.cdf-ms"
    1: Move File: Source = [l:162{81}]"\SystemRoot\WinSxS\Temp\PendingRenames\aa89f5d7c599cf01a41100007806a403.$$.cdf-ms", Destination = [l:74{37}]"\SystemRoot\WinSxS\FileMaps\$$.cdf-ms"
    2: Move File: Source = [l:216{108}]"\SystemRoot\WinSxS\Temp\PendingRenames\6a4cfad7c599cf01a51100007806a403.$$_resources_fbee56ab048ab239.cdf-ms", Destination = [l:128{64}]"\SystemRoot\WinSxS\FileMaps\$$_resources_fbee56ab048ab239.cdf-ms"
    3: Move File: Source = [l:230{115}]"\SystemRoot\WinSxS\Temp\PendingRenames\caadfcd7c599cf01a61100007806a403.$$_resources_themes_4d0d4910e83c2273.cdf-ms", Destination = [l:142{71}]"\SystemRoot\WinSxS\FileMaps\$$_resources_themes_4d0d4910e83c2273.cdf-ms"
    4: Move File: Source = [l:240{120}]"\SystemRoot\WinSxS\Temp\PendingRenames\caadfcd7c599cf01a71100007806a403.$$_resources_themes_aero_3fd78bf4cb5fa2c4.cdf-ms", Destination = [l:152{76}]"\SystemRoot\WinSxS\FileMaps\$$_resources_themes_aero_3fd78bf4cb5fa2c4.cdf-ms"
    5: Move File: Source = [l:252{126}]"\SystemRoot\WinSxS\Temp\PendingRenames\8a7001d8c599cf01a81100007806a403.$$_resources_themes_aero_shell_a91dfa5124b343c4.cdf-ms", Destination = [l:164{82}]"\SystemRoot\WinSxS\FileMaps\$$_resources_themes_aero_shell_a91dfa5124b343c4.cdf-ms"
    6: Move File: Source = [l:276{138}]"\SystemRoot\WinSxS\Temp\PendingRenames\aa9408d8c599cf01a91100007806a403.$$_resources_themes_aero_shell_normalcolor_10be8ec981b35fb6.cdf-ms", Destination = [l:188{94}]"\SystemRoot\WinSxS\FileMaps\$$_resources_themes_aero_shell_normalcolor_10be8ec981b35fb6.cdf-ms"
    7: Move File: Source = [l:214{107}]"\SystemRoot\WinSxS\Temp\PendingRenames\cab80fd8c599cf01aa1100007806a403.$$_schcache_f995a5d4decb8cc0.cdf-ms", Destination = [l:126{63}]"\SystemRoot\WinSxS\FileMaps\$$_schcache_f995a5d4decb8cc0.cdf
2014-07-07 14:58:43, Info                  CSI    -ms"
    8: Move File: Source = [l:212{106}]"\SystemRoot\WinSxS\Temp\PendingRenames\cad948d8c599cf01ab1100007806a403.$$_msagent_be90584645cb9b95.cdf-ms", Destination = [l:124{62}]"\SystemRoot\WinSxS\FileMaps\$$_msagent_be90584645cb9b95.cdf-ms"
    9: Move File: Source = [l:214{107}]"\SystemRoot\WinSxS\Temp\PendingRenames\4a7578d8c599cf01ac1100007806a403.$$_system32_21f9a9c4a2f8b514.cdf-ms", Destination = [l:126{63}]"\SystemRoot\WinSxS\FileMaps\$$_system32_21f9a9c4a2f8b514.cdf-ms"
    10: Move File: Source = [l:242{121}]"\SystemRoot\WinSxS\Temp\PendingRenames\cafa81d8c599cf01ad1100007806a403.$$_system32_manifeststore_7d35b12f9be4c20e.cdf-ms", Destination = [l:154{77}]"\SystemRoot\WinSxS\FileMaps\$$_system32_manifeststore_7d35b12f9be4c20e.cdf-ms"
    11: Move File: Source = [l:224{112}]"\SystemRoot\WinSxS\Temp\PendingRenames\aae18dd8c599cf01ae1100007806a403.$$_msagent_chars_9a5bcb5da392f588.cdf-ms", Destination = [l:136{68}]"\SystemRoot\WinSxS\FileMaps\$$_msagent_chars_9a5bcb5da392f588.cdf-ms"
POQ 107 ends.
2014-07-07 15:08:01, Info                  CSI    00000213 [SR] Repair complete
2014-07-07 15:08:01, Info                  CSI    00000214 [SR] Committing transaction
2014-07-07 15:08:01, Info                  CSI    00000215 Creating NT transaction (seq 1), objectname [6]"(null)"
2014-07-07 15:08:01, Info                  CSI    00000216 Created NT transaction (seq 1) result 0x00000000, handle @0x4cc
2014-07-07 15:08:01, Info                  CSI
00000217@2014/7/7:09:38:01.060 CSI perf trace:
CSIPERF:TXCOMMIT;5
2014-07-07 15:08:01, Info                  CSI    00000218 [SR] Verify and Repair Transaction completed. All files and registry keys listed in this transaction
have been successfully repaired
2014-07-07 15:15:58, Info                  CBS    Scavenge: Package store indicates there is no component to scavenge, skipping.

Hi,
First, I would suggest you using last known good configuration:
Using Last Known Good Configuration
http://windows.microsoft.com/en-in/windows/using-last-known-good-configuration#1TC=windows-vista
if this cannot bring your Windows Vista back to good state, I suggest you perform in-place upgrade to fix the corrupted files:
How to Perform an In-Place Upgrade on Windows Vista, Windows 7, Windows Server 2008 & Windows Server 2008 R2
http://support.microsoft.com/kb/2255099/en-us
If you have any feedback on our support, please click
here
Alex Zhao
TechNet Community Support

HP PSC2500 All-In-One noise after Power Failure

Product: HP PSC2510 All In One
OS: Windows XP Home
No Error Messages
No Changes made to OS or Printer
The issue:
After a Power Failure, upon starting the printer up, the scanner bar attempts to locate the Home Position but once it gets to the area it is supposed to set at, it continues to move to the right and makes a repeating (gear) noise.
The only fixes I have come across are:
1) Opening the scanner bed (glass top) and cleaning the glass where the white strip runs along the glass.
This stops the noise and allows the scanner to reset corretly for 1 to 3 months.
2) Holding the Cancel button or OK + Cancel.
This allowed the printer to reset correctly 1 time.
Now, the Hard Reset and Semi Reset will not work.
Again, this issue ONLY happens after a power failure or if the plug is pulled...
The issue does not happen if the power is shut off correctly.
I am sure that Opening the top and cleaning the glass will work but this is a serious headache for a printer that cost over $225.
I am a Computer Repair Technician but Printer issues of this nature are not in my area of expertise
Is there anyone who can tell me the possible cause and/or Permanent fix for this issue?
I cannot find any other information about this issue online, and I cannot find a Service Manual.
Please help because this is my work printer.
Please email me at:
{Personal Information Removed}

UPDATE: As it stands, I opened the scanner bed and cleaned the glass Home Position strip (for the 6th time now) and low-and-behold, the printer functions properly again.
I know this issue will happen again in a few weeks to a month or so...
My question still stands...
Can ANYONE come up with a permanent solution to repair this issue?
Thanks again in advance.

Trouble booting up after power failure

Similar Messages

Maybe you are looking for