JorgeB

Moderators
 View Profile  See their activity

  • Posts

    61486

  • Joined

  • Last visited

  • Days Won

    647

 Content Type 

Everything posted by JorgeB

  1. JorgeB
    Not really at the moment, but once we get to kernel 6.9, FUSE passthrough mode should be available, that's expected to increase performance by a lot, similar to native.
  2. JorgeB
    Constant ATA errors with both disks, looks more like a power/connection issue, replace cables and post new diags.
  3. JorgeB
    You can format the pool using the GUI, change the filesystem to a different one and you can then format, of course you need to backup the pool first.
  4. JorgeB
    I don't think that will make any difference, the HBA is working fine, also no issues with the HBA to enclosure connection, so I think the problem can only be the enclosure, or how the disks are connected there, i.e., if it needs some specific config.
  5. JorgeB
    That's a perfectly valid setup.
  6. JorgeB
    If you have data that needs to be moved you can use this: https://forums.unraid.net/topic/46802-faq-for-unraid-v6/?do=findComment&comment=511923
  7. JorgeB
    Still not seeing anything, does it still happen if you leave the Docker service disabled?
  8. JorgeB
    You need to contact support.
  9. JorgeB
    docker.folder.plg - 2021.08.20 (Up to date) (Incompatible) Remover this plugin, I believe there's a replacement now, but don't remember the name.
  10. JorgeB
    Yes.
  11. JorgeB
    Nothing jumps out to me on the logs, do you know the last timecode it happened?
  12. JorgeB
    The enclosure is being detected by the HBA: [12:0:0:0] enclosu EMC ESES Enclosure 0001 - /dev/sg20 state=running queue_depth=254 scsi_level=7 type=13 device_blocked=0 timeout=30 dir: /sys/bus/scsi/devices/12:0:0:0 [/sys/devices/pci0000:00/0000:00:03.2/0000:28:00.0/host12/port-12:0/expander-12:0/port-12:0:0/end_device-12:0:0/target12:0:0/12:0:0:0] This would point to a problem with the enclosure or how the devices are connected there, difficult for me to help more since I'm not familiar with those enclosures.
  13. JorgeB
    Cache filesystem is fully allocated, not fully used, see here to try and solve it: https://forums.unraid.net/topic/62230-out-of-space-errors-on-cache-drive/?do=findComment&comment=610551
  14. JorgeB
    This.
  15. JorgeB
    Multiple apps segfaulting like that suggests to me that there's still an hardware issue, if it's not RAM it could be a board or CPU issue.
  16. JorgeB
    Post new diags, notifications are known to sometimes be wrong.
  17. JorgeB
    Yes.
  18. JorgeB
    Alternatively you can contact support so that they can extend your trial.
  19. JorgeB
    The flies in the diags are all blanc, you may have flash drive issues, post the output of: df -f
  20. JorgeB
    Could be 3.3v SATA issue:
  21. JorgeB
    Filesystem went read-only, this suggests that it still has other issues, rebooting should make it read/write again, then suggest backing up and re-creating the filesystem to make sure it doesn't happen again.
  22. JorgeB
    If you added a new parity device you must do a parity sync first.
  23. JorgeB
    You can still use macvlan if you need it, but in that case need to disable bridging, see the 6.12.4 release notes for more info.
  24. JorgeB
    Yes, you could boot of the USB drive when you want to use Unraid, and leave the device where the other OS is installed unassigned, and Unraid won't touch it.
  25. JorgeB
    Unraid requires that all devices have a unique serial number, the OOS2000G devices both have the same serial, so you only be able to use one at a time with Unraid.