itimpi

Moderators
  • Posts

    19352
  • Joined

  • Last visited

  • Days Won

    53

Community Answers

  1. itimpi's post in FCP Found this after what I thought was a hung reboot was marked as the answer   
    I would expect that you can just delete the file and it would be recreated.
  2. itimpi's post in GPU Transcode to RAM was marked as the answer   
    With those settings at the container level, you want to tell Plex to transcode to /transcode.   The docker system will then redirect that to /tmp/plex_transcode at the Unraid level.
  3. itimpi's post in do i have to create at least one disk in array even if i have pool was marked as the answer   
    Unraid currently requires at least one drive in the array.   If you do not intend to use it to store anything a workaround is to use an old flash drive.
  4. itimpi's post in Parity drive never spins down was marked as the answer   
    You should:
    Disable the Docker service under settings (it needs to be disabled to stop it keeping files open) Run mover to transfer the contents of the 'system' share to the cache (optional) When that completes you might want to confirm that there is now no sign of the 'system' share on disk1  Set the secondary storage option for the 'system' to None Enable the option to use Exclusive shares under Settings->Global Share settings to get the performance advantage of bypassing the Unraid Fuse layer  Reenable the Docker service Once this is done then docker will not be keeping disk1 and parity spun up all the time.
  5. itimpi's post in Help identify why SDD keeps spinning up was marked as the answer   
    Did not spot anything obvious either!
     
    It might be worth installing the File Activity plugin to see if that gives a clue as to what is accessing the drive.
  6. itimpi's post in Invalid folder users contained within /mnt was marked as the answer   
    It is most likely to be something you have configured in a docker container.
  7. itimpi's post in First Time Setup was marked as the answer   
    The reason that 32GB is mentioned is that the flash drive needs to be formatted as FAT32 and Windows does not support as standard doing this on drives over 32GB.   Also Unraid only needs something like 1-2GB on the flash drive so large drives have lots of space that will never be used.
  8. itimpi's post in Dockers wont restart, doesnt do anything when clicking was marked as the answer   
    Do you by any chance have the Docker Folder plugin installed?   If so you should remove it (it has been replaced by Folder View).
     
    if it is not that you are likely to get better informed feedback if you attach your system’s diagnostics zip file to your next post in this thread.
  9. itimpi's post in Missing Data after attempt at drive replacement was marked as the answer   
    More often than not when a drive is disabled (because a write failed) it was due to an external factor and the drive is physically OK.
  10. itimpi's post in Possible failing drive concerns and questions (SOLVED) was marked as the answer   
    Your screen shot shows you ran a correcting parity check which made the parity agree with the data drives.  Had you by any chance had an unclean shutdown earlier - they would normally cause a few sync errors.   You should then not expect any further errors on the next check
     
    Was this a manually initiated check or a scheduled one?   Just asking as we normally recommend that scheduled checks are set to be non-correcting so that faulty hardware will not end up corrupting parity before you are aware of any issues.
  11. itimpi's post in (SOLVED) "Unmountable: Unsupported or no file system" after unclean shutdown was marked as the answer   
    That output suggests there is some level of corruption.
     
    You ran with the -n option (the no modify flag) so nothing was fixed.    To actually fix it you need to run without -n (and if it asks for it add -L). 
     
    After that you can restart the array in normal mode to see if the drive now mounts.   I expect it will, so you then need to look for a lost+found folder which is where the repair process puts any folders/files for which it could not find the directory entry giving the correct name and gives them cryptic names instead.  Not having this folder is a good sign that the repair went perfectly.   However if you DO have that folder you have to sort its contents out manually or restore any missing files from backups (which is normally easiest if your backups are good enough).
  12. itimpi's post in mkdir folder in ssh is creating shares. was marked as the answer   
    If you have User Shares enabled then it is normal for every top level folder on a drive to automatically become a User Share with default settings and Unraid has always worked like this. 
  13. itimpi's post in Finding Mounted USB Drive in Krusader. was marked as the answer   
    The only mapping you have is to /mnt/user which is where User Shares are mounted.   Local drives mounted by UD appear under  /mnt/disks and remote shares under /mnt/remote.   If you want Krusader to be able to access either of these then you need to add volume mappings to support this.
  14. itimpi's post in Share Flash Drive via SMB was marked as the answer   
    Yes.
     
    Click on the boot device on the Main tab and you can then set the SMB security setting for exporting it as a network share with the level of security you want to apply.
  15. itimpi's post in Unraid 6.12.6 Keeps crashing while computer remains on was marked as the answer   
    The syslog shows that you have docker set to use macvlan AND have bridging enabled on eth0.  As mentioned in the Release Notes this combination is know to cause system crashes.    You ether need to disable bridging on eth0 or switch docker to using ipvlan networking.
     
  16. itimpi's post in Repeating errors in logs was marked as the answer   
    I think it should be 0 3 * * *
    Note that space is a field separator so there should be 4 spaces between the 5 fields.
  17. itimpi's post in Replace UNRAID array and parity with 2 larger drives was marked as the answer   
    Both the links you posted go to obsolete documentation.  The online documentation is accessible via the ‘Manual’ link at the bottom of the GUI or the DOCS link at the top of each forum page. The Unraid OS->Manual section in particular covers most features of the current Unraid release.
     
    The section on replacing disks is here.   You will need to upgrade parity first as no data drive can be larger than the smallest parity drive.
  18. itimpi's post in [6.12.6] Unable to access SMB Shares from any device was marked as the answer   
    Have changed the SMB Export option for the shares you want visible on the network?   The default is No which means they are not visible on the network.
  19. itimpi's post in New unraid machine was marked as the answer   
    You could use a Trial licence to build out the new machine.
     
    On completion you could then copy the 'config' folder for the new machine (except for the trial licence key file) to the flash drive with the Pro licence to transfer the settings of the new machine to it.
  20. itimpi's post in CPU Warnings, when using Docker macvlan and usb devices was marked as the answer   
    The Release Notes mention that if you want to use macvlan then you should disable bridging on eth0 to avoid crashes that can eventually bring down the server.   According to the diagnostics you still have it enabled.
  21. itimpi's post in No space left on device was marked as the answer   
    The 61% relates to the amount of space used in the docker.img file.
     
    You should post your system's diagnostics zip file in your next post in this thread to get more informed feedback.  It is always a good idea to post this if your question might involve us seeing how you have things set up or to look at recent logs.
  22. itimpi's post in Share data set to use pool cache_dwnld, but files / folders exist on the cache_large pool was marked as the answer   
    That means that you almost certainly feel foul of the behaviour described in the Caution in this of the online documentation accessible via the Manual link at the bottom of the Unraid GUI. 
     
    If you had used something like Dynamix File Manager plugin to do this it would have protected you from this problem as it always uses a copy/delete strategy for moving files.
     
    You can use Dynamix File Manager to delete the empty folders.
  23. itimpi's post in Periodic CPU spikes when array is spun up - Unraid 6.12.6 was marked as the answer   
    It could be the Cache Dirs plugin which would keep issuing 'find' commands to try and keep directory entries in RAM.    It is a good idea to configure that plugin to only scan folders that need it as it does not work very well if there are too many files/folders in the ones it is scanning.
  24. itimpi's post in var.log filling and mac vlan errors was marked as the answer   
    That shows that the Connect plugin is the culprit.    The most recent update to that plugin fixes the excessive logging issue, but you will still need to reboot the server to clear the log space used.
  25. itimpi's post in Changed motherboard now array not showing was marked as the answer   
    I think the problem is all the disks are now showing:
    Formatted with type 2 protection I do not know if this can be removed and keep the data on the drives.