Please can we sort out colours for Dark Mode in the connect plugin? 😎

Update is working great for me!

OS Version: 7.1.4

M/B: ASUS ROG STRIX Z390-E GAMING

CPU: Intel i9-9900K

MEMORY: 32GB DDR4

Edited August 30, 2025Aug 30 by alpnwht

On 7/10/2025 at 5:05 AM, twiikker said:

Have you made the jump yet?

No....I'm got the itch though! I very apprehensive about my custom docker networks with vLAN's breaking during the upgrade. I do not want to rebuild anything.

On 8/19/2025 at 3:25 AM, twiikker said:

Did the update from 6.12.15 to 7.1.4 without issues so far.

This was my update checklist

- [x] update plugins and dockers

- [x] backup appdata VM USB

- [x] shutdown VMs

- [x] backups to cloud

- [x] stop array

- [x] update OS

- [x] check for plugin update errors if exist

- [x] reboot

- [x] pray

I'm still on the rock solid 6.12.15...is your upgrade to 7.1.4 still stable with now issues?

14 hours ago, gurulee said:

I'm still on the rock solid 6.12.15...is your upgrade to 7.1.4 still stable with now issues?

Havent had issues. vLANs are okey. Dont have any custom docker networks tho other than separated by vLANs.

I am excited to announce I just upgraded (15 min ago) from 6.12.15 to 7.1.4 on my x86 HP Z800 with no known issues as of yet. I had multiple cache pools, custom bri vLAN docker and VM subnets, and Nvidia GPU integrations. It might also be worth noting, I had stopped all my dockers, VM's, and the docker service prior to upgrading.

So 7.1.4 absolutely trashed my server, with it both not respecting the original Tips and Tweeks PBO disable I had on it causing it to run far hotter which required I instead needed to hard disable in the bios (though it still ran 20C hotter on average oddly at 75C versus 55C), but also entirely unable to get through a parity check without crashing 15% in I discovered when I came home to it shutdown and then repeat the instance each time I tried. The first time it even caused a communication error with my parity drive, causing it to record a single CRC error during the crash. Rolled back to the known good 7.0.0 and have since been able to completely rebuild parity with zero issue (ran it as a write correction check to learn more about what happened and logged 5.74 million errors). This ran on 7.1.4, upgraded directly from 7.0.0 for about 20 days, before my monthly parity check brought the full issues to light and brought it down. It even caused issues with my Windows VM (on a bare-metal passed SATA SSD), which was running at the time and kept failing to start after the crash in 7.1.4. After uninstalling the NVidia plug-in completely post rollback and redownloading the driver, plus a few boot attempts and a Windows repair pass it is finally back up on my 7.0.0 rollback, and I am writing this from that OS. Everything is back to normal including the idle temps except my UnRaid Connect is not willing to register (tried a full uninstall and reinstall after it wasn't connecting, and now just won't register).

MOBO - ASUS ROG Crosshair VIII Impact (BIOS 4402)

CPU - AMD 5950X

Power Supply - Corsair SFX 750W w/ Cyberpower 1500VA UPS

GPU - 3080TI Founders

Drives - Rocket 4.0 2TB Cache, EXO 20TB (ST20000NM007D-3DJ103) Parity, EXO 18TB (ST18000NM000J-2TV103) Array, EXO 16TB (ST16000NM001G-2KK103) Array, EXO 16TB (ST16000NM001G-2KK103) Array, IronWolf 16TB (ST16000NE000-2WX103) Array, 850 EVO 1TB SATA Windows Bare-Metal

Sadly, no, I don't have the pre-rollback diagnostics to post. Getting the server back up and working for my business was more important, especially as I was working on a brand new documentary at the time.

Edited September 15, 2025Sep 15 by TheTechnoPilot

This announce post is perfect for quick questions or comments, but if you suspect there will be back and forth for your specific issue, please start a new topic under General Support. Be sure to include your diagnostics.zip.

Hi

Just tried to upgrade from 7.0.0.1.

Now Unraid wont boot from my USB, BIOS says it's not bootable anymore.

For some stupid reason I didnt make a backup before upgrading.

A bit worried to mess thnis even more up.

This shows up on my Win11 PC and if I click on DVD is wants me to format. It's my Unraid USB

2 hours ago, sosdk said:

Now Unraid wont boot from my USB, BIOS says it's not bootable anymore.

Try recreating the flash drive, first backup the current one, then recreate it using 7.1.4 with the USB tool, confirm the flash drive boots with the stock install, and if yes, restore only the /config folder from the backup overwriting any existing files.

If you need further help, please start a new thread in the general support forum this thread is not the right place for support.

I had a problem that with Update from 7.1.2 to 7.1.4 (months after release) broke my kernel. It crashed every time when I checked parity but tries every time after booting, because unraid could not complete the process.

Hardware was not changed since I bought that new hardware.

(Server 1 from my signature)

Suddenly even copying was not possible anymore and creating diagnosis was also impossible. Parity check was calculated to be finished in >400 years.

I tried to set up a new 7.1.2 but the kernel seemed to be crashed. Strangely the kernel was never changed because it is the same on 7.1.2 and 7.1.4.

Nothing was working. Installing 7.2 RC2 fixed everything for me. Because of the lack of creating diagnostics I am not able to provide you with data from that.

I just wanted to write that here. For now I am lucky on 7.2 RC2

Edited October 28, 2025Oct 28 by Marino
Added Server# in Text

47 minutes ago, Marino said:

I had a problem that with Update from 7.1.2 to 7.1.4 (months after release) broke my kernel. It crashed every time when I checked parity but tries every time after booting, because unraid could not complete the process.

7.1.2 and 7.1.4 use the same kernel, so you likely had a different problem. From the description, looks more like a hardware issue, but if you want to troubleshoot more, please create a new thread in the general support forum.

Thanks for reply. No need to dig deeper. On 7.2.0 everything is running perfect now, thanks,