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
    It's not known and if it happens again grab the diagnostics before rebooting so we can see what happened.
  2. JorgeB
    There are some crashes/timeouts related to the NVMe device, please try running without it, keep the syslog server going and post a new one if it crashes again.
  3. JorgeB
    It should stop displaing temps for all dropped drives, that's a clue to which ones dropped, you also won't be able to get SMART attributes for them.
  4. JorgeB
    Try a different browser other than Firefox, if still the same please try rebooting in safe mode, if you get the stale config error post new diags.
  5. JorgeB
    Problem with the onboard SATA controller, quite common with some Ryzen servers, reboot and post new diags after array start, if this continues to happen best bet is to get an add-on controller (or use a different board).
  6. JorgeB
    "Invalid partition layout" is not a filesystem problem, the disk lost/damaged some part of the MBR, looks like it mostly happens with WD disks, so possibly a firmware problem. To fix you can rebuild the the disk, assuming parity is valid, you just unassign it, start the array, Unraid will recreate the partition correctly and emulated the disk, if all looks good you can then rebuild on top, alternatively you could mount the disk outside the array and copy the data back to it.
  7. JorgeB
    Looks like you solved it, do you mind posting the solution?
  8. JorgeB
    It's not one drive, all devices connected to the controller drop offline, you just get one disabled disk because Unraid only disables as many disks as there are parity drives, but obviously the server cannot continue to work correctly.
  9. JorgeB
    Aug 2 11:26:53 Altair8800 kernel: macvlan_broadcast+0x116/0x144 [macvlan] Aug 2 11:26:53 Altair8800 kernel: macvlan_process_broadcast+0xc7/0x110 [macvlan] Beside the mentioned possible hardware issues this will also make Unraid crash, these are usually the result of having dockers with a custom IP address, switching to ipvlan should fix it (Settings -> Docker Settings -> Docker custom network type -> ipvlan (advanced view must be enable, top right)).
  10. JorgeB
  11. JorgeB
    Most likely
  12. JorgeB
    If memtest doesn't find anything suggest updating to v6.11.0-rc2 and test, newer kernel might help.
  13. JorgeB
    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).
  14. JorgeB
    Enable the syslog server and post that together with the complete diagnostics after the next crash.
  15. JorgeB
    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))
  16. JorgeB
    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.
  17. JorgeB
    I don't use that plugin, ask in the existing plugin support thread:
  18. JorgeB
    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.
  19. JorgeB
    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.
  20. JorgeB
    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.
  21. JorgeB
    That's known to cause the "stale config" warning, if it keeps happening try a different browser.
  22. JorgeB
    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.
  23. JorgeB
    Multiple call traces, start by running memtest.
  24. JorgeB
    Try rebooting in normal mode, if you get stale config again uninstall all the plugins then re-install one at a time.
  25. JorgeB
    I have an array of SMR drives and pretty used to see writes speeds <5MB/s for a few minutes at a time.
×
×
  • Create New...