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
    The listed files should be deleted or restored from a backup if available.
  2. JorgeB
    Please post the diagnostics.
  3. JorgeB
    That's not really my specialty but first try using a Google DNS as the first option to see if that is why it's taking so long.
  4. JorgeB
    Yes, and if it finds corruption look at the syslog for a list of affected file(s) and delete/restore from backups.
  5. JorgeB
    Looks like the LUKS headers are corrupt, do you have a backup of the headers for that encrypted device?
  6. JorgeB
    Yes, those disks are SMR and known to in some cases slow down by a lot during writes.
  7. JorgeB
    Not exactly sure what they mean but I've seen other users with similar errors without issues. NVMe devices don't have SMART tests.
  8. JorgeB
    The addon NIC must have an IP address set, manual or DHCP, or it will start port down. And the DNS server is not set to the pfSense VM?
  9. JorgeB
    The upgrade to v6.11.5 keeps the old setting, if it was macvlan it remains macvlan, if it was ipvlan it remains ipvlan, maybe you upgraded from v6.11.4, the GUI with that release would always show ipvlan even if it was using macvlan.
  10. JorgeB
    Enable the syslog server and post that after the problem.
  11. JorgeB
    Do the NICs have a static or auto IP address configured? Does the server have internet access during boot?
  12. JorgeB
    Enable the syslog server and post that if it happens again together with the complete diagnostics.
  13. JorgeB
    Not really sure since I don't have SAS devices, but it should be mostly install and work, you can ask in the linked support thread if there are any issues.
  14. JorgeB
    You can change the mount point name in UD by clicking on it: Then the mount point is going to be /mnt/disks/mountpoint_name
  15. JorgeB
    Changed Status to Closed Changed Priority to Other
  16. JorgeB
    There's a possibility, bad RAM can cause all sorts of issues.
  17. JorgeB
    Unraid does not support spin down for SAS devices, try installing the SAS spin down plugin.
  18. JorgeB
    Global shares being enabled is normal, are disk shares also enabled?
  19. JorgeB
    Yes, you can create multiple pools, add a new pool, assign both devices, format the pool, looks like you'll need the total capacity of both disks so balance the pool to raid0, then you can unassign both devices from the pool, delete it, and keep using the pool with UD, for that you just mount one of the devices and the other one will mount together.
  20. JorgeB
    DO you know the time it last crashed? Nothing obvious logged.
  21. JorgeB
    You can ignore those, they are harmless.
  22. JorgeB
    Please post the diagnostics during use.
  23. JorgeB
    Please post the diagnostics.
  24. JorgeB
    Run the new permissions tool on that share to see if it helps.
  25. JorgeB
    Most likely parity has the partition starting on sector 2048, parity2 looks OK, but post the output of fdisk -l /dev/sdX for both.
×
×
  • Create New...