Jump to content

JorgeB

Moderators
 View Profile  See their activity

  • Posts

    67,884

  • Joined

  • Last visited

  • Days Won

    708

 Content Type 

Everything posted by JorgeB

  1. JorgeB
    No, like mentioned you should backup any data on the pool, reformat and restore.
  2. JorgeB
    Out of curiosity I was checking my server and there are 3 running smb PIDs, and one of then has a lower soft limit (16464) than the others (40960), type in the console: ps aux | grep smbd then check the limits for all smd processes with: cat /proc/<pid>/limits
  3. JorgeB
    Nope
  4. JorgeB
    Since there's no parity you need to do a new config: Tools -> New config
  5. JorgeB
    Check filesystem on the emulated disk 8
  6. JorgeB
    Try this to see if helps: Some NVMe devices have issues with power states on Linux, try this, on the main GUI page click on the flash drive, scroll down to "Syslinux Configuration", make sure it's set to "menu view" (top right) and add this to your default boot option, after "append initrd=/bzroot" nvme_core.default_ps_max_latency_us=0 pcie_aspm=off e.g.: append initrd=/bzroot nvme_core.default_ps_max_latency_us=0 pcie_aspm=off Reboot and see if it makes a difference.
  7. JorgeB
    checksum error at logical 2050129985536 on dev /dev/nvme0n1p1, physical 147737411584: metadata leaf (level 0) in tree 5 It's metadata corruption so the only way to get rid of it is to backup and re-format the pool.
  8. JorgeB
    Try a different computer but looks like it died.
  9. JorgeB
    LSI 9300 series support trim but only on devices with deterministic read zeros after trim support.
  10. JorgeB
    Nothing obvious, is it still going slow? Not sure the GUI speeds update correctly during this part, best to post new diags.
  11. JorgeB
    Try completing disabling C-States in the BIOS, some users have reported that's the only way to achieve stability with some Ryzen boards.
  12. JorgeB
    That was a typo, sorry about that, it should be plg, update to v6.11.3 and post new diags after rebooting.
  13. JorgeB
    Remove the RAM, reset CMOS, power back up (without RAM), assuming there's a speaker connected, do you hear any beeping?
  14. JorgeB
    It was an unfortunate issue, but it should not cause any data loss, you'd get an unmountable disk if there was a disk replacement, but just needed to unassign the disk and the emulated disk would still mount and show all the data, then downgrade to a previous release and re-assign the replacement disk, after the rebuild starts you could even cancel and upgrade back.
  15. JorgeB
    Looks like the HBA dropped offline and then came back again, make sure it's well seated or try a different PCIe slot if available.
  16. JorgeB
    It is, and it's the latest available for that model, post the diags when you can, they might give some clues.
  17. JorgeB
    Only after changing something.
  18. JorgeB
    Delete/rename /boot/config/network.cfg and network-rules.cfg and reboot, that will change all LAN settings to defaults.
  19. JorgeB
    Unlikely it will help but it won't hurt, also make sure you hear the drives spinning up.
  20. JorgeB
    The main issue with the cables is that they must be forward breakout cables, reverse breakout look the same but won't work for this, but like I mentioned and unless I saw wrong in the first diags it was detecting a drive, that would mean the cables are the correct type, can you confirm if there was a 2TB Seagate Firecuda connected to it? The HBA itself appears to be working correctly, it's detected and initialized without errors, of course if there's some issue with the connections that won't be visible in the logs.
  21. JorgeB
    Firmware was updated OK, but not seeing any drive detected like before, do your hear the drive spinning up? Which model cables are you suing?
  22. JorgeB
    Run a scrub and post new diags after it ends.
  23. JorgeB
    Not sure what that could be, sas2flash is from the Installer_P20_for_Linux? Try the one attached sas2flash
  24. JorgeB
    It's not a problem as long as you don't use RAID controllers.
  25. JorgeB
    It's detecting a 2TB Seagate but failing to initialize it, try swapping that disk with known good, like of of the already assigned disks, it would also be a good idea to update the firmware, it's using an old one.
×
×
  • Create New...