Jump to content

itimpi

Moderators
 View Profile  See their activity

  • Posts

    20,789

  • Joined

  • Last visited

  • Days Won

    57

 Content Type 

Everything posted by itimpi

  1. itimpi
    You can either copy them elsewhere during system startup in the 'go' file or using the User Scripts plugin and add execute permission or store them elsewhere in the first place (perhaps something like a folder within the musicbrainz appdata folder?). Note that if running a script via the User Scripts plugin it takes care of this for you.
  2. itimpi
    These can work slightly loose over time (presumably due to vibration) so always worth checking they are still firmly seated. If you have it an electrical cleaning spray on the pins would also not go amiss in case any corrosion is happening.
  3. itimpi
    It is also worth pointing out that both old and new terminology are covered in the User Shares 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. The Unraid OS->Manual section covers most aspects of the current Unraid release.
  4. itimpi
    This is not atypical, and the error messages from Windows can be misleading. You can also use Windows Credentials Manager to examine and/or change any cached credentials.
  5. itimpi
    You want to make sure you get a copy of the 'config' folder off the original drive as that contains all your settings.
  6. itimpi
    It would be possible write a script that checks memory usage using the linux 'free' command and set this to run regularly with the User Scripts plugin. The 'ps' command might also be relevant if you want to monitor particular processes. What you do when you detect a trigger level will be up to the script - although it could either write entries to the syslog, or alternatively raise a notification at the Unraid level.
  7. itimpi
    It is already planned to make the current Unraid array just another pool type (of which you can then have multiples). What the knock on implications around VMs and docker containers will be is not clear but it will presumably be decoupled from starting the main Unraid array (as you may no longer have one).
  8. itimpi
    Parity was valid after running the repair as long as it worked. Using New Config means any data written since the drive went unmountable is now lost.
  9. itimpi
    The settings you have mean it is only listening for other servers. As mentioned in the syslog server link you need to set one of the last two entries to get the server to record its own entries. The mirror to flash option is the easiest to set up, but if you are worried about excessive wear on the flash drive you can put your server's address into the remote server field.
  10. itimpi
    ... also worth checking the power cabling as that can also cause CRC errors.
  11. itimpi
    The parity check checks all of the parity disk as being correct. Since your parity drive is larger than your biggest data drive it is checking that the remaining part of the parity disk is all zeroes.
  12. itimpi
    That was the wrong place to add it! It needs to be added to the end of one of the 'append' lines for the boot option you are using.
  13. itimpi
    That command is wrong as the device name is incorrect and will give the symptoms you describe. Why could you not get it to run from the Gui - that is always the most reliable. You are likely to get better informed feedback if you attach your system’s diagnostics zip file to your next post in this thread.
  14. itimpi
    How did you run that xfs_repair? From the GUI or the command line. If the command line then what was the exact command you used as getting it even slightly wrong can produce the symptoms you describe.
  15. itimpi
    The free-standing RAM tests are nearly always more thorough that ones built into a BIOS. Any RAM faults can cause unpredictable errors.
  16. itimpi
    There should be only 1 key file (presumably the Plus key as the last one that was valid).
  17. itimpi
    What drive did you originally have as disk1? You are likely to get better informed feedback if you attach your system’s diagnostics zip file to your next post in this thread.
  18. itimpi
    Have you put the last key file you had into the ‘config’ folder on the flash drive?
  19. itimpi
    Do you have “turbo Write” mode enabled? If not then I expect the initial burst of speed happens while data is being cached to RAM and then the 30-50 MBps speed that continue is not atypical when writing to a parity protected array. This section of 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 describes what is going on. The Unraid OS->Manual section in particular covers most features of the current Unraid release.
  20. itimpi
    Looked on my test system and that is set to 50MB so that is probably the default as I cannot think why I would have changed it there.
  21. itimpi
    I do not seem to have that setting on my system (running Unraid 6.12.6) so cannot help then.
  22. itimpi
    You should post your system's diagnostics zip file in your next post in this thread to get more informed feedback. It is always a good idea to post this if your question might involve us seeing how you have things set up or to look at recent logs.
  23. itimpi
    I suspect because there is no frequent Use Case and it is very easy to just have 2 differently names shares.
  24. itimpi
    You need to have two different shares if you want them to be treated differently by mover
  25. itimpi
    Have you tried simply deleting the setting - that would probably revert it to default.
×
×
  • Create New...