Jump to content

itimpi

Moderators
  • Posts

    20,790
  • Joined

  • Last visited

  • Days Won

    57

Everything posted by itimpi

  1. Do you have notifications enabled to tell you when something like this occurs?
  2. Other than trying the HBA in a different machine in case there is some incompatibility with the motherboard (or at least the PCIe slot used) I cannot think of anything obvious.
  3. You should contact support about this. They were going to offer a 4 device licence but then published the bottom licence was 6 devices so it looks like there is something falling through the cracks on device limit checking.
  4. To clarify it will count if it is plugged in any time the array is started. If it is plugged in when the array is already started then it does not count. You have to decide the trade-off the inconvenience of having to make sure it is not plugged in every time the array is started vs the convenience of not having to worry about this by having a licence that allows for more drives..
  5. We know that Dynamix File Manager is expected to be built-in for the 6.13 release
  6. The Unraid boot drive should be readable on any system as it is formatted in FAT32. If you cannot read it on another system then it has probably failed.
  7. You will definitely need a new .key file. Not sure if it normally comes attached to the receipt email or whether that email includes a link to download it.
  8. Might as well let the check continue. It will only be updating parity to make it conform to the current data disks.
  9. If you have the .key file for the Plus licence in the ‘config’ folder on the flash drive then it should work. If you have it there and it is not working then you will need to contact support and if that is required removing a device could be a stopgap while working out why your plus licence is not working. It might be worth you attaching your system’s diagnostics zip file to your next post in this thread to see if we can spot an issue/
  10. Strange. Have you tried removing the old key?
  11. Have you rebooted since installing the updated key? this is required to make it active.
  12. Have you tried removing the plugin and then reinstalling it? After that log into Connect from each server in turn to get that servers licence registered. If that fails you should then contact support for help. You should also do this if you are missing one of your licence files and cannot get it from connect.
  13. With these types of problems it can be difficult to pin down the culprit. 😖 You might want to consider backing up the cache drive; reformatting it to get a clean file system; and then restoring its contents. You can also get docker containers starting to play up after they have had an upgrade. I mentioned RAM again because it is definitely possible for motherboard components to gradually degrade over time so that a system that has been stable for ages suddenly starts getting unpredictable errors.
  14. Have you checked in Windows Credentials Manager that it has the password stored for your username accessing the Unraid server?
  15. The 'problem' with memtest is that it is only definitive if you get a failure. If you continue to get new failures that look like they could be RAM related it can be worth running with less sticks of RAM to lighten the load on the memory controller.
  16. That is not atypical for a docker container continually crashing and attempting to restart. You should be able to see if this is the case by looking at the uptime of your containers on the Docket tab.
  17. The server rebooting on its own is nearly always hardware related with most likely culprits being cooling (causing thermal shutdown) or power.
  18. It can. Mover will never overwrite an existing file which explains why it will not move. You need to manually decide which copy to keep and delete the other one.
  19. Yes. Note that this means wipe and then rebuild the pool in case this was not clear.
  20. Yes. SMR as parity disks is likely to sometimes lead to significant performance bottlenecks when copy large amounts of data.
  21. You WILL if 6.13.x comes out before your year of updates has expired. Once you get the 6.13.x release you then get the 6.13.y type updates even though you have not taken out another years support. I would expect most users to therefore get the current release plus the next major release without paying extra as long as there is less than a year between the major releases.
  22. You should try to Copy (not move) what you can. Dynamix File Manager can be used for that.
  23. Mover never overwrites existing files. If a file exists in more than one location it is up to you to manually decide which copy to keep and delete the other one. The Dynamix File Manager is probably a good way to do this.
  24. It might make sense if mover did not run if it detected that. However you CAN write to the array with normal file operations while an array operation is in progress - it is just that the two operations interact badly from a performance perspective.
×
×
  • Create New...