extremeaudio

smart test extended result attached. MAIN shows no errors now. smart-20240415-1107.zip

Diagnostics attached. On a side note, I am also unable to update unraid. The page is blank. Should I just manually copy paste the bz* files? Can this be done with server running? diagnostics-20240411-2108.zip

In the MAIN view, one of the disks is showing 400 something errors, in the errors column after reads and writes. There is no disk disabled or anything. What is the process to clear this? As far as I remember I had run a parity check after this with write correction to disk enabled but this still shows.

I downgraded manually from 6.12 to 6.11 because zerotier does not work properly on 6.12 Now after booting the docker containers are all stopped. If I try to manually start it says "Server Error Execution Error" How to fix this? Diag attached. diagnostics-20240319-2159.zip

Sorry for being really dumb about this but my docker knowledge is very limited. The stack used is as below. Where do you think I could possibly retrieve the data from? And I hope I didnt overwrite the data since I have tried to start the stack since Any suggestions? version: "3" services: ztncui: image: keynetworks/ztncui container_name: ztncui environment: - USER_UID=99 #adjust to your system - USER_GID=100 #adjust to your system - NODE_ENV=production - HTTPS_PORT=3443 - ZTNCUI_PASSWD=******** #change this volumes: - ztncui:/opt/key-networks/ztncui/etc - zt1:/var/lib/zerotier-one ports: - 3443:3443 #dashboard port - 3180:3180

I have reconnected using SATA. Everything seems to be restoring fine except the userdata of the container added to portainer using stacks, outside of unraid app store. Any idea where this might be stored? In the docker.img itself? When I try to copy back the old docker.img I had backed up, the web UI hangs. I can only create the new docker img but then old data is lost.

Dockers disappeared again. akserver-diagnostics-20240125-1233.zip

This is not related dorectly to unraid, but I would be glad if someone helped me out. I installed zerotier controller on unraid using stacks in portainer-ce docker installed from the unraid app store. Now when I restore from the appdata backup and reinstall portainer from user templates, portainer installs properly and also shows a stack called ztncui which is the correct one. But ideally there should have been networks etc which is the userdata of that container. But I cant see that. Any way to restore that? In additon to the backup created by appdata backup plugin I also have a copy of the appdata folder and docker.img saved away, in case that helps restore the data any better.

Now the docker starts. But when I am installing from user templates the user data is not showing. The containers seem to be installing at default. Actually I'm not sure. Some containers seem ok. Others seem default. Cant be that way, right?

No it does not create a user template. So should restoring the appdata using the appdata backup/ restore plugin recreate the previous state? Just reseated everything and restarted. All looks ok now? Diag attached. akserver-diagnostics-20240122-1523.zip

Deleted the docker img, re created it and docker service started fine. Now I get some read only filesystem error when trying to install dockers. Btw will all the dockers be restored back perfectly when reinstalled using user template? I also had a zerotier controller docker installed from outside the unraid app store by using stacks in portainer I believe. So should installing portainer with the user template restore that docker? diag attached. akserver-diagnostics-20240121-1922.zip

syslog attached.syslog-192.168.1.49.log

Yes, within a few seconds of trying to start docker. Docker does not start.

I removed one of the 2 RAM sticks suspecting a bad RAM and had forgotten to put it back as the problem still persisted. With docker disabled the server is working fine. When should I issue this? Should I start docker now and immediately do this? Currently the output of that command is as below df -h Filesystem Size Used Avail Use% Mounted on rootfs 3.8G 232M 3.5G 7% / tmpfs 32M 520K 32M 2% /run /dev/sda1 29G 830M 28G 3% /boot overlay 3.8G 232M 3.5G 7% /lib overlay 3.8G 232M 3.5G 7% /usr devtmpfs 8.0M 0 8.0M 0% /dev tmpfs 3.8G 0 3.8G 0% /dev/shm tmpfs 128M 224K 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 7.3T 5.7T 1.7T 78% /mnt/disk1 /dev/md2p1 7.3T 6.8T 504G 94% /mnt/disk2 /dev/md3p1 7.3T 305G 7.0T 5% /mnt/disk3 /dev/sdb1 75G 35G 40G 47% /mnt/cache shfs 22T 13T 9.2T 59% /mnt/user0 shfs 22T 13T 9.2T 59% /mnt/user tmpfs 762M 0 762M 0% /run/user/0

I tried typing diagnostics with a keyboard attached to the tower again but same result. The screen says the file is saved but there is none in the flash. Pic attached. After that I booted using the flash by disabling docker and saved a diagnostics that is attached. Then I enabled docker from the web UI and attempted another diagnostics download which failed midway, presumably as the web UI and whichever other devices went down. The text that showed in the diagnostics pop up window are pasted in the text file attached. akserver-diagnostics-20240117-1310.zip failed diagnostics.txt

My tower cache disk became undetectable. So I swapped around a few cache disks till I realised a cable was faulty. The data disks are fine. After starting back up the tower web UI becomes unaccessible when trying to start docker. Unable to access the tower via putty from another machine too. Fortunately terminal on the tower itself works. So I typed diagnostics at the terminal. But after a message that said some /log file exists and saying that it is collecting diagnostics for a minute or so, there is no diagnostics zip on the flash drive. What do I do? I have tried checking the flash for errors. Nothing there.

So how do i shut down the server? Or should I pull it out while live?

I get the message "Flash drive corrupted or offline, post your diagnostics on the forum" Attached herewith akserver-diagnostics-20231008-1839.zip

Even tried using another sata cable. Could it be a bad port on the mobo?

diagnostics attached. Docker isnt starting and gives a message saying array needs to be started for docker. But array is already started. EDIT: Sorry, array is stuck at starting, and the cache disk seems to be holding it up. diagnostics-20230228-1251.zip

Warning: stream_socket_client(): unable to connect to unix:///var/run/docker.sock (Connection refused) in /usr/local/emhttp/plugins/dynamix.docker.manager/include/DockerClient.php on line 712 Couldn't create socket: [111] Connection refused Warning: Invalid argument supplied for foreach() in /usr/local/emhttp/plugins/dynamix.docker.manager/include/DockerClient.php on line 898 Warning: stream_socket_client(): unable to connect to unix:///var/run/docker.sock (Connection refused) in /usr/local/emhttp/plugins/dynamix.docker.manager/include/DockerClient.php on line 712 Couldn't create socket: [111] Connection refused Warning: Invalid argument supplied for foreach() in /usr/local/emhttp/plugins/dynamix.docker.manager/include/DockerClient.php on line 967 Docker keeps stopping. Deleted the image once and recreated but happened again. Any suggestions?

As title suggests, the plugin said it detects hardware errors. I have replaced a sata expander just recently. Dont know why the error is still there. Diag attached. akserver-diagnostics-20230112-1414.zip

Never mind. I think the container was updating or it was awaiting a reboot. After a reboot the data is all restored. WHEW!

In the ztncui documentation they say Copy data of ztncui (/opt/key-networks/ztncui/etc) and ZT controler (/var/lib/zerotier-one). Where do I find this in unraid?

Update 3: Copied the contents of the old cache disk over to the new disk. Unassigned the cache disk. Started array. Stopped the array. Assigned the new cache disk with the exact contents as the old cache disk. Started the array. Docker tab looks fine with all the dockers. All dockers start including the ztncui one. But unable to get to the web UI.