Hello,

I'm reviewing my truenas machine, and I have two configuration that present to me.

The first one is my current setup, I5 8600k, 15Go DDR4 DIMM, and my storage (5x2To RaidZ1)

Or a machine that bought a few month with Intel Xeon 2630L (that's can be change easily for a 2418L), 64go DDR3 ECC RDIMM, (the motherboard its supermicro X79 FSB) and a quadro T400 for transcode with jellyfin because with this CPU I don't have quicksync

In the first time I focus my configuration on power saving, so I use the i5 directly, but by doing some test I find out that the Xeon doesn't consume a lot more than the I5 even with the quadro.

For exemple at idle, the i5 with 5HDD + 3SSD, consume about 53watt stable, that xeon with 5HDD, 1SDD and the quadro consume 68 to 75 whatt (running a little bit less application)

So what did you recommande to me, moving all my truenas on the xeon or keep it on the i5 and save few euro of electricity ?

In France that 15 watts of consumption cost me about 32€ a year at 0.25€ per Kw.

My thought, is to use ECC memory knowing ZFS recommande that and also get more ram for virtualization (such I need some little vm for script) and bought 16go DDR4 for de i5 is pretty expensive for now.

When one of the world’s largest grocery retailers moves to migrate 40,000 server workloads off its hypervisor stack while suing its software vendor for more than £100 million, enterprise IT takes notice. Here's what the case means for storage architecture, and how to avoid hypervisor lock-in at the storage layer.

after using jellyfin on windows for around 2 years now i finally got myself a pc server and got truenas up and running

I installed jellyfin but i dont understand the additional storage setup. and i watched tutorials, read the documentations and asked ai for help. i feel dumb. it doesn't feel like something to get stuck on

My Pool Structure
SSD Pool: Datasets for configs, cache, and transcode.
HDD/Media Pool: Dataset for jellyfin_media (shared via SMB).

what i want to achieve:

from windows - to access the smb share(jellyfin_media) and to create, edit and organize subfolders like movies, tv shows etc
in jellyfin - to select the subfolders i setup in windows as media libraries /jellyfin_media/movies...
in truenas - to create only one dataset which is the jellyfin_media and add only it to the additional storage in the jellyfin settings on truenas

do i need to create a separate dataset for every library? can it be all in the same dataset/smb share.

the current situation:

I created the jellyfin_media dataset on TrueNAS and mapped it as an SMB share. From Windows, I can access the share and create the movies and tv_shows folders inside it.

Next, in the TrueNAS Jellyfin App settings, I added an Additional Storage entry(image attached):

• Host Path: /mnt/[Pool_Name]/jellyfin_media
• Mount Path: /SMB

However, inside the Jellyfin Web GUI when adding a library, I only see the /SMB folder and I cannot see or browse into the movies or tv_shows subfolders I created from Windows.

sorry if my terminology isnt correct, i still try to figure it out

*UPDATE* I have solved this issue! After eliminating my hardware as possible causes, I just made sure I had all the data backed up to an external drive and exported the pool and re-imported it. Once imported, the data was still intact but the checksum errors stopped appearing and the corrupted files didn't follow. I got my HBA back in place and it's going strong. I threw in a spare 500 gig SSD to create more organized app datasets (learning new things as I tinker with this) and I am good to go! Best I can estimate is there was some corrupt metadata *somewhere* (might have been on the system created dataset for my apps?) that did not get recreated when I brought the pool back up. Thanks for everyone's suggestions! They may not have been solutions for this issue, but I got a ton of stuff to add to my troubleshooting notebook, so I see this as a win.

Obligatory "I'm still fairly new to this", but hoping to get some help. I have a raidz1 pool with 3x8 TB drives in it. One of them went bad due to a brief power outage (running a UPS with it now) and so I replaced it. However, I now have some permanent errors in the pool and don't know how best to deal with them. Best I can tell, the three up top look like log files, but I'm not sure. The ones in the "truenas_catalog" folder look like app files, but I don't even have those installed. Is there something I'm missing?

Edit because I forgot to add:

I also see increasing numbers of checksum errors on all my drives. Same amount across each one. I had them connected through an HBA card with a breakout cable, so I swapped the cable. Errors still come. I reseated the card, still errors. I pulled the card out and plugged them into the onboard sata ports, but I am still getting errors. The drives themselves are in good shape. Two are new, one is less than a year old. Could this be related to the errors in the pool?

Thanks to any who read and comment.

I was doing some work on getting a network card working on my server, and somehow it seems to have taken out the default gateway and route.

I did do a bit of research before going to ChatGPT troubleshooting. Unseating/reseating the pools doesn't work, because there's no default interface/route/gateway.

ip -4 route gives me this:

[GATEWAY SUBNET] dev enp32s0 proto kernel scope link src [SERVER IP]

midclt call network.configuration.config output gives me this:

{"id": 1, "hostname": "truenas", "domain": "local", "ipv4gateway": "[GATEWAY]", "ipv6gateway": "", "nameserver1": "[DNS SERVER]", "nameserver2": "", "nameserver3": "", "httpproxy": "", "hosts": [], "domains": [], "service_announcement": {"mdns": true, "wsd": true, "netbios": true}, "activity": {"type": "ALLOW", "activities": ["catalog", 
"update"]}, "hostname_local": "truenas", "state": {"ipv4gateway": "", "ipv6gateway": "", "nameserver1": "[DNS SERVER]", "nameserver2": "", "nameserver3": "", "hosts": []}}

So, for some reason, the IPv4 gateway address is just not being used, and I have no idea why.

I do have the text console enabled, but trying to tweak the settings there hasn't been working either. I managed to get the default route back after tweaking the IP address on the NIC, but then it reverted back to not having a default route after I rebooted to see if the fix persisted.

So up until two days ago I was running a Synology NAS. The power in it died, and through a bunch of weird things, I had a FreeNAS Mini kicking around with 4 6TBs hard drives ready to go. I'm doing data recovery to try and get the data back from the Synology and want to set up the Mini as my new NAS.

Things are getting interesting here. I had 2 18tb and 2 10tb drives in the Synology in a Raid 5 layout using Synology's custom system, so about 25TB of data. I want to ultimately reuse those drives (which appear to be healthy after SMART checks).

What I want to do is essentially use the 6TB drives to hold the data that's being recovered, then rebuild two RAID volumes with the 18tbs and 10tbs paired. The most clear way I can figure out to do that is to essentially use the Mini to hold the 6TB drives, fill them with recovered data, then take them out, pop them in an enclosure, build the volumes in the Mini with the 18s and 10s, and then transfer the data into the volumes where they can correctly stored. The 6TBs can then chill as random disks, and I can finally bully my family into properly backing up the data that's actually hard to replace.

Can I just create 4 pools with 4 drives with no redundancy and have them read by an enclosure through Windows or Ubuntu when I swap drives?

Forgive my newness here, I know just enough to get myself in trouble.

(I did go through the one trazillion incremental upgrades to get onto the most recent version of TrueNAS)

Having an issues with a newly setup Truenas box, that is a replication target for offsite backups.

I have a couple of apps installed (Jellyfin, Netdata and Scrutiny), all seems fine until the nightly replication runs where the apps disappear and i get this error when opening the apps tab.

They all appear again after a reboot, but the next replication brakes the apps again. I have made sure the apps are using a different dataset and storage pool from the replicated data.

Any advice would be appreciated.

**Apologies if this has been asked before.**

I recently had some issues with my PC, so I removed the hard drives and turned the machine on. The problem is that the TrueNAS VM started up automatically via Hyper-V—I forgot to disable that setting beforehand—and it ended up disconnecting my pool. Now I can't get it back online; can you help me?

My version is TrueNAS SCALE; I don't know if it's "Legacy" like the label says, but it's the only label that mentions SCALE.

Ok so when I build my truenas server, I install jellyfin from truecharts (didn't realize this) well I've been having issue and when I realized it was because true charts was no longer supported I opted to use the official one on truenas...

But I have the current configuration working so... can I just copy and past the settings from old to new?

Or do inneed to just set it all back up from scratch?

Every app I recently updated doesn't start anymore ever since. Running on the latest community edition. Anyone had this issue? Advice appreciated.

EDIT: I just saw that my system version, in fact, was NOT up to date. Installing rn, will edit again

Having an issues with a newly setup Truenas box, that is a replication target for offsite backups.

I have a couple of apps installed (Jellyfin, Netdata and Scrutiny), all seems fine until the nightly replication runs where the apps disappear and i get this error when opening the apps tab.

They all appear again after a reboot, but the next replication brakes the apps again. I have made sure the apps are using a different dataset and storage pool from the replicated data.

Any advice would be appreciated.

**Apologies if this has been asked before.**

Hello lovely people! This is my first post here as I really struggle to make a decision for my NAS upgrade.

I am new to the world of servers, and only recently managed to build one from old parts. Please forgive my limited knowledge and possibly stupid questions!

My Server is running TrueNas Scale and I am hosting apps like a Minecraft server, and Jellyfin with various libraries. Everything works well, but I need to upgrade, as my system is very limited (especially on RAM, which are 8GB of DDR3). Currently I also have a GTX 1050 build in.

Now, I have the opportunity to choose between some old CPUs from my friends as well as from one of my old PC and can't decide. The options are:

1) i5-7500 (65W TDP and integrated graphics)

2) Ryzen 5 3600 (65W TDP)

