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

Feature Request: Invoke-IcingaCheckUsedPartitionSpace not listing all physical disks #417

Open
Captain-Abi opened this issue Aug 19, 2024 · 1 comment
Labels
Investigation The team is looking into the cause of the issue

Comments

@Captain-Abi
Copy link

on our servers we use the possibility to "mount" a physical disk into an empty ntfs folder.

the used space of those disks ist not shown by the powershell check, but from the old deprecated check_disk.

to reproduce the issue take a vm, install windows with default-settings. create an new folder somewhere on the harddrive, e.g. C:\mountpoint
image

insert a second harddrive into the vm, initialize it with gpt partition table. create a new basic volume, assign the new partition not with a drive letter, mount it into your created folder C:\mountpoint
image

i attach screenshots of an example machine to compare the old check_disk and Invoke-IcingaCheckUsedPartitionSpace.

  • check_disk
    Plugin Output:
    DISK WARNING - free space:C:\ 12344 MB (31%); C:\mountpoint\ 5080 MB (100%); D:\ 4050 MB (79%); D:\EBE\ 22281 MB (47%); D:\EBE_T\ 2432 MB (48%); D:\PFU\ 1529 MB (12%); D:\PFU_T\ 1977 MB (39%); D:\ROT\ 8334 MB (24%); D:\ROT_T\ 1857 MB (36%);
    Performance Data:
    image

-Invoke-IcingaCheckUsedPartitionSpace
Plugin Output:
Used Partition Space: 2 Ok (All must be )
_ Partition C: 69.40% (27.34GiB)
_ Partition D: 20.62% (1.03GiB)
Performance Data:
image

@LordHepipud LordHepipud added the Investigation The team is looking into the cause of the issue label Aug 30, 2024
@tectumopticum
Copy link

using „Win32_LogicalDisk“ instead of „Win32_Volume“ as data-collector might be more useful?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Investigation The team is looking into the cause of the issue
Projects
None yet
Development

No branches or pull requests

3 participants