Jump to content

JorgeB

Moderators
  • Posts

    67,112
  • Joined

  • Last visited

  • Days Won

    703

Everything posted by JorgeB

  1. It appears to be raid mode only, IT mode would be best, it might accept LSI IT firmware, it might not, unless you find some info where somebody else did it successfully it would probably be better to get one that is known to work in IT mode, e.g. LSI 9300-8i which uses the same chipset, though a SAS2 model would be cheaper and perform the same unless you plan to use SSDs and/or SAS expanders.
  2. Link isn't working for me.
  3. No, it's an addon ASmedia controller, and it's reported as 10 functional ports in the syslog though there might be less actual ports, recommended controller for Unraid is any LSI with a SAS2008/2308/3008 chipset in IT mode, e.g., 9201-8i, 9211-8i, 9207-8i, 9300-8i, etc and clones, like the Dell H200/H310 and IBM M1015, these latter ones need to be crossflashed.
  4. The 10 port SATA controller you're using is in a really a 2 port controller with 2 SATA port multipliers, those are not recommended at all, both for performance and reliability reasons, and frequent ATA timeouts are one of the known issues.
  5. Split settings override minimum space, either change split level or delete the folder form disk4.
  6. You need to change at least one, I recommend the share setting or you'll have the same problem when a disk fills up, to be larger than any file you intend to transfer to that share.
  7. There is the share's minimum space (default is 0) setting and general cache minimum space setting, as long as the share setting is adequate for that particular share, and it can be very different for other shares, no need to change the cache setting, unless you copy directly to the cache share, but if either threshold is hit it will stop writing to cache (or any other disk used by that share when it's the share setting).
  8. Set that share's minimum free space setting to a value higher than any file you intend to copy there, though for the initial transfer it might be a good idea to skip cache altogether.
  9. Although there are two cache devices assigned only one is currently part of the pool filesystem, stop the array, unassing cache 2 (nvme1n1), start the array, stop the array and re-assign it again, then convert to raid0
  10. There are known issues with the HP240 kernel/driver in v6.7, it affects other (all?) users with that controller.
  11. In the syslog, search for a line similar to this: May 1 08:09:02 Tower7 kernel: mpt2sas_cm0: LSISAS2008: FWVersion(20.00.07.00), ChipRevision(0x03), BiosVersion(07.39.02.00)
  12. Please post the diagnostics after updating.
  13. I was also using btrfs, but I use tunable settings that are considerably higher than defaults, that would explain why I wasn't seeing the problem.
  14. Can't reproduce this on my test server with a 20GB file, can you gives us more detail on the hardware used, mainly board/CPU? Just in case I have something similar where I can try. v6.6.7 root@Test:~# time cat /mnt/disk1/1.mkv > /dev/null real 1m19.655s user 0m0.128s sys 0m22.403s v6.7rc8 root@Test:~# time cat /mnt/disk1/1.mkv > /dev/null real 1m19.453s user 0m0.112s sys 0m24.293s
  15. There are known issues with Ryzen and Linux, most workarounds are discussed here.
  16. That error would suggest there's only one cache device so it can't be converted to raid0, but please post the diagnostics: Tools -> Diagnostics
  17. The syslog ends with Unraid forcing a shutdown since it couldn't unmout the disks, like mentioned that's the reason the for the unclean shutdown
  18. Something is preventing Unraid from unmounting the disks: Apr 30 01:27:07 Unraid-Server emhttpd: shcmd (416): umount /mnt/user Apr 30 01:27:07 Unraid-Server root: umount: /mnt/user: target is busy. Hence the unclean shutdowns.
  19. So you expect the disks to fail after 4 scheduled parity checks?
  20. Regarding the unclean shutdown, there should be diags saved in the flash drive that might show the reason for it.
×
×
  • Create New...