Skip to:

  1. Skip to Jira Navigation
  2. Skip to Side Navigation
  3. Skip to Main Content

Thanks for using the TrueNAS Community Edition issue tracker! TrueNAS Enterprise users receive direct support for their reports from our support portal.

Issues

Select view

Select search mode

 
1-9 of 9
1 of 9

Crashes during App installs

User Configuration Error

Description

Truenas upon booting fails to start ix-etc.service but starts post boot if manually started:

systemctl status ix-etc.service

× ix-etc.service - Generate TrueNAS /etc files

Loaded: loaded (/lib/systemd/system/ix-etc.service; enabled; preset: enabled)

Active: failed (Result: exit-code) since Sun 2024-11-10 21:30:09 NZDT; 1h 8min ago

Main PID: 2435 (code=exited, status=1/FAILURE)

Truenas crashes upon attempting to install Docker apps:

/var/log/syslog:

Nov 10 16:05:36 truenas kernel: br-8be3508b657d: port 1(vethb01a9ae) entered disabled state

Nov 10 16:05:36 truenas kernel: vethb01a9ae: entered allmulticast mode

Nov 10 16:05:36 truenas kernel: vethb01a9ae: entered promiscuous mode

Nov 10 16:05:36 truenas kernel: br-8be3508b657d: port 1(vethb01a9ae) entered blocking state

Nov 10 16:05:36 truenas kernel: br-8be3508b657d: port 1(vethb01a9ae) entered forwarding state

Nov 10 16:05:36 truenas kernel: br-8be3508b657d: port 1(vethb01a9ae) entered disabled state

Nov 10 16:05:36 truenas containerd[4515]: time="2024-11-10T16:05:36.973863734+13:00" level=info msg="loading plugin \"io.containerd.event.v1.publisher\"..." runtime=io.containerd.runc.v2 type=io.containerd.event.v1

Nov 10 16:05:36 truenas containerd[4515]: time="2024-11-10T16:05:36.974168032+13:00" level=info msg="loading plugin \"io.containerd.internal.v1.shutdown\"..." runtime=io.containerd.runc.v2 type=io.containerd.internal.v1

Nov 10 16:05:36 truenas containerd[4515]: time="2024-11-10T16:05:36.974201050+13:00" level=info msg="loading plugin \"io.containerd.ttrpc.v1.task\"..." runtime=io.containerd.runc.v2 type=io.containerd.ttrpc.v1

Nov 10 16:05:36 truenas containerd[4515]: time="2024-11-10T16:05:36.974416628+13:00" level=info msg="loading plugin \"io.containerd.ttrpc.v1.pause\"..." runtime=io.containerd.runc.v2 type=io.containerd.ttrpc.v1

Nov 10 16:05:36 truenas kernel: list_add corruption. next->prev should be prev (ffff93d2d2c0f788), but was 0000000000000000. (next=ffff93d7639d9a50).

Nov 10 16:05:36 truenas kernel: ------------[ cut here ]------------

Nov 10 16:05:36 truenas kernel: kernel BUG at lib/list_debug.c:29!

Nov 10 16:09:12 truenas kernel: microcode: updated early: 0x718 -> 0x71a, date = 2020-03-24

Nov 10 16:09:12 truenas kernel: Linux version 6.6.44-production+truenas (root@tnsbuilds01.tn.ixsystems.net) (gcc (Debian 12.2.0-14) 12.2.0, GNU ld (GNU Binutils for Debian) 2.40) #1 SMP PREEMPT_DYNAMIC Mon Nov 4 13:50:00 UTC 2024

Nov 10 16:09:12 truenas kernel: Command line: BOOT_IMAGE=/ROOT/24.10.0.1@/boot/vmlinuz-6.6.44-production+truenas root=ZFS=boot-pool/ROOT/24.10.0.1 ro libata.allow_tpm=1 amd_iommu=on iommu=pt kvm_amd.npt=1 kvm_amd.avic=1 intel_iommu=on zfsforce=1 nvme_core.multipath=N

Nov 10 16:09:12 truenas kernel: BIOS-provided physical RAM map:

Nov 10 16:09:12 truenas kernel: BIOS-e820: [mem 0x0000000000000000-0x000000000009dfff] usable

Nov 10 16:09:12 truenas kernel: BIOS-e820: [mem 0x0000000000100000-0x000000007d2effff] usable

Nov 10 16:09:12 truenas kernel: BIOS-e820: [mem 0x000000007d2f0000-0x000000007d31bfff] reserved

Nov 10 16:09:12 truenas kernel: BIOS-e820: [mem 0x000000007d31c000-0x000000007d35afff] ACPI data

sudo sudo cat /var/log/syslog | grep 0000000000000000

Nov 8 18:31:57 truenas kernel: BIOS-e820: [mem 0x0000000000000000-0x000000000009dfff] usable

Nov 8 18:31:57 truenas kernel: Faking a node at [mem 0x0000000000000000-0x000000407fffffff]

Nov 9 16:01:54 truenas kernel: BIOS-e820: [mem 0x0000000000000000-0x000000000009dfff] usable

Nov 9 16:01:54 truenas kernel: Faking a node at [mem 0x0000000000000000-0x000000407fffffff]

Nov 9 17:16:19 truenas kernel: BIOS-e820: [mem 0x0000000000000000-0x000000000009dfff] usable

Nov 9 17:16:19 truenas kernel: Faking a node at [mem 0x0000000000000000-0x000000407fffffff]

Problem/Justification

None

Impact

None
Pinned fields
Click on the next to a field label to start pinning.

Details

Assignee

Reporter

Labels

