12.0-RC1 Status Update

[Kris Moore]

TrueNAS Fans,

Just wanted to take a moment and let everybody know that the RC1 release is off to a fantastic start! We've already broken all other previous pre-release update records, and are getting great feedback. We're looking at the final release launching later in Oct, so please keep the feedback coming, and lets help make this the best new launch ever! As always, if you find an issue, please let us know right away on jira.ixsystems.com so we can investigate it in a timely manner.

Thanks!

 

[Newfoundland.Republic]

Great job Kris keeping everyone updated! (I wish the UniFi folks would do the same... )

 

[FalseNAS]

Hi,

I am just wondering if anyone has a rough estimate on the release date of the final release. Any sort of timeframe in Oct would be fine (the more specific the better, but something like later half of October would be fine).

Thank you!

 

[morganL]

Hi,

I am just wondering if anyone has a rough estimate on the release date of the final release. Any sort of timeframe in Oct would be fine (the more specific the better, but something like later half of October would be fine).

Thank you!

Prior to October 31st and with fewest bugs possible.....

Quality is more important than date.

 

[emk2203]

Does it make sense to file a bug report when the scenario is not well-defined? I had the Transmission plugin die on me a couple of times under heavy load, but I am struggling how to report it.

 

[morganL]

Does it make sense to file a bug report when the scenario is not well-defined? I had the Transmission plugin die on me a couple of times under heavy load, but I am struggling how to report it.

Its a good question.... if multiple plugins died, then its a TrueNAS issue. If only one plugin dies, we don't know whether it's the plugin or TrueNAS.

Do you run other plugins?
Can you replicate the issue easily?
What resource is heavily used... cpu, network, drives, RAM?

Suggest you gather all data you can and post to the forums... Maybe someone will see a pattern.

if it can be replicated easily, then reporting the bug may be worthwhile.

 

[sahuagin2]

I just upgraded, and while it mostly has gone well, I do have a problem with where things are mounted. While volume1 is mounted on /mnt/volume1, there is also a /mnt/mnt/volume1, which is less than desirable as nothing is now in it's proper place.
I'd appreciate some help, I'm hoping it's as simple as changing my altroot to something else.

Code:

freenas% mount | grep -E 'volume1 |tmpfs on /mnt'
tmpfs on /mnt (tmpfs, local)
volume1 on /mnt/mnt/volume1 (zfs, local, nfsv4acls)
freenas% zpool get altroot volume1
NAME     PROPERTY  VALUE    SOURCE
volume1  altroot   /mnt     local
freenas%

For example, ssh myuser, to the machine.

Code:

Welcome To FreeNAS
Could not chdir to home directory /mnt/volume1/datashare/myuser: No such file or directory
freenas% echo $HOME
/mnt/volume1/datashare/myuser
freenas% zfs list | grep myuser
volume1/datashare/myuser                                        3.19T  3.09T     2.34T  /mnt/mnt/volume1/datashare/myuser
volume1/datashare/myuser/DVR                                    47.3G  3.09T     47.3G  /mnt/iocage/jails/channels-dvr/root/media/DVR
freenas% zpool get all volume1 | grep altroot
volume1  altroot                        /mnt                           local
freenas% zfs get mountpoint /mnt/mnt/volume1/datashare/myuser
NAME                       PROPERTY    VALUE                               SOURCE
volume1/datashare/tcovert  mountpoint  /mnt/mnt/volume1/datashare/tcovert  inherited from volume1
freenas%

Additonally, all of my jails are down as well, as they can't find their baseroot.

Code:

freenas% iocage list
You need to be root to convert the configurations to the new format!
You need to be root to convert the configurations to the new format!
+------+--------------+---------+--------------+------+
| JID  |     NAME     |  STATE  |   RELEASE    | IP4  |
+======+==============+=========+==============+======+
| None | ansible      | down    | 11.4-RELEASE | DHCP |
+------+--------------+---------+--------------+------+
| None | channels-dvr | CORRUPT | N/A          | N/A  |
+------+--------------+---------+--------------+------+
| None | git_jail     | down    | 11.4-RELEASE | DHCP |
+------+--------------+---------+--------------+------+
| None | gitlab       | CORRUPT | N/A          | N/A  |
+------+--------------+---------+--------------+------+
| None | plex         | down    | 11.4-RELEASE | DHCP |
+------+--------------+---------+--------------+------+
| None | prometheus   | down    | 11.4-RELEASE | DHCP |
+------+--------------+---------+--------------+------+
| None | remotelog    | down    | 11.4-RELEASE | DHCP |
+------+--------------+---------+--------------+------+
freenas% zfs list volume1/iocage
NAME             USED  AVAIL     REFER  MOUNTPOINT
volume1/iocage  26.4G  3.09T     15.6M  /mnt/mnt/volume1/iocage
freenas% zfs get mountpoint volume1/iocage
NAME            PROPERTY    VALUE                    SOURCE
volume1/iocage  mountpoint  /mnt/mnt/volume1/iocage  inherited from volume1
freenas%

And, what /mnt looks like, well, a selection so as to not spam everyone.

Code:

