forked from HomeLab/unraid-mcp
chore: enhance project metadata, tooling, and documentation
**Project Configuration:** - Enhance pyproject.toml with comprehensive metadata, keywords, and classifiers - Add LICENSE file (MIT) for proper open-source distribution - Add PUBLISHING.md with comprehensive publishing guidelines - Update .gitignore to exclude tool artifacts (.cache, .pytest_cache, .ruff_cache, .ty_cache) - Ignore documentation working directories (.docs, .full-review, docs/plans, docs/sessions) **Documentation:** - Add extensive Unraid API research documentation - API source code analysis and resolver mapping - Competitive analysis and feature gap assessment - Release notes analysis (7.0.0, 7.1.0, 7.2.0) - Connect platform overview and remote access documentation - Document known API patterns, limitations, and edge cases **Testing & Code Quality:** - Expand test coverage across all tool modules - Add destructive action confirmation tests - Improve test assertions and error case validation - Refine type annotations for better static analysis **Tool Improvements:** - Enhance error handling consistency across all tools - Improve type safety with explicit type annotations - Refine GraphQL query construction patterns - Better handling of optional parameters and edge cases This commit prepares the project for v0.2.0 release with improved metadata, comprehensive documentation, and enhanced code quality. Co-authored-by: Claude <noreply@anthropic.com>
This commit is contained in:
Jacob Magar
176
docs/research/raw/blog-7.2.0.md
Normal file
176
docs/research/raw/blog-7.2.0.md
Normal file
@@ -0,0 +1,176 @@
|
||||
* [Unraid News](https://unraid.net/blog)
|
||||
|
||||
|
||||
29 October 2025
|
||||
|
||||
Unraid OS 7.2.0 Stable is Now Available
|
||||
=======================================
|
||||
|
||||
Unraid 7.2.0 delivers a **fully responsive web interface, expanded filesystem support, a built-in, open-source API**, **ZFS RAIDZ Expansion,** and much more!
|
||||
|
||||
|
||||
|
||||
**Your Server: More Responsive, Secure, and More Flexible than ever.**
|
||||
|
||||
Building on months of testing and feedback, this release brings major quality-of-life improvements for new and seasoned users alike. Whether you're upgrading your homelab or deploying at scale, this release brings more control, compatibility, and confidence to every system.
|
||||
|
||||
We want to give a huge thanks to the _over 5,000 beta testers_ that helped bring this release to Stable.
|
||||
|
||||
**Fully Responsive WebGUI**
|
||||
---------------------------
|
||||
|
||||
Unraid now adapts seamlessly to any screen size. The redesigned WebGUI ensures smooth operation across desktops, tablets, and mobile devices making it easier than ever to manage your server from anywhere, with any device.
|
||||
|
||||
### See the Responsive Webgui in action
|
||||
|
||||
**Expand Your RAIDZ Pools and Bring Every Drive With You**
|
||||
----------------------------------------------------------
|
||||
|
||||
### **ZFS RAIDZ Expansion**
|
||||
|
||||
You can now expand your single-vdev RAIDZ1/2/3 pools, one drive at a time!
|
||||
|
||||
1. Stop the array
|
||||
2. On _**Main → Pool Devices,**_ add a slot to the pool
|
||||
3. Select the appropriate drive. _Note: must be at least as large as the smallest drive in the pool._
|
||||
4. Start the array
|
||||
|
||||
### See How RAIDZ Expansion Works
|
||||
|
||||
### **External Drive Support: ext2/3/4, NTFS, exFAT**
|
||||
|
||||
Alongside XFS, BTRFS, and the ZFS file systems, Unraid now supports ext2 / ext3 / ext4, NTFS, and exFAT out of the box, making it easier to import data from external sources or legacy systems.
|
||||
|
||||
This means you can _create an array or single device pool with existing drives formatted in Ext2/3/4 or NTFS, and you can format drives in Ext4 or NTFS._
|
||||
|
||||
### Learn How Unraid Handles ext, NTFS, and exFAT Out of the Box
|
||||
|
||||
Cyber Weekend is Coming
|
||||
-----------------------
|
||||
|
||||
Don’t miss our biggest sale of the year November 28-December 1st. Subscribe to the [Unraid Digest](https://newsletter.unraid.net/)
|
||||
and be the first to know all of the details!
|
||||
|
||||
[Subscribe](https://newsletter.unraid.net/)
|
||||
|
||||
**Unraid API**
|
||||
--------------
|
||||
|
||||
The [**Unraid API**](https://docs.unraid.net/API/)
|
||||
is now integrated directly into Unraid OS, giving developers and power users new ways to interact with their systems.
|
||||
|
||||
The new **Notifications panel** is the first major feature built on this foundation, and over time, more of the webGUI will transition to use the API for faster, more dynamic updates.
|
||||
|
||||
The API is fully [**open source**](https://github.com/unraid/api)
|
||||
, providing direct access to system data and functionality for building automations, dashboards, and third‑party integrations. It also supports [**external authentication (OIDC)**](https://docs.unraid.net/API/oidc-provider-setup/)
|
||||
for secure, scalable access.
|
||||
|
||||
### See the Unraid API in Action!
|
||||
|
||||
Learn More about the Unraid API
|
||||
-------------------------------
|
||||
|
||||
* #### [Follow along the Unraid API Roadmap](https://docs.unraid.net/API/upcoming-features/)
|
||||
|
||||
* #### [See current apps using the Unraid API](https://discord.com/channels/216281096667529216/1375651142704566282)
|
||||
|
||||
|
||||
**Additional Improvements and Fixes**
|
||||
-------------------------------------
|
||||
|
||||
### **Storage & Array**
|
||||
|
||||
* Two-device ZFS pools default to mirrors; use RAIDZ1 for future vdev expansion
|
||||
* New _File System Status_ shows if drives are mounted and/or empty
|
||||
* Exclusive shares now exportable via NFS
|
||||
* Restricted special share names (homes, global, printers)
|
||||
* Improved SMB config (smb3 directory leases = no) and security settings UX
|
||||
* Better handling for parity disks with 1MiB partitions
|
||||
* BTRFS mounts more reliably with multiple FS signatures
|
||||
* New drives now repartitioned when added to parity-protected arrays
|
||||
* Devices in SMART test won’t spin down
|
||||
* Cleaner handling of case-insensitive share names and invalid characters
|
||||
* ZFS vdevs now display correctly in allocation profiles
|
||||
|
||||
### **VM Manager**
|
||||
|
||||
* Console access now works even when user shares are disabled
|
||||
* Single quotes are no longer allowed in the Domains storage path
|
||||
* Windows 11 defaults have been updated for better compatibility
|
||||
* Cdrom Bus now defaults to IDE for i440fx and SATA for Q35 machines
|
||||
* Vdisk locations now display properly in non-English languages
|
||||
* You'll now see a warning when adding a second vdisk if you forget to assign a capacity
|
||||
|
||||
### **WebGUI**
|
||||
|
||||
* Network and RAM stats now shown in human-readable units
|
||||
* Font size and layout fixes
|
||||
* Better error protection for PHP-based failures
|
||||
|
||||
### Miscellaneous **Improvements**
|
||||
|
||||
* Better logging during plugin installs
|
||||
* Added safeguards to protect WebGUI from fatal PHP errors
|
||||
* Diagnostics ZIPs are now further anonymized
|
||||
* Resolved crash related to Docker container CPU pinning
|
||||
* Fixed Docker NAT issue caused by missing br\_netfilter
|
||||
* Scheduled mover runs are now properly logged
|
||||
|
||||
### **Kernel & Packages**
|
||||
|
||||
* Linux Kernel 6.12.54-Unraid
|
||||
* Samba 4.23.2
|
||||
* Updated versions of openssl, mesa, kernel-firmware, git, exfatprogs, and more
|
||||
|
||||
**Plugin Compatibility Notice**
|
||||
-------------------------------
|
||||
|
||||
To maintain stability with the new responsive WebGUI, the following plugins will be removed during upgrade if present:
|
||||
|
||||
* **Theme Engine**
|
||||
* **Dark Theme**
|
||||
* **Dynamix Date Time**
|
||||
* **Flash Remount**
|
||||
* **Outdated versions of Unraid Connect**
|
||||
|
||||
Please update all other plugins—**especially Unraid Connect and Nvidia Driver**—before upgrading!
|
||||
|
||||
Unraid 7.2.0
|
||||
------------
|
||||
|
||||
Important Release Links
|
||||
|
||||
* #### [Docs](https://docs.unraid.net/unraid-os/release-notes/7.2.0/)
|
||||
|
||||
Version 7.2.0 Full Release Notes
|
||||
|
||||
* #### [Forum Thread](https://forums.unraid.net/topic/194610-unraid-os-version-720-available/)
|
||||
|
||||
Unraid 7.2.0 Forum Thread
|
||||
|
||||
* #### [Known Issues](https://docs.unraid.net/unraid-os/release-notes/7.2.0/#known-issues)
|
||||
|
||||
See the Known Issues for the Unraid 7.2 series
|
||||
|
||||
* #### [Learn More](https://docs.unraid.net/unraid-os/system-administration/maintain-and-update/upgrading-unraid/#standard-upgrade-process)
|
||||
|
||||
Ready to Upgrade? Visit your server’s Tools → Update OS page to install Unraid 7.2.0.
|
||||
|
||||
|
||||
|
||||
|
||||
Pricing
|
||||
-------
|
||||
|
||||
With affordable options starting at just $49, we have a license for everyone.
|
||||
|
||||
[Buy Now](https://account.unraid.net/buy)
|
||||
|
||||
|
||||
|
||||
Try before you buy
|
||||
------------------
|
||||
|
||||
Not sure if Unraid is right for you? Take Unraid for a test drive for 30 days—no credit card required.
|
||||
|
||||
[Free Trial](https://unraid.net/getting-started)
|
||||
139
docs/research/raw/blog-api-bounty.md
Normal file
139
docs/research/raw/blog-api-bounty.md
Normal file
@@ -0,0 +1,139 @@
|
||||
* [Unraid News](https://unraid.net/blog)
|
||||
|
||||
|
||||
5 September 2025
|
||||
|
||||
Introducing the Unraid API Feature Bounty Program
|
||||
=================================================
|
||||
|
||||
We’re opening new doors for developers and power users to directly shape the Unraid experience, together.
|
||||
|
||||
The new [Unraid API](https://docs.unraid.net/API/)
|
||||
has already come a long way as a powerful, open-source toolkit that unlocks endless possibilities for automation, integrations, and third-party applications. With each release, we’ve seen the creativity of our community take center stage, building tools that extend the Unraid experience in ways we never imagined.
|
||||
|
||||
Now, we’re taking it one step further with the [**Unraid API Feature Bounty Program**.](https://unraid.net/feature-bounty)
|
||||
|
||||
### **What Is the Feature Bounty Program?**
|
||||
|
||||
The bounty program gives developers (and adventurous users) a way to directly contribute to the Unraid API roadmap. Here’s how it works:
|
||||
|
||||
1. **Feature Requests Become Bounties:** We post specific API features that would benefit the entire Unraid ecosystem.
|
||||
2. **You Build & Contribute:** Developers who implement these features can claim the bounty, earn recognition, and a monetary reward.
|
||||
3. **Community Driven Growth:** Instead of waiting for features to arrive, you can help build them, get rewarded, and help the Unraid community.
|
||||
|
||||
Our core team focuses on high-priority roadmap items. Bounties give the community a way to help accelerate other highly requested features by bringing more ideas to life, faster, with recognition and reward for those who contribute.
|
||||
|
||||
API Feature Bounty Program Details
|
||||
----------------------------------
|
||||
|
||||
You can turn feature requests into reality, get rewarded for your contributions, and help grow the open-source Unraid API ecosystem.
|
||||
|
||||
[Learn More](https://unraid.net/feature-bounty)
|
||||
|
||||
### **The Open-Source Unraid API**
|
||||
|
||||
Alongside the bounty program, we’re thrilled to highlight just how open and flexible the Unraid API has become. Whether you’re scripting via the CLI, building automations with the API, or integrating with external identity providers through OAuth2/OIDC, the API is designed to be transparent and extensible.
|
||||
|
||||
API Docs
|
||||
--------
|
||||
|
||||
Learn about how to get started with the Unraid API.
|
||||
|
||||
[Start Here](https://docs.unraid.net/API/)
|
||||
|
||||
OIDC Provider Setup
|
||||
-------------------
|
||||
|
||||
Configure OIDC providers for SSO authentication in the Unraid API using the web interface.
|
||||
|
||||
[OIDC](https://docs.unraid.net/API/oidc-provider-setup/)
|
||||
|
||||
Upcoming API Features
|
||||
---------------------
|
||||
|
||||
The roadmap outlines completed and planned features for the Unraid API. Features and timelines may change based on development priorities and community feedback.
|
||||
|
||||
[Learn More](https://docs.unraid.net/API/upcoming-features/)
|
||||
|
||||
Community API Projects in Action
|
||||
--------------------------------
|
||||
|
||||
The power of an open API is best shown by what you build with it. Here are just a few highlights from the community so far!
|
||||
|
||||
|
||||
|
||||
### [Unraid Mobile App](https://forums.unraid.net/topic/189522-unraid-mobile-app/)
|
||||
|
||||
by S3ppo
|
||||
|
||||
|
||||
|
||||
### [Homepage Dashboard Widget](https://discord.com/channels/216281096667529216/1379497640110063656)
|
||||
|
||||
by surf108
|
||||
|
||||
|
||||
|
||||
### [Home Assistant Integration](https://github.com/domalab/ha-unraid-connect)
|
||||
|
||||
by domalab
|
||||
|
||||
|
||||
|
||||
[Unloggarr (AI-powered log analysis)](https://github.com/jmagar/unloggarr)
|
||||
|
||||
---------------------------------------------------------------------------
|
||||
|
||||
by jmagar
|
||||
|
||||
|
||||
|
||||
[nzb360 Mobile App (Android)](https://play.google.com/store/apps/details?id=com.kevinforeman.nzb360&hl=en_US)
|
||||
|
||||
--------------------------------------------------------------------------------------------------------------
|
||||
|
||||
by nzb360dev
|
||||
|
||||
|
||||
|
||||
[API Show and Tell](https://discord.com/channels/216281096667529216/1375651142704566282)
|
||||
|
||||
-----------------------------------------------------------------------------------------
|
||||
|
||||
Show off your project or see them all in action on our Discord channel!
|
||||
|
||||
Get Involved
|
||||
------------
|
||||
|
||||
Whether you’re a developer looking to contribute, or a user eager to see your most-wanted features come to life, the new Unraid API Feature Bounty Program is your chance to help shape the future of Unraid. The Unraid API is open and the bounties are live!
|
||||
|
||||
* #### [Feature Bounty Program](https://unraid.net/feature-bounty)
|
||||
|
||||
Learn More about the Feature Bounty Program
|
||||
|
||||
* #### [Claim Bounties](https://github.com/orgs/unraid/projects/3/views/1)
|
||||
|
||||
Browse the live bounty board
|
||||
|
||||
* #### [API Info](https://docs.unraid.net/API/)
|
||||
|
||||
Read the API Docs
|
||||
|
||||
|
||||
|
||||
|
||||
Pricing
|
||||
-------
|
||||
|
||||
With affordable options starting at just $49, we have a license for everyone.
|
||||
|
||||
[Buy Now](https://account.unraid.net/buy)
|
||||
|
||||
|
||||
|
||||
Try before you buy
|
||||
------------------
|
||||
|
||||
Not sure if Unraid is right for you? Take Unraid for a test drive for 30 days—no credit card required.
|
||||
|
||||
[Free Trial](https://unraid.net/getting-started)
|
||||
259
docs/research/raw/connect-overview.md
Normal file
259
docs/research/raw/connect-overview.md
Normal file
@@ -0,0 +1,259 @@
|
||||
[Skip to main content](https://docs.unraid.net/unraid-connect/overview-and-setup#__docusaurus_skipToContent_fallback)
|
||||
|
||||
On this page
|
||||
|
||||
**Unraid Connect** is a cloud-enabled companion designed to enhance your Unraid OS server experience. It makes server management, monitoring, and maintenance easier than ever, bringing cloud convenience directly to your homelab or business setup.
|
||||
|
||||
Unraid Connect works seamlessly with Unraid OS, boosting your server experience without altering its core functions. You can think of Unraid Connect as your remote command center. It expands the capabilities of your Unraid server by providing secure, web-based access and advanced features, no matter where you are.
|
||||
|
||||
With Unraid Connect, you can:
|
||||
|
||||
* Remotely access and manage your Unraid server from any device, anywhere in the world.
|
||||
* Monitor real-time server health and resource usage, including storage, network, and Docker container status.
|
||||
* Perform and schedule secure online flash backups to protect your configuration and licensing information.
|
||||
* Receive notifications about server health, storage status, and critical events.
|
||||
* Use dynamic remote access and server deep linking to navigate to specific management pages or troubleshoot issues quickly.
|
||||
* Manage multiple servers from a single dashboard, making it perfect for users with more than one Unraid system.
|
||||
|
||||
Unraid Connect is more than just an add-on; it's an essential extension of the Unraid platform, designed to maximize the value, security, and convenience of your Unraid OS investment.
|
||||
|
||||
[**Click here to dive in to Unraid Connect!**](https://connect.myunraid.net/)
|
||||
|
||||
Data collection and privacy[](https://docs.unraid.net/unraid-connect/overview-and-setup#data-collection-and-privacy "Direct link to Data collection and privacy")
|
||||
|
||||
-------------------------------------------------------------------------------------------------------------------------------------------------------------------
|
||||
|
||||
**Click to see what data is collected and how we handle it**
|
||||
|
||||
Unraid Connect prioritizes your privacy and transparency. Here’s what you need to know about how we handle your data:
|
||||
|
||||
### What data is collected and why
|
||||
|
||||
When your server connects to Unraid.net, it establishes a secure connection to our infrastructure and transmits only the necessary data required for a seamless experience in the Unraid Connect Dashboard. This includes:
|
||||
|
||||
* Server hostname, description, and icon
|
||||
* Keyfile details and flash GUID
|
||||
* Local access URL and LAN IP (only if a certificate is installed)
|
||||
* Remote access URL and WAN IP (if remote access is turned on)
|
||||
* Installed Unraid version and uptime
|
||||
* Unraid Connect plugin version and unraid-api version/uptime
|
||||
* Array size and usage (only numbers, no file specifics)
|
||||
* Number of Docker containers and VMs installed and running
|
||||
|
||||
We use this data solely to enable Unraid Connect features, such as remote monitoring, management, and notifications. It is not used for advertising or profiling.
|
||||
|
||||
### Data retention policy
|
||||
|
||||
* We only keep the most recent update from your server; no past data is stored.
|
||||
* Data is retained as long as your server is registered and using Unraid Connect.
|
||||
* To delete your data, simply uninstall the plugin and remove any SSL certificates issued through Let's Encrypt.
|
||||
|
||||
### Data sharing
|
||||
|
||||
* Your data is **not shared with third parties** unless it is necessary for Unraid Connect services, such as certificate provisioning through Let's Encrypt.
|
||||
* We do not collect or share any user content, file details, or personal information beyond what is specified above.
|
||||
|
||||
For more details, check out our [Policies](https://unraid.net/policies)
|
||||
page.
|
||||
|
||||
Installation[](https://docs.unraid.net/unraid-connect/overview-and-setup#installation "Direct link to Installation")
|
||||
|
||||
----------------------------------------------------------------------------------------------------------------------
|
||||
|
||||
Unraid Connect is available as a plugin that requires Unraid OS 6.10 or later. Before you start, make sure your server is connected to the internet and you have the [Community Applications](https://docs.unraid.net/unraid-os/using-unraid-to/run-docker-containers/community-applications/)
|
||||
plugin installed.
|
||||
|
||||
To install Unraid Connect:
|
||||
|
||||
1. Navigate to the **Apps** tab in the Unraid WebGUI.
|
||||
2. Search for **Unraid Connect** and proceed to install the plugin. Wait for the installation to fully complete before closing the dialog.
|
||||
3. In the top right corner of your Unraid WebGUI, click on the Unraid logo and select **Sign In**.
|
||||
|
||||
|
||||
|
||||
4. Sign in with your Unraid.net credentials or create a new account if necessary.
|
||||
5. Follow the on-screen instructions to register your server with Unraid Connect.
|
||||
6. After registration, you can access the [Unraid Connect Dashboard](https://connect.myunraid.net/)
|
||||
for centralized management.
|
||||
|
||||
note
|
||||
|
||||
Unraid Connect requires a myunraid.net certificate for secure remote management and access. To provision a certificate, go to _**Settings → Management Access**_ in the WebGUI and click **Provision** under the Certificate section.
|
||||
|
||||
Dashboard[](https://docs.unraid.net/unraid-connect/overview-and-setup#dashboard "Direct link to Dashboard")
|
||||
|
||||
-------------------------------------------------------------------------------------------------------------
|
||||
|
||||
The **Unraid Connect Dashboard** offers a centralized, cloud-based view of all your registered Unraid servers, with features like:
|
||||
|
||||
* **My Servers:** All linked servers appear in a sidebar and as interactive tiles for easy selection.
|
||||
* **Status (at a glance):** Quickly see which servers are online or offline, along with their Unraid OS version, license type, and recent activity.
|
||||
* **Health and alerts:** Visual indicators show server health, notifications, and update status.
|
||||
|
||||
When you click **Details** on a server, you will see:
|
||||
|
||||
* **Online/Offline:** Real-time connectivity status.
|
||||
* **License type:** Starter, Unleashed, or Lifetime.
|
||||
* **Uptime:** Duration the server has been running.
|
||||
* **Unraid OS version:** Current version and update availability.
|
||||
* **Storage:** Total and free space on all arrays and pools.
|
||||
* **Health metrics:** CPU usage, memory usage, and temperature (if supported).
|
||||
* **Notifications:** Hardware/software alerts, warnings, and errors.
|
||||
* **Flash backup:** Status and date of the last successful backup.
|
||||
|
||||
* * *
|
||||
|
||||
Managing your server remotely[](https://docs.unraid.net/unraid-connect/overview-and-setup#managing-your-server-remotely "Direct link to Managing your server remotely")
|
||||
|
||||
-------------------------------------------------------------------------------------------------------------------------------------------------------------------------
|
||||
|
||||
tip
|
||||
|
||||
To use all management features, provision a myunraid.net certificate under _**Settings → Management Access**_ on your server.
|
||||
|
||||
With a valid **myunraid.net** certificate, Unraid Connect enables secure, remote server management directly from the Connect web interface.
|
||||
|
||||
Remote management features include:
|
||||
|
||||
* **Remote WebGUI access:** Access the WebGUI from anywhere.
|
||||
* **Array controls:** Start or stop arrays and manage storage pools.
|
||||
* **Docker and VM management:** View, start, stop, and monitor containers and VMs.
|
||||
* **Parity & Scrub:** Launch parity check or ZFS/BTRFS scrub jobs
|
||||
* **Flash backup:** Trigger and monitor flash device backups to the cloud.
|
||||
* **Diagnostics:** Download a diagnostics zip for support
|
||||
* **Notifications:** Review and acknowledge system alerts.
|
||||
* **Server controls:** Reboot or shut down your server remotely.
|
||||
* **User management:** Manage Unraid.net account access and registration.
|
||||
|
||||
You can manage multiple servers from any device - phone, tablet, or computer - with a single browser window.
|
||||
|
||||
* * *
|
||||
|
||||
Deep linking[](https://docs.unraid.net/unraid-connect/overview-and-setup#deep-linking "Direct link to Deep linking")
|
||||
|
||||
----------------------------------------------------------------------------------------------------------------------
|
||||
|
||||
Deep linking in Unraid Connect lets you jump directly to specific sections of your Unraid WebGUI with a single click. Simply click any of the circled link buttons (below) in the Connect interface to go straight to the relevant management page for your server.
|
||||
|
||||
|
||||
|
||||
* * *
|
||||
|
||||
Customization[](https://docs.unraid.net/unraid-connect/overview-and-setup#customization "Direct link to Customization")
|
||||
|
||||
-------------------------------------------------------------------------------------------------------------------------
|
||||
|
||||
Unraid Connect provides a flexible dashboard experience, allowing you to personalize your server view and appearance. The customization options are organized below for easy reference.
|
||||
|
||||
* Change banner image
|
||||
* Rearrange dashboard tiles
|
||||
* Switch themes
|
||||
|
||||
To display your server’s banner image on the Connect dashboard, upload or select a banner image from your WebGUI under _**Settings → Display Settings → Banner**_. This banner will automatically appear in your Connect dashboard for that server.
|
||||
|
||||
You can customize your dashboard layout by dragging and dropping server tiles. In the Connect dashboard, click the hamburger (≡) button on any tile to rearrange its position. This allows you to prioritize the information and the services most important to you.
|
||||
|
||||
Toggle between dark and light mode by clicking the Sun or Moon icon on the far right of the Connect UI. Your theme preference will be instantly applied across the Connect dashboard for a consistent experience.
|
||||
|
||||
* * *
|
||||
|
||||
License management[](https://docs.unraid.net/unraid-connect/overview-and-setup#license-management "Direct link to License management")
|
||||
|
||||
----------------------------------------------------------------------------------------------------------------------------------------
|
||||
|
||||
Managing your licenses in Unraid Connect is easy. Under the **My Keys** section, you can:
|
||||
|
||||
* View or reissue a key to a new USB.
|
||||
* Upgrade your license tier directly from the Connect UI.
|
||||
* Download registration key files for backup or transfer.
|
||||
* Review license status and expiration (if applicable).
|
||||
|
||||
|
||||
|
||||
You don’t need to leave the Connect interface to manage or upgrade your licenses.
|
||||
|
||||
* * *
|
||||
|
||||
Language localization[](https://docs.unraid.net/unraid-connect/overview-and-setup#language-localization "Direct link to Language localization")
|
||||
|
||||
-------------------------------------------------------------------------------------------------------------------------------------------------
|
||||
|
||||
Unraid Connect supports multiple languages to cater to a global user base. You can change your language preference through the language selector in the Connect interface.
|
||||
|
||||
To change your language preference:
|
||||
|
||||
1. Open the Connect UI.
|
||||
2. Go to the language selector.
|
||||
|
||||
|
||||
|
||||
3. Select your preferred language from the list.
|
||||
|
||||
The interface will update automatically to reflect your selection.
|
||||
|
||||
* * *
|
||||
|
||||
Signing out[](https://docs.unraid.net/unraid-connect/overview-and-setup#signing-out "Direct link to Signing out")
|
||||
|
||||
-------------------------------------------------------------------------------------------------------------------
|
||||
|
||||
You can sign out of Unraid Connect anytime from _**Settings → Management Access → Unraid Connect → Account Status**_ by clicking the **Sign Out** button.
|
||||
|
||||
When you sign out:
|
||||
|
||||
* Your server remains listed on the Connect dashboard, but you lose access to remote management features.
|
||||
* Remote access, cloud-based flash backups, and other Unraid Connect features will be disabled for that server.
|
||||
* You can still download your registration keys, but you cannot manage or monitor the server remotely until you sign in again.
|
||||
* Signing out does **not** disconnect your server from the local network or affect local access.
|
||||
|
||||
* * *
|
||||
|
||||
Uninstalling the plugin[](https://docs.unraid.net/unraid-connect/overview-and-setup#uninstalling-the-plugin "Direct link to Uninstalling the plugin")
|
||||
|
||||
-------------------------------------------------------------------------------------------------------------------------------------------------------
|
||||
|
||||
When you uninstall the Unraid Connect plugin:
|
||||
|
||||
* All flash backup files will be deactivated and deleted from your local flash drive.
|
||||
* Cloud backups are marked for removal from Unraid servers; they will be retained for 30 days, after which they are permanently purged. For immediate deletion, [disable Flash Backup](https://docs.unraid.net/unraid-connect/automated-flash-backup/)
|
||||
before uninstalling.
|
||||
* Remote access will be disabled. Ensure that you remove any related port forwarding rules from your router.
|
||||
* Your server will be signed out of Unraid.net.
|
||||
|
||||
note
|
||||
|
||||
Uninstalling the plugin does **not** revert your server's URL from `https://yourpersonalhash.unraid.net` to `http://computername`. If you wish to change your access URL, refer to [Disabling SSL for local access](https://docs.unraid.net/unraid-os/system-administration/secure-your-server/securing-your-connection/#disabling-ssl-for-local-access)
|
||||
.
|
||||
|
||||
* * *
|
||||
|
||||
Connection errors[](https://docs.unraid.net/unraid-connect/overview-and-setup#connection-errors "Direct link to Connection errors")
|
||||
|
||||
-------------------------------------------------------------------------------------------------------------------------------------
|
||||
|
||||
If you encounter connection errors in Unraid Connect, [open a terminal](https://docs.unraid.net/unraid-os/system-administration/advanced-tools/command-line-interface/)
|
||||
from the WebGUI and run:
|
||||
|
||||
unraid-api restart
|
||||
|
||||
* [Data collection and privacy](https://docs.unraid.net/unraid-connect/overview-and-setup#data-collection-and-privacy)
|
||||
|
||||
* [Installation](https://docs.unraid.net/unraid-connect/overview-and-setup#installation)
|
||||
|
||||
* [Dashboard](https://docs.unraid.net/unraid-connect/overview-and-setup#dashboard)
|
||||
|
||||
* [Managing your server remotely](https://docs.unraid.net/unraid-connect/overview-and-setup#managing-your-server-remotely)
|
||||
|
||||
* [Deep linking](https://docs.unraid.net/unraid-connect/overview-and-setup#deep-linking)
|
||||
|
||||
* [Customization](https://docs.unraid.net/unraid-connect/overview-and-setup#customization)
|
||||
|
||||
* [License management](https://docs.unraid.net/unraid-connect/overview-and-setup#license-management)
|
||||
|
||||
* [Language localization](https://docs.unraid.net/unraid-connect/overview-and-setup#language-localization)
|
||||
|
||||
* [Signing out](https://docs.unraid.net/unraid-connect/overview-and-setup#signing-out)
|
||||
|
||||
* [Uninstalling the plugin](https://docs.unraid.net/unraid-connect/overview-and-setup#uninstalling-the-plugin)
|
||||
|
||||
* [Connection errors](https://docs.unraid.net/unraid-connect/overview-and-setup#connection-errors)
|
||||
180
docs/research/raw/connect-remote-access.md
Normal file
180
docs/research/raw/connect-remote-access.md
Normal file
@@ -0,0 +1,180 @@
|
||||
[Skip to main content](https://docs.unraid.net/unraid-connect/remote-access#__docusaurus_skipToContent_fallback)
|
||||
|
||||
On this page
|
||||
|
||||
Unlock secure, browser-based access to your Unraid WebGUI from anywhere with remote access. This feature is ideal for managing your server when you're away from home - no complicated networking or VPN Tunnel setup is required. For more advanced needs, such as connecting to Docker containers or accessing network drives, a VPN Tunnel remains the recommended solution.
|
||||
|
||||
Security reminder
|
||||
|
||||
Before enabling remote access, ensure your root password is strong and unique. Update it on the **Users** page if required. Additionally, keep your Unraid OS updated to the latest version to protect against security vulnerabilities. [Learn more about updating Unraid here](https://docs.unraid.net/unraid-os/system-administration/maintain-and-update/upgrading-unraid/)
|
||||
.
|
||||
|
||||
Remote access through Unraid Connect provides:
|
||||
|
||||
* **Convenience** - Quickly access your server’s management interface from anywhere, using a secure, cloud-managed connection.
|
||||
* **Security** - Dynamic access modes limit exposure by only allowing access to the internet when necessary, which helps reduce risks from automated attacks.
|
||||
* **Simplicity** - No need for manual port forwarding or VPN client setup for basic management tasks.
|
||||
|
||||
tip
|
||||
|
||||
For full network access or advanced use cases, consider setting up [Tailscale](https://docs.unraid.net/unraid-os/system-administration/secure-your-server/tailscale/)
|
||||
or a VPN solution.
|
||||
|
||||
* * *
|
||||
|
||||
Initial setup[](https://docs.unraid.net/unraid-connect/remote-access#initial-setup "Direct link to Initial setup")
|
||||
|
||||
--------------------------------------------------------------------------------------------------------------------
|
||||
|
||||
To enable remote access:
|
||||
|
||||
1. In the Unraid WebGUI, navigate to _**Settings → Management Access**_.
|
||||
2. Check the **HTTPS port** (default: 443). If this port is in use (e.g., by Docker), select an unused port above 1000 (like 3443, 4443, or 5443).
|
||||
3. Click **Apply** if you changed any settings.
|
||||
4. Under **CA-signed certificate file**, click **Provision** to generate a trusted certificate.
|
||||
|
||||
Your Unraid server will be ready to accept secure remote connections via the WebGUI, using the configured port and a trusted certificate.
|
||||
|
||||
* * *
|
||||
|
||||
Choosing a remote access type[](https://docs.unraid.net/unraid-connect/remote-access#choosing-a-remote-access-type "Direct link to Choosing a remote access type")
|
||||
|
||||
--------------------------------------------------------------------------------------------------------------------------------------------------------------------
|
||||
|
||||
Unraid Connect offers two modes:
|
||||
|
||||
* Dynamic remote access
|
||||
* Static remote access
|
||||
|
||||
**Dynamic remote access** provides secure, on-demand access to your WebGUI.
|
||||
|
||||
* **Access is enabled only when you need it.** The WebGUI remains closed to the internet by default, minimizing the attack surface.
|
||||
* **Works with UPnP or manual port forwarding.**
|
||||
* **Automatically opens and closes access** through the Connect dashboard or API, with sessions limited by time for added security.
|
||||
|
||||
**Static remote access** keeps your WebGUI continuously available from the internet.
|
||||
|
||||
* **Server is always accessible from the internet** on the configured port.
|
||||
* **Higher risk:** The WebGUI is exposed to WAN traffic at all times, increasing potential vulnerability.
|
||||
|
||||
| Feature | Dynamic remote access | Static remote access |
|
||||
| --- | --- | --- |
|
||||
| WebGUI open to internet | Only when enabled | Always |
|
||||
| Attack surface | Minimized | Maximized |
|
||||
| Automation | Auto open/close via Connect | Manual setup, always open |
|
||||
| UPnP support | Yes | Yes |
|
||||
| | **Recommended for most** | |
|
||||
|
||||
Dynamic remote access setup[](https://docs.unraid.net/unraid-connect/remote-access#dynamic-remote-access-setup "Direct link to Dynamic remote access setup")
|
||||
|
||||
--------------------------------------------------------------------------------------------------------------------------------------------------------------
|
||||
|
||||
To set up dynamic remote access:
|
||||
|
||||
1. In _**Settings → Management Access → Unraid API**_, select a dynamic option from the Remote Access dropdown:
|
||||
|
||||
* **Dynamic - UPnP:** Uses UPnP to open and close a random port automatically (requires UPnP enabled on your router).
|
||||
* **Dynamic - Manual port forward:** Requires you to forward the selected port on your router manually.
|
||||
2. Navigate to [Unraid Connect](https://connect.myunraid.net/)
|
||||
, and go to the management or server details page.
|
||||
|
||||
3. The **Dynamic remote access** card will show a button if your server isn’t currently accessible from your location.
|
||||
|
||||
4. Click the button to enable WAN access. If using UPnP, a new port forward lease is created (typically for 30 minutes) and auto-renewed while active.
|
||||
|
||||
5. The card will display the current status and UPnP state.
|
||||
|
||||
6. After 10 minutes of inactivity - or if you click **Disable remote access** - internet access is automatically revoked. UPnP leases are removed as well.
|
||||
|
||||
|
||||
* * *
|
||||
|
||||
Using UPnP (Universal Plug and Play)[](https://docs.unraid.net/unraid-connect/remote-access#using-upnp-universal-plug-and-play "Direct link to Using UPnP (Universal Plug and Play)")
|
||||
|
||||
---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
|
||||
|
||||
UPnP automates port forwarding, simplifying remote access without requiring manual router configuration.
|
||||
|
||||
To configure UPnP:
|
||||
|
||||
1. **Enable UPnP on your router.** Ensure that your router supports UPnP and verify that it is enabled in the router settings.
|
||||
|
||||
2. **Enable UPnP in Unraid.** Navigate to _**Settings → Management Access**_ and change **Use UPnP** to **Yes**.
|
||||
|
||||
3. **Select UPnP in Unraid Connect.** On the Unraid Connect settings page, choose the remote access option as UPnP (select either Dynamic or Always On) and then click **Apply**.
|
||||
|
||||
4. **Verify port forwarding (Always On only).** Click the **Check** button. If successful, you'll see the message, "Your Unraid Server is reachable from the Internet."
|
||||
|
||||
For Dynamic forwarding, you need to click **Enable Dynamic Remote Access** in [Unraid Connect](https://connect.myunraid.net/)
|
||||
to allow access.
|
||||
|
||||
|
||||
Troubleshooting
|
||||
|
||||
If the setting changes from UPnP to Manual Port Forward upon reloading, Unraid might not be able to communicate with your router. Double-check that UPnP is enabled and consider updating your router's firmware.
|
||||
|
||||
* * *
|
||||
|
||||
Using manual port forwarding[](https://docs.unraid.net/unraid-connect/remote-access#using-manual-port-forwarding "Direct link to Using manual port forwarding")
|
||||
|
||||
-----------------------------------------------------------------------------------------------------------------------------------------------------------------
|
||||
|
||||
Manual port forwarding provides greater control and is compatible with most routers.
|
||||
|
||||
To configure manual port forwarding:
|
||||
|
||||
1. **Choose a WAN port:** Pick a random port number above 1000 (for example, 13856 or 48653), rather than using the default 443.
|
||||
|
||||
2. **Apply settings in Unraid:** Click **Apply** to save the port you selected.
|
||||
|
||||
3. **Configure your router:** Set up a port forwarding rule on your router, directing your chosen WAN port to your server’s HTTPS port. The Unraid interface provides the correct ports and IP address.
|
||||
|
||||
Some routers may require the WAN port and HTTPS port to match. If so, use the same high random number for both.
|
||||
|
||||
4. **Verify port forwarding (Always On only):** Press the **Check** button. If everything is correct, you’ll see “Your Unraid Server is reachable from the Internet.”
|
||||
|
||||
For dynamic forwarding, ensure to click **Enable Dynamic Remote Access** in [Unraid Connect](https://connect.myunraid.net/)
|
||||
to enable access.
|
||||
|
||||
5. **Access your server:** Log in to [Unraid Connect](https://connect.myunraid.net/)
|
||||
and click the **Manage** link to connect to your server remotely.
|
||||
|
||||
|
||||
* * *
|
||||
|
||||
Enabling secure local access[](https://docs.unraid.net/unraid-connect/remote-access#enabling-secure-local-access "Direct link to Enabling secure local access")
|
||||
|
||||
-----------------------------------------------------------------------------------------------------------------------------------------------------------------
|
||||
|
||||
Secure local access ensures that all connections to your Unraid WebGUI, even within your home or office network, are encrypted using HTTPS, thereby safeguarding any sensitive information, such as login credentials and configuration data.
|
||||
|
||||
Benefits of secure local access include:
|
||||
|
||||
* **Encryption** - All data exchanged between your browser and the server is protected.
|
||||
* **Consistency** - Use the same secure URL for both local and remote access.
|
||||
* **Compliance** - Adheres to security best practices for protecting administrative interfaces.
|
||||
|
||||
To enable secure local access:
|
||||
|
||||
1. Go to _**Settings → Management Access**_.
|
||||
2. In the **CA-signed certificate** section, check for DNS Rebinding warnings.
|
||||
* If no warnings show, set **Use SSL/TLS** to **Strict**.
|
||||
* If warnings are present, review [DNS Rebinding Protection](https://docs.unraid.net/unraid-os/system-administration/secure-your-server/securing-your-connection/#dns-rebinding-protection)
|
||||
.
|
||||
|
||||
important
|
||||
|
||||
With SSL/TLS set to Strict, client devices must resolve your server’s DNS name. If your Internet connection fails, access to the WebGUI may be lost. See [Accessing your server when DNS is down](https://docs.unraid.net/unraid-os/system-administration/secure-your-server/securing-your-connection/#accessing-your-server-when-dns-is-down)
|
||||
for recovery steps.
|
||||
|
||||
* [Initial setup](https://docs.unraid.net/unraid-connect/remote-access#initial-setup)
|
||||
|
||||
* [Choosing a remote access type](https://docs.unraid.net/unraid-connect/remote-access#choosing-a-remote-access-type)
|
||||
|
||||
* [Dynamic remote access setup](https://docs.unraid.net/unraid-connect/remote-access#dynamic-remote-access-setup)
|
||||
|
||||
* [Using UPnP (Universal Plug and Play)](https://docs.unraid.net/unraid-connect/remote-access#using-upnp-universal-plug-and-play)
|
||||
|
||||
* [Using manual port forwarding](https://docs.unraid.net/unraid-connect/remote-access#using-manual-port-forwarding)
|
||||
|
||||
* [Enabling secure local access](https://docs.unraid.net/unraid-connect/remote-access#enabling-secure-local-access)
|
||||
958
docs/research/raw/release-7.0.0.md
Normal file
958
docs/research/raw/release-7.0.0.md
Normal file
@@ -0,0 +1,958 @@
|
||||
[Skip to main content](https://docs.unraid.net/unraid-os/release-notes/7.0.0#__docusaurus_skipToContent_fallback)
|
||||
|
||||
On this page
|
||||
|
||||
This version of Unraid OS includes significant improvements across all subsystems, while attempting to maintain backward compatibility as much as possible.
|
||||
|
||||
Special thanks to:
|
||||
|
||||
* @bonienl, @dlandon, @ich777, @JorgeB, @SimonF, and @Squid for their direction, support, and development work on this release
|
||||
* @bonienl for merging their **Dynamix File Manager** plugin into the webgui
|
||||
* @Squid for merging their **GUI Search** and **Unlimited Width Plugin** plugins into the webgui
|
||||
* @ludoux (**Proxy Editor** plugin) and @Squid (**Community Applications** plugin) for pioneering the work on http proxy support, of which several ideas have been incorporated into the webgui
|
||||
* @ich777 for maintaining third-party driver plugins, and for the [Tailscale Docker integration](https://docs.unraid.net/unraid-os/release-notes/7.0.0#tailscale-integration)
|
||||
|
||||
* @SimonF for significant new features in the Unraid OS VM Manager
|
||||
* @EDACerton for development of the Tailscale plugin
|
||||
|
||||
View the [contributors to Unraid on GitHub](https://github.com/unraid/webgui/graphs/contributors?from=2023-09-08&to=2025-01-08&type=c)
|
||||
with shoutouts to these community members who have contributed PRs (these are GitHub ids):
|
||||
|
||||
* almightyYantao
|
||||
* baumerdev
|
||||
* Commifreak
|
||||
* desertwitch
|
||||
* dkaser
|
||||
* donbuehl
|
||||
* FunkeCoder23
|
||||
* Garbee
|
||||
* jbtwo
|
||||
* jski
|
||||
* Leseratte10
|
||||
* Mainfrezzer
|
||||
* mtongnz
|
||||
* othyn
|
||||
* serisman
|
||||
* suzukua
|
||||
* thecode
|
||||
|
||||
And sincere thanks to everyone who has requested features, reported bugs, and tested pre-releases!
|
||||
|
||||
Upgrading[](https://docs.unraid.net/unraid-os/release-notes/7.0.0#upgrading "Direct link to Upgrading")
|
||||
|
||||
---------------------------------------------------------------------------------------------------------
|
||||
|
||||
### Known issues[](https://docs.unraid.net/unraid-os/release-notes/7.0.0#known-issues "Direct link to Known issues")
|
||||
|
||||
#### ZFS pools[](https://docs.unraid.net/unraid-os/release-notes/7.0.0#zfs-pools "Direct link to ZFS pools")
|
||||
|
||||
If you are using ZFS pools, please take note of the following:
|
||||
|
||||
* You will see a warning about unsupported features in your existing ZFS pools. This is because the version of ZFS in 7.0 is upgraded vs. 6.12 and contains new features. This warning is harmless, meaning your pool will still function normally. A button will appear letting you upgrade a pool to support the new ZFS features; however, Unraid OS does not make use of these new features, and once upgraded previous versions of Unraid OS will not be able to mount the pool.
|
||||
* Similarly, new pools created in 7.0 will not mount in 6.12 due to ZFS not supporting downgrades. There is no way around this.
|
||||
* If you decide to downgrade from 7.0 to 6.12 any previously existing hybrid pools will not be recognized upon reboot into 6.12. To work around this, first click Tools/New Config in 7.0, preserving all slots, then reboot into 6.12 and your hybrid pools should import correctly.
|
||||
* ZFS spares are not supported in this release. If you have created a hybrid pool in 6.12 which includes spares, please remove the 'spares' vdev before upgrading to v7.0. This will be fixed in a future release.
|
||||
* Currently unable to import TrueNAS pools. This will be fixed in a future release.
|
||||
* If you are using **Docker data-root=directory** on a ZFS volume, see [Add support for overlay2 storage driver](https://docs.unraid.net/unraid-os/release-notes/7.0.0#add-support-for-overlay2-storage-driver)
|
||||
.
|
||||
* We check that VM names do not include characters that are not valid for ZFS. Existing VMs are not modified but will throw an error and disable update if invalid characters are found.
|
||||
|
||||
#### General pool issues[](https://docs.unraid.net/unraid-os/release-notes/7.0.0#general-pool-issues "Direct link to General pool issues")
|
||||
|
||||
If your existing pools fail to import with _Wrong Pool State, invalid expansion_ or _Wrong pool State. Too many wrong or missing devices_, see this [forum post](https://forums.unraid.net/topic/184435-unraid-os-version-700-available/#findComment-1508012)
|
||||
.
|
||||
|
||||
#### Drive spindown issues[](https://docs.unraid.net/unraid-os/release-notes/7.0.0#drive-spindown-issues "Direct link to Drive spindown issues")
|
||||
|
||||
Drives may not spin down when connected to older Marvell drive controllers that use the sata\_mv driver (i.e. Supermicro SASLP and SAS2LP) or to older Intel controllers (i.e. ICH7-ICH10). This may be resolved by a future kernel update.
|
||||
|
||||
#### Excessive flash drive activity slows the system down[](https://docs.unraid.net/unraid-os/release-notes/7.0.0#excessive-flash-drive-activity-slows-the-system-down "Direct link to Excessive flash drive activity slows the system down")
|
||||
|
||||
If the system is running slowly, check the Main page and see if it shows significant continuous reads from the flash drive during normal operation. If so, the system may be experiencing sufficient memory pressure to push the OS out of RAM and cause it to be re-read from the flash drive. From the web terminal type:
|
||||
|
||||
touch /boot/config/fastusr
|
||||
|
||||
and then reboot. This will use around 500 MB of RAM to ensure the OS files always stay in memory. Please let us know if this helps.
|
||||
|
||||
#### New Windows changes may result in loss of access to Public shares[](https://docs.unraid.net/unraid-os/release-notes/7.0.0#new-windows-changes-may-result-in-loss-of-access-to-public-shares "Direct link to New Windows changes may result in loss of access to Public shares")
|
||||
|
||||
Due to recent security changes in Windows 11 24H2, "guest" access of Unraid public shares may not work. The easiest way around this is to create a user in Unraid with the same name as the Windows account you are using to connect. If the Unraid user password is not the same as the Windows account password, Windows will prompt for credentials.
|
||||
|
||||
If you are using a Microsoft account, it may be better to create a user in Unraid with a simple username, set a password, then in Windows go to _**Control Panel → Credential Manager → Windows credentials → Add a Windows Credential**_ and add the correct Unraid server name and credentials.
|
||||
|
||||
Alternately you can [re-enable Windows guest fallback](https://techcommunity.microsoft.com/blog/filecab/accessing-a-third-party-nas-with-smb-in-windows-11-24h2-may-fail/4154300)
|
||||
(not recommended).
|
||||
|
||||
#### Problems due to Realtek network cards[](https://docs.unraid.net/unraid-os/release-notes/7.0.0#problems-due-to-realtek-network-cards "Direct link to Problems due to Realtek network cards")
|
||||
|
||||
There have been multiple reports of issues with the Realtek driver plugin after upgrading to recent kernels. You may want to preemptively uninstall it before upgrading, or remove it afterwards if you have networking issues.
|
||||
|
||||
#### A virtual NIC is being assigned to eth0 on certain systems[](https://docs.unraid.net/unraid-os/release-notes/7.0.0#a-virtual-nic-is-being-assigned-to-eth0-on-certain-systems "Direct link to A virtual NIC is being assigned to eth0 on certain systems")
|
||||
|
||||
On some systems with IPMI KVM, a virtual NIC is being assigned to eth0 instead of the expected NIC. See this [forum post](https://forums.unraid.net/bug-reports/stable-releases/61214-no-network-after-updating-eth0-assigned-to-virtual-usb-nic-cdc-ethernet-device-with-169-ip-instead-of-mellanox-10gbe-nic-r3407/)
|
||||
for options.
|
||||
|
||||
#### Issues using Docker custom networks[](https://docs.unraid.net/unraid-os/release-notes/7.0.0#issues-using-docker-custom-networks "Direct link to Issues using Docker custom networks")
|
||||
|
||||
If certain custom Docker networks are not available for use by your Docker containers, navigate to _**Settings → Docker**_ and fix the CIDR definitions for the subnet mask and DHCP pool on those custom networks. The underlying systems have gotten more strict and invalid CIDR definitions which worked in earlier releases no longer work.
|
||||
|
||||
### Rolling back[](https://docs.unraid.net/unraid-os/release-notes/7.0.0#rolling-back "Direct link to Rolling back")
|
||||
|
||||
See the warnings under **Known Issues** above.
|
||||
|
||||
The Dynamix File Manager, GUI Search, and Unlimited Width Plugin plugins are now built into Unraid. If you rollback to an earlier version you will need to reinstall those plugins to retain their functionality.
|
||||
|
||||
If you disabled the unRAID array we recommend enabling it again before rolling back.
|
||||
|
||||
If you previously had Outgoing Proxies set up using the Proxy Editor plugin or some other mechanism, you will need to re-enable that mechanism after rolling back.
|
||||
|
||||
If you roll back after enabling the [overlay2 storage driver](https://docs.unraid.net/unraid-os/release-notes/7.0.0#add-support-for-overlay2-storage-driver)
|
||||
you will need to delete the Docker directory and let Docker re-download the image layers.
|
||||
|
||||
If you roll back after installing [Tailscale in a Docker container](https://docs.unraid.net/unraid-os/release-notes/7.0.0#tailscale-integration)
|
||||
, you will need to edit the container, make a dummy change, and **Apply** to rebuild the container without the Tailscale integration.
|
||||
|
||||
After rolling back, make a dummy change to each WireGuard config to get the settings appropriate for that version of Unraid.
|
||||
|
||||
If rolling back earlier than 6.12.14, also see the [6.12.14 release notes](https://docs.unraid.net/unraid-os/release-notes/6.12.14/#rolling-back)
|
||||
.
|
||||
|
||||
Storage[](https://docs.unraid.net/unraid-os/release-notes/7.0.0#storage "Direct link to Storage")
|
||||
|
||||
---------------------------------------------------------------------------------------------------
|
||||
|
||||
### unRAID array optional[](https://docs.unraid.net/unraid-os/release-notes/7.0.0#unraid-array-optional "Direct link to unRAID array optional")
|
||||
|
||||
You can now set the number of unRAID array slots to 'none'. This will allow the array to Start without any devices assigned to the unRAID array itself.
|
||||
|
||||
If you are running an all-SSD/NMVe server, we recommend assigning all devices to one or more ZFS/BTRFS pools, since Trim/Discard is not supported with unRAID array devices.
|
||||
|
||||
To unassign the unRAID array from an existing server, first unassign all Array slots on the Main page, and then set the Slots to 'none'.
|
||||
|
||||
For new installs, the default number of slots to reserve for the unRAID array is now 'none'.
|
||||
|
||||
### Share secondary storage may be assigned to a pool[](https://docs.unraid.net/unraid-os/release-notes/7.0.0#share-secondary-storage-may-be-assigned-to-a-pool "Direct link to Share secondary storage may be assigned to a pool")
|
||||
|
||||
Shares can now be configured with pools for both primary and secondary storage, and mover will move files between those pools. As a result of this change, the maximum number of supported pools is now 34 (previously 35).
|
||||
|
||||
### ReiserFS file system option has been disabled[](https://docs.unraid.net/unraid-os/release-notes/7.0.0#reiserfs-file-system-option-has-been-disabled "Direct link to ReiserFS file system option has been disabled")
|
||||
|
||||
Since ReiserFS is scheduled to be removed from the Linux kernel, the option to format a device with ReiserFS has also been disabled. You may use this mover function to empty an array disk prior to reformatting with another file system, see below. We will add a webGUI button for this in a future release.
|
||||
|
||||
### Using 'mover' to empty an array disk[](https://docs.unraid.net/unraid-os/release-notes/7.0.0#using-mover-to-empty-an-array-disk "Direct link to Using 'mover' to empty an array disk")
|
||||
|
||||
Removed in Unraid 7.2.1
|
||||
|
||||
This command line option was removed in Unraid 7.2.1. On newer releases, use the WebGUI method instead. See [Converting to a new file system type](https://docs.unraid.net/unraid-os/using-unraid-to/manage-storage/file-systems/#converting-to-a-new-file-system-type)
|
||||
for details.
|
||||
|
||||
Mover can now be used to empty an array disk. With the array started, run this at a web terminal:
|
||||
|
||||
mover start -e diskN |& logger & # where N is [1..28]
|
||||
|
||||
Mover will look at each top-level director (share) and then move files one-by-one to other disks in the array, following the usual config settings (include/exclude, split-level, alloc method). Move targets are restricted to just the unRAID array.
|
||||
|
||||
Watch the syslog for status. When the mover process ends, the syslog will show a list of files which could not be moved:
|
||||
|
||||
* maybe file was in-use
|
||||
* maybe file is at the top-level of /mnt/diskN
|
||||
* maybe we ran out of space
|
||||
|
||||
### Predefined shares handling[](https://docs.unraid.net/unraid-os/release-notes/7.0.0#predefined-shares-handling "Direct link to Predefined shares handling")
|
||||
|
||||
The Unraid OS Docker Manager is configured by default to use these predefined shares:
|
||||
|
||||
* system - used to store Docker image layers in a loopback image stored in system/docker.
|
||||
* appdata - used by Docker applications to store application data.
|
||||
|
||||
The Unraid OS VM Manager is configured by default to use these predefined shares:
|
||||
|
||||
* system - used to store libvirt loopback image stored in system/libvirt
|
||||
* domains - used to store VM vdisk images
|
||||
* isos - used to store ISO boot images
|
||||
|
||||
When either Docker or VMs are enabled, the required predefined shares are created if necessary according to these rules:
|
||||
|
||||
* if a pool named 'cache' is present, predefined shares are created with 'cache' as the Primary storage with no Secondary storage.
|
||||
* if no pool named 'cache' is present, the predefined shares are created with the first alphabetically present pool as Primary with no Secondary storage.
|
||||
* if no pools are present, the predefined shares are created on the unRAID array as Primary with no Secondary storage.
|
||||
|
||||
### ZFS implementation[](https://docs.unraid.net/unraid-os/release-notes/7.0.0#zfs-implementation "Direct link to ZFS implementation")
|
||||
|
||||
* Support Hybrid ZFS pools aka subpools (except 'spares')
|
||||
* Support recovery from multiple drive failures in a ZFS pool with sufficient protection
|
||||
* Support LUKS encryption on ZFS pools and drives
|
||||
* Set reasonable default profiles for new ZFS pools and subpools
|
||||
* Support upgrading ZFS pools when viewing the pool status. Note: after upgrading, the volume may not be mountable in previous versions of Unraid
|
||||
|
||||
### Allocation profiles for btrfs, zfs, and zfs subpools[](https://docs.unraid.net/unraid-os/release-notes/7.0.0#allocation-profiles-for-btrfs-zfs-and-zfs-subpools "Direct link to Allocation profiles for btrfs, zfs, and zfs subpools")
|
||||
|
||||
When a btrfs or zfs pool/subpool is created, the default storage allocation is determined by the number of slots (devices) initially assigned to the pool:
|
||||
|
||||
* for zfs main (root) pool:
|
||||
|
||||
* slots == 1 => single
|
||||
* slots == 2 => mirror (1 group of 2 devices)
|
||||
* slots >= 3 => raidz1 (1 group of 'slots' devices)
|
||||
* for zfs special, logs, and dedup subpools:
|
||||
|
||||
* slots == 1 => single
|
||||
* slots%2 == 0 => mirror (slots/2 groups of 2 devices)
|
||||
* slots%3 == 0 => mirror (slots/3 groups of 3 devices)
|
||||
* otherwise => stripe (1 group of 'slots' devices)
|
||||
* for zfs cache and spare subpools:
|
||||
|
||||
* slots == 1 => single
|
||||
* slots >= 2 => stripe (1 group of 'slots' devices)
|
||||
* for btrfs pools:
|
||||
|
||||
* slots == 1 => single
|
||||
* slots >= 2 => raid1 (ie, what btrfs called "raid1")
|
||||
|
||||
### Pool considerations[](https://docs.unraid.net/unraid-os/release-notes/7.0.0#pool-considerations "Direct link to Pool considerations")
|
||||
|
||||
When adding devices to (expanding) a single-slot pool, these rules apply:
|
||||
|
||||
For btrfs: adding one or more devices to a single-slot pool will result in converting the pool to raid1 (that is, what btrfs defines as raid1). Adding any number of devices to an existing multiple-slot btrfs pool increases the storage capacity of the pool and does not change the storage profile.
|
||||
|
||||
For zfs: adding one, two, or three devices to a single-slot pool will result in converting the pool to 2-way, 3-way, or 4-way mirror. Adding a single device to an existing 2-way or 3-way mirror converts the pool to a 3-way or 4-way mirror.
|
||||
|
||||
Changing the file system type of a pool:
|
||||
|
||||
For all single-slot pools, the file system type can be changed when array is Stopped.
|
||||
|
||||
For btrfs/zfs multi-slot pools, the file system type cannot be changed. To repurpose the devices you must click the Erase pool buton.
|
||||
|
||||
### Other features[](https://docs.unraid.net/unraid-os/release-notes/7.0.0#other-features "Direct link to Other features")
|
||||
|
||||
* Add Spin up/down devices of a pool in parallel
|
||||
* Add "Delete Pool" button, which unassigns all devices of a pool and then removes the pool. The devices themselves are not modified. This is useful when physically removing devices from a server.
|
||||
* Add ability to change encryption phrase/keyfile for LUKS encrypted disks
|
||||
* Introduce 'config/share.cfg' variable 'shareNOFILE' which sets maximum open file descriptors for shfs process (see the Known Issues)
|
||||
|
||||
VM Manager[](https://docs.unraid.net/unraid-os/release-notes/7.0.0#vm-manager "Direct link to VM Manager")
|
||||
|
||||
------------------------------------------------------------------------------------------------------------
|
||||
|
||||
### Improvements[](https://docs.unraid.net/unraid-os/release-notes/7.0.0#improvements "Direct link to Improvements")
|
||||
|
||||
Added support for VM clones, snapshots, and evdev passthru.
|
||||
|
||||
The VM editor now has a new read-only inline XML mode for advanced users, making it clear how the GUI choices affect the underlying XML used by the VM.
|
||||
|
||||
Big thanks to @SimonF for his ongoing enhancements to VMs.
|
||||
|
||||
### Other changes[](https://docs.unraid.net/unraid-os/release-notes/7.0.0#other-changes "Direct link to Other changes")
|
||||
|
||||
* **VM Tab**
|
||||
* Show all graphics cards and IP addresses assigned to VMs
|
||||
* noVNC version: 1.5
|
||||
* **VM Manager Settings**
|
||||
* Added VM autostart disable option
|
||||
* **Add/edit VM template**
|
||||
* Added "inline xml view" option
|
||||
* Support user-created VM templates
|
||||
* Add qemu ppc64 target
|
||||
* Add qemu:override support
|
||||
* Add "QEMU command-line passthrough" feature
|
||||
* Add VM multifunction support, including "PCI Other"
|
||||
* VM template enhancements for Windows VMs, including hypervclock support
|
||||
* Add "migratable" on/off option for emulated CPU
|
||||
* Add offset and timer support
|
||||
* Add no keymap option and set Virtual GPU default keyboard to use it
|
||||
* Add nogpu option
|
||||
* Add SR-IOV support for Intel iGPU
|
||||
* Add storage override to specify where images are created at add VM
|
||||
* Add SSD flag for vdisks
|
||||
* Add Unmap Support
|
||||
* Check that VM name does not include characters that are not valid for ZFS.
|
||||
* **Dashboard**
|
||||
* Add VM usage statistics to the dashboard, enable on _**Settings → VM Manager → Show VM Usage**_
|
||||
|
||||
Docker[](https://docs.unraid.net/unraid-os/release-notes/7.0.0#docker "Direct link to Docker")
|
||||
|
||||
------------------------------------------------------------------------------------------------
|
||||
|
||||
### Docker fork bomb prevention[](https://docs.unraid.net/unraid-os/release-notes/7.0.0#docker-fork-bomb-prevention "Direct link to Docker fork bomb prevention")
|
||||
|
||||
To prevent "Docker fork bombs" we introduced a new setting, _**Settings → Docker → Docker PID Limit**_, which specifies the maximum number of Process ID's which any container may have active (with default 2048).
|
||||
|
||||
If you have a container that requires more PID's you may either increase this setting or you may override for a specific container by adding, for example, `--pids-limit 3000` to the Docker template _Extra Parameters_ setting.
|
||||
|
||||
### Add support for overlay2 storage driver[](https://docs.unraid.net/unraid-os/release-notes/7.0.0#add-support-for-overlay2-storage-driver "Direct link to Add support for overlay2 storage driver")
|
||||
|
||||
If you are using **Docker data-root=directory** on a ZFS volume, we recommend that you navigate to _**Settings → Docker**_ and switch the **Docker storage driver** to **overlay2**, then delete the directory contents and let Docker re-download the image layers. The legacy **native** setting causes significant stability issues on ZFS volumes.
|
||||
|
||||
If retaining the ability to downgrade to earlier releases is important, then switch to **Docker data-root=xfs vDisk** instead.
|
||||
|
||||
### Other changes[](https://docs.unraid.net/unraid-os/release-notes/7.0.0#other-changes-1 "Direct link to Other changes")
|
||||
|
||||
* See [Tailscale integration](https://docs.unraid.net/unraid-os/release-notes/7.0.0#tailscale-integration)
|
||||
|
||||
* Allow custom registry with a port specification
|
||||
* Use "lazy unmount" unmount of docker image to prevent blocking array stop
|
||||
* Updated to address multiple security issues (CVE-2024-21626, CVE-2024-24557)
|
||||
* Docker Manager:
|
||||
* Allow users to select Container networks in the WebUI
|
||||
* Correctly identify/show non dockerman Managed containers
|
||||
* rc.docker:
|
||||
* Only stop Unraid managed containers
|
||||
* Honor restart policy from 3rd party containers
|
||||
* Set MTU of Docker Wireguard bridge to match Wireguard default MTU
|
||||
|
||||
Networking[](https://docs.unraid.net/unraid-os/release-notes/7.0.0#networking "Direct link to Networking")
|
||||
|
||||
------------------------------------------------------------------------------------------------------------
|
||||
|
||||
### Tailscale integration[](https://docs.unraid.net/unraid-os/release-notes/7.0.0#tailscale-integration "Direct link to Tailscale integration")
|
||||
|
||||
Unraid OS supports [Tailscale](https://tailscale.com/)
|
||||
through the use of a plugin created by Community Developer EDACerton. When this plugin is installed, Tailscale certificates are supported for https webGUI access, and the Tailnet URLs will be displayed on the _**Settings → Management Access**_ page.
|
||||
|
||||
And in Unraid natively, you can optionally install Tailscale in almost any Docker container, giving you the ability to share containers with specific people, access them using valid https certificates, and give them alternate routes to the Internet via Exit Nodes.
|
||||
|
||||
For more details see [the docs](https://docs.unraid.net/unraid-os/system-administration/secure-your-server/tailscale/)
|
||||
|
||||
### Support iframing the webGUI[](https://docs.unraid.net/unraid-os/release-notes/7.0.0#support-iframing-the-webgui "Direct link to Support iframing the webGUI")
|
||||
|
||||
Added "Content-Security-Policy frame-ancestors" support to automatically allow the webGUI to be iframed by domains it has certificates for. It isn't exactly supported, but additional customization is possible by using a script to modify NGINX\_CUSTOMFA in `/etc/defaults/nginx`
|
||||
|
||||
### Other changes[](https://docs.unraid.net/unraid-os/release-notes/7.0.0#other-changes-2 "Direct link to Other changes")
|
||||
|
||||
* Upgraded to OpenSSL 3
|
||||
* Allow ALL IPv4/IPv6 addresses as listener. This solves the issue when IPv4 or IPv6 addresses change dynamically
|
||||
* Samba:
|
||||
* Add ipv6 listening address only when NetBIOS is disabled
|
||||
* Fix MacOS unable to write 'flash' share and restore Time Machine compatibility (fruit changes)
|
||||
* The VPN manager now adds all interfaces to WireGuard tunnels, make a dummy change to the tunnel after upgrading or changing network settings to update WireGuard tunnel configs.
|
||||
|
||||
webGUI[](https://docs.unraid.net/unraid-os/release-notes/7.0.0#webgui "Direct link to webGUI")
|
||||
|
||||
------------------------------------------------------------------------------------------------
|
||||
|
||||
### Integrated Dynamix File Manager plugin[](https://docs.unraid.net/unraid-os/release-notes/7.0.0#integrated-dynamix-file-manager-plugin "Direct link to Integrated Dynamix File Manager plugin")
|
||||
|
||||
Click the file manager icon and navigate through your directory structure with the ability to perform common operations such as copy, move, delete, and rename files and directories.
|
||||
|
||||
### Integrated GUI Search plugin[](https://docs.unraid.net/unraid-os/release-notes/7.0.0#integrated-gui-search-plugin "Direct link to Integrated GUI Search plugin")
|
||||
|
||||
Click the search icon on the Menu bar and type the name of the setting you are looking for.
|
||||
|
||||
### Outgoing Proxy Manager[](https://docs.unraid.net/unraid-os/release-notes/7.0.0#outgoing-proxy-manager "Direct link to Outgoing Proxy Manager")
|
||||
|
||||
If you previously used the Proxy Editor plugin or had an outgoing proxy setup for CA, those will automatically be removed/imported. You can then adjust them on _**Settings → Outgoing Proxy Manager**_.
|
||||
|
||||
For more details, see the [manual](https://docs.unraid.net/unraid-os/system-administration/secure-your-server/secure-your-outgoing-comms/)
|
||||
.
|
||||
|
||||
Note: this feature is completely unrelated to any reverse proxies you may be using.
|
||||
|
||||
### Notification Agents[](https://docs.unraid.net/unraid-os/release-notes/7.0.0#notification-agents "Direct link to Notification Agents")
|
||||
|
||||
Notification agents xml are now stored as individual xml files, making it easier to add notification agents via plugin.
|
||||
|
||||
See this [sample plugin](https://github.com/Squidly271/Wxwork-sample)
|
||||
by @Squid
|
||||
|
||||
* fix: Agent notifications do not work if there is a problem with email notifications
|
||||
|
||||
### NTP Configuration[](https://docs.unraid.net/unraid-os/release-notes/7.0.0#ntp-configuration "Direct link to NTP Configuration")
|
||||
|
||||
For new installs, a single default NTP server is set to 'time.google.com'.
|
||||
|
||||
If your server is using our previous NTP defaults of time1.google.com, time2.google.com etc, you may notice some confusing NTP-related messages in your syslog. To avoid this, consider changing to our new defaults: navigate to _**Settings → Date & Time**_ and configure **NTP server 1** to be time.google.com, leaving all the others blank.
|
||||
|
||||
Of course, you are welcome to use any time servers you prefer, this is just to let you know that we have tweaked our defaults.
|
||||
|
||||
### NFS Shares[](https://docs.unraid.net/unraid-os/release-notes/7.0.0#nfs-shares "Direct link to NFS Shares")
|
||||
|
||||
We have added a few new settings to help resolve issues with NFS shares. On _**Settings → Global Share Settings**_ you can adjust the number of fuse file descriptors and on _**Settings → NFS**_ you can adjust the NFS protocol version and number of threads it uses. See the inline help for details.
|
||||
|
||||
* Added support for NFS 4.1 and 4.2, and permit NFSv4 mounts by default
|
||||
* Add a text box to configure multi-line NFS rules
|
||||
* Bug fix: nfsd doesn't restart properly
|
||||
|
||||
### Dashboard[](https://docs.unraid.net/unraid-os/release-notes/7.0.0#dashboard "Direct link to Dashboard")
|
||||
|
||||
* Add server date and time to the Dashboard; click the time to edit related settings
|
||||
* Rework the **System** tile to clarify what is being shown, including tooltips
|
||||
* Show useful content when dashboard tiles are minimized
|
||||
* Show Docker RAM usage on Dashboard
|
||||
* Add Docker RAM usage to the Dashboard
|
||||
* Rename 'Services' to 'System'
|
||||
* Fix memory leak on the Dashboard, VM Manager and Docker Manager pages
|
||||
|
||||
### SMART improvements[](https://docs.unraid.net/unraid-os/release-notes/7.0.0#smart-improvements "Direct link to SMART improvements")
|
||||
|
||||
* Display KB/MB/GB/TB written in SMART Attributes for SSDs
|
||||
* Add 'SSD endurance remaining' SMART Attribute.
|
||||
|
||||
### Diagnostics[](https://docs.unraid.net/unraid-os/release-notes/7.0.0#diagnostics "Direct link to Diagnostics")
|
||||
|
||||
* Add gpujson from gpu\_statistics to diagnostics
|
||||
* Improved anonymization of LXC logs
|
||||
* If the FCP plugin is installed, run scan during diagnostics
|
||||
* Add phplog to identify PHP errors
|
||||
* Improved anonymization of IPv6 addresses
|
||||
* Removed ps.txt because it exposed passwords in the process list
|
||||
|
||||
### Other changes[](https://docs.unraid.net/unraid-os/release-notes/7.0.0#other-changes-3 "Direct link to Other changes")
|
||||
|
||||
* Support different warning/critical temperature thresholds for HDD/SSD/NVMe drives. NVMe thresholds are set automatically by the drive itself, see _**Settings → Disk Settings**_ to set the thresholds for HDDs and SSDs. All can still be overridden for individual drives.
|
||||
* Add _**Settings → Local Console Settings**_ page with options for keyboard layout, screen blank time, and persistent Bash history
|
||||
* Add _**Settings → Power Mode**_ to optimize the system for power efficiency, balanced, or performance
|
||||
* Hover over an entry on **Tools** and **Settings** to favorite an item, and quickly get back to it on the new top-level **Favorites** page. Or disable Favorites functionality on \***Settings → Display Settings**.
|
||||
* Enhanced shutdown/restart screen showing more details of the process
|
||||
* Simplify notifications by removing submenus - View, History, and Acknowledge now apply to all notification types
|
||||
* Move date & time settings from **Display Settings** to _**Settings → Date & Time Settings**_
|
||||
* _**Settings → Display settings**_: new setting "width" to take advantage of larger screens
|
||||
* Optionally display NVMe power usage; see _**Settings → Disk Settings**_
|
||||
* Web component enhancements – downgrades, updates, and registration
|
||||
* Prevent formatting new drives as ReiserFS
|
||||
* Use atomic writes for updates of config files
|
||||
* ZFS pool settings changes:
|
||||
* Create meaningful ZFS subpool descriptions
|
||||
* Change ZFS profile text 'raid0' to 'stripe'
|
||||
* Add additional USB device passthrough smartmontools options to webgui (thanks to GitHub user jski)
|
||||
* UPS Settings page (thanks to @othyn):
|
||||
* Add the ability to set a manual UPS capacity override.
|
||||
* UserEdit: in addition to Ed25519, FIDO/U2F Ed25519, and RSA, support SSH key types DSA, ECDSA, and FIDO/U2F ECDSA
|
||||
* OpenTerminal: use shell defined for root user in /etc/passwd file
|
||||
* Always display the "delete share" option, but disable it when the share is not empty
|
||||
|
||||
Misc[](https://docs.unraid.net/unraid-os/release-notes/7.0.0#misc "Direct link to Misc")
|
||||
|
||||
------------------------------------------------------------------------------------------
|
||||
|
||||
### Other changes[](https://docs.unraid.net/unraid-os/release-notes/7.0.0#other-changes-4 "Direct link to Other changes")
|
||||
|
||||
* Replace very old 'memtest' with Memtest86+ version 6.20
|
||||
* There are also [Boot Options](https://github.com/memtest86plus/memtest86plus#boot-options)
|
||||
available
|
||||
* Remove support for legacy unraid.net certs
|
||||
* Remove "UpdateDNS" functionality since no longer using legacy non-wildcard 'unraid.net' SSL certs
|
||||
* Strip proxy info and '&' from go script
|
||||
* passwd file handling correction
|
||||
* When avahidaemon running, add name.local to hosts file
|
||||
* Remove keys.lime-technology.com from hosts file
|
||||
* rc.S: remove wsync from XFS mount to prevent WebGUI from freezing during heavy I/O on /boot
|
||||
* make\_bootable\_linux: version 1.4
|
||||
* detect if mtools is installed
|
||||
* ntp.conf: set 'logconfig' to ignore LOG\_INFO
|
||||
* Speed things up: use AVAHI reload instead of restart
|
||||
* Linux kernel: force all buggy Seagate external USB enclosures to bind to usb-storage instead of UAS driver
|
||||
* Startup improvements in rc.S script:
|
||||
* Automatically repair boot sector backup
|
||||
* Explicitly unmount all file systems if cannot continue boot
|
||||
* Detect bad root value in syslinux.cfg
|
||||
* reboot should not invoke shutdown
|
||||
* Clean up empty cgroups
|
||||
* Samba smb.conf: set "nmbd bind explicit broadcast = no" if NetBIOS enabled
|
||||
* Add fastcgi\_path\_info to default nginx configuration
|
||||
* Ensure calls to pgrep or killall are restricted to the current namespace
|
||||
* (Advanced) Added ability to apply custom udev rules from `/boot/config/udev/` upon boot
|
||||
* Bug fix: Correct handling of empty Trial.key when download fails
|
||||
* Bug fix: Fix PHP warning for UPS status
|
||||
* Create meaningful /etc/os-release file
|
||||
* Misc translation fixes
|
||||
* Bug fix: JavaScript console logging functionality restored
|
||||
* Clicking Unraid version number loads release notes from Unraid Docs website
|
||||
|
||||
Linux kernel[](https://docs.unraid.net/unraid-os/release-notes/7.0.0#linux-kernel "Direct link to Linux kernel")
|
||||
|
||||
------------------------------------------------------------------------------------------------------------------
|
||||
|
||||
* version 6.6.68
|
||||
* CONFIG\_MISC\_RTSX\_PCI: Realtek PCI-E card reader
|
||||
* CONFIG\_MISC\_RTSX\_USB: Realtek USB card reader
|
||||
* CONFIG\_DRM\_XE: Intel Xe Graphics
|
||||
* CONFIG\_DRM\_XE\_DISPLAY: Enable display support
|
||||
* CONFIG\_AUDIT: Auditing support
|
||||
* CONFIG\_USB\_SERIAL\_OPTION: USB driver for GSM and CDMA modems
|
||||
* CONFIG\_USB\_SERIAL\_SIMPLE: USB Serial Simple Driver
|
||||
* CONFIG\_USB\_UAS: USB Attached SCSI
|
||||
* CONFIG\_NFS\_V4\_1: NFS client support for NFSv4.1
|
||||
* CONFIG\_NFS\_V4\_1\_MIGRATION: NFSv4.1 client support for migration
|
||||
* CONFIG\_NFS\_V4\_2: NFS client support for NFSv4.2
|
||||
* CONFIG\_NFS\_V4\_2\_READ\_PLUS: NFS: Enable support for the NFSv4.2 READ\_PLUS operation
|
||||
* CONFIG\_NFSD\_V4\_2\_INTER\_SSC: NFSv4.2 inter server to server COPY
|
||||
* CONFIG\_USB\_NET\_CDC\_EEM: CDC EEM support
|
||||
* CONFIG\_USB\_NET\_CDC\_NCM: CDC NCM support
|
||||
* CONFIG\_USB\_SERIAL\_XR: USB MaxLinear/Exar USB to Serial driver
|
||||
* CONFIG\_CAN: CAN bus subsystem support
|
||||
* CONFIG\_CAN\_NETLINK: CAN device drivers with Netlink support
|
||||
* CONFIG\_CAN\_GS\_USB: Geschwister Schneider UG and candleLight compatible interfaces
|
||||
* CONFIG\_SCSI\_LPFC: Emulex LightPulse Fibre Channel Support
|
||||
* CONFIG\_DRM\_VIRTIO\_GPU: Virtio GPU driver
|
||||
* CONFIG\_DRM\_VIRTIO\_GPU\_KMS: Virtio GPU driver modesetting support
|
||||
* CONFIG\_LEDS\_TRIGGERS: LED Trigger support
|
||||
* CONFIG\_LEDS\_TRIGGER\_ONESHOT: LED One-shot Trigger
|
||||
* CONFIG\_LEDS\_TRIGGER\_NETDEV: LED Netdev Trigger
|
||||
* CONFIG\_QED: QLogic QED 25/40/100Gb core driver
|
||||
* CONFIG\_QED\_SRIOV: QLogic QED 25/40/100Gb SR-IOV support
|
||||
* CONFIG\_QEDE: QLogic QED 25/40/100Gb Ethernet NIC
|
||||
* CONFIG\_SCSI\_UFSHCD: Universal Flash Storage Controller
|
||||
* CONFIG\_SCSI\_UFS\_BSG: Universal Flash Storage BSG device node
|
||||
* CONFIG\_SCSI\_UFS\_HWMON: UFS Temperature Notification
|
||||
* CONFIG\_SCSI\_UFSHCD\_PCI: PCI bus based UFS Controller support
|
||||
* CONFIG\_SCSI\_UFS\_DWC\_TC\_PCI: DesignWare pci support using a G210 Test Chip
|
||||
* CONFIG\_SCSI\_UFSHCD\_PLATFORM: Platform bus based UFS Controller support
|
||||
* CONFIG\_SCSI\_UFS\_CDNS\_PLATFORM: Cadence UFS Controller platform driver
|
||||
* CONFIG\_SCSI\_QLA\_FC: QLogic QLA2XXX Fibre Channel Support
|
||||
* CONFIG\_LIQUIDIO: Cavium LiquidIO support
|
||||
* CONFIG\_LIQUIDIO\_VF: Cavium LiquidIO VF support
|
||||
* CONFIG\_NTFS\_FS: NTFS file system support \[removed - this is the old read-only vfs module\]
|
||||
* CONFIG\_NTFS3\_FS: NTFS Read-Write file system support
|
||||
* CONFIG\_NTFS3\_LZX\_XPRESS: activate support of external compressions lzx/xpress
|
||||
* CONFIG\_NTFS3\_FS\_POSIX\_ACL: NTFS POSIX Access Control Lists
|
||||
* CONFIG\_UHID: User-space I/O driver support for HID subsystem
|
||||
* md/unraid: version 2.9.33
|
||||
* fix regression: empty slots before first occupied slot returns NO\_DEVICES
|
||||
* fix handling of device failure during rebuild/sync
|
||||
* removed XEN support
|
||||
|
||||
Base distro[](https://docs.unraid.net/unraid-os/release-notes/7.0.0#base-distro "Direct link to Base distro")
|
||||
|
||||
---------------------------------------------------------------------------------------------------------------
|
||||
|
||||
* aaa\_base: version 15.1
|
||||
* aaa\_glibc-solibs: version 2.40
|
||||
* aaa\_libraries: version 15.1
|
||||
* acl: version 2.3.2
|
||||
* acpid: version 2.0.34
|
||||
* adwaita-icon-theme: version 47.0
|
||||
* apcupsd: version 3.14.14
|
||||
* appres: version 1.0.7
|
||||
* at: version 3.2.5
|
||||
* at-spi2-atk: version 2.38.0
|
||||
* at-spi2-core: version 2.54.0
|
||||
* atk: version 2.38.0
|
||||
* attr: version 2.5.2
|
||||
* avahi: version 0.8
|
||||
* bash: version 5.2.037
|
||||
* bash-completion: version 2.16.0
|
||||
* beep: version 1.3
|
||||
* bin: version 11.1
|
||||
* bind: version 9.20.4
|
||||
* bluez-firmware: version 1.2
|
||||
* bridge-utils: version 1.7.1
|
||||
* brotli: version 1.1.0
|
||||
* btrfs-progs: version 6.12
|
||||
* bzip2: version 1.0.8
|
||||
* ca-certificates: version 20241120
|
||||
* cairo: version 1.18.2
|
||||
* celt051: version 0.5.1.3
|
||||
* cifs-utils: version 7.1
|
||||
* coreutils: version 9.5
|
||||
* cpio: version 2.15
|
||||
* cpufrequtils: version 008
|
||||
* cracklib: version 2.10.3
|
||||
* cryptsetup: version 2.7.5
|
||||
* curl: version 8.11.1
|
||||
* cyrus-sasl: version 2.1.28
|
||||
* db48: version 4.8.30
|
||||
* dbus: version 1.16.0
|
||||
* dbus-glib: version 0.112
|
||||
* dcron: version 4.5
|
||||
* dejavu-fonts-ttf: version 2.37
|
||||
* devs: version 2.3.1
|
||||
* dhcpcd: version 10.0.10
|
||||
* diffutils: version 3.10
|
||||
* dmidecode: version 3.6
|
||||
* dnsmasq: version 2.90
|
||||
* docker: version 27.0.3
|
||||
* dosfstools: version 4.2
|
||||
* e2fsprogs: version 1.47.1
|
||||
* ebtables: version 2.0.11
|
||||
* editres: version 1.0.9
|
||||
* elfutils: version 0.192
|
||||
* elogind: version 255.5
|
||||
* elvis: version 2.2\_0
|
||||
* encodings: version 1.1.0
|
||||
* etc: version 15.1
|
||||
* ethtool: version 5.19
|
||||
* eudev: version 3.2.14
|
||||
* file: version 5.46
|
||||
* findutils: version 4.10.0
|
||||
* flex: version 2.6.4
|
||||
* floppy: version 5.5
|
||||
* fluxbox: version 1.3.7
|
||||
* fontconfig: version 2.15.0
|
||||
* freeglut: version 3.6.0
|
||||
* freetype: version 2.13.3
|
||||
* fribidi: version 1.0.16
|
||||
* fuse3: version 3.16.2
|
||||
* gawk: version 5.3.1
|
||||
* gd: version 2.3.3
|
||||
* gdbm: version 1.24
|
||||
* gdk-pixbuf2: version 2.42.12
|
||||
* genpower: version 1.0.5
|
||||
* git: version 2.47.1
|
||||
* glew: version 2.2.0
|
||||
* glib2: version 2.82.4
|
||||
* glibc: version 2.40
|
||||
* glibc-zoneinfo: version 2024b
|
||||
* glu: version 9.0.3
|
||||
* gmp: version 6.3.0
|
||||
* gnutls: version 3.8.8
|
||||
* gptfdisk: version 1.0.10
|
||||
* graphite2: version 1.3.14
|
||||
* grep: version 3.11
|
||||
* gtk+3: version 3.24.43
|
||||
* gzip: version 1.13
|
||||
* harfbuzz: version 10.1.0
|
||||
* hdparm: version 9.65
|
||||
* hicolor-icon-theme: version 0.18
|
||||
* hostname: version 3.25
|
||||
* htop: version 3.3.0
|
||||
* hwloc: version 2.2.0
|
||||
* icu4c: version 76.1
|
||||
* imlib2: version 1.7.1
|
||||
* inetd: version 1.79s
|
||||
* infozip: version 6.0
|
||||
* inih: version 58
|
||||
* inotify-tools: version 4.23.9.0
|
||||
* intel-microcode: version 20241112
|
||||
* iperf3: version 3.17.1
|
||||
* iproute2: version 6.12.0
|
||||
* iptables: version 1.8.11
|
||||
* iputils: version 20240905
|
||||
* irqbalance: version 1.7.0
|
||||
* jansson: version 2.14
|
||||
* jemalloc: version 5.3.0
|
||||
* jq: version 1.6
|
||||
* json-c: version 0.18\_20240915
|
||||
* json-glib: version 1.10.6
|
||||
* kbd: version 2.7.1
|
||||
* kernel-firmware: version 20241220\_9e1d9ae
|
||||
* keyutils: version 1.6.3
|
||||
* kmod: version 33
|
||||
* krb5: version 1.21.3
|
||||
* lbzip2: version 2.5
|
||||
* less: version 668
|
||||
* libICE: version 1.1.2
|
||||
* libSM: version 1.2.5
|
||||
* libX11: version 1.8.10
|
||||
* libXau: version 1.0.12
|
||||
* libXaw: version 1.0.16
|
||||
* libXcomposite: version 0.4.6
|
||||
* libXcursor: version 1.2.3
|
||||
* libXdamage: version 1.1.6
|
||||
* libXdmcp: version 1.1.5
|
||||
* libXevie: version 1.0.3
|
||||
* libXext: version 1.3.6
|
||||
* libXfixes: version 6.0.1
|
||||
* libXfont2: version 2.0.7
|
||||
* libXfontcache: version 1.0.5
|
||||
* libXft: version 2.3.8
|
||||
* libXi: version 1.8.2
|
||||
* libXinerama: version 1.1.5
|
||||
* libXmu: version 1.2.1
|
||||
* libXpm: version 3.5.17
|
||||
* libXrandr: version 1.5.4
|
||||
* libXrender: version 0.9.12
|
||||
* libXres: version 1.2.2
|
||||
* libXt: version 1.3.1
|
||||
* libXtst: version 1.2.5
|
||||
* libXxf86dga: version 1.1.6
|
||||
* libXxf86misc: version 1.0.4
|
||||
* libXxf86vm: version 1.1.6
|
||||
* libaio: version 0.3.113
|
||||
* libarchive: version 3.7.7
|
||||
* libcap-ng: version 0.8.5
|
||||
* libcgroup: version 0.41
|
||||
* libdaemon: version 0.14
|
||||
* libdeflate: version 1.23
|
||||
* libdmx: version 1.1.5
|
||||
* libdrm: version 2.4.124
|
||||
* libedit: version 20240808\_3.1
|
||||
* libepoxy: version 1.5.10
|
||||
* libestr: version 0.1.9
|
||||
* libevdev: version 1.13.3
|
||||
* libevent: version 2.1.12
|
||||
* libfastjson: version 0.99.9
|
||||
* libffi: version 3.4.6
|
||||
* libfontenc: version 1.1.8
|
||||
* libgcrypt: version 1.11.0
|
||||
* libglvnd: version 1.7.0
|
||||
* libgpg-error: version 1.51
|
||||
* libgudev: version 238
|
||||
* libidn: version 1.42
|
||||
* libjpeg-turbo: version 3.1.0
|
||||
* liblogging: version 1.0.6
|
||||
* libmnl: version 1.0.5
|
||||
* libnetfilter\_conntrack: version 1.1.0
|
||||
* libnfnetlink: version 1.0.2
|
||||
* libnftnl: version 1.2.8
|
||||
* libnl3: version 3.11.0
|
||||
* libnvme: version 1.11.1
|
||||
* libpcap: version 1.10.5
|
||||
* libpciaccess: version 0.18.1
|
||||
* libpng: version 1.6.44
|
||||
* libpsl: version 0.21.5
|
||||
* libpthread-stubs: version 0.5
|
||||
* libseccomp: version 2.5.5
|
||||
* libssh: version 0.11.1
|
||||
* libssh2: version 1.11.1
|
||||
* libtasn1: version 4.19.0
|
||||
* libtiff: version 4.7.0
|
||||
* libtirpc: version 1.3.6
|
||||
* libtpms: version 0.9.0
|
||||
* libunistring: version 1.3
|
||||
* libunwind: version 1.8.1
|
||||
* libusb: version 1.0.27
|
||||
* libusb-compat: version 0.1.8
|
||||
* libuv: version 1.49.2
|
||||
* libvirt: version 10.7.0
|
||||
* libvirt-php: version 0.5.8
|
||||
* libwebp: version 1.5.0
|
||||
* libwebsockets: version 4.3.2
|
||||
* libx86: version 1.1
|
||||
* libxcb: version 1.17.0
|
||||
* libxcvt: version 0.1.3
|
||||
* libxkbcommon: version 1.7.0
|
||||
* libxkbfile: version 1.1.3
|
||||
* libxml2: version 2.13.5
|
||||
* libxshmfence: version 1.3.3
|
||||
* libxslt: version 1.1.42
|
||||
* libzip: version 1.11.2
|
||||
* listres: version 1.0.6
|
||||
* lm\_sensors: version 3.6.0
|
||||
* lmdb: version 0.9.33
|
||||
* logrotate: version 3.22.0
|
||||
* lshw: version B.02.19.2
|
||||
* lsof: version 4.99.4
|
||||
* lsscsi: version 0.32
|
||||
* lvm2: version 2.03.29
|
||||
* lz4: version 1.10.0
|
||||
* lzip: version 1.24.1
|
||||
* lzlib: version 1.14
|
||||
* lzo: version 2.10
|
||||
* mbuffer: version 20240107
|
||||
* mc: version 4.8.31
|
||||
* mcelog: version 202
|
||||
* mesa: version 24.2.8
|
||||
* miniupnpc: version 2.1
|
||||
* mkfontscale: version 1.2.3
|
||||
* mpfr: version 4.2.1
|
||||
* mtdev: version 1.1.7
|
||||
* nano: version 8.3
|
||||
* ncompress: version 5.0
|
||||
* ncurses: version 6.5
|
||||
* net-tools: version 20181103\_0eebece
|
||||
* nettle: version 3.10
|
||||
* network-scripts: version 15.1
|
||||
* nfs-utils: version 2.8.2
|
||||
* nghttp2: version 1.64.0
|
||||
* nghttp3: version 1.7.0
|
||||
* nginx: version 1.27.2
|
||||
* noto-fonts-ttf: version 2024.12.01
|
||||
* nss-mdns: version 0.14.1
|
||||
* ntfs-3g: version 2022.10.3
|
||||
* ntp: version 4.2.8p18
|
||||
* numactl: version 2.0.13
|
||||
* nvme-cli: version 2.11
|
||||
* oniguruma: version 6.9.9
|
||||
* openssh: version 9.9p1
|
||||
* openssl: version 3.4.0
|
||||
* ovmf: version stable202411
|
||||
* p11-kit: version 0.25.5
|
||||
* pam: version 1.6.1
|
||||
* pango: version 1.54.0
|
||||
* patch: version 2.7.6
|
||||
* pciutils: version 3.13.0
|
||||
* pcre: version 8.45
|
||||
* pcre2: version 10.44
|
||||
* perl: version 5.40.0
|
||||
* php: version 8.3.8
|
||||
* pixman: version 0.44.2
|
||||
* pkgtools: version 15.1
|
||||
* procps-ng: version 4.0.4
|
||||
* pv: version 1.6.6
|
||||
* qemu: version 9.1.0
|
||||
* qrencode: version 4.1.1
|
||||
* readline: version 8.2.013
|
||||
* reiserfsprogs: version 3.6.27
|
||||
* rpcbind: version 1.2.6
|
||||
* rsync: version 3.3.0
|
||||
* rsyslog: version 8.2102.0
|
||||
* sakura: version 3.5.0
|
||||
* samba: version 4.21.1
|
||||
* sdparm: version 1.12
|
||||
* sed: version 4.9
|
||||
* sessreg: version 1.1.3
|
||||
* setxkbmap: version 1.3.4
|
||||
* sg3\_utils: version 1.48
|
||||
* shadow: version 4.16.0
|
||||
* shared-mime-info: version 2.4
|
||||
* slim: version 1.3.6
|
||||
* smartmontools: version 7.4
|
||||
* spice: version 0.15.0
|
||||
* spirv-llvm-translator: version 19.1.2
|
||||
* sqlite: version 3.46.1
|
||||
* ssmtp: version 2.64
|
||||
* startup-notification: version 0.12
|
||||
* sudo: version 1.9.16p2
|
||||
* swtpm: version 0.7.3
|
||||
* sysfsutils: version 2.1.1
|
||||
* sysstat: version 12.7.6
|
||||
* sysvinit: version 3.12
|
||||
* sysvinit-scripts: version 15.1
|
||||
* talloc: version 2.4.2
|
||||
* tar: version 1.35
|
||||
* tcp\_wrappers: version 7.6
|
||||
* tdb: version 1.4.12
|
||||
* telnet: version 0.17
|
||||
* tevent: version 0.16.1
|
||||
* traceroute: version 2.1.6
|
||||
* transset: version 1.0.4
|
||||
* tree: version 2.1.1
|
||||
* usbredir: version 0.8.0
|
||||
* usbutils: version 018
|
||||
* userspace-rcu: version 0.15.0
|
||||
* utempter: version 1.2.1
|
||||
* util-linux: version 2.40.2
|
||||
* vbetool: version 1.2.2
|
||||
* virtiofsd: version 1.11.1
|
||||
* vsftpd: version 3.0.5
|
||||
* vte3: version 0.50.2
|
||||
* wayland: version 1.23.1
|
||||
* wget: version 1.25.0
|
||||
* which: version 2.21
|
||||
* wireguard-tools: version 1.0.20210914
|
||||
* wqy-zenhei-font-ttf: version 0.8.38\_1
|
||||
* wsdd2: version 1.8.7
|
||||
* xauth: version 1.1.3
|
||||
* xcb-util: version 0.4.1
|
||||
* xcb-util-keysyms: version 0.4.1
|
||||
* xclock: version 1.1.1
|
||||
* xdpyinfo: version 1.3.4
|
||||
* xdriinfo: version 1.0.7
|
||||
* xev: version 1.2.6
|
||||
* xf86-input-evdev: version 2.11.0
|
||||
* xf86-input-keyboard: version 1.9.0
|
||||
* xf86-input-mouse: version 1.9.3
|
||||
* xf86-input-synaptics: version 1.9.2
|
||||
* xf86-video-ast: version 1.1.5
|
||||
* xf86-video-mga: version 2.1.0
|
||||
* xf86-video-vesa: version 2.6.0
|
||||
* xfsprogs: version 6.12.0
|
||||
* xhost: version 1.0.9
|
||||
* xinit: version 1.4.2
|
||||
* xkbcomp: version 1.4.7
|
||||
* xkbevd: version 1.1.6
|
||||
* xkbutils: version 1.0.6
|
||||
* xkeyboard-config: version 2.43
|
||||
* xkill: version 1.0.6
|
||||
* xload: version 1.2.0
|
||||
* xlsatoms: version 1.1.4
|
||||
* xlsclients: version 1.1.5
|
||||
* xmessage: version 1.0.7
|
||||
* xmodmap: version 1.0.11
|
||||
* xorg-server: version 21.1.15
|
||||
* xprop: version 1.2.8
|
||||
* xrandr: version 1.5.3
|
||||
* xrdb: version 1.2.2
|
||||
* xrefresh: version 1.1.0
|
||||
* xset: version 1.2.5
|
||||
* xsetroot: version 1.1.3
|
||||
* xsm: version 1.0.6
|
||||
* xterm: version 396
|
||||
* xtrans: version 1.5.2
|
||||
* xwd: version 1.0.9
|
||||
* xwininfo: version 1.1.6
|
||||
* xwud: version 1.0.7
|
||||
* xxHash: version 0.8.3
|
||||
* xz: version 5.6.3
|
||||
* yajl: version 2.1.0
|
||||
* zfs: version 2.2.7\_6.6.68\_Unraid
|
||||
* zlib: version 1.3.1
|
||||
* zstd: version 1.5.6
|
||||
|
||||
Patches[](https://docs.unraid.net/unraid-os/release-notes/7.0.0#patches "Direct link to Patches")
|
||||
|
||||
---------------------------------------------------------------------------------------------------
|
||||
|
||||
With the [Unraid Patch plugin](https://forums.unraid.net/topic/185560-unraid-patch-plugin/)
|
||||
installed, visit _**Tools → Unraid Patch**_ to get the following patches / hot fixes:
|
||||
|
||||
* mover was not moving shares with spaces in the name from array to pool
|
||||
* File Manager: allow access to UD remote shares
|
||||
* Share Listing: tool tip showed `%20` instead of a space
|
||||
* VM Manager: fix issue with blank Discard field on vDisk
|
||||
* Include installed patches in diagnostics
|
||||
|
||||
Note: if you have the Mover Tuning plugin installed, you will be prompted to reboot in order to apply these patches.
|
||||
|
||||
* [Upgrading](https://docs.unraid.net/unraid-os/release-notes/7.0.0#upgrading)
|
||||
* [Known issues](https://docs.unraid.net/unraid-os/release-notes/7.0.0#known-issues)
|
||||
|
||||
* [Rolling back](https://docs.unraid.net/unraid-os/release-notes/7.0.0#rolling-back)
|
||||
|
||||
* [Storage](https://docs.unraid.net/unraid-os/release-notes/7.0.0#storage)
|
||||
* [unRAID array optional](https://docs.unraid.net/unraid-os/release-notes/7.0.0#unraid-array-optional)
|
||||
|
||||
* [Share secondary storage may be assigned to a pool](https://docs.unraid.net/unraid-os/release-notes/7.0.0#share-secondary-storage-may-be-assigned-to-a-pool)
|
||||
|
||||
* [ReiserFS file system option has been disabled](https://docs.unraid.net/unraid-os/release-notes/7.0.0#reiserfs-file-system-option-has-been-disabled)
|
||||
|
||||
* [Using 'mover' to empty an array disk](https://docs.unraid.net/unraid-os/release-notes/7.0.0#using-mover-to-empty-an-array-disk)
|
||||
|
||||
* [Predefined shares handling](https://docs.unraid.net/unraid-os/release-notes/7.0.0#predefined-shares-handling)
|
||||
|
||||
* [ZFS implementation](https://docs.unraid.net/unraid-os/release-notes/7.0.0#zfs-implementation)
|
||||
|
||||
* [Allocation profiles for btrfs, zfs, and zfs subpools](https://docs.unraid.net/unraid-os/release-notes/7.0.0#allocation-profiles-for-btrfs-zfs-and-zfs-subpools)
|
||||
|
||||
* [Pool considerations](https://docs.unraid.net/unraid-os/release-notes/7.0.0#pool-considerations)
|
||||
|
||||
* [Other features](https://docs.unraid.net/unraid-os/release-notes/7.0.0#other-features)
|
||||
|
||||
* [VM Manager](https://docs.unraid.net/unraid-os/release-notes/7.0.0#vm-manager)
|
||||
* [Improvements](https://docs.unraid.net/unraid-os/release-notes/7.0.0#improvements)
|
||||
|
||||
* [Other changes](https://docs.unraid.net/unraid-os/release-notes/7.0.0#other-changes)
|
||||
|
||||
* [Docker](https://docs.unraid.net/unraid-os/release-notes/7.0.0#docker)
|
||||
* [Docker fork bomb prevention](https://docs.unraid.net/unraid-os/release-notes/7.0.0#docker-fork-bomb-prevention)
|
||||
|
||||
* [Add support for overlay2 storage driver](https://docs.unraid.net/unraid-os/release-notes/7.0.0#add-support-for-overlay2-storage-driver)
|
||||
|
||||
* [Other changes](https://docs.unraid.net/unraid-os/release-notes/7.0.0#other-changes-1)
|
||||
|
||||
* [Networking](https://docs.unraid.net/unraid-os/release-notes/7.0.0#networking)
|
||||
* [Tailscale integration](https://docs.unraid.net/unraid-os/release-notes/7.0.0#tailscale-integration)
|
||||
|
||||
* [Support iframing the webGUI](https://docs.unraid.net/unraid-os/release-notes/7.0.0#support-iframing-the-webgui)
|
||||
|
||||
* [Other changes](https://docs.unraid.net/unraid-os/release-notes/7.0.0#other-changes-2)
|
||||
|
||||
* [webGUI](https://docs.unraid.net/unraid-os/release-notes/7.0.0#webgui)
|
||||
* [Integrated Dynamix File Manager plugin](https://docs.unraid.net/unraid-os/release-notes/7.0.0#integrated-dynamix-file-manager-plugin)
|
||||
|
||||
* [Integrated GUI Search plugin](https://docs.unraid.net/unraid-os/release-notes/7.0.0#integrated-gui-search-plugin)
|
||||
|
||||
* [Outgoing Proxy Manager](https://docs.unraid.net/unraid-os/release-notes/7.0.0#outgoing-proxy-manager)
|
||||
|
||||
* [Notification Agents](https://docs.unraid.net/unraid-os/release-notes/7.0.0#notification-agents)
|
||||
|
||||
* [NTP Configuration](https://docs.unraid.net/unraid-os/release-notes/7.0.0#ntp-configuration)
|
||||
|
||||
* [NFS Shares](https://docs.unraid.net/unraid-os/release-notes/7.0.0#nfs-shares)
|
||||
|
||||
* [Dashboard](https://docs.unraid.net/unraid-os/release-notes/7.0.0#dashboard)
|
||||
|
||||
* [SMART improvements](https://docs.unraid.net/unraid-os/release-notes/7.0.0#smart-improvements)
|
||||
|
||||
* [Diagnostics](https://docs.unraid.net/unraid-os/release-notes/7.0.0#diagnostics)
|
||||
|
||||
* [Other changes](https://docs.unraid.net/unraid-os/release-notes/7.0.0#other-changes-3)
|
||||
|
||||
* [Misc](https://docs.unraid.net/unraid-os/release-notes/7.0.0#misc)
|
||||
* [Other changes](https://docs.unraid.net/unraid-os/release-notes/7.0.0#other-changes-4)
|
||||
|
||||
* [Linux kernel](https://docs.unraid.net/unraid-os/release-notes/7.0.0#linux-kernel)
|
||||
|
||||
* [Base distro](https://docs.unraid.net/unraid-os/release-notes/7.0.0#base-distro)
|
||||
|
||||
* [Patches](https://docs.unraid.net/unraid-os/release-notes/7.0.0#patches)
|
||||
374
docs/research/raw/release-7.1.0.md
Normal file
374
docs/research/raw/release-7.1.0.md
Normal file
@@ -0,0 +1,374 @@
|
||||
[Skip to main content](https://docs.unraid.net/unraid-os/release-notes/7.1.0#__docusaurus_skipToContent_fallback)
|
||||
|
||||
On this page
|
||||
|
||||
This release adds wireless networking, the ability to import TrueNAS and other foreign pools, multiple enhancements to VMs, early steps toward making the webGUI responsive, and more.
|
||||
|
||||
Upgrading[](https://docs.unraid.net/unraid-os/release-notes/7.1.0#upgrading "Direct link to Upgrading")
|
||||
|
||||
---------------------------------------------------------------------------------------------------------
|
||||
|
||||
### Known issues[](https://docs.unraid.net/unraid-os/release-notes/7.1.0#known-issues "Direct link to Known issues")
|
||||
|
||||
This release has a potential data-loss issue where the recent "mover empty disk" feature does not handle split levels on shares correctly. Resolved in 7.1.2.
|
||||
|
||||
#### Plugins[](https://docs.unraid.net/unraid-os/release-notes/7.1.0#plugins "Direct link to Plugins")
|
||||
|
||||
Please upgrade all plugins, particularly Unraid Connect and the Nvidia driver.
|
||||
|
||||
For other known issues, see the [7.0.0 release notes](https://docs.unraid.net/unraid-os/release-notes/7.0.0/#known-issues)
|
||||
.
|
||||
|
||||
### Rolling back[](https://docs.unraid.net/unraid-os/release-notes/7.1.0#rolling-back "Direct link to Rolling back")
|
||||
|
||||
We are making improvements to how we distribute patches between releases, so the standalone Patch Plugin will be uninstalled from this release. If rolling back to an earlier release we'd recommend reinstalling it. More details to come.
|
||||
|
||||
If rolling back earlier than 7.0.0, also see the [7.0.0 release notes](https://docs.unraid.net/unraid-os/release-notes/7.0.0/#rolling-back)
|
||||
.
|
||||
|
||||
Changes vs. [7.0.1](https://docs.unraid.net/unraid-os/release-notes/7.0.1/)
|
||||
[](https://docs.unraid.net/unraid-os/release-notes/7.1.0#changes-vs-701 "Direct link to changes-vs-701")
|
||||
|
||||
--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
|
||||
|
||||
### Storage[](https://docs.unraid.net/unraid-os/release-notes/7.1.0#storage "Direct link to Storage")
|
||||
|
||||
* Import foreign ZFS pools such as TrueNAS, Proxmox, Ubuntu, QNAP.
|
||||
* Import the largest partition on disk instead of the first.
|
||||
* Removing device from btrfs raid1 or zfs single-vdev mirror will now reduce pool slot count.
|
||||
|
||||
#### Other storage changes[](https://docs.unraid.net/unraid-os/release-notes/7.1.0#other-storage-changes "Direct link to Other storage changes")
|
||||
|
||||
* Fix: Disabled disks were not shown on the Dashboard.
|
||||
* Fix: Initially, only the first pool device spins down after adding a custom spin down setting.
|
||||
* Fix: Array Start was permitted if only 2 Parity devices and no Data devices.
|
||||
* Fix: The parity check notification often shows the previous parity check and not the current parity check.
|
||||
* Fix: Resolved certain instances of _Wrong pool State. Too many wrong or missing devices_ when upgrading.
|
||||
* Fix: Not possible to replace a zfs device from a smaller vdev.
|
||||
* mover:
|
||||
* Fix: Resolved issue with older share.cfg files that prevented mover from running.
|
||||
* Fix: mover would fail to recreate hard link if parent directory did not already exist.
|
||||
* Fix: mover would hang on named pipes.
|
||||
* Fix: [Using mover to empty an array disk](https://docs.unraid.net/unraid-os/release-notes/7.0.0/#using-mover-to-empty-an-array-disk)
|
||||
now only moves top level folders that have a corresponding share.cfg file, also fixed a bug that prevented the list of files _not moved_ from displaying.
|
||||
|
||||
### Networking[](https://docs.unraid.net/unraid-os/release-notes/7.1.0#networking "Direct link to Networking")
|
||||
|
||||
#### Wireless Networking[](https://docs.unraid.net/unraid-os/release-notes/7.1.0#wireless-networking "Direct link to Wireless Networking")
|
||||
|
||||
Unraid now supports WiFi! A hard wired connection is typically preferred, but if that isn't possible for your situation you can now setup WiFi.
|
||||
|
||||
For the initial setup you will either need a local keyboard/monitor (boot into GUI mode) or a wired connection. In the future, the USB Creator will be able to configure wireless networking prior to the initial boot.
|
||||
|
||||
* Access the webGUI and visit _**Settings → Network Settings → Wireless wlan0**_
|
||||
* First, enable WiFi
|
||||
* The **Regulatory Region** can generally be left to **Automatic**, but set it to your location if the network you want to connect to is not available
|
||||
* Find your preferred network and click the **Connect to WiFi network** icon
|
||||
* Fill in your WiFi password and other settings, then press **Join this network**
|
||||
* Note: if your goal is to use Docker containers over WiFi, unplug any wired connection before starting Docker
|
||||
|
||||
Additional details
|
||||
|
||||
* WPA2/WPA3 and WPA2/WPA3 Enterprise are supported, if both WPA2 and WPA3 are available then WPA3 is used.
|
||||
* Having both wired and wireless isn't recommended for long term use, it should be one or the other. But if both connections use DHCP and you (un)plug a network cable while wireless is configured, the system (excluding Docker) should adjust within 45-60 seconds.
|
||||
* Wireless chipset support: We expect to have success with modern WiFi adapters, but older adapters may not work. If your WiFi adapter isn't detected, please start a new forum thread and provide your diagnostics so it can be investigated.
|
||||
* If you want to use a USB WiFi adapter, see this list of [USB WiFi adapters that are supported with Linux in-kernel drivers](https://github.com/morrownr/USB-WiFi/blob/main/home/USB_WiFi_Adapters_that_are_supported_with_Linux_in-kernel_drivers.md)
|
||||
|
||||
* Advanced: New firmware files placed in `/boot/config/firmware/` will be copied to `/lib/firmware/` before driver modules are loaded (existing files will not be overwritten).
|
||||
|
||||
Limitations: there are networking limitations when using wireless, as a wlan can only have a single mac address.
|
||||
|
||||
* Only one wireless NIC is supported, wlan0
|
||||
* wlan0 is not able to participate in a bond
|
||||
* Docker containers
|
||||
* On _**Settings → Docker**_, note that when wireless is enabled, the system will ignore the **Docker custom network type** setting and always use **ipvlan** (macvlan is not possible because wireless does not support multiple mac addresses on a single interface)
|
||||
* _**Settings → Docker**_, **Host access to custom networks** must be disabled
|
||||
* A Docker container's **Network Type** cannot use br0/bond0/eth0
|
||||
* Docker has a limitation that it cannot participate in two networks that share the same subnet. If switching between wired and wireless, you will need to restart Docker and reconfigure all existing containers to use the new interface. We recommend setting up either wired or wireless and not switching.
|
||||
* VMs
|
||||
* We recommend setting your VM **Network Source** to **virbr0**, there are no limits to how many VMs you can run in this mode. The VMs will have full network access, the downside is they will not be accessible from the network. You can still access them via VNC to the host.
|
||||
* With some manual configuration, a single VM can be made accessible on the network:
|
||||
* Configure the VM with a static IP address
|
||||
* Configure the same IP address on the ipvtap interface, type: `ip addr add IP-ADDRESS dev shim-wlan0`
|
||||
|
||||
#### Other networking changes[](https://docs.unraid.net/unraid-os/release-notes/7.1.0#other-networking-changes "Direct link to Other networking changes")
|
||||
|
||||
* On _**Settings → Network Settings**_, you can now adjust the server's DNS settings without stopping other services first. See the top of the **eth0** section.
|
||||
* When configuring a network interface, each interface has an **Info** button showing details for the current connection.
|
||||
* When configuring a network interface, the **Desired MTU** field is disabled until you click **Enable jumbo frames**. Hover over the icon for a warning about changing the MTU, in most cases it should be left at the default setting.
|
||||
* When configuring multiple network interfaces, by default the additional interfaces will have their gateway disabled, this is a safe default that works on most networks where a single gateway is required. If an additional gateway is enabled, it will be given a higher metric than existing gateways so there are no conflicts. You can override as needed.
|
||||
* Old network interfaces are automatically removed from config files when you save changes to _**Settings → Network Settings**_.
|
||||
* Fix various issues with DHCP.
|
||||
|
||||
### VM Manager[](https://docs.unraid.net/unraid-os/release-notes/7.1.0#vm-manager "Direct link to VM Manager")
|
||||
|
||||
#### Nouveau GPU driver[](https://docs.unraid.net/unraid-os/release-notes/7.1.0#nouveau-gpu-driver "Direct link to Nouveau GPU driver")
|
||||
|
||||
The Nouveau driver for Nvidia GPUs is now included, disabled by default as we expect most users to want the Nvidia driver instead. To enable it, uninstall the Nvidia driver plugin and run `touch /boot/config/modprobe.d/nouveau.conf` then reboot.
|
||||
|
||||
#### VirGL[](https://docs.unraid.net/unraid-os/release-notes/7.1.0#virgl "Direct link to VirGL")
|
||||
|
||||
You can now share Intel and AMD GPUs between multiple Linux VMs at the same time using VirGL, the virtual 3D OpenGL renderer. When used this way, the GPU will provide accelerated graphics but will not output on the monitor. Note that this does not yet work with Windows VMs or the standard Nvidia plugin (it does work with Nvidia GPUs using the Nouveau driver though).
|
||||
|
||||
To use the virtual GPU in a Linux VM, edit the VM template and set the **Graphics Card** to **Virtual**. Then set the **VM Console Video Driver** to **Virtio(3d)** and select the appropriate **Render GPU** from the list of available GPUs (note that GPUs bound to VFIO-PCI or passed through to other VMs cannot be chosen here, and Nvidia GPUs are available only if the Nouveau driver is enabled).
|
||||
|
||||
#### QXL Virtual GPUs[](https://docs.unraid.net/unraid-os/release-notes/7.1.0#qxl-virtual-gpus "Direct link to QXL Virtual GPUs")
|
||||
|
||||
To use this feature in a VM, edit the VM template and set the **Graphics Card** to **Virtual** and the **VM Console Video Driver** to **QXL (Best)**, you can then choose how many screens it supports and how much memory to allocate to it.
|
||||
|
||||
#### CPU Pinning is optional[](https://docs.unraid.net/unraid-os/release-notes/7.1.0#cpu-pinning-is-optional "Direct link to CPU Pinning is optional")
|
||||
|
||||
CPU pinning is now optional, if no cores are pinned to a VM then the OS chooses which cores to use.
|
||||
|
||||
From _**Settings → CPU Settings**_ or when editing a VM, press **Deselect All** to unpin all cores for this VM and set the number of vCPUs to 1, increase as needed.
|
||||
|
||||
### User VM Templates[](https://docs.unraid.net/unraid-os/release-notes/7.1.0#user-vm-templates "Direct link to User VM Templates")
|
||||
|
||||
To create a user template:
|
||||
|
||||
* Edit the VM, choose **Create Modify Template** and give it a name. It will now be stored as a **User Template**, available on the **Add VM** screen.
|
||||
|
||||
To use a user template:
|
||||
|
||||
* From the VM listing, press **Add VM**, then choose the template from the **User Templates** area.
|
||||
|
||||
Import/Export
|
||||
|
||||
* From the **Add VM** screen, hover over a user template and click the arrow to export the template to a location on the server or download it.
|
||||
* On another Unraid system press **Import from file** or **Upload** to use the template.
|
||||
|
||||
#### Other VM changes[](https://docs.unraid.net/unraid-os/release-notes/7.1.0#other-vm-changes "Direct link to Other VM changes")
|
||||
|
||||
* When the **Primary** GPU is assigned as passthrough for a VM, warn that it may not work without loading a compatible vBIOS.
|
||||
* Fix: Remove confusing _Path does not exist_ message when setting up the VM service
|
||||
* Feat: Unraid VMs can now boot into GUI mode, when using the QXL video driver
|
||||
* Fix: Could not change VM icon when using XML view
|
||||
|
||||
### WebGUI[](https://docs.unraid.net/unraid-os/release-notes/7.1.0#webgui "Direct link to WebGUI")
|
||||
|
||||
#### CSS changes[](https://docs.unraid.net/unraid-os/release-notes/7.1.0#css-changes "Direct link to CSS changes")
|
||||
|
||||
As a step toward making the webGUI responsive, we have reworked the CSS. For the most part, this should not be noticeable aside from some minor color adjustments. We expect that most plugins will be fine as well, although plugin authors may want to review [this documentation](https://github.com/unraid/webgui/blob/master/emhttp/plugins/dynamix/styles/themes/README.md)
|
||||
. Responsiveness will continue to be improved in future releases.
|
||||
|
||||
If you notice alignment issues or color problems in any official theme, please let us know.
|
||||
|
||||
#### nchan out of shared memory issues[](https://docs.unraid.net/unraid-os/release-notes/7.1.0#nchan-out-of-shared-memory-issues "Direct link to nchan out of shared memory issues")
|
||||
|
||||
We have made several changes that should prevent this issue, and if we detect that it happens, we restart nginx in an attempt to automatically recover from it.
|
||||
|
||||
If your Main page never populates, or if you see "nchan: Out of shared memory" in your logs, please start a new forum thread and provide your diagnostics. You can optionally navigate to _**Settings → Display Settings**_ and disable **Allow realtime updates on inactive browsers**; this prevents your browser from requesting certain updates once it loses focus. When in this state you will see a banner saying **Live Updates Paused**, simply click on the webGUI to bring it to the foreground and re-enable live updates. Certain pages will automatically reload to ensure they are displaying the latest information.
|
||||
|
||||
#### Other WebGUI changes[](https://docs.unraid.net/unraid-os/release-notes/7.1.0#other-webgui-changes "Direct link to Other WebGUI changes")
|
||||
|
||||
* Fix: AdBlockers could prevent Dashboard from loading
|
||||
* Fix: Under certain circumstances, browser memory utilization on the Dashboard could exponentially grow
|
||||
* Fix: Prevent corrupted config file from breaking the Dashboard
|
||||
|
||||
Misc[](https://docs.unraid.net/unraid-os/release-notes/7.1.0#misc "Direct link to Misc")
|
||||
|
||||
------------------------------------------------------------------------------------------
|
||||
|
||||
### Other changes[](https://docs.unraid.net/unraid-os/release-notes/7.1.0#other-changes "Direct link to Other changes")
|
||||
|
||||
* On _**Settings → Date and Time**_ you can now sync your clock with a **PTP** server (we expect most users will continue to use **NTP**)
|
||||
* Upgraded to jQuery 3.7.1 and jQuery UI 1.14.1
|
||||
* Fix: Visiting boot.php will no longer shutdown the server
|
||||
* Fix: On the Docker tab, the dropdown menu for the last container was truncated in certain situations
|
||||
* Fix: On _**Settings → Docker**_, deleting a **Docker directory** stored on a ZFS volume now works properly
|
||||
* Fix: On boot, custom ssh configuration copied from `/boot/config/ssh/` to `/etc/ssh/` again
|
||||
* Fix: File Manager can copy files from a User Share to an Unassigned Disk mount
|
||||
* Fix: Remove confusing _Path does not exist_ message when setting up the Docker service
|
||||
* Fix: update `rc.messagebus` to correct handling of `/etc/machine-id`
|
||||
* Diagnostics
|
||||
* Fix: Improved anonymization of IPv6 addresses in diagnostics
|
||||
* Fix: Improved anonymization of user names in certain config files in diagnostics
|
||||
* Fix: diagnostics could fail due to multibyte strings in syslog
|
||||
* Feat: diagnostics now logs errors in logs/diagnostics.error.log
|
||||
|
||||
### Linux kernel[](https://docs.unraid.net/unraid-os/release-notes/7.1.0#linux-kernel "Direct link to Linux kernel")
|
||||
|
||||
* version 6.12.24-Unraid
|
||||
|
||||
* Apply: \[PATCH\] [Revert "PCI: Avoid reset when disabled via sysfs"](https://lore.kernel.org/lkml/20250414211828.3530741-1-alex.williamson@redhat.com/)
|
||||
|
||||
* CONFIG\_NR\_CPUS: increased from 256 to 512
|
||||
* CONFIG\_TEHUTI\_TN40: Tehuti Networks TN40xx 10G Ethernet adapters
|
||||
* CONFIG\_DRM\_XE: Intel Xe Graphics
|
||||
* CONFIG\_UDMABUF: userspace dmabuf misc driver
|
||||
* CONFIG\_DRM\_NOUVEAU: Nouveau (NVIDIA) cards
|
||||
* CONFIG\_DRM\_QXL: QXL virtual GPU
|
||||
* CONFIG\_EXFAT\_FS: exFAT filesystem support
|
||||
* CONFIG\_PSI: Pressure stall information tracking
|
||||
* CONFIG\_PSI\_DEFAULT\_DISABLED: Require boot parameter to enable pressure stall information tracking, i.e., `psi=1`
|
||||
* CONFIG\_ENCLOSURE\_SERVICES: Enclosure Services
|
||||
* CONFIG\_SCSI\_ENCLOSURE: SCSI Enclosure Support
|
||||
* CONFIG\_DRM\_ACCEL: Compute Acceleration Framework
|
||||
* CONFIG\_DRM\_ACCEL\_HABANALABS: HabanaLabs AI accelerators
|
||||
* CONFIG\_DRM\_ACCEL\_IVPU: Intel NPU (Neural Processing Unit)
|
||||
* CONFIG\_DRM\_ACCEL\_QAIC: Qualcomm Cloud AI accelerators
|
||||
* zfs: version 2.3.1
|
||||
* Wireless support
|
||||
|
||||
* Atheros/Qualcomm
|
||||
* Broadcom
|
||||
* Intel
|
||||
* Marvell
|
||||
* Microtek
|
||||
* Realtek
|
||||
|
||||
### Base distro updates[](https://docs.unraid.net/unraid-os/release-notes/7.1.0#base-distro-updates "Direct link to Base distro updates")
|
||||
|
||||
* aaa\_glibc-solibs: version 2.41
|
||||
* adwaita-icon-theme: version 48.0
|
||||
* at-spi2-core: version 2.56.1
|
||||
* bind: version 9.20.8
|
||||
* btrfs-progs: version 6.14
|
||||
* ca-certificates: version 20250425
|
||||
* cairo: version 1.18.4
|
||||
* cifs-utils: version 7.3
|
||||
* coreutils: version 9.7
|
||||
* dbus: version 1.16.2
|
||||
* dbus-glib: version 0.114
|
||||
* dhcpcd: version 9.5.2
|
||||
* diffutils: version 3.12
|
||||
* dnsmasq: version 2.91
|
||||
* docker: version 27.5.1
|
||||
* e2fsprogs: version 1.47.2
|
||||
* elogind: version 255.17
|
||||
* elfutils: version 0.193
|
||||
* ethtool: version 6.14
|
||||
* firefox: version 128.10 (AppImage)
|
||||
* floppy: version 5.6
|
||||
* fontconfig: version 2.16.2
|
||||
* gdbm: version 1.25
|
||||
* git: version 2.49.0
|
||||
* glib2: version 2.84.1
|
||||
* glibc: version 2.41
|
||||
* glibc-zoneinfo: version 2025b
|
||||
* grep: version 3.12
|
||||
* gtk+3: version 3.24.49
|
||||
* gzip: version 1.14
|
||||
* harfbuzz: version 11.1.0
|
||||
* htop: version 3.4.1
|
||||
* icu4c: version 77.1
|
||||
* inih: version 60
|
||||
* intel-microcode: version 20250211
|
||||
* iperf3: version 3.18
|
||||
* iproute2: version 6.14.0
|
||||
* iw: version 6.9
|
||||
* jansson: version 2.14.1
|
||||
* kernel-firmware: version 20250425\_cf6ea3d
|
||||
* kmod: version 34.2
|
||||
* less: version 674
|
||||
* libSM: version 1.2.6
|
||||
* libX11: version 1.8.12
|
||||
* libarchive: version 3.7.8
|
||||
* libcgroup: version 3.2.0
|
||||
* libedit: version 20250104\_3.1
|
||||
* libevdev: version 1.13.4
|
||||
* libffi: version 3.4.8
|
||||
* libidn: version 1.43
|
||||
* libnftnl: version 1.2.9
|
||||
* libnvme: version 1.13
|
||||
* libgpg-error: version 1.55
|
||||
* libpng: version 1.6.47
|
||||
* libseccomp: version 2.6.0
|
||||
* liburing: version 2.9
|
||||
* libusb: version 1.0.28
|
||||
* libuv: version 1.51.0
|
||||
* libvirt: version 11.2.0
|
||||
* libXft: version 2.3.9
|
||||
* libxkbcommon: version 1.9.0
|
||||
* libxml2: version 2.13.8
|
||||
* libxslt: version 1.1.43
|
||||
* libzip: version 1.11.3
|
||||
* linuxptp: version 4.4
|
||||
* lvm2: version 2.03.31
|
||||
* lzip: version 1.25
|
||||
* lzlib: version 1.15
|
||||
* mcelog: version 204
|
||||
* mesa: version 25.0.4
|
||||
* mpfr: version 4.2.2
|
||||
* nano: version 8.4
|
||||
* ncurses: version 6.5\_20250419
|
||||
* nettle: version 3.10.1
|
||||
* nghttp2: version 1.65.0
|
||||
* nghttp3: version 1.9.0
|
||||
* noto-fonts-ttf: version 2025.03.01
|
||||
* nvme-cli: version 2.13
|
||||
* oniguruma: version 6.9.10
|
||||
* openssh: version 10.0p1
|
||||
* openssl: version 3.5.0
|
||||
* ovmf: version stable202502
|
||||
* pam: version 1.7.0
|
||||
* pango: version 1.56.3
|
||||
* parted: version 3.6
|
||||
* patch: version 2.8
|
||||
* pcre2: version 10.45
|
||||
* perl: version 5.40.2
|
||||
* php: version 8.3.19
|
||||
* procps-ng: version 4.0.5
|
||||
* qemu: version 9.2.3
|
||||
* rsync: version 3.4.1
|
||||
* samba: version 4.21.3
|
||||
* shadow: version 4.17.4
|
||||
* spice: version 0.15.2
|
||||
* spirv-llvm-translator: version 20.1.0
|
||||
* sqlite: version 3.49.1
|
||||
* sysstat: version 12.7.7
|
||||
* sysvinit: version 3.14
|
||||
* talloc: version 2.4.3
|
||||
* tdb: version 1.4.13
|
||||
* tevent: version 0.16.2
|
||||
* tree: version 2.2.1
|
||||
* userspace-rcu: version 0.15.2
|
||||
* utempter: version 1.2.3
|
||||
* util-linux: version 2.41
|
||||
* virglrenderer: version 1.1.1
|
||||
* virtiofsd: version 1.13.1
|
||||
* which: version 2.23
|
||||
* wireless-regdb: version 2025.02.20
|
||||
* wpa\_supplicant: version 2.11
|
||||
* xauth: version 1.1.4
|
||||
* xf86-input-synaptics: version 1.10.0
|
||||
* xfsprogs: version 6.14.0
|
||||
* xhost: version 1.0.10
|
||||
* xinit: version 1.4.4
|
||||
* xkeyboard-config: version 2.44
|
||||
* xorg-server: version 21.1.16
|
||||
* xterm: version 398
|
||||
* xtrans: version 1.6.0
|
||||
* xz: version 5.8.1
|
||||
* zstd: version 1.5.7
|
||||
|
||||
Patches[](https://docs.unraid.net/unraid-os/release-notes/7.1.0#patches "Direct link to Patches")
|
||||
|
||||
---------------------------------------------------------------------------------------------------
|
||||
|
||||
No patches are currently available for this release.
|
||||
|
||||
* [Upgrading](https://docs.unraid.net/unraid-os/release-notes/7.1.0#upgrading)
|
||||
* [Known issues](https://docs.unraid.net/unraid-os/release-notes/7.1.0#known-issues)
|
||||
|
||||
* [Rolling back](https://docs.unraid.net/unraid-os/release-notes/7.1.0#rolling-back)
|
||||
|
||||
* [Changes vs. 7.0.1](https://docs.unraid.net/unraid-os/release-notes/7.1.0#changes-vs-701)
|
||||
* [Storage](https://docs.unraid.net/unraid-os/release-notes/7.1.0#storage)
|
||||
|
||||
* [Networking](https://docs.unraid.net/unraid-os/release-notes/7.1.0#networking)
|
||||
|
||||
* [VM Manager](https://docs.unraid.net/unraid-os/release-notes/7.1.0#vm-manager)
|
||||
|
||||
* [User VM Templates](https://docs.unraid.net/unraid-os/release-notes/7.1.0#user-vm-templates)
|
||||
|
||||
* [WebGUI](https://docs.unraid.net/unraid-os/release-notes/7.1.0#webgui)
|
||||
|
||||
* [Misc](https://docs.unraid.net/unraid-os/release-notes/7.1.0#misc)
|
||||
* [Other changes](https://docs.unraid.net/unraid-os/release-notes/7.1.0#other-changes)
|
||||
|
||||
* [Linux kernel](https://docs.unraid.net/unraid-os/release-notes/7.1.0#linux-kernel)
|
||||
|
||||
* [Base distro updates](https://docs.unraid.net/unraid-os/release-notes/7.1.0#base-distro-updates)
|
||||
|
||||
* [Patches](https://docs.unraid.net/unraid-os/release-notes/7.1.0#patches)
|
||||
348
docs/research/raw/release-7.2.0.md
Normal file
348
docs/research/raw/release-7.2.0.md
Normal file
@@ -0,0 +1,348 @@
|
||||
[Skip to main content](https://docs.unraid.net/unraid-os/release-notes/7.2.0#__docusaurus_skipToContent_fallback)
|
||||
|
||||
On this page
|
||||
|
||||
The Unraid webGUI is now responsive! The interface automatically adapts to different screen sizes, making it usable on mobile devices, tablets, and desktop monitors alike. The Unraid API is now built in, and the release also brings RAIDZ expansion, Ext2/3/4, NTFS and exFAT support, and the (optional) ability to login to the webGUI via SSO, among other features and bug fixes.
|
||||
|
||||
Note that some plugins may have visual issues in this release; please give plugin authors time to make adjustments. Plugin authors, please see this post describing [how to update your plugins to make them responsive](https://forums.unraid.net/topic/192172-responsive-webgui-plugin-migration-guide/)
|
||||
.
|
||||
|
||||
Upgrading[](https://docs.unraid.net/unraid-os/release-notes/7.2.0#upgrading "Direct link to Upgrading")
|
||||
|
||||
---------------------------------------------------------------------------------------------------------
|
||||
|
||||
For step-by-step instructions, see [Upgrading Unraid](https://docs.unraid.net/unraid-os/system-administration/maintain-and-update/upgrading-unraid/)
|
||||
. Questions about your [license](https://docs.unraid.net/unraid-os/troubleshooting/licensing-faq/#license-types--features)
|
||||
?
|
||||
|
||||
### Known issues[](https://docs.unraid.net/unraid-os/release-notes/7.2.0#known-issues "Direct link to Known issues")
|
||||
|
||||
#### Plugins[](https://docs.unraid.net/unraid-os/release-notes/7.2.0#plugins "Direct link to Plugins")
|
||||
|
||||
The Theme Engine, Dark Theme, Dynamix Date Time, and Flash Remount plugins are incompatible and will be automatically uninstalled, as will outdated versions of Unraid Connect.
|
||||
|
||||
Please upgrade all plugins, particularly Unraid Connect and the Nvidia driver, before updating. Note that some plugins may have visual issues in this release; please give plugin authors time to make adjustments.
|
||||
|
||||
For other known issues, see the [7.1.4 release notes](https://docs.unraid.net/unraid-os/release-notes/7.1.4/#known-issues)
|
||||
.
|
||||
|
||||
### Rolling back[](https://docs.unraid.net/unraid-os/release-notes/7.2.0#rolling-back "Direct link to Rolling back")
|
||||
|
||||
If rolling back earlier than 7.1.4, also see the [7.1.4 release notes](https://docs.unraid.net/unraid-os/release-notes/7.1.4/#rolling-back)
|
||||
.
|
||||
|
||||
Changes vs. [7.1.4](https://docs.unraid.net/unraid-os/release-notes/7.1.4/)
|
||||
[](https://docs.unraid.net/unraid-os/release-notes/7.2.0#changes-vs-714 "Direct link to changes-vs-714")
|
||||
|
||||
--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
|
||||
|
||||
### Storage[](https://docs.unraid.net/unraid-os/release-notes/7.2.0#storage "Direct link to Storage")
|
||||
|
||||
#### ZFS RAIDZ expansion[](https://docs.unraid.net/unraid-os/release-notes/7.2.0#zfs-raidz-expansion "Direct link to ZFS RAIDZ expansion")
|
||||
|
||||
You can now expand your single-vdev RAIDZ1/2/3 pools, one drive at a time. For detailed instructions, see [RAIDZ expansion](https://docs.unraid.net/unraid-os/release-notes/7.2.0/warn/)
|
||||
.
|
||||
|
||||
* With the array running, on **_Main → Pool Devices_**, select the pool name to view the details
|
||||
* In the **Pool Status** area, check for an **Upgrade Pool** button. If one exists, you'll need to click that before continuing. Note that upgrading the pool will limit your ability to downgrade to earlier releases of Unraid (7.1 should be OK, but not 7.0)
|
||||
* Stop the array
|
||||
* On **_Main → Pool Devices_**, add a slot to the pool
|
||||
* Select the appropriate drive (must be at least as large as the smallest drive in the pool)
|
||||
* Start the array
|
||||
|
||||
#### Enhancements[](https://docs.unraid.net/unraid-os/release-notes/7.2.0#enhancements "Direct link to Enhancements")
|
||||
|
||||
* Fix: There will now be an "invalid expansion" warning if the pool needs to be upgraded first
|
||||
* Improvement: Better defaults for ZFS RAIDZ vdevs
|
||||
|
||||
#### Ext2/3/4, NTFS, and exFAT Support[](https://docs.unraid.net/unraid-os/release-notes/7.2.0#ext234-ntfs-and-exfat-support "Direct link to Ext2/3/4, NTFS, and exFAT Support")
|
||||
|
||||
Unraid now supports Ext2/3/4, NTFS, and exFAT drive formats in addition to XFS, BTRFS, and ZFS.
|
||||
|
||||
Use case: say you are a content creator with a box full of hard drives containing all of your historical videos. When first creating an array (or after running **_Tools → New Config_**), add all of your existing data drives (blank, or with data in a supported drive format) to the array. Any parity drives will be overwritten but the data drives will retain their data. You can enjoy parity protection, share them on the network, and take full advantage of everything Unraid has to offer.
|
||||
|
||||
Critical note: you can continue adding filled data drives to the array up until you start the array with a parity drive installed. Once a parity drive has been added, any new data drives will be zeroed out when they are added to the array.
|
||||
|
||||
To clarify, Unraid has always worked this way; what is new is that Unraid now supports additional drive formats.
|
||||
|
||||
Additionally, you can create single drive pools using the new formats as well.
|
||||
|
||||
* Improved the usability of the **File System Type** dropdown as the list of available options is growing
|
||||
|
||||
#### Warn about deprecated file systems[](https://docs.unraid.net/unraid-os/release-notes/7.2.0#warn-about-deprecated-file-systems "Direct link to Warn about deprecated file systems")
|
||||
|
||||
The **_Main_** page will now warn if any array or pool drives are formatted with ReiserFS; these drives need to be migrated to another filesystem ASAP as they will not be usable in a future release of Unraid (likely Unraid 7.3). Similarly, it will warn if there are drives formatted in a deprecated version of XFS; those need to be migrated before 2030. See [Converting to a new file system type](https://docs.unraid.net/unraid-os/using-unraid-to/manage-storage/file-systems/#converting-to-a-new-file-system-type)
|
||||
in the docs for details.
|
||||
|
||||
#### Other storage changes[](https://docs.unraid.net/unraid-os/release-notes/7.2.0#other-storage-changes "Direct link to Other storage changes")
|
||||
|
||||
* Improvement: Two-device ZFS pools are mirrored by default, but you can make them RAIDZ1 if you plan to expand that vdev in the future
|
||||
* Improvement: Add **File system status** to **DeviceInfo** page, showing whether a drive is mounted/unmounted and empty/not empty
|
||||
* Fix: Display issue on Main page when two pools are named similarly
|
||||
* Fix: [glibc bug](https://github.com/openzfs/zfs/issues/17629)
|
||||
which could lead to data loss with ZFS
|
||||
* Fix: BTRFS array disks with multiple filesystem signatures don't mount
|
||||
* Fix: Resolved some issues for parity disks with existing 1MiB aligned partitions
|
||||
* Fix: When stopping array, do not attempt 'umount' on array devices that are not mounted
|
||||
* Improvement: Exclusive shares may be selected for NFS export
|
||||
* Improvement: Disallow shares named `homes`, `global`, and `printers` (these have special meaning in Samba)
|
||||
* Fix: Correct handling of case-insensitive share names
|
||||
* Fix: Shares with invalid characters in names could not be deleted or modified
|
||||
* Fix: Improvements to reading from/writing to SMB Security Settings
|
||||
* Improvement: A top-level `lost+found` directory will not be shared
|
||||
* Fix: In smb.conf, set `smb3 directory leases = no` to avoid issues with the current release of Samba
|
||||
* Fix: Restore comments in default `/etc/modprobe.d/*.conf` files
|
||||
* Fix: Windows fails to create a new folder for a share with primary=ZFS pool and secondary=EXT4 array disk
|
||||
* Fix: New devices added to an existing array with valid parity should be repartitioned
|
||||
* Fix: Do not spin down devices for which SMART self-test is in progress
|
||||
* Fix: New array device not available for shares until the array is restarted
|
||||
* Fix: ZFS allocation profile always shows one vdev only
|
||||
|
||||
### Networking[](https://docs.unraid.net/unraid-os/release-notes/7.2.0#networking "Direct link to Networking")
|
||||
|
||||
#### Other networking changes[](https://docs.unraid.net/unraid-os/release-notes/7.2.0#other-networking-changes "Direct link to Other networking changes")
|
||||
|
||||
* Feature: IPv6 Docker custom networks now support Unique Local Addresses (ULA) in addition to the more standard Global Unicast Addresses (GUA), assuming your router provides both subnets when the Unraid host gets an IPv6 address via DHCP or SLAAC. To use, assign a custom static IP from the appropriate subnet to the container.
|
||||
* Fix: The **_Settings → Network Settings → Interface Rules_** page sometimes showed the wrong network driver (was just a display issue)
|
||||
|
||||
### VM Manager[](https://docs.unraid.net/unraid-os/release-notes/7.2.0#vm-manager "Direct link to VM Manager")
|
||||
|
||||
* Feature: Save PCI hardware data, warn if hardware used by VM changes
|
||||
* Feature: Support virtual sound cards in VMs
|
||||
|
||||
#### Other VM changes[](https://docs.unraid.net/unraid-os/release-notes/7.2.0#other-vm-changes "Direct link to Other VM changes")
|
||||
|
||||
* Improvement: Enhance multi-monitor support, automatically enabling spicevmc when needed
|
||||
* Feature: Upgrade to noVNC v1.6
|
||||
* Removed historical OpenElec and LibreElec VM templates
|
||||
* Fix: VM Console did not work when user shares were disabled
|
||||
* Fix: Don't allow single quotes in Domains storage path
|
||||
* Fix: Change Windows 11 VM defaults
|
||||
* Fix: Unable to view vdisk locations in languages other than English
|
||||
* Fix: No capacity warning when editing a VM to add a 2nd vdisk
|
||||
* Fix: Cdrom Bus: select IDE for i440 and SATA for q35
|
||||
|
||||
### Unraid API[](https://docs.unraid.net/unraid-os/release-notes/7.2.0#unraid-api "Direct link to Unraid API")
|
||||
|
||||
The Unraid API is now built into Unraid! The new Notifications panel is the first major feature to use it, over time the entire webGUI will be updated to use it.
|
||||
|
||||
The Unraid API is fully open source: [https://github.com/unraid/api](https://github.com/unraid/api)
|
||||
. Get started in the [API docs](https://docs.unraid.net/API/)
|
||||
.
|
||||
|
||||
The Unraid Connect plugin adds functionality which communicates with our cloud servers; it remains completely optional.
|
||||
|
||||
#### Other Unraid API changes[](https://docs.unraid.net/unraid-os/release-notes/7.2.0#other-unraid-api-changes "Direct link to Other Unraid API changes")
|
||||
|
||||
* dynamix.unraid.net 4.25.3 - [see changes](https://github.com/unraid/api/releases)
|
||||
|
||||
|
||||
### WebGUI[](https://docs.unraid.net/unraid-os/release-notes/7.2.0#webgui "Direct link to WebGUI")
|
||||
|
||||
#### Responsive CSS[](https://docs.unraid.net/unraid-os/release-notes/7.2.0#responsive-css "Direct link to Responsive CSS")
|
||||
|
||||
The Unraid webGUI is now responsive! Most screens should now work as well on your phone as they do on your desktop monitor.
|
||||
|
||||
#### Login to the webGUI via SSO[](https://docs.unraid.net/unraid-os/release-notes/7.2.0#login-to-the-webgui-via-sso "Direct link to Login to the webGUI via SSO")
|
||||
|
||||
Login to the Unraid webGUI using Single Sign-On (SSO) with your Unraid.net account or any other OIDC-compliant provider. For details on this _optional_ feature, see [OIDC Provider Setup](https://docs.unraid.net/API/oidc-provider-setup/)
|
||||
in the Docs.
|
||||
|
||||
#### Other WebGUI changes[](https://docs.unraid.net/unraid-os/release-notes/7.2.0#other-webgui-changes "Direct link to Other WebGUI changes")
|
||||
|
||||
* Feature: Add new notifications management view, access via the bell in the upper right corner of the webGUI
|
||||
* Feature: Add progress indicator to Docker / Plugin / VM popup window
|
||||
* Feature: Show countdown timer on login page when locked out due to too many incorrect login attempts
|
||||
* Feature: Add _Force Install_ button to bypass version checks when manually installing plugins
|
||||
* Feature: Add **_Tools → Open Terminal_** page; can access it by searching for "terminal". Can optionally remove Terminal button from toolbar via **_Settings → Display Settings → Show Terminal Button in header_**
|
||||
* Feature: **_Users → Root → SSH authorized keys_** now supports more formats (thanks [wandercone](https://github.com/wandercone)
|
||||
)
|
||||
* Feature: Added a welcome screen for new systems, shown after setting the root password
|
||||
* Fix: Re-enable smart test buttons after completion of test
|
||||
* Fix: Prevent webGUI from crashing when dynamix.cfg is corrupt, log any issues
|
||||
* Fix: `blob:` links shouldn't be considered external
|
||||
* Feature: Differentiate between Intel E-Cores and P-Cores on the Dashboard
|
||||
* Feature: Dashboard now gets CPU usage stats from the Unraid API
|
||||
* Fix: Dashboard: More than 1TB of RAM was not reported correctly
|
||||
* Chore: Change charting libraries on the Dashboard
|
||||
* Fix: Prevent Firefox from showing resend/cancel popup when starting array (thanks [dkaser](https://github.com/dkaser)
|
||||
)
|
||||
* Fix: File Manager: stop spinner and show error when it fails (thanks [poroyo](https://github.com/poroyo)
|
||||
)
|
||||
* Feature: Speed up rendering of Plugins and Docker pages
|
||||
* Fix: Prevent issues when clicking an external link from within a changelog
|
||||
* Improvement: Show RAM and network speed in human-readable units
|
||||
* Fix: On _**Settings → Display Settings → Font size**_, remove extreme options that break the webGUI
|
||||
|
||||
Misc[](https://docs.unraid.net/unraid-os/release-notes/7.2.0#misc "Direct link to Misc")
|
||||
|
||||
------------------------------------------------------------------------------------------
|
||||
|
||||
* Feature: Do not execute `go` script when in safe mode, create `/boot/config/go.safemode` script if needed
|
||||
* Improvement: Require authentication on `http://localhost`. This improves security and allows Tailscale Funnel to work with the webGUI. Note that when booting in GUI mode, you will now need to login again to access the webGUI.
|
||||
* Feature: Add favicon and web app manifest support
|
||||
* Feature: License key upgrades are installed automatically, without needing to restart the array
|
||||
* Feature: Thunderbolt devices will be auto-authorized when connected
|
||||
* Feature: Improvements to custom udev rules and scripts, at boot:
|
||||
* `/boot/config/udev/*.rules` are copied to `/etc/udev/rules.d/`
|
||||
* `/boot/config/udev/*.sh` are copied to `/etc/udev/scripts/` where they can be used by your custom udev rules
|
||||
* Fix: Remove support for nonworking ipv6.hash.myunraid.net URLs
|
||||
* Fix: Docker custom network creation failed when IPv6 was enabled
|
||||
* Fix: Resolve issues with high CPU load due to nchan and lsof
|
||||
* Improvement: Removed option to disable live updates on inactive browsers; should no longer be needed
|
||||
* Improvement: Better messaging around mover and "dangling links"
|
||||
* Fix: Prevent errors related to _searchLink_ when installing plugins
|
||||
* Fix: PHP warnings importing WireGuard tunnels
|
||||
* Improvement: _Europe/Kiev_ timezone renamed to _Europe/Kyiv_ to align with the IANA Time Zone Database
|
||||
* Improvement: Enhance Discord notification agent; enable/disable the agent to get the updates (thanks [mgutt](https://github.com/mgutt)
|
||||
)
|
||||
* Fix: Further anonymization of diagnostics.zip
|
||||
* Improvement: Protect WebGUI from fatal PHP errors
|
||||
* Improvement: Adjust logging during plugin installs
|
||||
* Fix: CPU Pinning for Docker containers could crash in certain instances
|
||||
* Fix: Docker NAT failure due to missing br\_netfilter
|
||||
* Fix: Scheduled mover runs not logged
|
||||
|
||||
### Linux kernel[](https://docs.unraid.net/unraid-os/release-notes/7.2.0#linux-kernel "Direct link to Linux kernel")
|
||||
|
||||
* version 6.12.54-Unraid
|
||||
* built-in: CONFIG\_EFIVAR\_FS: EFI Variable filesystem
|
||||
* CONFIG\_INTEL\_RAPL: Intel RAPL support via MSR interface
|
||||
* CONFIG\_NLS\_DEFAULT: change from "iso8859-1" to "utf8"
|
||||
* Added eMMC support:
|
||||
* CONFIG\_MMC: MMC/SD/SDIO card support
|
||||
* CONFIG\_MMC\_BLOCK: MMC block device driver
|
||||
* CONFIG\_MMC\_SDHCI: Secure Digital Host Controller Interface support
|
||||
* CONFIG\_MMC\_SDHCI\_PCI: SDHCI support on PCI bus
|
||||
* CONFIG\_MMC\_SDHCI\_ACPI: SDHCI support for ACPI enumerated SDHCI controllers
|
||||
* CONFIG\_MMC\_SDHCI\_PLTFM: SDHCI platform and OF driver helper
|
||||
|
||||
### Base distro updates[](https://docs.unraid.net/unraid-os/release-notes/7.2.0#base-distro-updates "Direct link to Base distro updates")
|
||||
|
||||
* aaa\_glibc-solibs: version 2.42
|
||||
* adwaita-icon-theme: version 48.1
|
||||
* at-spi2-core: version 2.58.1
|
||||
* bash: version 5.3.003
|
||||
* bind: version 9.20.13
|
||||
* btrfs-progs: version 6.17
|
||||
* ca-certificates: version 20251003
|
||||
* cifs-utils: version 7.4
|
||||
* coreutils: version 9.8
|
||||
* cryptsetup: version 2.8.1
|
||||
* curl: version 8.16.0
|
||||
* e2fsprogs: version 1.47.3
|
||||
* ethtool: version 6.15
|
||||
* exfatprogs: version 1.3.0
|
||||
* fontconfig: version 2.17.1
|
||||
* freetype: version 2.14.0
|
||||
* gdbm: version 1.26
|
||||
* gdk-pixbuf2: version 2.44.3
|
||||
* git: version 2.51.1
|
||||
* glib2: version 2.86.0
|
||||
* glibc: version 2.42 (build 2)
|
||||
* gnutls: version 3.8.10
|
||||
* grub: version 2.12
|
||||
* gtk+3: version 3.24.51
|
||||
* harfbuzz: version 12.1.0
|
||||
* intel-microcode: version 20250812
|
||||
* iproute2: version 6.17.0
|
||||
* inih: version 61
|
||||
* inotify-tools: version 4.25.9.0
|
||||
* iputils: version 20250605
|
||||
* iw: version 6.17
|
||||
* json-glib: version 1.10.8
|
||||
* kbd: version 2.9.0
|
||||
* kernel-firmware: version 20251018\_8b4de42
|
||||
* krb5: version 1.22.1
|
||||
* less: version 685
|
||||
* libXfixes: version 6.0.2
|
||||
* libXpresent: version 1.0.2
|
||||
* libXres: version 1.2.3
|
||||
* libarchive: version 3.8.2
|
||||
* libdrm: version 2.4.127
|
||||
* libedit: version 20251016\_3.1
|
||||
* libevdev: version 1.13.5
|
||||
* libffi: version 3.5.2
|
||||
* libgpg-error: version 1.56
|
||||
* libjpeg-turbo: version 3.1.2
|
||||
* libnftnl: version 1.3.0
|
||||
* libnvme: version 1.15
|
||||
* libpng: version 1.6.50
|
||||
* libssh: version 0.11.3
|
||||
* libtiff: version 4.7.1
|
||||
* libtirpc: version 1.3.7
|
||||
* libunwind: version 1.8.3
|
||||
* liburing: version 2.12
|
||||
* libusb: version 1.0.29
|
||||
* libwebp: version 1.6.0
|
||||
* libvirt: version 11.7.0
|
||||
* libxkbcommon: version 1.11.0
|
||||
* libxml2: version 2.14.6
|
||||
* libzip: version 1.11.4
|
||||
* lsof: version 4.99.5
|
||||
* lvm2: version 2.03.35
|
||||
* mcelog: version 207
|
||||
* mesa: version 25.2.5
|
||||
* nano: version 8.6
|
||||
* ncurses: version 6.5\_20250816
|
||||
* nettle: version 3.10.2
|
||||
* nghttp2: version 1.67.1
|
||||
* nghttp3: version 1.12.0
|
||||
* noto-fonts-ttf: version 2025.10.01
|
||||
* nvme-cli: version 2.15
|
||||
* openssh: version 10.2p1
|
||||
* openssl: version 3.5.4
|
||||
* ovmf: version unraid202502
|
||||
* p11-kit: version 0.25.10
|
||||
* pam: version 1.7.1
|
||||
* pcre2: version 10.46
|
||||
* pango: version 1.56.4
|
||||
* pciutils: version 3.14.0
|
||||
* perl: version 5.42.0
|
||||
* php: version 8.3.26-x86\_64-1\_LT with gettext extension
|
||||
* pixman: version 0.46.4
|
||||
* rclone: version 1.70.1-x86\_64-1\_SBo\_LT.tgz
|
||||
* readline: version 8.3.001
|
||||
* samba: version 4.23.2
|
||||
* shadow: version 4.18.0
|
||||
* smartmontools: version 7.5
|
||||
* spirv-llvm-translator: version 21.1.1
|
||||
* sqlite: version 3.50.4
|
||||
* sudo: version 1.9.17p2
|
||||
* sysstat: version 12.7.8
|
||||
* sysvinit: version 3.15
|
||||
* tdb: version 1.4.14
|
||||
* tevent: version 0.17.1
|
||||
* userspace-rcu: version 0.15.3
|
||||
* util-linux: version 2.41.2
|
||||
* wayland: version 1.24.0
|
||||
* wireguard-tools: version 1.0.20250521
|
||||
* wireless-regdb: version 2025.10.07
|
||||
* xdpyinfo: version 1.4.0
|
||||
* xdriinfo: version 1.0.8
|
||||
* xfsprogs: version 6.16.0
|
||||
* xkeyboard-config: version 2.46
|
||||
* xorg-server: version 21.1.18
|
||||
* xterm: version 402
|
||||
* zfs: version zfs-2.3.4\_6.12.54\_Unraid-x86\_64-2\_LT
|
||||
|
||||
* [Upgrading](https://docs.unraid.net/unraid-os/release-notes/7.2.0#upgrading)
|
||||
* [Known issues](https://docs.unraid.net/unraid-os/release-notes/7.2.0#known-issues)
|
||||
|
||||
* [Rolling back](https://docs.unraid.net/unraid-os/release-notes/7.2.0#rolling-back)
|
||||
|
||||
* [Changes vs. 7.1.4](https://docs.unraid.net/unraid-os/release-notes/7.2.0#changes-vs-714)
|
||||
* [Storage](https://docs.unraid.net/unraid-os/release-notes/7.2.0#storage)
|
||||
|
||||
* [Networking](https://docs.unraid.net/unraid-os/release-notes/7.2.0#networking)
|
||||
|
||||
* [VM Manager](https://docs.unraid.net/unraid-os/release-notes/7.2.0#vm-manager)
|
||||
|
||||
* [Unraid API](https://docs.unraid.net/unraid-os/release-notes/7.2.0#unraid-api)
|
||||
|
||||
* [WebGUI](https://docs.unraid.net/unraid-os/release-notes/7.2.0#webgui)
|
||||
|
||||
* [Misc](https://docs.unraid.net/unraid-os/release-notes/7.2.0#misc)
|
||||
* [Linux kernel](https://docs.unraid.net/unraid-os/release-notes/7.2.0#linux-kernel)
|
||||
|
||||
* [Base distro updates](https://docs.unraid.net/unraid-os/release-notes/7.2.0#base-distro-updates)
|
||||
Reference in New Issue
Block a user