[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
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.

Sign up for GitHub

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

Jump to bottom

T95Z Plus TV Box (S912) NAS dropping out #668

Closed
JBHudston opened this issue Nov 2, 2022 · 10 comments
Closed

T95Z Plus TV Box (S912) NAS dropping out #668

JBHudston opened this issue Nov 2, 2022 · 10 comments

Comments

@JBHudston
Copy link
JBHudston commented Nov 2, 2022 •
edited by ophub
Loading

I have installed Armbian_22.11.0_Aml_s912-m8s_bullseye_5.10.142_server_2022.09.14.img.gz on the T95Z Plus box. Installed Gnome and setup a samba share of a 4TB USB hard drive (formatted NTFS).

The samba share works fine but connection keeps randomly dropping while playing mp3s or videos from windows PC or Kodi/FireTV

I am connected by ethernet and have turn off wifi.

I repeatably get the following error log in syslog:

Nov  2 14:32:13 VideoNASty hostapd[130771]: Could not open configuration file '/etc/hostapd/hostapd.conf' for reading.
Nov  2 14:32:13 VideoNASty hostapd[130771]: Failed to set up interface with /etc/hostapd/hostapd.conf
Nov  2 14:32:13 VideoNASty hostapd[130771]: Failed to initialize interface
Nov  2 14:32:13 VideoNASty systemd[1]: hostapd.service: Control process exited, code=exited, status=1/FAILURE
Nov  2 14:32:13 VideoNASty systemd[1]: hostapd.service: Failed with result 'exit-code'.
Nov  2 14:32:13 VideoNASty systemd[1]: Failed to start Access point and authentication server for Wi-Fi and Ethernet.`

and the samba log shows:
`[2022/10/26 22:11:29.576909,  0] ../../source3/smbd/service.c:168(chdir_current_service)
  chdir_current_service: vfs_ChDir(/media/spudgun/4TB USB HD/NAS) failed: Permission denied. Current token: uid=1000, gid=1000, 13 groups: 1000 5 6 20 27 29 44 46 60 100 101 106 111
[2022/10/26 23:02:51.146024,  0] ../../source3/smbd/vfs.c:1081(vfs_GetWd)
  vfs_GetWd: SMB_VFS_GETWD call failed: Input/output error
[2022/10/26 23:02:51.150871,  0] ../../source3/smbd/vfs.c:1081(vfs_GetWd)
  vfs_GetWd: SMB_VFS_GETWD call failed: Input/output error
[2022/10/26 23:02:51.545755,  0] ../../source3/smbd/vfs.c:1081(vfs_GetWd)
  vfs_GetWd: SMB_VFS_GETWD call failed: Input/output error
[2022/10/26 23:02:51.556669,  0] ../../source3/smbd/vfs.c:1081(vfs_GetWd)
  vfs_GetWd: SMB_VFS_GETWD call failed: Input/output error
[2022/10/26 23:02:51.565281,  0] ../../source3/smbd/vfs.c:1081(vfs_GetWd)
  vfs_GetWd: SMB_VFS_GETWD call failed: Input/output error
[2022/10/26 23:02:51.575333,  0] ../../source3/smbd/vfs.c:1081(vfs_GetWd)
  vfs_GetWd: SMB_VFS_GETWD call failed: Input/output error
[2022/10/26 23:03:10.444670,  0] ../../source3/smbd/vfs.c:1081(vfs_GetWd)
  vfs_GetWd: SMB_VFS_GETWD call failed: Input/output error
@ophub
Copy link
Owner
ophub commented Nov 3, 2022 •
edited
Loading

sudo systemctl status hostapd
sudo systemctl disable hostapd

chmod 777 /media/spudgun/4TB

@JBHudston
Copy link
Author

Thanks for your help.

I gave the incorrect version in my first post.
I have the following installed:
Armbian 22.11.0-trunk Jammy with Linux 5.15.62-flippy-76+o

root@VideoNASty:~# sudo systemctl status hostapd
● hostapd.service - Access point and authentication server for Wi-Fi and Ethernet
     Loaded: loaded (/lib/systemd/system/hostapd.service; enabled; vendor preset: enabled)
     Active: activating (start) since Thu 2022-11-03 09:36:56 GMT; 14ms ago
       Docs: man:hostapd(8)
Cntrl PID: 172951 (hostapd)
      Tasks: 1 (limit: 1853)
     Memory: 124.0K
        CPU: 3ms
     CGroup: /system.slice/hostapd.service

Nov 03 09:36:56 VideoNASty systemd[1]: Starting Access point and authentication server for Wi-Fi and Ethernet...
Nov 03 09:36:56 VideoNASty hostapd[172951]: Could not open configuration file '/etc/hostapd/hostapd.conf' for reading.
Nov 03 09:36:56 VideoNASty hostapd[172951]: Failed to set up interface with /etc/hostapd/hostapd.conf
Nov 03 09:36:56 VideoNASty hostapd[172951]: Failed to initialize interface
Nov 03 09:36:56 VideoNASty systemd[1]: hostapd.service: Control process exited, code=exited, status=1/FAILURE
Nov 03 09:36:56 VideoNASty systemd[1]: hostapd.service: Failed with result 'exit-code'.
Nov 03 09:36:56 VideoNASty systemd[1]: Failed to start Access point and authentication server for Wi-Fi and Ethernet.

`
root@VideoNASty:~# sudo systemctl disable hostapd
Synchronizing state of hostapd.service with SysV service script with /lib/systemd/systemd-sysv-install.
Executing: /lib/systemd/systemd-sysv-install disable hostapd
Removed /etc/systemd/system/multi-user.target.wants/hostapd.service.
`
`root@VideoNASty:~# chmod 777 "/media/spudgun/4TB USB HD"`

@ophub
Copy link
Owner
ophub commented Nov 3, 2022

It is recommended not to use spaces in the directory name, there will be some software incompatibility problems.

4TB_USB_HD

@ophub ophub closed this as completed Nov 4, 2022
@JBHudston
Copy link
Author

I have renamed the drive without spaces.

The Wi-Fi error has stopped now.

However the share still drops randomly.
Also I don’t get log files for the FireTV boxes that access the share via Kodi. Why would this be?

@ophub
Copy link
Owner
ophub commented Nov 4, 2022

Turn off automatic hibernation for shared hard drives.
Mount with uuid, not lable.
Open the log in kodi and save it to a fixed path.

@JBHudston
Copy link
Author

I believe I have already disabled auto hibernation: In Gnome settings>Power>Power Saving Options.Screen Blank = Never?

Should Mount options be (UUID=123456789):
Mount Point = /mnt/123456789
Identify As = UUID=123456789

I've also set Mount at Startup = On

I'll post the log from kodi

@ophub
Copy link
Owner
ophub commented Nov 4, 2022

blkid

write to:
/etc/fstab

@JBHudston
Copy link
Author
JBHudston commented Nov 4, 2022 •
edited by ophub
Loading 
root@VideoNASty:~# blkid
/dev/mmcblk2p1: SEC_TYPE="msdos" LABEL_FATBOOT="BOOT_EMMC" LABEL="BOOT_EMMC" UUID="7EDD-ED4D" BLOCK_SIZE="512" TYPE="vfat"
/dev/mmcblk2p2: LABEL="ROOTFS_EMMC" UUID="f33e65f2-a814-4397-82c6-6e13f38e3636" BLOCK_SIZE="4096" TYPE="ext4"
/dev/zram0: UUID="312b4f0c-eb8a-4cbd-8fdf-38a7af9f0a34" TYPE="swap"
/dev/zram1: LABEL="log2ram" UUID="291d8bda-354b-407c-984a-fcb759288fa7" BLOCK_SIZE="4096" TYPE="ext4"
/dev/zram2: LABEL="tmp" UUID="63444e5d-0146-4d24-8964-3d26bcc152e0" BLOCK_SIZE="4096" TYPE="ext4"
/dev/sda1: LABEL="4TB" BLOCK_SIZE="512" UUID="46A028775931E054" TYPE="ntfs" PARTUUID="53487fb5-959f-4346-8d82-fdbd68b85e9a"

@JBHudston
Copy link
Author

sudo nano /etc/fstab

UUID=f33e65f2-a814-4397-82c6-6e13f38e3636  /        ext4     defaults,noatime,errors=remount-ro     0 1
LABEL=BOOT_EMMC      /boot    vfat                    defaults                  0 2
tmpfs                /tmp     tmpfs                   defaults,nosuid           0 0
UUID=46A028775931E054 /mnt/46A028775931E054 auto nosuid,nodev,nofail,x-gvfs-show 0 0

@ophub
Copy link
Owner
ophub commented Nov 4, 2022

The ntfs format is not well supported under linux, ext4 and btrfs are recommended

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@ophub @JBHudston