This message was deleted.

I restarted other services and they also started failing

So following the steps at https://longhorn.io/kb/troubleshooting-volume-with-multipath fixed the issue? When a Longhorn volume is attached, it means it has been made available as a block device to the node. The next step is for the file system on the block device to be mounted into the container. However, multipathd running on the node may instead take control of the block device, preventing this mounting. As for why multipathd on your node just now started interacting with new Longhorn devices, it is not clear. Running the environment check script before installing Longhorn will warn you if multipathd is enabled on your nodes.

Yes. It fixed. Can it cause that to my nodes I added one more disk?