January 15Jan 15 Hello everyone,In the last few months and weeks, I get more and more often the problem, that my SMB shares are not working, when I then try to open the unraid dashboard I am stuck in the Login screen (I can enter my credentials but I get instantly redirected to the login without seeing my dashboard).I can access my server via ssh and restart the samba shares with '/etc/rc.d/rc.samba restart' but I am not able to restart my Dashboard. At the beginning this was very rarely the case but know I had this issue 3 times in 1 week. All my dockers like Jellyfin, Homar, nextcloud still work fine, as far as i noticed only samba and the dashboard are affected. Today before restarting my server i typed 'diagnostics' in ssh and hope that someone here can tell me what’s wrong with my system.This is the output that came when I entered the diagnostics command (zip file uploaded): diagnostics Starting diagnostics collection... tail: write error: No space left on device echo: write error: No space left on device echo: write error: No space left on device echo: write error: No space left on device echo: write error: No space left on device echo: write error: No space left on device echo: write error: No space left on device echo: write error: No space left on device echo: write error: No space left on device echo: write error: No space left on device echo: write error: No space left on device tr: write error: No space left on device done. ZIP file '/boot/logs/tower-diagnostics-20260115-1153.zip' created.All my drives at least got a few 100gb of free space except my boot drive with only 8gb where 6gb are freeThanks in Advance for all your expertise. tower-diagnostics-20260115-1153.zip
January 15Jan 15 Author df -h Filesystem Size Used Avail Use% Mounted on rootfs 7.7G 1.3G 6.5G 17% / tmpfs 128M 5.9M 123M 5% /run /dev/sdb1 7.6G 1.2G 6.4G 15% /boot overlay 7.7G 1.3G 6.5G 17% /lib overlay 7.7G 1.3G 6.5G 17% /usr devtmpfs 8.0M 0 8.0M 0% /dev tmpfs 7.8G 0 7.8G 0% /dev/shm tmpfs 128M 424K 128M 1% /var/log tmpfs 1.0M 0 1.0M 0% /mnt/disks tmpfs 1.0M 0 1.0M 0% /mnt/remotes tmpfs 1.0M 0 1.0M 0% /mnt/addons tmpfs 1.0M 0 1.0M 0% /mnt/rootshare /dev/md1p1 448G 4.1M 446G 1% /mnt/disk1 /dev/md2p1 9.1T 8.8T 320G 97% /mnt/disk2 disk3 3.5T 128K 3.5T 1% /mnt/disk3 /dev/md4p1 15T 9.2T 5.4T 64% /mnt/disk4 /dev/nvme0n1p1 477G 98G 377G 21% /mnt/cache disk3/Backup Share 9.0T 5.6T 3.5T 62% /mnt/disk3/Backup Share shfs 34T 24T 9.6T 72% /mnt/user0 shfs 34T 24T 9.6T 72% /mnt/user tmpfs 1.6G 0 1.6G 0% /run/user/0
January 15Jan 15 Community Expert 29 minutes ago, Herbert Horst said:tmpfs 1.6G 0 1.6G 0% /run/user/0Do you know what this is? It's not stock
January 15Jan 15 Author 20 minutes ago, JorgeB said:Do you know what this is? It's not stockI have no clue to be honest what this is. When setting up my server I did read in a thread that I can create a Ram disk so my docker logs are not written instantly all the time but are stored in ram and only every 30minutes written to disk, but I'm pretty sure this is not a result from that. I also checked these tmpfs are instantly after a reboot there, even when the array is still starting and mounting the disks (no dockers running at that moment) they are allready there.
January 15Jan 15 Community Expert The other ones are normal, the last one is not, at least AFAIK. The diags are completely empty, try booting in safe mode and check if that is created and/or if you can get the diags from there.
January 16Jan 16 Author Booting in safe mode and it is still there. What do you mean with 21 hours ago, JorgeB said:if you can get the diags from there.I'm almost certan you did'nt mean this but I did it anyway to be sure 🙃root@--:/run/user/0# ls root@--:/run/user/0# diagnostics Starting diagnostics collection... tail: write error: No space left on device echo: write error: No space left on device echo: write error: No space left on device echo: write error: No space left on device echo: write error: No space left on device echo: write error: No space left on device echo: write error: No space left on device echo: write error: No space left on device echo: write error: No space left on device echo: write error: No space left on device echo: write error: No space left on device tr: write error: No space left on device done. ZIP file '/boot/logs/tower-diagnostics-20260116-1605.zip' created.Here the output of df -h while in safe mode while the array is stopped: Filesystem Size Used Avail Use% Mounted on rootfs 7.7G 99M 7.6G 2% / tmpfs 128M 5.1M 123M 4% /run /dev/sdb1 7.6G 1.2G 6.5G 15% /boot overlay 7.7G 99M 7.6G 2% /lib overlay 7.7G 99M 7.6G 2% /usr devtmpfs 8.0M 0 8.0M 0% /dev tmpfs 7.8G 0 7.8G 0% /dev/shm tmpfs 128M 212K 128M 1% /var/log tmpfs 1.6G 0 1.6G 0% /run/user/0 tower-diagnostics-20260116-1605.zip
January 16Jan 16 Community Expert 42 minutes ago, Herbert Horst said:I'm almost certan you did'nt mean this but I did it anyway to be sureI meant get the diags from safe mode.Diags are still empty, and since you are using an older version, safe mode will still load the go file. Post the output from:cat /boot/config/go
January 16Jan 16 Author cat /boot/config/go #!/bin/bash # Start the Management Utility /usr/local/sbin/emhttp & # ------------------------------------------------- # RAM-Disk for Docker json/log files v1.4 # ------------------------------------------------- # create RAM-Disk on starting the docker service sed -i '/^ echo "starting \$BASE ..."$/i \ # move json/logs to ram disk\ rsync -aH --delete /var/lib/docker/containers/ ${DOCKER_APP_CONFIG_PATH%/}/containers_backup\ mountpoint -q /var/lib/docker/containers || mount -t tmpfs tmpfs /var/lib/docker/containers || logger -t docker Error: RAM-Disk could not be mounted!\ rsync -aH --delete ${DOCKER_APP_CONFIG_PATH%/}/containers_backup/ /var/lib/docker/containers\ logger -t docker RAM-Disk created' /etc/rc.d/rc.docker # remove RAM-Disk on stopping the docker service sed -i '/^ # tear down the bridge$/i \ # backup json/logs and remove RAM-Disk\ rsync -aH --delete /var/lib/docker/containers/ ${DOCKER_APP_CONFIG_PATH%/}/containers_backup\ umount /var/lib/docker/containers || logger -t docker Error: RAM-Disk could not be unmounted!\ rsync -aH --delete ${DOCKER_APP_CONFIG_PATH%/}/containers_backup/ /var/lib/docker/containers\ if [[ -d /var/lib/docker_bind ]]; then umount /var/lib/docker_bind || logger -t docker Error: RAM-Disk bind unmount failed while docker stops!; fi\ logger -t docker RAM-Disk removed' /etc/rc.d/rc.docker # Automatically backup Docker RAM-Disk sed -i '/^<?PHP$/a \ $sync_interval_minutes=30;\ if ( ! ((date("i") * date("H") * 60 + date("i")) % $sync_interval_minutes) && file_exists("/var/lib/docker/containers")) {\ exec("\ [[ ! -d /var/lib/docker_bind ]] && mkdir /var/lib/docker_bind\ if ! mountpoint -q /var/lib/docker_bind; then\ if ! mount --bind /var/lib/docker /var/lib/docker_bind; then\ logger -t docker Error: RAM-Disk bind mount failed!\ fi\ fi\ if mountpoint -q /var/lib/docker_bind; then\ rsync -aH --delete /var/lib/docker/containers/ /var/lib/docker_bind/containers && logger -t docker Success: Backup of RAM-Disk created.\ umount -l /var/lib/docker_bind\ else\ logger -t docker Error: RAM-Disk bind mount failed!\ fi\ ");\Would you recommend to upgrade my system? I only check every few months on new updates instead of installing them right away but since I got problems right now maybe it would be smart to upgrade unraid to the latest version.
January 16Jan 16 Community Expert Solution Recommend replacing that go file with the stock one and retesting, which is just this:#!/bin/bash # Start the Management Utility /usr/local/sbin/emhttp &
January 16Jan 16 Author Now it's gone, so it was there because of the docker logs stuff.I replaced it with the stock, restarted and will write an update in 1 or 2 Weeks if the Problem with SMB and the Login still happens. df -h Filesystem Size Used Avail Use% Mounted on rootfs 7.7G 1.2G 6.6G 16% / tmpfs 128M 5.2M 123M 5% /run /dev/sdb1 7.6G 1.2G 6.5G 15% /boot overlay 7.7G 1.2G 6.6G 16% /lib overlay 7.7G 1.2G 6.6G 16% /usr devtmpfs 8.0M 0 8.0M 0% /dev tmpfs 7.8G 0 7.8G 0% /dev/shm tmpfs 128M 352K 128M 1% /var/log tmpfs 1.0M 0 1.0M 0% /mnt/disks tmpfs 1.0M 0 1.0M 0% /mnt/remotes tmpfs 1.0M 0 1.0M 0% /mnt/addons tmpfs 1.0M 0 1.0M 0% /mnt/rootshare /dev/md1p1 448G 4.1M 446G 1% /mnt/disk1 tmpfs 1.6G 0 1.6G 0% /run/user/0 /dev/md2p1 9.1T 8.9T 292G 97% /mnt/disk2EDIT: Correction It is still there, I just overlooked it. Also Today (20 hours later) I still got the same Problem.Linux 6.1.79-Unraid. root@--:~# diagnostics Starting diagnostics collection... tail: write error: No space left on device echo: write error: No space left on device echo: write error: No space left on device echo: write error: No space left on device echo: write error: No space left on device echo: write error: No space left on device echo: write error: No space left on device echo: write error: No space left on device echo: write error: No space left on device echo: write error: No space left on device echo: write error: No space left on device tr: write error: No space left on device done. ZIP file '/boot/logs/tower-diagnostics-20260117-1404.zip' created. root@--:~# root@--:~# df -h Filesystem Size Used Avail Use% Mounted on rootfs 7.7G 7.7G 0 100% / tmpfs 128M 5.9M 123M 5% /run /dev/sdb1 7.6G 1.1G 6.5G 15% /boot overlay 7.7G 7.7G 0 100% /lib overlay 7.7G 7.7G 0 100% /usr devtmpfs 8.0M 0 8.0M 0% /dev tmpfs 7.8G 0 7.8G 0% /dev/shm tmpfs 128M 6.8M 122M 6% /var/log tmpfs 1.0M 0 1.0M 0% /mnt/disks tmpfs 1.0M 0 1.0M 0% /mnt/remotes tmpfs 1.0M 0 1.0M 0% /mnt/addons tmpfs 1.0M 0 1.0M 0% /mnt/rootshare /dev/md1p1 448G 4.1M 446G 1% /mnt/disk1 /dev/md2p1 9.1T 8.9T 290G 97% /mnt/disk2 disk3 3.3T 128K 3.3T 1% /mnt/disk3 /dev/md4p1 15T 9.2T 5.4T 64% /mnt/disk4 /dev/nvme0n1p1 477G 106G 370G 23% /mnt/cache disk3/Backup Share 9.0T 5.7T 3.3T 64% /mnt/disk3/Backup Share shfs 34T 24T 9.4T 72% /mnt/user0 shfs 34T 24T 9.4T 72% /mnt/user tmpfs 1.6G 0 1.6G 0% /run/user/0 root@--:~# cat /boot/config/go #!/bin/bash # Start the Management Utility /usr/local/sbin/emhttp & root@--:~# tower-diagnostics-20260117-1404.zip Edited January 17Jan 17 by Herbert Horst Add new information
Sunday at 08:51 PM1 day Author Duno why the last change didnt work but then after a last time with the error then it dissappeard forever (or at least until now) thanks
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.