Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Network share has stopped working - Impossible to add a new one - homeassistant systemd[1]: Failed to mount Supervisor cifs mount #5589

Open
alexboss opened this issue Jan 30, 2025 · 0 comments
Labels

Comments

@alexboss
Copy link

alexboss commented Jan 30, 2025

Describe the issue you are experiencing

Dear Hassio team,

The network storage has stopped working all of a sudden (could be related to the update of OS 14.2 or Core 2025.1.4 but not sure about this).

And when I try to create a new network storage, it's impossible to mount.

See below and see also "Additional information" about the certificate change notification in Filezilla.

I'm using Hetzner storage box BX11 https://www.hetzner.com/storage/storage-box/ and have a Fritz!box 6660.

Any idea anyone?

Thank you and best regards.

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. Add a network storage
  2. Provide all details such as

Image

  1. Click "Connect"

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

From supervisor:

2025-01-30 09:10:55.253 INFO (MainThread) [supervisor.mounts.manager] Creating or updating mount: 20250129Hassio
2025-01-30 09:10:55.553 ERROR (MainThread) [supervisor.mounts.mount] Mounting 20250129Hassio did not succeed. Check host logs for errors from mount or systemd unit mnt-data-supervisor-mounts-20250129Hassio.mount for details.

----
From host using https://****.your-storagebox.de as server:

2025-01-30 08:32:38.857 homeassistant systemd[1]: Mounting Supervisor cifs mount: 20250129Hassio...
2025-01-30 08:32:42.105 homeassistant mount[337668]: mount error: could not resolve address for https:: Unknown error
2025-01-30 08:32:42.111 homeassistant systemd[1]: mnt-data-supervisor-mounts-20250129Hassio.mount: Mount process exited, code=exited, status=1/FAILURE
2025-01-30 08:32:42.111 homeassistant systemd[1]: mnt-data-supervisor-mounts-20250129Hassio.mount: Failed with result 'exit-code'.
2025-01-30 08:32:42.112 homeassistant systemd[1]: Failed to mount Supervisor cifs mount: 20250129Hassio.

----
From host using ****.your-storagebox.de as server:

2025-01-30 08:35:35.862 homeassistant systemd[1]: Mounting Supervisor cifs mount: 20250129Hassio...
2025-01-30 08:35:35.906 homeassistant kernel: CIFS: Attempting to mount //xxxx.your-storagebox.de/backups/hassio
2025-01-30 08:35:36.234 homeassistant kernel: CIFS: VFS:  BAD_NETWORK_NAME: \\xxxx.your-storagebox.de\backups
2025-01-30 08:35:36.274 homeassistant kernel: CIFS: VFS: cifs_mount failed w/return code = -2
2025-01-30 08:35:36.274 homeassistant mount[338346]: mount error(2): No such file or directory
2025-01-30 08:35:36.274 homeassistant mount[338346]: Refer to the mount.cifs(8) manual page (e.g. man mount.cifs) and kernel log messages (dmesg)
2025-01-30 08:35:36.275 homeassistant systemd[1]: mnt-data-supervisor-mounts-20250129Hassio.mount: Mount process exited, code=exited, status=32/n/a
2025-01-30 08:35:36.275 homeassistant systemd[1]: mnt-data-supervisor-mounts-20250129Hassio.mount: Failed with result 'exit-code'.
2025-01-30 08:35:36.276 homeassistant systemd[1]: Failed to mount Supervisor cifs mount: 20250129Hassio.

----
From host using smb://****.your-storagebox.de as server:

2025-01-30 08:34:57.040 homeassistant systemd[1]: Mounting Supervisor cifs mount: 20250129Hassio...
2025-01-30 08:35:00.357 homeassistant mount[338181]: mount error: could not resolve address for smb:: Unknown error
2025-01-30 08:35:00.362 homeassistant systemd[1]: mnt-data-supervisor-mounts-20250129Hassio.mount: Mount process exited, code=exited, status=1/FAILURE
2025-01-30 08:35:00.363 homeassistant systemd[1]: mnt-data-supervisor-mounts-20250129Hassio.mount: Failed with result 'exit-code'.
2025-01-30 08:35:00.363 homeassistant systemd[1]: Failed to mount Supervisor cifs mount: 20250129Hassio.

System Health information

System Information

version core-2025.1.4
installation_type Home Assistant OS
dev false
hassio true
docker true
user root
virtualenv false
python_version 3.13.1
os_name Linux
os_version 6.6.62-haos-raspi
arch aarch64
timezone Europe/Luxembourg
config_dir /config
Home Assistant Community Store
GitHub API ok
GitHub Content ok
GitHub Web ok
HACS Data ok
GitHub API Calls Remaining 5000
Installed Version 2.0.5
Stage running
Available Repositories 1500
Downloaded Repositories 5
AccuWeather
can_reach_server ok
remaining_requests 25
Home Assistant Cloud
logged_in false
can_reach_cert_server ok
can_reach_cloud_auth ok
can_reach_cloud ok
Home Assistant Supervisor
host_os Home Assistant OS 14.2
update_channel stable
supervisor_version supervisor-2024.12.3
agent_version 1.6.0
docker_version 27.2.0
disk_total 116.9 GB
disk_used 34.1 GB
healthy true
supported true
host_connectivity true
supervisor_connectivity true
ntp_synchronized true
virtualization
board rpi4-64
supervisor_api ok
version_api ok
installed_addons Studio Code Server (5.18.1), motionEye (0.21.0), Mosquitto broker (6.5.0), Samba share (12.4.0), Advanced SSH & Web Terminal (20.0.0), Piper (1.5.2), Whisper (2.4.0), MySmartmeter2mqtt (1.7.0-beta.9), File editor (5.8.0), Tailscale (0.24.0), Signal Messenger (0.91.0), SQLite Web (4.3.0), Firefox (1.4.0)
Dashboards
dashboards 4
resources 0
views 4
mode storage
Miele
component_version 2025.1.1
reach_miele_cloud ok
Recorder
oldest_recorder_run 18 January 2025 at 10:06
current_recorder_run 29 January 2025 at 10:40
estimated_db_size 1657.53 MiB
database_engine sqlite
database_version 3.47.1

Supervisor diagnostics

config_entry-hassio-88dcb652f8aab6f8b7a28deacdf0daae.json

Additional information

Not sure it is important but just in case. When I connected to the storage box using Filezilla, there was a warning indicating the certificate has changed, and asked me to validate the new certificate.

@alexboss alexboss added the bug label Jan 30, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant