itimpi

Moderators
  • Posts

    19351
  • Joined

  • Last visited

  • Days Won

    53

Everything posted by itimpi

  1. For the time being you need to revert. Any ‘hot fix’ would get a higher patch number (e.g. 6.12.10).
  2. An unexpected reboot is nearly always hardware related. Nothing in the logs that I can see indicating a software reason for the reboot.
  3. I would expect you to now have a lost+found folder on the drive with files/folders with cryptic numeric names. These are ones for which the repair process could not find the directory entry giving the correct name and would need sorting out manually. The Linux ‘file’ command can be useful if doing this by at least telling you the content type of any file.
  4. If the Caddy passes through to Unraid the drive serial number then it will work fine with Unassigned Devices. It is easy using UD to set a script to run when the drive is inserted that could then do the backup.
  5. that is a quirk of the way Unraid UserShares interact with the underlying Linux system and is mentioned in the User Shares part of the online documentation. If you had instead used Dynamix Fiile Manager to do this you would have gotten the expected result as that implements ‘move’ using a copy/delete strategy.
  6. Have you rebooted yet? That should be the first step. I would recommend posting a copy of your diagnostics after doing that to see if we can spot anything.
  7. You must never forward the Unraid GUI directly as you will almost certainly get hacked.. You should only do it either via Unraid Connect or using the built-in WireGuard VPN server.
  8. The report does not look good - I would expect there to be quite a lot that ends up in the lost+found folder with cryptic names. and needs manually sorting out What is the state of your backups? Makes me wonder if parity is good and it might be better to try and get that drive emulated and then repair the emulated drive? Any thoughts @JorgeB
  9. Good chance rebooting will clear that as the location is in RAM, but you should post your diagnostics to let us give more informed feedback. Is you sever exposed to the internet? Unraid is not hardened enough to be directly exposed to the internet.
  10. Do you have notifications enabled to tell you when something like this occurs?
  11. 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.
  12. 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.
  13. 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..
  14. We know that Dynamix File Manager is expected to be built-in for the 6.13 release
  15. 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.
  16. 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.
  17. Might as well let the check continue. It will only be updating parity to make it conform to the current data disks.
  18. 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/
  19. Have you rebooted since installing the updated key? this is required to make it active.
  20. 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.
  21. 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.
  22. Have you checked in Windows Credentials Manager that it has the password stored for your username accessing the Unraid server?
  23. 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.