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

TrueNAS SCALE 22.02-RC.1 Now available!

Western Digital Drives - The Preferred Drives of FreeNAS and TrueNAS CORE

mye

Neophyte
Joined
Oct 1, 2021
Messages
10
It seems encryption is a common factor. In the system I've been able to inspect, the middleware was stuck in a job trying to recursively unlock the pool.
That's my guess. Encrypted pool. beta2->RC1 - on boot stuck on importing zfs pools. Rebooted to Beta1, delete pools, Boot to RC1, create pools with encryption, reboot to RC1 - stuck on importing pools. Fresh RC1 install, import pools from gui - reboot - stuck on importing.
 
Last edited:

rmr

Junior Member
Joined
Sep 8, 2021
Messages
13
Yes, that's it. On a fresh install, putting the "Apps" pool on an encrypted pool causes it to hang at the next reboot. Putting it on an unencrypted pool (leaving everything else the same) causes it to hang.

It seems encryption is a common factor. In the system I've been able to inspect, the middleware was stuck in a job trying to recursively unlock the pool.
 

uRyn

Newbie
Joined
Jul 15, 2021
Messages
1
I have try no matter fresh install or upgrade, same problem. I think it's not connected to the xattr. it's the pool's problem.
  1. If I shutdown the server, open the box and remove the hard disks which pool cannot import during system booting. Then turn on server, trueNAS RC1 can boot success. Login the web ui, disconnect the pool. Then shutdown. reconnect the harddisk and turn on the server. while boot success, import the pool just disconnect before and everything working as expected. But the problem is while I restart the system with the pool connected same problem happen again(stuck in import pool).
  2. I can also boot to beta2 and disconnect the pool, then restart and boot to RC1, after boot success, import the pool again, everything working as expected. but same problem while restart system with pool connected.
So the problem is the RC1 cannot import pool while system booting. And it's not every pool cause this while system booting. I have several pools, only one of my pool will have this problem. I don't know what's special connect to the pool types. The pool blocked import during booting is a raid-Z with 3 harddisk, several datasets and one of the dataset encrypted with a key.
 

rmr

Junior Member
Joined
Sep 8, 2021
Messages
13
There is a PR in the notes for https://jira.ixsystems.com/browse/NAS-113052, https://github.com/truenas/middleware/pull/7796, which I manually applied. It fixes the issue for me.
Code:
--- a/usr/lib/python3/dist-packages/middlewared/plugins/pool.py
+++ b/usr/lib/python3/dist-packages/middlewared/plugins/pool.py
@@ -1852,7 +1852,9 @@ def import_on_boot(self, job):
                         'Failed to inherit mountpoints for %s', pool['name'], exc_info=True,
                     )
 
-                unlock_job = self.middleware.call_sync('pool.dataset.unlock', pool['name'], {'recursive': True})
+                unlock_job = self.middleware.call_sync(
+                    'pool.dataset.unlock', pool['name'], {'recursive': True, 'toggle_attachments': False}
+                )
                 unlock_job.wait_sync()
                 if unlock_job.error or unlock_job.result['failed']:
                     failed = ', '.join(unlock_job.result['failed']) if not unlock_job.error else ''

To apply this patch, boot back into your working 21.08-BETA.2. Save the patch into a file (for example, ~root/7796.patch) Then, on the command line,
Code:
$ sudo bash
# mkdir /mnt/2202
# mount -t zfs boot-pool/ROOT/22.02-RC.1 /mnt/2202
# cd /mnt/2202
# patch -p1 < 7796.patch
# cd /
# umount /mnt/2202
# rmdir /mnt/2202

You can now reboot into 22.02-RC.1.
 
Last edited by a moderator:

marmoset

Member
Joined
Dec 18, 2020
Messages
27
There is a PR in the notes for https://jira.ixsystems.com/browse/NAS-113052, https://github.com/truenas/middleware/pull/7796, which I manually applied. It fixes the issue for me.
Code:
--- a/usr/lib/python3/dist-packages/middlewared/plugins/pool.py
+++ b/usr/lib/python3/dist-packages/middlewared/plugins/pool.py
@@ -1852,7 +1852,9 @@ def import_on_boot(self, job):
                         'Failed to inherit mountpoints for %s', pool['name'], exc_info=True,
                     )
 
-                unlock_job = self.middleware.call_sync('pool.dataset.unlock', pool['name'], {'recursive': True})
+                unlock_job = self.middleware.call_sync(
+                    'pool.dataset.unlock', pool['name'], {'recursive': True, 'toggle_attachments': False}
+                )
                 unlock_job.wait_sync()
                 if unlock_job.error or unlock_job.result['failed']:
                     failed = ', '.join(unlock_job.result['failed']) if not unlock_job.error else ''

To apply this patch, boot back into your working 21.08-BETA.2. Save the patch into a file (for example, ~root/7796.patch) Then, on the command line,
Code:
$ sudo bash
# mkdir /mnt/2202
# mount -t zfs boot-pool/ROOT/22.02-RC.1 /mnt/2202
# cd /mnt/2202
# patch -p1 < 7796.patch
# cd /
# mount /mnt/2202
# rmdir /mnt/2202

You can now reboot into 22.02-RC.1.

I think that last mount should be umount? I'm not impacted by this so I can't confirm, but just looking at what you're doing umount makes more sense than mount.
 
Last edited by a moderator:

rmr

Junior Member
Joined
Sep 8, 2021
Messages
13
I think that last mount should be umount? I'm not impacted by this so I can't confirm, but just looking at what you're doing umount makes more sense than mount.
yes you’re right. I edited the post.
 

openwinz

