Jump to content

JorgeB

Moderators
  • Posts

    67,814
  • Joined

  • Last visited

  • Days Won

    708

Everything posted by JorgeB

  1. Problems with the onboard SATA controller, quite common with some Ryzen servers, best bet is to use an add-on controller (or a different board).
  2. Enable the syslog server and post that together with the complete diagnostics after the next crash.
  3. Aug 2 07:49:22 ur01 kernel: macvlan_broadcast+0x10e/0x13c [macvlan] Aug 2 07:49:22 ur01 kernel: macvlan_process_broadcast+0xf8/0x143 [macvlan] Macvlan call traces are usually the result of having dockers with a custom IP address, upgrading to v6.10 and switching to ipvlan should fix it (Settings -> Docker Settings -> Docker custom network type -> ipvlan (advanced view must be enable, top right))
  4. I don't see a problem detecting any extra disks, assuming they are also connected to the LSI HBA check its BIOS and confirm they are being detected there, if not they also won't be detected by Unraid.
  5. I don't use that plugin, ask in the existing plugin support thread:
  6. That's fine, the other way avoided transferring the key, but even if you need to do it again before 1 year you just need to contact LT support.
  7. I see you have a 10TB Ironwolf unassigned, suggest assigning that disk to a pool and see if you see the same issues while transferring data to it.
  8. Diags are after rebooting so we can't see what happened, disk looks OK and if now it's in a different slot rebuild and see if it happens again to the same disk, since the array is stopped in the diags, before rebuilding on top make sure the emulate disk is mounting and contents look correct.
  9. That's known to cause the "stale config" warning, if it keeps happening try a different browser.
  10. I personally know the SV300 and they are pretty slow, the other 120GB SSD also doesn't like like a performance model, and most 120GB are much slower than larger capacity SSDs, due to parallel writing to the large number of flash modules, not all ( read most) SSDs can sustain announced write speeds.
  11. Multiple call traces, start by running memtest.
  12. Try rebooting in normal mode, if you get stale config again uninstall all the plugins then re-install one at a time.
  13. I have an array of SMR drives and pretty used to see writes speeds <5MB/s for a few minutes at a time.
  14. Yes, but I wanted to see ones showing the parity sync, which is going at 185MB/s, quite normal, also note that most of your disks are SMR, including parity, so some write performance degradation is expected.
  15. Correct, and the main Unraid NIC must be set to eth0.
  16. Go to Settings -> Network Settings -> Interface rules and make the Gbit NIC eth0, then reboot, it will have the same settings as the older eth0. eth1 should then use a different subnet for the direct PC connection.
  17. Parity sync errors were immediately after the disk read errors, so yes, replacing it should fix that, assuming parity was 100% in sync.
  18. Please try rebooting in safe mode to rule out any plugin and post new diags if you see the same.
  19. Aug 1 14:00:07 Tower kernel: nvme nvme1: Device not ready; aborting initialisation, CSTS=0x0 Aug 1 14:00:07 Tower kernel: nvme nvme1: Removing after probe failure status: -19 Device is failing to initialize, if you can test with a different OS to confirm if the device is working or not.
  20. Disk is OK for now, but like mentioned it doesn't look very good, it will likely fail again in the near future, up to you if you want to give it another shot or replace now.
  21. libvirt.img should be excluded, it's a file that can change.
  22. Use the recover password procedure: https://wiki.unraid.net/Manual/Troubleshooting#Lost_root_Password
  23. Either one works, use the most convenient for you.
×
×
  • Create New...