If it still doesn't happen in safe mode, it suggests a plugin or other modification, I see you have a lot of custom stuff on the go file, for example

41 minutes ago, JorgeB said:

If it still doesn't happen in safe mode, it suggests a plugin or other modification, I see you have a lot of custom stuff on the go file, for example

I am using all vanilla CA plug-ins and Apps so not sure where that would be coming from.

If I have the Docker containers stopped, why would it still be happening?

Did you try with a stock go file?

I have not modified the 'go file'. Not sure how to do that. I am still learning this system. Everything was a vanilla startup and just CA plugins and Apps.

I have unloaded some of the plugin to see if there is a difference but there is not. Is it possible that the 'smart controller' type is causing this problem? The devices are SATA but when I do a 'smartctl --scan' it shows that the array has SCSI devices. The scan interval changes when I choose ATA or SAT so I'm thinking it has something to do with that?

root@Linc:~# smartctl --scan
/dev/sdb -d scsi # /dev/sdb, SCSI device
/dev/sdc -d scsi # /dev/sdc, SCSI device
/dev/sdd -d scsi # /dev/sdd, SCSI device
/dev/sde -d scsi # /dev/sde, SCSI device
/dev/nvme0 -d nvme # /dev/nvme0, NVMe device
/dev/nvme1 -d nvme # /dev/nvme1, NVMe device
root@Linc:~# smartctl -i /dev/sdb
smartctl 7.5 2025-04-30 r5714 [x86_64-linux-6.12.54-Unraid] (local build)
Copyright (C) 2002-25, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF INFORMATION SECTION ===
Model Family:     Western Digital Red Plus
Device Model:     WDC WD60EFZX-68B3FN0
Serial Number:    WD-C80KK9GG
LU WWN Device Id: 5 0014ee 269138f9e
Firmware Version: 81.00A81
User Capacity:    6,001,175,126,016 bytes [6.00 TB]
Sector Sizes:     512 bytes logical, 4096 bytes physical
Rotation Rate:    5640 rpm
Form Factor:      3.5 inches
Device is:        In smartctl database 7.5/6045
ATA Version is:   ACS-3 T13/2161-D revision 5
SATA Version is:  SATA 3.1, 6.0 Gb/s (current: 6.0 Gb/s)
Local Time is:    Mon Jan 26 11:50:23 2026 CET
SMART support is: Available - device has SMART capability.
SMART support is: Enabled

root@Linc:~# 

Edited January 26Jan 26 by frank_sp61

Which Lincplus system is that?

The go file customizations likely come from them. It seems there's a "monitor" thing so maybe it's something they added that's not part of stock Unraid that does it.

10 minutes ago, Kilrah said:

Which Lincplus system is that?

The go file customizations likely come from them. It seems there's a "monitor" thing so maybe it's something they added that's not part of stock Unraid that does it.

It's the new S1, kind of like a tower.

LincPlus

