dlandon

Check your log when you have issues for a quicker answer: Apr 9 07:06:52 Tower unassigned.devices: Mount of '//192.168.1.13/storj' failed. Error message: 'mount error(13): Permission denied Refer to the mount.cifs(8) manual page (e.g. man mount.cifs) and kernel log messages (dmesg) ' Your credentials are a problem. Try to stay away from special characters.

The 'Mount' buton is grayed out because UD does not think the remote server is on-line. UD tests the server by sending a 'ping'. Your remote server must be configured to respond to a ping. This is probably a configurable setting on the remote server.

Show a screen shot of the UD page.

Mounts are all logged. I haven't seen in your log any attempt to auto mount or manual mount - click the 'Mount' button to manual mount. Auto mount only applies when the server is started manually or rebooted.

That is from a delete of the remote share, not an attempt to mount or unmount the share. From the log it is/was not set to auto mount: Apr 8 15:00:44 Tower unassigned.devices: Remote SMB/NFS mount '//192.168.1.13/storj' is not set to auto mount and will not be mounted. I don't see in the log any attempt to try to mount the share. @Squid you know the routine. UD runs through the different SMB version mounts until the share mounts. I see none of that in the log

UD doesn't see a file system. Check the disk in another system.

You don't need UD plus. The file system is not being recognized by UD. Are you sure the disk is formatted? The device is sda. This implies that the disk was connected when the server was rebooted. Disconnect the disk, reboot the server, then plug the disk back in. Don't leave it connected when you reboot the server.

UD Plus is not required to mount an ext4 disk. Remove the preclear plugin and see if the disk file system shows.

Please update to the latest version of UD. Then do the following. Your smb-extra.conf file is this: #unassigned_devices_start #unassigned_devices_end include = /etc/samba/unassigned-shares/HEADLESS_media.conf #vfs_recycle_start #Recycle bin configuration [global] syslog only = Yes log level = 0 vfs:0 #vfs_recycle_end Please change to this: #vfs_recycle_start #Recycle bin configuration [global] syslog only = No log level = 0 vfs:0 #vfs_recycle_end #unassigned_devices_start #Unassigned devices share includes include = /tmp/unassigned.devices/smb-settings.conf #unassigned_devices_end

Nevermind. I am looking for the IT833E chip support that is not avaiable yet.

The dockers themselves aren't that big an issue, but one that is misconfigured could end up consuming a lot of memory.

