Jump to content

JorgeB

Moderators
 View Profile  See their activity

  • Posts

    67,336

  • Joined

  • Last visited

  • Days Won

    705

 Content Type 

Everything posted by JorgeB

  1. JorgeB
    You can, assign all the disks to their original slots and check "parity is already valid" before starting the array.
  2. JorgeB
    Start by trying a different cable and/or switch (or port).
  3. JorgeB
    Backup the config folder, recreate flash with USB tool or manually, restore config folder.
  4. JorgeB
    Post the mirrored syslog after a crash like asked, it might show something.
  5. JorgeB
    Yes
  6. JorgeB
    You're not using parity, so no option to emulate that disk, also using a raid volume as an array device is not recommended, this is one of the reasons, raid controllers can mess with partition layout, Unraid requires a specific layout, sorry but can't help with this.
  7. JorgeB
    No, that will be considered a new device, stop the array, if Docker/VM services are using the cache pool disable them, unassign all cache devices, start array to make Unraid "forget" current cache config, stop array, reassign all cache devices, re-enable Docker/VMs if needed, start array.
  8. JorgeB
    You should post on that docker's support thread:
  9. JorgeB
    If you can try it on a different PC/server, but it's likely DOA.
  10. JorgeB
    Cables appear to the correct ones, no HBA is being detected, try a different slot if available, or a different PC to confirm it's not DOA.
  11. JorgeB
    If there is one, since it's optional, it will show at boot time, unless OPROM are disable in the board bios (or it's booting UEFI), like mentioned you can also post the diags.
  12. JorgeB
    Likely related to this:
  13. JorgeB
    Are the disks detected in the HBA bios? Most common reason for this is using the wrong cables, you need forward breakout cables, reverse breakout look the same but won't work for this, you can also post diags to confirm HBA is being detected correctly.
  14. JorgeB
    As of now keys are lifetime.
  15. JorgeB
    That's a new one: Jan 19 17:32:31 theVault root: mount: /mnt/disk1: unknown filesystem type 'xfs'. It's like the xfs module isn't present, take the opportunity to update to v6.8.1 and reboot, if still the same please post new diags.
  16. JorgeB
    👍
  17. JorgeB
    Just download latest firmware package from Broadcom's support site, you then need to use Windows or Dos for the actual update.
  18. JorgeB
    Usually you don't e even need to stop the services, just upgrade, reboot and are good to go, like mentioned problem could be related to having the docker image on a UD device because of the recent changes with the plugin.
  19. JorgeB
    Try re-doing the flash drive.
  20. JorgeB
    Please post the diagnostics: Tools -> Diagnostics
  21. JorgeB
    Not for the array as long as no RAID controllers are used, VMs with hardware pass-trough might require some re-config.
  22. JorgeB
    More likely to get help if you should post on that docker's support thread.
  23. JorgeB
    If the disk wasn't mounting you should have posted diags, can't help mess with partitions, if the disk isn't disabled you can try to fix the emulated disk and then rebuild on top, rebuilding will correctly re-create the partition .
  24. JorgeB
    Firmware 20.00.00.00 is known to give a lot of CRC errors, so updating to latest will fix that.
  25. JorgeB
    If issues continue with v6.8.1 I would suggest downgrading back to v6.7.2 to confirm if it's OK there, if not it's likely a hardware problem.
×
×
  • Create New...