ljm42 Posted August 22 Share Posted August 22 This is a quick release that updates the Linux kernel to correct a regression where some HDD devices could not be spun-down. 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 Read the release notes. As always, prior to upgrading, create a backup of your USB flash device: "Main/Flash/Flash Device Settings" - click "Flash Backup". 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. 8 1 Quote Link to comment
xanderman21 Posted August 22 Share Posted August 22 That was fast, all seems to be working great. Thanks for the speedy fix! 1 Quote Link to comment
210 Captain Posted August 22 Share Posted August 22 anything about the fan issue raised? Quote Link to comment
ljm42 Posted August 22 Author Share Posted August 22 52 minutes ago, 210 Captain said: anything about the fan issue raised? I commented over there https://forums.unraid.net/bug-reports/stable-releases/61212-temperature-readings-and-fan-control-broke-r3192/?tab=comments#comment-29721 Quote Link to comment
warpspeed Posted August 23 Share Posted August 23 (edited) In neither the 6.12.12 or 6.12.13 release notes is there any mention (except the start/stop array issue) of the NFS issues that various folks were experiencing in 6.12.11 - not noted as an issue, or a workaround, or whether addressed in the update. If they haven't been addressed, the least I'd have expected is a note that there may be issues with NFS. Though I thought I saw a partial workaround in one of the threads too. I'm referring to these threads: Edited August 23 by warpspeed Quote Link to comment
adammerkley Posted August 23 Share Posted August 23 Upgraded to 6.12.12 last night, never had the spin down issue some reported. Updated to 6.12.13 this evening, no issues. 1 Quote Link to comment
NAS-Man Posted August 23 Share Posted August 23 Upgraded from 6.12.11 -> 6.12.13 no issues. Thank you 1 Quote Link to comment
Gragorg Posted August 23 Share Posted August 23 Spindown Issue fixed thanks for the quick fix. 1 Quote Link to comment
JorgeB Posted August 23 Share Posted August 23 4 hours ago, warpspeed said: I'm referring to these threads: Please retest with 6.12.13 and if you still have the same issue reply to the original bug report. 1 Quote Link to comment
PPH Posted August 23 Share Posted August 23 Successfully upgraded my "virtual" testing unRAID instance from 6.12.12 -> 6.12.13 and my "Media Server" instance from 6.12.11 -> 6.12.13 . Happy to report 'disk spin down' now working on both unRAID Servers. 1 Quote Link to comment
Zonediver Posted August 23 Share Posted August 23 Update from 6.12.11 to 6.12.13 - no issues so far... 1 Quote Link to comment
craigr Posted August 25 Share Posted August 25 (edited) 6.12.11 to 6.12.13 seemingly smoothly. Now going to bed. Edited August 25 by craigr 1 Quote Link to comment
HardwareHarry Posted August 26 Share Posted August 26 Downgraded to 6.12.10 again as the networking seems somehow broken Quote Link to comment
yyu00 Posted August 27 Share Posted August 27 When I updated from version 6.12.11 to version 6.12.13, my graphics driver was lost and any applications based on the graphics card stopped working automatically, such as jellyfin, plex, ollama.The plugin gpu statics also cannot select the GPU.I use a Tesla P4 GPU Quote Link to comment
isvein Posted August 27 Share Posted August 27 Not sure if this has something to do with the docker things, but after this update, things hang way less and the gui is just more responsive. Before, specially docker tab, would hang often and not response. Quote Link to comment
Barry Staes Posted August 27 Share Posted August 27 FYI after update to this .13 my server did not reboot ok. Retry wont help. Details in topic I linked below, since I am not sure if .13 is the actual cause.. Quote Link to comment
dopeytree Posted August 29 Share Posted August 29 (edited) Had a CPU kernel error at 4am ish eventually the machine locked up with all drives spinning so had to do a forced reboot. Anyone had similar on .13 vs .11 ? Unlikely to be memory as did memtest when I built this system a few months ago. Could be anything but have downgraded to be safe. moulin-rouge-syslog-192.168.22.2-20240829-0747.zip Edited August 29 by dopeytree Quote Link to comment
GeorgeJetson20 Posted August 31 Share Posted August 31 I have 3 servers, 2 servers had no issues going from 6.12.11 to 6.12.13 - But the one server had 2 issues that I ran into 1) I have 3 NIC's but only a 2.5 Intel being used, but for some reason after restarting I had to reboot again ( didn't do anything else) then the 2nd time I rebooted, it came up with the correct NIC. 2) Still not sure what the problem is but my Binhex qbittorent VPN seems like it's working correctly but when I add any torrent, (from any Pc's) it does not load. Still investigating what this is but this is the first time I ran into this problem. Quote Link to comment
hundsboog Posted September 10 Share Posted September 10 Same here, network stack is somehow broken, my VMs cant talk to eachother like other users mention it. Downgraded to .11 again. Quote Link to comment
dopeytree Posted September 11 Share Posted September 11 (edited) On 8/29/2024 at 8:50 AM, dopeytree said: Had a CPU kernel error at 4am ish eventually the machine locked up with all drives spinning so had to do a forced reboot. Anyone had similar on .13 vs .11 ? Unlikely to be memory as did memtest when I built this system a few months ago. Could be anything but have downgraded to be safe. moulin-rouge-syslog-192.168.22.2-20240829-0747.zip 955.67 kB · 1 download Rock solid since rolling back to 6.12.11 Edited September 11 by dopeytree Quote Link to comment
warpspeed Posted October 13 Share Posted October 13 Are we going to get a 6.12 bugfix release before 7.x is released. 6.12 bug fixes seem to have gone quiet and many of us are sitting on earlier releases due to bugs. 1 Quote Link to comment
itimpi Posted October 13 Share Posted October 13 @warpspeed The 6.12.13 release has been out for a while now, but since you are posting in its announcement thread I assume you know that. Quote Link to comment
hundsboog Posted October 13 Share Posted October 13 Yes, and like we wrote, its buggy (network stack) Quote Link to comment
ezhik Posted October 14 Share Posted October 14 (edited) The what? This is my firewall/dns/webproxy unraid setup... Rock solid... What hardware are you running it on? Edited October 14 by ezhik Quote Link to comment
hundsboog Posted October 14 Share Posted October 14 If you follow this thread closely, people, me included have severe problems that VMs cannot reach eachother. This problem is not solved yet and if you net many vms, you should not update, Thats all. Quote Link to comment
Recommended Posts
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.