Disconnected mapped network drives return an error on Windows

[dharley-atlastix]

Describe the bug
When enumerating partitions, if a mapped network is in the disconnected state the following error (warning) will be returned:
Error 0: The network path was not found.

To Reproduce

1. Map a network drive from a client to a server. When you run the following code, the remote drive will be returned.
2. Disconnect the network between the client and server. When you run the following code, the error listed above will be returned.

package main

import (
	"fmt"

	"github.com/shirou/gopsutil/v4/disk"
)

func main() {
	v, err := disk.Partitions(true)
	fmt.Println("errors:", err)
	fmt.Println("values:", v)
}

Expected behavior
Ideally a network drive would return a disconnected state flag. However, as there is already precedence that ejectable devices can be missing it might be worth adding type 4 devices (DRIVE_REMOTE) to this group.

gopsutil/disk/disk_windows.go

Lines 135 to 138 in 262afcf

	if driveret == 0 {
	if typeret == 5 || typeret == 2 {
	continue // device is not ready will happen if there is no disk in the drive
	}

Environment (please complete the following information):

• Windows: Microsoft Windows [Version 10.0.20348.587
• Linux: [paste contents of /etc/os-release and the result of uname -a]
• Mac OS: [paste the result of sw_vers and uname -a
• FreeBSD: [paste the result of freebsd-version -k -r -u and uname -a]
• OpenBSD: [paste the result of uname -a]

[shirou]

fixed by #1699. Thank you for your report!