Unable to edit smb shares

TrueNAS General
,
1

Since upgading to 25.10 recently and the hotfix last night I realised today that I can no longer edit my samba shares, they are missing.

Had an image here, not allowed to attach it but it shows smb running with no shares and the placeholder text for samba shares

If I go to the datasets page and click the link to the share from there I see again no shares but a bright red stop sign with Cannot retrieve response

Here is the JS error from the console:

console.js:34 ApiCallError: Method call error - 3 validation errors for SmbShareQueryResult
result.list[SmbShareQueryResultItem].0.options.TIMEMACHINE_SHARE.timemachine_quota
Input should be less than or equal to 109951162777600 [type=less_than_equal, input_value=1048576000000000000, input_type=int]
For further information visit
result.SmbShareQueryResultItem
Input should be a valid dictionary or instance of SmbShareQueryResultItem [type=model_type, input_value=[{‘purpose’: 'TIMEMACHINE…alse}, ‘locked’: False}], input_type=list]
For further information visit
result.int
Input should be a valid integer [type=int_type, input_value=[{‘purpose’: 'TIMEMACHINE…alse}, ‘locked’: False}], input_type=list]
For further information visit
at api.service.ts:188:33

1 Like
2

Okay. That looks like another validation issue to fix for 25.10.1. Jira

1 Like
3

Is there any way to edit the broken one to fix the UI? Im guessing its the timemachine backup share with the huge size is the issue…

4

Commenting to follow this since I am getting the same message on TrueNaS scale 25.10.1 - Goldeye. Note that my SMB shares are still remotely accessible, I just cannot add/modify them from the Web admin interface.

Should I submit a bug report? or does that Jira ( that I don’t have access to view ) cover it?

Screenshot 2025-12-21 at 10.31.58 AM
Screenshot 2025-12-21 at 10.31.58 AM1648×516 18.9 KB

5

Can you PM me a debug from the system?

6

I opened Jira ticket NAS-139088 for this issue , with debug logs and screenshot attached.

1 Like
7

There is no system debug attached to the ticket and so it’s not actionable.

8

Weird, I checked the option to attach debug information when I submitted it. I’ll try again if I cannot attach the debug logs I manually.

Update

It allowed me to attached the debug logs! Let me know if you need any additional information or actions.

9

My Jira ticket is closed with the fix coming in 25.10.2. It appears that the root was that my Time Machine share quota was over the 7 TB limit , so it failed validation. That is probably a user error as I generally set the quote to twice the size of the drive I’m backing up, which would be 8 TB.

Now, I might need this much storage space for backups one day, but definitely not in the foreseeable future.

image
image410×659 32.6 KB

10

That’s 7 exabytes, not tebibytes. :wink:

2 Likes