Boot Failed on Time-of-Date chip

Dear Sir/Madam
When I suspend my Sun Enterprise 2 (UltraSparc II 296MHz CPU) a few weeks. I can't boot it on now, when system after starting real time clock and display OS version information, system halt at:
WARNING: Time-of-Date chip had incorrect date; check and reset
System hangup here and don't access any intrerupt such "Stop A" and etc. I have to press power switch from power supply board turn off it and restart it, it halt at same point.
Cidy

If you have more than one user account, these instructions must be carried out as an administrator.
Launch the Console application in any of the following ways:
☞ Enter the first few letters of its name into a Spotlight search. Select it in the results (it should be at the top.)
☞ In the Finder, select Go ▹ Utilities from the menu bar, or press the key combination shift-command-U. The application is in the folder that opens.
☞ Open LaunchPad. Click Utilities, then Console in the icon grid.
Make sure the title of the Console window is All Messages. If it isn't, select All Messages from the SYSTEM LOG QUERIES menu on the left. If you don't see that menu, select
View ▹ Show Log List
from the menu bar.
Enter the word "Starting" (without the quotes) in the String Matching text field. You should now see log messages with the words "Starting * backup," where * represents any of the words "automatic," "manual," or "standard." Note the timestamp of the last such message that corresponds to an abnormal backup. Now
CLEAR THE WORD "Starting" FROM THE TEXT FIELD
so that all messages are showing, and scroll back in the log to the time you noted. Select the messages timestamped from then until the end of the backup, or the end of the log if that's not clear. Copy them to the Clipboard by pressing the key combination command-C. Paste (command-V) into a reply to this message.
If all you see are messages that contain the word "Starting," you didn't clear the text field.
If there are runs of repeated messages, post only one example of each. Don't post many repetitions of the same message.
When posting a log extract, be selective. Don't post more than is requested.
Please do not indiscriminately dump thousands of lines from the log into this discussion.
Some personal information, such as the names of your files, may be included — anonymize before posting.

