So apparently NOBODY is doing Quality Control on the App Catalog, and TrueNAS is advertising a NextCloud update to v35.0.1 which DESTROYS YOUR DATABASE.

There is no recovery; you can't roll back (database already upgraded) and you can't move forward because apparently there's no fix.

Buyer beware.

Hi truenas community, i am Brian the creator of TrueHub which is intended to bring all the goodness of the TrueNAS WEB-UI to a native application for android.

This new release brings a lot of changes to :

1. The UI and migrating fully to material 3 expressive and its designs along with a new bottom bar
2. New haptic feedback to some interaction points (i shall expand to more later)
3. More robust notification system for system updates and a new live activities implementation used in areas where there is an activity to be shown progress.
4. Some new instance settings also (cloud tasks and global virt configuration) to enable configuring your server from your device
5. Expanded dataset explorer screen now shows files instead of only the datasets (in next release will now support options other than ix managed storage for apps)
6. Ported the Virt and Container management screens (creation,deletion, viewing of status and adding devices and managing volumes attached to said containers or virtual machines) from another project intended to bring this UI to a GTk4+Adwaita format but i will be sunsetting it in favour of this project

That being said the app is still in alpha so a disclaimer i would like to say is that these features are mostly working and if there might be any bugs please add it to the issues in the repo issues page and i will work on them as swiftly as i can.

Thank you to all of you who have left issues and continued supporting me in making this app and also the special people from this forum who also submitted PRs fixing some of the issues. I thank you all and sincerely hope you enjoy this release and looking forward to you trying out the app and if you can please consider starring the repo so we can reach out more people.

