itimpi

Moderators
  • Posts

    19682
  • Joined

  • Last visited

  • Days Won

    54

Everything posted by itimpi

  1. You should provide a copy of your diagnostics so we can get a better idea of what happened. It would also be a good idea to provide a copy of /etc/cron.d/root so we can see how the schedule has been set. BTW: It is normally recommended that scheduled checks are set to be non-correcting.
  2. The only thing you have to do to enable UEFI boot is to remove the trailing ‘~’ character from the EFI folder on the Unraid flash drive. the one thing to note is that if you are passing any hardware through to a VM then the hardware ‘iD’s will have changed on the new hardware and will need adjusting to match the new hardware. You should delete (or rename) the config/vfio.cfg file on the flash drive to stop inadvertently mapping the wrong hardware (and possibly causing issues) on the new system.
  3. Do you have the client on a different sub-net to the Unraid server? If not you are probably encountering routing issues.
  4. Looking at your screenshots you have mapped /transcode to /tmp (which is in RAM rather than /mnt/user/tmp which the guide suggests which is a User share called ‘tmp’ on physical media. If you have sufficient RAM then this might be OK to get best performance, but even then it should be a sub-folder of /tmp (e.g. /tmp/plex) to avoid issues.
  5. Unraid will not do that - you must have configured something to make that happen. The most likely culprit I can think of is the CA Backup/Restore plug-in being incorrectly configured to point to that location for storing backups. the only way I can think of to recover the data will be to restore it from your backups.T
  6. Worth noting that for initial data load it is normally recommended that you do not bother to use a cache drive but go straight to the array.
  7. can’t think of any reason why not as long as that machine has a 64-bit capable processor unless it is not capable of booting off a USB device.
  8. You might find this section of the online documentation that can be accessed via the Manual link at the bottom of the GUI illuminating as to why you will never get anything close to drive speeds when writing to an Unraid parity protected array.
  9. The .key file should still be valid. Make sure it is installed into the ‘config’ folder on the flash drive.
  10. You might try logging in with https://ip-address to see if that works? If so it will narrow down the possibilities of what has been going wrong.
  11. XMP profiles are always overclocks. You may get away with it but they are typically not a good idea when stability is more important than performance.
  12. Very strange then. In both local and remote access you are using a browser. Are you trying to connect via server name or IP address - maybe trying the other might help?
  13. You have to stop the array to change that. I believe that 'prefer' is the default setting even with no cache present. It does no harm to leave it like that so that if you later add a cache the system automatically moves the share to the cache.
  14. Have you tried clearing the cache in the browser?
  15. Either approach will work, but you seem to misunderstand how parity works when adding a new disk? At that point Unraid ‘clears’ the disk (I.e. writes zeroes to every sector) as that leaves parity unaffected and thus the parity drive is not involved at all.
  16. You might want to read this part of the online documentation that describes how User Shares work and how they relate to paths at the linux level. It sounds as if you may have managed to create a folder called ‘user’ on one of your drives which is what FCP is complaining about. This would most likely happen by setting up an incorrect mapping in a docker container.
  17. The Appdata Backup/Restore is about backing up all the variable part of the data for docker containers. The Settings for docker containers are stored on the flash drive and docker containers with their previous settings can be restored using Apps->Previous apps.
  18. when setting up the syslog server what did you put into the "Remote syslog server" field? It needs to be the address of the Unraid server for it to act as both client and server.
  19. The explanation sounds a bit strange you have to add the disk to the array BEFORE formatting it, and your description sounds as if this was not what happened?
  20. It is normal for the speed of a disk to get slower as the drive heads move towards the inner tracks. I believe that the reason is that the tracks are getting shorter and can thus hold less data per revolution of the disk.
  21. That log does not seem to go back far enough to cover you attempting to first add the drive do you have older log files that go back to that point?
  22. That means for some reason the pre-clear signature on the drive was not recognised. the fact it disappeared when you first tried to add it suggests dropped offline, but since it seems you rebooted without first grabbing diagnostics it is too late to see why that happened. It is possible it was at that point the pre-clear signature got destroyed.
  23. Are you actually using Bluetooth on your Unraid system? If not then I believe disabling any Bluetooth drivers is a solution.
  24. According to the diagnostics, both parity drives, the cache drive and disk9 have dropped offline. Do they have anything in common (power, disk controller, etc) that might have affected them all at the same time?