Register for the iXsystems Community to get an ad-free experience and exclusive discounts in our eBay Store.

Blog TrueNAS 12.0 Reaches Prime Time

JoshDW19

Community Moderator
Administrator
Moderator
iXsystems
Joined
May 16, 2016
Messages
940

da_da

Neophyte
Joined
Apr 7, 2021
Messages
9
Just updated to U3 and see the CPU and Memory spinning wheel... I tested it in FF, Brave and Chrome all showing the same spinning wheel.

updated the themes and reset the preferences and made no difference.
 

Patrick M. Hausen

Dedicated Sage
Joined
Nov 25, 2013
Messages
3,033
I guess a U3.1 is called for :wink:
 

Philip Robar

Member
Joined
Jun 10, 2014
Messages
104
After upgrading I lost access to the GUI (I tried multiple browsers on macOS and Linux) and Guest access to all of my SMB shares stopped working. I had to rollback from the console.
 

CHL

Neophyte
Joined
Apr 20, 2014
Messages
9
Just rolled back to U2.1 - could not export pools in U3 (I do some manual backups from time to time to external drives). So I just tried to export my main-pool what also resulted in an error. Sorry.... U3.1 will have to come :smile:
 

q/pa

Member
Joined
Mar 16, 2015
Messages
48
All good here.
 

davidjb

Newbie
Joined
Mar 20, 2017
Messages
3
After upgrading I lost access to the GUI (I tried multiple browsers on macOS and Linux) and Guest access to all of my SMB shares stopped working. I had to rollback from the console.
I also lost access to SMB upon moving to U3. All my shares, still present in the TrueNAS GUI, were lost/unknown to samba:

Code:
% smbclient -U user //127.0.0.1/home
Enter WORKGROUP\user password:
tree connect failed: NT_STATUS_BAD_NETWORK_NAME
% smbclient -U user -L 127.0.0.1
Enter WORKGROUP\user's password:
        Sharename       Type      Comment
        ---------       ----      -------
        IPC$            IPC       IPC Service (NAS Server)


My various shares, including the one I tried to connect to first up were missing. Tried restarting, restarting samba_server and no luck. Was just about to rollback to U2.1 but I went and edited all shares one-by-one, resaving without making any changes, and this brought them back and visible to smbclient. Haven't yet rebooted to check if this fix persists.
 
Top