Difference between revisions of "StableBit DrivePool Log Collection"

From Covecube - Wiki
 
(3 intermediate revisions by the same user not shown)
Line 2: Line 2:
  
 
All log files are written under ''C:\ProgramData\StableBitDrivePool\Service\Logs'' on the sever.
 
All log files are written under ''C:\ProgramData\StableBitDrivePool\Service\Logs'' on the sever.
−
 
−
''This is a new feature as of BETA M2''
 
  
 
''Be aware that if you try to read the log files yourself, you may see many warning messages. These by themselves do not indicate a problem. The Win32 API expects many functions to fail. For example, many applications will check whether a file exists or not by trying to open it, so it is perfectly normal for that to error out.''
 
''Be aware that if you try to read the log files yourself, you may see many warning messages. These by themselves do not indicate a problem. The Win32 API expects many functions to fail. For example, many applications will check whether a file exists or not by trying to open it, so it is perfectly normal for that to error out.''
Line 12: Line 10:
  
 
# Open the Windows Home Server 2011 Dashboard.
 
# Open the Windows Home Server 2011 Dashboard.
−
# Select the 'StableBit DrivePool' tab.
+
# Open 'Server settings'.
−
# Click 'About StableBit DrivePool' in the tasks list on the right.
+
# Select 'DrivePool'.
−
# Make sure 'Enable logging' is ''Checked''.
+
# Make sure 'Enable tracing' is ''Checked''.
−
#:[[File:DrivePool_enable_logging.png]]
 
 
# Reproduce your error by copying / opening a file.
 
# Reproduce your error by copying / opening a file.
−
# After you see the error, go back and ''Uncheck'' 'Enable logging'. This will flush all logs to disk and stop logging.
+
# After you see the error, go back and ''Uncheck'' 'Enable tracing'. This will flush all logs to disk and stop logging.
−
#:[[File:DrivePool_disable_logging.png]]
 
 
# Log into the home server using remote desktop with the 'Administrator' account.
 
# Log into the home server using remote desktop with the 'Administrator' account.
 
# Open 'C:\ProgramData\StableBitDrivePool' in Windows Explorer.
 
# Open 'C:\ProgramData\StableBitDrivePool' in Windows Explorer.
Line 24: Line 20:
 
#:[[File:drivepool_zip_service_folder.png]]
 
#:[[File:drivepool_zip_service_folder.png]]
 
# Upload the resulting zip file using the form below with a short description explaining the problem.
 
# Upload the resulting zip file using the form below with a short description explaining the problem.
−
# You can optionally open a support contact thread at [http://stablebit.com/contact http://stablebit.com/contact].
+
# You can optionally open a support contact thread at [http://stablebit.com/contact http://stablebit.com/contact] (don't attach the logs to the contact thread as they can be very large).
  
 
== Upload the log ==
 
== Upload the log ==
Line 34: Line 30:
 
Describe how you encountered the error.
 
Describe how you encountered the error.
  
−
'''If known, note the exact time that the error occurred in the description below.'''
+
[https://www.dropbox.com/request/8Qn4E3AXpSezhOq1DaL6 Click here to submit files with Dropbox (you don't need an account with Dropbox)]
−
 
 
−
<wikiscript src="https://www.box.net/embed/upload.js?token=smfthb45faqdniae7ghdbfd3ukl6f6af&folder_id=85721072&w=385&h=385&i=&d=1&t=StableBit%20DrivePool%20Logs&r=0" type="text/javascript"></wikiscript>
 
  
 
''Logs are only used to fix bugs in StableBit DrivePool and for no other purpose.''
 
''Logs are only used to fix bugs in StableBit DrivePool and for no other purpose.''

Latest revision as of 02:28, 25 May 2016

DrivePool features advanced kernel logging that can record every I/O operation performed on the pool. In addition, the StableBit DrivePool service performs high level logging of its operation.

All log files are written under C:\ProgramData\StableBitDrivePool\Service\Logs on the sever.

Be aware that if you try to read the log files yourself, you may see many warning messages. These by themselves do not indicate a problem. The Win32 API expects many functions to fail. For example, many applications will check whether a file exists or not by trying to open it, so it is perfectly normal for that to error out.

Collect a log

If you experience a problem with copying a file or reading data from the pool:

  1. Open the Windows Home Server 2011 Dashboard.
  2. Open 'Server settings'.
  3. Select 'DrivePool'.
  4. Make sure 'Enable tracing' is Checked.
  5. Reproduce your error by copying / opening a file.
  6. After you see the error, go back and Uncheck 'Enable tracing'. This will flush all logs to disk and stop logging.
  7. Log into the home server using remote desktop with the 'Administrator' account.
  8. Open 'C:\ProgramData\StableBitDrivePool' in Windows Explorer.
  9. ZIP up the 'Service' Sub folder.
    Drivepool zip service folder.png
  10. Upload the resulting zip file using the form below with a short description explaining the problem.
  11. You can optionally open a support contact thread at http://stablebit.com/contact (don't attach the logs to the contact thread as they can be very large).

Upload the log

You should not attach log files to a contact message at http://stablebit.com/contact because the files can be very large.

Upload Server.zip below.

Describe how you encountered the error.

Click here to submit files with Dropbox (you don't need an account with Dropbox)

Logs are only used to fix bugs in StableBit DrivePool and for no other purpose.

Thank you

Thank you for taking the time to submit a detailed log file of your problem. The log files help us fix bugs quicker.

Retrieved from "https://wiki.covecube.com/index.php?title=StableBit_DrivePool_Log_Collection&oldid=889"