Jump to content

trurl

Moderators
 View Profile  See their activity

  • Content Count

    21445

  • Joined

  • Last visited

  • Days Won

    50

Posts posted by trurl

  1. Posted

    There isn't often a need to do things at the command line, and you mostly shouldn't even be messing around with any paths except those for your disks and user shares.

     

    What are you trying to do?

  6. Posted

    29 minutes ago, terratex said:

    Thanks for the support, I found the problem. It was SDA1 Flash Drive. It was in the Only Write mode due to an error.

     

    Feb 20 11:10:50 Tower kernel: FAT-fs (sda1): error, corrupted directory (invalid entries)

    Feb 20 11:10:50 Tower kernel: FAT-fs (sda1): Filesystem has been set read-only

    Are you booting from a USB2 port? Recommended.

  8. Posted

    1 hour ago, Genide said:

    I've modified the existing lychee.subdomain.conf file to include a port number. 

    
        proxy_pass http://$upstream_lychee:3080;

     

     

    I don't think you need that port number. I don't have it and mine is working. 

            proxy_pass http://$upstream_lychee;

     

     

  11. Posted

    39 minutes ago, vanrhyn said:

    I realize that some are small, but I have space in the server case

    Each additional disk is an additional point of failure. If you don't need the capacity of these small disks don't use them. Just wait until you do need capacity and install larger disks.

     

    Also, every disk in the parity array is important. In order to reliably rebuild every bit of a failed disk, every bit of parity PLUS ALL remaining disks must be reliably read. I recommend testing all of these disks before trusting them in your server. I would just leave out the 2.5 inch disks completely.

     

    So none of these disks are SSDs?

     

    As for your question on backup, yes Unassigned Devices can be used to make backups. You must always make sure you have another copy of anything important and irreplaceable. Parity is not a substitute for backups. If you don't have much you consider worth backing up then those small disks might work well for that.

  12. Posted

    Are these just a bunch of disks you already have? 

     

    How much capacity do you need? 

     

    Some of those are too small to waste a slot or port on, unless some are SSDs for the cache pool. 

     

     

  14. Posted

    38 minutes ago, JimmyBar89 said:

    all my docker containers have lost their settings

    Do you mean it doesn't remember the mappings and other settings from the Add/Edit Docker page? Or do you mean each of the applications doesn't remember its settings?

     

    Go to Tools-diagnostics and attach the complete Diagnostics zip file to your NEXT post. 

  18. Posted

    The Unraid OS, with all of its usual Linux OS folders, is in RAM. It is loaded into RAM from the archives on Flash.

     

    You will have to run a script to make any changes to those folders after each boot. The User Scripts plugin will let you set that up.

  19. Posted

    17 hours ago, dezai said:

    BTRFS cristical (device md2) ...

     

    At first i thought it is the parity drive, so i removed the parity drive but the problem is the same.

    I also diabled the cache array - same problem.

    For future reference, md2 is referring specifically to the disk assigned as disk2 in the parity array, so there was no reason to think doing anything with parity or cache would help.

  20. Posted

    30 minutes ago, Rallysports said:

    To resync the parity do I just need to wait for the "Read Check" to finish and then there will be an option to resync or is it more in depth?

    Cancel the pointless read check. To rebuild a disk to itself, whether parity or data, stop array, unassign disk to be rebuilt, start, stop again, reassign disk to be rebuilt, start again to begin rebuild.

     

     

  22. Posted

    20 minutes ago, OjRacer said:

    I presumed data would go from the hard drive directly to my Plex machine

    All data goes through memory. That doesn't necessarily mean entire files are ever contained completely in memory. BRiT's point was that if you had more memory, more could be buffered and that would be faster than moving it to cache first. Whichever disk it is on is still going to require the data to be read into memory before it can be used for anything.