LincPlus LincStation S1 6-Bay NAS | 8GB RAM+128G ROM (Dis...

This nas storage supports full-featured docker and virtualization, comes with Unraid License. One-click deployment and installation of the docker application suite. Support to build virtual machines i

Is it not an issue that smartctl -scan thinks these are SCSI drives but smartctl -I /dev/sdb shows ATA and SATA?

root@Linc:~# smartctl --scan
/dev/sdb -d scsi # /dev/sdb, SCSI device

=== START OF INFORMATION SECTION ===
Model Family:     Western Digital Red Plus
Device Model:     WDC WD60EFZX-68B3FN0
Serial Number:    WD-C80KK9GG
LU WWN Device Id: 5 0014ee 269138f9e
Firmware Version: 81.00A81
User Capacity:    6,001,175,126,016 bytes [6.00 TB]
Sector Sizes:     512 bytes logical, 4096 bytes physical
Rotation Rate:    5640 rpm
Form Factor:      3.5 inches
Device is:        In smartctl database 7.5/6045
ATA Version is:   ACS-3 T13/2161-D revision 5
SATA Version is:  SATA 3.1, 6.0 Gb/s (current: 6.0 Gb/s)
Local Time is:    Mon Jan 26 12:47:52 2026 CET
SMART support is: Available - device has SMART capability.
SMART support is: Enabled

No, perfectly normal. There's a lot of legacy protocol encapsulation in most current interfaces.

1 hour ago, frank_sp61 said:

I have not modified the 'go file'. Not sure how to do that. I am still learning this system.

If it's a Lincstation, it was likely done by them. You can still try using a stock one, but you may lose some functionality with the LEDs, for example.

45 minutes ago, frank_sp61 said:

It's the new S1, kind of like a tower.

Edit /boot/config/go and comment out everything after

#!/bin/bash
# Start the Management Utility
/usr/local/sbin/emhttp

If that helps you can try putting the rest back from top to bottom...

My guess is it's this

# Start the Monitor Service
cp -r /boot/config/monitor/ /usr/local/sbin/monitor/
chmod 777 /usr/local/sbin/monitor/monitor
nohup /usr/local/sbin/monitor/monitor >/dev/null 2>&1 &

I.e. they added some kind of monitoring service to check drive status and display it on that pretty little LCD, but without considering the implications / being careful not to wake up drives for it.

If you can confirm it's fine with only the first 3 lines of the file then contact Linc and tell them about the problem, it'll be on their side.

I’ll give that a try and let you know.

2 hours ago, Kilrah said:

No, perfectly normal. There's a lot of legacy protocol encapsulation in most current interfaces.

Thanks. I can eliminate that at least!

2 hours ago, Kilrah said:

Edit /boot/config/go and comment out everything after

#!/bin/bash
# Start the Management Utility
/usr/local/sbin/emhttp

If that helps you can try putting the rest back from top to bottom...

My guess is it's this

# Start the Monitor Service
cp -r /boot/config/monitor/ /usr/local/sbin/monitor/
chmod 777 /usr/local/sbin/monitor/monitor
nohup /usr/local/sbin/monitor/monitor >/dev/null 2>&1 &

I.e. they added some kind of monitoring service to check drive status and display it on that pretty little LCD, but without considering the implications / being careful not to wake up drives for it.

If you can confirm it's fine with only the first 3 lines of the file then contact Linc and tell them about the problem, it'll be on their side.

I 'disabled' the Monitor Service and smartctl messages seemed to have stopped. Attached are the logs.

#!/bin/bash
# Start the Management Utility
/usr/local/sbin/emhttp

# Enable probe
modprobe i2c-dev

# Install PKG
installpkg /boot/config/pkg/i2c-tools-4.1-x86_64-1_slonly.txz

# Start the Monitor Service
# cp -r /boot/config/monitor/ /usr/local/sbin/monitor/
# chmod 777 /usr/local/sbin/monitor/monitor
# nohup /usr/local/sbin/monitor/monitor >/dev/null 2>&1 &

# Start the Screen Serial Service
cp -r /boot/config/serial/ /usr/local/sbin/serial/
chmod 777 /usr/local/sbin/serial/serialtest
chmod 777 /usr/local/sbin/serial/test.sh
nohup /usr/local/sbin/serial/test.sh >/dev/null 2>&1 &

# Start the RESET Service
cp -r /boot/config/reset/ /usr/local/sbin/reset/
chmod 777 /usr/local/sbin/reset/reset
nohup /usr/local/sbin/reset/reset >/dev/null 2>&1 &

linc-diagnostics-20260126-1626.zip

If that stops the spam, you can contact LincPlus support and ask them if that is needed, and mention that it is spamming the log.

That's my next step!

So now, back to my original issue. My Homeassistant server writes a backup file to my UNRAID server once per evening. Homeassistant is on a separate machine and is not on a docker container in my UNRAID server.

The share is setup for primary storage as cache and then moved to the array. After the backup, I get an error from my Homeassistant that the NFS share is unavailable and I have to reboot my Homeassistant to clear the error.

This does not occur when the share is setup for primary storage as the array. Looking to understand why this is happening.

Attached are the logs. You will notice that my Frigate server (also separate, 3rd server) writes just fine without reporting any errors. I've included the diagnostics as well as screen prints from my Homeassistant and the UNRAID share in case anyone can spot a setup error.

linc-diagnostics-20260127-1027.zip

Using NFS with the mover is known to have multiple issues/limitations, this is because of how NFS uses the file/folder inodes, not the names, to keep track of them, when you run the mover on the pool, Unraid will destroy the zfs dataset once it finishes moving all its contents, so the inode NFS was using will no longer exist.

My suggestion would be to use SMB instead if possible; it doesn't have these limitations. If you really must use NFS, use it with a share that only has primary storage, better yet, use it with exclusive shares only.

Excellent! I will try that! Thank you again. You've been a big help.

Just fyi, I confirmed that the SMB does work! Thank you. Also LINCPLUS confirmed that they are using the smartctl in the go file to update the LCD display and is optional.