itimpi

Members
  • Content count

    4859
  • Joined

  • Last visited

Community Reputation

19 Good

About itimpi

  • Rank
    Advanced Member
  • Birthday 06/10/50

Converted

  • Gender
    Male
  • Location
    United Kingdom
  1. I would check the fans and the power supply. Sounds as if the system is being shutdown by the BIOS rather than unRAID.
  2. I strongly suspect that you have your docker configured incorrectly. There is almost certainly a configuration option in the docker that allows you to specify what permissions it should set on files.
  3. Have you made sure that the floppy drive is disabled at the BIOS level?
  4. That is not normal behaviour of unRAID as far as I know. It is certainly not an issue that anyone else has ever reported.
  5. I think you may be getting mixed up with the 6.4 release that is expected to go into beta soon.
  6. Not sure where you read that recommendation - it does not apply to unRAID. The basic NAS functionality runs in about 2GB of RAM. If you are going to use dockers then you probably want to have something like 4-8GB. If you then want `VMs as well you need to add in the RAM requirements of the maximum number of VMs you are going to use simultaneously. In terms of whether you buy ECC RAM that is really up to you - many users run without it although some say that once you are going for server grade hardware then using ECC RAM makes sense.
  7. UnRAID is an OS based on Linux. However it boots from the USB drive (which also acts as the license key verifier) and unpacks itself into RAM and subsequently runs from RAM. After the initial boot the only use of the USB stick is for storing configuration information. There is therefore no pre-requisite in terms of pre-installed software - you just need to set up the USB stick according to the instructions on the Limetech site.
  8. You can always try a 'shutdown' command from the CLI level. I would have thought that should abort the preclear but have not tried it myself to be sure. Since successfully shutting down will abort the preclear and mean that you need to start it again from the beginning after the reboot (assuming you still want to do it) you may want to leave it running. Not sure how far through the preclear you already are?
  9. It is worth noting that ALL the plugin update options both download and install the update. This tends to be standard behaviour throughout the unRAID GUI. it is almost certain the sync will not finish with a preclear running. The whole idea of a 'sync' is to flush all disk buffers and the preclear is continually filling them up again.
  10. The syncing normally only takes a few seconds on a quiescent unRAID system. However if there is a lot of disk activity going on then the time can be a bit indeterminate as continual writing can significantly delay the sync completing. however, once that point in the update process has been reached then the files have in theory been successfully unpacked and written. If you can tidily stop the array then a reboot should come up in the new version. if the update has failed for any reason you can always do a manual upgrade by downloading the zip file from the Limetech site and then replace the bz* files on the unRAID USB stick with the ones from the zip.
  11. The big advantage of zeroing the disk before adding it as an active array drive is that you remain protected the whole time. If parity was rebuilt instead then you would be unprotected until the parity rebuild finished. There is also the side-effect that at you do a level of confidence check on the new drive before using it to store data.
  12. Never seen such a plugin. it would probably be quite easy to run a script daily (using the User Scripts plugin) based on the 'find' command that listed details of all files that have changed in the last day. Whether that would give you the level of detail you want I have no idea
  13. If you click on the diskX name in the Main Tab then you can set custom values for that drive that over-ride the global values.
  14. This is not true RAID-1 where you end up with drives mirrored. It is a BTRFS specific implementation which simply ensures that all data resides on at least 2 different drives so that recovery is possible after a drive failure.
  15. I believe there is an issue with the GUI if you are running a preclear when you try to stop the array. When the preclear finishes the GUI comes back to life.
Copyright © 2005-2017 Lime Technology, Inc. unRAIDĀ® is a registered trademark of Lime Technology, Inc.