Jump to content

itimpi

Moderators
  • Posts

    20,790
  • Joined

  • Last visited

  • Days Won

    57

Everything posted by itimpi

  1. Did you copy across the contents of the 'config' folder from the old flash? That should have gotten the plugins and docker templates back just as they were.
  2. That is more frequent than most people go for. Monthly or even less frequently is far more common.
  3. Yes. As long as they only happen occasionally they will be a non-issue.
  4. From your description it will not have gotten far enough to be able to write a file. It might be worth rewriting all the bz* type files as described here in the online documentation to see if that helps just in case one of those files is failing to be read properly on the problem machine.
  5. You should be able to do this using the Dynamix File Manager. You can also do it from the command line but if you are not familiar with it you could cause further problems.
  6. That is almost certainly a BIOS issue. It might be worth mentioning what motherboards are in use and whether you are trying to boot in UEFI or legacy mode.
  7. Sorry - missed the fact that it was ZFS. Not sure of the steps to handle this on ZFS I am afraid, hopefully someone else can provide some guidance. In the worst case I would expect something like UFS Explorer on Windows would be able to get most/all of the data.
  8. Not being seen at the hardware level. i would careful check cabling to the drive and power. It is not by any chance a ‘shucked’ drive?
  9. Can you read the config folder off the old flash drive?
  10. 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.
  11. 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.
  12. 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).
  13. 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.
  14. 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.
  15. @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.
  16. 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.
  17. 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.
  18. 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.
  19. 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.
  20. 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.
  21. Probably a silly question, but have you tried rebooting and trying again?
  22. 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
  23. The Unraid security model works at the top level of a share - it is not granular enough to apply to sub-folders within it.
  24. 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.
  25. 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.
×
×
  • Create New...