Welcome to Communities.
Please note that this is an English-language sub-forum and thus you should take the few seconds to use a translator tool before posting (or of course, post in a native language sub-forum e.g. Spanish )
Can you share a screenshot of the exact error message? I ask as translator potentially mangled the key points.
Are you getting "msg.disklib.UNSUPPORTEDFEATURE"?
If so then potentially it is the below issue which is easily confirmed and resolved:
Here is another useful resource for different reasons disk extend might fail:
"should I do it off?"
If you have a non-critical VM to test this on or if the issue is reproducible with a test VM then sure, try this to confirm what will or not work.
"Why does it work with machines that are not in cluster?"
You could potentially be comparing apples to oranges e.g. all Linux OS with shared storage and Multiwriter in cluster and all Windows OS with no shared disks outside of cluster - only you can answer this question really.
Again...please just copy+paste the error messages and use translate - asking others to manually type a foreign language into a translator from a screenshot is not a reasonable way to ask for assistance - please put in some effort.
It looks like it is complaining about hot-extend only being applicable for disks of types other than what you are using so cold-extend (VM powered-off) may be an option here. Are these persistent or non-persistent disks? Do these disks have snapshots on them?(don't look at snapshot manager for this, Right-click VM > Edit Settings > Hard Disk X > Look at the path, if it ends in -00000X.vmdk then you have snapshots - consolidate these then retry the extend).
The machine ends up on \disk_5.vmdk so it doesn't have snapshots.
disk mode indicates: dependent
Storage directive: vm profile erasure code r5
"Windows server 2012 r2 and is a file server with two nodes"
Are you indicating that the backing disks are shared with more than one VM?
The above error messages indicate that hot-extend isn't supported on the disks you are trying to extend so first thing should be to confirm that you can actually extend disks while VMs are powered off and then figure out is down-time for the rest of VMs that need extended a tenable option or figure out whether hot-extend is possible at all based on the configuration (and potentially history) of the VM and its backing storage. As an aside, I don't see anything vSAN-specific relating to this issue so consider asking a moderator to move this thread to vSphere/Storage sub-community for more visibility and thus potentially more ideas.
a moderator could help me move my question to vSphere/Storage sub-community please? thank you very much.