Shifttoo

Members
  • Posts

    9
  • Joined

  • Last visited

Recent Profile Visitors

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

Shifttoo's Achievements

Noob

Noob (1/14)

1

Reputation

  1. @Squid hope were not working you to hard... But I also noted that the CA change log took a bit of a time warp back to 2016
  2. That fixed the issue for both CA and FCP. Thank You @Squid
  3. I'm having the same issue "(Invalid URL / Server error response)" with same problem on the "Fix Common Problems" plugin. I have not tried the URL change suggested by others..
  4. @Hoopster Your EFI folder rename fix did the trick... 😃 6.6.1 is now up a running on my server! Thanks for guiding me to an easy fix!
  5. I'm still new to Unraid, so for what its worth I agree. UEFI is the current hardware firmware interface being utilized by most of the mainstream MB manufactures, and has pretty much replaced BIOS. With Unraid 6.6 being a new release it would make sense to have UEFI be the default.
  6. Thanks all for the responses! @Hoopster My servers MB is new this year, and only has the UEFI type of BIOS. I will try the EFI folder rename fix when I get home from work, and let you know if that works.
  7. I followed the in browser "Update Now" link to upgrade to version 6.6.1 from 6.5.3, and my server never came back up. I run my server headless, so when I went to go check on it I found it was stuck in a restart loop. I moved my server to a location where I could hook a monitor/keyboard to it, and found that every time it reached the automatic start splash screen for Unraid it would show “bzimage…ok”, and then “bzroot…ok” and then it crashes and restarts. When I changed the option to Unraid with GUI mode it will start “bzimage …ok”, and then “bzroot-gui…ok”, and then it starts up and acts as nothing is wrong. If I reboot the server and let go back to an automatic restart it goes back into a restart loop. I reverted my install back to 6.5.3, and my issue goes away. I verified my MB is running the latest available BIOS version. I ran the diagnostics tool under the GUI mode of 6.6.1, so I’m not sure it shows the issue with my server since it seems to work in this mode. ohmetep-diagnostics-20180930-1929.zip