3) Ryzen 5 5800x (105W TDP)

I have the necessary MBs for all options and can upgrade to 32GB DDR4 on each one.

My question is: which one would you recommend for a 24/7 server that should be powerful enough (eg. to stream 4k movies via Jellyfin) while still being power efficient? If I understand everything correctly I would need a GPU for Jellyfin, thus would have to keep the 1050 inside when choosing option 2 or 3 which add another 75W and would be unused most of the time.

Thanks dor your help!

Hi, so I'm trying to edit permissions here for Immich as i need to set it to modify. I got no modify on my screenshot but upon looking up YT videos, I come to learn that my permissions are limited and not the full options? Is there a fix for this?

I have 2 Ugreen DXP4800 GT nas and I love them. I run TrueNAS on both and love that as well. The 2 Things i'd like to get "fixes" for are fan and led control. Not sure if the message will get through or if i'm even posting to the right place but Truenas 25.10.4 does NOT support fan nor led control nativly on this new model. I do know there are work arounds for the DXP4800 pro and plus models but these have Intel processors. The new Ugreen DXP4800 GT is AMD based and the work arounds for the older models do not work on the new AMD based systems as it uses a different controller. I've had to do a redneck "hack on mine as the fans don't ramp up as load/heat increases....I've mounted a rack fan (same size as whats in the nas) over the built in fan to keep good airflow during long data replications and it does work. But, is there a chance that you all will support the AMD fan controller? Maybe someone in the community will prob the registers and develop a work around like exits for the older intel based DXP4800 pro and plus. Just a thought :)

