jdiacobbo

After recreating the docker image I woke up this morning to most (but not all) of my docker images stopped. I tried to restart them and got Execution error Error code 403 Looking at the syslogs I see BTRFS error (device nvme0n1p1): block=7008911360 write time tree block corruption detected I've attached the full syslogs from the last 4 days. *EDIT* Trying to restart Docker gives me this error Docker Service failed to start. syslog-192.168.0.150.log

The syslog server is how I got the attached logs. I just cut it to the part where the issue occurred. Should I post the whole log? Sent from my Pixel 8 using Tapatalk

From what I can tell it appears that I may need to delete and rebuild my docker image. I'm going to try that now and see if stability improves. If someone could confirm this is indeed my issue from what you can see in the logs I'd appreciate the confirmation.

Starting about a week ago my server started crashing every few days. I was able to capture the logs on the most recent crash and noticed there were many lines referencing a BTRFS issue. Any ideas whats causing this and how to resolve it? syslog errors: Dec 17 05:26:00 Tower kernel: BTRFS critical (device loop2): corrupt leaf: block=48136192 slot=140 extent bytenr=1060425728 len=8192 invalid data ref offset, have 4294936705 expect aligned to 4096 Dec 17 05:26:00 Tower kernel: BTRFS info (device loop2): leaf 48136192 gen 2207042 total ptrs 148 free space 4594 owner 2 Dec 17 05:26:00 Tower kernel: #011item 0 key (1059401728 168 16384) itemoff 16230 itemsize 53 Dec 17 05:26:00 Tower kernel: #011#011extent refs 1 gen 2084816 flags 1 Dec 17 05:26:00 Tower kernel: #011#011ref#0: extent data backref root 10841 objectid 12509 offset 37146624 count 1 Dec 17 05:26:00 Tower kernel: #011item 1 key (1059418112 168 4096) itemoff 16177 itemsize 53 Dec 17 05:26:00 Tower kernel: #011#011extent refs 1 gen 1407781 flags 1 Dec 17 05:26:00 Tower kernel: #011#011ref#0: extent data backref root 7995 objectid 17690 offset 0 count 1 Dec 17 05:26:00 Tower kernel: #011item 2 key (1059422208 168 4096) itemoff 16124 itemsize 53 ... Dec 17 05:26:00 Tower kernel: BTRFS error (device loop2): block=48136192 write time tree block corruption detected Dec 17 05:26:00 Tower kernel: BTRFS: error (device loop2) in btrfs_commit_transaction:2460: errno=-5 IO failure (Error while writing out transaction) Dec 17 05:26:00 Tower kernel: BTRFS info (device loop2: state E): forced readonly Dec 17 05:26:00 Tower kernel: BTRFS warning (device loop2: state E): Skipping commit of aborted transaction. Dec 17 05:26:00 Tower kernel: BTRFS: error (device loop2: state EA) in cleanup_transaction:1958: errno=-5 IO failure unraid_syslog_crash.txt tower-diagnostics-20231215-1623.zip

Pardon my ignorance but how would I be able to edit the run command for the CA container to remove this variable? **edit** I just ended up running the command in the terminal which worked.

This resolved the 'no such file' error. Still getting the database error with the Community Apps container install. If you are not getting that error with Docker Compose then would that suggest the issue is with the CA template?

Getting the following error after updating to the latest docker version:

Created issue #1252 https://github.com/ghostfolio/ghostfolio/issues/1252

I am also having this same issue. I am unable to get the Data Gather tasks to complete. Checking the Postgres logs I see this updating several times a second with the same error:

I updated /ect/sensors.d/sensors.conf.save to also remove the two kraken lines and now everything is working properly.

I am having trouble adding my NZXT Kraken x62 fan to the fan array in this plugin. When I go to the plug in settings and open the drop down it shows the kraken fan and pump but when I select the fan and click apply it wipes out all of the values set and none of the dropdowns have any options available. Before selecting the fan: After selecting the fan: If I run sensors I get the error Error: File /etc/sensors.d/sensors.conf, line 25: Undeclared bus id referenced sensors_init: Can't parse bus name Checking /etc/sensors.d/sensors.conf I see the Kraken is listed on that line. If I comment it out and rescan in the plug in I get the sensor options back. Is there a way to get this fan sensor to play nice with Unraid?

I was able to get everything set up and working but the one issue I am having is getting the Varken container to autostart after reboots and after weekly container backups. I tried moving it to the top of the priority list to start first but that didn't help and there doesn't appear to be anything in the logs either. Is anyone else having this issue?

No RAID card but I am using a Dell H310 SAS HBA flashed in IT mode. Would that potentially cause any issues?

Sorry to necro an old thread but I'm planning to do the same thing and I'm wondering how you made out. Did you have any issues bringing the array back up after moving drives around? Sent from my Pixel 6 using Tapatalk

I recently update my telegraf container and now it won't start with the following error in the container logs: ERROR: Unable to lock database: Permission denied ERROR: Failed to open apk database: Permission denied It was working just fine previously to updating. Any ideas on how to fix this? **EDIT** Oh boy I should have read the previous comments. That one is on me.

Just got this set up and I believe its working correctly but I would love to see how others have configured Grafana to display the data.