Jump to content

dlandon

Community Developer
  • Posts

    10,397
  • Joined

  • Last visited

  • Days Won

    20

Everything posted by dlandon

  1. Go to Options->System and turn on OPT_USE_AUTH.
  2. UD doesn't ask for the password. Access is controlled by Linux permissions.
  3. I'm not sure where to start to help you. You seem to have a lot if issues with disks: Apr 11 07:34:18 SEDECORE dnsmasq-dhcp[8990]: DHCP, IP range 192.168.122.2 -- 192.168.122.254, lease time 1h Apr 11 07:34:18 SEDECORE dnsmasq-dhcp[8990]: DHCP, sockets bound exclusively to interface virbr0 Apr 11 07:34:18 SEDECORE dnsmasq[8990]: reading /etc/resolv.conf Apr 11 07:34:18 SEDECORE dnsmasq[8990]: using nameserver 71.10.216.1#53 Apr 11 07:34:18 SEDECORE dnsmasq[8990]: using nameserver 71.10.216.2#53 Apr 11 07:34:18 SEDECORE dnsmasq[8990]: using nameserver 192.168.0.1#53 Apr 11 07:34:18 SEDECORE dnsmasq[8990]: read /etc/hosts - 2 addresses Apr 11 07:34:18 SEDECORE dnsmasq[8990]: read /var/lib/libvirt/dnsmasq/default.addnhosts - 0 addresses Apr 11 07:34:18 SEDECORE dnsmasq-dhcp[8990]: read /var/lib/libvirt/dnsmasq/default.hostsfile Apr 11 07:34:18 SEDECORE kernel: virbr0: port 1(virbr0-nic) entered disabled state Apr 11 07:34:18 SEDECORE kernel: L1TF CPU bug present and SMT on, data leak possible. See CVE-2018-3646 and https://www.kernel.org/doc/html/latest/admin-guide/hw-vuln/l1tf.html for details. Apr 11 07:39:22 SEDECORE dhcpcd[2224]: route socket overflowed - learning interface state ### [PREVIOUS LINE REPEATED 1 TIMES] ### Apr 11 07:44:00 SEDECORE root: Fix Common Problems Version 2021.04.10 Apr 11 07:55:06 SEDECORE kernel: isci 0000:05:00.0: sci_remote_device_frame_handler: in wrong state: STP_DEV_IDLE Apr 11 07:55:06 SEDECORE kernel: sas: Enter sas_scsi_recover_host busy: 1 failed: 1 Apr 11 07:55:06 SEDECORE kernel: sas: ata9: end_device-7:2: cmd error handler Apr 11 07:55:06 SEDECORE kernel: sas: ata7: end_device-7:0: dev error handler Apr 11 07:55:06 SEDECORE kernel: sas: ata8: end_device-7:1: dev error handler Apr 11 07:55:06 SEDECORE kernel: sas: ata9: end_device-7:2: dev error handler Apr 11 07:55:06 SEDECORE kernel: sas: ata10: end_device-7:3: dev error handler Apr 11 07:55:06 SEDECORE kernel: sas: --- Exit sas_scsi_recover_host: busy: 0 failed: 1 tries: 1 Apr 11 08:00:32 SEDECORE kernel: neighbour: arp_cache: neighbor table overflow! ### [PREVIOUS LINE REPEATED 9 TIMES] ### Apr 11 08:00:47 SEDECORE dhcpcd[2224]: route socket overflowed - learning interface state ### [PREVIOUS LINE REPEATED 1 TIMES] ### Apr 11 08:04:02 SEDECORE unassigned.devices: Removing configuration '//DS1/Downloads'. Apr 11 08:04:12 SEDECORE kernel: net_ratelimit: 10 callbacks suppressed Apr 11 08:04:12 SEDECORE kernel: neighbour: arp_cache: neighbor table overflow! ### [PREVIOUS LINE REPEATED 2 TIMES] ### Apr 11 08:04:25 SEDECORE dhcpcd[2224]: route socket overflowed - learning interface state ### [PREVIOUS LINE REPEATED 2 TIMES] ### Apr 11 08:14:28 SEDECORE kernel: neighbour: arp_cache: neighbor table overflow! ### [PREVIOUS LINE REPEATED 9 TIMES] ### Apr 11 08:14:33 SEDECORE dhcpcd[2224]: route socket overflowed - learning interface state Apr 11 08:54:34 SEDECORE kernel: isci 0000:05:00.0: sci_remote_device_frame_handler: in wrong state: STP_DEV_IDLE Apr 11 08:54:34 SEDECORE kernel: sas: Enter sas_scsi_recover_host busy: 1 failed: 1 Apr 11 08:54:34 SEDECORE kernel: sas: ata9: end_device-7:2: cmd error handler Apr 11 08:54:34 SEDECORE kernel: sas: ata7: end_device-7:0: dev error handler Apr 11 08:54:34 SEDECORE kernel: sas: ata8: end_device-7:1: dev error handler Apr 11 08:54:34 SEDECORE kernel: sas: ata9: end_device-7:2: dev error handler Apr 11 08:54:34 SEDECORE kernel: sas: ata10: end_device-7:3: dev error handler Apr 11 08:54:34 SEDECORE kernel: sas: --- Exit sas_scsi_recover_host: busy: 0 failed: 1 tries: 1 I am not a network expert, but something doesn't seem right with your network. UD won't turn on the 'Mount' button if the remote server won't respond to a ping. Go to a command line and manually ping the server in question. If you don't get a response, you'll have to figure out why not.
  4. A temporary fix is to install the Enhanced Log plugin and set up a log filter. Go to 'Settings->Enhanced Log Settings' and click on the 'Syslog Filter' tab. Enter the following in the text area: "to getport/addr" Then click 'Apply'. The getport/addr messages will blocked from the log.
  5. Can someone with this issue try the following? Add this line to the /etc/hosts.allow file: ALL: {IP address of remote server} Let me know if it works and if not we can try some other things.
  6. There are several things you are getting wrong. ALL disks mount at /mnt/disks. Remote (SMB and NFS) mounts will mount at /mnt/remotes, or /mnt/disks if the legacy option is enabled. Physical disks always mount at .mnt.disks. UD only mounts disks. It does not have any control over the permissions or r/w access. Move your nvme disk to the Unraid pool and use it from there. The support is better for the things you are trying to do. Based on the error you are seeing, it appears to be a Plex issue transcoding certain file types.
  7. Would probably be best. I'd say your database is corrupted.
  8. I think this issue is related to some remote servers needing to have the version specified when mounting a CIFS mount. I have updated UD and added a setting to possibly help with this issue. Procedure: Update UD plugin. Unmount all SMB remote shares. Go to settings and set 'Specify SMB Version when Mounting Remote Shares?' to 'Yes'. Mount remote SMB shares. Let me know if this takes care of the excessive log messages.
  9. Type 'service mysql start' and troubleshoot the errors. The ZM forum can lend a hand.
  10. If you are using SMB or NFS remote mounts and have issues with used and free showing zero, or excessive strange log messages related to CIFS mounts, be sure you are not using Jumbo frames on your network. It's difficult to set up Jumbo frames on a network because every device on the network must be set up properly. This includes network switches. It s recommended that you do not have Jumbo frames enabled anywhere on your network if you are using CIFS mounts (SMB or NFS).
  11. Linux is having an issue with the disk. UD can't do anything if Linux refuses to mount it.
  12. That's an ownCloud feature and not under my control.
  13. The file system has a problem. You need to take it to a Windows computer and see if it can be sorted out there,
  14. I have no idea what is causing this and a Google search does not present any meaningful information
  15. It is recommended that you do the update manually. Read the second post on the procedure.
×
×
  • Create New...