You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Jellyfin
[11:28:05] INFO: Automount is Enabled!
---------------------------------------------------
[11:28:05] INFO: Checking Mounting disks for reserved names:
Jellyfin
---------------------------------------------------
---------------------------------------------------
[11:28:06] INFO: Mounting disks:
Jellyfin
---------------------------------------------------
[11:28:06] WARNING: Your Jellyfin is ntfs. This is an EXPERIMENTAL support
mount: /mnt/Jellyfin: wrong fs type, bad option, bad superblock on /dev/sda1, missing codepage or helper program, or other error.
dmesg(1) may have more information after failed mount system call.
[11:28:06] WARNING: Fail to mount Jellyfin nosuid,relatime,noexec !
s6-rc: info: service init-automount successfully started
s6-rc: info: service init-smartd: starting
s6-rc: info: service init-samba: starting
s6-rc: info: service hd-idle: starting
s6-rc: info: service hd-idle successfully started
[11:28:06] INFO: Hostname: homeassistant
[11:28:06] INFO: Interfaces: end0
[11:28:06] INFO: Enabling S.M.A.R.T for /dev/sda
smartctl 7.4 2023-08-01 r5530 [aarch64-linux-6.6.33-haos] (local build)
Copyright (C) 2002-23, Bruce Allen, Christian Franke, www.smartmontools.org
[11:28:06] INFO: Docker Interface: hassio 172.30.32.0/23
=== START OF ENABLE/DISABLE COMMANDS SECTION ===
tdbsam_open: Converting version 0.0 database to version 4.0.
tdbsam_convert_backup: updated /var/lib/samba/private/passdb.tdb file.
SMART Enabled.
SMART Attribute Autosave Enabled.
Added user homeassistant.
SMART Automatic Offline Testing Enabled every four hours.
s6-rc: info: service init-smartd successfully started
Added user _ha_mount_user_.
---------------------------------------------------
[11:28:07] INFO: Exposed Disks Summary:
[CONFIG] path = /homeassistant # TM:false FS:native #
[ADDONS] path = /addons # TM:false FS:native #
[SSL] path = /ssl # TM:false FS:native #
[SHARE] path = /share # TM:false FS:native #
[BACKUP] path = /backup # TM:false FS:native #
[MEDIA] path = /media # TM:false FS:native #
[ADDON_CONFIGS] path = /addon_configs # TM:false FS:native #
---------------------------------------------------
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 wsdd successfully started
s6-rc: info: service nmbd successfully started
s6-rc: info: service smbd successfully started
s6-rc: info: service cifs-supervisor-mount: starting
s6-rc: info: service avahi successfully started
[11:28:07] INFO: Starting the AVAHI for homeassistant...
Waiting for daemon ...
[11:28:08] INFO: Automount Shares...
[11:28:08] INFO: MQTT support not enabled in config
s6-rc: info: service init-mqtt successfully started
nmbd version 4.18.9 started.
Copyright Andrew Tridgell and the Samba Team 1992-2023
[11:28:08] INFO: Starting the wsdd daemon for WORKGROUP/homeassistant...
[11:28:08] INFO: Wait Samba Server to going up..(max 30s)
smbd version 4.18.9 started.
Copyright Andrew Tridgell and the Samba Team 1992-2023
[11:28:08] INFO: Interfaces: -i end0
INFO: Profiling support unavailable in this build.
2024-07-17 11:28:09,327:wsdd INFO(pid 370): using pre-defined UUID cb6a33a0-b841-531d-a34e-09ecec492eb1
2024-07-17 11:28:09,333:wsdd INFO(pid 370): joined multicast group 239.255.255.250 on 192.168.1.40%end0
2024-07-17 11:28:09,341:wsdd INFO(pid 370): scheduling Hello message via end0 to 239.255.255.250%end0
2024-07-17 11:28:09,365:wsdd INFO(pid 370): joined multicast group [ff02::c] on fe80::f269:54e6:84fa:2ad0%end0
2024-07-17 11:28:09,367:wsdd INFO(pid 370): scheduling Hello message via end0 to ff02::c%end0
No locked files
Samba version 4.18.9
PID Username Group Machine Protocol Version Encryption Signing
----------------------------------------------------------------------------------------------------------------------------------------
Service pid Machine Connected at Encryption Signing
---------------------------------------------------------------------------------------------
s6-rc: info: service cifs-supervisor-mount 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
s6-rc: info: service mqtt-handler successfully started
s6-rc: info: service legacy-services: starting
s6-rc: info: service legacy-services successfully started
2024-07-17 11:28:09,680:wsdd INFO(pid 370): 192.168.1.32 - - "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 172.30.32.1
*****
It looks disk specific as I've just mounted another disk, also NTFS, and one works but not the other
[12:10:41] WARNING: Fail to mount Jellyfin nosuid,relatime,noexec !
[12:10:41] WARNING: Your NextCloud is ntfs. This is an EXPERIMENTAL support
[12:11:02] INFO: Mount NextCloud[ntfs] Success!
11:28:06] WARNING: Your Jellyfin is ntfs. This is an EXPERIMENTAL support
mount: /mnt/Jellyfin: wrong fs type, bad option, bad superblock on /dev/sda1, missing codepage or helper program, or other error.
dmesg(1) may have more information after failed mount system call.
Probably the NTFS is not unmounted clean. Just mount it in a Windows PC, check the disk and rety.
NTFS in Linux is experimental and not cover all fs state.
Hi @dianlight thanks for the answer, you were right it's due to NTFS, it would just suddenly stop working and I had to re-allocate the partitions for the disks to work. I tried multiple times with two differnt HDDS.
Addon
SambaNAS
Description
All of a sudden a working mount doesn't mount anymore; tried restart, reboot, plug out/back in... nothing works
Reproduction steps
Addon Logs
Addon Config
Architecture
other
OS
HaOS
The text was updated successfully, but these errors were encountered: