itimpi

Moderators
 View Profile  See their activity

  • Posts

    19672

  • Joined

  • Last visited

  • Days Won

    54

 Content Type 

Everything posted by itimpi

  1. itimpi
    I am virtually certain that the step you missed the first time around was to make sure that disk6 was not assigned after New Config was run as restricting which disks a share can use should have no effect. Regardless at least it appears you are now in the state you want
  2. itimpi
    Almost certainly this where the router is probing Unraid.
  3. itimpi
    Not quite - you have missed out the UD mount point under /mnt/disks (so it should be something like "/mnt/disks/UDmountpoint/appdata/Plex-Media-Server" )
  4. itimpi
    Unraid will not automatically move existing files when you change the pool associated with a share. The easiest (and most efficient) thing to do is to move them manually to the correct location. Alternatively you can exploit mover as described here in the online documentation that can be accessed via the Manual link at the bottom of the GUI
  5. itimpi
    If you have started with a clean system then the default shares should be automatically created when you enable the docker and VM services. Any other shares will require Manual action from you.
  6. itimpi
    Does it work if you omit the ‘login’ part? It should not be necessary.
  7. itimpi
    The initial boot process is controlled by the BIOS so it is up to the BIOS to decide to boot off the Unraid USB and there is nothing that Unraid can do if the BIOS won’t select the Unraid flash drive as its boot device.
  8. itimpi
    According to the screenshot the SSD WAS left as assigned so Unraid now thinks it is missing.
  9. itimpi
    Level 2 would be correct for your example as you only want to allow the Ozark level to exist on multiple drives. Note that there is a bug if you are running 6.10.0 rc2 where changes to share settings do not seem to take effect until you restart the array. The change only applies to new files. It would take Manual action to sort out any files that are already on the wrong disk.
  10. itimpi
    When you ran the New Config tool did you make sure that you no longer had the SSD assigned to the array before you tried to start the array (committing the assignments).
  11. itimpi
    It is also worth doing a full power-cycle of the server as If a drive dropped offline this can sometime bring it back. If it does then the diagnostics with the array started will help with identifying the issue.
  12. itimpi
    You would also need to reformat the drives as described here in the online documentations accessible via the ‘Manual’ link at the bottom of the GUI. By default Unraid will leave intact data on drives previously used by Unraid.
  13. itimpi
    You can do this via the User Scripts plugin using the ‘reboot’ command. This is equivalent to hitting the Reboot button on the Main tab, so you should test that you actually DO get a graceful reboot (in case there is something running that is preventing a graceful reboot).
  14. itimpi
    Do you know how you got into this situation? It looks like a copy or move was done manually at some point that went wrong?
  15. itimpi
    It all depends on what you mean by ‘root’ in in an earlier post. The Share name counts as one level, so if you meant root to refer to the Share name then you would need a value of 4 to allow folder3 to be on multiple drives. If you meant folder1 to be the share name then you would need a value of 3.
  16. itimpi
    With a Split level of 2 anything starting at folder2 will be constrained to the disk where any folder at the folder2 level is first created. In other words only the share/folder1 can exist on multiple drives.
  17. itimpi
    You have a share anonymised as S—f with a Split Level setting of 2. It is possible that this is constraining which disks can be used by this share depending on the full path of the files you are trying to put into it. it is always worth remembering that Split Level always wins any contention between share settings for which drives to use, so it is always one to check out first. if it is not that perhaps you can give the exact path of files that are not being distributed across drives as expected.
  18. itimpi
    Probably due to the settings on your shares. You are likely to get better informed feedback if you post your system’s diagnostics zip file.
  19. itimpi
    Once a disk is disabled (which it would be if removed with Unraid running) it has to be rebuilt to get it back into use. Not quite sure what you then did - did you follow the procedure documented here?
  20. itimpi
    You could use Tools->New Config and simply assign the nvme to a pool and if it is set for the same file system as it is using currently then it will be picked up with data intact. Note that the default for array drives is xfs while for pools it is btrfs (and multi-disk pools MUST be btrfs). Most people use a pool for dockers and VMs so that is definitely not an issue. Typically the array is used for storing large files (e.g video) or backups which do not fit onto a pool.
  21. itimpi
    Handling of unmountable disks is covered here in the online documentations accessible via the ‘Manual’ link at the bottom of the GUI. Unraid does not care about the sdX type designations which are unpredictably subject to change between boots - instead it identifies disk by their serial number.
  22. itimpi
    The diagnostics are a single zip file that contains all the files you posted. Please post that instead of the individual files as it is MUCH easier to work with - so much so that most people will not even look at them when posted as individual files.
  23. itimpi
    Most people prefer to use SSD’s in pool/cache scenarios for their increased performance. This is particularily the case when running VMs or Docker Containers. as to mover, without knowing more about what problems it caused you it is difficult to give a constructive answer.
  24. itimpi

    Kernel Panic

    itimpi replied to Sherk's topic in General Support

    Macvlan panics are a known issue with docker containers that use custom IP’s. You could try upgrading to 6.10.0 rc2 and then change any such containers to use Iplan instead
  25. 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.