Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

🐛 [SambaNas] <title>Disk folders disappear on only one drive out of 3 #241

Closed
SirDigitalKnight opened this issue Jun 23, 2024 · 5 comments
Assignees
Labels
bug Something isn't working no-issue-activity [ SambaNas ] To verify Need to reproduced in lab

Comments

@SirDigitalKnight
Copy link

SirDigitalKnight commented Jun 23, 2024

Addon

SambaNAS

Description

Having an issue with just one attached drive. For some reason it will randomly not show the folders on the drive until I stop and restart SambaNas then they show back up again for awhile but then will just disappear again. My other 2 drives do not have this issue. I am running HAos on a Intel NUC with the 3 USB external drives connected. 1 drive is a 2TB and another is a 3TB and the one that is acting funny is a 5TB drive, All 3 are Ext4 GPT. Anyone else see this?

DriveFolderEmpty

DriveFolderBackAfterRestart

Reproduction steps

1. see pic one attached above... no folders.
2. Click on 'restart'
3. See pic two attached above... folders come back.
4. No errors to show.

Addon Logs

This response was from IP 192.168.1.6, reporting an IP address of 192.168.1.6.
2024-06-23 10:27:35,379:wsdd INFO(pid 418): 192.168.1.125:60403(eno1) - - "Probe urn:uuid:d473f0ea-c076-4317-a53d-d9410f8cd8fb UDP" - -
2024-06-23 10:27:35,747:wsdd INFO(pid 418): 192.168.1.125:55156(eno1) - - "Resolve urn:uuid:13a24365-2405-42b7-b6a5-624ce4c9eeb6 UDP" - -
2024-06-23 10:27:35,893:wsdd INFO(pid 418): 192.168.1.125 - - "POST /cb6a33a0-b841-531d-a34e-09ecec492eb1 HTTP/1.1" 200 -
query_name_response: Multiple (2) responses received for a query on subnet 192.168.1.80 for name WORKGROUP<1d>.
This response was from IP 192.168.1.6, reporting an IP address of 192.168.1.6.
query_name_response: Multiple (2) responses received for a query on subnet 192.168.1.80 for name WORKGROUP<1d>.
This response was from IP 192.168.1.6, reporting an IP address of 192.168.1.6.
query_name_response: Multiple (2) responses received for a query on subnet 192.168.1.80 for name WORKGROUP<1d>.
This response was from IP 192.168.1.6, reporting an IP address of 192.168.1.6.
query_name_response: Multiple (2) responses received for a query on subnet 192.168.1.80 for name WORKGROUP<1d>.
This response was from IP 192.168.1.6, reporting an IP address of 192.168.1.6.
query_name_response: Multiple (2) responses received for a query on subnet 192.168.1.80 for name WORKGROUP<1d>.
This response was from IP 192.168.1.6, reporting an IP address of 192.168.1.6.
query_name_response: Multiple (2) responses received for a query on subnet 192.168.1.80 for name WORKGROUP<1d>.
This response was from IP 192.168.1.6, reporting an IP address of 192.168.1.6.
query_name_response: Multiple (2) responses received for a query on subnet 192.168.1.80 for name WORKGROUP<1d>.
This response was from IP 192.168.1.6, reporting an IP address of 192.168.1.6.
query_name_response: Multiple (2) responses received for a query on subnet 192.168.1.80 for name WORKGROUP<1d>.
This response was from IP 192.168.1.6, reporting an IP address of 192.168.1.6.
query_name_response: Multiple (2) responses received for a query on subnet 192.168.1.80 for name WORKGROUP<1d>.
This response was from IP 192.168.1.6, reporting an IP address of 192.168.1.6.
query_name_response: Multiple (2) responses received for a query on subnet 192.168.1.80 for name WORKGROUP<1d>.
This response was from IP 192.168.1.6, reporting an IP address of 192.168.1.6.
query_name_response: Multiple (2) responses received for a query on subnet 192.168.1.80 for name WORKGROUP<1d>.
This response was from IP 192.168.1.6, reporting an IP address of 192.168.1.6.
query_name_response: Multiple (2) responses received for a query on subnet 192.168.1.80 for name WORKGROUP<1d>.
This response was from IP 192.168.1.6, reporting an IP address of 192.168.1.6.
query_name_response: Multiple (2) responses received for a query on subnet 192.168.1.80 for name WORKGROUP<1d>.
This response was from IP 192.168.1.6, reporting an IP address of 192.168.1.6.
query_name_response: Multiple (2) responses received for a query on subnet 192.168.1.80 for name WORKGROUP<1d>.
This response was from IP 192.168.1.6, reporting an IP address of 192.168.1.6.
query_name_response: Multiple (2) responses received for a query on subnet 192.168.1.80 for name WORKGROUP<1d>.
This response was from IP 192.168.1.6, reporting an IP address of 192.168.1.6.
query_name_response: Multiple (2) responses received for a query on subnet 192.168.1.80 for name WORKGROUP<1d>.
This response was from IP 192.168.1.6, reporting an IP address of 192.168.1.6.
2024-06-23 11:50:45,699:wsdd INFO(pid 418): 192.168.1.125:63228(eno1) - - "Probe urn:uuid:c72a3bdf-2055-448c-915d-4068d51b854f UDP" - -
2024-06-23 11:50:45,882:wsdd INFO(pid 418): 192.168.1.125:56558(eno1) - - "Resolve urn:uuid:520cbcf2-7327-435b-aeca-fbfa8f316c7b UDP" - -
2024-06-23 11:50:45,900:wsdd INFO(pid 418): 192.168.1.125 - - "POST /cb6a33a0-b841-531d-a34e-09ecec492eb1 HTTP/1.1" 200 -
query_name_response: Multiple (2) responses received for a query on subnet 192.168.1.80 for name WORKGROUP<1d>.
This response was from IP 192.168.1.6, reporting an IP address of 192.168.1.6.
2024-06-23 11:53:01,098:wsdd INFO(pid 418): 192.168.1.125:56772(eno1) - - "Probe urn:uuid:0847288f-f639-454b-ae79-76f4ae21fe82 UDP" - -
2024-06-23 11:53:01,232:wsdd INFO(pid 418): 192.168.1.125:53409(eno1) - - "Resolve urn:uuid:39f00316-2342-4928-988c-b6b08505cd0c UDP" - -
2024-06-23 11:53:01,389:wsdd INFO(pid 418): 192.168.1.125 - - "POST /cb6a33a0-b841-531d-a34e-09ecec492eb1 HTTP/1.1" 200 -
query_name_response: Multiple (2) responses received for a query on subnet 192.168.1.80 for name WORKGROUP<1d>.
This response was from IP 192.168.1.6, reporting an IP address of 192.168.1.6.
query_name_response: Multiple (2) responses received for a query on subnet 192.168.1.80 for name WORKGROUP<1d>.
This response was from IP 192.168.1.6, reporting an IP address of 192.168.1.6.
2024-06-23 12:05:00,815:wsdd INFO(pid 418): 192.168.1.125:64402(eno1) - - "Probe urn:uuid:d34fdc75-c340-40a0-bad0-4b895f7a0370 UDP" - -
2024-06-23 12:05:00,874:wsdd INFO(pid 418): 192.168.1.125:63710(eno1) - - "Resolve urn:uuid:26f9ce33-4d8e-4213-823f-01466e38cdda UDP" - -
2024-06-23 12:05:00,885:wsdd INFO(pid 418): 192.168.1.125 - - "POST /cb6a33a0-b841-531d-a34e-09ecec492eb1 HTTP/1.1" 200 -
query_name_response: Multiple (2) responses received for a query on subnet 192.168.1.80 for name WORKGROUP<1d>.
This response was from IP 192.168.1.6, reporting an IP address of 192.168.1.6.
2024-06-23 12:07:34,073:wsdd INFO(pid 418): 192.168.1.125:52004(eno1) - - "Probe urn:uuid:eaccc5a8-7fab-4f03-930f-83c52c7bffdd UDP" - -
2024-06-23 12:07:34,133:wsdd INFO(pid 418): 192.168.1.125:57858(eno1) - - "Resolve urn:uuid:38275033-4a1f-4f0a-b06d-a98a40ce3a6f UDP" - -
2024-06-23 12:07:34,144:wsdd INFO(pid 418): 192.168.1.125 - - "POST /cb6a33a0-b841-531d-a34e-09ecec492eb1 HTTP/1.1" 200 -
2024-06-23 12:10:21,270:wsdd INFO(pid 418): 192.168.1.125:63250(eno1) - - "Probe urn:uuid:e9c588b0-7482-453b-ba25-ecec99591ba7 UDP" - -
2024-06-23 12:10:21,416:wsdd INFO(pid 418): 192.168.1.125:63252(eno1) - - "Resolve urn:uuid:4d744360-5e1c-434a-9aed-8b3f7275cbef UDP" - -
2024-06-23 12:10:21,424:wsdd INFO(pid 418): 192.168.1.125 - - "POST /cb6a33a0-b841-531d-a34e-09ecec492eb1 HTTP/1.1" 200 -
query_name_response: Multiple (2) responses received for a query on subnet 192.168.1.80 for name WORKGROUP<1d>.
This response was from IP 192.168.1.6, reporting an IP address of 192.168.1.6.
query_name_response: Multiple (2) responses received for a query on subnet 192.168.1.80 for name WORKGROUP<1d>.
This response was from IP 192.168.1.6, reporting an IP address of 192.168.1.6.
query_name_response: Multiple (2) responses received for a query on subnet 192.168.1.80 for name WORKGROUP<1d>.
This response was from IP 192.168.1.6, reporting an IP address of 192.168.1.6.
query_name_response: Multiple (2) responses received for a query on subnet 192.168.1.80 for name WORKGROUP<1d>.
This response was from IP 192.168.1.6, reporting an IP address of 192.168.1.6.
query_name_response: Multiple (2) responses received for a query on subnet 192.168.1.80 for name WORKGROUP<1d>.
This response was from IP 192.168.1.6, reporting an IP address of 192.168.1.6.
query_name_response: Multiple (2) responses received for a query on subnet 192.168.1.80 for name WORKGROUP<1d>.
This response was from IP 192.168.1.6, reporting an IP address of 192.168.1.6.
query_name_response: Multiple (2) responses received for a query on subnet 192.168.1.80 for name WORKGROUP<1d>.
This response was from IP 192.168.1.6, reporting an IP address of 192.168.1.6.
query_name_response: Multiple (2) responses received for a query on subnet 192.168.1.80 for name WORKGROUP<1d>.
This response was from IP 192.168.1.6, reporting an IP address of 192.168.1.6.
query_name_response: Multiple (2) responses received for a query on subnet 192.168.1.80 for name WORKGROUP<1d>.
This response was from IP 192.168.1.6, reporting an IP address of 192.168.1.6.
query_name_response: Multiple (2) responses received for a query on subnet 192.168.1.80 for name WORKGROUP<1d>.
This response was from IP 192.168.1.6, reporting an IP address of 192.168.1.6.
query_name_response: Multiple (2) responses received for a query on subnet 192.168.1.80 for name WORKGROUP<1d>.
This response was from IP 192.168.1.6, reporting an IP address of 192.168.1.6.
query_name_response: Multiple (2) responses received for a query on subnet 192.168.1.80 for name WORKGROUP<1d>.
This response was from IP 192.168.1.6, reporting an IP address of 192.168.1.6.
query_name_response: Multiple (2) responses received for a query on subnet 192.168.1.80 for name WORKGROUP<1d>.
This response was from IP 192.168.1.6, reporting an IP address of 192.168.1.6.
query_name_response: Multiple (2) responses received for a query on subnet 192.168.1.80 for name WORKGROUP<1d>.
This response was from IP 192.168.1.6, reporting an IP address of 192.168.1.6.
query_name_response: Multiple (2) responses received for a query on subnet 192.168.1.80 for name WORKGROUP<1d>.
This response was from IP 192.168.1.6, reporting an IP address of 192.168.1.6.
query_name_response: Multiple (2) responses received for a query on subnet 192.168.1.80 for name WORKGROUP<1d>.
This response was from IP 192.168.1.6, reporting an IP address of 192.168.1.6.
query_name_response: Multiple (2) responses received for a query on subnet 192.168.1.80 for name WORKGROUP<1d>.
This response was from IP 192.168.1.6, reporting an IP address of 192.168.1.6.
2024-06-23 13:36:59,418:wsdd INFO(pid 418): 192.168.1.125:59852(eno1) - - "Probe urn:uuid:6a9f5c58-3428-4b23-8554-3c535fe19a45 UDP" - -
2024-06-23 13:36:59,565:wsdd INFO(pid 418): 192.168.1.125:58746(eno1) - - "Resolve urn:uuid:2275cded-8399-41dc-976e-6b48a973dee4 UDP" - -
2024-06-23 13:36:59,587:wsdd INFO(pid 418): 192.168.1.125 - - "POST /cb6a33a0-b841-531d-a34e-09ecec492eb1 HTTP/1.1" 200 -
2024-06-23 13:37:16,603:wsdd INFO(pid 418): 192.168.1.125:59205(eno1) - - "Probe urn:uuid:9a6cc24a-4aa7-4ee0-ad24-280c0e1479fd UDP" - -
2024-06-23 13:37:16,782:wsdd INFO(pid 418): 192.168.1.125:59207(eno1) - - "Resolve urn:uuid:662cd254-9ec3-4596-b185-9ce39a4b6402 UDP" - -
2024-06-23 13:37:16,794:wsdd INFO(pid 418): 192.168.1.125 - - "POST /cb6a33a0-b841-531d-a34e-09ecec492eb1 HTTP/1.1" 200 -
query_name_response: Multiple (2) responses received for a query on subnet 192.168.1.80 for name WORKGROUP<1d>.
This response was from IP 192.168.1.6, reporting an IP address of 192.168.1.6.