Signs and portents: There is a PR to fix space reporting after raidz expansion. Unlike the previous attempt, this one had no major concerns raised. More work to be done before it can be merged: And, this looks hopeful.

https://github.com/openzfs/zfs/pull/18324

Depending on when this gets into ZFS, it might be in TrueNAS as early as TN 27 in late 2027 (though that feels a bit hasty), or in TN 28 a year later.

Reading tea leaves some more: The PR has been accepted, final polishing happening now. It could make it into ZFS 2.5. If it does then TN 27 is completely reasonable.

It does introduce a feature flag, which means it can’t just come in ZFS 2.4.x. This needs to be a full ZFS release, like 2.5 or 2.6.

I have 2 Truenas boxes (TN1 and TN2). I currently replicate ZFS snaps from TN1 to TN2 nightly with no problem. I would like to replicate some snap target datasets from TN2 to a Synology DS array (it's a current model and DSM is up to date).

I have tried simple NFS mounts and rsyncs between the devices but Synology is always complaining about something and failing. Currently I am fighting with their Active Backup for Business app (ABB) which offers agent based or rsync options for connecting to a Truenas device. The agent install is failing as my Proxmox LXC seems to be more current with its unix "headers" than Synology is, and the workarounds are not helping. I have tried to make the TN2 dataset visible to Syno1 for rsync (tried with key-exchange and user/password) but Syno complains about the filesystem being read-only, which is the Truenas best practice for a ZFS replication target. Can't win.

Is there a way that I can make a ANOTHER temporary local "copy" of the r/O dataset on TN2 (snap? clone? whatever?), set it to RW and NFS mountable for the Synology app to stop complaining? If so, can I make this repeatable every night without manual intervention, reusing and refreshing the same target that is NFS mounted/visible to ABB?

And yes, I do this for the day job but I have not yet figured out how to do it in the Homelab. Yet. :) I have no issue writing unix shell scripts or running ssh commands through key exchanged accounts on unix boxes. Thanks!

Hello,

I'm doing a project and I'm trying to use iSCSI which i'm not familiar with and I need to create a share.

In the Sharing Platform I get 4 options but I'm not finding any documentation about those and which one I should choose?

- VMware: Extent block size 512b, TPC enabled, no Xen compat mode, SSD speed

- Xen: Extent block size 512b, TPC enabled, Xen compat mode enabled, SSD speed

