Anyone try -U5 yet

[MarcusJ]

I have a number of iocage jails running and because of this: https://redmine.ixsystems.com/issues/34339
I'm too scared to try yet.

We upgraded and experienced the same bug with our IOCAGE Jails running VNET=on. The orginal post can be found here: https://forums.freenas.org/index.ph...n-iocage-jail-after-upgrade-to-11-1-u5.64124/

 

[INCSlayer]

I have several Jails both with VNET=on and off and on my system its all working fine

 

[DrumNBisco]

I've started migrating jails to iocage, so I'll hold off for a while due to this bug https://redmine.ixsystems.com/issues/34339

 

[JoelN]

Update from U3 to U5 went fine. Standard Plex jail created with FN v. 11 still working OK.

 

[Jailer]

I have a number of iocage jails running and because of this: https://redmine.ixsystems.com/issues/34339
I'm too scared to try yet.

And this is why I wait. This is a deal breaker for me, I have several jails. Until it's fixed I'm not updating.

 

[diskdiddler]

Every update I do, takes very ,very, very long to apply but I just accept it. It does end up working.
My system is pretty weak and it's on USB, so I'm forgiving, end of the day, it works.

I do have the "June 1, 2018, 1:24 p.m. - smartd_daemon is not running." others are reporting. But she seems ok?

 

[Wouter]

Changelog:
24965 Add more command output to freenas-debug
26484 Don't write unneeded SNMP messages to /var/log/messages
27936 More fixes to ensure /nonexistent directory is not created
28585 Fix Samba memory leak in vfswrap_getwd()
29971 Improve logging in AD monitoring
30213 Turn bootenv.delete into a job to prevent timeout related traceback when deleting boot enviroments
30609 Do not log nginx errors to console
30729 Speed up and clean up freenas-debug
30768 Fix argument for SMB_VFS_NEXT_DISK_FREE in zfs_space VFS module
30960 Display Samba version and git commit with smbd -v
30990 Make lagg work with 100Gbps and 25Gbps interfaces that report extended media types
31041 Add support for Self-Encrypting Drives
31050 Do not spawn another thread on call_sync middleware call
31059 Fix user.delete API call when DC is enabled
31404 When using ADS disable DOSATTRIB to prevent Windows 7 "Invalid MS-DOS function" error
31635 Correct PAM constants for AFP users authenticating as local user in LDAP environment
31773 Migrate MTU settings when upgrading from 9.10.X to 11.1.X
32868 Fix "Check Now" traceback error
32880 Fix alert services traceback
32943 Add -M to freenas-debug to check SATA DOM speed
33045 Check if TrueNAS system needs an HBA firmware update
33228 Add configured SMART, replication, and scrub tasks to freenas-debug
33618 Do not show beta UI link
33663 Alphabetize freenas-debug switches
33786 Be less restrictive for NFS exports
33855 Remove dtrace freenas-debug modules
33885 Start dbus before netatalk
33924 Add check to see if NIS is enabled
33927 Fix typo in NFS section of freenas-debug
33930 Fix traceback in system section of freenas-debug
33957 Fix Python global interpreter lock with LDAP
33987 Fix system.advanced traceback during system boot
33993 Remove parallel routines for freenas-debug to prevent CPU spike

I'm not reading a thing about an bhyve update. Does anybody know if its possible to run Ubuntu 18.04 via the VM option in this new Freenas release?

 

[Wouter]

I'm not reading a thing about an bhyve update. Does anybody know if its possible to run Ubuntu 18.04 via the VM option in this new Freenas release?

And to answer my own question:

