🐛 [Samba NAS2-β] High disk access rate when no active read/write operations

[EnderDragonEP]

Addon

SambaNAS

Description

When running this add-on, my USB attached disk drives show a very high access rate even when there are no active SMB read/write operations. Disabling the shares configuration does not stop this behavior either. This results in audible, periodic disk noise, as if something is continuously accessing the drive. Disabling the SMART feature in Disk Information stops the behavior immediately.

Reproduction steps

1. Install and start the Samba NAS2-β add-on.
2. Mount the USB attached disk drive.
3. Ensure no SMB clients are actively using shares (or disable shares configuration).
4. Observe disk activity and audible periodic disk access.
5. In the add-on, go to Disk Information and disable SMART.
6. Observe that disk activity/noise stops.

Addon Logs

s6-rc: info: service s6rc-oneshot-runner: starting
s6-rc: info: service s6rc-oneshot-runner successfully started
s6-rc: info: service base-addon-banner: starting
-----------------------------------------------------------
 App: Samba NAS2-β
 Expose Home Assistant disc with SMB/CIFS
-----------------------------------------------------------
 App version: 2026.2.0-beta.157
 You are running the latest version of this app.
 System: Home Assistant OS 17.0  (aarch64 / raspberrypi5-64)
 Home Assistant Core: 2026.2.1
 Home Assistant Supervisor: 2026.02.1
-----------------------------------------------------------
 Please, share the above information when looking for help
 or support in, e.g., GitHub, forums or the Discord chat.
-----------------------------------------------------------
s6-rc: info: service base-addon-banner successfully started
s6-rc: info: service fix-attrs: starting
s6-rc: info: service base-addon-log-level: starting
s6-rc: info: service fix-attrs successfully started
Log level is set to FATAL
s6-rc: info: service base-addon-log-level successfully started
s6-rc: info: service legacy-cont-init: starting
s6-rc: info: service legacy-cont-init successfully started
s6-rc: info: service modprobe: starting
s6-rc: info: service init-smbd: starting
s6-rc: info: service factory-reset: starting
s6-rc: info: service clean-config: starting
s6-rc: info: service factory-reset successfully started
s6-rc: info: service check-srat-update: starting
Certificate will not expire
modprobe: module nls not found in modules.dep
modprobe: module quota not found in modules.dep
s6-rc: info: service init-smbd successfully started
s6-rc: info: service clean-config successfully started
modprobe: module smb not found in modules.dep
modprobe: module unicode not found in modules.dep
------------------------------------------------------------------------------------------------------
System Supported fs: 	ext3	ext2	ext4	squashfs	vfat	msdos	f2fs	erofs	fuseblk	ntfs3	exfat	btrfs	xfs	bcachefs	gfs2	gfs2meta	hfs	hfsplus	iso9660	jfs	nilfs2	ocfs2	reiserfs	udf
Supported fusefs: apfs tats  
------------------------------------------------------------------------------------------------------
s6-rc: info: service modprobe successfully started
s6-rc: info: service init-nfsd: starting
                _             _  _
 ___ _ _  __ _ | |_  ___  __ | |(_)