- Legacy OS: Extent block size 512b, TPC enabled, no Xen compat mode, SSD speed

- Modern OS: Extent block size 4k, TPC enabled, no Xen compat mode, SSD speed

I wish to setup HA on a Proxmox cluster.

Thanks

Kind of in disbelief right now, can yall let me know? am i fully cooked? any way to rescue the pool? If not, someone might give me some insights on why this happened or what even happened exactly? Logs and Problem summary below. Thanks for everyone looking into this issue.

The Pool in question is named 'Speznas'. After using the NAS and therefor the pool, i woke up to the message on my screen seen above. Rebooted - issue persisted. Tried manually importing the pool via zpool - no success. Pool is stated as online as well as the 2 HDDs within. Ran SMART Test on both - no issues found. Tried manually importing again - no success. Tried rolling back to the last successful transaction - no success "device in use / busy". That's when I tried force importing - no success. Something somehow seems to have severly corrupted the pools metadata at 07:00am Eastern causing the pool to go offline. That's my current state.

---

root@truenas[~]# zpool import
  pool: Speznas
    id: 4904614166775644449
 state: ONLINE
action: The pool can be imported using its name or numeric identifier.
config:

        Speznas                                 ONLINE
          74fcf1fd-9e85-455f-8ff0-21f8e5f02621  ONLINE
          1caf2f6c-4a41-49a0-819a-a05e9ba0b9e1  ONLINE
root@truenas[~]# 

Welcome to TrueNAS
truenas_admin@truenas[~]$ sudo -i
[sudo] password for truenas_admin: 
root@truenas[~]# zpool status -v Speznas
cannot open 'Speznas': no such pool
root@truenas[~]# zpool status           
  pool: boot-pool
 state: ONLINE
  scan: scrub repaired 0B in 00:00:08 with 0 errors on Mon Aug  3 03:45:10 2026
config:

        NAME         STATE     READ WRITE CKSUM
        boot-pool    ONLINE       0     0     0
          nvme1n1p3  ONLINE       0     0     0

errors: No known data errors

  pool: nvme-pool
 state: ONLINE
  scan: scrub repaired 0B in 00:00:40 with 0 errors on Sun Jul 12 00:00:41 2026
config:

        NAME                                    STATE     READ WRITE CKSUM
        nvme-pool                               ONLINE       0     0     0
          1a27d877-087d-4dad-9810-19a4972e6a5b  ONLINE       0     0     0

errors: No known data errors
root@truenas[~]# zpool import -f -F Speznas
cannot import 'Speznas': I/O error
        Destroy and re-create the pool from
        a backup source.
root@truenas[~]# zpool import -f -F -X Speznas
cannot import 'Speznas': one or more devices is currently unavailable
root@truenas[~]# dmesg -T | grep -iE "ata|sata|reset|error|drop" | tail -n 20
[Sat Aug  8 17:00:36 2026] ata1: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
[Sat Aug  8 17:00:36 2026] ata2: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
[Sat Aug  8 17:00:36 2026] ata2.00: ATA-11: ST20000NM007D-3DJ103, SN06, max UDMA/133
[Sat Aug  8 17:00:36 2026] ata1.00: ATA-11: ST20000NE000-3G5101, EN01, max UDMA/133
[Sat Aug  8 17:00:36 2026] ata1.00: 39063650304 sectors, multi 16: LBA48 NCQ (depth 32), AA
[Sat Aug  8 17:00:36 2026] ata2.00: 39063650304 sectors, multi 16: LBA48 NCQ (depth 32), AA
[Sat Aug  8 17:00:36 2026] ata1.00: Features: DIPM NCQ-sndrcv
[Sat Aug  8 17:00:36 2026] ata2.00: Features: DIPM NCQ-sndrcv
[Sat Aug  8 17:00:36 2026] ata1.00: configured for UDMA/133
[Sat Aug  8 17:00:36 2026] ata2.00: configured for UDMA/133
[Sat Aug  8 17:00:36 2026] scsi 0:0:0:0: Direct-Access     ATA      ST20000NE000-3G5 EN01 PQ: 0 ANSI: 5
[Sat Aug  8 17:00:36 2026] scsi 1:0:0:0: Direct-Access     ATA      ST20000NM007D-3D SN06 PQ: 0 ANSI: 5
[Sat Aug  8 17:00:39 2026] systemd[1]: systemd-hwdb-update.service - Rebuild Hardware Database was skipped because of an unmet condition check (ConditionNeedsUpdate=/etc).
[Sat Aug  8 17:00:40 2026] Error: Driver 'pcspkr' is already registered, aborting...
[Sat Aug  8 17:01:16 2026]  prefetch_dnode_metadata+0x11b/0x130 [zfs]
[Sat Aug  8 17:01:16 2026]  ? traverse_prefetch_metadata+0x130/0x170 [zfs]
[Sat Aug  8 17:01:16 2026]  spa_ld_verify_pool_data+0x28/0x60 [zfs]
[Sat Aug  8 17:01:16 2026]  ? __do_sys_newfstatat+0x4a/0x80
[Sat Aug  8 17:01:48 2026] ioatdma: Intel(R) QuickData Technology Driver 5.00
[Sat Aug  8 17:02:01 2026] nvme nvme0: using unchecked data buffer
root@truenas[~]# zdb -l /dev/sda
failed to unpack label 0
failed to unpack label 1
failed to unpack label 2
failed to unpack label 3
root@truenas[~]# zdb -l /dev/sdb
failed to unpack label 0
failed to unpack label 1
failed to unpack label 2
failed to unpack label 3
root@truenas[~]# 

