hassio-addons icon indicating copy to clipboard operation
hassio-addons copied to clipboard

🐛 [SambaNAS] repair appears with every host reboot and needs manual reload input

Open Shiroe93 opened this issue 11 months ago • 10 comments

Addon

SambaNAS

Description

every time the host is rebooted a repair appears that asks to try a reload (manual button press needed) it wuold be possible to create an automation that reload the share automatically?

Reproduction steps

1. rebbot the host
2. repair appears 
3. solved if manually reload

Addon Logs

[18:22:21] INFO: Enabling S.M.A.R.T for /dev/sda
[18:22:21] INFO: Docker Interface: hassio 172.30.32.0/23
=== START OF ENABLE/DISABLE COMMANDS SECTION ===
SMART Enabled.
SMART Attribute Autosave Enabled.
SMART Automatic Offline Testing Enabled every four hours.
tdbsam_open: Converting version 0.0 database to version 4.0.
tdbsam_convert_backup: updated /var/lib/samba/private/passdb.tdb file.

[18:22:21] INFO: Enabling S.M.A.R.T for /dev/nvme0
Added user admin.
smartctl 7.4 2023-08-01 r5530 [x86_64-linux-6.6.16-haos] (local build)
Copyright (C) 2002-23, Bruce Allen, Christian Franke, www.smartmontools.org

---------------------------------------------------
[18:22:21] INFO: Exposed Disks Summary:
[CONFIG]                path = /homeassistant # TM:false#
[ADDONS]                path = /addons # TM:false#
[SSL]                   path = /ssl # TM:false#
[SHARE]                 path = /share # TM:false#
[BACKUP]                path = /backup # TM:false#
[MEDIA]                 path = /media # TM:false#
[ADDON_CONFIGS]         path = /addon_configs # TM:false#
[FRIGATE]               path = /mnt/frigate # TM:true#
---------------------------------------------------
s6-rc: info: service init-samba successfully started
s6-rc: info: service init-mqtt: starting
s6-rc: info: service wsdd: starting
s6-rc: info: service smbd: starting
s6-rc: info: service nmbd: starting
s6-rc: info: service avahi: starting
s6-rc: info: service smbd successfully started
s6-rc: info: service wsdd successfully started
s6-rc: info: service avahi successfully started
s6-rc: info: service nmbd successfully started
s6-rc: info: service cifs-supervisor-mount: starting
s6-rc: info: service cifs-supervisor-mount successfully started
[18:22:21] INFO: MQTT support not enabled in config
s6-rc: info: service init-mqtt successfully started
s6-rc: info: service mqtt-disk-handler: starting
s6-rc: info: service mqtt-disk-handler successfully started
s6-rc: info: service mqtt-handler: starting
[18:22:21] INFO: Starting the AVAHI for homeassistant...
Waiting for daemon ...
NVMe device successfully opened

Use 'smartctl -a' (or '-x') to print SMART (and more) information

[18:22:21] INFO: Starting the wsdd daemon for WORKGROUP/homeassistant...
s6-rc: info: service mqtt-handler successfully started
s6-rc: info: service init-smartd successfully started
s6-rc: info: service legacy-services: starting
nmbd version 4.18.9 started.
Copyright Andrew Tridgell and the Samba Team 1992-2023
smbd version 4.18.9 started.
Copyright Andrew Tridgell and the Samba Team 1992-2023
[18:22:21] INFO: Interfaces: -i enp2s0 
INFO: Profiling support unavailable in this build.
s6-rc: info: service legacy-services successfully started
2024-03-11 18:22:22,104:wsdd INFO(pid 358): using pre-defined UUID cb6a33a0-b841-531d-a34e-09ecec492eb1
2024-03-11 18:22:22,105:wsdd INFO(pid 358): joined multicast group 239.255.255.250 on 192.168.50.46%enp2s0
2024-03-11 18:22:22,106:wsdd INFO(pid 358): scheduling Hello message via enp2s0 to 239.255.255.250%enp2s0
2024-03-11 18:22:22,205:wsdd INFO(pid 358): joined multicast group [ff02::c] on fe80::bef6:2db6:a88b:3446%enp2s0
2024-03-11 18:22:22,206:wsdd INFO(pid 358): scheduling Hello message via enp2s0 to ff02::c%enp2s0
2024-03-11 18:22:22,261:wsdd INFO(pid 358): 192.168.50.58 - - "POST /cb6a33a0-b841-531d-a34e-09ecec492eb1 HTTP/1.1" 200 -
2024-03-11 18:22:22,267:wsdd INFO(pid 358): fe80::35b6:bba1:e454:f96b - - "POST /cb6a33a0-b841-531d-a34e-09ecec492eb1 HTTP/1.1" 200 -
*****

Samba name server HOMEASSISTANT is now a local master browser for workgroup WORKGROUP on subnet 192.168.50.46

*****
*****

Samba name server HOMEASSISTANT is now a local master browser for workgroup WORKGROUP on subnet 172.30.32.1

