dlandon

I don't use the fans plugin so I don't know what you are referring to with the 'hwmonX'. What designation does the fans plugin use to monitor the disk device?

I assume these are commands on Unraid. If so use the UD Plugin to mount the remote NFS share as you are not mounting the NFSv4 with any options. It will make management of the remote share a lot easier. UD will also manage a default set of rules that should work in most cases. Also, post your diagnostics zip file for further help.

You have to remove the partition before UD Preclear will allow you to preclear the disk. Click on the red X next to the drive serial number and clear the disk. It will then show up as being able to preclear.

What the "Reboot" indicator on the Mount button means is that the device was removed before being unmounted. A reboot is the only way to fix it. This can happen when a disk is physically unplugged, or the connection drops. Your log is full of disk errors indicating that the device dropped offline or was disconnected. This is an example: Jun 4 12:22:19 Tardis ntfs-3g[15010]: ntfs_attr_pread_i: ntfs_pread failed: Input/output error Jun 4 12:22:19 Tardis ntfs-3g[15010]: Failed to read vcn 0x0 from inode 5: Input/output error Jun 4 12:22:19 Tardis ntfs-3g[15010]: ntfs_attr_pread_i: ntfs_pread failed: Input/output error Jun 4 12:22:19 Tardis ntfs-3g[15010]: Failed to read vcn 0x0 from inode 5: Input/output error Jun 4 12:22:19 Tardis kernel: Buffer I/O error on dev sdn1, logical block 183141285, async page read You may have cable or enclosure issues.

You can assign an alias name to replace the 'Dev X' designation and the name will not change even if the 'Dev X' changes. Click on the device settings (three gear icon) and assign a name of your choice, A benefit of this is that your devices with assigned alias names will be sorted.

Yes, click on the device designator ('Dev X') and make a change to the SMART settings and save the change. The warnings will follow the serial number and not the 'Dev X'.

The post read verification failed. This could be due to bad memory. You should run a memory test. The SMART report also reports that the drive has overheated in the past. This may have caused the errors. Run the memory test and fix any issues there. Then if you really want to use the disk, run another preclear. If you are on Unraid 6.9 or greater, remove the preclear disk plugin and install the UD Preclear plugin. It's an updated preclear.

The reason this was done is because updating the whole recycle bin can take a lot of time with a large recycle bin. This would cause the GUI to hang while it is refreshing the recycle bin. That's why the background update was inplemented so the GUI would not appear to hang. If someone wants immediate gratification, they can turn off the background update, with the understanding an update could take a long time and hang the GUI.

Does it bother you that much? When you delete a file, the recycle bin space could take up to 5 minutes to update. Same issue.

Sonarr will have to be accessing the share through SMB. The recycle bin won't work by accessing the share through /mnt/disks/mountpoint.

I don't see where you tried to mount the rootshare. In order to mount a rootshare, you need to have SMB enabled, and UD SMB settings to enable SMB shares on UD. Then click the "Mount" button to mount the root share. I don't suggest you use the smb-extra.conf settings. That is not "stock" and can create other issues.

The Dashboard is stock Unraid and UD has no control over that page. Since UD is controlling the naming of devices, Unraid is not aware of those device names, and it is a minor display issue, it is not going to be viewed as a very important change.

SMB has to be enabled. What is not working? Post diagnostics and possibly a screen shot.

You'll need to report this to the LMS developers. There's nothing I can do with the docker container to solve this.

Both your servers are 6.10. I have two servers running 6.0 and I can cross mount NFSv3 and NFSv4 shares. Shares are mounted RW and not RO. Don't minimize the errors on the one server. You need to clean those up. Not sure what effect those have on NFS. The server not responding is probably a network or server configuration issue.

The issue of the NFS server (192.168.0.1) not responding is a problem.

