Jump to content


  • Content Count

  • Joined

  • Last visited

Community Reputation

0 Neutral

About joefig44

  • Rank
    Advanced Member


  • Gender

Recent Profile Visitors

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

  1. Nevermind, found it all in Settings on the console. I'm back up and running now! Thanks!
  2. Just so I'm clear on what you mean by "go forward from here...", do you mean I should plug the flash drive into a PC and manipulate the cfg files so all the listed settings match those of the same on the cfg files in that Dec 2 diagnostic you found that I posted? Or do I somehow do it on the unraid console?
  3. Yes, it was Tower on the previous diagnostic. So, what should I do as next steps now? The backup I took was of this flash (post corruption).
  4. tower-diagnostics-20190111-0701.zip Here you go.
  5. So, as mentioned I managed to get it to work but I notice now two key things have changed: 1. The server name: it's no longer called "executioner" - what I named it before, but instead called just Tower 2. It says "Docker Service Failed to Start" Any ideas what I should be doing beyond what you recommended above?
  6. I managed to get the other port to work. Now let's see if it is stable or if it starts exhibiting the same symptoms I had before (which would indicate it's not the network port and may be something else)
  7. Thanks, I'll look into this. Question: so if it is a faulty NIC card, I do have a network mobo port I can plug into. It lights up too when plugged into, but I can't seem to get it to work (but can't tell if it's my main issue or if it is due to something I may need to do in unraid to enable the intregated NIC)?
  8. Brilliant! Done. So, you think that it's more about which port the USB key is plugged into and not what port the network cable is plugged into?
  9. Ok, after a few more reboots, I still get the same errors I posted but now I have flickering lights on the network card AND access to the server. First thing I'm doing is taking a backup of the USB. Here is the diagnostic file diagtower-diagnostics-20190108-1834.zip BTW, I'm running v 6.5.3
  10. I was incorrect in assuming it didn't do anything after the error. After about 30 seconds it goes to a "Tower login:" prompt. I also tried unplugging the network cable from the Atheros network card and plugged it into the network port on the motherboard. While I get flickering lights I still get the same error I quoted above and the same result.
  11. That's it, it stops at that error. Yes, it is an Atheros I guess. Can't find a backup anywhere. Stupidly I may have stored it on the NAS.
  12. I do not. So hooked up a monitor and basically it boots and loads until starts rsyslogd daemon. Then it says this: modprobe: FATAL : Module ATL1E not found modprobe : WARNING: Module ATL1E not found in directory /lib/modules/4.14.4....
  13. No, actually I'm pretty sure it's not fully booting because I can't ping it and I also can't see it in my router's list of devices. Lights on network card light up when booting but then go out
  14. Recently on my Unraid server (v 6.x - unsure and cant' check now) I've been getting intermittent error messages when access user shares that state the folder is no longer available. The first time this happened a few weeks ago I shut down the server and restarted it to find that it would not come back onto the network. After hard rebooting several times and hitting the enter key after one of those once, I got it back up and running. Note that I do not have a monitor setup on the server currently, so don't actually know what is going on in there....that's my next step. Now the same issue started happening again, and I can't seem to get it back up. My next step is to find a monitor somewhere to try and see what is going on, but thought I'd ask here first for any help.
  15. I figured it out - I hadn't mapped anything in Plex by going to the unraid dashboard and clicking Plex and then Edit and mapping the shares. Now I can see them in Plex when I add library.