Jump to content

dlandon

Community Developer
 View Profile  See their activity

  • Posts

    10,395

  • Joined

  • Last visited

  • Days Won

    20

 Content Type 

Everything posted by dlandon

  1. dlandon
    I believe you might have an interface issue. These are the interfaces in your 'testparm' output: interfaces = 192.168.50.200 10.253.0.1 127.0.0.1 Check that these look right. The 192.168.50.200 is your server. The issue might be the application of the interfaces/networking is not taking on first boot. The are networking changes new to 6.12. When this happens go to a command line and do this command: /etc/rc.d/rc.samba restart and see if SMB will work.
  2. dlandon
    UD won't unmount a disk unless done by a user or in a script. Unmounting by no activity is not a good idea. What you should do is unmount the disk in your backup script when it is done. What is you use case? You should be able to handle this in your script.
  3. dlandon
    Start by turning off Multi Channel. I'm still reviewing your diagnostics. EDIT: Also remove the entries in the smb-extra.conf and see if it fixes the mount.
  4. dlandon
    I jsut ran a quick test and it worked for me. Make sure your flash drive doesn't have any errors.
  5. dlandon
    Post diagnostics so I can see more. It's hard to troubleshoot from a log snippet.
  6. dlandon
    That's the way Linux handles an unclean unmount. A reboot is about the only way to fix it. UD can't do anything about that.
  7. dlandon
    No. You'll need to get the Synology to respond to a ping.
  8. dlandon
    Your configuration looks good. I would do the following: Install the cache-dirs plugin and set it up to cache your shares, but not any share set 'Prefer' on your cache. There is no need to cache directory entries on an SSD disk. Be sure to specify what to cache or it will do too much caching. Install the 'File Activity' plugin to see the files being written to your disks and/or shares.
  9. dlandon
    ownCloud uses port 443 for https access. Unraid also uses port 443 as the default. Be sure they don't conflict and that port 443 is passed to ownCloud through your router.
  10. dlandon
    I have mine set with 'Custom: br0' network and a fixed IP address, so I know it can be done. It appears there is an issue with your network. Check your network setting in Settings->Docker. Be sure the 'IPv4 custom network on interface br0:' is set properly and your ownCloud IP address is set in that range.
  11. dlandon
    Post diagnostics.
  12. dlandon
    Be sure to set SMB Sharing in the UD settings to share with SMB the security you want to use. It defaults to disabled. Be sure to set the root share to "Share".
  13. dlandon
    It's not a good idea to add shares the way you have to smb-extra.conf. Smb-extra.conf is intended only for a few global settings. The reason it stopped working with rc8 is probably because of samba changes.
  14. dlandon
    The file type of a UD disk is not determined by UD, Linux makes that determination. I'm not sure how, but Linux is seeing a btrfs disk. So are you wanting to mount it in UD and pass it through to the VM? That's not a good idea as you will get corruption. What is it that you are wanting to do?
  15. dlandon
    Kind of both. I'm looking into how to stop the spin down.
  16. dlandon
    Looks like the Recycle Bin setup is fine on those two shares (Serverfolders and isos). What share are you trying to delete files from?
  17. dlandon
    Show the output of this command: testparm -s
  18. dlandon
    A few things to check: Does it say that the Recycle Bin is running in the upper right side if the Recycle Bin GUI? Do you see deleted files in the Recycle Bin log? Be sure 'Log Deleted FIles' is set to 'Yes'. Deleted files are logged immediately, but may not show in the Shares for up to 5 Minutes if you are refreshing the Recycle Bin in the Background. Only files deleted with SMB show in the Recyce Bin. You cannot delete files in the Unraid File Manager or the Terminal and expect them to show in the Recycle Bin.
  19. dlandon
    As I mentioned earlier, the disk temps are monitored by serial number and not DevX. You can check by looking in the /flash/config/smart-one.cfg file. See if the disk in question is in that file and has the settings you changed. If it does, then you may have found a bug. The problem is you are on 6.9 and you will be asked to upgrade to the latest version before any time will be spent on finding the problem. If I remember correctly, this was an issue in an earlier version and was fixed, but I don't remember the version.
  20. dlandon
    Can you post diagnostics for a closer look?
  21. dlandon
    Unraid tracks the temperature by the Serial Number (Identification), not the DevX because the DevX can change. In your first screen shot, there is no Identification. Did you blank it out? If you didn't, I'm not sure how this happened. I assume you are using UD. Show a screen shot of this disk in UD. Also post your diagnostics.
  22. dlandon
    Post your diagnostics.
  23. dlandon
    Wow, time for new glasses.
  24. dlandon
    The first Dev1 and Dev2 have the same serial numbers. It looks like this is a drive bay with two drives reporting the same serial numbers. Every disk also has the same mount point. Disk sdo is not formatted. What is your setup? Is this a drive bay with 15 disks? Are all these disks supposed to be in one pool?
  25. dlandon
    I don't see any reference in the log to a ntfs disk. I see the unassigned disk is a btrfs disk that is having issues. I don't see where a disk was formatted by UD. UD doesn't change disk formats without a format being initiated by the user. I don't know how you were able to read a btrfs disk in Windows.
×
×
  • Create New...