Jump to content

itimpi

Moderators
  • Posts

    20,734
  • Joined

  • Last visited

  • Days Won

    56

Everything posted by itimpi

  1. You say that you issued a format command on disk15 before trying to rebuild it? You would have got a big warning NOT to do this unless you were prepared to lose the disk contents! The format would have created an empty file system on the emulated disk15 and updated parity to reflect this so a rebuild would just end up with an empty disk as all a rebuild does is make a physical disk match the emulated one. Do you still have the original disk15 untouched as if it has not completely failed it could be the best chance of recovering the contents.
  2. Unraid will only try to read the SMART data if thinks the drive is NOT spundown. You probably have something else trying to read or write to the array that is causing the drives to spin up immediately after a spindown.
  3. it looks like those diagnostics are taken shortly after booting. If this is correct, can you post new diagnostics after the speed issue has manifested itself so e can see if anything relevant is being logged?
  4. One disadvantage of using a RAID controller is that it normally means that Unraid cannot monitor a disk's SMART attributes and thus warn you about issues that are reported via SMART.
  5. That almost certainly means the error is from a plugin. You may have to go through a trial-and-error process to identify the culprit.
  6. You can if you want but there is no need to as the plugin still functions as it has on earlier releases. The plugin provides more extensive capabilities than the built-in support but if you do not use any of these extra options then less reason to keep it.
  7. With the File Integrity plugin you want to exclude any folders where the files are being continually updated. Ideally it should be used for files that once written are rarely changed.
  8. It is probably worth mentioning that 4GB is now the minimum recommended RAM for running Unraid without issues. The RAM needed for all functionality to work reliably has been creeping up as more function is added so when loaded into RAM at boot more space is used by the OS.
  9. Have you checked that any vfio bindings are still correct? Either of the OS or the Bios upgrades could lead to them changing IDs
  10. @tTownTom have you checked the permissions at the Linux level on the share and the files in it? There have been a number of reports of permissions being wrong for network access and it only showing up after upgrading. it might be worth posting your system’s diagnostics zip file to your next post in this thread to see if anyone can spot something there.
  11. This suggests a plugin is causing your problem. The key thing that is different in Safe Mode is that no plugins are loaded.
  12. Are you talking about over the network or when checking locally? If over the network then running the New Permissions tool on the share might fix it. If locally then please provide your system's diagnostics so we can look further.
  13. Use the New Config tool and tell it to keep all current assignments. Then change the one for the new disk and start the array to commit the new set of disks. All disks previously used by Unraid and with data already on them are left untouched.
  14. The mover behaviour IS displayed in the GUI alongside that setting. You will see it changing as you change the setting. One of the Unraid releases messed up the display of this additional text pushing it to the right so it was less obvious, but that should now be corrected.
  15. The one that has come up several times is when people deliberately WANT to keep some (but not all) files for a share on a fast SSD. There have been scripts posted to achieve this. what may not be obvious is that the Use Cache setting is specifically about what to do with NEW files. For read purposes existing files can be found on any drive (regardless of user share settings) being managed by Unraid if they have the correct top level folder to make them part of a User Share
  16. There are valid use cases for NOT doing this, and changing current behaviour would break them.
  17. This is expected behaviour! The help built into the GUI describes how the Use Cache settings work and how they affect mover behaviour.
  18. I wonder if perhaps last time you forgot to run without removing the -n option so that the disk got checked but not repaired?
  19. You can also go this way by using the New Config tool to set the drive set you want to keep (although you would then have to rebuild parity to match the new drive set). After doing this you can then mount the old drives in UD to copy the content of the old drives to the array with the new drives in it.
  20. You might want to check what is in the system share on disk5? If it is the docker.img or libvirt.img files then having the docker/VM services enabled will keep the disk spinning.
  21. Perhaps you could explain why you want to do this? That way we can check that what you are trying to do makes sense for the Use Case you are trying to satisfy.
  22. From past experience one thing that can mess with permissions is a plugin that has been built with the wrong permissions on files it installs. When a plugin is installed any permissions in an associated .tgz file that is unpacked can override the standard ones that are set by Unraid. This can apply to any level of the paths to the files contained within the .tgz file.
  23. A User Share is simply an amalgamated view of all the top level folders of that name on all drives. In that sense if you put the drive into any other system it would see these folders and their contents. When you look at a disk at the drive level in Unraid that is the same contents you would see on another system for the same drive.
  24. You can use the Parity Swap procedure that is designed for exactly this Use Case.
  25. You cannot recover data if you have 2 bad disks and only single parity.
×
×
  • Create New...