TrueNAS 13.0-U2 is now available

[SweetAndLow]

1. update your jails
2. could it be Realtek RTL8111H networking?

Probably not the realtek since it's not a 2.5GB nic.

 

[House Of Cards]

Probably not the realtek since it's not a 2.5GB nic.

It's just GB LAN. Intel...

 

[House Of Cards]

1. update your jails.

Was there something that changed? I will upgrade them, but I usually do this in stages because of issues just like this. Right now, I know it's the TrueNAS upgrade that broke something, so unless I have a reason to start upgrading all the jails I'd rather hold off or try one of the less important ones first.

I thought the theory was that if the jail is running 12.3 it shouldn't rely on the underlying OS of the host system? That's why I go this path concerning upgrades. I update the host to 13, then follow up getting the jails to 13... Seems rational. Again, unless something changed?

 

[Samuel Tai]

1. update your jails
2. could it be Realtek RTL8111H networking?

Most definitely. The specs for the MSI C236M motherboard show the onboard NIC is a Realtek RTL8111H.

 

[Samuel Tai]

Also, what does iocage get resolver <name of jail> show for each jail? It's supposed to have value /etc/resolv.conf, with the contents populated from the host DNS settings from Network->Global Summary.

 

[Volts]

manually configured 172.16.2.0/24 address

Literally 172.16.2.0? Or (I assume) addresses from that subnet?

Is that the subnet for the wired LAN, and 172.16.2.1 is the gateway? Or do you expect NAT for these jails?

Are there any other jails that do use NAT?

 

[mistermanko]

Updated via GUI, which was uneventful. As always, great work!

 

[norseman]

I updated to latest version.

I destroyed my zdev cache of 2x 960GB Intel SSD. However, in trying to create it again, I am unable to click 'create'.

Any ideas how I resolve this or do it form cli?

 

[Samuel Tai]

@norseman, go to Storage->Pools, and click the gear. Select Add VDEVs, and then pull down the Add VDEV button to the Cache VDEV. It's not possible to create a pool with only a cache VDEV. It has to be added to an existing pool with active data VDEVs.

See also https://www.truenas.com/community/threads/cannot-create-l2arc-cache-vdev.103541/, which is what I think you're doing.

 

[norseman]

@norseman, go to Storage->Pools, and click the gear. Select Add VDEVs, and then pull down the Add VDEV button to the Cache VDEV. It's not possible to create a pool with only a cache VDEV. It has to be added to an existing pool with active data VDEVs.

See also https://www.truenas.com/community/threads/cannot-create-l2arc-cache-vdev.103541/, which is what I think you're doing.

That is exactly what I was doing.
Thanks for the correction!
norseman

 

[House Of Cards]

Most definitely. The specs for the MSI C236M motherboard show the onboard NIC is a Realtek RTL8111H.

I disabled the onboard NIC. Got an intel in there...

 

[House Of Cards]

Also, what does iocage get resolver <name of jail> show for each jail? It's supposed to have value /etc/resolv.conf, with the contents populated from the host DNS settings from Network->Global Summary.

It returns /etc/resolv.conf...

 

[Samuel Tai]

Can you provide the contents of /etc/resolv.conf from inside a non-working jail?

 

[House Of Cards]

Literally 172.16.2.0? Or (I assume) addresses from that subnet?

Is that the subnet for the wired LAN, and 172.16.2.1 is the gateway? Or do you expect NAT for these jails?

Are there any other jails that do use NAT?

An IP on that subnet. 172.16.2.1 is the gateway for the pfSense router interface. There is a 4-port NIC in the pfSense box. This is the gateway for that interface. There are two Intel NICS (EM0 and EM1) on the NAS. The jails (which are for automation items) are directed to use EM0 which is connected to pfSense's 172.16.2.1 interface.

TrueNAS uses EM1 and is connected to the 172.16.1.1 interface.

 

[House Of Cards]

Can you provide the contents of /etc/resolv.conf from inside a non-working jail?

Code:

# Generated by resolveconf
search LOCAL LOCAL.LAN
nameserver 172.16.1.1
nameserver 172.16.2.1

 

[Samuel Tai]

Can you provide the output of netstat -rn from both the host and from inside a non-working jail?

Also, the output of ifconfig -a on the host. I'm curious if you have multiple bridges, and iocage ended using the wrong bridge after the upgrade.

 

[andrema2]

To answer all questions:
1. I didn't upgrade the pool since installing 13.0
2. I did a successful scrub.
3. The system has 24GB of RAM.
4. The system doesn't use a thumb drive but a virtual 10GB harddisk.

The TrueNAS VM gets two cores in one socket from Proxmox. The host CPU is a Xeon E5-2630 v2 (12 core). Virtualized CPU type is equal real CPU.

In the meantime I trimmed the boot environment to one (U1.1) before the update and switched from above CPU configuration to 2 sockets, 1 cores and also 1 sockets, 1 cores but behaviour stayed the same.

I don't use any Jails or VM inside TrueNAS.

So I just created https://ixsystems.atlassian.net/browse/NAS-117975

Regards,
Chris

I'm having the same issue with a system simmilar but with 128gb RAM and 2 CPUs and 4 core each. Rolling back to 13 U1.1 solves it. I saw it would be corrected in a nighly build. Would it be rollout in a 13 U2.1 in the coming days or it will follow the normal release cicles ?

 

[Samuel Tai]

@andrema2, have you tried the work-around @pkerwien discovered of changing the vCPU to kvm64?

 

[andrema2]

@andrema2, have you tried the work-around @pkerwien discovered of changing the vCPU to kvm64?

No, I've not. I saw that kvm32/kvm64 are non-recomended x86 CPU, listed "just for historical compatibility with ancient QEMU versions", qemu32/qemu64 CPU (lower performance and increased security risks as such QEMU cpu has no patches for spectre/meltdown/etc). This is per Proxmox Forums.

 

[House Of Cards]

Code:

# Generated by resolveconf
search LOCAL LOCAL.LAN
nameserver 172.16.1.1
nameserver 172.16.2.1

Okay, sorry. I had rebooted into the working environment before checking this. The get resolver command does output

Code:

/etc/resolv.conf

but that files contents are...

Code:

# Generated by resolveconf
search LOCAL.LAN
nameserver 172.16.1.1

Before this update the jails had the 172.16.2.1 in there, but after, it doesn't contain that. If I boot back into RELEASE it shows both. My firewall will block attempts from the 172.16.2.0/24 from going across networks to isolate the home automation stuff from going into other LAN segments.

So I guess the question now is, why doesn't it carry over like before, and how do I fix it? My global configuration in TrueNAS has 172.16.1.1 and 172.16.2.1 as nameservers, and the default gateway is 172.16.1.1.