Jump to content

JorgeB

Moderators
  • Posts

    62,244
  • Joined

  • Last visited

  • Days Won

    659

Everything posted by JorgeB

  1. Run xfs_repair again without -n or nothing will be done.
  2. One thing you can try is to boot the server in safe mode with all docker/VMs disabled, let it run as a basic NAS for a few days, if it still crashes it's likely a hardware problem, if it doesn't start turning on the other services one by one.
  3. UFS explorer has been used successfully by other users to recover deleted data.
  4. Disk looks fine, first thing to try is to update the LSI firmware to latest.
  5. If they are also using br1 no idea what it could be.
  6. This works but it's not a direct replacement, first add one device and only after that's done can you remove the old one. There's a good change your old cache is still recoverable if nothing else was done, please post the diagnostics.
  7. If you mean the docker image you can just recreate it on a different device, you also move the appdata folder there if you want using for example the mover, docker service must be disabled first.
  8. Lots of crashes in the log but not clear to me what's causing them, did these start after any changes, hardware or software?
  9. Have you seen this? There are reports that a kernel change can make a difference, i.e., users that didn't need to do this before start needing it after a kernel change, others had power supply correctly set but need to complete disable C-sates after a change.
  10. You are looking to see if the internet starts working.
  11. Try switching to ipvlan (Settings -> Docker Settings -> Docker custom network type -> ipvlan (advanced view must be enabled, top right)).
  12. If there was an unclean shutdown Unraid will start an automated parity check, but that is OK. This will depend on the enclosure.
  13. This suggests a LAN problem, connection or router, try deleting/renaming /boot/network.cfg and post the diagnostics after boot.
  14. Do you mean you followed the part for a directly device replacement that has a line across it and mentions it does no longer works or was this a multi device pool? If the latter please post the diagnostics.
  15. Not much else you can do other then trying again, if still nothing try with a different device if available.
  16. Nothing obvious in the log that I can see, you are using eth2 as you main NIC (in a bond), technically it's OK but we recommend using eth0 as the main one, also since there' no link in the other NIC remove the bond, if it still happens suggest trying using the other NIC instead.
  17. Still looks to me more like a firmware problem, I would contact Intel support and ask if a firmware update is available for that NIC.
  18. There are some OOM errors. Also see btrfs detecting data corruption, so a good idea to run memtest.
  19. Yeah, I think this could be a recently introduced Samba bug but if you can live with that setting disabled for now it would be probably best for now.
  20. This is a NIC problem, see if you can still access the server over SSH.
  21. It could very well be, XMP is overclocking, with Ryzen especially you want to keep to the max supported speeds for your config.
  22. They would only be the same if they were a mirror in the same pool As you prefer, single cache can be xfs or btrfs, depending on the user preference, both have advantages and disadvantages.
×
×
  • Create New...