May 11, 20251 yr This is a small but important release, resolving a potential data-loss issue in 7.1.0 and 7.1.1 where the recent "mover empty disk" feature does not handle split levels on shares correctly. 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 11, 20251 yr Confirmed the Issue I posted is now fixed : Upgraded 7.0.1 to 7.1.1 - Mover then reports no space left on device on my media share - New Issue with Manual Split Level Updated the post.
May 11, 20251 yr 5 hours ago, ljm42 said: This is a small but important release, resolving a potential data-loss issue in 7.1.0 and 7.1.2 where ... It should be "... issue in 7.1.0 and 7.1.1 ..." Edited May 11, 20251 yr by bluebean
May 11, 20251 yr 25 minutes ago, bluebean said: It should be "... issue in 7.1.0 and 7.1.1 ..." Thanks, I've corrected that.
May 11, 20251 yr Did the update on my ugreen and no issues so far. System went up without any problems. Thanks for the new release!
May 12, 20251 yr 9 hours ago, IonelChila said: This is all I get, trying to upgrade 2 boxes. Any idea? It looks like you have no working DNS. Edited May 12, 20251 yr by NoRaid99
May 12, 20251 yr 2 hours ago, NoRaid99 said: It looks like you have no working DNS. My DNS if fine. But you may be pointing to something. I need to look at my pi-hole logs and see if the request is getting denied. It worked perfect up to this point when upgrading the UnRaid boxes?
May 12, 20251 yr This is a continuation of my original thread of all issues i have experienced after upgrading to v7.1.0 and v7.1.2. The last stable release for me was v7.0.1, which i have reverted to on one of the 2 servers. The newest issues are as follows: Server T02 (Now running v7.0.1 - was upgraded to both 7.1.0 and v7.1.2) Crashed before reboot after upgrading to v7.1.2 from v7.0.1. Plex docker will no longer accept the extra parameter --runtime=nvidia; nvidia drivers are installed and working. This also affected the GPU Statistics plugin v2025.04.27. The webgui is no longer available within 2 days. Webgui feels slower than normal. SMB no longer works within 2 days. Docker was still working and had network access! No video out when hooked up to a monitor. Momentary press of the power button for a soft shutdown did not work; had to hard reset. NO flash appeared on the webgui. I am preparing a second USB to test with incase this is all related to an aging USB drive. Server T04 (Now running v7.1.2; upgraded from 7.0.1) 2 HDDs again corrupted with the message Unmountable: wrong or no file system (different HDDs each time). Same issue when upgrading to v7.1.0 from v7.0.1. Running Check Filesystem or Disks (gnome-disks) on Ubuntu did not fix the issue. I did not run any other data retrieval software to try to salvage the data as this is a backup server. My first post has the messages displayed when trying these 2 utilities. Random reboot after parity check completed. Webgui feels slower than normal. Webgui can no longer show the disks in the array on the Dashboard or Main tab. Downloading diagnostics data never completes; i let it sit over an hour. None of these issues are present on v7.0.1. At this time i am not asking for assistance and only wanted to share my experience. UPDATE 1: I found another reproducible issue on T04 where after using the Terminal in the upper right hand corner of the webgui and exiting, the webgui no longer shows the drives (no longer visible but array is online) in the array for about 30 mins, then it returns. Clicking refresh does not work. The drives are also no longer visible from Main > Array Devices. This same issue also occurres when trying to move files under Shares > [Pick a share] > move files. The files i was trying to move were 12.2TB in size amounting to just over 10,000 files. I let it sit for over an hour and no files were moved. I have only been able to move small files or small amounts of files with this built in feature in the past. I ended up using the docker Krusader and moved the files in a few seconds since they were all on the same server (T04). While i was updating this post T04 randomly rebooted and i was able to retrieve diagnostics (T04-diagnostics-20250513-1540.zip) this time. When the reboot happened a Windows 10 22H2 VM was running and performing a large file sync with robocopy. This was working fine for several hours before the server rebooted unexpectedly. After the reboot i reverted from v7.1.2 to v7.0.1 and again 2 drives were showing Unmountable: wrong or no file system and had to be reformatted. Downloading diagnostic data is not working on T04 after downgrading to v7.0.1, and the drives in the array are not visable, but the array is online. Diagnostics (T02-diagnostics-20250512_1030.zip) from T02 was collected while it was still running v7.1.2 at some point. A report was submitted for this under Stable Releases. T02-diagnostics-20250512_1030.zip T04-diagnostics-20250513-1540.zip Edited May 13, 20251 yr by chris1259
May 12, 20251 yr In 7.1.1 and 7.1.2, after typing a command in terminal, it finishes then does not return to a new line. Just at the end of the output.
May 12, 20251 yr 20 minutes ago, RowdyBurns said: In 7.1.1 and 7.1.2, after typing a command in terminal, it finishes then does not return to a new line. Just at the end of the output. what command can you give an example? as i run script and tested this and unless the command is still doing stuff it will not show a new line what command are you running?
May 12, 20251 yr 3 hours ago, chris1259 said: This is a continuation of my original thread of all issues i have experienced after upgrading to v7.1.0 and v7.1.2. The last stable release for me was v7.0.1, which i have reverted to on one of the 2 servers. The newest issues are as follows: Server T02 (Now running v7.0.1 - was upgraded to both 7.1.0 and v7.1.2) Crashed before reboot after upgrading to v7.1.2 from v7.0.1. Plex docker will no longer accept the extra parameter --runtime=nvidia; nvidia drivers are installed and working. This also affected the GPU Statistics plugin v2025.04.27. The webgui is no longer available within 2 days. Webgui feels slower than normal. SMB no longer works within 2 days. Docker was still working and had network access! No video out when hooked up to a monitor. Momentary press of the power button for a soft shutdown did not work; had to hard reset. NO flash appeared on the webgui. I am preparing a second USB to test with incase this is all related to an aging USB drive. Server T04 (Now running v7.1.2; upgraded from 7.0.1) 2 HDDs again corrupted with the message Unmountable: wrong or no file system (different HDDs each time). Same issue when upgrading to v7.1.0 from v7.0.1. Running Check Filesystem or Disks (gnome-disks) on Ubuntu did not fix the issue. I did not run any other data retrieval software to try to salvage the data as this is a backup server. My first post has the messages displayed when trying these 2 utilities. Random reboot after parity check completed. Webgui feels slower than normal. Webgui can no longer show the disks in the array on the Dashboard or Main tab. Downloading diagnostics data never completes; i let it sit over an hour. None of these issues are present on v7.0.1. At this time i am not asking for assistance and only wanted to share my experience. for your to2 servcer nvidia is a known issue with older hardware as the nvidia plugin will force update you to latte v570 drivers. and will not show older v550 drivers. as NVIDIA killed support for those driver versions... NVIDIA had some updates when there were kernel change as v7.0,1 is on kernel v6.6 while unraid v7.1 is on kernel version 6.12 also they added novua open source driver that may conflict... Noted in the release and on ich777 nvdia driver page. Kernel shifts to LTS... try ich777 oldest known nvida drive v565 make sure nouveau is blacklisted... as you want to use ich777 driver version... not Linux open-source NVIDIA drivers. for t04 seems like 2 hard disk have failed. More info form transfers of v6 to v7 where a config file was not writing correctly and v7 cares that its written correctly.
May 13, 20251 yr 31 minutes ago, bmartino1 said: for your to2 servcer nvidia is a known issue with older hardware as the nvidia plugin will force update you to latte v570 drivers. and will not show older v550 drivers. as NVIDIA killed support for those driver versions... NVIDIA had some updates when there were kernel change as v7.0,1 is on kernel v6.6 while unraid v7.1 is on kernel version 6.12 also they added novua open source driver that may conflict... Noted in the release and on ich777 nvdia driver page. Kernel shifts to LTS... try ich777 oldest known nvida drive v565 make sure nouveau is blacklisted... as you want to use ich777 driver version... not Linux open-source NVIDIA drivers. for t04 seems like 2 hard disk have failed. More info form transfers of v6 to v7 where a config file was not writing correctly and v7 cares that its written correctly. Thank you for your input on this. For the HDDs on T04, that would mean 4 different HDDs with 1-2 years of usage max all failed. The drives themselves are fine and were only corrupted during the upgrade. I was able to replicate this issue. The the GPU on T02 is a Nvidia EVGA Geforce GTX 960 SuperClocked Gaming with drivers v575.51.02. Next time i attempt to upgrade i will downgrade the drivers. Thanks!
May 13, 20251 yr since you were able to replicate the issue, do you mind filling out a 7.01-7.2 bug report https://forums.unraid.net/bug-reports/stable-releases/ so that we may test, confirm and see where it broke. as there have been issues outside of mover and disk configurations that need redone. you may still be affected via the v7.0.0 disk configuration bug.
May 13, 20251 yr 9 hours ago, chris1259 said: This is a continuation of my original thread of all issues i have experienced after upgrading to v7.1.0 and v7.1.2. The last stable release for me was v7.0.1, which i have reverted to on one of the 2 servers. The newest issues are as follows Please create a dedicated bug report in the bug subforums here since this is the wrong thread to report such issues: https://forums.unraid.net/bug-reports/stable-releases/ Including Diagnostics. 9 hours ago, chris1259 said: Plex docker will no longer accept the extra parameter --runtime=nvidia; nvidia drivers are installed and working. This is probably a 3rd party driver plugin issue and you should report that in the support thread from the plugin including your Diagnostics since I can‘t even see what the syslog or your driver does. Again, this is the wrong thread to report issues because this is the announce post, see the first post: On 5/11/2025 at 7:56 AM, ljm42 said: 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 13, 20251 yr Performed update from 7.0.1 and caught an 'Unknown pci header type '127' for device' error related to a pfsense VM. Specifically pointing at an intel i226v rev4 dual nic (first port). Could not resolve quickly and rolled back to 7.0.1 and it came back up. No interest in troubeshooting this one, more of an fyi.
May 13, 20251 yr 19 hours ago, bmartino1 said: since you were able to replicate the issue, do you mind filling out a 7.01-7.2 bug report https://forums.unraid.net/bug-reports/stable-releases/ so that we may test, confirm and see where it broke. as there have been issues outside of mover and disk configurations that need redone. you may still be affected via the v7.0.0 disk configuration bug. A report was submitted for this under Stable Releases. Edited May 13, 20251 yr by chris1259
May 13, 20251 yr 15 hours ago, ich777 said: Please create a dedicated bug report in the bug subforums here since this is the wrong thread to report such issues: https://forums.unraid.net/bug-reports/stable-releases/ Including Diagnostics. This is probably a 3rd party driver plugin issue and you should report that in the support thread from the plugin including your Diagnostics since I can‘t even see what the syslog or your driver does. Again, this is the wrong thread to report issues because this is the announce post, see the first post: A report was submitted for this under Stable Releases, and my mistake about posting this in the wrong forum. It wasn't my intention to create such a big post. Edited May 13, 20251 yr by chris1259
May 14, 20251 yr Between these 3 release threads, it's really difficult to gauge the stability of this release. I can't tell if these issues are just isolated to individuals with unique hardware configurations or if it's a release I should really hold off on putting into my production servers. I'm wondering if more can be done to ramp up participation in the beta/rc phases. I feel like back in the day there was a lot more effort on the community's part but unsure what can be done to improve that. I personally have 2 servers which originally was 1 prod and 1 dev; but now over time both have evolved into having very important purposes so I can't gamble as much anymore. Perhaps Unraid could develop some free license program just for testing new releases; free to use for the life of that release or something. Edited May 15, 20251 yr by cj0r
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.