Jump to content

JorgeB

Moderators
 View Profile  See their activity

  • Posts

    67,893

  • Joined

  • Last visited

  • Days Won

    708

 Content Type 

Everything posted by JorgeB

  1. JorgeB
    Nope, it's already on the latest available firmware and IT mode: Nov 29 18:51:21 Tower kernel: mpt2sas_cm0: LSISAS2308: FWVersion(20.00.07.00), ChipRevision(0x05), BiosVersion(07.39.02.00) Nov 29 18:51:21 Tower kernel: mpt2sas_cm0: Protocol=(Initiator,Target), Capabilities=(TLR,EEDP,Snapshot Buffer,Diag Trace Buffer,Task Set Full,NCQ)
  2. JorgeB
    It's a known issue, use a different browser, or don't click the resend box, I believe that it will work if don't do that.
  3. JorgeB
    If it works with Win10 is suggests a Linux in tree driver issue, problem is that the Intel Linux out of tree drivers usually cause different issues, best bet it to wait for a newer release with a newer in tree driver, soon also there should be an option to easily install out of tree drivers with Unraid, so you can then try those.
  4. JorgeB
    It's strange, another option to try and troubleshoot would be to swap that NVMe device with a different one and see if the issue follow the device or the slot.
  5. JorgeB
    It does, it looks like the problem it the Intel 10GbE NIC, not the btrfs filesystem: Nov 30 06:15:47 afterdark kernel: BTRFS info (device nvme1n1p1): start tree-log replay Nov 30 06:16:17 afterdark kernel: ------------[ cut here ]------------ Nov 30 06:16:17 afterdark kernel: NETDEV WATCHDOG: eth0 (ixgbe): transmit queue 18 timed out Maybe that NVMe device having some conflict with the NIC, can you try without the NIC or with disabled?
  6. JorgeB
    Try uninstalling the S3 sleep plugin.
  7. JorgeB
    Run a scrub, but most likely there's some data and/or filesystem corruption, I would suggest backing up and reformatting the pool, after the memory issue is solved of course.
  8. JorgeB
    It will work with CSM or UEFI boot, difference is that with UEFI you might not see the LSI BIOS, depends on the board. If you confirmed the drives are spinning up it suggests a HBA or cable problem.
  9. JorgeB
    A permanent syslog would be better, but if 'start tree-log replay' is the last line displayed it suggests a problem with the tree-log, if that's the only problem this might fix it: btrfs rescue zero-log /dev/nvme1n1p1 If you rebooted since check that the device is still nvme1n1, then try mounting again.
  10. JorgeB
    There have been multiple reports of this happening with Firefox, after a "Resend data" or similar box appears.
  11. JorgeB
    Try a different browser, also make there are no Ad-blocker or firewalls blocking GUI access.
  12. JorgeB
    Yep. Keep an eye on and total uncorrected errors, you can also run long SMART tests.
  13. JorgeB
    Sorry, not familiar with those servers, Googling the backplane model should find some results.
  14. JorgeB
    That is the normal output for a SAS drive, it's very different than SMART for ATA devices.
  15. JorgeB
    Correct, don't forget the 1 in the end or it won't work.
  16. JorgeB
    One of the recommended LSI HBAs should work fine.
  17. JorgeB
    It's a problem with the release you are using, update to v6.11.5 and try again.
  18. JorgeB
    Btrfs is detecting data corruption, start by running memtest.
  19. JorgeB
    Nov 30 13:17:37 WaWi-Server kernel: atlantic: Boot code hanged Nov 30 13:17:37 WaWi-Server kernel: atlantic: probe of 0000:01:00.0 failed with error -110 It's failing to initialize, you just changed the CPU?
  20. JorgeB
    You need to copy to /domains, VM service must be disabled, after doing that post new diags after array start.
  21. JorgeB
    If xfs_repair doesn't work, and like it won't if it didn't by now, there's one last thing you can try, and you need to do that to run a file recovery util anyway, rebuild the disk as is, then run xfs_repair on the sd device (xfs_repair -v /dev/sdx1), the result will likely be the same but it's just to rule out any md driver issues, there have been a couple of times where it did make a difference.
  22. JorgeB
    Are you using Firefox? If yes reboot first then connect with a different browser.
  23. JorgeB
    Let it run until if finishes, because if xfs_repair cannot fix the filesystem, and assuming no backups exist, the only solution to try and recover the data would be running a file recovery util like UFS explorer.
  24. JorgeB
    Yep.
  25. JorgeB
    If it still didn't find one unlikely to find it later, so do it now.
×
×
  • Create New...