Jump to content

brianieface

Members
  • Posts

    2
  • Joined

  • Last visited

Posts posted by brianieface

  1. On 3/13/2013 at 2:23 AM, trurl said:

    unRAID has a RAM filesystem where all of its operating system files are kept. When unRAID boots it unpacks all of its operating system files from bzroot and keeps them in RAM. Since bzroot is not altered to reflect any changes to these operating system files, they will all be restored to the original from bzroot when you reboot. This is why anything stored in any of the usual linux operating system folders does not survive a reboot.

     

    In general, anything not in /boot (your flash drive) or /mnt (actual disks or shares on those disks) is in RAM.  Anything stored in these locations will persist after reboot.

     

    This is why some people add code to the go script to alter operating system files every time they reboot. I have code in my go script which alters /etc for example.

     

    You can put those packages in /boot/extra and they will be automatically installed on boot.

     

    Add the other script to the script in /boot/config/go (like I have just done. Thanks for this)

     

     

     

     

    Thank you so much...  !  Beer++

     

     

  2.  

    Hello... I _think_ I may have your answer.  If you're like me and you run on an AMD platform, this is due to the c-states setting in your bios.   My problem got so bad I had a crash at least once a day.

     

    The fix for me?  I setup a virtual windows machine, and leave it running.  Am on day 15 now of no crashes.

     

    Hope this helps...

     

     

    B.

×
×
  • Create New...