How to reset Apps completely?

zyrex

Dabbler
Joined
Nov 20, 2019
Messages
17
I've posted a thread about apps not wanting to start here already, https://www.truenas.com/community/posts/733818/

However, I'm quite done with the troubleshooting and trying different things, since none of it have helped.

Now I'd like to just reset the apps-portion of my Truenas-install completely, so I could get the apps up and running again. I didn't have many, so it would be less hassle.

I tried unsetting the pool, then deleting the ix-applications dataset, rebooting, and choosing a pool when it asks me to. But I'm still greeted with the same error as I've had all along.

{/var/log/k3s_daemon.log}
Jan 25 15:41:31 megabyte k3s[1786492]: E0125 15:41:31.723499 1786492 kubelet.go:1397] "Failed to start ContainerManager" err="failed to initialize top level QOS containers: root container [kubepods] doesn't exist"

and the issue that the k3s-service won't start. It still behaves the same way.

I've waited several hours to see if it needed to settle, but no change.

@morganL :
I never posted hardware in the earlier thread;
System: Supermicro PIO-628U-TR4T+-ST031
MB: X10DRU-i+
CPU: E5-2680 v3
RAM: 64GB DDR4 ECC
 

sretalla

Powered by Neutrality
Moderator
Joined
Jan 1, 2016
Messages
9,703
Sounds to me like a fresh install may be the way forward...

Import your config if really necessary or just import your pool(s) and go from scratch.
 

morganL

Captain Morgan
Administrator
Moderator
iXsystems
Joined
Mar 10, 2018
Messages
2,694
I've posted a thread about apps not wanting to start here already, https://www.truenas.com/community/posts/733818/

However, I'm quite done with the troubleshooting and trying different things, since none of it have helped.

Now I'd like to just reset the apps-portion of my Truenas-install completely, so I could get the apps up and running again. I didn't have many, so it would be less hassle.

I tried unsetting the pool, then deleting the ix-applications dataset, rebooting, and choosing a pool when it asks me to. But I'm still greeted with the same error as I've had all along.

{/var/log/k3s_daemon.log}
Jan 25 15:41:31 megabyte k3s[1786492]: E0125 15:41:31.723499 1786492 kubelet.go:1397] "Failed to start ContainerManager" err="failed to initialize top level QOS containers: root container [kubepods] doesn't exist"

and the issue that the k3s-service won't start. It still behaves the same way.

I've waited several hours to see if it needed to settle, but no change.

@morganL :
I never posted hardware in the earlier thread;
System: Supermicro PIO-628U-TR4T+-ST031
MB: X10DRU-i+
CPU: E5-2680 v3
RAM: 64GB DDR4 ECC
Could you describe your drives and pools...I've seen a potential correlation with larger HDD pools.
 

zyrex

Dabbler
Joined
Nov 20, 2019
Messages
17
Could you describe your drives and pools...I've seen a potential correlation with larger HDD pools.
Right, good point, should've thought of that.

3 pools, quite modest:

NAME SIZE ALLOC FREE CKPOINT EXPANDSZ FRAG CAP DEDUP HEALTH ALTROOT
backuppool 16.4T 13.1T 3.27T - - 56% 80% 1.00x ONLINE /mnt
boot-pool 222G 8.52G 213G - - 0% 3% 1.00x ONLINE -
mediapool 36.4T 25.4T 10.9T - - 5% 69% 1.05x ONLINE /mnt
vaultpool 10.9T 5.86T 5.05T - - 3% 53% 1.00x ONLINE /mnt

ix-applications were on mediapool.

backuppool is 3x6TB WD Reds, CMR, RAIDz1
mediapool is 4x10TB TOSHIBA_MG06ACA10TE, CMR, RAIDz1
vaultpool is 4x3TB HGST_HDN724030ALE640, CMR, RAIDz2
 

zyrex

Dabbler
Joined
Nov 20, 2019
Messages
17
Sounds to me like a fresh install may be the way forward...

Import your config if really necessary or just import your pool(s) and go from scratch.
So I now I actually went to this step, reinstalled my system, without restoring my config just to be sure no old stuff came along, and I still get the same error as I did before. Kinda tired of this now.
 
Top