Addon Config

Samba NAS
Options
workgroup
WORKGROUP
username
akore
password
•••••
automount
moredisks
nosuid
relatime
noexec
mountoptions
available_disks_log
medialibrary
1
2
enable: false

10.0.0.0/8
172.16.0.0/12
192.168.0.0/16
169.254.0.0/16
fe80::/10
fc00::/7
allow_hosts
._*
.DS_Store
Thumbs.db
icon?
.Trashes
veto_files
compatibility_mode
recyle_bin_enabled
wsdd2
mqtt_nexgen_entities
autodiscovery
1

other_users
1

acl
1

interfaces
Show unused optional configuration options

Architecture

amd64

OS

Other

@SirDigitalKnight SirDigitalKnight added the bug Something isn't working label Jun 23, 2024
@dianlight dianlight added To verify Need to reproduced in lab [ SambaNas ] labels Jun 24, 2024
@dianlight dianlight self-assigned this Jun 24, 2024
@dianlight
Copy link
Owner

This type of error usually is caused from an usb/Sata transmission error o power problem.
The disk has an external power source or use usb also for power? If yes check that the connected usb port is capable to support it. If I remember right on nuc there are usb 'black' and 'orange' and only orange are capable to power external unit proper. You can try to simply switch the port or change the usb cable. Also an external powered usb hub can be the solution.