I tried the 18.04 installer on U5 today, no luck :(

 

[spotcatbug]

Um, no, it wasn't. What makes you think this?

Hmmm. Weird. Yeah, I think I got that wrong. I definitely remember needing a new jail, trying to make one (the "old" way) and discovering that it was no longer possible in the GUI. That's the only reason I went iocage, seriously. I needed a jail and wasn't interested in learning the new iocage way (in hindsight, I realize I never would be :D), but I was "forced" to move to iocage. Looking at the old GUI right now, I see "Add Jail" is still there, so I don't know what my problem was.

Wait, there are no templates listed. Must have been something to do with that. Maybe I figured learning how to get the template back to make an old-style jail would be just as big a hassle as figuring out the new iocage way of doing things, and, since eventually the warden jail support would be gone (new GUI doesn't have it at all), that would be a better use of my time.

 

[danb35]

Wait, there are no templates listed.

That's been the case for a long time too (I think since 9.10-U2, when they finally pulled VirtualBox out). There's just the standard template, which is there, but doesn't show up in the drop-down.

The problem with warden jails is that they're stuck on a FreeBSD 11.0 template, which has been EOL since 90 days after 11.1 released. That's causing issues with pkg updates and such, though they can be worked around if needed.

So the bottom line is that building the jails with iocage is the better thing to be doing, though the ongoing networking issues with iocage are getting frustrating.

 

[Jailer]

though the ongoing networking issues with iocage are getting frustrating.

That's an understatement.

 

[diskdiddler]

That's an understatement.

What's the issue and is it fixed in the nightlies for 11.2? I used several builds of 11.2 nightly and the UI improvements for iocage were huge.

However, I haven't actually gone and used the plugins much, just confirmed they make a jail, they install ok, etc.

 

[felthamn]

Sticking to 11.1 U4. I have everything working the way I want it (including iocage - thanks to the regulars of this forum).

 

[hoserama]

Upgraded from 11.1-U4 without any problems. Running Transmission and Plex plugins.

 

[ninjai]

I don't know how the new update is because I updated on my lunch break and it's now unreachable (and for some reason IPMI also unreachable... maybe the cable is disconnected, I don't know). It's been about 2.5 hours and nothing is up.

 

[nojohnny101]

I don't know how the new update is because I updated on my lunch break and it's now unreachable (and for some reason IPMI also unreachable... maybe the cable is disconnected, I don't know). It's been about 2.5 hours and nothing is up.

Yikes, updating while away and not able to put out any fires, sounds like risks I wouldn't take. What hardware are you running. Seems conspicuously like the ASROCK debacle.

 

[ninjai]

Yikes, updating while away and not able to put out any fires, sounds like risks I wouldn't take. What hardware are you running. Seems conspicuously like the ASROCK debacle.

False alarm! I only did it because it's my home NAS. Not ASROCK. I'm running fully supported hardware . Can't remember exact model but a supermicro motherboard. It turned out to be a UEFI glitch . Same thing happens on my ASROCK motherboard on my PC though... It's like UEFI cant see certain devices on a soft boot. Once I shut down the NAS then started it again it was all good

 

[Chris Moore]

Just checked and it's available. I'm waiting for the early adopters to report their findings............

On day two after release, I installed it on a system and on day three I installed it on another system. No problem so far.
First system has an old plugin Plex install and a bhyve Linux VM.

 

[felthamn]

I'm still going to step back from the update a while longer. To be honest looking at the list of changes and updates. I don't see anything that would influence me to update right now. I have a stable and secure system at the moment so I will go on the basis of not trying to fix something that isn't broken.

 

[NaCl]

I have a very weird issue. I'm not even certain what to check to root-cause the thing. It's not strictly 11.1-u5 issues as it happened in 11.1-RELEASE and I just rolled back to 11.0-u4 and figured I'd wait it out. I tried 11.1-u5 and the same thing's happening. So I figured I'd break down and ask wtfo!?

Topology:
4 fully populated 24 bay SAS jbod boxes w/Arecca SAS expanders. 2 w/750GB drives and 2 w/4TB drives.

When I update to 11.1-(RELEASE|u5) I get a hole in the number of drives the system sees. /dev/da47 in 11.0-u4 is the last drive in the 2nd of the 4TB populated jbod. In 11.1-u5 that drive/slot isn't even enumerated in the OS. /dev/da47 is the first drive of the first of the 750GB populated jbod. When doing a sequential access 'test':

Code:

for d in {0..95}; do echo "--- /dev/da${d} ---"; dd if=/dev/da${d} of=/dev/null bs=512m count=1; done

And watching the leds on the drive carriers. It gets to 46, as slot 22 (0 index) of 2nd 4TB jbod, skips over slot 23 (0 index) of that same jbod, and slot 0 of the first 750GB jbod is accessed. In 11.0-u4 there are no issues. All 96 drives are present and accounted for.

I have a diskmap from both versions for further verification:

Code:

root@freenas11: for d in {45..50}; do grep da${d} 11-0-u4/disk_map.txt; done																  ~ 0
da45: Serial Z3051GXE ; GPTID=gptid/1b227d4d-022b-11e7-a647-a0369f3c3d84
da46: Serial Z3051H2T ; GPTID=gptid/1c056812-022b-11e7-a647-a0369f3c3d84
da47: Serial Z3051PC5 ; GPTID=gptid/1ced0d90-022b-11e7-a647-a0369f3c3d84
da48: Serial GTD200P8G4MY6D ; GPTID=gptid/6a81b334-0224-11e7-92db-a0369f3c3d84
da49: Serial GTA200P8G4UTZA ; GPTID=gptid/6ca5f360-0224-11e7-92db-a0369f3c3d84
da50: Serial GTD200P8G4N6JD ; GPTID=gptid/6ed038c6-0224-11e7-92db-a0369f3c3d84

root@freenas11: for d in {45..50}; do grep da${d} 11-1-u5/disk_map.txt; done																  ~ 0
da45: Serial Z3051GXE ; GPTID=gptid/1b227d4d-022b-11e7-a647-a0369f3c3d84
da46: Serial Z3051H2T ; GPTID=gptid/1c056812-022b-11e7-a647-a0369f3c3d84
da47: Serial GTD200P8G4MY6D ; GPTID=gptid/6a81b334-0224-11e7-92db-a0369f3c3d84
da48: Serial GTA200P8G4UTZA ; GPTID=gptid/6ca5f360-0224-11e7-92db-a0369f3c3d84
da49: Serial GTD200P8G4N6JD ; GPTID=gptid/6ed038c6-0224-11e7-92db-a0369f3c3d84
da50: Serial GTF200P8G5094F ; GPTID=gptid/70ed41e5-0224-11e7-92db-a0369f3c3d84

root@freenas11: diskinfo -v /dev/da47																									~ 0
/dev/da47
		512			 # sectorsize
		4000787030016   # mediasize in bytes (3.6T)
		7814037168	  # mediasize in sectors
		4096			# stripesize
		0			   # stripeoffset
		486401		  # Cylinders according to firmware.
		255			 # Heads according to firmware.
		63			  # Sectors according to firmware.
		Z3051PC5		# Disk ident.
		id1,enc@n5001b4d50dbba03d/type@0/slot@18/elmdesc@SLOT_24		# Physical path
		Not_Zoned	   # Zone Mode

root@freenas11: grep -A12 'da47' 11-1-u5/diskinfo.txt																						 ~ 0
--- /dev/da47 ---
/dev/da47
		512			 # sectorsize
		750156374016	# mediasize in bytes (699G)
		1465149168	  # mediasize in sectors
		0			   # stripesize
		0			   # stripeoffset
		91201		   # Cylinders according to firmware.
		255			 # Heads according to firmware.
		63			  # Sectors according to firmware.
		ATA Hitachi HDS72107	# Disk descr.
		GTD200P8G4MY6D  # Disk ident.
		id1,enc@n5001b4d5123ed03d/type@0/slot@1/elmdesc@SLOT_01 # Physical path
		Not_Zoned	   # Zone Mode

Controllers:

Code:

mpr0: <Avago Technologies (LSI) SAS3216> port 0xd000-0xd0ff mem 0xfb400000-0xfb40ffff irq 26 at device 0.0 on pci1
mpr0: Firmware: 14.00.00.00, Driver: 18.03.00.00-fbsd
mpr0: IOCCapabilities: 7a85c<ScsiTaskFull,DiagTrace,SnapBuf,EEDP,TransRetry,EventReplay,MSIXIndex,HostDisc,FastPath,RDPQArray>

mpr1: <Avago Technologies (LSI) SAS3224> port 0xe000-0xe0ff mem 0xfb600000-0xfb60ffff irq 32 at device 0.0 on pci2
mpr1: Firmware: 14.00.00.00, Driver: 18.03.00.00-fbsd
mpr1: IOCCapabilities: 7a85c<ScsiTaskFull,DiagTrace,SnapBuf,EEDP,TransRetry,EventReplay,MSIXIndex,HostDisc,FastPath,RDPQArray>

mpr2: <Avago Technologies (LSI) SAS3008> port 0xc000-0xc0ff mem 0xfb240000-0xfb24ffff,0xfb200000-0xfb23ffff irq 42 at device 0.0 on pci4
mpr2: Firmware: 12.00.00.00, Driver: 18.03.00.00-fbsd
mpr2: IOCCapabilities: 7a85c<ScsiTaskFull,DiagTrace,SnapBuf,EEDP,TransRetry,EventReplay,MSIXIndex,HostDisc,FastPath,RDPQArray>

There looks to be some odd enumeration in the 11-0-u4 case (all drives showing up):

Code:

root@freenas11: grep da47 11-0-u4/dmesg.txt																								   ~ 0
da47 at mpr0 bus 0 scbus0 target 122 lun 0
da47: <ATA Hitachi HDS72107 A70M> Fixed Direct Access SPC-4 SCSI device
da47: Serial Number GTD200P8G4MY6D
da47: 300.000MB/s transfers
da47: Command Queueing enabled
da47: 715404MB (1465149168 512 byte sectors)
ses2: da47,pass50: Element descriptor: 'SLOT 01'
ses2: da47,pass50: SAS Device Slot Element: 1 Phys at Slot 0
da47 at mpr0 bus 0 scbus0 target 122 lun 0
da47: <ATA Hitachi HDS72107 A70M> Fixed Direct Access SPC-4 SCSI device
da47: Serial Number GTD200P8G4MY6D
da47: 300.000MB/s transfers
da47: Command Queueing enabled
da47: 715404MB (1465149168 512 byte sectors)
ses2: da47,pass50: Element descriptor: 'SLOT 01'
ses2: da47,pass50: SAS Device Slot Element: 1 Phys at Slot 0
da47 at mpr0 bus 0 scbus0 target 121 lun 0
da47: <ATA ST4000VN000-1H41 SC46> Fixed Direct Access SPC-4 SCSI device
da47: Serial Number Z3051PC5
da47: 600.000MB/s transfers
da47: Command Queueing enabled
da47: 3815447MB (7814037168 512 byte sectors)
ses1: da47: Element descriptor: 'SLOT 24'
ses1: da47: SAS Device Slot Element: 1 Phys at Slot 23
GEOM_ELI: Device da47p1.eli created.

root@freenas11: grep da47 11-1-u5/dmesg.txt																								   ~ 0
da47 at mpr0 bus 0 scbus0 target 122 lun 0
da47: <ATA Hitachi HDS72107 A70M> Fixed Direct Access SPC-4 SCSI device
da47: Serial Number GTD200P8G4MY6D
da47: 300.000MB/s transfers
da47: Command Queueing enabled
da47: 715404MB (1465149168 512 byte sectors)
ses2: da47,pass50: Element descriptor: 'SLOT 01'
ses2: da47,pass50: SAS Device Slot Element: 1 Phys at Slot 0
da47 at mpr0 bus 0 scbus0 target 122 lun 0
da47: <ATA Hitachi HDS72107 A70M> Fixed Direct Access SPC-4 SCSI device
da47: Serial Number GTD200P8G4MY6D
da47: 300.000MB/s transfers
da47: Command Queueing enabled
da47: 715404MB (1465149168 512 byte sectors)
ses2: da47,pass50: Element descriptor: 'SLOT 01'
ses2: da47,pass50: SAS Device Slot Element: 1 Phys at Slot 0

Why does it enumerate da47 2x as the 750GB drive and once as the 4TB drive and bump the 750GB to da48 in the 11-0-u4 case but no enumeration entirely of that drive in
the 11-1-u5 case?

Any/all assitance would be _grand_!

Thanks!