Neophyte
Joined
Aug 22, 2020
Messages
5
I think that last mount should be umount? I'm not impacted by this so I can't confirm, but just looking at what you're doing umount makes more sense than mount.
There is a PR in the notes for https://jira.ixsystems.com/browse/NAS-113052, https://github.com/truenas/middleware/pull/7796, which I manually applied. It fixes the issue for me.
Code:
--- a/usr/lib/python3/dist-packages/middlewared/plugins/pool.py
+++ b/usr/lib/python3/dist-packages/middlewared/plugins/pool.py
@@ -1852,7 +1852,9 @@ def import_on_boot(self, job):
                         'Failed to inherit mountpoints for %s', pool['name'], exc_info=True,
                     )
 
-                unlock_job = self.middleware.call_sync('pool.dataset.unlock', pool['name'], {'recursive': True})
+                unlock_job = self.middleware.call_sync(
+                    'pool.dataset.unlock', pool['name'], {'recursive': True, 'toggle_attachments': False}
+                )
                 unlock_job.wait_sync()
                 if unlock_job.error or unlock_job.result['failed']:
                     failed = ', '.join(unlock_job.result['failed']) if not unlock_job.error else ''

To apply this patch, boot back into your working 21.08-BETA.2. Save the patch into a file (for example, ~root/7796.patch) Then, on the command line,
Code:
$ sudo bash
# mkdir /mnt/2202
# mount -t zfs boot-pool/ROOT/22.02-RC.1 /mnt/2202
# cd /mnt/2202
# patch -p1 < 7796.patch
# cd /
# umount /mnt/2202
# rmdir /mnt/2202

You can now reboot into 22.02-RC.1.
Confirmed, this patch worked for me as well. Hoping the patch will be part of RC.2. Really appreciate Truenas SCALE and the community support.
 
Last edited by a moderator:

Andreuha

Newbie
Joined
Oct 31, 2021
Messages
2
I just tried upgrading from Core to Scale and out of 3 pools only one is successfully brought online.

  • Physical drives are available in the disk list.
  • 'smartctl -H /dev/... ' returns PASSED for all devices
    • SMART tests initiated through the UI it hang at 99.00% for disks from both online and undetected pools (unrelated bug?)
  • pool still not visible after export
  • ruled out controller by shuffling drives around (mixing mainboard connectors & an LSI 9205-8I).
  • Pools come online with no problems after replacing old boot media and booting into TrueNAS CORE

Is this a known issue?
 

morganL

Captain Morgan
Administrator
Moderator
iXsystems
Joined
Mar 10, 2018
Messages
1,053

georgelza

Member
Joined
Feb 24, 2021
Messages
159
... so came here all "READY" to do... reading 5 pages later and it's hmmm ye maybe wait.

I created a VM on VirtualBox to test the water, well Plex install as a start did not go well, it seems to be complaining about the name I want to give the Application name,

Then can't find QBitTorrent either.

... not "clear" either how to maybe add external containers, ie the Unifi Controller.

at the moment my base TrueNAS Core OS is on a thumb drive, with all my physical internal drives allocated to two pools.
Easy enough to push a TrueNAS SCALE OS onto a 2nd thumb drive, and boot onto that... well my first expectation would have been it should have been smooth sailing to import my Pools... reading the above, seems not, and then guessing all my settings/sync jobs etc, none will be there, as I also can't pull in a previous config backup (would have been nice if it was able to import it and indicate the following can be restored and the following not...)

G
 

cap

Neophyte
Joined
Mar 17, 2016
Messages
9
Two questions:
Which kernel (version) is used?
Is PowerTOP included?

"Powertop is a tool provided by Intel to enable various powersaving modes in userspace, kernel and hardware. It is possible to monitor processes and show which of them are utilizing the CPU and wake it from its Idle-States, allowing to identify applications with particular high power demands."
https://wiki.archlinux.org/title/Powertop
 

ClassicGOD

Member
Joined
Jul 28, 2011
Messages
121
Which kernel (version) is used?

Code:
Linux version 5.10.70+truenas (root@tnsbuilds01.tn.ixsystems.net) (gcc (Debian 10.2.1-6) 10.2.1 20210110, GNU ld (GNU Binutils for Debian) 2.35.2) #1 SMP Mon Nov 22 21:32:24 UTC 2021


no powertop from what I can tell.
 

truecharts

Member
Joined
Aug 19, 2021
Messages
236

Bruce Ho

Newbie
Joined
Dec 20, 2021
Messages
2
When TrueNAS SCALE 22.02-RC.1, I can't use apt-get update command.

1640047263885.png
 

NugentS

Neophyte Sage
Joined
Apr 16, 2020
Messages
860
TrueNAS is an appliance. Trying to manually update it yourself is an excellent way of breaking things
 

NugentS

Neophyte Sage
Joined
Apr 16, 2020
Messages
860
Try vi instead
 

truecharts

Member
Joined
Aug 19, 2021
Messages
236
TrueNAS is an appliance. Trying to manually update it yourself is an excellent way of breaking things
apt-get update is 100% safe (apt-get update is NOT apt-get upgrade!).
and works fine, the error thrown above is not relevant to apt-get update.

apt-get update && apt-get install powertop works perfectly fine on RC1-2.
 

NugentS

Neophyte Sage
Joined
Apr 16, 2020
Messages
860
apt-get update is 100% safe (apt-get update is NOT apt-get upgrade!).
and works fine, the error thrown above is not relevant to apt-get update.

apt-get update && apt-get install powertop works perfectly fine on RC1-2.
Listen to @truecharts on this one, not me. Could still use vi though
 
Top