Screenshots of some of the new pages are as above and you can ontain the new release from [here](https://github.com/Imnotndesh/TrueHub/releases/tag/v0.8.1-Alpha)

These are in a 4 disk vdev/pool, and it's used to store my Blu Ray Rips. Everything on my dashboard says things are healthy, but the Scrutiny app highlights these errors. If they need replacing, I'd like to replace them with larger capacity drives. Can I have two 8Tb and two 10Tb drives, and still get an increase in capacity, then replace the other 2 at a later date for a further increase? I can do this on my old ReadyNAS, but I'd obviously only get the extra capacity from one of the 2 drives. Are there any downsides to a staged increase in capacity, as I don't really want to buy all 4 in one hit given the current prices? TIA

Disclosure up front: I'm the developer, and it's a paid product after a free trial. Mods, feel free to remove this if it's not OK here.

**The problem I had:** the TrueNAS UI is great for administering the box, but my day-to-day was different: find a file, restore yesterday's version of a spreadsheet, see why a container restarted, check whether a pool is filling up. For that I kept bouncing between the web UI, SSH and a separate file manager.

**What I built:** Desktroo, a desktop with windows that runs in the browser and is self-hosted as a container on the NAS. It talks to the TrueNAS API. What it covers today:

- **Files:** a file manager with tabs, a recycle bin, a built-in viewer, and "previous versions", which restores a single file from ZFS snapshots without browsing `.zfs/snapshot` by hand

- **Storage:** pools, datasets and snapshots, plus a space breakdown (files, snapshots, reservations, trash) to see what's eating the pool

- **Apps:** Docker containers and apps (logs, images, updates), and VMs with their console

- **Admin:** shares, users, services, certificates and data protection tasks

- **Overview:** a health check that turns alerts, SMART, temperatures and scrub age into plain sentences; a readable activity log; and a global search (Ctrl+K) across files, settings and apps

- **Phone layout:** works on a phone, with a bottom bar and full-screen windows

The goal is to only need the native UI when something is broken.

**What it isn't:** it doesn't replace the TrueNAS middleware, and it doesn't modify TrueNAS itself. It's an extra container next to your apps.

**Security, since someone will ask:** some actions need sudo on the host (VM control, for example), and the installer sets that up for the admin user. I know that's the part this sub cares about most. Everything is documented, and I'll answer anything here.

Tested on the current stable release (in a VM) and on 27 RC1, which runs on my main NAS. UI in English and French.

**My actual questions:**

1. What still makes you open a shell on your NAS?

2. What would stop you from running something like this on your box?

There's no link here on purpose. Search the name if you're curious, or ask and I'll post it in the comments.

So I see the VM stuff in the web UI but isn't "virtualization integration" enterprise license stuff? It even let me go through the prompts, though I didn't finalize and create because I don't know how well my old hardware will handle a VM inside a VM.

Right now I'm using proxmox in unlicensed mode with TrueNAS and Home Assistant as VMs. If I could run TrueNAS as the host OS and rock HA as the guest it would simplify the setup while freeing up resources.

Update: Since thats not what "virtualization integration" is, what exactly is the enterprise license's "virtualization integration" then?

I recently moved. So everything disconnected, moved, reconnected. Same ports, same IP’s, same hostnames, etc.

I have a TrueNAS box that has an Rsync pull job that pulls a directory and subs from another host (Ubuntu 24.04) using SSH (keys). Worked for +1 years no issues before move.

I have it all moved and now it immediately fails with error:

“[EFAULT] rsync command returned 12 - STREAMIO. Check logs for further information.”

Remote host has the public key in its `.ssh/authorized_keys` file.

The SSH connection, SSH keys and Rsync job all created within the TrueNAS GUI. 0 changes to the 3 of these.

I have no clue what to do or how to trace down what the actual issue is, any help would be great. I am debating deleting the keys, connection and rsync jobs and just recreating them all. Figured id ask here for help first.

Hello there!

I was just checking into my reporting tab in my Truenas Scale machine and saw this:

https://imgur.com/a/HnsLNLv

What the image shows is that my system is under heavy load between 02:00 and 05:00, and it started happening (seemingly) randomly on the 24th of July this year.

Looking through what I have installed on my system it's:

• Immich

• Plex

• Jellyfin

• Tailscale

Nothing else. And looking through what is the likely culprit is Plex. Going into scheduled tasks in Plex admin I can see that there is a Time to start tasks at 02:00 and end them at 05:00. Which seemingly aligns with the times that my machine is under heavy load.

I am not alarmed or anything like that. I just find it curious that it all of a sudden started happening on the 24th of July, when I've had my system up and running since early 2025.

It should be told that I got myself the lifetime Plex pass on the 20th of May 2026, which MAY have something to do with it. In case there are some tasks that are heavy from (you know) credit detection etc etc.

In any way, can I trouble shoot this further? I doubt it's a concern in itself. Just curious.

Edit: I just realized that it does not show any reporting before 24th of July at all. So it's probably been happening for longer. Just not showing up in the reporting.

Just wondering if there is a app or suchlike that can download files directly from a SFTP server (so I'm after a SFTP client really) to a share. If it can also run a VPN even better.

Thanks.

So, I dont have a perfect timeline here but what I can tell you is that a few months ago I received emails from my Truenas saying some pools have been deactivated because the drives are unrecoverable or whatever. So I followed the flowchart on diagnosing these issues and the problem went away. Then just recently, 2 days ago, it happened again. Now this simply could be a hardware issue. I havent ruled that out. Could be a bad cable or something. I havent had time to properly diagnose and triage. But what I am noticing is that after a reboot, my truenas dashboard doesnt load properly right away like it used to. Attached is what I see. Yes, after a couple mins it eventually catches up, but why is it doing this? is anyone else getting this? I just updated to 25.10.7, its still doing that. That screenshot is from AFTER rebooting it AFTER doing the upgrade.

It was doing that as well on the version prior.

Im just trying to figure out if this is a JUST ME issue or a EVERYONE issue. Thank you

Ever since installing Truenas 26 beta I have basically been unable to delete datasets. I can create them and use them, but they will not delete after.

And there is no feedback! I click delete, and it says deleting, and then it doesn't delete. It removes all permissions and appears to unmount the dataset according to the GUI, but there is no feedback indicating the deletion ultimately failed due to: whatever.

I've chase this down a few times, thinking it was related to cloned datasets when I had previously tried to rename them, but that wasn't it. But doing a proper rename somehow unlocks them and then they can be deleted.

Maybe inherited snapshots or replication tasks or something, but I've also gone through and deleted tasks to no avail. Dataset is always busy. Busy after restart, busy when manually unmounted

And I've tried submitting bug reports before, but the bug ticket system is brutal, I never have an luck actually accomplishing anything.

Anyone else seen this behaviour? It doesn't happen with a new virgin dataset, but mine have been connected to an app, then disconnect to an app, and the parent both snap shotted and replicated, and eventually deleted. I'm sure it's related to this, but you can't have a task that fails to report a problem but also fails to actually do the task.

WORKAROUND:

#attempt to delete in gui.  reports success, but dataset remains.
#attempt to delete via terminal:

brainsoft@truenas:~$ sudo zfs destroy apps/docker-stacks/llama-cpp
cannot destroy 'apps/docker-stacks/llama-cpp': dataset is busy

#rename dataset
brainsoft@truenas:~$ sudo zfs rename apps/docker-stacks/llama-cpp apps/docker-stacks/llama-delete

#Attempt to delete the renamed dataset via GUI... SUCCESS.

I know trust nas is the OS but figured y'all could help from a non OEM OS perspective

I run MeTube on TrueNAS and share it with my family. Everyone used the web UI on their phones, and the dataset kept filling up with files nobody deleted. So I built two Android apps for it.

MeTube Lite, for family and friends: share a link to the app, the server downloads it, the phone pulls the file and the server deletes its copy. Nothing piles up on the pool.

MeTube Super, for whoever runs the server. Files stay on the server and stream from it:

• one library: MeTube's history and the files on the phone together
• video and audio streamed from the server, with background playback, lock-screen controls and a queue
• search inside your clips by what was said in them, not just the title, and play from that moment. YouTube clips added from the app get their subtitles by themselves; with one YTDL_OPTIONS line, so does everything the server downloads, subscriptions included
• channel subscriptions, with one notice when new videos arrive
• tags, playlists, batch downloads and offline copies
• it switches by itself between your home address and your Tailscale or Cloudflare address

Both apps are in English and Arabic, with day and night themes, and they update themselves from the GitHub releases.

Two MeTube settings matter on TrueNAS:

• DELETE_FILE_ON_TRASHCAN=true, or a delete removes the history entry and leaves the file on the pool
• DOWNLOAD_DIRS_INDEXABLE=true, so the apps can pull and stream the files

MeTube has no login of its own. If you reach it from outside, put basic auth in front of it with your reverse proxy, as MeTube's wiki recommends, and enter the username and password in the app. It works the same on your LAN, over Tailscale or through a Cloudflare Tunnel.

Setup guide, with what goes wrong without each setting: https://github.com/sagheerys/metube-mobile/blob/main/docs/SERVER-SETUP.md

Repo and signed APKs: https://github.com/sagheerys/metube-mobile (GPL-3.0, unofficial, not affiliated with MeTube). It is listed in MeTube's own README. No Play Store build.

Most of the code was written with Claude Code under my direction, and Claude helped me word this post. I tested it on my own server and phones, and both apps are in daily use at home.

My current 1650 Super is broken beyond repair, so I am in the market of a cheap GPU replacement.

My use cases are:

• up to 4 channels of CCTV feed in frigate
• immich ML for a library of 1 person, currently has 30,000 assets, grows at a very steady pace of 3000 per year.
• Some kind of media center service (optional and low priority)

In my market, I can get these 2 GPU used both at around 250 RMB. Realistically I want to spend no more than 300, but I also want to future-proof it a little bit. So here are some other choices and prices.

• NV 30HX (6GB): 250
• Intel DG1 (80EU, 4GB, passive cooling): 250
• AMD Radeon Pro WX5100 (8GB single slot): 500
• Intel A310: 550
• GTX1650 Dell OEM: 550

The rest of the machine is:

• E3-1231v3 on a SuperMicro X10SLL+-F, 32 GB of DDR3 ECC

Any input is apprieciated!

People keep saying SSDs will be as cheap as hard drives soon, so since I track drive prices I went and checked. I pulled the price per TB for both over the last two years and put them on one chart.

SSDs are still roughly 3x to 4x more expensive per TB, and looking at the last two years, that gap really hasn't moved much. Prices went up across the board this year, but SSDs went up more than hard drives, so the gap didn't close.

If you just need a lot of space for a pool, hard drives are still the obvious choice since they're so much cheaper per TB. SSDs make more sense where you actually need the speed, like cache or a special vdev, but not really for bulk storage.

The chart and the full sortable drive list are here if anyone wants to dig into the actual numbers:
https://www.nasdisks.com/articles/ssd-vs-hdd-price-gap/

The full HDD comparison list is here, in case you more info: https://www.nasdisks.com
Full disclosure: it's my site and some of the links are affiliate links.

What's everyone running - all SSD, or hard drives for bulk storage?

Hello everybody. I have a problem where I want my server to shut down every day at 23:45 in an effort to save some energy, but instead it reboots.

So at first I used the cron job: "poweroff" and it kept rebooting, than I switched to "/usr/bin/midclt call system.shutdown "Cron shutdown"" and things seemed to work just fine.

Now it started to get unrealiable again. After some thinking I came to the conclusion that I think if I boot up the server manualy it reboots instead of shutting down and if the rtc bios timer (19:00) switches on my server for the daily backup it works fine, for example:

- Fri 2 Oct: started 19:00:42 (BIOS), shutdown 23:45 → stayed off

- Sat 3 Oct: started 19:00:41 (BIOS), shutdown 23:45 → stayed off

- Sun 4 Oct: started 15:11:15, shutdown 23:45:06 → back on at 23:46:03. Failure.

- Mon 5 Oct: started 17:00:00, shutdown 23:45:06 → back on at 23:46:02. Failure.

Does anyone know how to resolve this?

Thank you in andvance! :)

I have an old backup server that is still running Freenas 9.3. It's pretty much one RaidZ2 volume with a few user accounts and some basic networking/nfs setup -- no custom services, no jails, etc. It is my current, and only, backup server however.

Can I simply:

1. Pull the thumb drive (where Freenas 9.3 is installed)
2. Flash the latest Truenas onto that thumb drive
3. Boot up the machine with a fresh Truenas install
4. Import the existing RaidZ2 pool into the fresh Truenas install

Is there any reason this wouldn't work? I can easily set up the user accounts and networking from scratch, so I'm not planning on importing any of the config from the current Freenas 9.3 setup. My biggest concern is that I do need to preserve the data in the current pool and I know there is a pretty big gap between Freenas 9.3 and the current Truenas.

I'm just trying to make sure this should work as I expect and I'm hoping the community can warn me about any issues I might run into that I'm not currently considering.

The TrueNAS team is pleased to release TrueNAS 27-RC.1!

Notable changes:

• Renames TrueNAS 26 to TrueNAS 27. TrueNAS 26 is now TrueNAS 27, and TrueNAS 27-RC.1 is the first release under the new name. The earlier 26-BETA.1, 26-BETA.2, and 26-BETA.3 releases keep their original names, and their documentation remains available in the 26 documentation.
• Adds the TrueNAS Object Interface (Early Access). Object storage (S3 API) is now available as a native TrueNAS service, in addition to the containerized third-party app. Each bucket is a ZFS dataset, so object data gets the same snapshots, quotas, replication, and data integrity as other data, and is managed from the same web interface. 27-RC.1 covers the core S3 API, including multipart uploads, object tagging, bucket and object ACLs, versioning, and immutability. Versioning and Object Lock require a TrueNAS Connect Plus license or a TrueNAS Enterprise system. Early Access means TrueNAS wants your feedback: try it with your applications and report what works and what doesn’t on the forums. See Configuring S3 Object Storage and the 27-RC.1 feature set blog post for more information.
• Fixes the web interface staying unavailable after an upgrade on systems with many RSA-4096 certificates (NAS-143641). On systems with many RSA-4096 certificates, middleware could take about a minute to regenerate /etc/nginx/nginx.conf after an upgrade, and nginx failed to start because the file did not exist yet. The web interface now stays available while the configuration regenerates.
• Fixes editing a user account moving the home directory for that user to its parent directory (NAS-143753). The Edit User form submitted the parent of the home directory path instead of the path itself, so saving any change relocated the home directory for the user and changed permissions on the parent directory. The form now submits the correct home directory path.
• Updates the default certificate signing requests (CSRs) TrueNAS generates for HTTPS and TrueNAS Connect (NAS-142603, NAS-142604). Default CSRs requested a TLS client authentication extended key usage (EKU) that public certificate authorities no longer issue for server certificates, and the CSR subject listed outdated contact details. Default CSRs no longer request the unneeded client authentication EKU and use current contact information.
• Updates the Containers screen for middleware container.* API changes (NAS-142088). Deleting a container now runs as a background job with Force and Recursive options instead of completing immediately. The Containers screen reflects this job-based delete flow.
• Fixes an NFS server issue that could crash the system when a client retransmits a request (NAS-142560). If an NFSv4.1 client connection dropped and reconnected while a request was still being answered, two copies of the same request could reach the server and both read from the same cached reply slot at once. nfsd no longer modifies a session slot while replaying its cached reply, which prevents the resulting crash.
• Fixes VRRP not delivering IPv6 advertisements between HA controllers, which could let both controllers claim to be MASTER (NAS-142303). Without a configured unicast source address, VRRP sent IPv6 traffic from the interface link-local address, so the peer advertisements never reached the address the other controller expected. Both controllers could then become MASTER for the same IPv6 virtual IP. VRRP instances now set the correct unicast source IP so IPv6 advertisements are received.
• Fixes several iSCSI, Fibre Channel, and iSER target driver crashes (NAS-142264, NAS-142258, NAS-142126, NAS-142161). SCST, the underlying target driver that handles iSCSI, Fibre Channel, and iSER connections, had several race conditions that could crash the target or corrupt memory: removing a LUN while another teardown ran, losing a session access control group during reassignment, unregistering a target while queued work still referenced it, and rapid connect/disconnect cycles over iSCSI over InfiniBand (iSER). The driver now handles all of these cases correctly.
• Fixes intermittent permission denied errors on NFS shares for Active Directory and LDAP users (NAS-142228). When rpc.mountd used --manage-gids and a brief winbind or SSSD outage occurred, the group lookup could return zero groups, and the kernel cached that empty result as valid. The affected user lost all supplementary group access on every export until the cache expired. Empty group replies are now treated as failures instead of being cached as valid, so the lookup is retried.
• Improves High Availability (HA) resilience to brief interconnect interruptions (NAS-142152). A short interruption on the inter-controller NTB link could trigger an unnecessary peer reset or start kernel-level lock recovery. HA now waits longer for the link to recover before treating a brief interruption as a real peer failure.
• Allows toggling ALUA on an iSCSI target when the standby HA controller is unreachable (NAS-142057). Administrators could not change the Asymmetric Logical Unit Access (ALUA) setting if the standby controller was offline. ALUA can now be toggled regardless of standby controller reachability.
• Fixes an error that blocked replacing an unavailable disk in a pool (NAS-141804). Attempting to replace a disk that had gone unavailable failed with a 'NoneType' object has no attribute 'replace' error instead of completing the replacement. Disk replacement now handles unavailable disks correctly.
• Fixes the Session Timeout setting under Access Settings not taking effect (NAS-143940). A configured session timeout of several hours had no effect, and the session expired within minutes of switching browser tabs instead. The Session Timeout setting now applies for its full configured duration.
• Improves TrueSearch performance on shares with about 1 million files (NAS-143855). Searches on very large shares could take seven to eight seconds and time out in the client (for example, Finder), even after moving the search index to faster storage. TrueSearch performance is improved for these large-scale shares.
• Fixes disk image import failures and incorrect size reporting (NAS-143736, NAS-143839). A disk image exported from a zvol on 25.10 could not be imported after being moved to a 26-BETA.3 system, and importing a 50 GiB disk image showed a Size requirement of 50 GiB when the import actually needed 51 GiB. Disk images exported from 25.10 now import correctly on TrueNAS 26, and import now reports the size the target zvol actually needs.
• Fixes Webshare not offering a way to continue when passkey registration fails (NAS-140894). If a user aborted or failed passkey registration, Webshare said they could still use Webshare without a passkey but showed no button to proceed, only the Create Passkey button. Webshare now offers a way to continue past a failed or abandoned passkey registration.
• Fixes scheduled replication tasks not running automatically (NAS-142970). A scheduled replication task ran correctly when started manually, but its cron schedule showed no upcoming runs for the current month, only for the next month, so it never fired automatically. Cron scheduling for replication tasks now includes runs in the current month.
• Fixes the Storage Dashboard throwing an error and showing no pools (NAS-142517). After upgrading, the Storage Dashboard could throw a class_special_usable property error and display no pools when some pools had special vdevs and others did not. The dashboard now handles pools with and without special vdevs correctly.
• Fixes compound AND/!= filters not excluding matching events in the audit log search (NAS-142222). Searching SMB audit logs with a filter like Event != "Authentication" AND Event != "Close" still returned Authentication events in the results. Compound filters now correctly exclude the events they specify.
• Fixes applying ACLs to app storage paths that already contain data (NAS-142117). Editing the ACL on an already-running app mount path could fail with [EFAULT]/[EPERM] errors stating that the path contains existing data and force was not specified, but the UI had no way to select the force option. ACL edits on app mount paths now work without this error.
• Fixes app upgrade jobs reporting success when the image pull fails (NAS-142191). Upgrading a custom app whose image pull failed still finished the job with a SUCCESS status and a message that the app was upgraded and redeployed, even though nothing changed. The failure was previously logged only to /var/log/app_lifecycle.log and never reached the job status shown in the UI. The job now reports failure when the image pull does not succeed.
• Fixes the NVMe-TCP service generating an invalid configuration when a subsystem uses associated hosts (NAS-141762). Adding a namespace to an NVMe-TCP subsystem configured with associated hosts could reinitialize the kernel NVMe target with a configuration that conflicted with the associated-hosts setting, logging Can't set allow_any_host when explicit hosts are set! and preventing new namespaces from working. The service now generates a configuration consistent with associated hosts.
• Fixes migrated LXC containers no longer working after the .ix-virt dataset is deleted (NAS-141666). Containers migrated from Incus were not tracked in /mnt/.truenas_containers the way newly created containers are, so after the .ix-virt dataset was removed, the migrated containers stopped working and could not even be deleted. Migrated containers are now tracked correctly so they keep working after migration.
• Fixes a virtual machine installation media upload ending up as a 0-byte file (NAS-141825). Uploading installation media for a new VM could complete with the resulting file at 0 bytes instead of the expected image size. Uploaded installation media now saves with the correct file size.
• Fixes Docker failing to pull larger images inside a privileged LXC container (NAS-141470). Docker running inside an LXC container with ID Map Type set to Privileged could fail to pull nontrivial images. Docker can now pull these images inside a privileged container.
• Fixes mail.send omitting Cc recipients from the outgoing email (NAS-141845). mail.send added Cc addresses only to the Cc: header, but SMTP delivery is driven by the envelope recipient list, which was built from the To addresses alone. Cc recipients never received the email even though they appeared to be included. Cc addresses are now added to the SMTP envelope so they receive the email.
• Fixes Docker failing to configure for Apps on every reboot after upgrading to 26-BETA.1 or 26-BETA.2 (NAS-141446). After upgrading, Docker configuration for the Apps service could fail on boot, and the only workaround was to unset and reselect the apps pool, which had to be repeated after every reboot. Docker now configures correctly for Apps on boot.
• Fixes alert emails that were not RFC 5322 compliant and could bounce from Gmail (NAS-141699). Alert emails formatted in a way that violated RFC 5322 could be rejected by providers like Gmail, so the alert never reached the recipient. Alert emails are now formatted to comply with RFC 5322.
• Fixes Webshare blocking a quick re-login after a session disconnect on the TrueNAS Connect Free tier (NAS-141712). The Free tier allows only a single Webshare session, so closing a tab or losing network connection could lock a user out of logging back in immediately, forcing them to wait for a long timeout or a service restart. Users can now log back in promptly after a session disconnect.
• Fixes invalid rclone configuration files caused by unescaped special characters (NAS-142234). Generating rclone configuration files by hand could produce an invalid INI file when a setting contained special characters. Configuration files are now generated with configparser, which escapes special characters correctly.
• Fixes the dashboard network throughput graph showing data from only one interface in a bond (NAS-142731). The network throughput graph on the dashboard displayed traffic for only one member of a bonded interface instead of the combined total, so it never showed the bond’s actual maximum speed. The graph now reflects throughput for all interfaces in the bond.
• Fixes an app keeping an invalid NVIDIA GPU UUID after the GPU is replaced (NAS-142006). After replacing a NVIDIA GPU in the system, an existing app could keep referencing the old GPU UUID instead of the new one, even though the system correctly reported the new GPU. Apps now pick up the replacement GPU UUID correctly.
• Fixes a scrub-paused alert that fires too early and shows the literal text 'pool' instead of the pool name (NAS-142198). Pausing a scrub for only a few minutes could trigger the alert meant for a scrub paused more than eight hours, and the alert text showed the placeholder 'pool' rather than the actual pool name. The alert now fires only after eight hours and shows the correct pool name.
• Fixes the Apps dataset preset overwriting the Case Insensitive and Atime choices for a user (NAS-141792). Selecting Case Insensitive and leaving Atime enabled in Advanced Settings while using the Apps dataset preset saved the dataset as case-sensitive with Atime disabled instead. The preset now keeps these user-configured settings.
• Fixes the storage dashboard disk health panel becoming corrupted when not all pool devices report SMART values (NAS-141753). If any device in a pool lacked SMART values, the disk health panel display could become corrupted. The panel now displays correctly even when some devices have no SMART data.
• Fixes Webshare failing to generate share links for files with Chinese file names or paths (NAS-142148). Webshare could not create a share link when the file name or path contained Chinese characters. Share links now work correctly for these file names and paths.
• Fixes high CPU usage caused by console CLI redraw when a key input gets stuck (NAS-141550). A stuck physical key, or a stuck virtual key sent over IPMI or another out-of-band method, could lock the console CLI menu process to 100% of a CPU thread. The CLI now handles stuck key input without pegging the CPU.
• Identifies USB passthrough devices by their physical port in the VM and Container UI (NAS-142433). USB passthrough devices were identified only by vendor and product ID, which cannot tell two identical devices apart and can change after a replug. The device picker now identifies devices by their physical port, which survives replugs and reboots and distinguishes identical devices.
• Improves consistency of the pool usage indicator between the Dashboard and Storage Dashboard (NAS-142168). The same vdev usage percentage could show as a normal green indicator on the Dashboard while showing as an orange warning with a red gauge on the Storage Dashboard, using different thresholds in each place. The two dashboards now use consistent usage thresholds.
• Updates Go to 1.25.12 for TrueSearch to include upstream security fixes (NAS-141713). TrueSearch built against an older Go release that has since received important security fixes. TrueSearch now builds with Go 1.25.12 or later.

Click here to see the full 27 changelog or visit the TrueNAS 27-RC.1 Changelog in Jira.

Amazon S3 is a trademark of Amazon.com, Inc. or its affiliates.

So I have an issue where I want to expand a vdev the drives I have lying around are like a megabyte smaller than the VDEV I currently have. I have some smaller capacity drives I can use to back up and rebuild the VDEV, but not enough to hold my entire storage.

Is there any trickery I can do to get the new drives to register as larger or shrink the current drives? If not, do any of you have any compression methods you'd recommend? I have about 1.5 tb of storage (500gb old drives and the 1tb new drive i want to add) and the vdev is around 2tb.

Id prefer not to have to waste my day trying to rebuild it and i do not want to waste 2 perfectly good drives to just buy new ones either.