2 hours ago, Cout99 said:

Why is this configuration file not created by default in Unraid? There is no reason for the OS to ever be pushed out of RAM.

LT's always been pretty keen about minimizing RAM use, probably a bit too much given current hardware, everything used to be in RAM but /usr and /lib were moved out in 6.12.

 

But there are still people running it on 4-8GB systems where 1GB extra for the OS makes a significant difference... probably difficult to decide which group to favor by default.

Edited January 29, 20251 yr by Kilrah

16 hours ago, Chris Teasdale said:

My upgrade to 7.0 didn't go so well.  Both of my thunderbolt enclosures (OWC Thunderbay 8 and OWC Flex 1U4) failed to show any drives in unRAID 7.0

From the diags, Thunderbolt controllers are bound to vfio-pci:

 

00:0d.2 USB controller [0c03]: Intel Corporation Raptor Lake-P Thunderbolt 4 NHI #0 [8086:a73e]
    DeviceName: Onboard - Other
    Subsystem: Device [2222:1111]
    Kernel driver in use: vfio-pci
    Kernel modules: thunderbolt
00:0d.3 USB controller [0c03]: Intel Corporation Raptor Lake-P Thunderbolt 4 NHI #1 [8086:a76d]
    DeviceName: Onboard - Other
    Subsystem: Device [2222:1111]
    Kernel driver in use: vfio-pci
    Kernel modules: thunderbolt

Maybe the device IDs changed with the new kernel? Please start a new thread in the general support forum and post these again and new ones from 6.12 for comparison.

Upgraded from 6.12.14 to 7.0.0 with no issues.

Hi folks, we are using a new method to distribute bug fixes, with the goal of getting the fixes out to you faster.

 

See the new "Patches" section of the release notes for details:
https://docs.unraid.net/unraid-os/release-notes/7.0.0/#patches

 

 

Update: if you have the Mover Tuning plugin installed, the Unraid Patch plugin will throw an error when patching mover. It is safe to ignore, we're working on a way to improve that experience (see Update 2)

 

Update 2: the latest version of Unraid Patch will detect this situation above and advise you to reboot. Upon rebooting, the patch plugin will patch the files first, before any other plugins are installed. This will avoid conflicts with other plugins.

On 1/12/2025 at 11:18 AM, kaiguy said:

Upgraded to 7.0 stable from 6.12.14 without issue.

 

Most tedious part was reinstalling all the docker containers after switching to overlay2.

 

Might help others--when I deleted the existing docker folder, I didn't realize that would nuke my docker network. After a few reinstalls of containers I noticed they had no network assigned. Once I created the same docker network name, all the containers from that point on were assigned to the correct (previously-assigned) docker network.

 

Really impressed how smooth this went overall! Great job, unraid team!

Why this overlay2?

Upgraded to 7.0 stable from 6.12.14 without issue, everything is xfs.

 

On 1/29/2025 at 6:11 AM, Cout99 said:

I recently upgraded from Unraid 6.12.10 to Unraid 7, and initially, everything seemed to be running smoothly. However, after a few days, I started noticing severe slowdowns, especially in the GUI. Eventually, the system became completely unresponsive, forcing me to perform a hard reboot.
 

Issue:
Upon inspecting the logs, I found multiple warnings such as:

Unraid php-fpm[7718]: [WARNING] [pool www] child 3095784 exited on signal 9 (SIGKILL) after 15.407785 seconds from start

After searching online, many discussions suggested that plugins could be the cause of such issues. I went through a tedious process of uninstalling plugins, rebooting, and testing again, but the issue persisted. Just before I was about to downgrade back to Unraid 6.12.10, I accidentally noticed high transfer rates on my Unraid USB stick.
 

Root Cause & Solution:
I recalled reading the Unraid 7 changelog, which mentioned a known issue: "Excessive flash drive activity slows the system down." The recommended fix was to create a file named fastusr in /boot/config/ and reboot:

touch /boot/config/fastusr

After applying this fix, my system has been running smoothly with no further slowdowns.
 

