Jazmodo

I've had a very strange issue with this docker twice now over the past few days. Having installed and trying to set up, I've not been able to successfully get replies from the chat/browser, and in trying to get the most basic of replies through the Anthropic API, I've had a major issue that required a restart, both times. The docker/program will hang, followed by all of my unraid 'shares' disappearing, and things slowly starting to break in other dockers as they attempt to access the /mnt/user/ share. Strangely, I can still browse my files via the 'Main' tab, but /mnt/user/ in particular (possibly others) was not visible/working. In both instances, uninstalling openclaw, and performing a full reboot, fixed the shares. I otherwise run dozens of other dockers 24/7, many with internet access (via reverse proxy), and the server is showing no other errors, not disk/ram errors. And given the issue was repeatable, it does lead me to think this openclaw docker is somehow to blame. A) What could cause the openclaw docker to do this? and B) is it me doing something wrong, or something not quite right with the docker, or openclaw itself? If it wasn't repeatable, I'd be thinking some kind of RAM issue, but as above, uninstalling openclaw & rebooting after has fixed it twice now. Edit: Same issue, I couldn't get a reply, using anthropic/claude either

Good to know, I'll try and run an extended SMART test, see what shows up. I chatGPT'd (forgive me...) the errors - it suggested to monitor, but also these errors (as both drives show the same sector & same error) that it could have been caused by refurbishing processes - is this possible, or are these likely old drives that have just started to fail? The below current, normal SMART test looks ok though? # Attribute Name Flag Value Worst Threshold Type Updated Failed Raw Value 1 Raw read error rate 0x000b 100 100 001 Pre-fail Always Never 0 2 Throughput performance 0x0005 136 136 054 Pre-fail Offline Never 96 3 Spin up time 0x0007 099 099 001 Pre-fail Always Never 66 4 Start stop count 0x0012 100 100 000 Old age Always Never 2 5 Reallocated sector count 0x0033 100 100 001 Pre-fail Always Never 0 7 Seek error rate 0x000b 100 100 001 Pre-fail Always Never 0 8 Seek time performance 0x0005 140 140 020 Pre-fail Offline Never 15 9 Power on hours 0x0012 100 100 000 Old age Always Never 239 (9d, 23h) 10 Spin retry count 0x0013 100 100 001 Pre-fail Always Never 0 12 Power cycle count 0x0032 100 100 000 Old age Always Never 2 22 Helium level 0x0023 100 100 025 Pre-fail Always Never 100 192 Power-off retract count 0x0032 100 100 000 Old age Always Never 11 193 Load cycle count 0x0012 100 100 000 Old age Always Never 11 194 Temperature celsius 0x0002 059 059 000 Old age Always Never 35 (min/max 22/40) 196 Reallocated event count 0x0032 100 100 000 Old age Always Never 0 197 Current pending sector 0x0022 100 100 000 Old age Always Never 0 198 Offline uncorrectable 0x0008 100 100 000 Old age Offline Never 0 199 UDMA CRC error count 0x000a 100 100 000 Old age Always Never 0

Purchased a couple of 'new' HDDs from an unusual source (website in Singapore with limited history) - 2x 18TB WD HC550s - sold to me as new. Given their price, I expected cold spares and/or manufacturer refurbished. Anyhow, got the drives & installed them, working fine and no immediate errors after a quick smart test, and ran preclear on one of them I think. But I've been looking at the drives SMART error logs, and they show the following: ATA Error Count: 88 (device log contains only the most recent five errors) & ATA Error Count: 105 (device log contains only the most recent five errors) All 10 (5 each) of the errors I can see all are the same: Error 105 occurred at disk power-on lifetime: 0 hours (0 days + 0 hours) When the command that caused the error occurred, the device was active or idle. After command completion occurred, registers were: ER ST SC SN CL CH DH -- -- -- -- -- -- -- 40 43 00 00 00 00 00 Error: UNC at LBA = 0x00000000 = 0 Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name -- -- -- -- -- -- -- -- ---------------- -------------------- 60 08 00 00 00 00 40 00 00:04:20.472 READ FPDMA QUEUED ef 10 02 00 00 00 00 00 00:04:20.334 SET FEATURES [Enable SATA feature] ef aa 00 00 00 00 00 00 00:04:20.334 SET FEATURES [Enable read look-ahead] ef 03 46 00 00 00 00 00 00:04:20.334 SET FEATURES [Set transfer mode] ef 03 0c 00 00 00 00 00 00:04:20.152 SET FEATURES [Set transfer mode] All error occurred at 0 Hours, and all are the same error: uncorrectable read errors at LBA 0 - thoughts?

