Jump to content

JorgeB

Moderators
  • Posts

    67,504
  • Joined

  • Last visited

  • Days Won

    707

Everything posted by JorgeB

  1. There are various options to create checksums, including corz for Windows, Dynamix File Integrity Plugin, etc, another option is to use btrfs since it automatically creates checksums for all blocks.
  2. User shares are disable, go to Settings -> Global Share Setting as and enable them. As for the disabled disk, it happened before this boot, so nothing in the logs, SMART looks mostly OK, run an extended SMART test and if successful rebuild on top, might be good to replace/swap cables before doing it to rule them out if it happens again to the same disk.
  3. Yep, it's nginx again, but like mentioned I have no idea what causes these, maybe someone else has.
  4. Please post the diagnostics: Tools -> Diagnostics
  5. You should post this in the existing plugin support thread:
  6. Post new diags just to confirm it's the same issue.
  7. Disk1 is failing: 197 Current_Pending_Sector -O---K 100 100 000 - 99 And without parity you can't replace it, best bet is to use ddrescue to clone it then run xfs_repair if still needed.
  8. Please explain in more detail where/when it crashes. You're using a SAS2LP (or similar) controller and those are not recommended for a long time.
  9. Please post the diagnostics: Tools -> Diagnostics
  10. You're absolutely sure no unclean shutdowns? If it wasn't that it's likely some hardware issue, but since second check didn't found any errors no much to go on for now, disks look fine and unlikely to be RAM the way it happened, see if you get more errors on future checks. Unfortunately no way of knowing, you'd need per-existing checksums to be able to check all your data.
  11. Your Asmedia controller has (or is connect to) SATA port multipliers, those are known to cause many troubles, including those ATA errors reference by trurl.
  12. That suggests a network or source problem, without parity you should be able to write to the array faster than that, start by running iperf.
  13. Looks like a flash problem, try running chkdsk or recreating it.
  14. Tem de haver sempre pelo menos um dispositivo de dados no array, mas uma pequena pen drive é suficiente, para não desperdiçar um SSD/porta SATA.
  15. Changed Status to Closed Changed Priority to Other
  16. This isn't a Dynamix plugin, support thread is here.
  17. Please post diagnostics, it's working for me on both servers I have running the beta: Aug 26 06:30:18 Tower7 root: /var/lib/docker: 1.2 GiB (1247686656 bytes) trimmed on /dev/loop2 Aug 26 06:30:18 Tower7 root: /mnt/pcache: 307.6 MiB (322502656 bytes) trimmed on /dev/sdj1 Aug 26 06:30:18 Tower7 root: /mnt/downloads: 201.1 GiB (215877206016 bytes) trimmed on /dev/sdi1 Aug 26 06:30:18 Tower7 root: /mnt/cache: 3.6 GiB (3868098560 bytes) trimmed on /dev/sdb1 Aug 26 05:00:14 Tower1 root: /mnt/cache: 6 GiB (6470180864 bytes) trimmed
  18. Do you mean write to the disk share? If yes that's quite common, see here for a recent example.
  19. Disk is showing some issues on SMART, and it did fail a recent extended test, but since it passed the last one it should be OK for now, you can rebuild on top but any more read errors/failed tests in the near future best to replace it. Since it was disabled Unraid emulates the disk, and any writes to that disk still go there, and will be on the rebuilt disk.
  20. This was the problem, not the docker image, docker image stopped being able to write due to cache being full.
  21. It's nginx spamming the log, and I've seen it before, but no idea what causes it or the solution, does it do the same if you boot in safe mode?
  22. Restarting (unmounting/mounting the filesystem) might free up some space, you still need to make sure cache has enough available space now, or it will happen again.
  23. Yes for some reason pools appear to be more susceptible to bad performance, there's a big thread about it, and a report that it helps.
×
×
  • Create New...