Sign in
Microsoft.com
 
Microsoft
 
 
 

locked
How to log Bug Report - SYS Drive Failing RRS feed

 > 

  • Question

  • Question
    Sign in to vote
    0
    Sign in to vote
    Hi

    Having installed WHS Toolkit and collected the logs to submit as a bug report for my ongoing 12 - 14 day cycle of "SYS Drive Failing" error messages, its not clear how I should add contextual info for the cab?

    Appreciate if someone could give a quick summary so that I can value add to the log data and try and progress resolution of my ongoing problem with WHS.

    Cheers,
    TonyT
    Thursday, November 6, 2008 6:44 PM

Answers

  • Question
    Sign in to vote
    0
    Sign in to vote
    TonyT,

    As the bug reporting process is semi-automated, in previous cases like this the recommended method is to post your summary here - along with the CAB file ID numbers.

    A couple of the Team read all posts, mainly Lara, and either they can pick up on your post, or a Mod can highlight it for them.

    Colin




    If anyone answers your query successfully, please mark it as 'Helpful', to guide other users.
    • Marked as answer by TonyT65 Friday, November 7, 2008 10:06 AM
    Thursday, November 6, 2008 7:33 PM
    Moderator
  • Question
    Sign in to vote
    0
    Sign in to vote
    Or you can try to join the WHS Beta program on Connect, as outlined in this thread.
    Here you can add information in text form to a bug report.
    Best greetings from Germany
    Olaf
    • Marked as answer by TonyT65 Friday, November 7, 2008 10:06 AM
    Thursday, November 6, 2008 8:43 PM
    Moderator
  • Question
    Sign in to vote
    0
    Sign in to vote
    You should do as Olaf has recommended and join the WHS "beta program" on Connect.
    I'm not on the WHS team, I just post a lot. :)
    • Marked as answer by TonyT65 Friday, November 7, 2008 10:06 AM
    Thursday, November 6, 2008 9:35 PM
    Moderator

All replies

  • Question
    Sign in to vote
    0
    Sign in to vote
    TonyT,

    As the bug reporting process is semi-automated, in previous cases like this the recommended method is to post your summary here - along with the CAB file ID numbers.

    A couple of the Team read all posts, mainly Lara, and either they can pick up on your post, or a Mod can highlight it for them.

    Colin




    If anyone answers your query successfully, please mark it as 'Helpful', to guide other users.
    • Marked as answer by TonyT65 Friday, November 7, 2008 10:06 AM
    Thursday, November 6, 2008 7:33 PM
    Moderator
  • Question
    Sign in to vote
    0
    Sign in to vote
    Or you can try to join the WHS Beta program on Connect, as outlined in this thread.
    Here you can add information in text form to a bug report.
    Best greetings from Germany
    Olaf
    • Marked as answer by TonyT65 Friday, November 7, 2008 10:06 AM
    Thursday, November 6, 2008 8:43 PM
    Moderator
  • Question
    Sign in to vote
    0
    Sign in to vote
    You should do as Olaf has recommended and join the WHS "beta program" on Connect.
    I'm not on the WHS team, I just post a lot. :)
    • Marked as answer by TonyT65 Friday, November 7, 2008 10:06 AM
    Thursday, November 6, 2008 9:35 PM
    Moderator
  • Question
    Sign in to vote
    0
    Sign in to vote
    Thanks

    Have used the Connect board to reference my cab logs and provide background info
    I used the the PP1 Bug Report Form Feedback report. 

    Title is "SYS Drive Failing - Long Term Regular Error" dated 7/11/2008

    I hope to get to the bottom of this 14 day error cycle that has been around for a long time...

    Thanks for the direction.

    TonyT
    Friday, November 7, 2008 10:00 AM
  • Question
    Sign in to vote
    0
    Sign in to vote
    TonyT65 said:

    Thanks

    Have used the Connect board to reference my cab logs and provide background info
    I used the the PP1 Bug Report Form Feedback report. 

    Title is "SYS Drive Failing - Long Term Regular Error" dated 7/11/2008

    I hope to get to the bottom of this 14 day error cycle that has been around for a long time...

    Thanks for the direction.

    TonyT



    Hi Tony,

    I apologize for not catching this thread earlier. Connect is the preferred method so thanks for posting the report.  The bug has been assigned to a developer and we'll follow up with you via Connect or email.

    Regards,
    Lara Jones [MSFT] Windows Home Server Team
    Wednesday, November 12, 2008 9:25 PM
    Moderator
  • Question
    Sign in to vote
    0
    Sign in to vote
    Hi Lara

    Thx - but am curious as to the bug report having been changed this morning to "Closed - non reproducable error".

    I did provide feedback on the chkdsk log as requested - but the instructions as to how to do this exactly were unclear, so I added feedback as a comment to the bug report and attached the chkdsk log as requested.  Was this not the right method ???  Is this why it say "we have not heard from you in a few days and will be archiving this feedback - please open a new one if you have ongoing probs ..."?

    There are two ther bug reports in Connect for the same issue (repeating SYS Volume Failing cycle) that on inspection seem to reflect a similar result of quick closure without any resolution.

    Is that it...?  Am I to just assume that there is nothing further to be considered?  Happy to carry on sending CABs and logging new bug reports for this issue, but that would seem to be a waste.

    Rgds
    Tony
    Wednesday, November 12, 2008 11:21 PM
  • Question
    Sign in to vote
    0
    Sign in to vote
    TonyT65 said:

    Hi Lara

    Thx - but am curious as to the bug report having been changed this morning to "Closed - non reproducable error".

    I did provide feedback on the chkdsk log as requested - but the instructions as to how to do this exactly were unclear, so I added feedback as a comment to the bug report and attached the chkdsk log as requested.  Was this not the right method ???  Is this why it say "we have not heard from you in a few days and will be archiving this feedback - please open a new one if you have ongoing probs ..."?

    There are two ther bug reports in Connect for the same issue (repeating SYS Volume Failing cycle) that on inspection seem to reflect a similar result of quick closure without any resolution.

    Is that it...?  Am I to just assume that there is nothing further to be considered?  Happy to carry on sending CABs and logging new bug reports for this issue, but that would seem to be a waste.

    Rgds
    Tony



    Connect only parses the "Comments" section of the reports. This has to do with the way the feedback forms work and with the way our databases work.  It appears that the bug description section was updated. It can be confusing.

    In effect, we never saw this update :(

    I can send a message to the developer and let them know that you did answer their questions. 

    Thanks!
    Lara Jones [MSFT] Windows Home Server Team
    Thursday, November 13, 2008 3:03 AM
    Moderator