Jump to content

JorgeB

Moderators
  • Posts

    67,556
  • Joined

  • Last visited

  • Days Won

    707

Everything posted by JorgeB

  1. /dev/sdb2 466G 107M 466G 1% /mnt/disks/Backup Something is showing as mounted there, likely a USB disk, if there's not a reboot will clear it.
  2. Do you known what time it crashed? Can't find anything crash related in the log.
  3. You should run a parity check, since there's known bug with the parity swap where sometimes the new parity isn't correctly zeroed
  4. Check the share's minimum space, it also applies to the cache
  5. It also makes looking at the diags much more difficult, remove that and reboot, than post new clean diags showing just the disk errors.
  6. If it's a raid1 pool you can remove one of the devices, then test with the remaining one.
  7. IIRC this is caused by the docker folders plugin.
  8. One more thing, is PCIe ACS override enable? If yes then it could be related, especially if the USB/NVMe controllers were in the same IOMMU group.
  9. Screenshot still looks like a USB/flash drive problem.
  10. By the way you described it it doesn't look like an SMB problem: SMB/LAN problem would usually be evident from the beginning, usually.
  11. Are you using USB 3.0 or 2.0 controller? USB 3.0 is not recommended.
  12. This suggests like mentioned above that it's a device problem.
  13. That's only a read test, and the current problem is with writes. What cache? There was no cache device assigned.
  14. That suggests a device issue, see if you try with a different device, even a regular HDD.
  15. Looks more like a connection problem, swap both cables with another drive and see if the problem follows the drive.
  16. Is it the same transferring to both devices or just the array one?
  17. Did you reboot? Syslog ends here: Dec 8 22:33:20 unRyzend emhttpd: copy: disk2 to disk0 running There's no error but also there's no info it completed.
  18. Diags are after rebooting, by array crash do you mean multiple disk errors? There's a known issue with the Ryzen SATA controller and Linux, it can go wrong especially when there's high I/O, latest Unraid beta helps for some, also look for a BIOS update or disable IOMMU if not needed.
  19. Not many good 4 port options, you can look for a JMB585 based 5 port controller like this one, or an 8 port LSI HBA.
  20. Dec 8 07:04:06 Tower move: move: create_parent: /mnt/disk3/appdata/airsonic error: No space left on device Dec 8 07:04:06 Tower move: move: file /mnt/disk3/appdata/airsonic/thumbs/400/3784cc61d8762b7ad309a0fbc7414a3d.jpeg Dec 8 07:04:06 Tower shfs: cache disk full It's failing to move appdata to cache because cache if full (technically the fs is fully allocated), and since that fails it won't try to move anything else, see here to fix the cache issue.
  21. Yes. You can't install drivers, use one of the recommended controllers and Unraid will have the driver, how many additional ports do you need/want?
  22. df -H -H, --si print sizes in powers of 1000 (e.g., 1.1G)
  23. No, you could start with just the cache pool, or cache plus one array disk and write to that one only for testing. If parity is assigned it will always be involved in any array disk write, but you can use turbo write for better write performance (it won't work if you write to multiple disks simultaneously). I've had arrays with 30 drives without issues.
×
×
  • Create New...