possible issue when NFS computer shuts down before HAOS?

[Anto79-ops]

Describe the issue you are experiencing

Hello!

I'm currently running HAOS(13.1) on a Nuc12 bare metal. I also have a seperate Ubuntu 22.04-based PC (on the same network) that I use for other things like Ollama, Music Assistant, Glances, and NUT as integrations.

I also use the Ubuntu PC as a NFS to store my HA backups.

I want to mention an issue, that I believe may be related to Supervisor and the NFS fileshare.

Its happened a few times where I have to gracefully shutdown these two systems because of a planned power outage. However, if I turn off the Ubuntu computer first, something strange happens to my HAOS system on the NUC.

First, I cannot shutdown HAOS because the option goes missing, like this:

Second, I cannot start or open any of the addons in HAOS, they simply just stall or don't load. For example, since the option to shutdown was missing from GUI, I thought I could just try doing it in the CLI via the terminal addon, but the addon could not start. At this point I was stuck and the only way to shutdown HAOS was pressing the power button.

however, I soon relized that if I turned the Ubuntu computer back on, HAOS returned to normal, and I was able to shutdown HAOS using the GUI because the option was back (and all the addon loaded normally, with no stalling).

So for my system, I need to shutdown HAOS first, then the Ubuntu computer.

Is this intended? and is this because I have a file share mounted on that computer?

Currently, have:

Core 2024.9.1
Supervisor 2024.09.0
Operating System 13.1
Frontend 20240906.0

But its also happend once in July (I always update)

thanks

What type of installation are you running?

Home Assistant OS

Which operating system are you running on?

Home Assistant Operating System

Steps to reproduce the issue

1. Turn off the computer that has NFS (Ubuntu 22.04) on it, while HAOS is still running

...

Anything in the Supervisor logs that might be useful for us?

didnt get those yet

System Health information

no repairs

Supervisor diagnostics

No response

Additional information

No response

[github-actions]

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates.
Please make sure to update to the latest version and check if that solves the issue. Let us know if that works for you by adding a comment 👍
This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.

[Anto79-ops]

hi, still here, thanks

[github-actions]

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates.
Please make sure to update to the latest version and check if that solves the issue. Let us know if that works for you by adding a comment 👍
This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.

[Anto79-ops]

Thanks.

[github-actions]

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates.
Please make sure to update to the latest version and check if that solves the issue. Let us know if that works for you by adding a comment 👍
This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.

[Anto79-ops]

Hi