Can't Mount SMB

[sudodaemon]

Been using this since 0.12, never had this issue before. I went from 0.16 to 0.17 and that seems to have broken SMB.

I deleted everything, all backups, repositories, volumes. Went through the initial setup again and it will not connect to any of my SMB shares. I have verified IP's, and credentials are correct as I can connect from other computers. On every SMB connection it times out

2025-12-08 09:38:19


Started server: http://localhost:4096⁠
2025-12-08 09:38:20


<-- GET /api/v1/events
2025-12-08 09:38:20


info > Client connected to SSE endpoint
2025-12-08 09:38:20


--> GET /api/v1/events 200 4ms
2025-12-08 09:38:22


<-- GET /api/v1/events
2025-12-08 09:38:22


info > Client connected to SSE endpoint
2025-12-08 09:38:22


--> GET /api/v1/events 200 0ms
2025-12-08 09:38:36


<-- POST /api/v1/volumes
2025-12-08 09:38:36


error > SMB volume health check failed: ENOENT: no such file or directory, access '/var/lib/zerobyte/volumes/g3hzv/_data'
2025-12-08 09:38:36


warn > Path /var/lib/zerobyte/volumes/g3hzv/_data does not exist. Skipping unmount.
2025-12-08 09:38:36


info > Executing mount: mount -t cifs -o user=sudodaemon,pass=***,vers=3.0,port=445,uid=1000,gid=1000,domain=WORKGROUP //192.168.1.73/MiniPC /var/lib/zerobyte/volumes/g3hzv/_data
2025-12-08 09:38:41


error > Error mounting SMB volume {
2025-12-08 09:38:41


  "error": "SMB mount timed out after 5000ms"
2025-12-08 09:38:41


}
2025-12-08 09:38:41


--> POST /api/v1/volumes 201 5s
2025-12-08 09:38:41


<-- GET /api/v1/auth/me
2025-12-08 09:38:41


--> GET /api/v1/auth/me 200 3ms
2025-12-08 09:38:41


<-- GET /api/v1/volumes/69-server
2025-12-08 09:38:41


--> GET /api/v1/volumes/69-server 200 2ms
2025-12-08 09:38:41


<-- GET /api/v1/volumes/69-server
2025-12-08 09:38:41


--> GET /api/v1/volumes/69-server 200 3ms
2025-12-08 09:38:41


<-- GET /api/v1/system/info
2025-12-08 09:38:41


--> GET /api/v1/system/info 200 1ms
2025-12-08 09:38:41


mount: mounting //192.168.1.73/MiniPC on /var/lib/zerobyte/volumes/g3hzv/_data failed: Operation in progress
2025-12-08 09:38:41


warn > mount: mounting //192.168.1.73/MiniPC on /var/lib/zerobyte/volumes/g3hzv/_data failed: Operation in progress
2025-12-08 09:38:59


<-- POST /api/v1/volumes/test-connection
2025-12-08 09:38:59


error > SMB volume health check failed: Path /var/lib/zerobyte/volumes/test/_data is not mounted as CIFS/SMB.
2025-12-08 09:38:59


umount: can't unmount /var/lib/zerobyte/volumes/test/_data: Invalid argument
2025-12-08 09:38:59


warn > umount: can't unmount /var/lib/zerobyte/volumes/test/_data: Invalid argument
2025-12-08 09:38:59


error > Error unmounting SMB volume {
2025-12-08 09:38:59


  "path": "/var/lib/zerobyte/volumes/test/_data",
2025-12-08 09:38:59


  "error": "Mount command failed with exit code 1: umount: can't unmount /var/lib/zerobyte/volumes/test/_data: Invalid argument"
2025-12-08 09:38:59


}
2025-12-08 09:38:59


info > Executing mount: mount -t cifs -o user=sudodaemon,pass=***,vers=3.0,port=445,uid=1000,gid=1000,domain=WORKGROUP //192.168.1.73/MiniPC /var/lib/zerobyte/volumes/test/_data
2025-12-08 09:39:04


error > Error mounting SMB volume {
2025-12-08 09:39:04


  "error": "SMB mount timed out after 5000ms"
2025-12-08 09:39:04


}
2025-12-08 09:39:04


umount: can't unmount /var/lib/zerobyte/volumes/test/_data: Invalid argument
2025-12-08 09:39:04


warn > umount: can't unmount /var/lib/zerobyte/volumes/test/_data: Invalid argument
2025-12-08 09:39:04


error > Error unmounting SMB volume {
2025-12-08 09:39:04


  "path": "/var/lib/zerobyte/volumes/test/_data",
2025-12-08 09:39:04


  "error": "Mount command failed with exit code 1: umount: can't unmount /var/lib/zerobyte/volumes/test/_data: Invalid argument"
2025-12-08 09:39:04


}
2025-12-08 09:39:04


--> POST /api/v1/volumes/test-connection 200 5s
2025-12-08 09:39:04


<-- GET /api/v1/volumes/69-server
2025-12-08 09:39:04


--> GET /api/v1/volumes/69-server 200 1ms
2025-12-08 09:39:04


<-- GET /api/v1/system/info
2025-12-08 09:39:04


--> GET /api/v1/system/info 200 0ms
2025-12-08 09:39:04


mount: mounting //192.168.1.73/MiniPC on /var/lib/zerobyte/volumes/test/_data failed: Operation in progress
2025-12-08 09:39:04


warn > mount: mounting //192.168.1.73/MiniPC on /var/lib/zerobyte/volumes/test/_data failed: Operation in progress
2025-12-08 09:39:07


info > SIGTERM received, starting graceful shutdown...
2025-12-08 09:39:07


info > Scheduler stopped

[sudodaemon]

Docker Compose is as follows

services:
  zerobyte:
    image: ghcr.io/nicotsx/zerobyte:v0.17 
    container_name: zerobyte 
    restart: unless-stopped 
    cap_add:
      - SYS_ADMIN
    ports:
      - "4096:4096"
    devices:
      - /dev/fuse:/dev/fuse
    environment:
      - TZ=America/New_York
    volumes:
      - /etc/localtime:/etc/localtime:ro
      - /var/lib/zerobyte:/var/lib/zerobyte
      - /Volumes/BackUps:/mybackups
      - /Users/sudodaemon/Docker Containers:/iMac_Containers

[sudodaemon]

I moved ZeroByte from my iMac to a MiniPC that I have, and it all seems to be working there... Maybe something specific to my iMac? If you see something obvious in the logs I'm willing to troubleshoot more, if not, I'm just going to run this off my MiniPC

[nicotsx]

Hello @sudodaemon, this is most probably an issue with macos? I never was able to mount shares from a macos host. Weird that it was working before that. I didn't issue changes into how the mounting is performed between these versions: https://github.com/nicotsx/zerobyte/compare/v0.16.0...v0.17.0

[sudodaemon]

Weird, now that I have it up and running on my miniPC I'm going to install it back on my iMac to see what I can figure out. It was working, but for all we know a docker update or OS update broke something.

[eriknelson]

Just tried the project for the first time and I also couldn't mount an SMB. Issue was that the password contained a comma. I'm going to post a specific issue and I have a patch I'd like to contribute which uses a credentials file and resolves it, but thought I'd mention it for you in case that might be your issue. Running v0.18.0.