JorgeB

Moderators
  • Posts

    61659
  • Joined

  • Last visited

  • Days Won

    650

Everything posted by JorgeB

  1. Unraid can only format array or pool derives, and only after the array is started, format button is next to the array stop button.
  2. Your are using a cracked key: https://unraid.net/buy-genuine-license
  3. The global settings should also work, but if for some reason they are not, use those.
  4. Not directly, depends on how the pool is configured, for a example a single device will be slower than a raid0 pool, but perform about the same as a raid1 pool. Yes, if you consider a mirror a backup.
  5. Depends on how they are assinged, if they are in the same pool it can also be a mirror. What do you mean affect? If you mean if it can be added later, it can. No, You cannot have parity without array data devices. Yes, but not automatically, you could use a script for example, there are also some containers that work for that, look in Apps.
  6. Those are set in /boot/config/disk.cfg, check if they are correct there, they are set disk by disk, for disk1 for example it's these lines: diskWarning.1="50" diskCritical.1="" Disk2 would be: diskWarning.2="50" diskCritical.2="" etc
  7. See if it works correctly now, re-apply for all other disks and check they were added to the smart-one.cfg, you can open the file with any text editor
  8. Run a correcting scrub in the pool, and make sure all errors are corrected.
  9. Just don't click preclear, it won't start on its own.
  10. Sorry, missed them below the screenshots. First thing update to latest stable, but I don't see the smart-one.cfg file, and it should exist if there are custom tempos for array devices, see if it exists locally, if not, after updating, try changing temps for one of the array disks and see if it still doesn't get created.
  11. Apr 26 07:32:59 unraid kernel: nvme nvme0: controller is down; will reset: CSTS=0x3, PCI_STATUS=0x10 Apr 26 07:33:10 unraid kernel: nvme nvme0: Device not ready; aborting reset, CSTS=0x3 Apr 26 07:33:10 unraid kernel: nvme nvme0: Removing after probe failure status: -19 NVMe device dropped offline, try power cycling the server, not just rebooting, to see if it comes back.
  12. Yes. It's perfectly fine, if it matches your use case, both pool can be set as primary storage for any shares. Yes. For that you'd need to assign at least one of the devices to the array, instead of the flash drive.
  13. Pool went read only, with btrfs suggest you backup the data and re-format.
  14. Yes. You can set a pool as the primary storage for shares.
  15. What do you mean by WebPanel, is this a container?
  16. Docker image is corrupt, delete and re-create: https://docs.unraid.net/unraid-os/manual/docker-management/#re-create-the-docker-image-file Also see below if you have any custom docker networks: https://docs.unraid.net/unraid-os/manual/docker-management/#docker-custom-networks
  17. Enable mover logging, run the mover, look at the syslog. Reboot, if it still gets created it's pretty sure there's a container mapped to that.
  18. That looks like a hardware problem, but it can be difficult to troubleshoot remotely, if you have some more spare parts you can try besides the PSU do it.
  19. If it doesn't boot it's a different issue, that line won't affect booting.