Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[check_drivesize] Filter processing failed: Error: Failed to get size for: 87: Falscher Parameter. #276

Closed
ghost opened this issue Apr 6, 2016 · 8 comments

Comments

@ghost
Copy link

ghost commented Apr 6, 2016

I have a problem with the check_drivesize command.

From time to time the check throws the following error which results in an unknow state.

Filter processing failed: Error: Failed to get size for: 87: Falscher Parameter.

However, after some time the problem disappears and the drive can be checked correctly.

@mickem
Copy link
Owner

mickem commented Apr 6, 2016

Is there any errors in the log file?

@mickem
Copy link
Owner

mickem commented Apr 7, 2016

Try the new 38 build and let me know what the message says should report the actual drive now instead of "empty"

@mickem
Copy link
Owner

mickem commented Apr 8, 2016

Is it possible to test the new build and provide the error message?

@ghost
Copy link
Author

ghost commented Apr 8, 2016

Sorry for the delayed response. A colleague will check the 50 build on Monday. I will get back to you as soon as I can get anything.

@prime07
Copy link

prime07 commented May 18, 2016

Hello,

same problem here, log file says:

_2016-05-18 09:11:46: error:c:\source\nscp\modules\CheckDisk\check_drive.cpp:432: Failed to get volume information ?\Volume{6d1acf4d-739f-11e2-9295-806e6f6e6963}: 87: Falscher Parameter.

It is possible to solve the problem by deactivating the floppy drive.

@mickem
Copy link
Owner

mickem commented May 30, 2016

For floppys (and other removable drives) I can resolve the problem using the following command:

check_drivesize "filter=removable = 1"

@ghost
Copy link
Author

ghost commented Aug 18, 2016

A quick update for you: We have been running the 50 version for quite some time. However, the error has not occurred.

I suggest we close this ticket and I reopen it when the error occurs again.

@mickem
Copy link
Owner

mickem commented Aug 22, 2016

sound good...

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants