Jump to content

JorgeB

Moderators
 View Profile  See their activity

  • Posts

    67,826

  • Joined

  • Last visited

  • Days Won

    708

 Content Type 

Everything posted by JorgeB

  1. JorgeB
    Parity swap is known to sometimes, unclear yet why this happens only in some cases, no correctly zero out the extra parity capacity, so the first check will correct that.
  2. JorgeB
    There were read errors on disk2 during disk4 rebuild: Aug 7 13:25:18 TaFlix-UNRAID kernel: md: disk2 read error, sector=86476512 Aug 7 13:25:18 TaFlix-UNRAID kernel: md: recovery thread: multiple disk errors, sector=86476336 So some corruption is expected, you can check filesystem but if you have the old disk you should them compare the data.
  3. JorgeB
    Switching to ipvlan should fix it (Settings -> Docker Settings -> Docker custom network type -> ipvlan (advanced view must be enable, top right)). What said that? Cache is about 50% used at the moment. Look at the syslog after a scrub and delete/restore the corrupt files, also a good idea to run memtest.
  4. JorgeB
    Single transfer will only use one NIC, did you try simultaneous transfers?
  5. JorgeB
    There's nothing in the log, was it after the crash?
  6. JorgeB
    User shares can be very slow with many small files, if it's an option make those shares use a single disk then use a disk share instead of a user share.
  7. JorgeB
    Problems with the flash drive, try a different USB port, and make sure it's USB 2.0, not 3.0
  8. JorgeB
    Please post the diagnostics.
  9. JorgeB
    Enable the syslog server and post that after a crash.
  10. JorgeB
    With turbo write enable those disks should be able to sustain 100MB/s+ writes.
  11. JorgeB
    Array must be started to see all the mounts.
  12. JorgeB
    If you didn't reboot yet post the diagnostics, if you did grab them next time it happens.
  13. JorgeB
    SMART looks healthy and the extended test passed so the disk is good.
  14. JorgeB
    Check filesystem on disk2, before that check/replace cables, there are ATA errors on that disk suggesting a power/connection problem.
  15. JorgeB
    That suggests a hardware problem.
  16. JorgeB
    If you updated using the GUI you can to Tools -> Update OS and look for the "restore" option, it will show the previous Unraid release installed, I'm just mentioning that because there's a lot of data corruption and you're using a Microserver Gen8 with VT-d enabled, and those are known to be affected by Linux kernel bug that affects all Unraid v6.10 releases except v6.10.3, causing data corruption.
  17. JorgeB
    Array disk to array disk will never be fast because of parity, I was referring to reads and writes from the array to another computer.
  18. JorgeB
    Still ATA errors with disk9, try swapping cables with a different disk, one that is connected to the onboard SATA. re: fs corruption, those should all be fixed, recommend running xfs_repair (without -n) on all array disks.
  19. JorgeB
    Read speed should be the maximum disk read speed at that point, note that disks are much faster in the outer sectors compared to the inner ones. Write speeds can be much faster, assuming no controller bottlenecks, if you use turbo write, at the expanse of all disks spinning up for writes.
  20. JorgeB
    Please use the existing plugin support thread:
  21. JorgeB
    The GUI won't show device errors for pool members, see here for more info and better pool monitoring.
  22. JorgeB
    Syslog posted it's not from the syslog server, it's the same from the diags, that one will only cover the last boot.
  23. JorgeB
    Enable the syslog server and post that after a crash.
  24. JorgeB
    Aug 5 23:01:33 NAS kernel: macvlan_broadcast+0x116/0x144 [macvlan] Aug 5 23:01:33 NAS kernel: macvlan_process_broadcast+0xc7/0x110 [macvlan] Macvlan call traces are usually the result of having dockers with a custom IP address and will end up crashing the server, switching to ipvlan should fix it (Settings -> Docker Settings -> Docker custom network type -> ipvlan (advanced view must be enable, top right)).
  25. JorgeB
    As long as parity is valid and the server has no know issues, like bad RAM or frequent sync errors after a parity check, no reason to expect any issues with the rebuilt disk.
×
×
  • Create New...