1.54 smb stopped working

Operating System ZimaOS
1

Hi everyone,

Is anyone else running into issues with SMB shares after updating to v1.54?

Ever since the update, I’ve been completely unable to connect to my NAS. Every time I try to map the drive or access the share, I get the following error:

“operation not supported”

This is a major headache for me because I use this connection to run backups to my NAS over my local network (LAN). Since the NAS doesn’t use HTTPS, I’m strictly dependent on a stable SMB connection. It was working perfectly on the previous version, and nothing has changed in my network configuration or NAS settings.

Has anyone found a workaround, or is there a way to roll back the SMB client settings? I’d love to know if this is a widespread bug or if there’s a new security toggle I need to flip.

Thanks in advance for any help!

ZVM and access to host (specifically shares)
2

Yes, this has come up after 1.5.4.

Most cases are not a full SMB break. v1.5.4 added “Pause Sharing”, and some shares end up stopped after the upgrade. When that happens, Windows throws “operation not supported”.

Quick checks:

  • Go to Files → Shared Folders and confirm the share is active, not paused
  • Remove the mapped drive on the client, clear saved credentials, reconnect using \\IP\share
  • Try accessing the share from another client or via the Files app (server-side)

If Files works locally but clients fail, it’s almost always a paused share or SMB negotiation issue, not your data.

1 Like
3

Thank you so much for your quick reply.

Unfortunately it’s the other way round. ZimaOS throws “operation not supported” when I’m trying to mount my NAS in Files on ZimaOS.

image
image799×444 14.3 KB

Also Backupapp

image
image1323×679 49.9 KB

EDIT: I did toggle SMB back and forth in settings and tried all possible combinations of (un)toggled options.

4

Run these on ZimaOS.

1) Check kernel SMB support (quick sanity)

lsmod | grep cifs

If nothing returns → that’s a bug.

2) Try a manual SMB probe (no mount)

smbclient -L 192.168.178.113 -U admin
  • If this fails → SMB client regression
  • If this works → UI mount path is broken

3) Check Files / mount errors

dmesg | tail -50 | grep -i cifs

4) Check system logs around mount

journalctl -xe | grep -i smb

These commands don’t change anything and will clearly show whether:

  • CIFS is broken
  • Auth/negotiation fails
  • The Files app mount wrapper is erroring

If you post the output of 2 + 3, it’s enough to confirm a 1.5.4 bug.

1 Like
5

2)

smb1

image
image933×269 30.9 KB

without smb1

image
image933×258 28.9 KB

3)

image
image933×421 79.2 KB

6

Any chance I can roll back to 1.53?

7

This is not authentication and not a UI issue.
It’s a protocol mismatch introduced in ZimaOS 1.5.4.

Key log line:

CIFS: VFS: Dialect not supported by server … return code = -95

What this means:

  • Your NAS only supports older SMB dialects (SMB1 / early SMB2)
  • ZimaOS 1.5.4 now defaults to newer SMB dialects
  • The Files / Backup UI does not expose vers=, so the mount fails with “operation not supported”

That’s why:

  • smbclient can list shares successfully
  • Files / Backup cannot mount them

Rollback note:

  • There is no supported in-place downgrade from 1.5.4 > 1.5.3
  • Downgrading requires a full reinstall
  • Back up all data first before attempting a downgrade

Status summary:

  • Confirmed SMB client regression in 1.5.4
  • Deterministic failure against NAS devices requiring SMB1 / early SMB2
  • Needs either:
    • a vers= selector in Files, or
    • restored legacy SMB dialect fallback
1 Like
8

Thank you!
That’s too bad. Shouldn’t have upgraded just yet.