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
    Most of your non-system shares are set to go straight to the array and not be cached. Nothing wrong wit this, but it does means write speed for new files will be limited by the overhead of updating parity.
  2. itimpi
    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.
  3. itimpi
    That is probably due to this: system shareUseCache="prefer" # Share exists on cache, disk1 Ideally you want all of this share to be on the cache to avoid keeping disk1 and parity spun up.
  4. itimpi
    It could be a counterfeit. If you look at the GUID for the drive it is normally quite obvious if it is not a unique one.
  5. itimpi
    You can expose the flash drive over the network if you want as the 'flash' share by going into its properties and setting the SMB part appropriately. Plugging it into another computer is another easy way.
  6. itimpi
    You might want to play safe and initially start the array without assigning a parity drive. That way you definitely cannot have an accident.
  7. itimpi
    It might be worth installing the DiskSpeed docker to see if the drive in question is performing as expected.
  8. itimpi
    Yes - this is why it survives a crash. It does, however, mean you are doing a lot more writes to the flash so it is probably something you want left running if you are not investigating a problem.
  9. itimpi
    The Manual install method is far more reliable than the USB Creator tool.
  10. itimpi
    What exactly do you mean by this? A disk can be disabled (marked with a red ‘x’) if a write to it fails for some reason. Far more often than not this is not a problem with the disk itself but an external factor such as the cabling or power. the best test of a disks health tends to be the Extended SNART test - of that passes error free the disk is normally OK.
  11. itimpi
    Looks like you have a problem with the following drive as it is showing I/O errors so what is it being used for?: Device Model: ST3000VN007 Serial Number: Z6A0ZCWS
  12. itimpi
    Even those diagnostics do not seem to be while showing the problem as the last line in the syslog is the parity check stating.
  13. itimpi
    We would need diagnostics taken while you are experiencing the problem. The ones posted look like just after a reboot. Guessing, I would think the most likely issues are the SATA and/or power cabling causing tone o more drives to be continually resetting.
  14. itimpi
    Have you ever formatted the drives after a adding them to the Unraid array to create a file system on each drive?
  15. itimpi
    Bear in mind that the value is only checked when a new file is created and does not take into account the size of the file about to be written so you may want a little more headroom. The normal recommendation is twice the size of the largest file you expect to write during day-to-day operation. BTRFS file systems seem a bit fragile when getting close to full.
  16. itimpi
    The file will be in the ‘logs’ folder on the flash drive. You can plug that into your Windows machine to get at it.
  17. itimpi
    This suggests a permissions issue! If you run Tools->New Permissions against the share in question to see if it rectifies the problem? If it does the issue will be getting the files created with the correct permissions in the first place.
  18. itimpi
    According to your screen shot there is still an Extended SMART test running (bottom left image). The FAILED column in the upper image is normally irrelevant unless it say something like "Failing Now"
  19. itimpi
    It is the result of the test in the SMART information for the drive. Does it say something like "Read Failure 90%" indicating it failed at 90% through the test.
  20. itimpi
    Has it failed with an indication there was a read failure? If so you can probably make a warranty claim. note that the SATA overall health assessment takes no account of the effect of running tests. It is based purely on whether any of the attributes have a “failing now” status so is frequently not a useful indication of failure.
  21. itimpi
    If the problem does not appear in Safe Mode this normally means it is being caused by a plugin. No idea which one so it may be a case of trial and error to identify the culprit.
  22. itimpi
    I thought it could use more than 1/2 but may be wrong about that.
  23. itimpi
    I think you need to contact support. Did you get an automated acknowledgement when you tried - if not then the request may not have gotten through (this seems to have been happening quite frequently).
  24. itimpi
    Did you map directly to /tmp or to a folder under /tmp at the Unraid level? Just asking if it was not to a folder under /tmp then the container could have been deleting some of Unraid’s /tmp files that Unraid expects to be there thus causing problems. The other possibility is that more was being put into /tmp than you expected and eventually caused RAM usage issues at the Unraid host level.
  25. itimpi
    You need to set the Minimum Free Space value for the cache pool as mentioned in the online documentation accessible via the ‘Manual’ link at the bottom of the GUI or the DOCS link at the top of each forum page. The free space dropping below this value is what tells Unraid to stop writing to the cache and start writing directly to the array instead.
×
×
  • Create New...