Failing recovery...so frustrating

I just got a HP Envy 17-j184nr. I also bought a Samsung 850 pro 256gb ssd to go along with it. Made the recovery discs. Put in the ssd and started the recovery process. It got all the way past the part with administrator and the second drive download, then it restarted. It loaded up and went into recovery imcomplete. Tried it twice with the same result. The retry option does nothing except sit there on "Insert recovery media" even though i've inserted every disc at least twice. The log shows...
[6:58:36.74] ChkErrBB.CMD : Detect some error during PININST_BBV.
[6:58:36.74] ChkErrBB.CMD : Check c:\system.sav\Logs\BurnBootWarn.log
[6:58:36.76] ChkErrBB.CMD : or, check c:\system.sav\Logs\BurnBootMerge.log
[6:58:36.77] --------------------------------------------------
[6:58:36.77] Critical error condition was detected at BBV1...
Please help me, I really want to start using my computer.
This question was solved.
View Solution.

The recovery media does not work well with disks that are of less capacity than the originally installed disk.
The workaround is to use a usb to sata cable and cloning software. This one came with a Corsair SSD purchased as a migration kit. You can purchase one from a vendor online or at a PC store.
I will post an image in a few minutes.
Samsung has data migration wizard software for owners of the SSD that can be downloaded from their support website.
The cloning software will resize the OS to fit on the SSD. You will need to reinstall the OEM hard disk into the notebook to perform the migration.Once the migration is complete you can reomove the original hard disk from the notebook, replace it with the SSD and then power it on. You should boot right to the Windows login screen in a matter of a few seconds.
****Please click on Accept As Solution if a suggestion solves your problem. It helps others facing the same problem to find a solution easily****
2015 Microsoft MVP - Windows Experience Consumer

Similar Messages

When trying to install Mountain Lion I get an error message, Failed, recovery can't be created

When trying to install Mountain Lion I get an error message, Failed, recovery can't be created

My Mountain Lion install failed for the following reason:
OS X can't be installed on the disk Macintosh HD, because a recovery system can't be created.
The message went on:
Visit www.apple.com/support/no-recovery to learn more.
The page is about a different failure, but I'm assuming the reason for my failure is this one:
The disk has a non-standard Boot Camp partition setup, in which further partitioning was performed after running Boot Camp Assistant, or the configuration that Boot Camp Assistant created was manually modified.
The cure involves erasing the entire HD and starting from scratch, which in my case would involve backing up both the Mac and Windows sides, setting up Boot Camp again, reinstalling Windows XP and recovering everything from backups on both sides. I would rather not have Mountain Lion than go through all that, and I think it's unfair for Apple to expect me to.
Because I don't recall doing anything off-piste when I set up Boot Camp in the first place (for a start, I'm not clever enough), I consider this episode an inadequacy in the Mountain Lion installer. As I won't be using the download, is it possible to get my money back?

Failed Recovery of Satellite C855

I have created Recovery DVDs for this product and they don't seem to work. It is for Windows 8 but booting from the DVD fails. It boots the DVD and then presents a Windows 8 type screen which says "Recovery - your PC needs to be repaired" with "a required device isn't connected or can't be accessed" and an error code of 0xc0000185 (these are all zeroes). The laptop is unbootable. Using a Windows 7 DVD I can get to the recovery concole - I haven't tried it but this and a Ubuntu Live DVD seem to point at a failure in the Recovery DVD.
I don't have a hard disk recovery partition but I have no reason to suspect theres anything wrong with the DVDs I created. Other computers can read them without any problems.
Is these any way I can boot this system? I am loathe to pay 30 quid for a couple of recovery DVDs from Toshiba when I don't think I've done anything wrong. Has anyone solved this?

Problem with recovery discs is quite simple: either it works or not. If recovery disc doesnt work you cannot do anything about it.
In your posting I didn't understand how far recovery installation goes but if you cannot start OS anymore or start HDD recovery installation there is a big problem. You can have factory settings again using recovery disc only. Other solution is own OS installation but I would not do this because in this case you must pay new product key.
Believe me the best solution for you is to order new recovery disc. It costs 30 Euro but you will have original recovery image and this version must not be activated.
>...when I don't think I've done anything wrong
Generally speaking you are right but if created recovery disc is not usable what else you can do.

PC Reset failed, recovery USB corrupted...

Tried to reset my WT8, but something went wrong and partitioning was interrupted with an error message.
I have USB recovery stick - but it seems to be corrupted and I'm stuck.
Any idea on how to get going again?
Cheers,
rikluost

If all else fails, Toshiba will supply recovery media. But the S&H cost is exorbitant.
For US machines, go to Get Recovery Media.
Elsewhere, go to the Backup Media Online Shop.
-Jerry

Toshiba S135-S2356 failed recovery Vista - need windows installation disk

Hi,
My Toshiba S135-S2356 recovery failed. Now it says ' insert your windows installation disk and restart your computer' . I have the Toshiba recovery and Application cd /drivers satelitte a130/a135 series windows vista home basic 32 bit CD but it won't start Window. It also said something about winload.exe . What should I do? Thanks

It sounds like your recovery discs may be bad. You might need to order new recovery media or have your laptop serviced.
- Peter

R/3 extraction failed - recovery procedure?

R/3 extraction is running from past 2 years.
Suddenly it failed since 5 days and again today it is running fine.
But how i do get data loaded to cube for failed loads?
what is the exact process that should be normally followed?

Hi,
In case you are doing full loads, there is no problem since the last request went fine.
In case of delta loads, there is the option to repeat the last delta. Every time a delta request fails, you can do a Repeat delta, which will load again the last delta.
If you have already load another delta request and didn't repeat the failed delta, you may have missing records in BW system. In this case, a full repair extraction is need.
Have a look a below SAP notes which describes in details the options you have:
739863 - Repairing data in BW
873694 - Consulting: Delta repeat and status in monitor/data target
Best regards,
Eduardo

Failed recovery partition

I think it is unfair that hp thinks that they should be charging for recovery disks when in fact it was there factory installed partition that has now crapped out leaving me with a useless recovery partition. But because they felt it was in there best interest not to send recovery disks with my laptop I now have a machine I can now use as a paperweight, when if they had just sent recovery disks I could be designing websites instead of writing this ridicules letter...

On HP machines you have 2 options-burn your Recovery DVD set using the software on the machine (before the hdd craps out) or order them from HP.Usually less than $20, not bad to salvage a paperweight.
******Clicking the Thumbs-Up button is a way to say -Thanks!.******
**Click Accept as Solution on a Reply that solves your issue to help others**

P67A-C45 (b3) bios fail - recovery

