Jump to content

dlandon

Community Developer
  • Content Count

    5453
  • Joined

  • Last visited

  • Days Won

    6

dlandon last won the day on September 5 2018

dlandon had the most liked content!

Community Reputation

419 Very Good

About dlandon

  • Rank
    Advanced Member
  • Birthday 07/31/1946

Converted

  • Gender
    Male
  • Location
    Cincinnati, Ohio

Recent Profile Visitors

4147 profile views
  1. Setting 'Pass Thru' in UD is not a requirement. It is best to set it though so UD will not be able to mount the disk. Passing through a disk and mounting it with UD will cause corruption.
  2. I was looking for some command time outs and I found several. These help me understand where there are delays in UD that potentially cause slow response.
  3. UD does not do anything with the /root/keyfile in any way except to read it when it needs to mount an encrypted disk. There is an ontion in Unraid to delete that file after the array is started. Check to see if that is enabled. You could also set the password for the disk in UD Settings.
  4. UD checks for the preclear signature on a disk when the UI is loaded. That's how it knows to mark the disk as 'Precleared'. You can stop this by setting the disk as 'Pass Thru'. You will of course get the no file system indicator. When a disk is precleared, there is no file system. This is what '-' indicator means. If UD finds the preclear signature it marks the file system as 'Preclared'. I suspect that the sanning to look for the signature times out at times and fails to find the signature, and marks the disk as having no file system. If you'll post your diagnostics zip I can see if that is the case.
  5. This is generally from a corrupted file on the flash. Remove the /flash/config/plugins/unassigned.devices/*.cfg files and reboot.
  6. You didn't get it quite right. Delete /flash/config/plugins.unassigned.devices/*.cfg, then immediately reboot. There are working copies in memory that will overwrite the ones on the flash unless you reboot right away.
  7. I have been trying to figure out your use case and you seem to want to just explain permissions over and over. I'd like to see if there is another option for you. I'm not a fan of additional UD settings that can be confusing to users and potentially create support issues. You are the first user that has had an issue with this. The "force users = nobody" was added for good reasons. I put a lot of thought into implementing features in UD to be sure the feature applies to the greatest number of users. My goal is to minimize user issues to be sure their experience is positive and limit support issues. One of the downsides of this approach is a potential loss of some features that advanced users might want. You are a newbie and haven't had much experience with the forum. Spend a minute and search the forum for "force user = nobody". You will see a lot of discussion about permission issues. That is why I implemented "force users = nobody". It solved more problems than it created.
  8. I would appreciate it if you would take your intensity level down a notch. I understand you are frustrated because UD dosn't work exactly as you want. There are many users each with different needs and I try to address as many of the needs as I can for everyone and not customize UD for a particular situation. If I provided a check box for every off the wall request in UD, there would not be enough UI space for them all. I didn't explain why the force nobody user was done on UD remote shares because you didn't ask. CIFS mounts are a real can of worms. There are three diferent versions of the SMB protocol, one of which is becoming obsolete. There are two levels of security. Each host seems to have its own way of doing things which makes it a bit difficult to manage with UD. Some older servers only support SMB v1. Some require different levels of security for each version. Permissions are handled by the host and there have been issues in the past with access to a remote share without the force nobody parameter in the samba config file. That's why it was added. I guess I am a bit confused as to why you are mounting a remote SMB share only to then share it again on Unraid and then demand UD do the permissions as you desire. Why not access the remote share directly and set permissions on the host as you like?
  9. New release of UD. Highlights: Don't allow unmounting a disk that was not mounted by UD. If you manually mount an unassigned disk at a mount point other than /mnt/disks/, UD will not be able to unmount it. Change disk size query to try to keep from spinning up disks. Cut down on tmp file accesses. Fix a situation where permission settings from UD Settings would not update the shares. Some more code cleanup.
  10. Execute the following command and see if the disk spins up: /bin/lsblk -nb -o size /dev/sdX