Can't start up after power failure.

Greetings.
Here in the Santa Cruz mountains we experience occasional power outages. After an outage, when I attempt to re-start the computer, it doesn't get past the spinning spokes (or whatever you call that thing). The thing just keeps spinning until I press the power button, shut the computer off, and re-start. After one or two tries, it starts up, but I'd like to know how to prevent the problem in the first place.
G4 Dual 450 Mac OS X (10.3.9) 1 GB RAM

The first thing you should do after an abnormal shutdown is boot from your OS X Installer Disc and use Disk Utility to repair both the hard drive and permissions.
There are two ways to prevent a problem like this:
1. Buy an external Firewire drive and backup software. Maintain a bootable backup of your system on the external drive. Update incrementally on a regular schedule - Daily for your work files; weekly for the entire system.
2. Buy an Uninterruptible Power Supply (UPS) with sufficient capacity to keep your system running long enough for you to shutdown normally until power is restored. Usually this means a UPS with enough capacity for about 10 minutes of operating time on battery. Of course you can buy as much capacity as you are willing to spend money for if you want longer operating times during blackouts.

Similar Messages

Imac wont start up after power failure

i moved the table my imac was on and i accidentally took off the power cable.the imac was on so when i took the cable off it shut off. then i put the cable back and tried to turn it on but nothing happened..it is like dead. any suggestions?

Also, there is a small battery or capacitor on the logic board that may need to be replaced, as this has been the cause of a similar issue over many generations of Mac computer hardware. Of course there are other causes of failure, and that is why the help of an expert to troubleshoot and diagnose issues to attempt to resolve them can take time.
And it may not be resolved after the first attempt if the actual problem is deeper than first best educated guess arrived by troubleshooting. Part of some repairs requires replacement of suspect parts, even if they may not be the cause, to eliminate their being within the realm of possibility. A good read is among the original Apple Technical Service Manuals, those aren't often available to the general public. I used one to self-troublehoot an iMac under AppleCare after the nearby 200+ miles one-way distant 'specialist' could not fix my new iMac, four times. So I am a bit cool on newer Macs; the way I see it one new headache lasting 10 months and requiring 3,000 miles travel, to not be resolved by experts (and under warranty, so I can't touch it!?!) is enough.
The best cure for main power failure, is to have a good high quality battery backup system in place with automatic voltage regulation, that also works as a power filter; and can step in to isolate the Mac from mains high-or-low power fluctuation. This can save many products from bad power sources; do not rely on these, either. Make copies of your work ahead of time. This saves your computer from issues you can prevent.
PS: my Macs seldom are shut off, for up to 11 months, some of mine only get to sleep when not in use. When the main power goes offline, during a storm or extended utility failure of their own making, I will have to shut them off as a choice. There is software in the UPS unit that can help shut down automatically, and that is a choice, too. I usually find their software problematic on occasion; and the battery backup is not very long in duration, so one with a few hours runtime and a method of rationing the power if you are present when the mains fail, is helpful in performing a normal shutdown after a power failure.
Good luck & happy computing!

Problems With Starting Up After Power Failure

Hi Everyone,
I'm having the strangest problem booting up (or rather, not being able to boot up) after a power outage in my neighborhood last night. What's more, it's the second night in a row that it's happened and has blocked my ability to boot into my two main drives. I installed OSX on a separate internal drive so that I can access them and they seem to be all right and have all the information on them which is good.
Here's what happened: Two nights ago my computer was on and we had a power outage which turned my computer off, of course. I don't have it set to restart after something like this so I tried to restart it in the morning. The blue progress bar makes it about a quarter of the way across and stops. I have the same OS on another drive so I started up with the Option key and chose that and everything was fine. However, the next night the exact same thing happened and I couldn't boot into that drive the following morning either so I had to install a fresh version of OSX on another drive just to get into my computer. I've used Drive Utility, Drive Warrior, Drive Genius and TechTool Deluxe to check the drives and they all say there's nothing wrong. I've tried to reset the PRAM but still can't boot up into those drives which were on when we had the outage. I have unplugged everything and nothing else in the house seems to be effected. Any suggestions? I've had many power outages over the years with my Mac on but never have I ever experienced something like this, and on both drives too! As always, any help will be greatly appreciated and needless to say, I'm turning my computer off tonight before I go to bed!