Final Thoughts:
The issue arises because when too much RAM is used, the OS gets pushed out of memory, causing data to be read and written directly from the flash drive, which significantly slows down the system. My server has 64GB of DDR4 RAM, running around 50 Docker containers and 5 vdi`s. My typical RAM usage is between 80-90%, which likely contributed to the problem.

Why is this configuration file not created by default in Unraid? There is no reason for the OS to ever be pushed out of RAM. Ensuring that the system remains responsive at all times should be a fundamental priority.

 

I was about to upgrade, thank God I read this first lol

I have 64GB of memory and my ZFS cache pool uses the full amount of ram a lot of times (as intended). How was this overlooked? odd

Edited February 4, 20251 yr by Sptz87

1 hour ago, Sptz87 said:

I was about to upgrade, thank God I read this first lol

I have 64GB of memory and my ZFS cache pool uses the full amount of ram a lot of times (as intended). How was this overlooked? odd

6.12 is affected by the same issue, and unlike v7.0, there's no solution, so not sure I follow.

 

 

14 hours ago, JorgeB said:

6.12 is affected by the same issue, and unlike v7.0, there's no solution, so not sure I follow.

 

 

I’ve never experienced this issue hence I thought it was a new one due to the person I quoted experiencing this on 7.

Upgraded from 6.12.14 to 7.0.0 with 1.0 patches without problems.

On 2/4/2025 at 5:25 AM, Sptz87 said:

 

I was about to upgrade, thank God I read this first lol

I have 64GB of memory and my ZFS cache pool uses the full amount of ram a lot of times (as intended). How was this overlooked? odd

I don't have this issue, but I would of absolutely expect the OS to always take priority and stay running in RAM without getting pushed out. Sounds insane to me.

Just upgraded to 7.0.0 and had a couple of hiccups.

During the upgrade it stalled at 'updating 3rd party drivers' which I've seen a few other people had problems with.  I left it for a few hours, no progress so I sighed, took a backup of my flash drive and rebooted and..... it came up fine.  Took a while to boot, but got there.

Now however, whenever I click on 'vms' in the main menu, the interface crashes.  Just straight up stops responding.  I have to restart PHP-fpm to get it going again.

What's the best way to get support for this? 

6 hours ago, deicist said:

Just upgraded to 7.0.0 and had a couple of hiccups.

During the upgrade it stalled at 'updating 3rd party drivers' which I've seen a few other people had problems with.  I left it for a few hours, no progress so I sighed, took a backup of my flash drive and rebooted and..... it came up fine.  Took a while to boot, but got there.

Now however, whenever I click on 'vms' in the main menu, the interface crashes.  Just straight up stops responding.  I have to restart PHP-fpm to get it going again.

What's the best way to get support for this? 

Separate post in general forum. Please post Diags.

This sounds like the CA plugin needs updated first, DNS settings need checked and to confrm some nginx/updates...
*New plugin for v7 Uraid Patches.

 

No apparent problem from 6.12.14 to 6.12.15 then to 7.

 

4-3-2025: VMs are freezing, updating to 701 doesn't help either.

Edited April 3, 20251 yr by TheGleaner

Upgraded from 6.12.15 to 7.0.0 mostly without issues.

 

The upgrade nuked the l2arc devices I manually added to my zfs pools in 6.12, but otherwise the actual data is fine. This is a little sad since I have been warming up the persistent l2arc devices for a long time now and have to start from scratch again.

 

In light of this, anyone that added special vdevs manually may want to be extra cautious with the upgrade to 7.0.0, since this would cause total data loss when the special vdevs are nuked. Pools with special vdevs will just fail to mount, so data loss will not occur. Thanks @JorgeB for the testing.

Edited February 13, 20251 yr by Percutio

10 hours ago, Percutio said:

he upgrade nuked the l2arc devices I manually added to my zfs pools in 6.12

That should never have happened, if the devices were assigned to the pool they should have been imported normally, if they weren't, or were for example using multiple partitions, which is not supported, the pool would not mount, but would not remove the devices, if you still have the diagnostics, please start a new thread in the general support forum and add them there.

On 2/8/2025 at 10:04 PM, bmartino1 said:

Separate post in general forum. Please post Diags.

This sounds like the CA plugin needs updated first, DNS settings need checked and to confrm some nginx/updates...
*New plugin for v7 Uraid Patches.

 

note: I found out about this Patch plugin from the forums, I feel like this should of been natively added to unraid with a toggle which maybe?  Another route to go about it would be to have sent out a notice which shows as a banner about it. Not everyone is watching the forums all the time, and I think that should be the idea going forward.

Hey y'all, I just upgraded to 7.0.0 and a device I was using for my cache drive is no longer showing up as an option. It's a 4x SSD on RAID0 connected via PCIe slot on my server. It was working just fine before the upgrade, and reading this post makes me think there's something I need to do to get it to appear again. The instructions above didn't work unfortunately. Please help if you can, thanks in advance. 

5 minutes ago, Ignatious11 said:

It's a 4x SSD on RAID0 connected via PCIe slot on my server.

Does that mean it's hardware RAID? 

7 hours ago, Ignatious11 said:

Hey y'all, I just upgraded to 7.0.0 and a device I was using for my cache drive is no longer showing up as an option.

Please create a new thread in the general support forum and post the diagnostics.

Hello, 

 

Everything was working fine for many days on version 7,  and now I'm sudenly getting these in the log, curl is failing to check every service, and Parts of the UI is not functioning? 

Feb 21 09:32:13 Tower2 publish: curl to parity failed
Feb 21 09:32:13 Tower2 publish: curl to paritymonitor failed
Feb 21 09:32:14 Tower2 publish: curl to fsState failed
Feb 21 09:32:14 Tower2 publish: curl to mymonitor failed
Feb 21 09:32:14 Tower2 publish: curl to devices failed
Feb 21 09:32:14 Tower2 publish: curl to arraymonitor failed
Feb 21 09:32:14 Tower2 publish: curl to temperature failed
Feb 21 09:32:15 Tower2 publish: curl to devices failed
Feb 21 09:32:15 Tower2 publish: curl to arraymonitor failed
Feb 21 09:32:16 Tower2 publish: curl to devices failed
Feb 21 09:32:16 Tower2 publish: curl to arraymonitor failed
Feb 21 09:32:17 Tower2 publish: curl to parity failed
Feb 21 09:32:17 Tower2 publish: curl to paritymonitor failed
Feb 21 09:32:17 Tower2 publish: curl to fsState failed
Feb 21 09:32:17 Tower2 publish: curl to mymonitor failed
Feb 21 09:32:17 Tower2 publish: curl to devices failed
Feb 21 09:32:17 Tower2 publish: curl to arraymonitor failed
Feb 21 09:32:18 Tower2 publish: curl to devices failed
Feb 21 09:32:18 Tower2 publish: curl to arraymonitor failed
Feb 21 09:32:19 Tower2 publish: curl to temperature failed
Feb 21 09:32:19 Tower2 publish: curl to devices failed
Feb 21 09:32:19 Tower2 publish: curl to arraymonitor failed
Feb 21 09:32:20 Tower2 publish: curl to parity failed
Feb 21 09:32:20 Tower2 publish: curl to paritymonitor failed
Feb 21 09:32:20 Tower2 publish: curl to fsState failed
Feb 21 09:32:20 Tower2 publish: curl to mymonitor failed
Feb 21 09:32:20 Tower2 publish: curl to devices failed
Feb 21 09:32:20 Tower2 publish: curl to arraymonitor failed
Feb 21 09:32:21 Tower2 publish: curl to devices failed
Feb 21 09:32:21 Tower2 publish: curl to arraymonitor failed
Feb 21 09:32:23 Tower2 publish: curl to devices failed
Feb 21 09:32:23 Tower2 publish: curl to arraymonitor failed
Feb 21 09:32:23 Tower2 publish: curl to parity failed
Feb 21 09:32:23 Tower2 publish: curl to paritymonitor failed
Feb 21 09:32:23 Tower2 publish: curl to fsState failed
Feb 21 09:32:23 Tower2 publish: curl to mymonitor failed
Feb 21 09:32:24 Tower2 publish: curl to devices failed
Feb 21 09:32:24 Tower2 publish: curl to arraymonitor failed
Feb 21 09:32:24 Tower2 publish: curl to temperature failed
Feb 21 09:32:25 Tower2 publish: curl to devices failed
Feb 21 09:32:25 Tower2 publish: curl to arraymonitor failed
Feb 21 09:32:26 Tower2 publish: curl to devices failed
Feb 21 09:32:26 Tower2 publish: curl to arraymonitor failed
Feb 21 09:32:26 Tower2 publish: curl to parity failed
Feb 21 09:32:26 Tower2 publish: curl to paritymonitor failed
Feb 21 09:32:26 Tower2 publish: curl to fsState failed
Feb 21 09:32:26 Tower2 publish: curl to mymonitor failed
Feb 21 09:32:27 Tower2 publish: curl to devices failed
Feb 21 09:32:27 Tower2 publish: curl to arraymonitor failed
Feb 21 09:32:28 Tower2 publish: curl to devices failed
Feb 21 09:32:28 Tower2 publish: curl to arraymonitor failed
Feb 21 09:32:29 Tower2 publish: curl to devices failed
Feb 21 09:32:29 Tower2 publish: curl to arraymonitor failed
Feb 21 09:32:29 Tower2 publish: curl to parity failed
Feb 21 09:32:29 Tower2 publish: curl to paritymonitor failed
Feb 21 09:32:29 Tower2 publish: curl to fsState failed
Feb 21 09:32:29 Tower2 publish: curl to mymonitor failed
Feb 21 09:32:29 Tower2 publish: curl to temperature failed
Feb 21 09:32:30 Tower2 publish: curl to devices failed
Feb 21 09:32:30 Tower2 publish: curl to arraymonitor failed
Feb 21 09:32:31 Tower2 publish: curl to devices failed
Feb 21 09:32:31 Tower2 publish: curl to arraymonitor failed

Edited February 21, 20251 yr by dianasta

@dianasta, you should create a new thread in General Support and attach your diagnostics.

4 minutes ago, ChatNoir said:

@dianasta, you should create a new thread in General Support and attach your diagnostics.

Very weird, I just shutdown and start the server and is now fine ! 

On 1/20/2025 at 6:10 PM, aglyons said:

Something that didn't come up a an error is the mover tuning plugin. With that installed the mover wouldn't move any files. 

 

There was an error message (which I can't recall), I did find a post in here somewhere that concluded it was the tuner plugin causing the problem.

 

Once I uninstalled it the mover started working again.

Is this plugin flagged in the upgrade assistant or fix common problems plugin if it's a known issue? 

Massive thanks again for this release.

 

Have just done the first parity check in 6months or so and it's flown by at 109MB/s when before it would usually craw to about 40MB/s as it progressed. Used to take 3x days so in the region of 72hours for 9x disks + 2x parity.