Your edi-diagnostics server has some issues you need to clean up: Jun 6 04:40:02 EDI emhttpd: error: share_luks_status, 6158: Operation not supported (95): getxattr: /mnt/user/backup Jun 6 04:40:02 EDI emhttpd: error: share_luks_status, 6158: Operation not supported (95): getxattr: /mnt/user/tdarr Jun 6 04:40:03 EDI emhttpd: error: share_luks_status, 6158: Operation not supported (95): getxattr: /mnt/user/backup Jun 6 04:40:03 EDI emhttpd: error: share_luks_status, 6158: Operation not supported (95): getxattr: /mnt/user/tdarr Jun 6 04:40:04 EDI emhttpd: error: share_luks_status, 6158: Operation not supported (95): getxattr: /mnt/user/backup Jun 6 04:40:04 EDI emhttpd: error: share_luks_status, 6158: Operation not supported (95): getxattr: /mnt/user/tdarr Jun 6 04:50:06 EDI kernel: Call Trace: Jun 6 04:50:06 EDI kernel: <TASK> Jun 6 04:50:06 EDI kernel: intel_idle+0x1b/0x21 Jun 6 04:50:06 EDI kernel: cpuidle_enter_state+0xc6/0x1db Jun 6 04:50:06 EDI kernel: cpuidle_enter+0x2a/0x36 Jun 6 04:50:06 EDI kernel: do_idle+0x1b7/0x225 Jun 6 04:50:06 EDI kernel: cpu_startup_entry+0x1d/0x1f Jun 6 04:50:06 EDI kernel: start_kernel+0x656/0x67b Jun 6 04:50:06 EDI kernel: secondary_startup_64_no_verify+0xb0/0xbb Jun 6 04:50:06 EDI kernel: </TASK> Jun 6 04:50:06 EDI kernel: NMI: IOCK error (debug interrupt?) for reason 61 on CPU 0. Jun 6 04:50:06 EDI kernel: CPU: 0 PID: 0 Comm: swapper/0 Tainted: P W IO 5.15.43-Unraid #1 Jun 6 04:50:06 EDI kernel: Hardware name: HP ProLiant DL380 G7, BIOS P67 03/30/2010 Jun 6 04:50:06 EDI kernel: RIP: 0010:mwait_idle_with_hints.constprop.0+0x5f/0x86 Jun 6 04:50:06 EDI kernel: Code: 48 89 d1 65 48 8b 04 25 c0 bb 01 00 0f 01 c8 48 8b 00 a8 08 75 14 eb 07 0f 00 2d dc 6e 9f 00 b9 01 00 00 00 48 89 f8 0f 01 c9 <65> 48 8b 04 25 c0 bb 01 00 f0 80 60 02 df f0 83 44 24 fc 00 48 8b Jun 6 04:50:06 EDI kernel: RSP: 0018:ffffffff82203e48 EFLAGS: 00000046 Jun 6 04:50:06 EDI kernel: RAX: 0000000000000001 RBX: 0000000000000002 RCX: 0000000000000001 Jun 6 04:50:06 EDI kernel: RDX: 0000000000000000 RSI: ffffffff82311ca0 RDI: 0000000000000001 Jun 6 04:50:06 EDI kernel: RBP: ffffe8f6ff81b300 R08: 0000215f75e73451 R09: ffff888913a1eca0 Jun 6 04:50:06 EDI kernel: R10: 0000000000000020 R11: 00000000000005d8 R12: 0000000000000002 Jun 6 04:50:06 EDI kernel: R13: ffffffff82311d70 R14: ffffffff82311d88 R15: 0000000000000000 Jun 6 04:50:06 EDI kernel: FS: 0000000000000000(0000) GS:ffff888913a00000(0000) knlGS:0000000000000000 Jun 6 04:50:06 EDI kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 Jun 6 04:50:06 EDI kernel: CR2: 000014e4467a4000 CR3: 000000016eeb6006 CR4: 00000000000226f0 Jun 6 04:53:33 EDI kernel: nfs: server 192.168.0.1 not responding, timed out You are wanting the two servers to cross mount shares using NFSv4 and have a remote share mounted NFSv3?

