Jump to content

JorgeB

Moderators
  • Posts

    67,603
  • Joined

  • Last visited

  • Days Won

    707

Everything posted by JorgeB

  1. Please post the diagnostics: Tools -> Diagnostics
  2. No, but much more than the continuous writes reported by iotop would generate, check SSDs TBW then let it run for 24H without any downloading, then check again.
  3. Parity1 is still checked, and corrected if there are errors.
  4. ASM1166 is an Asmedia 6 port controller, and works fine with Unraid.
  5. Any continuous writes should be in there, at least they were for all users with that issue, including myself, do you do any downloading/unpacking to the cache pool?
  6. Not 100% valid. Disk is showing some SMART issues, but these errors look more like a connection problem, replace the cables/slot and try again.
  7. That's from 3 Hours? It shows a total of less than 2GiB. That's very little, something else must be doing most of the writing.
  8. https://forums.unraid.net/bug-reports/stable-releases/691-setting-warningcritical-temperature-in-smart-settings-not-possible-r1376/?do=findComment&comment=13795
  9. 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.
  10. JorgeB

    SAS SSD

    I use normal consumer SSDs for my small array, Samsung 860 EVO for data and a WD Black NVMe device for parity, most other users I've seen using SSDs also use consumer models. Cache device is always optional.
  11. Unraid parity is used to rebuild a disable/missing device, formatting is never part of a rebuild, to test you'd need to remove the USB device and then rebuild.
  12. Disk looks fine for now, just keep monitoring.
  13. Looks like it is: SMART overall-health self-assessment test result: FAILED! - available spare has fallen below threshold - media has been placed in read only mode You can try mounting in read-only mode, if it works you can copy the data.
  14. Unraid agora suporta pools múltiplas, é possível ter duas pools com um NVMe cada, se ambos forem adicionadas na mesma pool por defeito fica em raid1, mas é possível alterar para raid0 ou single profile para utilizar a capacidade total de ambos, nesse caso ficando sem redundância.
  15. Tools -> New config Keep all assignments, then re-assign old data disk and start array to begin parity sync.
  16. JorgeB

    SAS SSD

    This is old, you can use SSDs, just be aware that they can't be trimmed for now, so write performance might degrade over time, especially on cheaper models.
  17. There's multiple segfaulting apps, start by running memtest.
  18. It shouldn't, but next time you should attempt to fix the filesystem on the emulate disk before rebuilding, just in case it isn't. Let it finish, you can still do a new config in the end if needed.
  19. You need to run a filesystem check on disk9, after it's fixed reboot, enable this and post that log after a crash.
  20. Sim, normalmente usam-se as partilhas do utilizador, cada partilha pode incluir um ou mais discos, também é possível partilhar cada disco individualmente, mas para a maior parte das pessoas as partilhas de utilizador são o recomendado.
  21. Stop array, unassign one or both parity drives, start array.
  22. 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.
×
×
  • Create New...