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
    The 61% relates to the amount of space used in the docker.img file. 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.
  2. itimpi
    I do not think this is true as parity would only be completely valid if Unraid unmounted the array before the sleep which I do not think happens with S3 sleep? I think it is just as if the system crashed while otherwise idle. It is true that any parity corrections are likely to be near the front of the disk so it likely safe to cancel the parity check after it has run for a few minutes but not guaranteed.
  3. itimpi
    It looks as though that is because your 'cache' pool has failed to mount and is not visible to the system at the moment. Not sure how to interpret the error messages in the syslog and thus the best way to proceed. @JorgeB is likely to be the best for having a good suggestion.
  4. itimpi
    Most people leave the global section at 'All' and then control things at the individual share level. This means any new disks are automatically available to user shares and one is less likely to overlook any change required to the global setting.
  5. itimpi
    The syslog in the diagnostics is the RAM version that starts afresh every time the system is booted. You should enable the syslog server (probably with the option to Mirror to Flash set) to get a syslog that survives a reboot so we can see what leads up to a crash. If using the mirror option the syslog file is stored in the 'logs' folder on the flash drive.
  6. itimpi
    Yes - I do this all the time. The Unraid parity operations handle this correctly. You can even do it if you are rebuilding a parity or data drive without it causing problems.
  7. itimpi
    The standard Unraid behaviour is as you describe. If you install the Parity Check Tuning plugin then one of the features it offers is restarting array operations from point previously reached.
  8. itimpi
    It will disable the plugin as you mention. Not sure what will happen if the parity check was not completed before rebooting into Safe mode when you next go into Normal mode - not something I have tested as far as I can remember. No easy way to selectively start plugins while in Safe mode except by re-installing them. Having said that it is probably possible using the command line, but not sure of the details.
  9. itimpi
    The default Unraid behaviour is to restart from the beginning, although if you have the Parity Check Tuning plugin installed it does have an option to support restarting from point previously reached.
  10. itimpi
    I would think the most likely things to cause a reboot would be thermal (e.g. CPU overheating), or PSU issues.
  11. itimpi
    You are likely to get better informed feedback if you attach your system’s diagnostics zip file to your next post in this thread.
  12. itimpi
    The standard recovery methods will not work with 2 drives failed and single parity. It might be possible to force Unraid to tread disk4 as valid and see if it can then successfully emulate disk1. @JorgeB is the expert on this type of recovery so I would suggest waiting for him to chime in.
  13. itimpi
    I notice that you have not set a Minimum Free Space setting on either the cache pool or the appdata share. This will mean you are likely to start getting problems if the 'cache' pool gets anywhere near full. You want the Minimum Free Space to be something like twice the size of the largest file you are likely to write.
  14. itimpi
    What makes you think it is still in the array? Have you found it on a specific array disk? User Shares will show files regardless of whether they are on the array or a pool (cache).
  15. itimpi
    Have you tried running tools->New Permissions on that share? It sounds as if the permissions on the files got messed up when you moved the files!
  16. itimpi
    You need to set one of the last two fields to get anything generated (as mentioned in the syslog server link). The ‘mirror to flash’ is the easiest to set up.
  17. itimpi
    There is this in the online documentation accessible via the Manual link at the bottom of the Unraid GUI.
  18. itimpi
    1. The parity build does not check whether a disk has been precleared so it always does the full size of the parity drive. 2. I would avoid this if possible as removing a drive to shrink the array can be problematic.
  19. itimpi
    While I think of it we normally recommended that scheduled parity checks are set to be non-correcting. The rationale being that if you have a drive playing up you do not want to run a correcting check that might corrupt parity and reduce the chances of a clean data recovery.
  20. itimpi
    You should probably contact support as they are the ones who can sort out Licencing issues.
  21. itimpi
    The Parity Check Tuning plugin would not have initiated the check. The only reason I can think of for it trying to resume is that there was some unexpected state information found in the plugins folder on the flash drive. It might be useful if a listing of the files that are there could be given as that could provide a clue as to what that might be. In addition the contents of any "progress" type files that are there.
  22. itimpi
    If you are writing to a drive in the parity protected array then you will get nowhere near the raw write speed of drives. To understand why read this section of the online documentation.
  23. itimpi
    You need to restart in Normal mode to see if this issue has been fixed.
  24. itimpi
    If you did this and it is a new drive then you should be taken through the licence transfer process as the licence is tied to the drive for which it was initially licenced.
  25. itimpi
    This.
×
×
  • Create New...