itimpi

Moderators
  • Posts

    19666
  • Joined

  • Last visited

  • Days Won

    54

Everything posted by itimpi

  1. Handling of drives that unexpectedly go unmountable is covered here in the online documentation accessible via the ‘Manual’ link at the bottom of the GUI or the DOCS link at the top of each forum page.
  2. You can always use the Custom TAB to add anything as long as you have a URL for it. I personally use it to add a DOCS tab there.
  3. For any issue to do with licencing you will need to contact support, we cannot help in the forum. You should get an automated reply when you do to confirm that the issue was raised with them. My suspicion is that the problem is to do with the GUID of the flash drive that you are using (e.g. it may not be unique).
  4. If you read the syslog server link you will see that it specifically mentions putting your Unraid servers address into the remote server field to get it to log to itself.
  5. You can use the New Config tool to reset the array as described here in the online documentation accessible via the ‘Manual’ link at the bottom of the GUI or the DOCS link at the top of each forum page. I recommend that you start by using the options to keep all current assignments to reduce the chance of error and then return to the Main tab to remove the drive before starting the array. Since you have removed a drive parity will need to be built sgain.
  6. @SkinnyV I have never seen any suggestion that AMD is NOT recommended - just that there are a few things you need to take care of when using AMD. I would think a high proportion of Unraid users are using AMD and most of them without issues.
  7. Those setting only set the server up in listening’ mode. You need to set either the “mirror to flash” option or the ‘remote server” field to your servers address to get something logged as mentioned in the syslog server link.
  8. You will need to make use of the New Config tool to reset the array. If you are not absolutely sure of your drive assignments then this might be worth reading.
  9. You might want to check out this section of the the online documentation accessible via the Manual link at the bottom of the Unraid GUI. In addition every forum page has a DOCS link at the top and a Documentation link at the bottom.
  10. This has in the past been nothing like a fixed time. I seem to remember it varying between about 3 months and 12 months. Whether this will become more predictable (and if it does what the intervals are likely to be) I have no idea. Limetech have improved over their initial suggested offering (as you noticed) in that you are still entitled to any patch releases that are produced for your current release even if the support period on your licence has expired.
  11. itimpi

    JBOD

    As long as the JBOD exposes each drive individually to Unraid with their unique serial numbers then you can treat them just like any SATA connected drive and use them for any purpose supported by Unraid. As was said earlier the potential issues would be: Problems if the drives have a tendency to disconnect and then reconnect as a different device ID (as many USB connected drives often do) as Unraid arrays are not hot-plug aware. performance bottlenecks due to putting multiple drives through a single connection to the host.
  12. Probably a silly question, but have you tried rebooting and trying again?
  13. You need to set either the “mirror to flash” option or set the “remote syslog server” to be your Unraid server to get anything recorded as mentioned in the syslog server link. The settings you have just set it up in ‘listen’ mode
  14. The Unraid security model works at the top level of a share - it is not granular enough to apply to sub-folders within it.
  15. I expect that is inherent in the fact that Unraid is based on Linux and the pre-clear stops a system ‘sync’ call from completing.
  16. With those setting you end up with the a syslog fole in the ‘logs’ folder on the flash drive and in the ‘appdata’ share. The file from the ‘logs’ folder is automatically included in any diagnostics.
  17. Those show that server is in ‘listening’ mode. As the syslog server link mentions you need to set the Mirror to Flash option or put your servers address into the Remote Server field to actually get anything written.
  18. You can also do an extended SMART test on the drive to test its health - passing normally means the drive is OK.
  19. In Unraid you can use any case within file/folder names - it is just that under Linux they are case significant so different ones with the same spelling but different case are different files/folders.
  20. Only if you want to lose all previous contents of the drive. You have not mentioned if you tried the procedure for handling unmountable disks and if soi what the results were.
  21. It might be worth posting a screenshot of your syslog server settings so we can check them
  22. This cannot (in the latest releases) be simply done with the server running. Best to do it on another machine.
  23. Have you tried following the procedure documented here in the online documentation accessible via the Manual link at the bottom of the Unraid GUI. In addition every forum page has a DOCS link at the top and a Documentation link at the bottom.
  24. itimpi

    JBOD

    You can try USB and some people seem to use it successfully. However other experience problems and it is difficult to predict which camp any particular user will fall into. If you must use USB then you might be better off running without parity and ensuring that you have a good backup strategy in place to handle any drive failures.
  25. You appear to be using macvlan docker networking? To avoid instability you need to either switch to ipvlan for docker networking, or (if you want to continue using macvlan) disable bridging on the eth0 interface.