ljm42
Administrators
-
Joined
-
Last visited
Everything posted by ljm42
-
Are you changing SSL settings? The only cause I know of for what you are describing happens when you disable SSL, it can confuse your browser. To help prevent confusion, the webgui shows this message: If you are sure that is not the cause, go to Settings > Syslog Server and temporarily enable "Mirror syslog to flash". The next time it happens: 1) clear your browser's cache to see if that helps 2) if not, reboot the server and upload your diagnostics (from Tools -> Diagnostics) here Note: once you past this issue be sure to disable "Mirror syslog to flash" as it adds wear and tear to the flash drive
-
Think of Unraid as an appliance, not a general purpose operating system. If you need a place to perform "daily business" the recommendation would be to run a different OS in a VM.
-
Manual upgrade instructions are in the docs: https://docs.unraid.net/unraid-os/manual/upgrade-instructions/#manual-upgrade-or-downgrade It sounds like you might have skipped this step: Move (not copy) bz* and changes.txt from the root of the flash drive to the "previous" directory, overwriting files as needed If so, when you replaced the files in the root of the flash you overwrote the running OS. There is no graceful recovery for this. Your best bet would be to turn the system off, put the flash drive in a different computer, and follow those manual instructions from the top
-
Unraid 6.12.8 does not have proper support for Lifetime keys. Please upgrade to Unraid 6.12.10
-
Yes, this release is intended to resolve the issue with your drive controller: https://forums.unraid.net/topic/160471-unraid-os-version-61210-available/
-
Yes the update process isn't really setup for people to run in "pending restart" mode for an extended period. TBH this could confuse plugins and other things that aren't prepared for this as well, I would not recommend updating the OS until you are ready to restart. 6.12.9 does have an issue with certain Asmedia controllers, if you are at all concerned about that you can go to Settings -> Disk Settings and disable array autostart. Then when it boots into 6.12.9 there will be no problems and you can just run the update to 6.12.10 and reboot into that.
-
Glad to hear it! Kudos to @Kilrah
-
This is suspect. Try manually stopping the container (reload the page and be sure it is really stopped) before doing the update and see if it makes a difference. Otherwise, I agree with the suggestion to recreate the docker image
-
Unraid 6.12.10 is now available:
-
This release reverts to an earlier version of the Linux kernel to resolve two issues being reported in 6.12.9. It also includes a 'curl' security update and corner case bug fix. All users are encouraged to read the release notes and upgrade. 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". 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 Unraid 6.12.8 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 thread 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. Be sure to include your diagnostics.zip.
-
This release reverts to an earlier version of the Linux kernel to resolve two issues being reported in 6.12.9. It also includes a 'curl' security update and corner case bug fix. We'd appreciate your feedback before releasing it as 6.12.10 This thread 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. 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". 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, then press More options and switch to the Next branch. You may be prompted to sign in to access the Next branch. Select the appropriate version and choose "View changelog to Start Update". More details in this blog post If you are on an earlier version: Go to Tools -> Update OS and switch to the "Next" branch. 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 thread 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. Be sure to include your diagnostics.zip. Upgrade notes This release reverts to an earlier version of the Linux kernel to resolve two issues being reported in 6.12.9. It also includes a 'curl' security update and corner case bug fix. Known issues Out of date plugins Out of date plugins can cause problems, we recommend they be kept current. Call traces and crashes related to macvlan If you are getting call traces related to macvlan (or any unexplained crashes, really), as a first step we recommend navigating to Settings > Docker, switching to advanced view, and changing the Docker custom network type from macvlan to ipvlan. This is the default configuration that Unraid has shipped with since version 6.11.5 and should work for most systems. Note that some users have reported issues with port forwarding from certain routers (Fritzbox) and reduced functionality with advanced network management tools (Ubiquity) when in ipvlan mode. If this affects you, see the alternate solution available since Unraid 6.12.4. Network problems due to jumbo frames If you are having network issues of any kind, confirm that you have not enabled jumbo frames. Navigate to Settings > Network Settings > eth0 and confirm the Desired MTU is 1500. For more information see the Fix Common Problems warning for jumbo frames. Problems due to Realtek network cards Upgraded kernel fixes the deadlock issue with jumbo frames and the in-tree Realtek 8125 driver. However, we still recommend following the advice above regarding jumbo frames. If you continue to have network stability issues and Tools > System Devices shows that you have a Realtek ethernet controller, grab the part number shown and search Community Apps to see if there is a Realtek vendor-supplied driver plugin for that device. For more information, see the support page for Realtek driver plugins. Other issues? We highly recommend installing the Fix Common Problems plugin as it will warn you of common configuration problems. If you are having other crashes or stability issues, navigate to Settings > Syslog Server and enable Mirror syslog to flash. This will cause additional wear and tear on you USB flash boot device but is useful in the short term for gathering logs after a crash. After the next reboot, navigate to Tools > Diagnostics and download your anonymized diagnostics (as of 6.12.5, diagnostics automatically include logs that were mirrored to the flash drive). Finally, start a new topic and provide all the details of the issue. Once the issue is resolved, be sure to disable Mirror syslog to flash. Rolling back Be aware that rolling back to an earlier release will make your system vulnerable to the Docker security issues and potential data loss scenario mentioned in Upgrade notes. If rolling back earlier than 6.12.9, also see the 6.12.9 release notes. Changes vs. 6.12.9 Bug fixes and improvements Resolve issues mounting remote SMB shares via the Unassigned Devices plugin. Resolve issues with certain Asmedia controllers not seeing all the attached devices. nfs: (revert) NFSv4 mounts by default zfs: Detect if insufficient pools slots are defined for an imported pool with a missing device. Fix translations issue with SystemDrivers Base Distro curl: version: 8.7.1 (CVE-2024-2466 CVE-2024-2398 CVE-2024-2379 CVE-2024-2004) Linux kernel version 6.1.79 This thread 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. Be sure to include your diagnostics.zip.
-
The 6.12 branch of the Unraid webgui repo is here if you would like to submit a PR: https://github.com/unraid/webgui/tree/6.12 The exact file is: https://github.com/unraid/webgui/blob/6.12/emhttp/plugins/dynamix/scripts/monitor Nice troubleshooting. This is not my area of expertise, but your research helps a lot. Do you think this: grep -c 'missing' should be changed to: grep -c 'ERROR' Or should it check for both? grep -Ec 'missing|ERROR' Would you mind testing locally by adding '- x' near the end of line 196: exec("$notify -l '/Main' -e ".escapeshellarg("Unraid $text message")." -s ".escapeshellarg("Warning [$server] - Cache pool BTRFS missing device(s)")." -d ".escapeshellarg("$info")." -i \"warning\" -x 2>/dev/null"); That will give you one notification for this subject per reboot (or until you go to Tools -> Archived Notifications and delete the notification)
-
This thread 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. Be sure to include your diagnostics.zip.
-
Thanks, we're looking into it
-
Thanks for linking to this, it is being looked in to
-
Hmm if you are hoping someone will look into this, we need diagnostics from 6.12.9 after the issue occurs. Preferably in a new thread in general support
-
Interesting. Glad it is working again
-
The Unraid Array is best when you need flexibility, i.e. the ability to mix and match drive sizes, easily add drives to expand the array, and the ability to spin down individual drives when they aren't in use. The array does not currently support trim, so it is best with spinning hard drives. A ZFS pool is best when you care about speed more than flexibility. Also if you are using SSD/NVMe drives. Make sure the appdata share is set to use the Cache pool, you want Docker data being stored on SSD/NVME drives rather than spinning disks. In terms of writing to cache first and having mover transfer that to the array during the night, currently that functionality works with the array only and not other pools. Because a ZFS pool is already optimized for speed, this functionality is typically not as important for pools as it is for the array.
-
Would you please upload your diagnostics.zip file (from Tools -> Diagnostics)
-
This thread 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. Be sure to include your diagnostics.zip.
-
Please let us know! If the problem persists... the only discussions I can find about this issue are buried in a release thread, it would be super helpful to have a separate forum topic that summarizes what we know about it. It is very difficult to follow long running conversations across release threads.
-
It is coming : ) But not in the 6.12 series, we aren't going to make a major kernel jump in a patch release. ZFS now supports the 6.7 kernel, I would expect the 6.13 series to be based on that.
-
hi @Atilla0406 I went ahead and moved your conversation to a new thread. There were no driver changes between 6.12.8 and 6.12.9, it is very difficult to think of a cause for the issue you saw. Would you please upload diagnostics from 6.12.8? It will contain logs from the previous boot that may have clues.
-
No. It is difficult to speculate without any details, we don't even know what version you are coming from : ) When you are ready to try again please grab diagnostics and start a new thread.
-
This thread 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. Be sure to include your diagnostics.zip.
