Volumes: red dot but mounted

[mononym]

Hello.
In the Volumes interface, my sshfs volumes are indicated with a red dot: "Could not determine mount failure reason". Remounting also does not turn the dot green. But I can flawlessly access the File Browser and rely on the data in their relative apps.
Don't know if this appeared after the latest update. Current Platform Version v8.1.0 (Ubuntu 20.04.4 LTS)

[joseph]

@mononym Can you run this on your server?

systemctl status mnt-volumes-8aa128f595aa40f99f8aa6d4b7c1bed2.mount

The 8aa128f595aa40f99f8aa6d4b7c1bed2 above is the volume id. You can get volume id from the url of the volume's file manager.

[mononym]

● mnt-volumes-xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx.mount - volume-name
     Loaded: loaded (/etc/systemd/system/mnt-volumes-xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx.mount; enabled; vendor preset>
     Active: failed (Result: exit-code) since Fri 2024-11-22 18:31:09 UTC; 5 days ago
      Where: /mnt/volumes/xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
       What: account@address.of.external.storage:/folder
      Tasks: 13 (limit: 9425)
     Memory: 2.8M
     CGroup: /system.slice/mnt-volumes-xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx.mount
             ├─    892 sshfs account@address.of.external.storage:/folder /mnt/volumes/xxxxxxxxxxxxxxxxxxxxxxxxxxx>
             └─2279000 ssh -x -a -oClearAllForwardings=yes -oport=23 -oIdentityFile=/home/yellowtent/platformdata/s>

Warning: journal has been rotated since unit was started, output may be incomplete.

[nebulon]

Can you also try to remount this via systemctl restart mnt-volumes-xxxxx.mount and then also check the logs from journalctl --system as well as journalctl -u mnt-volumes-xxxxx.mount ?