Jump to content

JorgeB

Moderators
  • Posts

    67,480
  • Joined

  • Last visited

  • Days Won

    706

Everything posted by JorgeB

  1. If you haven't yet you can try beta25 and re-partition the NVMe device, it now aligns the partitions for non rotational devices on the 1Mib boundary, and that can make a lot of difference for some SSDs, e.g. Samsung is one the known affected brands.
  2. If you only see two shares using the disk mappings the other ones are either gone or were moved inside one of the existing ones, shares are just top level folders.
  3. It's faster than normal Unraid parity write speed, i.e., if you use 2 or more data drives, though you can get close to that with turbo write.
  4. Try this to see if it catches something, post it after a crash.
  5. That doesn't make much sense, they shouldn't get hotter than that just idling, or even during continued use.
  6. Even if there's an issue with spin down, and there might be if there were SMART changes, disks should never overheat if left always spun up, that suggests insufficient cooling.
  7. The temps come from the disks themselves, so they are really getting hot, when it happens again check your cooling, you might have a problem with one or more fans.
  8. If you use a single data device + plus parity Unraid will basically work as a RAID1 (mirroring) setup.
  9. There's no option AFAIK, any unpartitioned non rotational device will be partitioned starting on the 1MbB boundary, and I see the default partition format setting was removed, which is understandable since no one should be currently formatting disk with unaligned partitions.
  10. I don't see anything out of the ordinary on the logs, are the shares not available locally and on the LAN or just on the LAN?
  11. If it's not RAM the board/controller would be my next suspect, but not so easy to test unless you have another board/CPU combo you could test with.
  12. Please post the diagnostics: Tools -> Diagnostics
  13. There's nothing on the log about the crash, which might suggest a hardware problem, but try safe mode with all dockers/VMs stopped for a few hours to see if it makes any difference.
  14. Run an extended SMART test on each disk.
  15. No, I don't use encryption, also if you can get a sector by sector copy of one of the failed disks you can rebuild the array (assuming parity was valid).
  16. 10m (33 feet) cables from HBA to a SAS expander should be fine and within specs, form SAS expander to SATA devices 1m (3.3 feet) max, but you should use as smaller cables as possible.
  17. Is this delay loading the main page or for the UD animation? I have 35 UDs on one of my servers and the main page loads instantly, UD animation takes a couple of seconds before it displays the devices. I would also like to see this, the less the refresh animation shows the better, if possible of course. My main request for current UD would be to update the disks used/free space in real time, like the GUI does, currently you need to refresh the GUI (and wait for the animation), again if possible to do.
  18. I assume the SAS disks are on the LSI HBA, there's no reason for the LSI not work with the beta, are you sure that is the problem, i.e. if you downgrade to they show up? If yes post those diags.
  19. Encrypted disks can be accessed on any Linux distro with LUKS support, you need to provide the key.
  20. You should post the diagnostics after this happens.
  21. Because it isn't. Do you mean you formatted the disks? If not check filesystem on both, only after that and in case it's successful you think of rebuilding.
  22. See here, it should be enough to run a stable Ryzen based server.
  23. Max officially supported RAM speed with 4 DR DIMMs is 2667Mhz, make sure you won't go above that.
×
×
  • Create New...