Jump to content

JorgeB

Moderators
 View Profile  See their activity

  • Posts

    67,871

  • Joined

  • Last visited

  • Days Won

    708

 Content Type 

Everything posted by JorgeB

  1. JorgeB
    Oct 11 11:49:14 FileSRV kernel: e1000e 0000:00:1f.6: The NVM Checksum Is Not Valid Oct 11 11:49:14 FileSRV kernel: e1000e: probe of 0000:00:1f.6 failed with error -5 Look for a BIOS/firmware update.
  2. JorgeB
    It really depends on your needs, but that looks OK.
  3. JorgeB
    Those are not good, you should not have more than two drives on a SATA splitter.
  4. JorgeB
    Running xfs_repair is the only option to fix that.
  5. JorgeB
    Try booting in safe mode to see if it's plugin related.
  6. JorgeB
    Diags are being spammed with USB related issues, so difficult to look for anything else, but the disk looks healthy, so most likely a power/connection problem, you should also update Unraid, v6.7 is ancient by now.
  7. JorgeB
    Appdata share is set to use the docker_nvme pool, if an appdata folder is being created in another pool you likely have a container creating it, check all container paths.
  8. JorgeB
    Diags are after rebooting so we cannot see what happened but disk3 looks fine, disk7 should be replaced since there's a failing NOW attribute, parity swap requires that the array be offline during the parity copy part, it will be online for the rebuild.
  9. JorgeB
    Pool is a mess, these errors suggests both devices dropped offline in the past: Oct 10 13:27:34 PlexServer kernel: BTRFS info (device sde1): bdev /dev/sde1 errs: wr 23018629, rd 43586, flush 92116, corrupt 2684790, gen 0 Oct 10 13:27:34 PlexServer kernel: BTRFS info (device sde1): bdev /dev/sdf1 errs: wr 59247801, rd 1252542, flush 618630, corrupt 14809834, gen 0 Run a correcting scrub to see if it still can be corrected, then post the output.
  10. JorgeB
    Oct 10 23:22:19 Tower kernel: ata10: reset failed, giving up Oct 10 23:22:19 Tower kernel: ata10.00: disabled Disk9 dropped offline again, did you replace both cables?
  11. JorgeB
    That suggests a problem with the installation, try recreating the flash drive, backup current /config folder first then restore it.
  12. JorgeB
    This is usually a bad SATA cable.
  13. JorgeB
    Parity can be on the same controller, also don't forget that Unraid array performance can only be as fast as the slowest disk at any point, so if for example you have one slow disk with a max speed of 140/150MB/s the array cannot be faster than that, and a single -16i controller would perform the same as two -8i.
  14. JorgeB
    If you are using Firefox try with a different browser.
  15. JorgeB
    You can click on the thumbs down to acknowledge the current errors, if there are more in the future it means there's still a problem, and like mentioned it's usually a bad SATA cable.
  16. JorgeB
    Do you mean it stops at the Unraid boot menu?
  17. JorgeB
    Please post the complete diagnostics.
  18. JorgeB
    Everything looks normal for now, hopefully it was a one time thing, but in any case it was not Unraid related.
  19. JorgeB
    Problem started a couple of days after the server was first booted, if it starts again try to see if it coincides with some device accessing the server.
  20. JorgeB
    You can try using a data recovery util life UFS explorer for example.
  21. JorgeB
    Make sure the plugin is up to date.
  22. JorgeB
  23. JorgeB
    Try typing in the console: unraid-api restart If that doesn't do it best to repost that error in the MyServers support subforum.
  24. JorgeB
    No, data disks are not touched, parity might need to be resynced/corrected if the USB bridge is non transparent.
  25. JorgeB
    Devices can sometimes easily drop offline and USB in general is bad at error handling, also some USB bridges are not transparent, i.e., if you move the disk to a SATA controller it might not be recognized by Unraid because it has a different identifier and/or it might not recognize the partition.
×
×
  • Create New...