Jump to content

JorgeB

Moderators
  • Posts

    67,737
  • Joined

  • Last visited

  • Days Won

    708

Everything posted by JorgeB

  1. You can do a new config to re-enable disk4 and rebuild parity, but since disk10 appears to be failing there might be read errors making it not 100% valid.
  2. Unraid can boot using UEFI, just enable that in the USB tool or rename EFI- to EFI in the flash drive if already created without UEFI support.
  3. That's risky since if another drives fails you'll be in trouble, the only thing you can do is to exclude it from the shares so no new data goes there, and also avoid reading from it.
  4. Not needed, and likely would fail since the disk is bad, replacing the disk will rebuild the data to the new disk.
  5. Nothing obvious in the diags, try the diskspeed docker to see if all disks are performing normally.
  6. If you can't complete a parity check without crashing first you need to fix that, and if it also crashes in safe mode it suggests a hardware issue, try with a different PSU or board if available.
  7. Unfortunately there's nothing relevant logged, one thing you can try it to boot the server in safe mode with all docker/VMs disable, let it run as a basic NAS for a few days, if it still crashes it's likely a hardware problem, if it doesn't start turning on the other services one by one.
  8. Disks appear to be correctly detected by Unraid, if they don't appear in UD you should post in the UD plugin support thread:
  9. Enable the syslog server and post that after a crash, it might catch something.
  10. It should, make sure it's running the latest BIOS, if not it's a board problem, that setting, if implemented correctly, is enough to solve the C-states issue, avoiding the need to completely disabling them.
  11. Move (or copy but then the mover won't move them back, it won't move existing files, you'd need to delete them manually when not needed) using disk paths to avoid issues, e.g. /mnt/disk1/share to /mnt/cache/share, you can also use /mnt/user0/share to /mnt/cache/share, never use /mnt/user/share to /mnt/cache/share. This, as long as the use cache setting is correctly set.
  12. Docker image went read-only, try recreating it, also make sure there's enough space for it.
  13. You can use Unbalance, but first you can explore the disk to see if there's tactfully any data there. Tools -> New config then re-assign the disk as parity and start the array to begin a parity sync, the data on the remaining data disk won't be touched.
  14. Please use the existing plugin support thread:
  15. You don't need to disable C-states, just set the correct power supply idle control.
  16. Most likely, but I'm not familiar with those to help troubleshooting.
  17. BTRFS info (device sdh1): forced readonly Cache pool is going read only, suggest backing it up and re-formatting.
  18. First thing to do is to reboot (with all disks connected) to see the actual damage, pool should come back online and we'll see which disk got disabled.
  19. You can manually, to use the mover you'd need to move the complete share or create a new one for those movies.
×
×
  • Create New...