Hello guys i have problem.
I copy New bios in flash memory
After run bios file (.exe) and click agree and pc stuck.
I Will restart pc but not run bios. I must recovery bios. Help immediately pls thanks :(

Hi,
Try >>Clear CMOS Guide<<
If still doesn't work, then your BIOS is bricked and needs to be recovered with SPI programmer (Contact local IT services about this).

Account Blocked and failed Recovery Attemps.

Note: There is a warning on the right, stating i shouldnt state my account name for my own good but i think it is neccesary for the sake of resolving this issue. The account concerned is:[Redacted for privacy]
A few days ago, i used my laptop to log-in to my Skype account. I did nothing out of the ordinary during this procedure except clicking on my Skype client, only to see that a message popped up stating it was blocked. I clicked on the suggested link which led me through a procedure where i had to fill in a form.
I tried to fill in the forms as accurately as possible but in all honesty this account is very old and i do not know the specifics of it like the registration e-mail and when i made it. This most likely resulted in me filling in the forms in a wrong matter three times. Finaly after the third time i got a e-mail where it was stated the issue couldntn be forwarded and my account will not be recovered or unblocked for good. I was told to make a new account.
In the end, i am a legitimate user of Skype for years, i have done nothing wrong. However my account is still blocked, as it is now, forever.
Hopefully through this route, i can still recover my account as my e-mails i sent in response to the unblocking e-mails are not answered to no matter what.
If any member of the support team can contact me personally, i can provide you with a massive list of users i had on the other account, and a correct registration e-mail (I probably entered the wrong one in the forms), the last few users i added, the last user i had a conversation with and all the information you want.
If no-one responds to this, other users can see this as a warning. Beware if your account is blocked because Skype will perma-ban it if you mis-enter your information, regardless if it is indeed your account.
Moderator Notes:
First things, first: for your safety and protection, please never, ever include any personally identifiable information such as your real name, Skype account name, e-mail address, or a telephone number in a post on a public Community or forum such as this.
Please also remember the Community is not a branch of Skype Customer Service - so adding personally identifiable information in posts made to a public website is all the more unsafe. Thanks for understanding.

I think you may need to contact customer service regarding your concern. Just click the link below to see the instructions on how you can get in touch with the Support team ;
http://community.skype.com/t5/The-Skype-Lounge/How-to-Contact-Skype-Customer-Service/td-p/2056783
Yet, if you will not be able to verify the details that the support are requesting in order to prove that you are the owner of that account, I think the support team may not be able to assist you further.
IF YOU FOUND OUR POST USEFUL THEN PLEASE GIVE "KUDOS". IF IT HELPED TO FIX YOUR ISSUE PLEASE MARK IT AS A "SOLUTION" TO HELP OTHERS. THANKS!
ALTERNATIVE SKYPE DOWNLOAD LINKS | HOW TO RECORD SKYPE VIDEO CALLS | HOW TO HANDLE SUSPICIOS CALLS AND MESSAGES
SEE MORE TIPS, TRICKS, TUTORIALS AND UPDATES in
| skypefordummies.blogspot.com |

E9G80UA#ABA 17-j017cl Recovery attempt failed

I recently had the HDD fail on me. It was making clicking noises and would not boot up anymore, giving me the 3F0 error. I contacted HP since it's still under warranty and they verified it was a failed HDD. They sent me one to replace it with along with 3 recovery discs and 1 driver/program disc. I have tried 3 failed attempts to install the recovery discs and each has failed the same way. I get the failed recovery attempt message box along with 3 options, save log, view details and retry. I saved it and tried over and over with no luck. I read on here that someone said to change the BIOS date to 1/14/2014. I'm currently trying that as of right now, disc 1 is loading. If this doesn't work, what other options do I have?
I also have tried installing it like so:
install 3 recovery discs and when it asks for a supplemental disc to install it. I installed the supplemental disc at this time
Install 3 recovery discs and when it asks for the supp disc, I skipped it and let it reboot before attempting to install drivers.
Both ways I get the same error.

Try changing the date in the BIOS to 01/01/2014
****Please click on Accept As Solution if a suggestion solves your problem. It helps others facing the same problem to find a solution easily****
2015 Microsoft MVP - Windows Experience Consumer

DPM failing SQL backups due to error: "the SQL Server instance refused a connection to the protection agent. (ID 30172 Details: Internal error code: 0x80990F85)

I ran across this error starting on 6/4/2011 and have been unable to find the root of the problem. In our environment, we have a DPM 2010 server dedicated to backing up all our SQL envrionment (about 45 SQL Servers total). All of the SQL
environment is backing up fine except for a SQL Cluster Application. This particular SQL Instances is part of a 6 node failover cluster with 6 SQL Instances distributed amongst them. The other 5 SQL instances in the cluster are backing
up fine; only one instance is failing. The DPM Alerts section shows this error when attempting to do a SQL backup of one of the databases on this SQL instance:
Affected area: KEN-PROD-VDB001\POSREPL1\master
Occurred since: 6/11/2011 11:00:56 PM
Description: Recovery point creation jobs for SQL Server 2008 database KEN-PROD-VDB001\POSREPL1\master on SQL Server (POSREPL1) - Store Settings.ken-prod-cl004.aarons.aaronrents.com have been failing. The number of failed recovery point creation jobs =
4.
If the datasource protected is SharePoint, then click on the Error Details to view the list of databases for which recovery point creation failed. (ID 3114)
The DPM job failed for SQL Server 2008 database KEN-PROD-VDB001\POSREPL1\master on SQL Server (POSREPL1) - Store Settings.ken-prod-cl004.aarons.aaronrents.com because the SQL Server instance refused a connection to the protection agent. (ID 30172 Details:
Internal error code: 0x80990F85)
More information
Recommended action: This can happen if the SQL Server process is overloaded, or running short of memory. Please ensure that you are able to successfully run transactions against the SQL database in question and then retry the failed job.
Create a recovery point...
Resolution: To dismiss the alert, click below
Inactivate alert
I have checked the cluster node this particular SQL instance is running on using Perfmon and the machine is nowhere near capacity on CPU, memory, network, or Disk I/O.  I have failed this SQL Application to another node in the cluster and
receive the same error (this other node has another clustered SQL application on it that is actively running as well as backing up fine). The only thing that I am aware of that has changed is that we installed SP2 for SQL 2008 about 2 weeks prior
to when the failures started to occur. However, we updated all six clustered SQL Instances at the same time and only this one is having this issue so I don't believe that caused the problem. We are running SQL 2008 SP2 (version 10.0.4000.0)
on all clustered instances along with DPM 2010 (version 3.0.7696.0) on this particular DPM server that has the issue.
One last thing, I have also noticed errors in the event log pertaining to the same SQL backups that are failing (but the time stamps are not concurrent with each backup attempt):
Log Name:      Application
Source:        MSDPM
Date:          6/13/2011 1:09:12 AM
Event ID:      4223
Task Category: None
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      KEN-PROD-BS002.aarons.aaronrents.com
Description:
The description for Event ID 4223 from source MSDPM cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.
If the event originated on another computer, the display information had to be saved with the event.
The following information was included with the event:
DPM writer was unable to snapshot the replica of KEN-PROD-VDB001\POSREPL1\model. This may be due to:
1) No valid recovery points present on the replica.
2) Failure of the last express full backup job for the datasource.
3) Failure while deleting the invalid incremental recovery points on the replica.
Problem Details:
<DpmWriterEvent><__System><ID>30</ID><Seq>1833</Seq><TimeCreated>6/13/2011 5:09:12 AM</TimeCreated><Source>f:\dpmv3_rtm\private\product\tapebackup\dpswriter\vssfunctionality.cpp</Source><Line>815</Line><HasError>True</HasError></__System><DetailedCode>-2147212300</DetailedCode></DpmWriterEvent>
the message resource is present but the message is not found in the string/message table
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
    <Provider Name="MSDPM" />
    <EventID Qualifiers="0">4223</EventID>
    <Level>2</Level>
    <Task>0</Task>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2011-06-13T05:09:12.000000000Z" />
    <EventRecordID>68785</EventRecordID>
    <Channel>Application</Channel>
    <Computer>KEN-PROD-BS002.aarons.aaronrents.com</Computer>
    <Security />
</System>
<EventData>
    <Data>DPM writer was unable to snapshot the replica of KEN-PROD-VDB001\POSREPL1\model. This may be due to:
1) No valid recovery points present on the replica.
2) Failure of the last express full backup job for the datasource.
3) Failure while deleting the invalid incremental recovery points on the replica.
Problem Details:
<DpmWriterEvent><__System><ID>30</ID><Seq>1833</Seq><TimeCreated>6/13/2011 5:09:12 AM</TimeCreated><Source>f:\dpmv3_rtm\private\product\tapebackup\dpswriter\vssfunctionality.cpp</Source><Line>815</Line><HasError>True</HasError></__System><DetailedCode>-2147212300</DetailedCode></DpmWriterEvent>
</Data>
    <Binary>3C00440070006D005700720069007400650072004500760065006E0074003E003C005F005F00530079007300740065006D003E003C00490044003E00330030003C002F00490044003E003C005300650071003E0031003800330033003C002F005300650071003E003C00540069006D00650043007200650061007400650064003E0036002F00310033002F003200300031003100200035003A00300039003A0031003200200041004D003C002F00540069006D00650043007200650061007400650064003E003C0053006F0075007200630065003E0066003A005C00640070006D00760033005F00720074006D005C0070007200690076006100740065005C00700072006F0064007500630074005C0074006100700065006200610063006B00750070005C006400700073007700720069007400650072005C00760073007300660075006E006300740069006F006E0061006C006900740079002E006300700070003C002F0053006F0075007200630065003E003C004C0069006E0065003E003800310035003C002F004C0069006E0065003E003C004800610073004500720072006F0072003E0054007200750065003C002F004800610073004500720072006F0072003E003C002F005F005F00530079007300740065006D003E003C00440065007400610069006C006500640043006F00640065003E002D0032003100340037003200310032003300300030003C002F00440065007400610069006C006500640043006F00640065003E003C002F00440070006D005700720069007400650072004500760065006E0074003E00</Binary>
</EventData>
</Event>
Any help would be greatly appreciated!

Don't know if this helps or not, but I also noticed another peculiar issue that is derived from this problem. If I go to "Modify protection group", then expand the cluster, then expand all six nodes in the cluster, five of them show "All SQL Servers"
and allow me to expand the SQL Instance and show all databases; the one that is having a problem backing up, when I expand the node, doesn't even show that SQL exists on the node, when in fact, it does.
I would also like to add that the databases on this node that will not backup are running fine. They run hundreds of transactions daily so we know SQL itself is OK. Even though it is a busy SQL Server, there is plenty of available resources as
the SQL buffer and memory counters show the node is not under durress.

Recovery DVD Or Recovery USB

Help me for below product
Thanks
Vijay
Product name: HP PAVILION 14 NOTEBOOK PC TS 14-n019se
Product number: F0F92EA#ABV
Error while do recovery from DVD media or USB disk.
End with error

I don't know HP really gives support to customer.
I never support from HP Middle East. They never gave me Recovery DVD within three month warranty period of software. But other country giving free of recovery DVD. There is no standard in HP country to country. I have experienced of total 7 years with HP Middle East. I will give all 4 notebooks in my home
1st Notebook Pavilion dv6915ee windows Vista
2nd notebook Pavilion dv6-2152ee windows 7
3rd note book Pavilion F0F92EA#ABV Windows 8
4th note book Pavilion F0F92EA#ABV Windows 8
I always get support from HP UK HP India but never get support from HP Middle East for recovery DVD, That why i used to ordered Recovery DVD from HP UK. But unfortunate DVD for 3rd & 4th note book DVD never works. Even i wrote email to you direct on [email protected] this address.
This unit have some fault manufactured defect to work on external source i.e. Recovery DVD from HP or created Recovery DVD from note book or created recovery on USB thumb drive never worked. it end wih error, Only Recovery from note book recovery partition working. I can challenge HP software people in this matter.
Please see below error which is I copied when it failed recovery from HP Recovery DVD.
P2PP BurnBoot Check Failed
Possible Causes:
   1. Yellow-Bang occured at Device Manager
   2. Some silent-install failure of applications
   3. Found failed at PININST_BBV
   4. Found failed at PININST_BBV2
   5. Found Memory Dump file
