Jump to content

JorgeB

Moderators
 View Profile  See their activity

  • Posts

    67,125

  • Joined

  • Last visited

  • Days Won

    703

 Content Type 

Everything posted by JorgeB

  1. JorgeB

    10Gb NIC

    JorgeB replied to bionicrocky's topic in Hardware

    Mellanox ConnectX-2, it's one of the cheapest out there and works fine with Unraid
  2. JorgeB
    If it's used on an older board that doesn't support UEFI it's not a problem, as it will boot using legacy bios without user intervention. If UEFI is buggy the user will have to choose in the bios to boot legacy, or the other away around if legacy is the problem, but AFAIK there's no way LT can choose which one is the default, that will be whatever option the board defaults to.
  3. JorgeB
    How would you make it default? IMO it should be enable by default, so either method could be used by selecting the correct bios option, or if a board can only use one or the other it will use it without the user having to make any changes.
  4. JorgeB
    This is more a question than a bug report, since v6.6 and during scripted rsync backups, Unraid is on the receiving end, log gets spammed with these warnings: Oct 2 14:46:00 Tower1 sshd[14336]: SSH: Server;Ltype: Version;Remote: 192.168.1.27-42621;Protocol: 2.0;Client: OpenSSH_7.5 FreeBSD-20170903 Oct 2 14:46:00 Tower1 sshd[14336]: SSH: Server;Ltype: Kex;Remote: 192.168.1.27-42621;Enc: [email protected];MAC: <implicit>;Comp: none [preauth] Oct 2 14:46:00 Tower1 sshd[14336]: SSH: Server;Ltype: Authname;Remote: 192.168.1.27-42621;Name: root [preauth] Oct 2 14:46:00 Tower1 sshd[14336]: Accepted none for root from 192.168.1.27 port 42621 ssh2 Oct 2 14:46:17 Tower1 sshd[14336]: SSH: Server;Ltype: Kex;Remote: 192.168.1.27-42621;Enc: [email protected];MAC: <implicit>;Comp: none Oct 2 14:46:27 Tower1 sshd[14336]: SSH: Server;Ltype: Kex;Remote: 192.168.1.27-42621;Enc: [email protected];MAC: <implicit>;Comp: none Oct 2 14:46:41 Tower1 sshd[14336]: SSH: Server;Ltype: Kex;Remote: 192.168.1.27-42621;Enc: [email protected];MAC: <implicit>;Comp: none Oct 2 14:46:53 Tower1 sshd[14336]: SSH: Server;Ltype: Kex;Remote: 192.168.1.27-42621;Enc: [email protected];MAC: <implicit>;Comp: none Oct 2 14:47:06 Tower1 sshd[14336]: SSH: Server;Ltype: Kex;Remote: 192.168.1.27-42621;Enc: [email protected];MAC: <implicit>;Comp: none Oct 2 14:47:15 Tower1 sshd[14336]: SSH: Server;Ltype: Kex;Remote: 192.168.1.27-42621;Enc: [email protected];MAC: <implicit>;Comp: none Oct 2 14:47:26 Tower1 sshd[14336]: SSH: Server;Ltype: Kex;Remote: 192.168.1.27-42621;Enc: [email protected];MAC: <implicit>;Comp: none Oct 2 14:47:39 Tower1 sshd[14336]: SSH: Server;Ltype: Kex;Remote: 192.168.1.27-42621;Enc: [email protected];MAC: <implicit>;Comp: none Oct 2 14:47:52 Tower1 sshd[14336]: SSH: Server;Ltype: Kex;Remote: 192.168.1.27-42621;Enc: [email protected];MAC: <implicit>;Comp: none Oct 2 14:48:06 Tower1 sshd[14336]: Received disconnect from 192.168.1.27 port 42621:11: disconnected by user Oct 2 14:48:06 Tower1 sshd[14336]: Disconnected from user root 192.168.1.27 port 42621 Earlier releases would just log: Oct 2 14:46:00 Tower1 sshd[14336]: Accepted none for root from 192.168.1.27 port 42621 ssh2 Oct 2 14:48:06 Tower1 sshd[14336]: Received disconnect from 192.168.1.27 port 42621:11: disconnected by user Oct 2 14:48:06 Tower1 sshd[14336]: Disconnected from user root 192.168.1.27 port 42621 Except for the log spam, it doesn't appear to cause any issues, but my question is was the SSH log level changed? tower1-diagnostics-20181002-1553.zip
  5. JorgeB
    No, that's not possible, array/rebuild start isn't dependent of formatting.
  6. JorgeB
    You need to check that share's split level, it takes precedence over allocation method.
  7. JorgeB
    Yes, it's a standard dual ranked (2Rx8) ECC dimm.
  8. JorgeB
    My bad, I copy pasted GA-AX370-GAMING, omitted the 5, so it took me to a different model, in that case the GA-AX370-GAMING 5 should correctly use ECC.
  9. JorgeB
    Maybe, the problem is confirming it's really working, and according to Gigabyte: "Support for ECC Un-buffered DIMM 1Rx8/2Rx8 memory modules (operate in non-ECC mode)", that's why I prefer server boards for Intel for NAS use and can't really recommend any Ryzen boards, as I don't have any.
  10. JorgeB
    It should work, but it will operate in non-ECC mode, so really no point. Can't comment on IOMMU grouping.
  11. JorgeB
    Correct.
  12. JorgeB
    No, 20.00.07 is the latest one and it's working fine, LSI controllers are likely the most used with Unraid at the moment, so if they were a problem with v6.6 I'm certain there would be a lot of bug reports, your issue is likely unrelated.
  13. JorgeB
    p20.00.00 and p20.00.04 can have issues with any Linux driver version, and you are already on p20.00.07
  14. JorgeB
    He used 24 drives as a cache pool, you can also do that, current limit is 28 data drives (+1 or 2 parity drives) + 24 cache drives.
  15. JorgeB
    Yes, only array and cache devices, I believe there's no way for now to do that for unassigned devices. You could probably get around it by disabling 197 on the general SMART settings, and then enable for all array/cache devices, though it will stop monitoring other unassigned devices, if you have some.
  16. JorgeB
    Have you tried after booting in safe mode to rule out any plugins?
  17. JorgeB
    On the main page click on the SSD, scroll down to SMART settings and untick attribute 197
  18. JorgeB
    One of his cache devices dropped offline, discussed here, parity is a difference issue I expect he's fixing on his own.
  19. JorgeB
    I believe that error always happens when there are a lot of logged errors and the syslog gets very large, not sure if it's a bug or a design feature.
  20. JorgeB
    You can disable monitoring that attribute just for the SSD for now, no point to keep receiving false alerts.
  21. JorgeB
    No idea what's causing that but there's something very wrong, syslog is showing repeated lines on things that should never repeat and then call traces left and right, maybe start by trying safe mode, or another flash drive.
  22. JorgeB
    Depends on the use, also on the SSD and the amount of spare flash it comes with, you can also overprovision a little if you want to void write performance degradation.
  23. JorgeB
    Same problem if still on the 9207. No, xfs or btrfs (or the not recommended reiser fs)
  24. JorgeB
    There are been some reports of trimm not working on the 9207 with latest Unraid releases, that likely include a newer LSI driver.
  25. JorgeB
    I have the same and first thought it was a problem but if I just wait a few seconds, sometimes it takes a minute or so, the fan control kicks in.
×
×
  • Create New...