auujay

Members
  • Posts

    8
  • Joined

  • Last visited

Converted

  • Gender
    Male
  • Location
    Cleveland, OH

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

auujay's Achievements

Noob

Noob (1/14)

5

Reputation

  1. I too started getting this. I got a new router a few months ago and never figured out how to setup port forwarding to my UnRaid server so I don't anyone should have access that way. After getting this message I double checked my router I don' t see any DMZ or port forwarding enabled. I would love to hear ideas. Maybe I have a compromised system on my local network that is trying to do this? Basically if I a computer on my local network was hacked, maybe it is trying to log into the unraid box?
  2. I upgraded to 6.5.0 a week or two ago, the upgrade went fine and everything was just as solid as before on 6.3.5. As of last night the machine seemed fine, streaming files like normal. Tonight while watching a movie the server suddenly rebooted. I have never had this problem before, it normally runs for months util I do an intentional shutown/restart. One I realize it rebooted I peeked at the log and saw some concerning error messages. Apr 4 19:51:15 Tower kernel: mce: [Hardware Error]: Machine check events logged Apr 4 19:51:15 Tower kernel: mce: [Hardware Error]: CPU 0: Machine Check: 0 Bank 4: b2000010000b0c0f Apr 4 19:51:15 Tower kernel: mce: [Hardware Error]: TSC 0 Apr 4 19:51:15 Tower kernel: mce: [Hardware Error]: PROCESSOR 2:610f31 TIME 1522885859 SOCKET 0 APIC 0 microcode 6001119 Some internet searching indicates this could be a hardware problem? I tried using mcelog but it seems incompatible with my AMD based system. The Fix Common Problems plugin suggested using EDAC but I am not sure what exactly yo do with it. Should I try running a memory test? Any help determining if this is a real hardware issue to be concerned with or an error that I may have always getting but never noticed is greatly appreciated. tower-diagnostics-20180404-2016.zip
  3. My Win10 laptop started doing this a lot more recently. I am assuming some Windows update has prompted the change. I can resolve it by telling windows to log into the share with username of "\" and leave the password box blank. I hope that works for you.
  4. Thanks, mgworek! That did the trick. I have been super happy with this docker (and Emby), normally the regular updates don't really impact me much but I noticed a few points about library updates changes that I was hoping to see a few weeks ago. The way I forced the update was to "edit" the docker, keep all the settings as is and click "Save". It pulled down the latest and was up and running right away. Now I am running Version 3.0.6200.0 (even newer than when I posted this question the other day). Thanks again everyone!
  5. Not sure if this is the best place to put this, it looks like Emby now has a newer public release 3.0.6070 than what I am running in this docker (mine reports Version 3.0.5972.0). Any chance of getting an update of this docker to the latest public release of Emby? I have been running this container for months now and it rocks! Please keep up the good work. Thanks.
  6. FYI, it looks like a new build of MakeMKV was released.
  7. Big thanks on this one. I got a blu-ray drive added to my unRaid box so I could use this. Works great, exactly as I had hoped.