May 5, 20251 yr 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. Please see the release notes for all the details. 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. Upgrade steps for this release As always, prior to upgrading, create a backup of your USB flash device: "Main/Flash/Flash Device Settings" - click "Flash Backup". Read the release notes. Update all of your plugins. This is critical for the Connect, NVIDIA and Realtek plugins in particular. If the system is currently running 6.12.0 - 6.12.6, we're going to suggest that you stop the array at this point. If it gets stuck on "Retry unmounting shares", open a web terminal and type: umount /var/lib/docker The array should now stop successfully If you have a recent release or Unraid Connect installed Open the dropdown in the top-right of the Unraid webgui and click Check for Update. More details in this blog post If you are on an earlier version Go to Tools -> Update OS and switch to the "Stable" branch if needed. If the update doesn't show, click "Check for Updates" Wait for the update to download and install If you have any plugins that install 3rd party drivers (NVIDIA, Realtek, etc), wait for the notification that the new version of the driver has been downloaded. Reboot 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.
May 5, 20251 yr Author We recommend that everyone running 7.1.0 betas or rcs upgrade to stable. The main difference between -rc.4 and stable is this kernel patch mentioned in the release notes: Apply: [PATCH] Revert "PCI: Avoid reset when disabled via sysfs"
May 5, 20251 yr Upgraded 7.0.1 -> 7.1.0 and I could not boot. I tried all boot options and moving the USB to different ports. I grabbed a different USB flash drive, installed a fresh copy of 7.1.0. Same thing, would not boot. I installed 7.0.1 on that same new USB and it booted just fine. I then followed these instructions to downgrade my main install to 7.0.1 and everything booted up fine. So at least on my hardware, 7.1.0 breaks boot. I can provide diagnostics if requested. Hardware: ASUSTeK COMPUTER INC. ROG STRIX B560-I GAMING WIFI , Version Rev 1.xx American Megatrends Inc., Version 2302 BIOS dated: Wed 13 Nov 2024 12:00 AM 11th Gen Intel® Core™ i5-11500 @ 2.70GHz
May 6, 20251 yr 2 hours ago, veeco said: 7.1.0 breaks boot Do you get to a command prompt or does it hang? If you get a command prompt, can you try again and then from the prompt after logging in with "root", enter in diagnostics The zip file will get saved onto the flash drive (logs folder). Upload that file (ideally in a new topic in General Support)
May 6, 20251 yr 8 minutes ago, Squid said: Do you get to a command prompt or does it hang? It hangs, no command prompt, just this (see image) Edited May 6, 20251 yr by veeco
May 6, 20251 yr Have been running the release candidate builds without problem, but upgrading to the stable of 7.1.0 seems to coincide with a sudden problem with communicating with my UPS via USB upon rebooting following the upgrade. The UPS has otherwise been working fine for a long while prior, and other devices show it just fine. I get a "Lost communication" error in the `UPS Settings` area. Edited May 6, 20251 yr by Hammy Havoc
May 6, 20251 yr Update ran without any problems on the main server with 20 running Docker and 1 VM. The update from rc4 to 7.1.0 also ran smoothly on the backup system. Thank you for your work.
May 6, 20251 yr -updated from 7.0.1 -system booted without any problems (actually faster then last boot) -all services started normal (array, dockercontainers, vm's, nut-server with ups@usb) The only "problem" I do have now is that my vm's do not get a IP in my homenet IP range. (192.168.1.0/24) It looks like virbr0 changed route to a different subnet. (192.168.122.0/24) How can this be changed (tried to delete route and make a new one, but this does not work) or what I am doing wrong? ----- silly... had to change network-module of the VM from virbr0 to eth0. Somehow this got changed with update. So everything is working fine. Edited May 6, 20251 yr by NoRaid99
May 6, 20251 yr Smooth upgrade. Is it possible to have some more theme settings soon? 😎 Would be super cool to have some of the Jquery effects be usable in the webGUI such as top menu grows / fades as one hovers over the menu & ONLY the current active & or hover is bright orange rest are a faded colour. Re-order icons & have them more interactive (CSS) Font choices / sizes (google fonts etc) Appreciate this a bit beyond scope but can't do any of it in current CSS only themes. Would easily add $$$ to experience. Happy to help contribute ideas / code. For example would be nice to have these notification buttons be the same size & style as rest of webGUI (see left of screen). So they should ONLY turn solid orrange on hover. Also noticed the settings for [summary] / [detailed] doesn't seem to make a difference? Colour of search bar results (new search bar is ace!!!) black / grey etc Maybe the entire menu heading & tabs should be centred? The main page content below menu seems to now be centred? Or let user choose: Left / right / centre / justified etc Edited May 6, 20251 yr by dopeytree
May 6, 20251 yr I'm stuck at the "Performing Actions" screen. I guess I'll have to try a manual upgrade.
May 6, 20251 yr Updated my main and test servers to 7.1.0 without any issues, everything works perfectly. 👌
May 6, 20251 yr 4 hours ago, NoRaid99 said: -updated from 7.0.1 -system booted without any problems (actually faster then last boot) -all services started normal (array, dockercontainers, vm's, nut-server with ups@usb) The only "problem" I do have now is that my vm's do not get a IP in my homenet IP range. (192.168.1.0/24) It looks like virbr0 changed route to a different subnet. (192.168.122.0/24) How can this be changed (tried to delete route and make a new one, but this does not work) or what I am doing wrong? ----- silly... had to change network-module of the VM from virbr0 to eth0. Somehow this got changed with update. So everything is working fine. That is not a routing issue, you IP is from a NAT, so the bridge is not working as it should. Try deleting the bridge and creating it again.
May 6, 20251 yr Upgraded my main "media" Server plus two additional unRAID Servers from 7.0.1 to 7.1.0 - no issues encountered up to now. 👍
May 6, 20251 yr upgraded 7.01 --> 7.1 no problem - like the responsive GUI, as I often use laptop for admin tasks... 👍
May 6, 20251 yr just upgraded: 7.0.1 -> 7.1.0. no problems here! thanks for your work! 🙂 Edited May 6, 20251 yr by bohN
May 6, 20251 yr Author Love these "upgraded with no issues" comments Just a quick reminder that 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.
May 7, 20251 yr Upgrade worked fine for me, as well. However, I seem to have lost the ability to transcode video using my AMD Ryzen 7 5700G APU within docker containers (Jellyfin). Downgrading to 7.0.1 makes things work again. Tried upgrading to 7.1, broken again. I'll have to check why that is later.
May 7, 20251 yr Upgraded from 7.0.1 to 7.1.0 on 2 machines: 1st machine (T02) was fine, 2nd machine (T04) was fine except for the Windows 10 VM with 2 virtual disks on 2 different drives disappeared. Downgraded to 7.0.1 and it did not fix the issue. Upgraded again to 7.1.0 and the VM did not return. Under Settings > Backup/Restore Appdata > Backup VM meta is set to yes, and Settings > VM Manager > Enable VMs is set to Yes. Some posts state the XML is within /mnt/user/system/libvirt/libvirt.img which i do have a backup of before the upgrade. Is there another location where the XML file can be found? UPDATE: 2 of my non-parity drives are now reporting as "Unmountable: wrong or no file system" on T04, yet there are no errors and the array is mounted. I am attempting to put the array in Maintenance mode and run a filesystem check. UPDATE 2: While waiting for the filesystem check to run i found the VM XML in my backup CommunityApplicationsAppdataBackup > DATE_OF_BACKUP > vm_meta.tgz > vm_meta.tar > etc> libvirt > qemu. UPDATE 3: Clicking on the disk and pressing the Check Filesystem Status button on T04 was unsuccessful after running for more than 11 hours. Both HDDs are reporting the same message over and over: Phase 1 - find and verify superblock... bad primary superblock - bad magic number !!! attempting to find secondary superblock unable to verify superblock, continuing... I also attempted fixing the filesystem with Disks (gnome-disks) on Ubuntu and it failed right away with the final message "Corrupt index block signature", "Failed to open $Secure: No such file or directory" and "Remount failed: No such file or directory". I ended up reformatting the drives in unRaid. Restoring the VM went a lot smoother: Virtual Machines > Add VM > create a generic VM but do not start it > enable form view > paste in XML and start it. A report was submitted for this under Stable Releases. T04-diagnostics-20250513-1540.zip T02-diagnostics-20250512_1030.zip Edited May 13, 20251 yr by chris1259
May 7, 20251 yr absolutely lovely, no issues on my good ol server! also i love the added wifi support, but i cant find a way to make wifi as active-backup. will that work in the future? also the gui now is super fast! thank you very much for this update you great people!
May 7, 20251 yr oh and just a quickie, my preclear progress button in the lower right corner have been gone for a while is this removed?
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.