freenas% find /mnt -maxdepth 4                                                                                                                                                                           
/mnt                                                                                                                                                                                                     
/mnt/volume1                                                                                                                                                                                             
/mnt/volume1/jails                                                                                                                                                                                       
/mnt/volume1/jails/.warden-template-pluginjail-10.3-x64                                                                                                                                                 
/mnt/volume1/jails/.warden-template-pluginjail-10.3-x64/libexec                                                                                                                                         
/mnt/volume1/jails/.warden-template-pluginjail-10.3-x64/rescue 
/mnt/iocage
/mnt/iocage/jails
/mnt/iocage/jails/channels-dvr
/mnt/iocage/jails/channels-dvr/root
/mnt/md_size
/mnt/mnt
/mnt/mnt/volume1
/mnt/mnt/volume1/.freenas
/mnt/mnt/volume1/.freenas/gui-install-environment.tar
/mnt/mnt/volume1/.freenas/pre-install
/mnt/mnt/volume1/.freenas/tmp
/mnt/mnt/volume1/.freenas/lib
/mnt/mnt/volume1/.freenas/etc
/mnt/mnt/volume1/.freenas/install
/mnt/mnt/volume1/.freenas/firmware.img
/mnt/mnt/volume1/.freenas/bin
/mnt/mnt/volume1/.freenas/gui-boot.tar
/mnt/mnt/volume1/.freenas/gui-packages.tar
/mnt/mnt/volume1/jails
/mnt/mnt/volume1/jails/git_jail_orig
/mnt/mnt/volume1/jails/.warden-template-pluginjail-9.3-x64
/mnt/mnt/volume1/jails/.warden-template-standard-11.0-x64
/mnt/mnt/volume1/jails/plex
/mnt/mnt/volume1/jails/.git_jail.meta
/mnt/mnt/volume1/jails/.warden-template-pluginjail-9.2-x64
/mnt/mnt/volume1/jails/.warden-template-pluginjail-10.3-x64
/mnt/mnt/volume1/jails/.plex.meta
/mnt/mnt/volume1/jails/.warden-files-cache
/mnt/mnt/volume1/jails/.redmine.meta
/mnt/mnt/volume1/jails/redmine
/mnt/mnt/volume1/jails/.warden-template-standard-11.0-x64-20180819223447
/mnt/mnt/volume1/jails/.warden-template-standard--x64
/mnt/mnt/volume1/jails/.plugins
/mnt/mnt/volume1/jails/.warden-template-standard-10.3-x64
/mnt/mnt/volume1/datashare
/mnt/mnt/volume1/myuser
/mnt/mnt/volume1/timecapsule
/mnt/mnt/volume1/timecapsule/.AppleDB
/mnt/mnt/volume1/timecapsule/backup_myuser
/mnt/mnt/volume1/plexdata
/mnt/mnt/volume1/plexdata/Plex Media Server
/mnt/mnt/volume1/plexdata/Plex
/mnt/mnt/volume1/iocage
/mnt/mnt/volume1/iocage/.plugins
/mnt/mnt/volume1/iocage/images
/mnt/mnt/volume1/iocage/defaults.json
/mnt/mnt/volume1/iocage/default_rc.conf
/mnt/mnt/volume1/iocage/jails
/mnt/mnt/volume1/iocage/log
/mnt/mnt/volume1/iocage/download
/mnt/mnt/volume1/iocage/templates
/mnt/mnt/volume1/iocage/releases
/mnt/mnt/volume1/iocage/defaults_backup.json
freenas%

 

[sahuagin2]

Ah, and I left this out.

Code:

freenas% zpool get altroot volume1
NAME     PROPERTY  VALUE    SOURCE
volume1  altroot   /mnt     local
freenas% zfs get mountpoint volume1
NAME     PROPERTY    VALUE             SOURCE
volume1  mountpoint  /mnt/mnt/volume1  local
freenas% sudo zfs set mountpoint=/mnt/volume1 volume1
cannot set property for 'volume1': child dataset with inherited mountpoint is used in a non-global zone
freenas% zpool set altroot=/ volume1
cannot set property for 'volume1': property 'altroot' can only be set during pool creation or import
freenas% 

 

[Stilez]

Just to mention, I was unable to upgrade to RC1 - something changed in the cxgbe driver (T540-CR NIC) between 2.1 beta and RC1, and RC1 kernel panics during boot every time, on both normal and single user. Had to go back to 2.1 beta boot environment to get it to boot properly. JIRA reports filed.

Just mentioning in case anyone else hits the same issue.

Also, any chance of a speedy fix to that specific bug, so I can try out the RC? I haven't been able to see it running yet, and I'd like to before final! Thanks!

UPDATE - resolved, its a bug in the cxgbe(4) driver (NAS-107648), the updated version in RC1 crashed on boot if the tunable hw.cxgbe.largest_rx_cluster is set. Now reported upstream to Chelsio.

 

[VladTepes]

Many apologies if I've missed a thread/ announcement elsewhere.

I've seen that a number of issues have cropped up with RC1 that require a remedy,and that all takes time but is there any ETA for RC2 or release versions?

Ta