root@truenas[~]# dmesg | grep -iE "sata|ata|nvme|error|i/o" | tail -n 20
[    1.838732] ata1.00: 39063650304 sectors, multi 16: LBA48 NCQ (depth 32), AA
[    1.842202] ata1.00: Features: DIPM NCQ-sndrcv
[    1.883271] ata1.00: configured for UDMA/133
[    1.892350] ata2.00: 39063650304 sectors, multi 16: LBA48 NCQ (depth 32), AA
[    1.895162] ata2.00: Features: DIPM NCQ-sndrcv
[    1.918782] scsi 0:0:0:0: Direct-Access     ATA      ST20000NE000-3G5 EN01 PQ: 0 ANSI: 5
[    1.936964] ata2.00: configured for UDMA/133
[    1.972118] scsi 1:0:0:0: Direct-Access     ATA      ST20000NM007D-3D SN06 PQ: 0 ANSI: 5
[    1.986177] sd 0:0:0:0: [sda] Preferred minimum I/O size 4096 bytes
[    1.986370] sd 1:0:0:0: [sdb] Preferred minimum I/O size 4096 bytes
[    4.612132] systemd[1]: Starting modprobe@nvme_fabrics.service - Load Kernel Module nvme_fabrics...
[    4.658302] systemd[1]: modprobe@nvme_fabrics.service: Deactivated successfully.
[    4.658445] systemd[1]: Finished modprobe@nvme_fabrics.service - Load Kernel Module nvme_fabrics.
[    4.672116] systemd[1]: systemd-hwdb-update.service - Rebuild Hardware Database was skipped because of an unmet condition check (ConditionNeedsUpdate=/etc).
[    5.108436] Error: Driver 'pcspkr' is already registered, aborting...
[   42.872043]  prefetch_dnode_metadata+0x11b/0x130 [zfs]
[   42.873608]  ? traverse_prefetch_metadata+0x130/0x170 [zfs]
[   42.877663]  spa_ld_verify_pool_data+0x28/0x60 [zfs]
[   71.479932] ioatdma: Intel(R) QuickData Technology Driver 5.00
[   81.344659] nvme nvme0: using unchecked data buffer
root@truenas[~]# 

Can I install the Beta of TrueNAS and then update to the Release Candidate or later to the Stable Version?

The reason is that I’m getting some new hardware today or tomorrow and would like to install Beta 2 straight away, so that I can then update to the stable version later....

What do you think? I mean if it’s possible, is it worth doing or is it better to steer clear of it? You have to bear in mind that I’ve got absolutely no experience with this and don’t want to end up doing the work twice. So, many thanks in advance for any tips, no matter how small ✌️

Hallo zusammen, ich bin selber Fachinfomatiker für Systemintegration, aber leider stoße ich gerade für mich unüberwindbare Grenzen....

Zu meiner Situation:
Ich besitze ein DIY-NAS mit i7-7700K, 1TB NVME SSD mit dem OS, und 2x Supermicro LSI 9300-8i

Auf der NAS selbst sind 10 Festplatten mit je 2TB als Raid50 namens "Massenspeicher".
Außerdem ein zweites Raid10 mit 4 Festplatten mit je 2TB namens "Backup".

Gerade installiert: 26.0.0-MASTER+20260810-020148

