trurl

Moderators
  • Posts

    43866
  • Joined

  • Last visited

  • Days Won

    137

Posts posted by trurl

  1. 9 minutes ago, MrCrispy said:

    even standard SATA has much higher write speeds. There are posts here where people have done plenty of tests and the conclusion was the smb and FUSE in unraid was to blame, without that they got much higher speeds, without using any cache.

    Realtime parity updates are the reason writes to the array cannot be as fast as SATA or even HDD speeds.

     

    https://docs.unraid.net/unraid-os/manual/storage-management/#array-write-modes

     

    And also the reason Unraid can allow different sized disks in the array.

     

  2. Unrelated, your domains and system shares have files on the array.

     

    Ideally, appdata, domains, and system shares would have all files on a fast pool with nothing on the array, so Dockers/VMs will perform better, and so array disks can spin down since these files are always open.

     

    Looks like you had your docker.img set to 50G before you switched it to a docker folder. Were you having problems filling it? The usual cause of filling docker.img is an application writing to a path that isn't mapped. Docker images shouldn't be growing.

  3. Unclean shutdown means that Unraid thinks the array was not stopped before the server was shut down or rebooted.

     

    Unclean shutdowns happen when Unraid can't write the array started/stopped status to flash. This can be because shutdown happens before the array has been stopped, or because flash can't be written.

     

    Unclean shutdown always happens due to how things are shutdown and are detected on boot up. The consequence is a parity check when the array is first started after booting.

     

    Changing things will not cause this, unless you change the timeouts related to shutdown, or unless it causes your flash drive to become read-only.

     

    Here is the sticky at the top of this same subforum which discusses the timeouts.