Sign in
Microsoft.com
 
Microsoft
 
 
 

locked
Backup service not running - PC locked up RRS feed

 > 

  • Question

  • Question
    Sign in to vote
    0
    Sign in to vote
    WHS has all current updates, yet during backups at random times and with random clients, the PC locks up. The only entry is "Backup service Not Running", which is logical since the PC has frozen. After reboot, WHS starts normally with no errors. Nothing in the log files (again, since PC locked up).

    I'm not thinking PC hardware issue because this ONLY seems to happen during PC backups. Not all backups- some OK and system goes several days 100% OK.

    I've seen here where backup database needs to be recoved/repaired, but as I said, the system will go several days without issue, than lock during backup.

    I see in the logs where chkdsk is run by the ststem with no errors- so again I'm slow to suspect hardware issues...also the unit was running fine as a PC before I installed WHS OEM.

    Should I simply purge the backup database and keep fingers crossed?
    I'm more interseted to know why this is happening and if others have seen similar.
    During backup, what cause's lockup?

    As always, thanks in advance- this forum has been very helpful and oh yeah WHS is one of the best efforts msoft has created to date...besides W7 ;-)

    Monday, March 2, 2009 3:00 PM

All replies

  • Question
    Sign in to vote
    0
    Sign in to vote
    Fauldini said:

    WHS has all current updates, yet during backups at random times and with random clients, the PC locks up.


    Lock-ups or 'hangs' can be the result of failing drivers. In your case it looks like the lock-ups happen when stressing the network interface? So personally I would look for problems there first. Be sure to use the latest NIC drivers. Also make sure they are Windows 2003 compatible (if not available, you can try XP-drivers. In most cases they will also work)

    Theo.
    No home server like Home Server
    Monday, March 2, 2009 9:50 PM
    Moderator
  • Question
    Sign in to vote
    0
    Sign in to vote
    During manual backups, or copy large files I have no issues. NIC driver is the current one available. I have chkdsk'd all drives and removed all backups, for now assuming corrupt backup data, haven't deleted the backup content from the system root yet. I thought deleting all backups and doing a cleanup/repair (no errors BTW) would be next best thing. I'm letting the PC cook with all backups off.

    If no issues, then when backups turned back on, I get lockups again, not sure what next step would be as that would indicate a backup issue.
    Tuesday, March 3, 2009 1:51 PM
  • Question
    Sign in to vote
    0
    Sign in to vote
    Could you please submit a bug report on Connect? Make sure you collect and send logs from your server and a client that's having this issue (using the Windows Home Server toolkit) as part of the bug report.
    I'm not on the WHS team, I just post a lot. :)
    Tuesday, March 3, 2009 6:25 PM
    Moderator
  • Question
    Sign in to vote
    0
    Sign in to vote
    Fauldini said:

    During manual backups, or copy large files I have no issues. NIC driver is the current one available. I have chkdsk'd all drives and removed all backups, for now assuming corrupt backup data, haven't deleted the backup content from the system root yet. I thought deleting all backups and doing a cleanup/repair (no errors BTW) would be next best thing. I'm letting the PC cook with all backups off.

    If no issues, then when backups turned back on, I get lockups again, not sure what next step would be as that would indicate a backup issue.



    That your backup problem (and some other problems with WHS) is related to a bug in the Feburary WHS update released to Automatic Updates on or about Feb 24, 2009 is an unconfirmed rumor at this point. However, I would rather spread and unconfirmed rumor (that may be true) than not get the problems fixed with my server as soon as possible.

    Here is thread about backup (and other) problems being possibly related to the Feb update.  There is a good bit of evidence there supporting that the bug in the update exist.

    Please read this thread and in addition to submitting the bug on Connect as Ken recommended, please also validate the bug submitted by msdcinfo (Klode) on MS Connect.  The link to Klode's Bug Report is given in the thread.  Your help in tracking down wheather this issue if related to the Feburary update is appeciated.  Your validation of the existing bug report will help the WHS Team find the problem (if it exist) and solve a rash of recent problems that seem to be coming up since the Feb Update was released. Thanks! 
    George in Florida
    Tuesday, March 3, 2009 6:55 PM
  • Question
    Sign in to vote
    0
    Sign in to vote
    Hmm.....
    Theo.

    SeaRay33,
    If possible please save the "Memory Dump" you mention in your recent post on the link above. It could be helpfull to the WHS Team in determining why your server crashed. When submitting the issue to Connect, mention the dump file (submit only on request)


    No home server like Home Server
    Tuesday, March 3, 2009 8:16 PM
    Moderator
  • Question
    Sign in to vote
    0
    Sign in to vote
    Hi Theo,
    Thanks for your reply.  I have not used thid forum for a while but it appears your post is cut off to me.  I see (submit only request... and then a backet on the next line. Is some part of your reply missing?

    Also you do know I cannot open the WHS Console to get to the Toolkit Add-in so I cannot submit the data needed by MS on MS Connect.  Is there some way I can submit the memory dump file to MS other than via MS Connect which I cannot use right now?  Any ideas you have I will follow. I want to get this data to MS if it can help. Let me know please.
    George
    George in Florida
    Tuesday, March 3, 2009 8:25 PM
  • Question
    Sign in to vote
    0
    Sign in to vote
    I went ahead and created a bug on MS Connect. I can't submit CABS so don't know how well this will be recieved by MS.  Also there is a 10MB limit on files attached via Connect.  I tried anyway to send the Memory Dump file even though it is 480MB.  It is uploading now but I suspect it will fail before the file gets to the MS Server completely.  I know there is a way to send a large file to MS because I have done it before (probalby FTP, but I don' really remember).  I do remember you have to have a link sent from MS to get the file upload going. I have a contact at MS (Laura Jones) and may try to get it to her and MS that way.  Any idea anyone has about how to get the dump to MS to associate with the Connect Bug, I 'm listening.
    George in Florida
    Tuesday, March 3, 2009 9:24 PM
  • Question
    Sign in to vote
    0
    Sign in to vote
    SeaRay,
    (Sorry. My reply looked a bit odd. Fixed it)

    I do not want to hijack Fauldini's thread, but best would be to submit your bug-report now. You can add the CAB's at a later time. Optionally you can submit attachments to your report (like a .dmp file) under "File Attachments" at the end of the bug-report.
    Theo.

    Btw: I am not a regular reader on of the MediaSmartServer forum. As you seem to have major problems maybe it is an idea to start a new thread on this forum. Maybe others on this forum can confirm your "unconfirmed rumors". And if there is a bug this will help MS resolve it.

    No home server like Home Server
    Tuesday, March 3, 2009 9:31 PM
    Moderator
  • Question
    Sign in to vote
    0
    Sign in to vote
    Point taken.  Bug Summited on Connect. Moving on. Thanks.
    George in Florida
    Tuesday, March 3, 2009 9:35 PM
  • Question
    Sign in to vote
    0
    Sign in to vote
    I'd certainly like to do that Ken- however I do have "submit error reports" turned ON in WHS so is it necessary? I did notice 3 reports have been sent from my console which seem to respond to my 3 lockups since the Feb patch. I'll get on connect also and see if I can figure out how to start the process anyway.

    George- I certainly hope we don't have a bug caused by the feb patch... as I'm fast becoming a big fan of WHS, and if bug exists (as in the past) and caused backup routine to fail, corrupt or lock-up that would be a real shame.
    Wednesday, March 4, 2009 2:23 PM
  • Question
    Sign in to vote
    0
    Sign in to vote
    Fauldini said:

    I'd certainly like to do that Ken- however I do have "submit error reports" turned ON in WHS so is it necessary?

    One, this is a common misconception. The Windows Home Server team does not triage OCAs without having CABS from the toolkit.  Watson files are placed on a large server where they are triaged, analyzed and tracked by the OCA group.  If you want a developer to look at your individual problem, you need to file a bug report so we can assign it to a member of the product team.  The OCA mechanism is automatic and is in no way a part of Connect nor is it designed as a feedback mechansim for customers. We would have no way to locate your crashes on the watson servers without reviewing your event logs using CABs from the toolkit and again, we need a bug for this. Also, sending in CABs using the toolkit but not filing a bug, places them on the watson servers without a reference point.

    Two, from what we can gather, this behavior is being caused by an add-in as we have not seen this internally on servers that do not have any add-ins installed; however, we have not yet received a bug with enough information for us to triage i.e a bug describing all add-ins in the console.

    Thank you
    Lara Jones [MSFT] | Program Manager
    Community Support and Beta | Windows Home Server Team
    Windows Home Server Team Blog
    Connect Windows Home Server
    Windows Home Server
    Wednesday, March 4, 2009 8:11 PM
    Moderator
  • Question
    Sign in to vote
    0
    Sign in to vote

    This issue unresolved:

    The latest submission being
    CAB(s):
    606552096-client
    606548915-server

    During backups for no obvious reason, the client backup service will fail communication with sever:

    CLIENT LOGS at event time...

    Volume Shadow Copy Service error: Shadow Copy writer RemovableStorageManager called routine OpenNtmsSessionW which failed with status 0x80070422 (converted to 0x800423f4).

    =========and=====================

    Backup of volume S: to LMFSRV failed: Microsoft.HomeServer.Backup.Protocol.ProtocolException: Client / Server connection lost
       at Microsoft.HomeServer.Backup.Protocol.ReconnectableStream.TryReconnect(Int32 localGeneration)
       at Microsoft.HomeServer.Backup.Protocol.ReconnectableStream.WriteWithReconnect(Int32 count)
       at Microsoft.HomeServer.Backup.Protocol.ReconnectableStream.Write(Byte[] buffer, Int32 offset, Int32 count)
       at Microsoft.HomeServer.Common.Client.BinaryWriterEx.WriteFixed(Byte[] value)
       at Microsoft.HomeServer.Backup.Protocol.BackupProtocol.SendClusterHash(Int64 clusterIndex, Byte[] hash)
       at Microsoft.HomeServer.Backup.BackupOp.BackupOperation.DoClusterPass1()
       at Microsoft.HomeServer.Backup.BackupOp.BackupOperation.RunWithoutCatch()

    • Proposed as answer by kariya21Moderator Sunday, March 15, 2009 4:03 PM
    • Unproposed as answer by Fauldini Monday, March 23, 2009 1:42 PM
    Monday, March 9, 2009 2:37 PM