You are running out of memory: Apr 5 03:29:05 MIKESDESKTOP kernel: CPU: 2 PID: 9741 Comm: mono Tainted: P O 4.19.107-Unraid #1 Apr 5 03:29:05 MIKESDESKTOP kernel: Hardware name: Supermicro PIO-617R-TLN4F+-ST031/X9DRi-LN4+/X9DR3-LN4+, BIOS 3.2 03/04/2015 Apr 5 03:29:05 MIKESDESKTOP kernel: Call Trace: Apr 5 03:29:05 MIKESDESKTOP kernel: dump_stack+0x67/0x83 Apr 5 03:29:05 MIKESDESKTOP kernel: dump_header+0x66/0x289 Apr 5 03:29:05 MIKESDESKTOP kernel: oom_kill_process+0x9d/0x220 Apr 5 03:29:05 MIKESDESKTOP kernel: out_of_memory+0x3b7/0x3ea Apr 5 03:29:05 MIKESDESKTOP kernel: mem_cgroup_out_of_memory+0x94/0xc8 Apr 5 03:29:05 MIKESDESKTOP kernel: try_charge+0x52a/0x682 Apr 5 03:29:05 MIKESDESKTOP kernel: ? __alloc_pages_nodemask+0x150/0xae1 Apr 5 03:29:05 MIKESDESKTOP kernel: mem_cgroup_try_charge+0x115/0x158 Apr 5 03:29:05 MIKESDESKTOP kernel: __add_to_page_cache_locked+0x73/0x184 Apr 5 03:29:05 MIKESDESKTOP kernel: add_to_page_cache_lru+0x47/0xd5 Apr 5 03:29:05 MIKESDESKTOP kernel: filemap_fault+0x238/0x47c Apr 5 03:29:05 MIKESDESKTOP kernel: __do_fault+0x4d/0x88 Apr 5 03:29:05 MIKESDESKTOP kernel: __handle_mm_fault+0xdb5/0x11b7 Apr 5 03:29:05 MIKESDESKTOP kernel: handle_mm_fault+0x189/0x1e3 Apr 5 03:29:05 MIKESDESKTOP kernel: __do_page_fault+0x267/0x3ff Apr 5 03:29:05 MIKESDESKTOP kernel: ? page_fault+0x8/0x30 Apr 5 03:29:05 MIKESDESKTOP kernel: page_fault+0x1e/0x30 Apr 5 03:29:05 MIKESDESKTOP kernel: RIP: 0033:0x14b61a22efa0 Apr 5 03:29:05 MIKESDESKTOP kernel: Code: Bad RIP value. Apr 5 03:29:05 MIKESDESKTOP kernel: RSP: 002b:000014b6047eca98 EFLAGS: 00010206 Apr 5 03:29:05 MIKESDESKTOP kernel: RAX: 0000000000000001 RBX: 0000000000000508 RCX: 000000000000185d Apr 5 03:29:05 MIKESDESKTOP kernel: RDX: 0000000000000002 RSI: 0000000000000000 RDI: 000014b607acde28 Apr 5 03:29:05 MIKESDESKTOP kernel: RBP: 0000000000000000 R08: 0000000000000002 R09: 000014b5f56353b1 Apr 5 03:29:05 MIKESDESKTOP kernel: R10: 000014b6047ecd30 R11: 000000000000001b R12: 00000000000027b3 Apr 5 03:29:05 MIKESDESKTOP kernel: R13: 0000000000000002 R14: 000014b5ec5d49d0 R15: 000014b5f5625af8 Apr 5 03:29:05 MIKESDESKTOP kernel: Task in /docker/a469741e4e9d3605e94e76b94b3d968cfbaafe31bcd4dc0499b6764523f21eab killed as a result of limit of /docker/a469741e4e9d3605e94e76b94b3d968cfbaafe31bcd4dc0499b6764523f21eab Apr 5 03:29:05 MIKESDESKTOP kernel: memory: usage 1048576kB, limit 1048576kB, failcnt 4331854 Apr 5 03:29:05 MIKESDESKTOP kernel: memory+swap: usage 1048576kB, limit 2097152kB, failcnt 0 Apr 5 03:29:05 MIKESDESKTOP kernel: kmem: usage 28720kB, limit 9007199254740988kB, failcnt 0 Apr 5 03:29:05 MIKESDESKTOP kernel: Memory cgroup stats for /docker/a469741e4e9d3605e94e76b94b3d968cfbaafe31bcd4dc0499b6764523f21eab: cache:9144KB rss:1012216KB rss_huge:2048KB shmem:0KB mapped_file:2640KB dirty:1056KB writeback:1188KB swap:0KB inactive_anon:4KB active_anon:1012424KB inactive_file:4196KB active_file:3104KB unevictable:0KB Apr 5 03:29:05 MIKESDESKTOP kernel: Tasks state (memory values in pages): Apr 5 03:29:05 MIKESDESKTOP kernel: [ pid ] uid tgid total_vm rss pgtables_bytes swapents oom_score_adj name Apr 5 03:29:05 MIKESDESKTOP kernel: [ 16125] 0 16125 51 1 24576 0 0 s6-svscan Apr 5 03:29:05 MIKESDESKTOP kernel: [ 16245] 0 16245 51 1 24576 0 0 s6-supervise Apr 5 03:29:05 MIKESDESKTOP kernel: [ 22539] 0 22539 51 1 24576 0 0 s6-supervise Apr 5 03:29:05 MIKESDESKTOP kernel: [ 8530] 99 8530 4367132 249608 5468160 0 0 mono Apr 5 03:29:05 MIKESDESKTOP kernel: Memory cgroup out of memory: Kill process 8530 (mono) score 957 or sacrifice child Apr 5 03:29:05 MIKESDESKTOP kernel: Killed process 8530 (mono) total-vm:17468528kB, anon-rss:998428kB, file-rss:0kB, shmem-rss:4kB The messages are not a big issue, but running out of memory is a problem.

Please add hwmon it87 driver for later motherboards.

mysqueezebox.com is optional. Just ignore the login.

It's hard for me to follow when the screens are not in English. Is the problem from invalid credentials or something else? Translate the error dialog. You might also try Windows troubleshooting and see if something comes out of that. I suspect a Windows issue. I don't have any problems with SMB sharing.

Try to access the share directly to see if it is a SMB share issue or a browsing issue: \\Tower\ShareName

Go to the UD settings and enable SMB security and set the permissions you want for the users. Turn on the 'Share' switch in UD for the device you want to share. It might take two or three minutes to show at \\Tower\ because of the SMB refresh time of Unraid.

Those are the correct mount points. So what is the problem you are having?

So, Unraid needs to include the driver I need?

Understood, but does the sensors-detect file do that seems to have driver information.

Wow, that goes back a long ways.

Did you delete the folder as I asked?

I don't think this is correct: Disclaimer: This script is NOT definitive. There may be other issues with your server that will affect compatibility. Current unRaid Version: 6.8.3 Upgrade unRaid Version: 6.9.0-beta1 Checking for plugin updates OK: All plugins up to date Checking for plugin compatibility Issue Found: dynamix.cache.dirs.plg is not known to Community Applications. Compatibility for this plugin CANNOT be determined and it may cause you issues.

@bonienl Can you add support for it8733E chip to the temperature plugin?

I also updated the Dynamix plugins and have no issues with UD. One of my servers is 6.8.3, the other is 6.9 beta 1.