Kubernetes porworx node down "Online (StorageDown) Full or Offline"

Portworx on Kubernetes
1 
Status: PX is operational
Telemetry: Disabled or Unhealthy
License: PX-Enterprise IBM Cloud DR (expires in 366 days)
Node ID: 0a8c7060-e907-41fb-be0e-3c16cf8bfaff
	IP: 10.183.233.47 
 	Local Storage Pool: 0 pool
	POOL	IO_PRIORITY	RAID_LEVEL	USABLE	USED	STATUS	ZONE	REGION
	No storage pool
	Local Storage Devices: 0 device
	Device	Path	Media Type	Size		Last-Scan
	No storage device
	total		-	0 B
	Cache Devices:
	 * No cache devices
Cluster Summary
	Cluster ID: dsgprodv1
	Cluster UUID: 22bcd9d7-0312-4ced-b5ae-f00f0cc1ad6a
	Scheduler: kubernetes
	Nodes: 3 node(s) with storage (2 online), 3 node(s) without storage (3 online)
	IP		ID					SchedulerNodeName	Auth		StorageNode	Used	Capacity	Status			StorageStatus		Version		Kernel			OS
	10.190.86.245	c7c83ac9-b528-46bc-8328-c4cf4032b3cf	10.190.86.245		Disabled	Yes		0 B	0 B		Online (StorageDown)	Full or Offline		2.9.0.0-32303a6	4.15.0-167-generic	Ubuntu 18.04.6 LTS
	10.183.233.57	87eb73b2-4880-4cc3-9677-4656ada35d90	10.183.233.57		Disabled	Yes		1.1 TiB	10 TiB		Online			Up		2.9.0.0-32303a6	4.15.0-167-generic	Ubuntu 18.04.6 LTS
	10.188.129.209	28527401-7cc0-4350-ab69-5e3421b7b04d	10.188.129.209		Disabled	Yes		1.2 TiB	10 TiB		Online			Up		2.9.0.0-32303a6	4.15.0-167-generic	Ubuntu 18.04.6 LTS
	10.188.129.206	b730414e-896e-4025-8333-3340ab03a81c	10.188.129.206		Disabled	No		0 B	0 B		Online			No Storag2.9.0.0-32303a6	4.15.0-167-generic	Ubuntu 18.04.6 LTS
	10.190.86.236	43aa24cf-89b9-42aa-8aa4-96d51956ad19	10.190.86.236		Disabled	No		0 B	0 B		Online			No Storag2.9.0.0-32303a6	4.15.0-167-generic	Ubuntu 18.04.6 LTS
	10.183.233.47	0a8c7060-e907-41fb-be0e-3c16cf8bfaff	10.183.233.47		Disabled	No		0 B	0 B		Online			No Storage (This node)	2.9.0.0-32303a6	4.15.0-167-generic	Ubuntu 18.04.6 LTS
Global Storage Pool
	Total Used    	:  2.2 TiB
	Total Capacity	:  21 TiB

Do you know how can I fix this?

2

Below options you can bring back the node back online, See which one will suit for you.

Option 1: You can relocate volume presence by move their replicas around between nodes manually, using pxctl volume ha-update (please check the usage, you need to specify --node with a nodeID (available in output of pxctl status ) when raising or lowering the repl number (so decrease it off a node, then increase it onto another node with more space)

Option 2: you can check the cluster options and see if you can free up some space on the cluster level. which will enable the node come online.
pxctl cluster options update --free-space-threshold-gb 50
pxctl cluster options update --free-space-threshold-gb 10

Option 3: INcrease the pool size on the node by adding additional disk on the node. Adding storage to existing Portworx Cluster Nodes