Jump to content

JorgeB

Moderators
 View Profile  See their activity

  • Posts

    67,504

  • Joined

  • Last visited

  • Days Won

    706

 Content Type 

Everything posted by JorgeB

  1. JorgeB
    It won't hurt to try, I would also get rid of the bond, simplify the LAN as much as possible.
  2. JorgeB
    Try using one of the other NICs, also you appear to have a failing DIMM, check system event log, it might have more info on which one it is.
  3. JorgeB
    Yes, as long that slot is set to x2 in the BIOS.
  4. JorgeB
    Use -L to destroy the log.
  5. JorgeB
    That's not how you run xfs_repair with Unraid, see here: https://wiki.unraid.net/Check_Disk_Filesystems
  6. JorgeB
    sdj1 wasn't successful, so you shouldn't have run sdj, though it won't matter much, reboot and try running preclear again.
  7. JorgeB
    No, M2_1 will disable SATA_2 if used with an M.2 SATA device, it won't with an NVMe device, you also can still use M2_2 and SATA_5/6 if you run the NVMe device @ x2.
  8. JorgeB
    If next check finds 0 errors likely parity wasn't valid before, if it finds more then you likely have a hardware issue, like bad RAM. We recommend setting scheduled checks to non correct.
  9. JorgeB
    Is this the the normalized value or the raw value? Please post the SMART report.
  10. JorgeB
    Try: wipefs -a /dev/sdX1 if successful then wipefs -a /dev/sdX
  11. JorgeB
    The 10GbE NIC is set as eth0 and gigabit to eth1, swap that, you can do that after booting using GUI mode.
  12. JorgeB
    Disk2 is complaining of a duplicate UUID, to make sure it's not some phantom issue reboot and if still unmountable post new diags (after array start).
  13. JorgeB
    Check filesystem on disk3: https://wiki.unraid.net/Check_Disk_Filesystems#Checking_and_fixing_drives_in_the_webGui
  14. JorgeB
    Both disks look fine, mostly likely a cable/power issue, check all cables and try again.
  15. JorgeB
    No need to remove the disk, you can follow this.
  16. JorgeB
    Might not be a problem, or at least not affect normal usage, but it is strange. First start the array with the disk disabled/unassigned and check that the emulated disk is mounting correctly and data looks OK, if yes rebuild on top. Never a good sign, but I've seen that attribute return to normal on its own, after a few power cycles, but if it doesn't consider replacing it.
  17. JorgeB
    Unfortunately log is being spammed with spin down error messages, looks like disk2 isn't spinning down, best to set it to never so at least it won't spam the log, because of that the errors are not visible. Disable disk looks healthy and multiple disk errors suggest another issue, make sure the emulated disk is mounting correctly and that data looks correct then rebuild on top, if it happens again post new diags, don't forget to disable spin down for disk2.
  18. JorgeB
    Since there's no cache it won't be used, though if you're using /mnt/cache paths for anything it will try to use them and fail.
  19. JorgeB
    Perfectly normal, you can set higher temp thresholds for SSDs.
  20. JorgeB
    Yes, assuming the disk is healthy, there are no SMART reports on the diags posted, you'll need to power cycle or reboot, also make sure the emulated disk is mounting correctly and contents look OK before rebuilding on top.
  21. JorgeB
    No, it's a hardware problem. Not unless you can get them detected. Depends on what profile you were using, default is raid1, so you'd just need 1.
  22. JorgeB
    Multiple disk errors suggest a controller issue, but syslog is getting spammed with ACPI errors so can't see anything else, see here how to fix that, then reboot and post new diags if/when it happens again.
  23. JorgeB
    Diags are after rebooting so can't see what happened, but cache devices are not being detected, that's a hardware issue, you need to fix that first.
  24. JorgeB
    Please post the diagnostics: Tools -> Diagnostics
  25. JorgeB
    Diags are after rebooting so we can't see what happened but the disk looks fine, recommend replacing/swapping cables to rule them out and then rebuild on top (assuming the emulated disk is mounting correctly and contents look OK). P.S. you should update to latest beta.
×
×
  • Create New...