itimpi

Moderators
 View Profile  See their activity

  • Posts

    19673

  • Joined

  • Last visited

  • Days Won

    54

 Content Type 

Everything posted by itimpi

  1. itimpi
    Download the ZIP for the release and then extract all the bz* type files for the release overwriting the ones on the flash drive.
  2. itimpi
    You probably need a later Unraid release (e.g. 6.10.0 rc2) to have a driver for the NIC in that board.
  3. itimpi
    One option that some people use is to use a small USB stick as the only array drive (with no data being stored on it) and then set up the SSD as a pool device. This meets the requirement that Unraid must have at least 1 drive assigned to the main array before it can start up properly, and pool devices CAN be trimmed.
  4. itimpi
    You do NOT have the files mirrored - they are simply different views of the same files. Usef Shares provide an aggravated view of files within a top level folder on all array and pool drives. You might want to read the online documentations accessible via the ‘Manual’ link at the bottom of the GUI to find out more.
  5. itimpi
    The sentiment is correct but that is not one of my plugins
  6. itimpi
    They do not count as long as they are not plugged at the point where the array starts. If they are plugged in at that point they DO count. Once the array is started then removable drives can be plugged in without problems (at least until the next array start). In practice many people like to have a licence level which means they can leave such drives plugged in as it is more convenient to not to have to unplug them to be able to start the array, but it is up to the user to make a decision on this.
  7. itimpi
    From the command line it would be /boot/config
  8. itimpi
    If you are ta;king about the sdX type designations then Unraid has no control over those. They are assigned dynamically at the Linux level during the boot process as Linux recognises the drives and are subject to change on any boot due to slight variations in timing. In practice they tend to remain constant between boots but you should never rely on that.
  9. itimpi
    According to your syslog it look like a couple of disks had connection problems, and then disk11 dropped offline, and later reconnected with a different device ID so it now showing up under Unassigned Devices (Unraid cannot is not hot-plug aware for array devices and cannot handle this so it thinks it has failed). As was mentioned previously you need to carefully check the cabling (both power and SATA) to make sure all cables are properly seated. Also are you sure your power supply is up to handling all the drives you now have connected?
  10. itimpi
    It could be worth hitting the Stop option and time how long it takes for the array to be successfully stopped. The timeout needs to be at least as long as that plus a safety margin. at that point try a reboot. If you still get an unclean shutdown detected, then this might indicate an issue with updating the flash drive to say the array was successfully stopped before the reboot.
  11. itimpi
    It must have been online during the boot-tocess, but it looks as if it may have now dropped offline since none of the expected contents are showing.
  12. itimpi
    It might be worth using the ‘df’ command to check that the flash drive is mounted at /boot? The messages you give suggest that it is either not online, or has problems.
  13. itimpi
    When using a custom IP for the container I do not think you can change the port used it would be up to the person who provides the container to provide a mechanism for changing the port.
  14. itimpi
    All the configuration information was saved in the config folder on the flash drive and if you have a backup of that you can restore settings.
  15. itimpi
    You can use the procedure documented here in the online documentation accessible via the ‘Manual’ link at the bottom of the HUI.
  16. itimpi
    Any suggestions for improving the wording in the documentation that you would have found less confusing are always welcomed.
  17. itimpi
    Only means new files are created on the cache, but any files for the share on the array are left there. Use Prefer to cause files to be moved from array to cache. Once all files are on the cache you can (optionally) change it to Only or simply leave it at Prefer.
  18. itimpi
    Setting it to Yes means you want it to be moved to the array when mover runs. Use the Help built into the GUI to see how the settings for this value work or read the online documentation about this setting.
  19. itimpi
    You always need backups of anything important just for this type of issue. The Linux 'files' command can be useful if you want to put the effort into sorting out the Lost+Found folder (as opposed to restoring from backups) as it will at least give you the content type of files whose names were lost.
  20. itimpi
    You do realise that any files for the appdata share that are on the array will be left there as mover ignores any shares with the Only setting? If you want files to be moved from array to the cache drive you need the Prefer setting.
  21. itimpi
    Even if you do not use any of its features, it might be worth installing the Parity Check Tuning plugin as that will start enhancing the Parity History entries with the type of check that was run.
  22. itimpi
    Yes. Unraid is quite happy for you leave intermediate slots unpopulated.
  23. itimpi
    The procedure works for removing the drive even with Dual Purity as long as you do not subsequently reorder the remaining drives.
  24. itimpi
    No - I think that will be 30K If you click on the field name in the GUI it will display the help text that gives you the suffixes you can use.
  25. itimpi
    I think I misread the post and it is a pool device - sorry about that It might be worth checking that there are no files directly under / that should not be there? Cannot see from the 'df' output if this could be the case as it only shows mount points. You might also want to check if any other folders that are not mount points and are located in RAM appear unexpectedly large (e.g. du -sh /tmp) .