*****
2024-03-11 18:24:00,837:wsdd INFO(pid 358): deleted address fe80::6844:8ff:fea4:90ab%veth6746533
2024-03-11 18:24:06,923:wsdd INFO(pid 358): deleted address fe80::c045:a1ff:fe1c:2563%vethccb88f0
2024-03-11 18:24:13,110:wsdd INFO(pid 358): deleted address fe80::80db:3dff:fe3b:2d19%veth1fda0d6
2024-03-11 18:24:19,270:wsdd INFO(pid 358): deleted address fe80::6832:c2ff:fe02:9266%veth10f3231
2024-03-11 18:24:25,363:wsdd INFO(pid 358): deleted address fe80::5cbd:a4ff:fe9b:5c21%vethcf0cea5
2024-03-11 18:29:09,794:wsdd INFO(pid 358): [fe80::35b6:bba1:e454:f96b]:62643(enp2s0) - - "Resolve urn:uuid:3e0dd336-7de2-4e3f-add7-7b0ba8a4ee39 UDP" - -
2024-03-11 18:29:19,795:wsdd INFO(pid 358): [fe80::35b6:bba1:e454:f96b]:62643(enp2s0) - - "Resolve urn:uuid:3e89f1bd-4101-44d6-b3ec-ac2922ebf384 UDP" - -
2024-03-11 18:31:57,997:wsdd INFO(pid 358): [fe80::35b6:bba1:e454:f96b]:62643(enp2s0) - - "Resolve urn:uuid:4190f49d-5b56-422b-9536-1ec2aa508b44 UDP" - -
2024-03-11 18:39:29,803:wsdd INFO(pid 358): [fe80::35b6:bba1:e454:f96b]:62643(enp2s0) - - "Resolve urn:uuid:e658e48a-0407-48e7-b225-0079e19e14bb UDP" - -
2024-03-11 18:39:39,800:wsdd INFO(pid 358): [fe80::35b6:bba1:e454:f96b]:62643(enp2s0) - - "Resolve urn:uuid:4832dd74-32e6-45c5-b16a-c582b446a3f2 UDP" - -
2024-03-11 18:41:57,982:wsdd INFO(pid 358): [fe80::35b6:bba1:e454:f96b]:62643(enp2s0) - - "Resolve urn:uuid:18cb062a-570d-4893-93ec-ecdd5faeae4e UDP" - -

Addon Config

workgroup: WORKGROUP
username: redacted
allow_hosts:
  - 10.0.0.0/8
  - 172.16.0.0/12
  - 192.168.0.0/16
  - 169.254.0.0/16
  - fe80::/10
  - fc00::/7
automount: true
moredisks: []
mountoptions:
  - nosuid
  - relatime
  - noexec
available_disks_log: true
medialibrary:
  enable: false
veto_files:
  - ._*
  - .DS_Store
  - Thumbs.db
  - icon?
  - .Trashes
compatibility_mode: false
recyle_bin_enabled: false
wsdd2: false
mqtt_nexgen_entities: false
autodiscovery: {}
other_users: []
acl: []
interfaces: []
password: redacted

Architecture

amd64

OS

HaOS

Shiroe93 avatar Mar 11 '24 17:03 Shiroe93

HA Supervisor 2024.04.2 should fixed the proble. Try it and report if persists

dianlight avatar Apr 21 '24 05:04 dianlight

I will test as soon i receive the update because this is a major issue for me

Shiroe93 avatar Apr 21 '24 05:04 Shiroe93

HA Supervisor 2024.04.2 should fixed the proble. Try it and report if persists

i updated the Supervisor to 2024.04.4 a few minutes ago but the issue still persists

Shiroe93 avatar Apr 30 '24 18:04 Shiroe93

A few minutes ago I restarted it two times and the issue vanished completely Did you do something? I didn't do anything on my part no update or anything I reboot the host everyday and yesterday the issue was still there I'm very confused right know (so confused that i thought that i didn't do an host reboot the first time but a core reboot so I did another reboot to be sure)

Shiroe93 avatar May 14 '24 05:05 Shiroe93

In the last beta version of -nas3 I try to change boot sequence to ensure ha core is up before ask them to mount drive. But if you don't have updated to the last beta version is not my work. Remember that form the supervisor 2024.4.3 the failed network mount are retried automatically if the server is reachable that in many cases is sufficient.

L.

dianlight avatar May 14 '24 07:05 dianlight

that's not possible because if it was a retry an error would appear at least once but there's absolutely nothing

Shiroe93 avatar May 14 '24 07:05 Shiroe93

also can confirm that i did not update because i'm still on nas2

Shiroe93 avatar May 14 '24 07:05 Shiroe93

problem has returned

Shiroe93 avatar May 21 '24 10:05 Shiroe93

probrably was "solved" because the drive disapeared from the network share so nothing has actually changed

Shiroe93 avatar May 21 '24 11:05 Shiroe93

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

github-actions[bot] avatar Jul 20 '24 12:07 github-actions[bot]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

github-actions[bot] avatar Sep 20 '24 01:09 github-actions[bot]