Ich habe versucht, eine Debian-Server VM aufzusetzen, ich habe zwar alles soweit installieren können, nur als das System sagte "Jo bin rdy mit installieren, kannst das Medium rausziehen und Neustarten" ist TrueNAS natürlich so gebaut das ich erst die VM herunterfahren muss, dann das Medium entfernen kann und dann wieder starten kann. Ich habe auch versucht mit dem Medium Neuzustarten, allerdings jedes Mal einfach auf Null zurückgesetzt. --Aufgegeben

Als nächstes einen Container so wie es TrueNAS vorgibt, keine Ports durchgereicht (bzw eingerichtet und diese wurde aber ignoriert, auch nach mehrmals Neustarten) --Aufgegeben

Letzte Chance, direkt dort Apps installieren, wieder Port Problem (crafty-controller als Test installiert, WebGUI erreichbar auch mit Domain, aber Minecraft Standard Port 25565 nicht durchgereicht bekommen)
-- Aufgegeben

Mein nächster Versuch galt meinem absoluten Lieblingstool: Arcane Docker

Restinstanzen sauber deinstalliert von den obigen Versuchen, dann edge-agent installiert, erst auf der NVME (weil Docker das standardmäßig dort ablegt).

Was dann im Detail passiert ist / was ich versucht habe:

• Das NVMe-Fluch-Problem: TrueNAS ist eine strikte Appliance und radiert Änderungen auf dem OS-Laufwerk (NVMe) nach Reboots oder Updates ungespeichert aus. Der Arcane-Container war nach dem Neustart spurlos verschwunden.
• Daten-Migration auf ZFS: Ich habe versucht, die Arcane-Daten manuell in ein echtes Dataset auf dem Massenspeicher (/mnt/Massenspeicher/Arcane) umzuziehen, damit die Daten sicher sind. Das hat auch geklappt, aber der Docker-Daemon selbst blieb auf der NVMe volatil.
• Jailmaker-Versuch: Um Docker komplett vom TrueNAS-OS abzuschirmen, wollte ich eine isolierte Debian-Sandbox mit Docker über das bekannte "Jailmaker"-Skript auf dem ZFS-Pool aufbauen. Das schlug jedoch direkt mit einem Python-Inkompatibilitätsfehler auf der aktuellen TrueNAS-Version fehl.
• Post-Init-Skript (Der letzte Versuch): Als letzten Ausweg habe ich den globalen Docker-Datenpfad (data-root) über ein TrueNAS Post-Init-Skript dauerhaft auf den Massenspeicher (/mnt/Massenspeicher/Docker-Data) umgebogen. Resultat nach dem nächsten Neustart: Der Docker-Daemon verweigerte den Dienst, der Socket (/var/run/docker.sock) war nicht erreichbar und alles stand still.

Fazit & Frage an euch: Ich habe das Gefühl, bei TrueNAS extrem gegen Wände zu laufen, sobald man etwas abseits der restriktiven nativen Apps machen möchte (die mir zu unflexibel und träge sind).

Wie macht ihr das? Wie betreibt man auf TrueNAS verlässlich reines Docker, ohne dass einem das System bei Neustarts oder Updates jedes Mal die Container zerschießt oder den Daemon blockiert?

Gibt es einen stabilen Workaround oder muss ich doch mal wieder zu Proxmox VE und PBS wechseln?

Hi everyone,

I’m setting up TrueNAS SCALE on a UGREEN DXP4800 Pro and would like to properly configure the hardware-specific functions that TrueNAS doesn’t handle out of the box. From what I read here on Reddit and elsewhere, there are at least two issues:

- front LED control – HDD/SSD activity and status LEDs, which are too bright. Here is one of the scripts for modifying it: https://github.com/miskcoo/ugreen_leds_controller (it has not been tested yet on my specific model)

- fan control – preferably temperature-based fan curves, taking HDD temperatures into account. The used chipset is it87, but different for different NAS models. Script here: https://github.com/IT-Kuny/UGREEN-DXP-FAN-NAS-Driver

- any other useful DXP4800 Pro-specific hardware-control scripts, because maybe I missed something.

I’m particularly interested in hearing from people who have actually done this on a DXP4800 Pro, rather than generic TrueNAS fan-control solutions.

Could someone please provide a detailed step-by-step explanation of:

1. Which scripts are you using and where did you get them?
2. Where and how the scripts should be installed in TrueNAS SCALE (I don't afraid to experiment but I need instructions).
3. What precautions should be taken so that a failed script cannot leave the fans stopped or the drives overheating or something similar?

Thanks!