Jump to content

JorgeB

Moderators
 View Profile  See their activity

  • Posts

    67,797

  • Joined

  • Last visited

  • Days Won

    708

 Content Type 

Everything posted by JorgeB

  1. JorgeB
    Yes, it won't affect the rebuild, check filesystem on disk2 when it's done.
  2. JorgeB
    CPU usage is still very high for just two disks going at those speeds: USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND root 2 0.0 0.0 0 0 ? S 22:22 0:00 [kthreadd] root 92867 94.9 0.0 0 0 ? R 22:31 3:35 \_ [unraidd0]
  3. JorgeB
    9211 could limit performance a little in an x4 slot with 6 fast disks, other 2 options will be the same.
  4. JorgeB
    Sounds good to me.
  5. JorgeB
    First thing to try is booting in safe mode to rule out any plugin, you can also disconnect the power button just to make sure there's not a problem there.
  6. JorgeB
    That would be unrelated, 6.10.3 doesn't blacklist any NICs like some previous 6.10 releases, please post the diagnostics.
  7. JorgeB
    Best bet is to use the container's existing support options:
  8. JorgeB
    Enable mover logging, run the mover and when it stops post diags.
  9. JorgeB
    Run another parity check without rebooting and post new diags if sync errors are found.
  10. JorgeB
    There appears to be issues with the flash drive, not sure it's related,. you should also update Unraid since you're on an ancient release.
  11. JorgeB
    Make a backup of the flash drive just in case but usually there's not much to it, just update and reboot.
  12. JorgeB
    Did rsync finish the transfer? Incomplete transfer folders might have the wrong permissions, if it did finish also check folder permissions and compare with a working one
  13. JorgeB
    You can still use the data in the other disks, just need to do a new config and re-sync parity.
  14. JorgeB
    Cache2 SSD appears to be failing, you can run an extended SMART test to confirm.
  15. JorgeB
    Found the other thread but there's no clear solution, some things to try though: https://forums.unraid.net/topic/123903-slow-parity-rebuild/?do=findComment&comment=1130584
  16. JorgeB
    I believe there's a plan for Unraid to soon have an option to easily install out of tree drives, this is the best bet for issues like these, since compiling the various out of tree drivers with every Unraid release was becoming very difficult for LT.
  17. JorgeB
    Don't see how.
  18. JorgeB
    After replacing the cables start the array and check that the emulated disk is mounting and contents look correct, then you can rebuild on top: https://wiki.unraid.net/Manual/Storage_Management#Rebuilding_a_drive_onto_itself
  19. JorgeB
    Again, it only affects Broadcom NIC, and it's resolved on v6.10.3, no NICs are disabled there. If it's really hardware it won't fix it, but since the driver is likely newer it might help if it's not.
  20. JorgeB
    Yes, it does look like a power/connection problem, disk 1 also showing similar issues, replace cables and rebuild.
  21. JorgeB
    It's up to you, but the data corruption issue is not NIC related, and even when we suspected it was it was with Broadcom NICs, not Intel.
  22. JorgeB
    Jul 5 09:39:17 Tower kernel: ahci 0000:03:00.0: AHCI controller unavailable! Problems with the Marvell controller, and all devices connected there dropped, Marvell controllers are not recommended for Unraid, first thing I would recommend is replacing it with a recommended controller, once that's done (or if you don't want to do that for now just power cycle the server) run a scrub on the pool and post new diags.
  23. JorgeB
    There was a QEMU related crash: Jul 4 17:06:42 Tower kernel: qemu-event[9717]: segfault at 0 ip 0000148e82990396 sp 0000148e7e03d930 error 4 in libvirt.so.0.6005.0[148e82846000+1f6000] Rebooting should fix it, if it doesn't post new diags.
  24. JorgeB
    That suggests a NIC problem. You don't need to do that for v6.10.3, also your NIC wasn't affected even when you needed to use that. No, and those are fixed in v6.10.3, there could be some issue with your hardware though.
  25. JorgeB
    The sync thread is single threaded and the CPU usage is very high for the speed it's going, there was a similar case recently, also with a threadripper IIRC, but don't remember the solution, let me see if I can find it.
×
×
  • Create New...