Upgraded trhee hours ago from 11.1-U6 to FreeNAS-11.2-RELEASE. Everything seems OK. Old plugins working, VM also.Looking for feedback from anyone that has installed 11.2, released today
Upgraded trhee hours ago from 11.1-U6 to FreeNAS-11.2-RELEASE. Everything seems OK. Old plugins working, VM also.Looking for feedback from anyone that has installed 11.2, released today
Encrypting the pool is not a feature? See menu to right of your pool menu when you select "Storage" in the new UI:Dataset encryption is not, and never has been, a FreeNAS feature. What exactly are you talking about?
Yes, it is--well, mostly. More accurately, the partitions are encrypted, and then a pool is created on them. But in any case, a pool is not a dataset. Dataset-level encryption is a very different thing, which has only recently been added to OpenZFS on Linux but isn't present in FreeBSD yet.Encrypting the pool is not a feature?
I doubt it actually did this, or even that it would be possible for it to have done so*. What it might have done would be to remove the passphrase for the encryption key, which might make it appear that the encryption was gone. But either way, it sounds like a bug. Suggest you report it using the "support" link in the web GUI, which will attach a debug file to help the devs figure out what happened. Edit: I just tried to reproduce this by creating an encrypted pool under 11.2-BETA2, setting a passphrase, and then upgrading to 11.2-RELEASE. When it rebooted after the upgrade, I needed to enter the passphrase to unlock the pool--so at least with going from 11.2-BETA2 to 11.2-RELEASE, I couldn't duplicate the issue.the FreeNAS upgrade process removed the encryption protection.
Dashboard graphs are still broke looks like :(
Yes, it is--well, mostly. More accurately, the partitions are encrypted, and then a pool is created on them. But in any case, a pool is not a dataset. Dataset-level encryption is a very different thing, which has only recently been added to OpenZFS on Linux but isn't present in FreeBSD yet.
I'm getting some errors while trying to install 11.2 from USB created with Rufus 3.4.1430 on Windows 10 (also tried 3.3.1400 with two different thumb drives).
ISO Checksum is OK
Tried with 11.1-U6 and it worked fine no problem, also Rufus behaves more like it usually do, asks if you want ISO or DD mode and also says "hey i need to download grub, is this ok?". For 11.2 it just grays out everything and just writes it.
Code:FreeBSD/x86 bootstrap loader, Revision 1.1 (Wed Dec 5 15:05:26 EST 2018 root@nemesis.tn.ixsystems.com) read 272 from 128 to 0xdbe03220, error: 0x80 read 258 from 2 to 0xdbdf3620, error: 0x80 read 260 from 64 to 0xdbe03220, error: 0x80 read 1 from 64 to 0xdvdfb220, error: 0x80 read 1 from 1 to 0xdbdf3420, error: 0x80 panic: free: guard1 fail @ 0xdbef9320 from unknown:0
What am I doing wrong?
I am not a particular 'fan' of the feature where dataset encryption pass-phrases are removed as part of the upgrade process.
I'm sure there is a reason but FreeNAS might want to inform users of this explicitly during the process.
My VM and Test machine are fine, my main machine always takes __*__AGES__*__ to install now, she's old, weak and maybe USB keys getting old, but I literally wait 2 or 3 hours to be certain generally, so I do it remotely from work.
I'm curious if that Rancher 1.4.2 made it in or still 1.4.1 ?
I have change the train, but I still see the update for 11.2-RC2. Is there a way to clear the caches of the updates?
Edit: Also after reboot I can’t see th e update :(
Tried to go from RC2 to Release. Not having much luck. Been running nearly 45 minutes and all I'm seeing is core dumps...
View attachment 26867
Not sure if I should kill it and restart or just let it error out on its own.
Cheers,
Matt
Are you behind a proxy? Can you verify that you can ping an Internet address?
My pool was encrypted with a pass-phrase from the very beginning (9.10, IIRC). Thus, every time the NAS is rebooted, I have to provide a pass-phrase in order for FreeNAS to be able to mount the pool contents and share them.Can you clarify what you mean by that? We don't support dataset encryption (this is a 2019 feature provided by native crypto). What exactly is the issue (I am asking to make sure it is clear in the Upgrading Recommendations section of the Release Notes).
It is possible that the stress of the update is causing the boot device to fail (just a heads up for those who want to try a different boot device).
took a little time to generate stats, but things look good now.Just completed upgrading from 11.2-RC2 to 11.2-RELEASE no issues to report with the upgrade. Still have some reporting problems with CPU and Memory on the dashboard, but I haven't started to research what that's all about yet.