Sounds like a lesson in there: don't wait to put OS X on an external drive that is usually off line.
Rush to a store or on-line and get a UPS of the 1500VA sort (APC RS would be nice, or SMART UPS 1000VA).
The directory of the drives could be corrupt.
I have all my equipment, modem, routers, the works, but we had a bad storm and one port on the router/modem is out (the one I used, the modem seems to be okay) and I am worried that the UPS's line filter for DSL in is also 'compromised.'
Storms and power outages can wRECK or cuase havoc.
It sounds like you need to map out bad sectors maybe (zero all in Disk Utility) perhaps. The directory, volume blocks, or even journal file, got scrambled. However, because no test can find it means - to me - it could be the "non user partitions" rather than OS X partition etc. Hence, zero the drive or just reformat it in full.
Why have you not ever with these outages, just continued to live w/o one? I wouldn't just shutdown, I would unplug if a storm approaches.
PS: SMC Reset button is under drive bay #4. Give it a 5-10 seconds depress.

Controled Auto Start DomU after power failure

Hi, all,
I was hoping to get a few pointers on this. I have a 2 DomU "nodes" for a demo Oracle Apps Vision. My server (basic rack mount PC) is hooked up to a UPS battery backup. I managed to install NUT on the Dom0 (usb to the battery) and DomU (network to Dom0). When the battery goes critical, the DomUs shutdown, then the Dom0 shuts down. So far, so good.
Now, when the server restarts (wol from the router for now), I was hoping to restart my DomUs in a controlled manner (meaning start my db node first, then my Apps server node a bit later) without manually going to the web interface. I guess I can do this with Xen directly (xm create or links in /etc/xen/auto), but is this going to confuse the VM Manager and possibly leave the VM database out of sync? Is there a Python script I should use instead? Thanks for sharing your thoughts.

user12262982 wrote:
Now, when the server restarts (wol from the router for now), I was hoping to restart my DomUs in a controlled manner (meaning start my db node first, then my Apps server node a bit later) without manually going to the web interface. I guess I can do this with Xen directly (xm create or links in /etc/xen/auto), but is this going to confuse the VM Manager and possibly leave the VM database out of sync? Is there a Python script I should use instead? Thanks for sharing your thoughts.You can use both xm and the */etc/xen/auto* symlink method: VM Manager periodically polls the pool and will automatically detect that the guests have been started. You could also use the HA functionality within Oracle VM itself to automatically start the guests, but I'm not sure you could do that in a controlled fashion, i.e. the startup process would be non-deterministic.

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?

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.

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

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.

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.

Can't start Tomcat after installing Bea WorkShop for JSP

Hi,
I have been using Eclipse SDK Version: 3.1.2 Build id: M20060118-1600 and Web Tools Project 1.0.2 and Tomcat 5.0 and Tomcat 5.5 for about 2 months with no problems. But now I Can't start Tomcat after installing Bea WorkShop for JSP plug-in. I get "Server Tomcat v5.0 @ localhost failed to start". Any help would be greatly appreciated.

I installed BEA Workshop for JSP Version: 3.1.0
Build id: 536. I only wanted to install the plug-in to my existng Eclipse 3.1 / WTP application. The only option that I saw was to download the entire FullWorkshopFreeInstall-536.zip, which is 192,496 KB. During the installation, there is a screen that you can specify to only install the plug-in - and I selected that option. Today, I chose to uninstall the BEA Workshop for JSP and then I was again able to start Tomcat server. I then did a complete install of BEA Workshop for JSP into a totally separate location. My original Eclipse installation still works fine, but my Workshop for JSP Version (which is now a completely new installation) has the same problem with Tomcat that I reported with the plug-in. I am using j2sdk1.4.2_08 and have tried both Tomcat 5.0 and Tomcat 5.5. I have the same problem with both Windows XP Home Edition and Windows XP Professional.
Thanks for your assistance.
Ron

