StableBit DrivePool Log Collection

From Covecube - Wiki
Jump to: navigation, search

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 (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 because the files can be very large.

Upload 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.