Jump to content

dlandon

Community Developer
 View Profile  See their activity

  • Posts

    10,398

  • Joined

  • Last visited

  • Days Won

    20

 Content Type 

Everything posted by dlandon

  1. dlandon
    The older color icons should have been public domain, but some may not have been. LT is smart in developing their own and using them with granted permission. This is a lot cleaner from a legal standpoint. Imagine a forced redesign because of some lawyer trying to get royalties for an ownership claim on an icon, plus legal costs. All of you complaining about the design choices need to remember this is a nas with some awesome additional features. It is not mission critical. You manage your storage, VMs, Dockers etc. The color of the icons doesn’t make or break it. If you have an idea for a better look, make the suggestion to LT and then accept their decision.
  2. dlandon
    Changed Status to Closed
  3. dlandon
    Hard to do with all the differing information.
  4. dlandon
    Not enough of a need for the community vs. the effort required to implement. There is also a lack of web UI real estate to add more stuff.
  5. dlandon
    This is one of the reasons I stick around. There are some very talented and knowledgeable people here.
  6. dlandon
    Ok. That will work.
  7. dlandon
    For the installed plugins page yes, but the .page icon will still be set to fa in this case. Menu="Utilities" Title="Unassigned Devices" Icon="unlock-alt" --- Do we need to have a different entry for the new (fa) Icon?
  8. dlandon
    When the array is stopped there are cron entries that could be problematic. When the array is stopped the following is in the crontab and /etc/cron.d/root. # If you don't want the output of a cron job mailed to you, you have to direct # any output to /dev/null. We'll do this here since these jobs should run # properly on a newly installed system. If a script fails, run-parts will # mail a notice to root. # # Run the hourly, daily, weekly, and monthly cron jobs. # Jobs that need different timing may be entered into the crontab as before, # but most really don't need greater granularity than this. If the exact # times of the hourly, daily, weekly, and monthly cron jobs do not suit your # needs, feel free to adjust them. # # Run hourly cron jobs at 47 minutes after the hour: 47 * * * * /usr/bin/run-parts /etc/cron.hourly 1> /dev/null # # Run daily cron jobs at 4:40 every day: 40 4 * * * /usr/bin/run-parts /etc/cron.daily 1> /dev/null # # Run weekly cron jobs at 4:30 on the first day of the week: 30 4 * * 0 /usr/bin/run-parts /etc/cron.weekly 1> /dev/null # # Run monthly cron jobs at 4:20 on the first day of the month: 20 4 1 * * /usr/bin/run-parts /etc/cron.monthly 1> /dev/null # Generated docker monitoring schedule: 10 0 * * 1 /usr/local/emhttp/plugins/dynamix.docker.manager/scripts/dockerupdate.php check &> /dev/null # Generated system monitoring schedule: */1 * * * * /usr/local/emhttp/plugins/dynamix/scripts/monitor &> /dev/null # Generated parity check schedule: 0 9 1 * * /usr/local/sbin/mdcmd check &> /dev/null || : # Generated plugins version check schedule: 10 0 * * * /usr/local/emhttp/plugins/dynamix.plugin.manager/scripts/plugincheck &> /dev/null # Generated unRAID OS update check schedule: 11 0 * * * /usr/local/emhttp/plugins/dynamix.plugin.manager/scripts/unraidcheck &> /dev/null # Generated ssd trim schedule: 30 5 * * * /sbin/fstrim -a -v | logger &> /dev/null I don't know if any of these items running while the array is stopped would cause any issues. If the timing was right during a shutdown, I could see come issues.
  9. dlandon
    How do plugins handle this?
  10. dlandon
    Yes. Could be messy if it doesn't.
  11. dlandon
    Yea, the user can take that risk. Why would someone want to mount anything manually anyway? Doesn't UD handle just about every case of mounting things that is needed? Only thing I can think of that isn't covered is a cloud mount.
  12. dlandon
    Been that way for quite a while. I may have changed it when I took over UD.
  13. dlandon
    Normally not a problem, but is this case the user mounted a disk that was already set up by UD and when he deleted it, the mount got messed up. I really don't think it is good idea regardless.
  14. dlandon
    Nobody said it was your fault. I don't see any bug in UD. The confusion is probably more on the part of Microsoft than UD. They insist on the user and password just to be able to list the shares. Linux computers don't have this restriction for listing the shares. They do insist on credentials for authentication.
  15. dlandon
    I don't understand what you think is wrong with the order. The user and password are above the load shares button.
  16. dlandon
    Ok. I did a little experiment. I've never tried to mount a Windows share. When mounting a Windows share, you have to enter the login user and password just to get it to list the shares and to mount the share.
  17. dlandon
    Do you have password protected sharing turned off on the Windows computers?
  18. dlandon
    Are your Windows computers and Unraid on the same workgroup? Can your Windows computers browse the Unraid shares?
  19. dlandon
    This list is more for convenience than for functionality. Not showing the list would not necessarily keep the remote share from mounting. Try this command and let me know the output. /usr/bin/smbclient -g -L IP -U% 2>/dev/null
  20. dlandon
    Is there an issue with the user login password? Expired?
  21. dlandon
    Are you using Active Directory?
  22. dlandon
    Here are your issues: Feb 12 10:05:59 Shelbyville unassigned.devices: Mount SMB share '//HOMER/G' using SMB3 protocol. Feb 12 10:05:59 Shelbyville kernel: Status code returned 0xc0000072 STATUS_ACCOUNT_DISABLED Feb 12 10:05:59 Shelbyville kernel: CIFS VFS: Send error in SessSetup = -128 Feb 12 10:05:59 Shelbyville kernel: CIFS VFS: cifs_mount failed w/return code = -128 Feb 12 10:05:59 Shelbyville unassigned.devices: SMB3 mount failed: mount error(128): Key has been revoked Refer to the mount.cifs(8) manual page (e.g. man mount.cifs) . Feb 12 10:05:59 Shelbyville unassigned.devices: Mount SMB share '//HOMER/G' using SMB2 protocol. Feb 12 10:05:59 Shelbyville kernel: Status code returned 0xc0000072 STATUS_ACCOUNT_DISABLED Feb 12 10:05:59 Shelbyville kernel: CIFS VFS: Send error in SessSetup = -128 Feb 12 10:05:59 Shelbyville kernel: CIFS VFS: cifs_mount failed w/return code = -128 Feb 12 10:05:59 Shelbyville unassigned.devices: SMB2 mount failed: mount error(128): Key has been revoked Refer to the mount.cifs(8) manual page (e.g. man mount.cifs) . Feb 12 10:05:59 Shelbyville unassigned.devices: Mount SMB share '//HOMER/G' using SMB1 protocol. Feb 12 10:05:59 Shelbyville kernel: CIFS VFS: cifs_mount failed w/return code = -112 Feb 12 10:05:59 Shelbyville unassigned.devices: Mount SMB/NFS command: mount -t cifs -o rw,nounix,iocharset=utf8,_netdev,file_mode=0777,dir_mode=0777,,vers=1.0,username=xxx=******* '//HOMER/G' '/mnt/disks/HOMER_G' Feb 12 10:05:59 Shelbyville unassigned.devices: Mount of '//HOMER/G' failed. Error message: mount error(112): Host is down Refer to the mount.cifs(8) manual page (e.g. man mount.cifs) I have no idea what the "Key has been revoked" means. Possibly a Windows 10 permission issue?
  23. dlandon
    Don't use /mnt/disks/ for anything. UD manages that and can interfere as you found out.
  24. dlandon
    Click on the 'Search for Servers' button, then select the server. Then click on the 'Load Shares' button and you'll see the shares on that PC. User and password are only needed to authenticate access to the share. It is not necessary to show the shares on the PC. You shouldn't have to enter the share manually. Works for me. The ability for UD to see the shares on the PC depends on the Master Browser. It might help to set Unraid as the Master Browser. Settings->SMB->Workgroup Settings Can't help unless you post your diagnostics. Tools->Diagnostics.
  25. dlandon
    @bonienl I saw that one coming.
×
×
  • Create New...