(_-<| '_|/ _` ||  _||___|/ _|| || |
/__/|_|  \__,_| \__|     \__||_||_|upgrade
SambaNAS2 Rest Administration Interface
Version: 2026.2.0-dev.3 (c58406e6) - 2026-02-05T10:50:47
Documentation: https://github.com/dianlight/SRAT
Log level: FATAL
s6-rc: info: service check-srat-update successfully started
s6-rc: info: service srat: starting
s6-rc: info: service srat successfully started
s6-rc: info: service socat: starting
s6-rc: info: service socat successfully started
s6-rc: info: service init-nfsd successfully started
s6-rc: info: service legacy-services: starting
s6-rc: info: service legacy-services successfully started
                _
 ___ _ _  __ _ | |_  ___  ___ ___  _ _ __ __ ___  _ _
(_-<| '_|/ _` ||  _||___|(_-</ -_)| '_|\ V // -_)| '_|
/__/|_|  \__,_| \__|     /__/\___||_|   \_/ \___||_|
SambaNAS2 Rest Administration Interface
Version: 2026.2.0-dev.3 (c58406e6) - 2026-02-05T10:50:47
Documentation: https://github.com/dianlight/SRAT
Log level: FATAL
smbd version 4.22.6 started.
Copyright Andrew Tridgell and the Samba Team 1992-2025
do_connect: Connection to localhost failed (Error NT_STATUS_CONNECTION_REFUSED)
Anonymous login successful
	Sharename       Type      Comment
	---------       ----      -------
	ADDON_CONFIGS   Disk      
	ADDONS          Disk      
	BACKUP          Disk      
	CONFIG          Disk      
	MEDIA           Disk      
	SHARE           Disk      
	SSL             Disk      
	IPC$            IPC       IPC Service (SambaNAS2 HomeAssistant)
SMB1 disabled -- no workgroup available
nmbd version 4.22.6 started.
Copyright Andrew Tridgell and the Samba Team 1992-2025
Looking up status of 127.0.0.1
	HOMEASSISTANT   <00> -         B <ACTIVE> 
	HOMEASSISTANT   <03> -         B <ACTIVE> 
	HOMEASSISTANT   <20> -         B <ACTIVE> 
	WORKGROUP       <00> - <GROUP> B <ACTIVE> 
	WORKGROUP       <1e> - <GROUP> B <ACTIVE> 
	MAC Address = 00-00-00-00-00-00
Configuring and starting wsddn...
Starting wsddn with arguments:-H :NETBIOS: --user wsddn --smb-conf /etc/samba/smb.conf --metadata /etc/wsddn/metadata.xml -4 --log-level 1
dump_workgroups()
 dump workgroup on subnet     172.30.32.1: netmask=  255.255.254.0:
	WORKGROUP(1) current master browser = HOMEASSISTANT
		HOMEASSISTANT 40849a03 (SambaNAS2 HomeAssistant)
dump_workgroups()
 dump workgroup on subnet    172.30.232.1: netmask=  255.255.254.0:
	WORKGROUP(1) current master browser = HOMEASSISTANT
		HOMEASSISTANT 40849a03 (SambaNAS2 HomeAssistant)
dump_workgroups()
 dump workgroup on subnet   192.168.1.100: netmask=  255.255.255.0:
	WORKGROUP(1) current master browser = HOMEASSISTANT
		HOMEASSISTANT 40849a03 (SambaNAS2 HomeAssistant)
dump_workgroups()
 dump workgroup on subnet     172.30.32.1: netmask=  255.255.254.0:
	WORKGROUP(1) current master browser = HOMEASSISTANT
		HOMEASSISTANT 40849a03 (SambaNAS2 HomeAssistant)
dump_workgroups()
 dump workgroup on subnet    172.30.232.1: netmask=  255.255.254.0:
	WORKGROUP(1) current master browser = HOMEASSISTANT
		HOMEASSISTANT 40849a03 (SambaNAS2 HomeAssistant)
dump_workgroups()
 dump workgroup on subnet   192.168.1.100: netmask=  255.255.255.0:
	WORKGROUP(1) current master browser = HOMEASSISTANT
		HOMEASSISTANT 40849a03 (SambaNAS2 HomeAssistant)
dump_workgroups()
 dump workgroup on subnet     172.30.32.1: netmask=  255.255.254.0:
	WORKGROUP(1) current master browser = HOMEASSISTANT
		HOMEASSISTANT 40849a03 (SambaNAS2 HomeAssistant)
dump_workgroups()
 dump workgroup on subnet    172.30.232.1: netmask=  255.255.254.0:
	WORKGROUP(1) current master browser = HOMEASSISTANT
		HOMEASSISTANT 40849a03 (SambaNAS2 HomeAssistant)
dump_workgroups()
 dump workgroup on subnet   192.168.1.100: netmask=  255.255.255.0:
	WORKGROUP(1) current master browser = HOMEASSISTANT
		HOMEASSISTANT 40849a03 (SambaNAS2 HomeAssistant)

Addon Config

srat_update_channel: release
auto_update: true
log_level: fatal
leave_front_door_open: true
disable_ipv6: true
clean_upgrade_dir: false
factory_reset: false

Architecture

armv7

OS

HaOS

[dianlight]

please try the last beta and give me a feedback

[EnderDragonEP]

Problem still exist in version: 2026.3.0-beta.158
Same behavior.

[dianlight]

I can't replicate so I can only suspect that it is or Smart or HA Report.
For the next release I plan to add a new config to disable SMART.
Can you meantime try to disable export statistic to HA to see if change? ( after disable don't open the sambanas dashboard to eliminate other disk access )

[dianlight]

I'have released the rc5. Can you try if you have the described issue anymore?

[EnderDragonEP]

I was not able to get any logs because the wsdapi interface stuck at loading:

I've tried Factory reset option and reinstall.

[EnderDragonEP]

This update (2026.5.0-rc5-beta.175) still performs continuous disk read/write operations when the addon is enabled, even during idle periods, resulting in persistent and regular drive noise.

[dianlight]

I make a lot of optimizations in rc9, I can't reproduce your case because it depends on an hardware implementation ( the usb disk interface ) I don't have. Please retry if this changes.