Ok. I asked you if the log of the BluRay device had anything about NFS. Can you access the log and what does it show? Also, how are you mounting the Unraid share on the BluRay player?

You have network or remote server issues that are keeping UD from geting the information it needs for the remote share: Jun 5 21:47:45 FERRANTEAPP1 unassigned.devices: Error: shell_exec(/bin/df '/mnt/remotes/FERRANTEMD1_PMS_DATA_UNRAID' --output=size,used,avail | /bin/grep -v '1K-blocks' 2>/dev/null) took longer than 5s! Jun 5 21:47:45 FERRANTEAPP1 unassigned.devices: Error: shell_exec(/bin/df '/mnt/remotes/FERRANTEMD1_PMS_DATA_UNRAID' --output=size,used,avail | /bin/grep -v '1K-blocks' 2>/dev/null) took longer than 5s! Jun 5 21:47:46 FERRANTEAPP1 unassigned.devices: Error: shell_exec(/bin/df '/mnt/remotes/FERRANTEMD1_PMS_DATA_UNRAID' --output=size,used,avail | /bin/grep -v '1K-blocks' 2>/dev/null) took longer than 5s! Jun 5 21:47:48 FERRANTEAPP1 unassigned.devices: Error: shell_exec(/bin/df '/mnt/remotes/FERRANTEMD1_PMS_DATA_UNRAID' --output=size,used,avail | /bin/grep -v '1K-blocks' 2>/dev/null) took longer than 5s! Jun 5 21:47:50 FERRANTEAPP1 unassigned.devices: Error: shell_exec(/bin/df '/mnt/remotes/FERRANTEMD1_Sync' --output=size,used,avail | /bin/grep -v '1K-blocks' 2>/dev/null) took longer than 5s! Jun 5 21:47:50 FERRANTEAPP1 unassigned.devices: Error: shell_exec(/bin/df '/mnt/remotes/FERRANTEMD1_Sync' --output=size,used,avail | /bin/grep -v '1K-blocks' 2>/dev/null) took longer than 5s! Jun 5 21:47:51 FERRANTEAPP1 unassigned.devices: Error: shell_exec(/bin/df '/mnt/remotes/FERRANTEMD1_Sync' --output=size,used,avail | /bin/grep -v '1K-blocks' 2>/dev/null) took longer than 5s! Jun 5 21:47:51 FERRANTEAPP1 unassigned.devices: Error: shell_exec(/bin/df '/mnt/remotes/FERRANTEMD1_Sync' --output=size,used,avail | /bin/grep -v '1K-blocks' 2>/dev/null) took longer than 5s! Jun 5 21:47:53 FERRANTEAPP1 unassigned.devices: Error: shell_exec(/bin/df '/mnt/remotes/FERRANTEMD1_Sync' --output=size,used,avail | /bin/grep -v '1K-blocks' 2>/dev/null) took longer than 5s! Jun 5 21:47:54 FERRANTEAPP1 unassigned.devices: Error: shell_exec(/bin/df '/mnt/remotes/FERRANTEMD1_Sync' --output=size,used,avail | /bin/grep -v '1K-blocks' 2>/dev/null) took longer than 5s! The 'df' commands are timing out. This is the comand to determine the size, used, and free space on the remote share. That's why you see all zeroes.

You can set to mount UD remote shares by going to UD Settings and setting to NFSv3.

Post your diagnostics zip.

Unraid 6.9 uses NFSv3. Unraid 6.10 uses NFSv4. You'll probably have to set the Unraid 6.10 to only mount using NFSv3. Why don't you update both servers to 6.10? The NFS versions will then both be NFSv4. NFSv4 has a lot fewer issues that NFSv3.

Downgrade to 6.9.

Share issue fixed in the next release.

That shows UD is sharing the disk. I'll have to look and see how this happens.