Jump to content

JorgeB

Moderators
 View Profile  See their activity

  • Posts

    67,849

  • Joined

  • Last visited

  • Days Won

    708

 Content Type 

Everything posted by JorgeB

  1. JorgeB
    Try using a different flash drive.
  2. JorgeB
    Delete/rename /boot/config/network.cfg so it will go back to defaults and then check if the server and get an IP address from the DHCP server.
  3. JorgeB
    LSI3008 has RAID and IT modes but AFAIK 3108 is RAID only.
  4. JorgeB
    RAID controller is still changing the devices names, and that is the problem, e.g. parity it was: WDC_WD80EFAX-68LHPN0_7SGMN7JC and now is : WDC_WD80EFAX-68L_7SGMN7JC_35000cca252c8ef0a You can do a new config but will have issues again if you change the controller in the future, we recommend using a true LSI HBA.
  5. JorgeB
    Power cycle the server (not just rebooting) to see if the missing device comes back online.
  6. JorgeB
    Looks like the first device was still in use when it was disconnected, hence the following problems, rebooting will fix it.
  7. JorgeB
    If you don't use the iGPU block it from loading the driver, it could be this issue:
  8. JorgeB
    You can wipe it by stopping the array and typing blkdiscard -f /dev/nvme#n1 then start the array to format
  9. JorgeB
    Jul 26 17:14:29 UnRaid-Server kernel: macvlan_broadcast+0x116/0x144 [macvlan] Jul 26 17:14:29 UnRaid-Server 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, upgrading to v6.10 and switching to ipvlan should fix it (Settings -> Docker Settings -> Docker custom network type -> ipvlan (advanced view must be enabled, top right)).
  10. JorgeB
    You can try swapping cables to confirm but it looks like a disk problem, not even generating a valid SMART report.
  11. JorgeB
    Eth1 doesn't need to be in a bridge, but yes, looks like that should work.
  12. JorgeB
    Did you replace the cables before this like I suggested or not? If yes it suggests a cable problem, if not it might be a power issue, do the SSDs share for example a power splitter?
  13. JorgeB
    Some RAID controllers don't fully/correctly support spin down, was going to suggest testing on an onboard SATA port but it looks like there are none.
  14. JorgeB
    It should work again once -rc5 is released, so please re-test once it's available.
  15. JorgeB
    Use a different IP subnet for the 2.5GbE NIC, e.g. 192.168.10.x, then access the server by IP or add that IP to the WIndows hosts file.
  16. JorgeB
    Enable the syslog server and post that after a crash.
  17. JorgeB
    This suggests the devices are waiting for the data, then writing in quick bursts, start by checking NIC link speed is 10GbE and not 1GbE, if 10GbE run a single stream iperf test in both directions.
  18. JorgeB
    Delete this invalid key since it's spamming the log: /boot/config/03F0-5307-0000-0000000002C0.key Then see here to disable the RAM overclock and respect max officially RAM speed for that config, also not a bad idea to run a quick memtest after.
  19. JorgeB
    Unassign one of the parity drives, start array, stop array, assign old parity as disk1, start array to begin rebuilding.
  20. JorgeB
    Please post the diagnostics.
  21. JorgeB
    This won't happen if you properly remove the device from the pool first, or wipe them manually, if you don't and separate both members to different pools it will happen, but we don't want Unraid to wipe new members of a pool, or it would not be possible to import old pools.
  22. JorgeB
    Yep, as long as you boot CMS/legacy, it won't work with UEFI boot. It only checks the RAM, but those errors appear to be the result of bad RAM
  23. JorgeB
    You needed to reboot first: Sep 10 08:47:47 Gringotts root: Warning: The kernel is still using the old partition table. Sep 10 08:47:47 Gringotts root: The new table will be used at the next reboot or after you Sep 10 08:47:47 Gringotts root: run partprobe(8) or kpartx(8)
  24. JorgeB
    Looking OK.
  25. JorgeB
    That looks like a bad flash drive, might be wroth grabbing the diagnostics and posting them after it happens.
×
×
  • Create New...