Jump to content

JorgeB

Moderators
  • Posts

    67,540
  • Joined

  • Last visited

  • Days Won

    707

Everything posted by JorgeB

  1. You appear to be using the "most free" allocation method, that's very bad for performance due to overlapping writes to parity.
  2. Yep, likely not the reason the for problem, maybe a one-off thing...
  3. Nothing obvious, start by running a single stream iperf test, if that's normal check if read speed is the same from array or cache.
  4. That's not normal, but also not an Unraid problem.
  5. Disk looks fine, you should upgrade the LSI firmware since all p20 releases except 20.00.07.00 have known issues. after that re-enable the disk, if it gets disabled again then it could really be the disk (assuming you swapped both cables before).
  6. Just re-assign all the devices as they were before and check "parity is already valid" before starting the array.
  7. If you haven't yet nonnect a different device to that port, if errors persist it's likely a board problem.
  8. Difficult to say, BIOS update might help, same for a newer kernel in a future Unraid release.
  9. Looks like a problem with one the SATA controllers, it dropped both connected disks, possibly related to IOMMU, is device 06:00.0 in its own group if you don't use pcie_acs_override?
  10. Pool has dual data profiles, single and raid0: Data Data Metadata System Id Path single RAID0 single single Unallocated -- --------- --------- --------- --------- -------- ----------- 1 /dev/sdb1 100.00GiB 60.55GiB 1.01GiB 4.00MiB 62.01GiB 2 /dev/sdd1 - 60.55GiB - - 386.58GiB Run balance to raid0 again.
  11. Try this and post that log after the next crash.
  12. If I understand correctly you currently have cache2 only working? If yes just add cache1 back to the pool, best to wipe it first though.
  13. NIC is not supported by v6.8.x, use v6.9-beta.
  14. CPU usage in the dashboard includes I/O wait, check with top, it will show actual CPU utilization.
  15. Hardware errors are memory related, check system/ipmi event log, there should be more info there.
  16. Make sure BIOS is up do date, though some boards might not have this option, but they should.
  17. Also make sure cache floor is correctly set.
  18. Disk1 does show less data now than before, but that will have nothing to do with parity and stock Unraid behavior, something/someone else is deleting your data.
  19. My suspicions were correct: Device 09:00.0 was the GPU: 09:00.0 VGA compatible controller [0300]: NVIDIA Corporation TU104 [GeForce RTX 2070 SUPER] [10de:1e84] (rev a1) Subsystem: Gigabyte Technology Co., Ltd Device [1458:4001] Kernel driver in use: vfio-pci Now is a SATA controller 09:00.0 SATA controller [0106]: Advanced Micro Devices, Inc. [AMD] FCH SATA Controller [AHCI mode] [1022:7901] (rev 51) Subsystem: Advanced Micro Devices, Inc. [AMD] FCH SATA Controller [AHCI mode] [1022:7901] Kernel driver in use: vfio-pci Kernel modules: ahci And is being passed-through/bound to a VM.
  20. Please use the existing plugin support thread:
  21. Please post the diagnostics: Tools -> Diagnostics
×
×
  • Create New...