I've had this happen twice now in the past couple of weeks, Server continues to operate fine in the background - HomeAssistant/Z2M/Zwave/Plex/SWAG/Nextcloud/MariaDB/all other Dockers seemed unaffected, but GUI was missing parts. Issues such as: All array discs, pool ssds, and even flash drive not showing at all under the 'Main' tab All discs/ssds missing from 'Dashboard' tab Other components of 'Dashboard' tab glitched, such as percentage bars/graph for CPU/RAM etc not working 'Shares' tab seemed unaffected reloading either page within Chrome tab didn't work reloading in an incognito Chrome tab didn't work reloading in either Safari (different browser) or mobile Chrome (different IP) didn't work Logs nor Terminal work via buttons in GUI (top right buttons) Logs are visible if viewed via Tools>System Log however The logs showed mostly the same 4-6 messages: ngx_slab_alloc() failed: no memory shpool alloc failed nchan: Out of shared memory while allocating channel /temperature. Increase nchan_max_reserved_memory. *1798536 nchan: error publishing message (HTTP status code 507), client: unix:, server: , request: "POST /pub/cpuload?buffer_length=1 HTTP/1.1", host: "localhost" kernel: nginx[25247]: segfault at 0 ip 0000000000000000 sp 00007ffc32198c58 error 14 in nginx[400000+24000] likely on CPU 8 (core 4, socket 0) kernel: Code: Unable to access opcode bytes at 0xffffffffffffffd6. Both times, a full restart resolved the GUI issues, and the repeated errors in the log. Yes, I do leave 1-2 tabs open with Unraid most of the time... Could this be the main cause? Logs from before restart attached Unraid Syslog 14.08.24 GUI Freeze

Ok - well A) I shouldn't have panicked & B) I should've read more before posting. Wiped the broken/corrupt Docker.img using the docker settings, then just restarted to build a new blank docker.img Reinstalled all dockers using the 'Previous Apps' in the App tab, which also had all ports/settings saved - Godsend, was my biggest worry - all the configs & settings I shoud've screenshot, but didn't. Small issued with Swag, MariaDB, HomeAssistant, Zigbee2MQTT, and Mosquitto - but all seem to be working internally & externally again. Relief...

These logs indicated the issue, but now all the dockers have completely vanished: rc.docker: nextcloud: Error response from daemon: stat /var/lib/docker/btrfs/subvolumes/0a818820b2c6ac7a48acd4bdda2b933b9d57390e230e4136467e2f64e02a69c1: no such file or directory Aug 29 16:58:22 rc.docker: Error: failed to start containers: nextcloud Aug 29 16:58:22 rc.docker: nzbgetvpn: Error response from daemon: stat /var/lib/docker/btrfs/subvolumes/e906cbb8b9e0a3d56bd4112fa212c566908de681b5feae69c2858e83278ad0b8: no such file or directory I then tried to follow this: I did (luckily?) download a copy of the docker.img, but having tried putting the docker in the old & a new location, none of the dockers are even showing. Bit of a newbie when it comes to this, so maybe I've just broken everything and need to start again... but hopefully not.

As the title says.... been tinkering a lot recently. Last night I was trying to trim down the docker file, as it appeared too large. Somethings gone wrong, and all my dockers stopped working. I rebooted the server, and all the dockers went offline, couldn't restart them. I turned off the Docker in settings, and turned it back on again - now everything has gone? I still have a docker.img in system/docker.... but no idea what to do now, scared I'll break things further. Can post logs/screenshots if anyone can advise/help/assist

I've come a long way in the past few months, from building my first PC/Server earlier this year, I've now done the following: Unraid set up & running, Plex set up with associated Dockers (NZB/BT), NextCloud set up, with Swag for remote access/backup (via DuckDNS & Cloudflare), and finally Home Assistant Docker, with a Zigbee2MQTT & Mosquitto Dockers to run the Zigbee devices directly So quite a bit done, but I'm admittedly very new when it comes to Linux & networking, and have finally hit a problem I can't seem to find a ready solution for. Long story short, I want to enable remote access to my Home Assistant docker, but the NextCloud remote access is already using the same ports, and Swag (reverse proxy?). It would seem I should configure Home Assistant in a similar way to NextCloud - through Swag, and DuckDNS.... But how would I do this? There seems to be a good guide here: https://community.home-assistant.io/t/remote-access-with-docker/314345 but uses the same ports as my Nextcloud config, so I'm a little lost. Anyone able to offer some tips/suggestions? 🙏