Can't Start Portal After Install

After downloading and installing the of evaluation Portal 4.0 SP1, I get the following message upon startup when I enter the system password that I entered during installation:
Starting WebLogic Server ....
The WebLogic Server did not start up properly.
Exception raised:
java.lang.IllegalAccessError: try to access method weblogic/management/internal/
Helper.preloadMBeanInfos()V from class weblogic/management/Admin
at weblogic.management.Admin.initialize(Admin.java:210)
at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:362)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:202)
at weblogic.Server.main(Server.java:35)
Reason: Fatal initialization exception
I even tried "weblogic" for the system password and I get the same message.
What password should I use to start the server?

I've followed the directions and am experiencing the exact same problem. Brand
new installation of Weblogic server 6.1 SP2 with examples. That install is working.
Then added Portal 4.0 SP1, updated the license file and I have the same issue
with the Illegal access exception resulting in the "Fatal initialization exception"....
Hmm!
[email protected] (Bowrat) wrote:
Below listed are the common errors you run into during installation
process:
- You need to have the correct version numbers of both the weblogic
server and the portal server. For instance the portal server 4.0 (eval
copy) will only run on WebLogic 6.1 SP1. So check the edocs for
supported platforms
- Make sure you have the installed the full version of the weblogic
server (including examples)
- Finally, you need to run the UpdateLicense.cmd file to update the
license.bea under ur Bea Root
Give it a shot after u have checked all of the above three - goodluck
- Bowrat
www.Bowstreet.com
Steve Anderson <[email protected]> wrote in message news:<[email protected]>...
From: Steve Anderson <[email protected]>
Newsgroups: weblogic.support.install
Subject: Can't Start Portal After Install
References:
NNTP-Posting-Host: 209.11.114.150
X-Original-NNTP-Posting-Host: 209.11.114.150
Message-ID: <[email protected]>
Date: 13 Feb 2002 20:25:53 -0800
X-Trace: 13 Feb 2002 20:25:53 -0800, 209.11.114.150
Organization: BEA SYSTEMS Inc
Lines: 18
XPident: firewall-user
Path: newsgroups.bea.com!209.11.114.150
Xref: newsgroups.bea.com weblogic.support.install:9600
After downloading and installing the of evaluation Portal 4.0 SP1,I get the following message upon startup when I enter the system password
that I entered during installation:
Starting WebLogic Server ....
The WebLogic Server did not start up properly.
Exception raised:
java.lang.IllegalAccessError: try to access method weblogic/management/internal/
Helper.preloadMBeanInfos()V from class weblogic/management/Admin
at weblogic.management.Admin.initialize(Admin.java:210)
at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:362)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:202)
at weblogic.Server.main(Server.java:35)
Reason: Fatal initialization exception
I even tried "weblogic" for the system password and I get the samemessage.
What password should I use to start the server?

Can nort start OC4J_BI_FORM after Portal password change(9.0.4)

We changed PORTAL password by going top sqlplus and OAS. Thinking it will make changes at both places. Now we see that when we start OAS. OC4J_BI_FORM does not start???

I provided an answer in the Portal Security forum:
Can not start OC4J_BI_FORM after PORTAL user password change

Option that SAP starts automaticly after power loss

I am using an windows/sql ECC 6.0 server. I would like option that SAP starts automaticly after power loss. Is it possible and how?

Hi
I think this not possible.
Thanks
Pankaj Kumar

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

Can't start up after power failure.

Similar Messages

Maybe you are looking for