# Metricbeat 7.11.1 fail in system fsstat and filesystem: The device is not ready **URL:** \ **Category:** Beats\ **Tags:** metricbeat\ **Created:** [February 26, 2021, 1:04pm UTC](https://discuss.elastic.co/t/metricbeat-7-11-1-fail-in-system-fsstat-and-filesystem-the-device-is-not-ready/265613 "2021-02-26T13:04:09Z")\ **Posts on this page:** 10\ **Page:** 1
**Author:** ![Sommerdal](https://avatars.discourse-cdn.com/v4/letter/s/bc8723/32.png) [@Sommerdal](https://discuss.elastic.co/u/Sommerdal)\ **Post date:** [February 26, 2021, 1:04pm UTC](https://discuss.elastic.co/t/metricbeat-7-11-1-fail-in-system-fsstat-and-filesystem-the-device-is-not-ready/265613/1 "2021-02-26T13:04:09Z")
I keep getting this: module/wrapper.go:259 Error fetching data for metricset system.fsstat: filesystem list: GetFilesystemType failed: GetVolumeInformationW failed: The device is module/wrapper.go:259 Error fetching data for metricset system.filesystem: error getting filesystem list: GetFilesystemType failed: GetVolumeInformationW failed: The device is not ready. The enviroment is: agent.type metricbeat agent.version 7.11.1 ecs.version 1.7.0 error.message error getting filesystem list: GetFilesystemType failed: GetVolumeInformationW failed: The device is not ready. event.dataset system.filesystem event.module system host.architecture x86\_64 host.os.build 9600.19542 host.os.family windows host.os.kernel 6.3.9600.19538 (winblue\_ltsb\_escrow.191014-1700) host.os.name Windows Server 2012 R2 Standard host.os.platform windows host.os.version 6.3 metricset.name filesystem service.type system ---
**Author:** ![anderssonjohan](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/anderssonjohan/32/60037_2.png) [@anderssonjohan](https://discuss.elastic.co/u/anderssonjohan)\ **Post date:** [February 26, 2021, 2:05pm UTC](https://discuss.elastic.co/t/metricbeat-7-11-1-fail-in-system-fsstat-and-filesystem-the-device-is-not-ready/265613/2 "2021-02-26T14:05:00Z")
We also have this issue when upgrading from 7.10 to 7.11. The reason is this change to metricbeat: [[Metricbeat] Filesystem Metricset: Inconsistent `system.filesystem.type` values on Windows · Issue #22501 · elastic/beats · GitHub](https://github.com/elastic/beats/issues/22501) The change adds a call to Kernel32.GetVolumeInformationW to all drives on the system, but this will fail for certain drive types. For example, on our system we get the drives A:\ C:\ D:\ L:\ where A is a floppy and D is a CD-ROM. Both these two returns false when calling GetVolumeInformationW and that will stop metricbeat from working. Right now you can only ignore certain filesystem types, but that filter will be applied on the result from making the syscall. Since the syscall fails, metricbeat stops reporting filesystem metrics. ---
**Author:** ![anderssonjohan](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/anderssonjohan/32/60037_2.png) [@anderssonjohan](https://discuss.elastic.co/u/anderssonjohan)\ **Post date:** [February 26, 2021, 2:24pm UTC](https://discuss.elastic.co/t/metricbeat-7-11-1-fail-in-system-fsstat-and-filesystem-the-device-is-not-ready/265613/3 "2021-02-26T14:24:58Z")
I posted a script here that confirms the issue on our system: > When the GetVolumeInformationW returns false/error it will get to this line: > ---
**Author:** ![Sommerdal](https://avatars.discourse-cdn.com/v4/letter/s/bc8723/32.png) [@Sommerdal](https://discuss.elastic.co/u/Sommerdal)\ **Post date:** [March 1, 2021, 11:44am UTC](https://discuss.elastic.co/t/metricbeat-7-11-1-fail-in-system-fsstat-and-filesystem-the-device-is-not-ready/265613/4 "2021-03-01T11:44:04Z")
Downgrading to mb 7.10 solved the problem. Thx ---
**Author:** ![swtrux](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/swtrux/32/146347_2.png) [@swtrux](https://discuss.elastic.co/u/swtrux)\ **Post date:** [March 11, 2021, 8:12pm UTC](https://discuss.elastic.co/t/metricbeat-7-11-1-fail-in-system-fsstat-and-filesystem-the-device-is-not-ready/265613/5 "2021-03-11T20:12:11Z")
I am experiencing the same issue and although you have found the cause there does not seem to be a solution/workaround other than downgrading to 7.10. Is there a bug open on this issue? ---
**Author:** ![anderssonjohan](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/anderssonjohan/32/60037_2.png) [@anderssonjohan](https://discuss.elastic.co/u/anderssonjohan)\ **Post date:** [March 11, 2021, 8:38pm UTC](https://discuss.elastic.co/t/metricbeat-7-11-1-fail-in-system-fsstat-and-filesystem-the-device-is-not-ready/265613/6 "2021-03-11T20:38:42Z")
@swtrux Yes, the original issue was re-opened and a fix was posted yesterday. Please see this comment [[Metricbeat] Filesystem Metricset: Inconsistent `system.filesystem.type` values on Windows · Issue #22501 · elastic/beats · GitHub](https://github.com/elastic/beats/issues/22501#issuecomment-795255969) ---
**Author:** ![swtrux](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/swtrux/32/146347_2.png) [@swtrux](https://discuss.elastic.co/u/swtrux)\ **Post date:** [March 11, 2021, 9:03pm UTC](https://discuss.elastic.co/t/metricbeat-7-11-1-fail-in-system-fsstat-and-filesystem-the-device-is-not-ready/265613/7 "2021-03-11T21:03:55Z")
Thanks for the quick response, that is great news. So at this time from what I can tell they have a fix but still have not disclosed what version the fix will be in. Is that true? ---
**Author:** ![swtrux](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/swtrux/32/146347_2.png) [@swtrux](https://discuss.elastic.co/u/swtrux)\ **Post date:** [March 23, 2021, 5:41pm UTC](https://discuss.elastic.co/t/metricbeat-7-11-1-fail-in-system-fsstat-and-filesystem-the-device-is-not-ready/265613/8 "2021-03-23T17:41:48Z")
7.12.0 dropped today and it looks like the fix DID NOT make it in. ---
**Author:** ![Aymeric\_Caroff](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/aymeric_caroff/32/86152_2.png) [@Aymeric\_Caroff](https://discuss.elastic.co/u/Aymeric_Caroff)\ **Post date:** [April 19, 2021, 8:04pm UTC](https://discuss.elastic.co/t/metricbeat-7-11-1-fail-in-system-fsstat-and-filesystem-the-device-is-not-ready/265613/9 "2021-04-19T20:04:16Z")
I'm wondering why the Github issue got closed since it's been confirmed that the error is still present in 7.12.0. I hope we are not dropping the ball here, there's still a bunch of Windows VMs out there 😄. ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [May 17, 2021, 10:04pm UTC](https://discuss.elastic.co/t/metricbeat-7-11-1-fail-in-system-fsstat-and-filesystem-the-device-is-not-ready/265613/10 "2021-05-17T22:04:54Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.