Jump to content


  • Content Count

  • Joined

  • Last visited

  • Days Won


trurl last won the day on February 5

trurl had the most liked content!

Community Reputation

530 Guru


About trurl

  • Rank
  • Birthday 12/26/1954


  • Gender
  • Location
    North Carolina
  • Personal Text

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. trurl

    Syslog errors

    You have a problem with your memory. Try reseating it.
  2. trurl

    Syslog errors

    Post your Diagnostics too
  3. trurl

    [Support] Linuxserver.io - Nextcloud

    The Console option gives you a bash command line inside the container, so that is all you need.,
  4. trurl

    Unraid Unmenu not working anymore

    Try booting from another USB port, preferably USB2.
  5. trurl

    Parity check running Every night

    Assuming you updated Unraid, it might be necessary to make a change to the schedule just to get the old bad schedule cleared.
  6. trurl

    Unraid OS version 6.7.0-rc4 available

    Since that plugin installs a custom build of Unraid your report doesn't belong here. Try to reproduce on the actual Unraid release this report thread is about.
  7. trurl

    Terminal Permission denied

    It would only be necessary to add if you were NOT logged in as root since normally root is the only user with access to the command line.
  8. trurl

    Server Reboots Unraid

    Still don't see anything. You aren't trying to overclock are you?
  9. trurl

    All shares set to cache=yes

  10. trurl

    Strange problems with newly added drive

    The disk isn't producing a SMART report in those diagnostics. How is it connected? Also, a lot of UPS disconnections happening in your syslog. Any idea why?
  11. trurl

    Parity scan grinds server to halt

    Why are you doing a parity check anyway? Most people just schedule a parity check to run once a month. Unraid parity is realtime so should always be correct. A parity check is just intended to be an occasional test that parity is still correct.
  12. trurl

    Parity scan grinds server to halt

    Parity check requires reading all the disks. Parity check and any other process trying to access those disks will be competing with each other, with the result that the disks often have to "thrash", moving the read/write heads and waiting for the disk to spin, as it seeks the sectors one process is using, then seeks the sectors the other process is using, then etc.
  13. That problem is sort of the compliment of the other problem being mentioned earlier, mixing disks and user shares when moving/copying. If you move/copy from a user share to a disk, or from a disk to a user share, Linux doesn't realize that the source path and the destination path might actually be the same file. So it tries to overwrite the file it is trying to read.
  14. Linux sees all user shares as being mounted at /mnt/user. So when you try to move from one user share to another, Linux will see they are on the same mount, and instead of copying from source to destination and then deleting from source, as it would if you were moving between disks, it will instead just rename to a different path. This is instantaneous but it stays on the same disk, not the result you wanted. You will have to do the move in 2 steps. Copy from source to destination. That will make another copy that follows the user share settings of the destination. Then delete it from the source.