Jump to content

JorgeB

Moderators
 View Profile  See their activity

  • Posts

    67,686

  • Joined

  • Last visited

  • Days Won

    707

 Content Type 

Everything posted by JorgeB

  1. JorgeB
    Yep.
  2. JorgeB
    LSISAS2308: FWVersion(20.00.02.00) Update LSI firmware to latest, that one has known issues, then reboot and post new diags.
  3. JorgeB
  4. JorgeB
    Yes, if you want parity to remain valid make sure you mount them read-only, it's an option with UD. You can also disable parity in the new server for faster simultaneous multiple disk copy.
  5. JorgeB
    There are issues with the SAS2LP controller, those controllers are not recommended for v6, if possible replace it with an LSI HBA, if not using ECC RAM also a good idea to run memtest.
  6. JorgeB
    Changed Status to Closed Changed Priority to Other
  7. JorgeB
    Also posted in the general support forum, continue discussion there since this look more like a general support issue:
  8. JorgeB
    Not that I know of, just make sure user shares are still enable after updating.
  9. JorgeB
    It's a known issue with v6.9.x, should be fixed on v6.10-rc1
  10. JorgeB
    Looks like the fs is very damaged, you can try IRC as mentioned in the FAQ, it's frequented by very experienced btrfs users and some maintainers, they might be able to help more, but it doesn't look very good to me.
  11. JorgeB
    There's nothing logged about the crash, this usually points to a hardware issue, make sure you're using the correct power supply idle control setting.
  12. JorgeB
    Minimum free space for that share it set to 2TB, more than it's available on any disk.
  13. JorgeB
    Click on disk1, set filesystem to xfs, then start array and post new diags.
  14. JorgeB
    This is usually a flash drive problem, try recreating it.
  15. JorgeB
    If Supermicro said it's a SAS2 model that would be enough for me.
  16. JorgeB
    It's an expander backplane, you can see the back of the expander chip and also the sticker for the SAS address, but it could be the SAS1 model, and those will be limited to 2TB disks, you should contact Supermicro, since the serial is visible they should be able to identify the model.
  17. JorgeB
    Array is XFS, btrfs is much more sensitive to bad RAM, though if that is the problem you'll also get data corruption on the array, just undetected.
  18. JorgeB
    This.
  19. JorgeB
    You just need to free up some space on cache.
  20. JorgeB
    Not stock, though if notifications are enable you get warnings if any of the monitored attributes change or a SMART test fails, but you can easily run a script with the User Scripts plugin to do that.
  21. JorgeB
    Disks look OK, diags are after rebooting so we can't see what happened, but multiple disk errors are usually a power/connection/controller problem, one thing you should do is update the LSI to latest firmware, since it's on a very old one, then and if it happens again grab diags before rebooting.
  22. JorgeB
    This is normal with SAS devices, SMART on the GUI only works correctly with SATA, diagnostics before rebooting might give some clues.
  23. JorgeB
    These type of read errors can be intermittent, i.e., they can work today and fail tomorrow.
  24. JorgeB
    Looks like Veeam doesn't work with everything: https://forums.veeam.com/vmware-vsphere-f24/xfs-reflinks-enable-not-recognized-t73927.html
  25. JorgeB
    Problem is that this device wasn't decrypted after the reboot: Aug 30 20:40:37 Server emhttpd: import 32 cache device: (sdc) SanDisk_SSD_PLUS_240GB_184302A005B3 It's strange since the device was there, but since it wasn't decrypted it can be used by btrfs, so it was like the device wasn't present and the pool balanced to single, not sure why this is happening, if you have a spare try replacing that SSD with a different one, if it still happens it's likely a bug.
×
×
  • Create New...