ljm42

Administrators
  • Posts

    4342
  • Joined

  • Last visited

  • Days Won

    27

ljm42 last won the day on March 2

ljm42 had the most liked content!

Converted

  • Gender
    Undisclosed
  • Personal Text
    the answer to life, the universe, and everything

Recent Profile Visitors

50342 profile views

ljm42's Achievements

Experienced

Experienced (11/14)

1.2k

Reputation

137

Community Answers

  1. That is probably it. If you are concerned, you could fully delete that container and reboot, see if tunl0@none comes back. I don't see any proof of a hack in the comments in this thread or in the diagnostics. Not saying it is impossible, just saying I don't see anything that would lead me to that conclusion. Although I do see that your previous release was 6.11.5, which is about 1.5 years old, an eternity in Internet security terms. Even so, if the system is not exposed to the Internet the risks are minimal. Unraid is different from most operating systems in that it is loaded fresh into RAM with every reboot. A hacker would need to take special steps for the hack to persist, and those should be visible in diagnostics. So in general once you reboot you are good. Although IF a hack did occur you should take steps to prevent it from happening again, I'd suggest reviewing our Security Best Practices: https://unraid.net/blog/unraid-server-security-best-practices and resetting your root password and user passwords to be safe. (Note that if a Docker container was hacked, that would not be resolved by a reboot. To clean that up you would want to fully delete the affected container.)
  2. Yep that is all good. The diagnostics do show that you have an interface named tunl0@NONE which is currently down. I don't have that on my systems but Google suggests it is related to Docker. Do you have any Docker containers that provide VPN services or otherwise mess with the network?
  3. /tmp/emhttp/smb.service is fine. The user "nobatko" is not included in Unraid by default, I'm guessing that is a user you added? It is not configured like a normal Unraid user in the current release of Unraid, did you follow a guide to do something special with it? Or perhaps an older version of Unraid used this format, not sure. I'd recommend going to Settings -> FTP Server, disabling the service and removing any users listed there. Then go to the users page and delete and recreate the nobatko user. When you are done I would expect the entry to look like this: nobatko:x:1000:100::/:/bin/false
  4. This is included in the standard Unraid distribution and is not an indicator of a hack
  5. Interesting. Glad it is working again
  6. 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.
  7. Would you please upload your diagnostics.zip file (from Tools -> Diagnostics)
  8. 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.
  9. 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.
  10. 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.
  11. 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.
  12. 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.
  13. 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.
  14. It is very difficult to do back and forth support in a release thread, please start a new thread under General Support and provide diagnostics.zip from both versions. Thanks!
  15. This is a bug fix release, resolving a nice collection of problems reported by the community, details below. 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.