Suggestion:
   1. Checking REGDEV_BB.LOG for drivers
   2. Checking BBApps.log for applications
   3. Checking MEMDUMP_BBV.log for memory dump file
Note[for ODM]:
   If you know which component failed in preinstall process
      after checking above files, please OTS it to the component owner.
   Otherwise, suggest to contact TWN PDC NB-PreinPM or create PIN-Log and OTS it with OTS Category Image
[RegistryDevicesCheck]
Result=PASSED
[PININST_BBV]
PININST (Mini-FBI) starts at: 22:23:36 Friday, December 05, 2014
[RunOnceThese_CMD#1]
LAUNCHED=> "C:\SYSTEM.SAV\UTIL\CLEANFBI.CMD"
START=> 22:23:38 Friday, December 05, 2014
END=> 22:23:44 Friday, December 05, 2014
RESULT=> Command finished in 6 seconds.
>==============================================================================
[RunOnceThese_CMD#2]
LAUNCHED=> "CMD.exe /c MOVE c:\System.sav\FactoryUpdate\boot.wim c:\System.sav\2ndCap"
START=> 22:23:44 Friday, December 05, 2014
END=> 22:23:45 Friday, December 05, 2014
RESULT=> Command finished in less than 1 seconds.
>==============================================================================
[RunOnceThese_CMD#3]
LAUNCHED=> "CMD.exe /c C:\System.sav\Util\Pre-BBV1.CMD"
START=> 22:23:45 Friday, December 05, 2014
Pre-Process=> This is 32bit OS. Skip disabling WOW64 File Redirection....
Post-Process=> This is 32bit OS. Skip enabling WOW64 File Redirection....
END=> 22:24:02 Friday, December 05, 2014
RESULT=> Command finished in 16 seconds.
>==============================================================================
[RunThese_CMD#1]
LAUNCHED=> "CMD.exe /c C:\System.sav\bbv\ClnWinSxS.cmd"
START=> 22:24:04 Friday, December 05, 2014
END=> 22:24:55 Friday, December 05, 2014
RESULT=> Command finished in 51 seconds.
>==============================================================================
[RunThese_CMD#2]
LAUNCHED=> "C:\System.sav\util\TDC\MCPP\Drivers\Chipset_BBV.CMD"
START=> 22:24:55 Friday, December 05, 2014
END=> 22:25:11 Friday, December 05, 2014
RESULT=> Command finished in 16 seconds.
>==============================================================================
[RunThese_CMD#3]
LAUNCHED=> "C:\System.sav\util\TDC\MCPP\Drivers\VID_TRPV_BBV.CMD"
START=> 22:25:11 Friday, December 05, 2014
END=> 22:25:17 Friday, December 05, 2014
RESULT=> Command finished in 6 seconds.
>==============================================================================
[RunThese_CMD#4]
LAUNCHED=> "C:\System.sav\util\TDC\MCPP\Drivers\VID_RLPV_BBV.CMD"
START=> 22:25:17 Friday, December 05, 2014
END=> 22:25:23 Friday, December 05, 2014
RESULT=> Command finished in 6 seconds.
>==============================================================================
[RunThese_CMD#5]
LAUNCHED=> "C:\System.sav\util\TDC\MCPP\Drivers\VID_KBPV_BBV.CMD"
START=> 22:25:23 Friday, December 05, 2014
END=> 22:25:29 Friday, December 05, 2014
RESULT=> Command finished in 6 seconds.
>==============================================================================
[RunThese_CMD#6]
LAUNCHED=> "C:\System.sav\util\TDC\MCPP\Drivers\MEI_CR_BBV.CMD"
START=> 22:25:29 Friday, December 05, 2014
END=> 22:25:30 Friday, December 05, 2014
RESULT=> Command finished in less than 1 seconds.
>==============================================================================
[RunThese_CMD#7]
LAUNCHED=> "C:\System.sav\util\TDC\MCPP\Drivers\MEI_BBV.CMD"
START=> 22:25:30 Friday, December 05, 2014
END=> 22:26:06 Friday, December 05, 2014
RESULT=> Command finished in 36 seconds.
>==============================================================================
[RunThese_CMD#8]
LAUNCHED=> "C:\System.sav\util\TDC\MCPP\Drivers\ISCT_BBV.CMD"
START=> 22:26:06 Friday, December 05, 2014
Pre-Process=> This is 32bit OS. Skip disabling WOW64 File Redirection....
Post-Process=> This is 32bit OS. Skip enabling WOW64 File Redirection....
END=> 22:26:07 Friday, December 05, 2014
RESULT=> Command finished in less than 1 seconds.
>==============================================================================
[RunThese_CMD#9]
LAUNCHED=> "C:\System.sav\util\TDC\MCPP\Drivers\IFFS_BBV.CMD"
START=> 22:26:07 Friday, December 05, 2014
END=> 22:26:13 Friday, December 05, 2014
RESULT=> Command finished in 6 seconds.
>==============================================================================
[RunThese_CMD#10]
LAUNCHED=> "C:\System.sav\util\TDC\MCPP\Drivers\CardReader_BBV.CMD"
START=> 22:26:13 Friday, December 05, 2014
END=> 22:26:44 Friday, December 05, 2014
RESULT=> Command finished in 31 seconds.
>==============================================================================
[RunThese_CMD#11]
LAUNCHED=> "C:\System.sav\util\TDC\MCPP\Drivers\Audio_BBV.CMD"
START=> 22:26:44 Friday, December 05, 2014
END=> 22:28:11 Friday, December 05, 2014
RESULT=> Command finished in 86 seconds.
>==============================================================================
[RunThese_CMD#12]
LAUNCHED=> "C:\System.sav\util\TDC\MCPP\Drivers\AlpsTP_BBV.CMD"
START=> 22:28:11 Friday, December 05, 2014
END=> 22:28:22 Friday, December 05, 2014
RESULT=> Command finished in 11 seconds.
>==============================================================================
[RunThese_CMD#13]
LAUNCHED=> "C:\System.sav\util\TDC\MCPP\Drivers\NIC_BBV.CMD"
START=> 22:28:22 Friday, December 05, 2014
END=> 22:29:03 Friday, December 05, 2014
RESULT=> Command finished in 41 seconds.
>==============================================================================
[RunThese_CMD#14]
LAUNCHED=> "C:\System.sav\util\TDC\MCPP\Drivers\VIDIntel_BBV.CMD"
START=> 22:29:03 Friday, December 05, 2014
END=> 22:30:04 Friday, December 05, 2014
RESULT=> Command finished in 61 seconds.
>==============================================================================
[RunThese_CMD#15]
LAUNCHED=> "C:\System.sav\util\TDC\MCPP\Drivers\VIDAMD_BBV.CMD"
START=> 22:30:04 Friday, December 05, 2014
END=> 22:31:33 Friday, December 05, 2014
RESULT=> Command finished in 76 seconds.
>==============================================================================
[RunThese_CMD#16]
LAUNCHED=> "C:\system.sav\Util\TDC\MCPP\TDCWIDI_BBV.CMD"
START=> 22:31:33 Friday, December 05, 2014
END=> 22:31:34 Friday, December 05, 2014
RESULT=> Command finished in less than 1 seconds.
>==============================================================================
[RunThese_CMD#17]
LAUNCHED=> "C:\System.sav\util\TDC\MCPP\Drivers\nVidia_BBV.CMD"
START=> 22:31:34 Friday, December 05, 2014
END=> 22:31:35 Friday, December 05, 2014
RESULT=> Command finished in less than 1 seconds.
>==============================================================================
[RunThese_CMD#18]
LAUNCHED=> "C:\System.sav\util\TDC\MCPP\Drivers\RST_BBV.CMD"
START=> 22:31:35 Friday, December 05, 2014
END=> 22:31:46 Friday, December 05, 2014
RESULT=> Command finished in 11 seconds.
>==============================================================================
[RunThese_CMD#19]
LAUNCHED=> "C:\System.sav\Util\TDC\MCPP\WLAN_IAC_BBV.CMD"
START=> 22:31:46 Friday, December 05, 2014
END=> 22:31:48 Friday, December 05, 2014
RESULT=> Command finished in less than 1 seconds.
>==============================================================================
[RunThese_CMD#20]
LAUNCHED=> "C:\System.sav\Util\TDC\MCPP\WLAN4EE_BBV.CMD"
START=> 22:31:48 Friday, December 05, 2014
END=> 22:31:49 Friday, December 05, 2014
RESULT=> Command finished in less than 1 seconds.
>==============================================================================
[RunThese_CMD#21]
LAUNCHED=> "C:\System.sav\Util\TDC\MCPP\RaWiFi_BBV.cmd"
START=> 22:31:49 Friday, December 05, 2014
END=> 22:31:50 Friday, December 05, 2014
RESULT=> Command finished in less than 1 seconds.
>==============================================================================
[RunThese_CMD#22]
LAUNCHED=> "cscript.exe c:\SwSetup\powerset\sys_mem_check.vbs"
START=> 22:31:50 Friday, December 05, 2014
END=> 22:31:51 Friday, December 05, 2014
RESULT=> Command finished in less than 1 seconds.
>==============================================================================
[RunThese_CMD#23]
LAUNCHED=> "C:\System.sav\Util\TDC\MCPP\HPePrint_BBV.CMD"
START=> 22:31:51 Friday, December 05, 2014
END=> 22:32:02 Friday, December 05, 2014
RESULT=> Command finished in 11 seconds.
>==============================================================================
[RunThese_CMD#24]
LAUNCHED=> "C:\System.sav\Util\TDC\MCPP\RaBtooth_BBV.CMD"
START=> 22:32:02 Friday, December 05, 2014
END=> 22:32:03 Friday, December 05, 2014
RESULT=> Command finished in less than 1 seconds.
>==============================================================================
[RunThese_CMD#25]
LAUNCHED=> "C:\System.sav\Util\TDC\MCPP\I_WPBT_BBV.CMD"
START=> 22:32:03 Friday, December 05, 2014
END=> 22:32:19 Friday, December 05, 2014
RESULT=> Command finished in 16 seconds.
>==============================================================================
[RunThese_CMD#26]
LAUNCHED=> "C:\System.sav\Util\TDC\MCPP\HPWBD_BBV.CMD"
START=> 22:32:19 Friday, December 05, 2014
END=> 22:32:30 Friday, December 05, 2014
RESULT=> Command finished in 11 seconds.
>==============================================================================
[RunThese_CMD#27]
LAUNCHED=> "C:\System.sav\Util\TDC\MCPP\HP3DG6NB_BBV.CMD"
START=> 22:32:30 Friday, December 05, 2014
END=> 22:32:51 Friday, December 05, 2014
RESULT=> Command finished in 21 seconds.
>==============================================================================
[RunThese_CMD#28]
LAUNCHED=> "C:\System.sav\Util\TDC\MCPP\EFIDIAG_BBV.CMD"
START=> 22:32:51 Friday, December 05, 2014
END=> 22:32:57 Friday, December 05, 2014
RESULT=> Command finished in 6 seconds.
>==============================================================================
[RunThese_CMD#29]
LAUNCHED=> "C:\System.sav\Util\TDC\MCPP\HPSEU_BBV.CMD"
START=> 22:32:57 Friday, December 05, 2014
END=> 22:32:58 Friday, December 05, 2014
RESULT=> Command finished in less than 1 seconds.
>==============================================================================
[RunThese_CMD#30]
LAUNCHED=> "CMD.exe /c C:\System.sav\bbv\QFEList32.cmd"
START=> 22:32:58 Friday, December 05, 2014
Pre-Process=> This is 32bit OS. Skip disabling WOW64 File Redirection....
Post-Process=> This is 32bit OS. Skip enabling WOW64 File Redirection....
END=> 22:33:04 Friday, December 05, 2014
RESULT=> Command finished in 6 seconds.
>==============================================================================
[RunThese_CMD#31]
LAUNCHED=> "C:\SWSetup\ESUW8\ESURun.bat"
START=> 22:33:04 Friday, December 05, 2014
END=> 22:33:16 Friday, December 05, 2014
RESULT=> Command finished in 11 seconds.
>==============================================================================
[RunThese_CMD#32]
LAUNCHED=> "C:\System.sav\Util\_RTEND.CMD"
START=> 22:33:16 Friday, December 05, 2014
END=> 22:33:17 Friday, December 05, 2014
RESULT=> Command finished in less than 1 seconds.
>==============================================================================
[RunThese_CMD#33]
LAUNCHED=> "C:\System.sav\Util\TDC\MCPP\QAWLAN_BBV.CMD"
START=> 22:33:17 Friday, December 05, 2014
END=> 22:33:18 Friday, December 05, 2014
RESULT=> Command finished in less than 1 seconds.
>==============================================================================
PININST (Mini-FBI) exits at: 22:33:20 Friday, December 05, 2014
[Mini-FBI]
Result=PASSED
[PININST_BBV2]
PININST (Mini-FBI) starts at: 22:34:40 Friday, December 05, 2014
[RunOnceThese_CMD#1]
LAUNCHED=> "CMD.exe /c C:\System.sav\Util\Pre-BBV2.CMD"
START=> 22:34:42 Friday, December 05, 2014
Pre-Process=> This is 32bit OS. Skip disabling WOW64 File Redirection....
Post-Process=> This is 32bit OS. Skip enabling WOW64 File Redirection....
END=> 22:34:48 Friday, December 05, 2014
RESULT=> Command finished in 6 seconds.
>==============================================================================
[RunThese_CMD#1]
LAUNCHED=> "CMD.exe /c C:\System.sav\bbv\PanelSize.cmd"
START=> 22:34:50 Friday, December 05, 2014
END=> 22:34:51 Friday, December 05, 2014
RESULT=> Command finished in less than 1 seconds.
>==============================================================================
[RunThese_CMD#2]
LAUNCHED=> "CMD.exe /c C:\System.sav\bbv\QryWinSxS.cmd"
START=> 22:34:51 Friday, December 05, 2014
END=> 22:34:52 Friday, December 05, 2014
RESULT=> Command finished in less than 1 seconds.
>==============================================================================
[RunThese_CMD#3]
LAUNCHED=> "cscript.exe c:\System.sav\Util\HP_OSEnh1\webcam.vbs"
START=> 22:34:52 Friday, December 05, 2014
END=> 22:34:53 Friday, December 05, 2014
RESULT=> Command finished in less than 1 seconds.
>==============================================================================
[RunThese_CMD#4]
LAUNCHED=> "C:\SWSetup\ESUW8\ESUDelete.bat"
START=> 22:34:53 Friday, December 05, 2014
END=> 22:34:54 Friday, December 05, 2014
RESULT=> Command finished in less than 1 seconds.
>==============================================================================
[RunThese_CMD#5]
LAUNCHED=> "C:\System.sav\Util\TDC\MCPP\HPSA_BBV.CMD"
START=> 22:34:54 Friday, December 05, 2014
END=> 22:34:55 Friday, December 05, 2014
RESULT=> Command finished in less than 1 seconds.
>==============================================================================
[RunThese_CMD#6]
LAUNCHED=> "c:\SwSetup\powerset\setactive.cmd"
START=> 22:34:55 Friday, December 05, 2014
END=> 22:34:56 Friday, December 05, 2014
RESULT=> Command finished in less than 1 seconds.
>==============================================================================
[RunThese_CMD#7]
LAUNCHED=> "c:\SwSetup\powerset\batterycap.cmd"
START=> 22:34:56 Friday, December 05, 2014
END=> 22:35:02 Friday, December 05, 2014
RESULT=> Command finished in 6 seconds.
>==============================================================================
[RunThese_CMD#8]
LAUNCHED=> "C:\System.sav\Util\TDC\MCPP\IntelECM_BBV.CMD"
START=> 22:35:02 Friday, December 05, 2014
END=> 22:36:24 Friday, December 05, 2014
RESULT=> Command finished in 81 seconds.
>==============================================================================
[RunThese_CMD#9]
LAUNCHED=> "C:\System.sav\Util\TDC\MCPP\HPCOSE_BBV.CMD"
START=> 22:36:24 Friday, December 05, 2014
END=> 22:36:25 Friday, December 05, 2014
RESULT=> Command finished in less than 1 seconds.
>==============================================================================
[RunThese_CMD#10]
LAUNCHED=> "C:\System.sav\Util\TDC\MCPP\IEHome_BBV.CMD"
START=> 22:36:25 Friday, December 05, 2014
END=> 22:36:31 Friday, December 05, 2014
RESULT=> Command finished in 6 seconds.
>==============================================================================
[RunThese_CMD#11]
LAUNCHED=> "C:\System.sav\Util\TDC\MCPP\HPUC_BBV.CMD"
START=> 22:36:31 Friday, December 05, 2014
END=> 22:36:37 Friday, December 05, 2014
RESULT=> Command finished in 6 seconds.
>==============================================================================
[RunThese_CMD#12]
LAUNCHED=> "C:\System.sav\Util\TDC\MCPP\HPREGW8M_BBV.CMD"
START=> 22:36:37 Friday, December 05, 2014
END=> 22:36:54 Friday, December 05, 2014
RESULT=> Command finished in 16 seconds.
>==============================================================================
[RunThese_CMD#13]
LAUNCHED=> "C:\System.sav\Util\TDC\MCPP\HPD1243_BBV.CMD"
START=> 22:36:54 Friday, December 05, 2014
END=> 22:37:05 Friday, December 05, 2014
RESULT=> Command finished in 11 seconds.
>==============================================================================
[RunThese_CMD#14]
LAUNCHED=> "C:\System.sav\Util\TDC\MCPP\EngyStar_BBV.CMD"
START=> 22:37:05 Friday, December 05, 2014
END=> 22:37:11 Friday, December 05, 2014
RESULT=> Command finished in 6 seconds.
>==============================================================================
[RunThese_CMD#15]
LAUNCHED=> "C:\System.sav\Util\TDC\MCPP\DragonA_BBV.CMD"
START=> 22:37:11 Friday, December 05, 2014
END=> 22:37:12 Friday, December 05, 2014
RESULT=> Command finished in less than 1 seconds.
>==============================================================================
[RunThese_CMD#16]
LAUNCHED=> "C:\System.sav\Util\TDC\MCPP\CyberMS_BBV.CMD"
START=> 22:37:12 Friday, December 05, 2014
END=> 22:37:58 Friday, December 05, 2014
RESULT=> Command finished in 46 seconds.
>==============================================================================
[RunThese_CMD#17]
LAUNCHED=> "C:\System.sav\Util\TDC\MCPP\CyberLP_BBV.CMD"
START=> 22:37:58 Friday, December 05, 2014
END=> 22:38:24 Friday, December 05, 2014
RESULT=> Command finished in 26 seconds.
>==============================================================================
[RunThese_CMD#18]
LAUNCHED=> "C:\System.sav\Util\TDC\MCPP\BoxWin8_BBV.CMD"
START=> 22:38:24 Friday, December 05, 2014
END=> 22:38:45 Friday, December 05, 2014
RESULT=> Command finished in 21 seconds.
>==============================================================================
[RunThese_CMD#19]
LAUNCHED=> "C:\System.sav\Util\TDC\MCPP\YouCamM_BBV.CMD"
START=> 22:38:45 Friday, December 05, 2014
END=> 22:39:11 Friday, December 05, 2014
RESULT=> Command finished in 26 seconds.
>==============================================================================
[RunThese_CMD#20]
LAUNCHED=> "C:\System.sav\Util\TDC\MCPP\YouCam_BBV.CMD"
START=> 22:39:11 Friday, December 05, 2014
END=> 22:40:18 Friday, December 05, 2014
RESULT=> Command finished in 66 seconds.
>==============================================================================
[RunThese_CMD#21]
LAUNCHED=> "C:\System.sav\Util\TDC\MCPP\WinLive_BBV.CMD"
START=> 22:40:18 Friday, December 05, 2014
END=> 22:40:19 Friday, December 05, 2014
RESULT=> Command finished in less than 1 seconds.
>==============================================================================
[RunThese_CMD#22]
LAUNCHED=> "C:\System.sav\Util\TDC\MCPP\Win8M_BBV.CMD"
START=> 22:40:19 Friday, December 05, 2014
END=> 22:40:35 Friday, December 05, 2014
RESULT=> Command finished in 16 seconds.
>==============================================================================
[RunThese_CMD#23]
LAUNCHED=> "C:\System.sav\Util\TDC\MCPP\U8BIOS_BBV.CMD"
START=> 22:40:35 Friday, December 05, 2014
END=> 22:40:51 Friday, December 05, 2014
RESULT=> Command finished in 16 seconds.
>==============================================================================
[RunThese_CMD#24]
LAUNCHED=> "C:\System.sav\Util\TDC\MCPP\SkypeM_BBV.CMD"
START=> 22:40:51 Friday, December 05, 2014
END=> 22:41:17 Friday, December 05, 2014
RESULT=> Command finished in 26 seconds.
>==============================================================================
[RunThese_CMD#25]
LAUNCHED=> "C:\System.sav\Util\TDC\MCPP\PWDVD12_BBV.CMD"
START=> 22:41:17 Friday, December 05, 2014
END=> 22:42:43 Friday, December 05, 2014
RESULT=> Command finished in 86 seconds.
>==============================================================================
[RunThese_CMD#26]
LAUNCHED=> "C:\System.sav\Util\TDC\MCPP\P2Go_BBV.CMD"
START=> 22:42:43 Friday, December 05, 2014
END=> 22:43:24 Friday, December 05, 2014
RESULT=> Command finished in 41 seconds.
>==============================================================================
[RunThese_CMD#27]
LAUNCHED=> "CMD.exe /c C:\SWSetup\OCAMark\OCAMark.cmd"
START=> 22:43:24 Friday, December 05, 2014
Pre-Process=> This is 32bit OS. Skip disabling WOW64 File Redirection....
Post-Process=> This is 32bit OS. Skip enabling WOW64 File Redirection....
END=> 22:43:30 Friday, December 05, 2014
RESULT=> Command finished in 6 seconds.
>==============================================================================
[RunThese_CMD#28]
LAUNCHED=> "C:\System.sav\Util\TDC\MCPP\NTStudio_bbv.CMD"
START=> 22:43:30 Friday, December 05, 2014
END=> 22:43:51 Friday, December 05, 2014
RESULT=> Command finished in 21 seconds.
>==============================================================================
[RunThese_CMD#29]
LAUNCHED=> "C:\System.sav\Util\TDC\MCPP\intelWD_BBV.CMD"
START=> 22:43:51 Friday, December 05, 2014
END=> 22:43:52 Friday, December 05, 2014
RESULT=> Command finished in less than 1 seconds.
>==============================================================================
[RunThese_CMD#30]
LAUNCHED=> "C:\System.sav\Util\TDC\MCPP\RM4Win.CMD"
START=> 22:43:52 Friday, December 05, 2014
END=> 22:43:53 Friday, December 05, 2014
RESULT=> Command finished in less than 1 seconds.
>==============================================================================
[RunThese_CMD#31]
LAUNCHED=> "cmd.exe /c c:\System.sav\bbv\defkey.cmd"
START=> 22:43:53 Friday, December 05, 2014
Pre-Process=> This is 32bit OS. Skip disabling WOW64 File Redirection....
Post-Process=> This is 32bit OS. Skip enabling WOW64 File Redirection....
END=> 22:43:59 Friday, December 05, 2014
RESULT=> Command finished in 6 seconds.
>==============================================================================
[RunThese_CMD#32]
LAUNCHED=> "C:\System.sav\Util\TDC\MCPP\HPQStar_BBV.CMD"
START=> 22:43:59 Friday, December 05, 2014
END=> 22:44:01 Friday, December 05, 2014
RESULT=> Command finished in less than 1 seconds.
>==============================================================================
[RunThese_CMD#33]
LAUNCHED=> "C:\System.sav\Util\TDC\MCPP\CPwrDD_BBV.cmd"
START=> 22:44:01 Friday, December 05, 2014
END=> 22:46:52 Friday, December 05, 2014
RESULT=> Command finished in 171 seconds.
>==============================================================================
[RunThese_CMD#34]
LAUNCHED=> "C:\System.sav\Util\TDC\MCPP\CPDD_BBV.cmd"
START=> 22:46:52 Friday, December 05, 2014
END=> 22:47:18 Friday, December 05, 2014
RESULT=> Command finished in 26 seconds.
>==============================================================================
[RunThese_CMD#35]
LAUNCHED=> "C:\SWSetup\Wallpaper\Scripts\WallpaperInstallBOM.cmd"
START=> 22:47:18 Friday, December 05, 2014
END=> 22:47:19 Friday, December 05, 2014
RESULT=> Command finished in less than 1 seconds.
>==============================================================================
[RunThese_CMD#36]
LAUNCHED=> "C:\SWSetup\Wallpaper\Disk1\Wallpaper.exe"
START=> 22:47:19 Friday, December 05, 2014
Pre-Process=> This is 32bit OS. Skip disabling WOW64 File Redirection....
Post-Process=> This is 32bit OS. Skip enabling WOW64 File Redirection....
END=> 22:47:20 Friday, December 05, 2014
RESULT=> Command finished in less than 1 seconds.
>==============================================================================
[RunThese_CMD#37]
LAUNCHED=> "C:\SWSetup\Wallpaper\Scripts\wallpapertheme.cmd"
START=> 22:47:20 Friday, December 05, 2014
END=> 22:47:21 Friday, December 05, 2014
RESULT=> Command finished in less than 1 seconds.
>==============================================================================
[RunThese_CMD#38]
LAUNCHED=> "C:\SWSetup\Wallpaper\Scripts\Wallpaper_Result.cmd"
START=> 22:47:21 Friday, December 05, 2014
END=> 22:47:23 Friday, December 05, 2014
RESULT=> Command finished in less than 1 seconds.
>==============================================================================
[RunThese_CMD#39]
LAUNCHED=> "C:\System.sav\Util\TDC\MCPP\ADP_BBV.CMD"
START=> 22:47:23 Friday, December 05, 2014
END=> 22:47:34 Friday, December 05, 2014
RESULT=> Command finished in 11 seconds.
>==============================================================================
[RunThese_CMD#40]
LAUNCHED=> "C:\System.sav\Util\TDC\MCPP\60NIS2013_BBV.CMD"
START=> 22:47:34 Friday, December 05, 2014
END=> 22:48:40 Friday, December 05, 2014
RESULT=> Command finished in 66 seconds.
>==============================================================================
[RunThese_CMD#41]
LAUNCHED=> "C:\System.sav\Util\TDC\MCPP\7ZIP_BBV.CMD"
START=> 22:48:40 Friday, December 05, 2014
END=> 22:48:46 Friday, December 05, 2014
RESULT=> Command finished in 6 seconds.
>==============================================================================
[RunThese_CMD#42]
LAUNCHED=> "C:\System.sav\Util\TDC\MCPP\SymHPE_BBV.CMD"
START=> 22:48:46 Friday, December 05, 2014
END=> 22:48:47 Friday, December 05, 2014
RESULT=> Command finished in less than 1 seconds.
>==============================================================================
[RunThese_CMD#43]
LAUNCHED=> "C:\System.sav\Util\TDC\MCPP\HOSTEND.cmd"
START=> 22:48:47 Friday, December 05, 2014
END=> 22:48:48 Friday, December 05, 2014
RESULT=> Command finished in less than 1 seconds.
>==============================================================================
[RunThese_CMD#44]
LAUNCHED=> "C:\System.sav\Util\_RTEND.CMD"
START=> 22:48:48 Friday, December 05, 2014
END=> 22:48:49 Friday, December 05, 2014
RESULT=> Command finished in less than 1 seconds.
>==============================================================================
[RunThese_CMD#45]
LAUNCHED=> "C:\System.sav\Util\TDC\MCPP\HPSIOB_BBV.CMD"
START=> 22:48:49 Friday, December 05, 2014
END=> 22:49:50 Friday, December 05, 2014
RESULT=> Command finished in 61 seconds.
>==============================================================================
[RunThese_CMD#46]
LAUNCHED=> "C:\System.sav\Util\TDC\MCPP\HPSIOBPC_BBV.CMD"
START=> 22:49:50 Friday, December 05, 2014
END=> 22:50:52 Friday, December 05, 2014
RESULT=> Command finished in 61 seconds.
>==============================================================================
[RunThese_CMD#47]
LAUNCHED=> "C:\System.sav\Util\TDC\MCPP\QAWLAN_BBV2.CMD"
START=> 22:50:52 Friday, December 05, 2014
END=> 22:50:53 Friday, December 05, 2014
RESULT=> Command finished in less than 1 seconds.
>==============================================================================
[RunThese_CMD#48]
LAUNCHED=> "C:\system.sav\Util\TDC\MCPP\1stHDD_BBV2.CMD"
START=> 22:50:53 Friday, December 05, 2014
END=> 22:50:54 Friday, December 05, 2014
RESULT=> Command finished in less than 1 seconds.
>==============================================================================
[RunThese_CMD#49]
LAUNCHED=> "C:\system.sav\Util\TDC\MCPP\2ndHDD_BBV2.CMD"
START=> 22:50:54 Friday, December 05, 2014
END=> 22:50:55 Friday, December 05, 2014
RESULT=> Command finished in less than 1 seconds.
>==============================================================================
[RunThese_CMD#50]
LAUNCHED=> "C:\system.sav\Util\TDC\MCPP\DisableDefender.cmd"
START=> 22:50:55 Friday, December 05, 2014
END=> 22:50:56 Friday, December 05, 2014
RESULT=> Command finished in less than 1 seconds.
>==============================================================================
[RunThese_CMD#51]
LAUNCHED=> "C:\system.sav\Util\TDC\MCPP\DTICON_BBV.CMD"
START=> 22:50:56 Friday, December 05, 2014
END=> 22:50:57 Friday, December 05, 2014
RESULT=> Command finished in less than 1 seconds.
>==============================================================================
[RunThese_CMD#52]
LAUNCHED=> "C:\system.sav\Util\TDC\MCPP\HOTSTART_BBV.CMD"
START=> 22:50:57 Friday, December 05, 2014
END=> 22:50:58 Friday, December 05, 2014
RESULT=> Command finished in less than 1 seconds.
>==============================================================================
[RunThese_CMD#53]
LAUNCHED=> "C:\System.sav\Util\TDC\MCPP\CUST_BBV2.CMD"
START=> 22:50:58 Friday, December 05, 2014
END=> 22:50:59 Friday, December 05, 2014
RESULT=> Command finished in less than 1 seconds.
>==============================================================================
PININST (Mini-FBI) exits at: 22:51:03 Friday, December 05, 2014
[Mini-FBI]
Result=PASSED
[C:\System.sav\Logs\BB\2ndHDD_BBV2.LOG]
Result=PASSED
[C:\System.sav\Logs\BB\60NIS2013.LOG]
Result=PASSED
[C:\System.sav\Logs\BB\7ZIP.LOG]
Result=PASSED
[C:\System.sav\Logs\BB\ADP.LOG]
Result=PASSED
[C:\System.sav\Logs\BB\AlpsTP.LOG]
Result=PASSED
[C:\System.sav\Logs\BB\Audio.LOG]
Result=PASSED
[C:\System.sav\Logs\BB\BoxWin8.LOG]
Result=PASSED
[C:\System.sav\Logs\BB\BTBHOST.LOG]
Result=PASSED
[C:\System.sav\Logs\BB\CardReader.LOG]
Result=PASSED
[C:\System.sav\Logs\BB\Chipset.LOG]
Result=PASSED
[C:\System.sav\Logs\BB\ChkLicen.log]
Result=PASSED
[C:\System.sav\Logs\BB\CPDD.LOG]
Result=PASSED
[C:\System.sav\Logs\BB\CPwrDD.LOG]
Result=PASSED
[C:\System.sav\Logs\BB\CustTweak.log]
Result=PASSED
[C:\System.sav\Logs\BB\CyberLP.LOG]
Result=PASSED
[C:\System.sav\Logs\BB\CyberMS.LOG]
Result=PASSED
[C:\System.sav\Logs\BB\DefaultHDD_BBV2.LOG]
Result=PASSED
[C:\System.sav\Logs\BB\DisableDefender.LOG]
Result=PASSED
[C:\System.sav\Logs\BB\DragonA.LOG]
Result=PASSED
[C:\System.sav\Logs\BB\DTICON_BBV.LOG]
Result=PASSED
[C:\System.sav\Logs\BB\EFIDIAG.LOG]
Result=PASSED
[C:\System.sav\Logs\BB\EngyStar.LOG]
Result=PASSED
[C:\System.sav\Logs\BB\FU_CTO.LOG]
Result=PASSED
[C:\System.sav\Logs\BB\HOTSTART_BBV.LOG]
Result=PASSED
[C:\System.sav\Logs\BB\HP3DG6NB.LOG]
Result=PASSED
[C:\System.sav\Logs\BB\HPCOSE.LOG]
Result=PASSED
[C:\System.sav\Logs\BB\HPD1243.LOG]
Result=PASSED
[C:\System.sav\Logs\BB\HPePrint.LOG]
Result=PASSED
[C:\System.sav\Logs\BB\HPQStar.LOG]
Result=PASSED
[C:\System.sav\Logs\BB\HPREGW8M.LOG]
Result=PASSED
[C:\System.sav\Logs\BB\HPSA.LOG]
Result=PASSED
[C:\System.sav\Logs\BB\HPSEU.LOG]
Result=PASSED
[C:\System.sav\Logs\BB\HPSIOB.LOG]
Result=PASSED
[C:\System.sav\Logs\BB\HPSIOBPC.LOG]
Result=PASSED
[C:\System.sav\Logs\BB\HPUC.LOG]
Result=PASSED
[C:\System.sav\Logs\BB\HPWBD.LOG]
Result=PASSED
[C:\System.sav\Logs\BB\IEHome.LOG]
Result=PASSED
[C:\System.sav\Logs\BB\IFFS.LOG]
Result=PASSED
[C:\System.sav\Logs\BB\IntelECM.LOG]
Result=PASSED
[C:\System.sav\Logs\BB\intelWD.LOG]
Result=PASSED
[C:\System.sav\Logs\BB\ISCT.LOG]
Result=PASSED
[C:\System.sav\Logs\BB\I_WPBT.LOG]
Result=PASSED
[C:\System.sav\Logs\BB\MEI.LOG]
Result=PASSED
[C:\System.sav\Logs\BB\MEI_CR.LOG]
Result=PASSED
[C:\System.sav\Logs\BB\NIC.LOG]
Result=PASSED
[C:\System.sav\Logs\BB\NTStudio.LOG]
Result=PASSED
[C:\System.sav\Logs\BB\nVidia.LOG]
Result=PASSED
[C:\System.sav\Logs\BB\OCAMark.log]
Result=PASSED
[C:\System.sav\Logs\BB\P2Go.LOG]
Result=PASSED
[C:\System.sav\Logs\BB\PureOSSR.log]
Result=PASSED
[C:\System.sav\Logs\BB\PWDVD12.LOG]
Result=PASSED
[C:\System.sav\Logs\BB\QAWLAN.LOG]
Result=PASSED
[C:\System.sav\Logs\BB\QAWLAN_2.LOG]
Log file...
[05/12/2014]
[22:50:52.20] Beginning of the QAWLAN_BBV2.cmd
[22:50:52.22] Dummy RStone Checking
[22:50:52.22] Rstone_BBVa.INI Check
WLAN=0
[22:50:52.23] RStone Detection
[22:50:52.23] No WLAN card detected.
[22:50:52.23] Result of the Qualcomm Atheros AR9000 Series Wireless LAN Driver for Microsoft Windows 8
ERRRORLEVEL=0
RESULT=FAILED
Standard Error information...
Standard Out information...
Result=FAILED
[C:\System.sav\Logs\BB\RaBtooth.LOG]
Result=PASSED
[C:\System.sav\Logs\BB\RaWiFi.log]
Result=PASSED
[C:\System.sav\Logs\BB\RM4Win.LOG]
Result=PASSED
[C:\System.sav\Logs\BB\RST.LOG]
Result=PASSED
[C:\System.sav\Logs\BB\SkypeM.LOG]
Result=PASSED
[C:\System.sav\Logs\BB\SymHPE.LOG]
Result=PASSED
[C:\System.sav\Logs\BB\TDCULTRABOOK.LOG]
Result=PASSED
[C:\System.sav\Logs\BB\TDCWIDI.LOG]
Result=PASSED
[C:\System.sav\Logs\BB\U8BIOS.LOG]
Result=PASSED
[C:\System.sav\Logs\BB\VIDAMD.LOG]
Result=PASSED
[C:\System.sav\Logs\BB\VIDIntel.LOG]
Result=PASSED
[C:\System.sav\Logs\BB\VID_KBPV.LOG]
Result=PASSED
[C:\System.sav\Logs\BB\VID_RLPV.LOG]
Result=PASSED
[C:\System.sav\Logs\BB\VID_TRPV.LOG]
Result=PASSED
[C:\System.sav\Logs\BB\WallpaperOk.log]
Result=PASSED
[C:\System.sav\Logs\BB\Win8M.LOG]
Result=PASSED
[C:\System.sav\Logs\BB\WinLive.log]
Result=PASSED
[C:\System.sav\Logs\BB\WLAN4EE.LOG]
Result=PASSED
[C:\System.sav\Logs\BB\WLAN_IAC.LOG]
Result=PASSED
[C:\System.sav\Logs\BB\Youcam.LOG]
Result=PASSED
[C:\System.sav\Logs\BB\YoucamM.log]
Result=PASSED
[LogFiles]
NumOfLogs=74.
[DumpFile]
Result=PASSED
[WinSAT]
Result=PASSED
[22:57:47.19] Sysprep_succeeded.tag does not exist ...
[22:57:47.19] ------------------------------------------------------------------------------------------
[22:57:47.21] BBVLast.cmd : [20x] CTOError.flg is detected at the end of BBV process...
[22:57:47.21] Suggest to create PIN-log and send to TWN PDC NB-PreinPM for further analysis ...
[22:57:47.21] ------------------------------------------------------------------------------------------

ORACLE8 OPS BACKUP & RECOVERY

제품 : ORACLE SERVER
작성날짜 : 2004-08-16
ORACLE8 OPS BACKUP & RECOVERY
=============================
SCOPE
Standard Edition 에서는 Real Application Clusters 기능이 10g(10.1.0) 이상 부터 지원이 됩니다.
Explanation
OPS에서의 database backup & recovery 방법은 single instance의 backup 방법과
비슷하다. 즉, Single instance에서의 모든 backup 방법은 ops에서도 지원된다.
1. Backup 방법
다음의 backup 방법 모두 사용이 가능하다. 여기서는 2)의 os 명령을 이용한
backup 방법에 대해 기술합니다.
1) Recovery Manager (RMAN) : <Bulletin 11451> 참고
2) OS 명령을 활용한 백업
Noarchive log mode : full offline backup only
Archive log mode : full or partial, offline or online backup
3) export : <Bulletin 10080> 참고 : ORACLE 7 BACKUP 및 RECOVERY 방법
2. backup 정책 수립 시 고려 사항
1) disk crash나 user error 등으로 말미암은 손실을 허용하지 않는다면 ARCHIVE
LOG MODE를 사용해야 한다.
2) 대부분 모든 instance는 자동 archiving을 사용한다.
3) 모든 data backup 작업이 어떤 instance 건 가능하다.
4) media recovery 시 모든 thread의 archive file이 사용된다.
5) Instance recovery 시 살아있는 instance의 smon에 의해 자동으로 recovery된다.
3. Noarchive log mode : Full offline backup
1) 다음의 view들을 query하여 backup이 필요한 file을 알아낸다.
V$DATAFILE or DBA_DATA_FILES
V$LOGFILE
V$CONTROLFILE
2) 모든 instance를 shutdown한다.
3) 확인된 file을 backup destination으로 copy한다.
4. Archive log mode : Partial or Full Online Backup
1) 백업을 수행하기 전에 ALTER SYSTEM ARCHIVE LOG CURRENT 명령 실행(이 명령을
실행하여 현재 운영되지 않는 데이터베이스를 포함한 모든 노드의 current redo
log에 대한 로그 스위치와 그에 따른 아카이브를 모든 인스턴스에서 실행시킨다.)
2) ALTER TABLESPACE tablespace BEGIN BACKUP 명령 실행
3) ALTER TABLESPACE 명령이 성공적을 실행될 때까지 대기
4) OS에서 적절한 명령어를 활용하여 테이블스페이스에 속하는 데이터파일들을 백업
(tar, cpio, cp 등)
5) OS 명령을 활용한 백업이 다 끝날 때까지 대기
6) ALTER TABLESPACE tablespace END BACKUP 명령 수행
7) ALTER DATABASE BACKUP CONTROLFILE TO filename 이나
ALTER DATABASE BACKUP CONTROLFILE TO TRACE
명령을 수행시켜 컨트롤 파일을 백업.
만약 아카이브 로그 파일을 백업받는다면 END BACKUP 명령을 실행시킨 이후
ALTER SYSTEM ARCHIVE LOG CURRENT 명령을 실행시켜 END BACKUP 시점까지의
모든 리두 로그 파일들을 확보한다.
5. Import Parameter
1) Controlfile 내의 Redo Log History (MAXLOGHISTORY )
CREATE DATABASE 명령이나 CREATE CONTROLFILE 명령에서 MAXLOGHISTORY 값을
지정하여 parallel server에서 다 채워진 리두 로그 파일에 대한 history를
컨트롤 파일이 저장하도록 할 수 있다. 이미 데이터베이스를 생성한 후라면
log history 값을 증가시키거나 감소시키기 위해서는 컨트롤 파일을 재생성
하여야만 한다.
MAXLOGHISTORY는 컨트롤 파일 내의 archive history를 얼마나 저장할 수
있는지를 지정하며, 기본값은 플랫폼 별로 다르다. 이 값이 0이 아닌 다른
값으로 지정된다면 log switch가 발생할 때마다 LGWR 프로세스에서는 컨트롤
파일에 다음 정보를 기록한다.
thread number, log sequence number, low SCN, low SCN timestamp, next SCN
(next log의 가장 낮은 SCN값)
(이 정보는 리두 로그 파일이 archive된 후가 아니라 log switch가 발생할 때
컨트롤 파일에 저장된다.)
MAXLOGHISTORY 값에서 지정한 값을 넘어서 log history가 저장되어야 할 경우
가장 오래된 history를 overwrite하는 방식으로 저장된다. Log history 정보는
OPS에서 자동 media recovery 시 SCN, thread number를 기준으로 적절한
아카이브 로그 파일을 찾아 재구성하는 데 사용된다. 데이터베이스를 exclusive
모드에서 한개의 쓰레드만 사용하는 환경에서는 log history 정보가 필요하지 않다.
Log history 관련 정보는 V$LOG_HISTORY를 이용해 조회해 볼 수 있다.
서버 관리자에서 V$RECOVERY_LOG를 조회하면 media recovery에 필요한 아카이브
로그에 대한 정보를 얻을 수 있다.
Multiplex된 리두 로그 파일에 대해서, log history 내에서 여러개의 entry가
사용되지 않는다. 각각의 entry는 개개의 파일에 대한 정보가 아니라, multiplex
된 log 파일의 그룹에 대한 정보를 가지고 있다.
2) Archive Log Mode 시 Parameter
OPS에서 archive log mode로 변경 시 exclusive mode로 db mount 후에 변경한다.
a. LOG_ARCHIVE_FORMAT
파라미터     설명     예
%T     thread number, left-zero-padded     arch0000000001
%t     thread number, not padded     arch1
%S     log sequence number, left-zero-padded     arch0000000251
%s     log sequence number, not padded     arch251
이 가운데 %T와 %t는 OPS에서만 유효한 파라미터이다.
모든 instance의 format은 같아야 하며 OPS 환경에서는 반드시 thread 번호를
포함시켜야 한다.
예) log_archive_format = %t_%s.arc
b. LOG_ARCHIVE_START
- 자동 archiving : TRUE로 지정한 후 인스턴스를 구동시키면 background process
인 ARCH에서 자동 archiving을 수행한다. Closed Thread의 경우에는 실행 중인
thread에서 closed thread를 대신해 log switch와 archiving을 수행한다.
이것은 모든 노드에서 비슷한 SCN을 유지하도록 하기 위해 강제적으로 log switch
가 발생할 때 일어난다
- 수동 Archiving : FALSE이면 archive를 시작하도록 지시하는 명령을 명시적으로
내리지 않는 이상 동작을 멈추고 대기한다. OPS에서는 각각의 인스턴스에서 서로
다른 LOG_ARCHIVE_START 값을 사용할 수 있다.
다음과 같은 방법으로 수동 archiving을 수행할 수 있다.
ALTER SYSTEM ARCHIVE LOG SQL 명령을 실행
ALTER SYSTEM ARCHIVE LOG START 명령을 실행하여 자동 archiving을 실행하도록
지정.
수동 archiving은 명령을 실행시킨 노드에서만 실행 되며, 이 때 archiving
작업을 ARCH 프로세스가 처리하지 않는다.
c. LOG_ARCHIVE_DEST
archive log file이 만들어질 directory를 지정한다.
예) log_archive_dest = /arch2/arc
6. OPS Recovery
1) Instance Failure 시
Instance failure는 S/W나 H/W 상의 문제, 정전이나 background process에서
fail이 발생하거나, shutdown abort를 시키거나 OS crash 등 여러가지 이유로
인해 instance가 더 이상 작업을 진행할 수 없을 때 발생할 수 있다.
Single instance 환경에서는 instance failure는 instance를 restart 시키고
database를 open하여 해결된다. Mount 상태에서 open 되는 중간 단계에서 SMON은
online redo log 파일을 읽어 instance recovery 작업을 수행한다.
OPS에서는 instance failure가 발생 했을 경우 다른 방식으로 instance
recovery가 수행된다. OPS에서는 한 노드에서 fail이 발생했다고 하더라도
다른 노드의 인스턴스는 계속 운영될 수 있기 때문에 instance failure는
database가 가용하지 않다는 것을 의미하지는 않는다.
Instance recovery는 dead instance를 처음으로 발견한 SMON 프로세스에서
수행한다. Recovery가 수행되는 동안 다음과 같은 작업이 일어난다.
- Fail이 발생하지 않은 다른 인스턴스에서는 fail이 발생한 인스턴스의
redo log 파일을 읽어 들여 데이터파일에 그 내용을 적용시킨다.
- 이 기간 동안 fail이 발생하지 않은 다른 노드에서도 buffer cache 영역의
내용을 write 하지는 못한다.
- DBWR disk I/O가 일어나지 못한다.
- DML 사용자에 의해 lock request를 할 수 없다.
a. Single-node Failure
한 인스턴스에서 fail이 난 다른 인스턴스에 대한 recovery를 수행하는 동안,
정상적으로 운영 중인 인스턴스는 fail이 난 인스턴스의 redo log entry를
읽어 들어 commit이 된 트랜잭션의 결과치를 데이터베이스에 반영시킨다.
따라서 commit 된 데이터에 대한 손실은 일어나지 않으며, fail이 난
인스턴스에서 commit 시키지 않은 트랜잭션에 대해서는 rollback을 수행하고,
트랜잭션에서 사용 중이던 자원을 release시킨다.
b. Multiple-node Failure
만약 OPS의 모든 인스턴스에서 fail이 발생했을 경우, 인스턴스 recovery는
어느 한 인스턴스라도 open이 될 때 자동으로 수행된다. 이 때 open되는 인스턴스는
fail이 발생한 인스턴스가 아니라도 상관 없으며, OPS에서 shared 모드
혹은 execlusive 모드에서 데이터베이스를 mount 하더라도 상관 없이 수행된다.
오라클이 shared 모드에서 수행되던, execlusive 모드에서 수행되건,
recovery 절차는 하나의 인스턴스에서, fail이 난 모든 인스턴스에 대한
recovery를 수행하는지 여부를 제외하고는 동일하다.
2) Media Failure 시
Oracle에서 사용하는 file을 저장하는 storage media에 문제가 발생했을 경우
발생한다. 이와 같은 상황에서는 일반적으로 data에 대한 read/write가 불가능하다.
Media failure가 발생했을 경우 recovery는 single instance의 경우와
마찬가지로 recovery가 수행되어야 한다. 두 경우 모드 archive log 파일을
이용해서 transaction recovery를 수행하여야 한다.
3) Node Failure 시
OPS 환경에서, 한 노드 전체에 fail이 발생했을 때, 해당 노드에서 동작하던
instance와 IDLM 컴포넌트에서도 fail이 발생한다. 이 경우 instance recovery를
하기 위해서는 IDLM은 lock에 대한 remaster를 시키기 위해 그 자신을
reconfigure시켜야 한다.
한 노드에서 fail이 발생했을 때 Cluster Manager 또는 다른 GMS product에서는
failure를 알리고, reconfiguration을 수행하여야만 한다. 이 작업이 수행되어야만
다른 노드에서 운영 중인 LMD0 프로세스와의 통신이 가능하다.
오라클에서는 fail이 발생한 노드에서 잡고 있는 lock 정보를 access할 경우나,
LMON 프로세스에서 heartbeat을 이용해서 fail이 발생한 노드가 더 이상
가용하지 않다는 것을 감지할 때 failure가 발생한 것을 알게 된다.
IDLM에서 reconfigure가 일어나면 instance recovery가 수행된다.
Instance recovery는 recovery를 수행하는 동안 자원에 대한 contention을
피하기 위해 전체 데이터베이스의 작업을 일시 중지시킬 수 있다.
FREEZE_DB_FOR_FAST_INSTANCE_RECOVERY initialization parameter 값을
TRUE로 지정하며 전체 데이터베이스가 일시적으로 작업을 멈추게 된다.
데이터 화일에서 fine-grain lock을 사용할 경우 기본값은 TRUE이다.
이 값을 FALSE로 지정할 경우 recovery가 필요한 데이터만이 일시적으로 작업이
멈춰진다. 데이터 화일이 hash lock을 사용할 경우 FALSE가 기본 값이다.
4) IDLM failure 시
한 노드에서 다른 연관된 프로세스의 fail이나 memory fault 등의 이유로 인해
IDLM 프로세스만 fail이 발생했다면 다른 노드의 LMON에서는 이 문제를 감지하여
lock reconfiguration process를 시작한다.
이 작업이 진행 중인 동안 lock 관련 작업은 처리가 정지되고 PCM lock 또는
다른 resource를 획득하기 위해 일부 사용자들은 대기 상태로 들어간다.
5) Interconnect Failure ( GMS failure ) 시
노드 간의 interconnect에서 fail이 발생하면 각각의 노드에서는 서로 다른
노드의 IDLM과 GMS에서 fail 이 발생했다고 간주하게 된다. GMS에서는 quorum
disk나 node에 pinging 등을 수행하는 다른 방법을 통해 시스템의 상태를 확인한다.
이 경우 Fail이 발생한 connection에 대해 두 노드 혹은 한쪽 노드에서
shutdown 이 일어난다.
Oracle 8 recovery mechanism에서는 노드 혹은 인스턴스에서 강제로 fail이
발생했을 경우 IDLM이나 instance가 startup 될 수 없게 된다. 경우에 따라서는
노드 간의 IDLM communication이 가용한지 여부를 확인하기 위해 cluster
validation code를 직접 작성하여 사용할 수도 있다. 이 방법을 사용하여
GMS에서 제공하지는 않지만, 문제를 진단한 후 shutdown을 수행하도록 할 수 있다.
이같은 code를 작성하기 위해서는 단일 PCM lock에서 처리되는 단일 data block에
대해 계속해서 update 를 수행해 보는 루틴이 들어가면 된다. 서로 연결된
두 노드에서 이 프로그램을 실행시키게 될 경우 interconnect에서 fail이
난 상황을 진단할 수 있게 된다.
만약 여러개의 노드가 cluster를 구성할 경우에는 매 interconnect 마다
다른 PCM lock에 의해 처리되는 data block을 update 함으로써, 어떤 노드와의
interconnect에 문제가 발생했는지를 알아낼 수 있다.
7. Parallel Recovery
Parallel Recovery의 목표는 compute와 I/O parallelism을 사용해서 crash
recovery, single-instance recovery, media recovery 시 소요되는 시간을 줄이는
데 있다.
Parallel recovery는 여러 디스크에 걸쳐 몇 개의 데이터파일에 대해 동시에
recovery를 수행할 때 가장 효율적이다
다음과 같이 2가지 방식으로 병렬화시킬 수 있다.
- RECOVERY_PARALLELISM 파라미터 지정
- RECOVER 명령의 옵션에 지정
오라클 서버는 하나의 프로세스에서 log file을 순차적으로 읽어들이고, redo
정보를 여러 개의 recovery 프로세스에 전달해, log file에 기록된 변동 사항을
데이터파일에 적용시킬 수 있다.
Recovery Process는 오라클에서 자동적으로 구동되므로, recovery를 수행할 경우
한 개 이상의 session을 사용할 필요가 없다.
RECOVERY_PARALLELISM의 최대값은 PARALLEL_MAX_SERVERS 파라미터에 지정된 값을
초과할 수 없다.
Reference Ducumment
Oracle8 ops manual

Configuration files of the Oracle Application server can be backed up by "Backup and Recovery Tool"
Pls refer to the documentation,
http://download.oracle.com/docs/cd/B32110_01/core.1013/b32196/part5.htm#i436649
Also "backup to tapes feature" is not yet supported by this tool
thanks,
Murugesh
Message was edited by:
Murugesan Appukuttty

Sun Identity Manger 8.0 and fail over..

We are setting up a fail/recovery site for our Sun Identity Manager solution, I had pictured a seem less fail over, but that looks near impossible to do with oracle database. I had pictured load balanced Appserver, with load balanced data bases, sort of a multi-master like LDAP allows..
Curious what others are using for a fail over site / setup.
Thanks

We're using 7.0. For us failover is basically mulitple servers all using the same DB repository, with a "smart" loadbalancer in front of them (smart meaning, able to detect which back end servers are responsive).
IdM doesn't use any inter-server temp-data synchronization, all the servers running off the same repository communicate by committing changes to the database.
So if a specific IdM instance dies, on the next page load the user will be redirected to a new server. That server will redirect to the login page and ask the user to re-auth, with the desired page placed after login.jsp as a "nextPage" argument. After (re-)logging in, the user's returned to the page they were trying to get to. However, in-progress edits that had not been committed back to the database will be lost.
We looked at high availability arrangements where valid sessions are shared across a new server, but fundamentally the limitation is that the app servers still don't sync in-progress edits, so the only difference between an HA environment and a more passive fail-over environment (like ours) is that in an HA environment the user doesn't have to re-login on a server failure; they still lose in-progress edits. So HA didn't seem like it added value to us.
If you are literally talking about an off-site, completely standby, seamless failover site, I agree I don't see how you would do that. I'd expect that you'd need the offsite setup to be a cold-standby site; configured to use the replicated database, but with the apps powered down until you actually need them. Otherwise, I think you'd have problems with the standby site servers not wanting to "standby". You could ensure no users end up on the standby servers, but background processes are likely to be run across both the primary and the standby services; I don't think you can enforce an "idle but running" status for the standby servers.
Edited by: etech on Feb 4, 2009 7:37 PM

Keep getting errors during recovery from recovery media?

My hard drive failed on my L655-S5065 Laptop.
I replace the Hard Drive, Purchased the Toshiba Recovery Media and updated the BIOS.
The first disc of the media loads fine. The second disc runs for about 20 minuntes then kicks back the error code (0A-0543-0000). After the first failed recovery I used the "erase hard drive" option on the recovery media, tried the recovery again and same error code?
Thanks for the help, Steve

I'd suggest contacting support and telling them what happens. It's possible that there's a problem with the discs, and if it hasn't been too long since you purchased them, maybe you can get another set. However, I don't know what the policy is regarding that.
- Peter

Failing recovery..​.so frustratin​g

Similar Messages

Maybe you are looking for

Failing recovery...so frustrating