Another test you can try is set enable_smart option to false and see if the problem is an incompatibility with the disc so go on sleep but never wake up.

L.

@SirDigitalKnight
Copy link
Author

SirDigitalKnight commented Jun 24, 2024 via email

@dianlight
Copy link
Owner

So I then swapped the 3TB disk port on the back and moved the 5TB drive to the port on the back that the 3TB disk was plugged into and I haven't seen the problem come back since then, which was yesterday

Switching from 'same color' usb shouldn't change. If it now work I suggest to check o change the cable. It can be a contact problem and may return in future.

... So with your reply about setting it to false I will take it to mean that it is currently set to true.

Right gray or true are true.

When I restart HAos the Home Assistant Supervisor gives me 3 errors, one for each drive: "Could not connect to PlexHD1 . Check host logs for errors from the mount service for more details," and the same for PlexHD2 and PlexHD3. But I can click the "Reload" for all three and it seems to be happy as it says "Success" so not sure why that comes up everytime I restart HAos?

Is a know problem. On startup the core need to be up for start the addon but when go up try to reconnect drivers but the addon is not yet started. In the beta repo there is a version that minimize the problem but is not yet resolved.

The NUC also has a SD card slot on it and I put a 256GB card (GPT formatted as ext4) into it but it never shows up so I take it the Samba Nas only checks for USB attached drives?

The addon search for partition devices so also SD should work. Is more probable that the sd slot need a driver that is not in hassos kernel. Check if in you all hardware tab you see the sd. If yes post me so I can check. If not I can't do anything.

@SirDigitalKnight
Copy link
Author

SirDigitalKnight commented Jun 25, 2024 via email

Copy link

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 github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Aug 31, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working no-issue-activity [ SambaNas ] To verify Need to reproduced in lab
Projects
None yet
Development

No branches or pull requests

2 participants