Similar Messages

  • 2006 boot - 'fail to open eeprom.dat'

    2006 controller fails to boot, as follows:
    Cisco AireOS Version 3.2.150.10
    Initializing OS Services: Failed to open /mnt/application/eeprom.dat.
    Cisco Crash Handler
    This build was configured to copy this crash information to
    a file called: "/mnt/application/mwar_dump1.crash"
    I've not been able to find docs on this topic. Any help is appreciated! thanks,
    Steve

    Hi
    See this URL:
    http://www.cisco.com/en/US/customer/products/ps6308/products_field_notice09186a00807516b4.shtml
    Might not be the same root cause, but it seems if that eeprom file is lost or corrupted your WLC needs to go back to Cisco...
    Regards
    Aaron
    Please rate helpful posts...

  • Fail in Time and Date Update

    Hello,
    I use Compaq Presario CQ2200IX Desktop Pc for past 3 years....
    Problem:
    Recently i discovered that my pc has wrong date and time...whenever i switch on my pc everytime  i have to change my date and time from settings...
    Suggest me the solution for this issue...

    Hi,
    You're welcome
    If you set the correct date and time in the bios menu, then load into Windows, does the time then look correct?
    If it does, restart the PC and see if it still looks Ok.  If it doesn't, check the bios menu again - if the time is also incorrect again, you probably will need to replace the RTC ( cmos ) battery.
    Best regards,
    DP-K
    ****Click the White thumb to say thanks****
    ****Please mark Accept As Solution if it solves your problem****
    ****I don't work for HP****
    Microsoft MVP - Windows Experience

  • Boot Failed, Single User FSCK couldn't load, mounting Macintosh HD failed, repair and verify returns no errors, and i need to transfer my data before starting over - HELP!!!!

    Lets break down the facts here: My machine is an Intel-Based iMac running Mavericks - 1TB Hitachi Hard Drive
    1. Was running an initial baseline image with Time Machine when the computer froze - waited hours - nothing got better and no functions were possible (force quit, etc.)
    2. Hard Reboot
    3. Upon reboot, the iMac was unable to load the log-in screen. The image was a folder with a "?" on it.
    4. Rebooted with option key held down and selected Macintosh HD - Boot Failed
    5. Restarted and Rebooted with Command R held down
    6. Ran Disk Verify and Disk Repair - returned errors round one.
    7. Ran Disk Verify and Disk Repair - Returned no Errors
    8. Restart - Boot failed - the "NO" symbol replaced the apple symbol
    9. Reboot with Command R
    10. Attempt to mount Macintosh HD
    11. Mount Failed.
    12. Shutdown
    13. Connect Firwire to Host computer and Target Computer
    14. Boot with Command T
    15. TDM entered - Host Machine cannot read Target Hard Drive
    16. Shutdown
    17. Boot with Command S
    18. Endless loop created - Multiple errors including:
         - failed to open create the journal retval 0
         - could not read 512 bytes for the journal header - Return 22
         - Errorno 19
         - hfs_mounterror return: 22
    Short of springing for a software online, I have no idea what the next steps are to getting my data moved from the Macintosh HD to my external so I can just reformat and install the OS again. Any help would be greatly appreciated, this is is a serious headache and I cannot lose my data - Thats what I was backing it up for in the first place!!!!

    You may not have the luxury of having another Mac but you must know someone who does. You need to boot your Mac into target disk mode. This is going to be your best bet as far as saving your files. Keep in mind that everytime you mess with this computer you are further endangering your data. Also, once your Mac is booted as a target disk, it may be possible to mount it on a windoze computer just to copy your files to another drive. I used to have one here and if i still did I would try this for you but I "offed" it in favor on running windoze (Parallels) on my MBP. But, one way or another, you need to get next to another computer.

  • Biometrics/fingerorint reader fails 3 times on boot up

    when my system first boots up the fingerprint reader (integrated biometrics on my T60) reads 3 attempts (fails each time)  and prompts me for a password. I never actually run my finger through,  it just run through 3 attempts and fails.
    Use to work fine, device driver is working and updated. PC doc indicates a problem but in a very generic way (not helpfull)
    A little baffled by the self initiated 3 attempts to read a fingerprint on boot up
    Any help would be appreciated
    Thanks

    The lens seems to be scratched but before I try to replace the palmrest which I believe includes the lens ($115 !! ) I wanted to make sure that the symptoms made sense. I also ran PCdoctor on the Biometric Coprocessor and the test passed.
    Thanks for the help

  • I have to reset time and date after booting

    My mac pro cannot hold date and time.
    so far, I have replaced the pram battery and done the pram reset several times.
    at first i noticed that the sys pref panes were unlocked when I went in to change the time and date but I have since cured that in sys pref/security.
    the governing factor seems to be wetherr or npt is a revoot or completely cold boot (mains power switched completely off)
    the expected message comes up i.e. " your system clock is set to a time and date before 1.1.2008 some progs may bave erratically blah blah "
    the actual time has reset to 1.1.2001 ( dont know if that is significant but mentioned it just in case).
    So, if i just shut the machine down and then boot it up again, no probs
    if i restart, no probs
    shut down and pull the plug ??   1dt, Jan 2001
    would appreciate some advice

    Click here and ask. If they tell you to call, and they probably will, accept that.
    (123024)

  • Time Zone data downoad failed for 7841 phones

    Hi All ,
    we have 100 above 7841 phones facing same issue , time changes automatically . when i check the status message it is showing as "time zone data download failed "
    CUCM - 8.6.2
    Firmware -  sip78xx.10-1-1-9

    Hi Reddy,
    have a look into this discussion
    https://supportforums.cisco.com/discussion/12187361/cisco-7821-phones
    regds,
    aman

  • PowerPC G5 boots sporadically & doesn't remember date & time

    I have an old Dual 2.5 GHz PowerPC G5 (aluminum tower). When it boots up, I get a message that the Date & Time are no longer correct. I go into date and time settings and reset them, however when I shot down and reboot later, the time has been reset to June 1969 or some similar date. Also, when the computer shuts down, it cannot be rebooted immediately. If I try to reboot it, I hear the fans start up and drives start spinning, but then they all seem to power down (a red light can still be visible inside. If I shut it down and wait 15 minutes, it will boot up fine, however the date/time has reset to 1969.
    I have done the obvious things like replacing the clock battery and resetting the pram and smu, but still no joy. I suspect a hardware fault of some kind, but don't know what to try next. Any suggestions? It is such a beautiful machine, I hate to scrap it.

    I have just gone through a range of startup issues and have found the start-up problems were created by an unsuitable cable.
    See https://discussions.apple.com/message/18848177#18848177
    First thoughs were PRAM, cudo button and battery age. But the problem was a cable!
    If you have a printer and other peripherals attached, try an isolation test. Boot up without any cables connected and see if the computer behaves. If it does, add cables one at a time until you identify the faulty one.

  • Satellite A660 - Will not boot up and HDD boot fail

    Hi,
    firstly thanks for your time.
    Model: Satellite A660 (PSAW3A-07U00R)
    The problem started yesterday, the computer was going slow as an application closed, so I held the off button untill the pc turned off. When I restarded the laptop it went to a screen saying: Start windows normally or repair Windows (recomended)
    When started normally it just hangs at a blank screen, the repair Windows recommends a system restore to earlier point which didnt work. As it just hangs again. I tried pressing F8 and starting in safe mode but again it just hangs. Then after a few times trying safe mode and another system restore the computer then hangs when I press F8. After this the computer goes past the Toshiba logo screen with F2 and F12 options (which both still work), and then it comes up boot failed then goes blank and comes with boot failed bootfailed with some numbers and letters, then it goes to a small box titled boot menu with 4 options.These are
    HDD/SSD Toshiba MK6465GSX
    CD/DVD MAT****ABD-CMB UJ141ES
    FDD
    LAN
    If I press ESC it goes through the bootfailed loop and ends up at same screen, if I press enter on "HDD/SSD Toshiba MK6465GSX" then it quickly comes back to screen and at the bottom it says [HDD/SSD Toshiba MK6465GSX] is failed.
    I dont understand why it got worse over time. Can anyone think of why this has happend and more importantly how can I get my pc working again? Note: holding 0 then starting does nothing for me atm
    regards, Matthew

    All you people looking here on this dead thread.....
    Toshiba A660 laptops are renowned for having hard drive fails and boot up problems after grinding to a halt.
    My solution (after losing 3 hard drives [and a terabyte of family treasured times]) is the following.
    Use MALWAREBYTES (free download and use for 28 days)
    Scan and fix. Mine found over 300 trojans that 2013 Norton 360 could not find.
    Re-boot into safe mode.
    SCAN again.
    Re-boot and empty the malwarebytes repair files it retains...
    Run Norton/McAfee (whichever you have) and you should still have no issues.
    Make a back-up repair disc. Ooooops......no you cant...........at least my laptop can`t.
    I don`t know why.....
    Tell me tosh..... why does windows x64 refuse to allow me to make a system boot disc (even though the laptop is all driver updated and Windows updated)?
    Uninstall MalwareBytes when Norton/McAfee tells you there will be a conflict between the two programs.
    It tells you to re-boot after uninstalling it.
    Then when it re-boots you get a black screen. You cannot even get to bios. You think ytour laptop is turned into a brick frisbee. You pull out the battery in frustration after five minutes.
    You replace and re-boot....but again you get no bios or boot up.... you think its destroyed the Bios or graphics somehow....youo can hear the hard-drive but you have no clue whats going on..
    Around this time you shake the laptop in frustration.....
    Calm down.
    Switch on and leave FIFTEEN MINUTES....Ten of which will be a Black nothing screen with maybe a single white underscore line in the top left corner.LEAVE IT ALONE.
    Make a sunday dinner for ten people....When you go back to the computer it will be up and running.
    When you re-boot again, it will be dead black for five minutes...then boots up... you still think it has a problem... LEAVE IT.
    When you reboot again it should work perfect (assuming you have not been overheating it by using it on a cushion on your lap and overheating the insides [use a laptop fan tray]) if you have not shaken your hard drive or caused scrambled damage by pulling the power fifty times like some people do.
    I have lost three hard drives and thousands of Gigabytes of treasured family memories discovering the secret the hard way.
    Enjoy.
    Buy a different brand next time.
    ALL Windows system files should be on a SWITCHED (to update) version of Windows.
    Spinning drives should be for Data only.

  • Is or is not "Application & Driver Recovery DVD" bootable? - SafeMode boot fails-corrupt CryptUI.dll

    I'm trying to recover my daughter's Pavilion dm4-3170se. My daughter had not made a recovery disk and has no recent back-up of her data file set.
    Problems (and what I have done so far) are quite parallel to what the user reported in this amazingly detailed post:
    Difference is that in Safe Mode boot (command line or not), Windows boot fails on a dll, specifically CryptUI.DLL.
    While amazingly detailed post user isn't getting into Windows boot, I am...for about 30 DLLs before it chokes on the corrupted one. I have tried a number of other things to get past it to no avail.
    My daughter's original Recovery Disc set bought the farm when her house burned. So I ordered and got a replacement set from HP. I am loathe to use it before recovering her data files because she will lose maybe 40% of her professional work.
    The delivered Recovery Disc set includes an "Application and Driver Recovery DVD". Given >20 years of Wintel machine tradition, I'm presuming it's bootable. Amazingly Detailed Post user got hers to boot from her DVD drive. But configuring the BIOS to seek the DVD drive as the first boot choice doesn't get it to boot after two tries.
    Before I pour more time into this, I'd like the Collective Wisdom here.
    Q1: Is this HP disc, numbered 691822-B22, meant to be bootable?
    Q2a: If it is, do you imagine I can use the command line interface to copy identifed-as-bad DLL(s) to the HD?
    Q2b: If it isn't, why the, er, gollygoshdarn isn't it? Must be an actual reasonable thing...
    Thanks for all insights based on experience.
    This question was solved.
    View Solution.

    Hi:
    Any HP application and driver DVD I have ever used is not bootable.
    It should autorun from the windows desktop once windows has been reinstalled.
    That is the only question I can answer of the ones you asked.
    Suggestion...
    Make your own W7 installation ISO from the link below.
    Use that to install W7 and do not delete any partitions or format the drive.
    Windows will install and create a Windows.old folder of the current operating system.
    Then you can copy any files you need from the Windows.old folder after W7 is installed.
    Once you are sure you got what you need, run the recovery disk set to restore the hard drive to its out of the box condition.
    Link to W7 ISO files is below.  Use the W7 x64 home premium file from the SP1 Media Refresh listing.
    http://forums.mydigitallife.info/threads/14709-Windows-7-Digital-River-direct-links-Multiple-Languag...
    Then use this tool to transfer the iso file onto a DVD or 4 GB USB flash drive.  The tool will also make the iso file bootable.
    http://www.microsoftstore.com/store/msusa/html/pbPage.Help_Win7_usbdvd_dwnTool

  • PXE boot fails and reboots after loading PE

    I have run into what I think is a unique issue and need some help determining the cause.
    We are in the process of replacing and aging DP/PXE point (2003 R2 SP2) with a new server (2008 STD R2 SP1).  What makes my pxe issue unique is that pxe works without issue on the existing 2003 DP/PXE server.  But on the new 2008 server I run into
    the following issue.
    Environment:  Config Manager 2007 R2, a single primary, multiple DP's and PXE points.
    Issue:  When I attempt to PXE boot a system, I am able to load PE, but shortly after the custom background screen is loaded, the system reboots.  I've searched the internet quite a bit and found lots of potential causes including, bad/missing drivers,
    certificate issues, rights issues, etc.  None of these seem to be the cause.
    My troubleshooting has determined that the client computers are unable to download the variables.dat file.  I just don't know why.
    We're using the same boot images on both servers. 
    I've tried using multiple computer models and VM's. 
    I've opened a command prompt as soon as our background image loads and have verified that the system is pulling a valid IP address.  I am able to map a drive to the PXE server's REMINST share using our sccm net access account and manually copy the .var
    file using xcopy to the appropriate directory on the local virtual drive.   I've also attempted to manually run smstftp.exe by mimicking the command line from the smsts log file.  I'll admit that I'm not sure I have the correct syntax for smstftp. 
    I've tried several variations and all but one result in a short pause and no file copied/created in the X:\sms\data folder.  The one that does produce a result says that the file cannot be found.  I checked for typos and made sure I used the name
    of the newly created .var file.
    I've also tried disabling anti-virus on the server, shutting off the windows firewall on the server, granting everyone read rights to the REMINST share.
    Below is the smstslog file I've been using as a reference.  Per corporate security policy, I have X'd out the IP address of the PXE server.  The log file for the successful pxe boot from the 2003 server shows an exit code of 0 for smstftp.exe, a note
    about successful download of the pxe var file and then it continues through the rest of the boot process.
    -----SMSTS log file from a failed PXE boot on the new 2008 server -----
    <![LOG[LOGGING: Finalize process ID set to 832]LOG]!><time="16:13:54.440+000" date="12-23-2013" component="TSBootShell" context="" type="1" thread="836" file="tslogging.cpp:1489">
    <![LOG[==============================[ TSBootShell.exe ]==============================]LOG]!><time="16:13:54.440+000" date="12-23-2013" component="TSBootShell" context="" type="1" thread="836"
    file="bootshell.cpp:963">
    <![LOG[Succeeded loading resource DLL 'X:\sms\bin\i386\1033\TSRES.DLL']LOG]!><time="16:13:54.440+000" date="12-23-2013" component="TSBootShell" context="" type="1" thread="836" file="util.cpp:869">
    <![LOG[Debug shell is enabled]LOG]!><time="16:13:54.440+000" date="12-23-2013" component="TSBootShell" context="" type="1" thread="836" file="bootshell.cpp:974">
    <![LOG[Waiting for PNP initialization...]LOG]!><time="16:13:54.471+000" date="12-23-2013" component="TSBootShell" context="" type="1" thread="880" file="bootshell.cpp:59">
    <![LOG[Booted from network (PXE)]LOG]!><time="16:13:54.830+000" date="12-23-2013" component="TSBootShell" context="" type="1" thread="880" file="configpath.cpp:198">
    <![LOG[Found config path X:\sms\data\]LOG]!><time="16:13:54.830+000" date="12-23-2013" component="TSBootShell" context="" type="1" thread="880" file="bootshell.cpp:553">
    <![LOG[Booting from removable media, not restoring bootloaders on hard drive]LOG]!><time="16:13:54.830+000" date="12-23-2013" component="TSBootShell" context="" type="1" thread="880" file="bootshell.cpp:564">
    <![LOG[Executing command line: wpeinit.exe -winpe]LOG]!><time="16:13:54.830+000" date="12-23-2013" component="TSBootShell" context="" type="1" thread="880" file="bootshell.cpp:767">
    <![LOG[Executing command line: X:\WINDOWS\system32\cmd.exe /k]LOG]!><time="16:13:57.014+000" date="12-23-2013" component="TSBootShell" context="" type="1" thread="836" file="bootshell.cpp:767">
    <![LOG[The command completed successfully.]LOG]!><time="16:13:57.014+000" date="12-23-2013" component="TSBootShell" context="" type="1" thread="836" file="bootshell.cpp:850">
    <![LOG[Successfully launched command shell.]LOG]!><time="16:13:57.014+000" date="12-23-2013" component="TSBootShell" context="" type="1" thread="836" file="bootshell.cpp:430">
    <![LOG[The command completed successfully.]LOG]!><time="16:14:41.458+000" date="12-23-2013" component="TSBootShell" context="" type="1" thread="880" file="bootshell.cpp:850">
    <![LOG[Starting DNS client service.]LOG]!><time="16:14:41.458+000" date="12-23-2013" component="TSBootShell" context="" type="1" thread="880" file="bootshell.cpp:597">
    <![LOG[Executing command line: X:\sms\bin\i386\TsmBootstrap.exe /env:WinPE /configpath:X:\sms\data\]LOG]!><time="16:14:41.973+000" date="12-23-2013" component="TSBootShell" context="" type="1" thread="880"
    file="bootshell.cpp:767">
    <![LOG[The command completed successfully.]LOG]!><time="16:14:41.973+000" date="12-23-2013" component="TSBootShell" context="" type="1" thread="880" file="bootshell.cpp:850">
    <![LOG[==============================[ TSMBootStrap.exe ]==============================]LOG]!><time="16:14:41.989+000" date="12-23-2013" component="TSMBootstrap" context="" type="1" thread="1932"
    file="tsmbootstrap.cpp:1039">
    <![LOG[Command line: X:\sms\bin\i386\TsmBootstrap.exe /env:WinPE /configpath:X:\sms\data\]LOG]!><time="16:14:41.989+000" date="12-23-2013" component="TSMBootstrap" context="" type="0" thread="1932"
    file="tsmbootstrap.cpp:1040">
    <![LOG[Succeeded loading resource DLL 'X:\sms\bin\i386\1033\TSRES.DLL']LOG]!><time="16:14:41.989+000" date="12-23-2013" component="TSMBootstrap" context="" type="1" thread="1932" file="util.cpp:869">
    <![LOG[Succeeded loading resource DLL 'X:\sms\bin\i386\TSRESNLC.DLL']LOG]!><time="16:14:41.989+000" date="12-23-2013" component="TSMBootstrap" context="" type="1" thread="1932" file="resourceutils.cpp:152">
    <![LOG[Processor Is IA64: 0]LOG]!><time="16:14:41.989+000" date="12-23-2013" component="TSMBootstrap" context="" type="1" thread="1932" file="tsmbootstrap.cpp:1005">
    <![LOG[PXE Boot with Root = X:\]LOG]!><time="16:14:41.989+000" date="12-23-2013" component="TSMBootstrap" context="" type="1" thread="1932" file="tsmbootstrap.cpp:921">
    <![LOG[Executing from PXE in WinPE]LOG]!><time="16:14:41.989+000" date="12-23-2013" component="TSMBootstrap" context="" type="0" thread="1932" file="tsmbootstrap.cpp:936">
    <![LOG[Loading TsPxe.dll from X:\sms\bin\i386\TsPxe.dll]LOG]!><time="16:14:41.989+000" date="12-23-2013" component="TSMBootstrap" context="" type="0" thread="1932" file="tsmbootstraputil.cpp:1319">
    <![LOG[TsPxe.dll loaded]LOG]!><time="16:14:42.004+000" date="12-23-2013" component="TSPxe" context="" type="0" thread="1932" file="tsmbootstraputil.cpp:1329">
    <![LOG[Device has PXE booted]LOG]!><time="16:14:42.004+000" date="12-23-2013" component="TSPxe" context="" type="0" thread="1932" file="tspxe.cpp:122">
    <![LOG[Variable Path: \SMSTemp\2013.12.23.16.11.24.0002.{AB0FBE86-1F6C-47D7-919B-A44641035A2E}.boot.var]LOG]!><time="16:14:42.004+000" date="12-23-2013" component="TSPxe" context="" type="0" thread="1932"
    file="tspxe.cpp:134">
    <![LOG[Variable Key Len: 61]LOG]!><time="16:14:42.004+000" date="12-23-2013" component="TSPxe" context="" type="0" thread="1932" file="tspxe.cpp:141">
    <![LOG[Succesfully added firewall rule for Tftp]LOG]!><time="16:14:42.004+000" date="12-23-2013" component="TSPxe" context="" type="0" thread="1932" file="fwopen.cpp:123">
    <![LOG[Executing: X:\sms\bin\i386\smstftp.exe -i XXX.XXX.XXX.XXX get \SMSTemp\2013.12.23.16.11.24.0002.{AB0FBE86-1F6C-47D7-919B-A44641035A2E}.boot.var X:\sms\data\variables.dat]LOG]!><time="16:14:42.004+000" date="12-23-2013"
    component="TSPxe" context="" type="0" thread="1932" file="tspxe.cpp:177">
    <![LOG[Command line for extension .exe is "%1" %*]LOG]!><time="16:14:42.067+000" date="12-23-2013" component="TSPxe" context="" type="0" thread="1932" file="commandline.cpp:229">
    <![LOG[Set command line: "X:\sms\bin\i386\smstftp.exe" -i XXX.XXX.XXX.XXX get \SMSTemp\2013.12.23.16.11.24.0002.{AB0FBE86-1F6C-47D7-919B-A44641035A2E}.boot.var X:\sms\data\variables.dat]LOG]!><time="16:14:42.067+000" date="12-23-2013"
    component="TSPxe" context="" type="0" thread="1932" file="commandline.cpp:707">
    <![LOG[Executing command line: "X:\sms\bin\i386\smstftp.exe" -i XXX.XXX.XXX.XXX get \SMSTemp\2013.12.23.16.11.24.0002.{AB0FBE86-1F6C-47D7-919B-A44641035A2E}.boot.var X:\sms\data\variables.dat]LOG]!><time="16:14:42.067+000" date="12-23-2013"
    component="TSPxe" context="" type="1" thread="1932" file="commandline.cpp:805">
    <![LOG[Process completed with exit code 1]LOG]!><time="16:15:29.179+000" date="12-23-2013" component="TSPxe" context="" type="1" thread="1932" file="commandline.cpp:1102">
    <![LOG[Succesfully removed firewall rule for Tftp]LOG]!><time="16:15:29.194+000" date="12-23-2013" component="TSPxe" context="" type="0" thread="1932" file="fwopen.cpp:146">
    <![LOG[uExitCode == 0, HRESULT=80004005 (e:\nts_sms_fre\sms\server\pxe\tspxe\tspxe.cpp,185)]LOG]!><time="16:15:29.194+000" date="12-23-2013" component="TSPxe" context="" type="0" thread="1932"
    file="tspxe.cpp:185">
    <![LOG[Failed to download pxe variable file. Code(0x00000001)]LOG]!><time="16:15:29.194+000" date="12-23-2013" component="TSPxe" context="" type="3" thread="1932" file="tspxe.cpp:185">
    <![LOG[PxeGetPxeData failed with 0x80004005]LOG]!><time="16:15:29.194+000" date="12-23-2013" component="TSPxe" context="" type="3" thread="1932" file="tsmbootstraputil.cpp:1419">
    <![LOG[HRESULT_FROM_WIN32(dwError), HRESULT=80004005 (e:\nts_sms_fre\sms\client\tasksequence\tsmbootstrap\tsmbootstraputil.cpp,1420)]LOG]!><time="16:15:29.194+000" date="12-23-2013" component="TSPxe" context=""
    type="0" thread="1932" file="tsmbootstraputil.cpp:1420">
    <![LOG[TSMBootstrapUtil::PxeGetPxeData(&bPxeBooted, sVariablesFile, sPxePasswd), HRESULT=80004005 (e:\nts_sms_fre\sms\client\tasksequence\tsmbootstrap\tsmediawizardcontrol.cpp,2236)]LOG]!><time="16:15:29.194+000" date="12-23-2013"
    component="TSPxe" context="" type="0" thread="1932" file="tsmediawizardcontrol.cpp:2236">
    <![LOG[oTSMediaWizardControl.Run( sMediaRoot, true, true ), HRESULT=80004005 (e:\nts_sms_fre\sms\client\tasksequence\tsmbootstrap\tsmbootstrap.cpp,937)]LOG]!><time="16:15:29.194+000" date="12-23-2013" component="TSPxe"
    context="" type="0" thread="1932" file="tsmbootstrap.cpp:937">
    <![LOG[Execute( eExecutionEnv, sConfigPath, sTSXMLFile, uBootCount, &uExitCode ), HRESULT=80004005 (e:\nts_sms_fre\sms\client\tasksequence\tsmbootstrap\tsmbootstrap.cpp,1106)]LOG]!><time="16:15:29.194+000" date="12-23-2013"
    component="TSPxe" context="" type="0" thread="1932" file="tsmbootstrap.cpp:1106">
    <![LOG[Exiting with return code 0x80004005]LOG]!><time="16:15:29.194+000" date="12-23-2013" component="TSPxe" context="" type="1" thread="1932" file="tsmbootstrap.cpp:1118">
    <![LOG[Execution complete.]LOG]!><time="16:15:29.194+000" date="12-23-2013" component="TSBootShell" context="" type="1" thread="880" file="bootshell.cpp:624">
    <![LOG[Finalizing logging from process 832]LOG]!><time="16:15:29.194+000" date="12-23-2013" component="TSBootShell" context="" type="1" thread="880" file="tslogging.cpp:1736">
    <![LOG[Finalizing logs to root of first available drive]LOG]!><time="16:15:29.194+000" date="12-23-2013" component="TSBootShell" context="" type="1" thread="880" file="tslogging.cpp:1578">
    <![LOG[LOGGING: Setting log directory to "D:\SMSTSLog".]LOG]!><time="16:15:29.491+000" date="12-23-2013" component="TSBootShell" context="" type="1" thread="880" file="tslogging.cpp:1803">
    This has been an extremely frustrating issue and any assistance would be greatly appreciated!

    Thanks for your quick response Jason!  I didn't expect someone to reply so quickly or I would have checked back sooner. 
    I had found the two 'older' posts already, but had not seen the 'newer' one.  Unfortunately that did not give me any new ideas.  But your comment on checking for TFTP availability did.  Here are things I have tried since my original
    post...
    I re-ran most of my tests in case I missed something.  I only found one change.  Even though I double-checked, I must have made a typo when I manually ran the smstftp.exe command, because when I ran it again I received a timeout message instead
    of file not found.
    I had a minor 'thinking outside of the box moment' and decided to PXE boot the new 2008 R2 server itself.  This was successful and I interpreted the success as meaning that the hardware is ok.  Thinking there may be a compatibility issue with
    the hardware and the OS, I tried a few different NIC drivers, settings, registry keys, and even a completely different NIC.  No luck on any of these.
    I decided to build another Server on a VM tovalidate my build process and configuration.  And of course clients in multiple locations were able to PXE boot off this VM.  Too bad I can't use this in production.
    After reading your response Jason, I began to focus on network.  I moved the server to a few different locations so it was utilizing different switches.  No luck.  I noticed in the event viewer for WDS that the server was logging the
    beginning of the boot.var file via TFTP.  This of course was not very surprising.  What was surprising is that the very next entry (informational) noted that the client 'COMPLETED' the download of the boot.var file via TFTP.  I know that completed
    does not mean successful, but it usually implies or is interpreted as successful.  It should have logged a warning or error, or nothing at all because although the process completed, it was not successful.  I re-verified that the file was not downloaded
    to the client and the client log file still shows the same error noted in the logfile from my original post.
    Finally, I installed sniffing software on the server and ran some captures while attempting to PXE boot.  Even though I am not much of a network guy, I quickly discovered two things.  First, I found the section where the client attempts to download
    the boot.var file.  Unfortunately I don't think the local security team will allow me to post the capture, so I'll do my best to describe what I found.  It starts with a single entry where the client calls for the file via TFTP protocol.  This
    is followed by a series of alternating entries (all TFTP) where it looks like the server attempts to send a portion of the file, and the client sends an acknowledgement.  The sending entries all have checksum errors.  The checksum received on
    all packets is 0x0000 and of course should be something else.  There is also a shorter section below this with alternating entries where the server attempts to send ICMP packets and the client responds with TFTP acknowledgements. 
    The ICMP entries are all marked as Destination unreachable (Port Unreachable).
    The second thing I noticed from the network capture is the a few 'Spanning Tree Protocol' entries.  I my search for a solution, I remember reading several posts saying that Spanning Tree can cause this issue.  When I asked, I was assured that
    Spanning Tree was disabled in this environment.  It made sense too, because the 2003 PXE server was functioning properly, and Spanning Tree should affect both 2003 and 2008 servers, right?
    Either way I will bring my findings to the network team and see what they have to say.
    Any additional thoughts or ideas???

  • Time Machine spends hours partially backing up and then fails with "Time Machine couldn't complete the backup due to a network problem."  Tried suggestions I've seen on the forum.

    Time Machine spends hours partially backing up and then fails with "Time Machine couldn't complete the backup due to a network problem."  I've tried various suggestions I've seen on the forum but nothing has worked.  TIme Machine worked fine for the last two years and just suddenly started having this problem every time.  The only thing that was a little different is that the computer was off for a week while on vacation and then I added a large amount (20 GB) of photos. Now the requested backup size is 82GB, which is large, and process proceeds very slowly for 2-3 hours before failing with the message mentioned.  I have more than enough available backup storage space for it.  Before failing, Time Machine has backed up no more than 12GB or so of the backup.  It fails during different files each time.
    I've turned off the computer sleep feature, and I've checked that the NAS is set to never automatically power down. I normally backup over Wi-Fi, but I've also tried connecting to Ethernet and it still has the same problem.  It's odd because I also have a MacBook Pro that is still backing up fine to the same NAS using the MacBook's Time Machine. 
    I am using an iMac with OS X 10.6.8 and an Iomega StorCenter ix2-200 NAS.
    I have system logs that I can share if helpful.  The logged messages vary a bit from run to run, but here are some messages that I've been seeing:
    I always get this message near the beginning of the backup:
    Event store UUIDs don't match for volume: Macintosh HD
    I've gotten this messsage a number of times:
    Bulk setting Spotlight attributes failed.
    One Day
    Stopping backupd to allow ejection of backup destination disk!
    Another day
    1/7/12 10:44:20 AM
    mDNSResponder[18]
    PenaltyTimeForServer: PenaltyTime negative -112916, (server penaltyTime -1132397006, timenow -1132284090) resetting the penalty
    1/7/12 10:46:37 AM
    kernel
    ASP_TCP Disconnect: triggering reconnect by bumping reconnTrigger from curr value 0 on so 0x1106be94
    1/7/12 10:46:37 AM
    kernel
    AFP_VFS afpfs_DoReconnect started /Volumes/TimeMachine prevTrigger 0 currTrigger 1
    Another Day
    1/6/12 8:03:22 AM
    Google Chrome[164]
    Cannot find function pointer CMPluginInFactory for factory 3487BB5A-3E66-11D5-A64E-003065B300BC in CFBundle/CFPlugIn 0x16f99e20 </Users/smarmer/Library/Contextual Menu Items/Google Notifier Quick Add CM Plugin.plugin> (not loaded)
    1/6/12 8:04:02 AM
    com.apple.backupd[193]
    Copied 7.5 GB of 67.0 GB, 8866 of 8866 items
    1/6/12 8:06:58 AM
    /System/Library/CoreServices/CCacheServer.app/Contents/MacOS/CCacheServer[1013]
    No valid tickets, timing out
    1/6/12 8:29:44 AM
    mDNSResponder[19]
    PenaltyTimeForServer: PenaltyTime negative -148702, (server penaltyTime 2056822773, timenow 2056971475) resetting the penalty
    1/6/12 8:59:22 AM
    kernel
    ASP_TCP Disconnect: triggering reconnect by bumping reconnTrigger from curr value 0 on so 0xa5ac380
    1/6/12 8:59:22 AM
    kernel
    AFP_VFS afpfs_DoReconnect started /Volumes/TimeMachine prevTrigger 0 currTrigger 1
    1/6/12 8:59:22 AM
    kernel
    AFP_VFS afpfs_DoReconnect:  doing reconnect on /Volumes/TimeMachine
    1/6/12 8:59:22 AM
    kernel
    AFP_VFS afpfs_DoReconnect:  soft mounted and hidden volume so do not notify KEA for /Volumes/TimeMachine
    1/6/12 8:59:22 AM
    kernel
    AFP_VFS afpfs_DoReconnect:  Max reconnect time: 30 secs, Connect timeout: 15 secs for /Volumes/TimeMachine
    1/6/12 8:59:22 AM
    kernel
    AFP_VFS afpfs_DoReconnect:  connect to the server /Volumes/TimeMachine
    1/6/12 8:59:22 AM
    kernel
    ASP_TCP asp_SetTCPQoS:  sock_settclassopt got error 57
    Another day
    1/5/12 3:48:55 PM
    mdworker[2128]
    CFPropertyListCreateFromXMLData(): Old-style plist parser: missing semicolon in dictionary.
    1/5/12 4:24:54 PM
    mDNSResponder[19]
    PenaltyTimeForServer: PenaltyTime negative -42698, (server penaltyTime 1148718961, timenow 1148761659) resetting the penalty
    1/5/12 4:29:58 PM
    com.apple.backupd[2074]
    Copied 586.4 MB of 67.0 GB, 9891 of 9891 items
    1/5/12 4:39:00 PM
    kernel
    ASP_TCP Disconnect: triggering reconnect by bumping reconnTrigger from curr value 0 on so 0xa1c0380

    bokon0n wrote:
    1/11/12 8:53:30 AM
    com.apple.backupd[1169]
    Warning: Destination /Volumes/TimeMachine does not support TM Lock Stealing
    1/11/12 8:53:30 AM
    com.apple.backupd[1169]
    Warning: Destination /Volumes/TimeMachine does not support Server Reply Cache
    Those indicate that your NAS is not fully compatible with Snow Leopard. 
    1/11/12 8:53:35 AM
    kernel
    jnl: disk2s2: replay_journal: from: 67182592 to: 78680064 (joffset 0xa7b8000)
    1/11/12 8:53:39 AM
    kernel
    jnl: disk2s2: examining extra transactions starting @ 78680064 / 0x4b09000
    1/11/12 8:53:39 AM
    kernel
    jnl: disk2s2: Extra txn replay stopped @ 79056896 / 0x4b65000
    1/11/12 8:53:49 AM
    kernel
    jnl: disk2s2: journal replay done.
    1/11/12 8:53:49 AM
    fseventsd[41]
    event logs in /Volumes/Time Machine/.fseventsd out of sync with volume.  destroying old logs. (253512 14 253512)
    1/11/12 8:53:50 AM
    kernel
    hfs: Removed 1 orphaned / unlinked files and 0 directories
    That looks like a problem was found with the file system (data) on the TM disk.  I don't know the details, but OSX tried to recover it from the journal, and found extra data on the drive.    Likely a result of the incompatibility mentioned above.
    1/11/12 9:47:40 AM
    com.apple.backupd[1169]
    Bulk setting Spotlight attributes failed.
    That's a problem writing to the NAS drive.
    But the backup continued after all this.
    1/11/12 1:25:07 PM
    kernel
    ASP_TCP Disconnect: triggering reconnect by bumping reconnTrigger from curr value 0 on so 0x9d00b44
    Something caused a disconnect.  Can't tell from the log what it was.
    I doubt it's a problem with something in OSX being damaged or corrupted, but reinstalling OSX isn't a major hassle, so might be worth a try.
    To be incompatible with Snow Leopard, this NAS must be at least a couple of years old.  It may be beginning to fail.
    Contact the maker.  See if there's an update to make it compatible with Snow Leopard.  If so, that might fix it.
    If not, or if that doesn't fix it, see if they have any diagnostics that will shed any light.

  • When I did 7.1 update on iPhone five my reminders no longer works correctly it automatically erases the time and date that I requested

    Can somebody tell me why my reminders no longer work correctly on 7.1 update on iPhone five every time I post a reminder it would delete the time and date of the reminder and my reminders do not go off.

    Remove Office 2008 for Mac using Microsoft deinstall procedure. Reinstall Office 2008 for Mac.  If there are updates, apply them. Using Disk Utility, verify/repair permissions on your boot drive.
    Does Office for Mac 2008 now work correctly? If not, you may want to repeat the above first sentence, and then update to Office for Mac 2011, and apply the latest (14.4.8) update which has Yosemite fixes.

  • Hard Drive failed - Trying to Use Data Rescue II

    I am trying to recover some photos and videos of my first child's first 20 months alive. My MacBook crashed while I was checking my gmail one night. I have a friend's iBook G4 connected to my MacBook via FireWire right now and am trying to use Data Rescue II to possibly recover my photos and videos. I can live without everything else. When I use the install disc to boot up my MacBook, all the iBook is seeing is the install disc, not the hard drive. Why? and what am I doing wrong? Why can't I see/scan the hard drive, too? Do I have other options?
    Thank you!

    When I hook the FireWire up, should something automatically pop up on the iBook, showing me that it recognizes the MacBook is now connected?
    The drive in the MacBook would mount like any other hard drive.
    Is it still a possibility that it's the data cable, or is that pretty unlikely?
    Given that Disk Utility in the installer disk won't see the drive, I think it most likely that the drive has failed, in which case Data Rescue will not be able to recover anything (it won't work if the drive won't even mount). Probably the only way you're going to be able to recover any files would be by sending the drive to a data recovery service, and those are very expensive.
    You can try removing the drive and putting it in an external case or using a drive adapter like the NewerTech unit (whatever's least expensive). That would verify that the problem is the drive and not with the drive circuitry on the MacBook. If you have an Apple Store near you, often they can perform such a test at the Genius Bar which would save you from having to buy a case/adapter yourself.

  • Is it possible to sync time capsule data to a external hard drive

    Is it possible to sync time capsule data to a external hard drive connected to time capsule via usb. (as an precaution just incase time capsule fails)
    Thanks

    Yes, if the USB drive has been previously formatted correctly in Mac OS Extended (Journaled) format.
    Open AirPort Utility - Click Manual Setup
    Click the Disks icon
    Click the Disks tab below the icon
    Click Archive
    Allow plenty of time for the copy process to occur. You will not be able to make Time Machine backups from your Mac until the Archive process has completed.

Maybe you are looking for

  • Finder problems in 10.9.5

    Hi All Since installing the 10.9.5 update today I have experienced lots of problems with the finder - it won't allow me to select folders or items, and finder windows won't close or minimize.  Everything else seems to be ok but finder being unusable

  • Satellite A200-1GB PSAE6 Flashcards issue - serial number is invalid

    Hi all. I need help and something for my headache... :D Today I were looking to the updates zone and see a newer version for the Flashcard, so I donwloaded it and install, but now begin the problems... when the setup starts it says that must uninstal

  • Blank page shown when Jive Forum is started

    Hi, we got a blank page when the Forum is started. Configuration of iViews is fine. Problem only occurs when forum is called when using browsers that have more security restrictions. Strange enough the SDN forum works fine in those case, but not our

  • Duplicate check in a Java functionality

    Hi, I am writing a small integration piece to to retrive the testcases from TestCase Management tool in java, in which i have the following scenarios:- 1)     I have testcase which is "failed", that time I am checking whether there is any defect whic

  • Can I use the marker option to separate files in one track

    Hi, Can anybody give me some advice please on how to record an audio track (speaking) one channel in stereo then split into separate parts like chapters in a book. Its for a charity group Talking Newspaper for the blind. They have readers reading loc