Impact

High

Components

Fix versions

Affects versions

Priority

More fields

Katalon Platform

Created November 10, 2024 at 10:27 AM
Updated November 11, 2024 at 7:02 PM
Resolved November 11, 2024 at 7:02 PM
Configure

Activity

Show:

Bug Clerk November 11, 2024 at 7:02 PM

This issue has now been closed. Comments made after this point may not be viewed by the TrueNAS Teams. Please open a new issue if you have found a problem or need to re-engage with the TrueNAS Engineering Teams.

Bonnie Follweiler November 11, 2024 at 2:14 PM

Good Morning .

This ticket has been moved into our queue to review.

An engineering representative will update with any further questions or details in the near future.

Mike S November 11, 2024 at 6:42 AM
Edited

RESOLVED!

Issue 1 - So, I had plugged in a GTX 1660 Ti awaiting for the power lead to arrive. With the PCIe giving it's base power already,, the GPU was detected but spitting out an error regarding incorrect power / missing cable. Installing apps invokes the checks involved for passing through the GPU. I've temporarily unplugged the GFX card until the power lead arrives.

Nov 11 19:04:56 truenas kernel: NVRM: GPU 0000:42:00.0: GPU does not have the necessary power cables connected.
Nov 11 19:04:56 truenas kernel: NVRM: GPU 0000:42:00.0: RmInitAdapter failed! (0x24:0x1c:1568)
Nov 11 19:04:56 truenas kernel: NVRM: GPU 0000:42:00.0: rm_init_adapter failed, device minor number 0

Issue 2 - This one didn't make sense but ultimately unplugging the USB I used to install TrueNAS allowed the ix-etc.service to start everytime across reboots.

The 2 issues weren't tied to each other.

Is there a possible solution of implementing a check on the GPU power so that it can somehow ignore the GPU config until this is corrected. Every time an APP is installed, it reloads the Docker config and was moaning of the GPU briefly before rebooting.

Mike S November 11, 2024 at 5:11 AM

That mem issue doesn’t appear now, so guessing it was the USB stick contributing to that. Is what I have highlighted the issue of crashing?

Nov 11 17:46:38 truenas systemd[1]: Starting docker.service - Docker Application Container Engine...
Nov 11 17:46:38 truenas dockerd[12496]: time="2024-11-11T17:46:38.979328346+13:00" level=info msg="Starting up"
Nov 11 17:46:39 truenas dockerd[12496]: time="2024-11-11T17:46:39.043455453+13:00" level=info msg="[graphdriver] trying configured driver: overlay2"
Nov 11 17:46:39 truenas dockerd[12496]: time="2024-11-11T17:46:39.059945127+13:00" level=info msg="Loading containers: start."
Nov 11 17:46:39 truenas dockerd[12496]: time="2024-11-11T17:46:39.719514505+13:00" level=info msg="Default bridge (docker0) is assigned with an IP address 172.16.0.0/24. Daemon option --bip can be used to set a preferred IP address"
Nov 11 17:46:39 truenas dockerd[12496]: time="2024-11-11T17:46:39.911034335+13:00" level=info msg="Loading containers: done."
Nov 11 17:46:39 truenas dockerd[12496]: time="2024-11-11T17:46:39.933496712+13:00" level=info msg="Docker daemon" commit=cc13f95 containerd-snapshotter=false storage-driver=overlay2 version=27.1.1
Nov 11 17:46:39 truenas dockerd[12496]: time="2024-11-11T17:46:39.933694237+13:00" level=info msg="Daemon has completed initialization"
Nov 11 17:46:40 truenas dockerd[12496]: time="2024-11-11T17:46:40.009338644+13:00" level=info msg="API listen on /run/docker.sock"
Nov 11 17:46:40 truenas systemd[1]: Started docker.service - Docker Application Container Engine.
Nov 11 17:47:01 truenas cron[4301]: (systemmiddlewared) RELOAD (/etc/cron.d/middlewared)
Nov 11 17:47:40 truenas dhclient[3898]: DHCPDISCOVER on eno1 to 255.255.255.255 port 67 interval 3
Nov 11 17:47:43 truenas dhclient[3898]: DHCPDISCOVER on eno1 to 255.255.255.255 port 67 interval 8
Nov 11 17:47:51 truenas dhclient[3898]: DHCPDISCOVER on eno1 to 255.255.255.255 port 67 interval 15
Nov 11 17:48:06 truenas dhclient[3898]: DHCPDISCOVER on eno1 to 255.255.255.255 port 67 interval 16
Nov 11 17:48:06 truenas dhclient[3853]: DHCPDISCOVER on eno3 to 255.255.255.255 port 67 interval 8
Nov 11 17:58:39 truenas syslog-ng[4092]: syslog-ng starting up; version='3.38.1'
Nov 11 17:56:54 truenas kernel: microcode: updated early: 0x718 -> 0x71a, date = 2020-03-24
Nov 11 17:56:54 truenas kernel: Linux version 6.6.44-production+truenas (root@tnsbuilds01.tn.ixsystems.net) (gcc (Debian 12.2.0-14) 12.2.0, GNU ld (GNU Binutils for Debian) 2.40) #1 SMP PREEMPT_DYNAMIC Fri Nov 8 18:37:36 UTC 2024

Mike S November 11, 2024 at 4:41 AM

I think I’ve cleared the issue with ix-etc.service. I unplugged 2 x USB sticks (one included the installer) that were left in during install etc. I’ve removed both of those and this service now starts upon boot. Don’t know how or why that changed that but may be coincidence - go figure.

As for the crashing, that is still happening.

Loading...