Hi everyone, I've been running the same instance of unraid for almost 8 years. Currently upgraded to 6.12. My docker had failed 3 times alone this year where I've had to delete and create a new docker.img. 

Also, the server has a tendency to "hang", where I'd still be able to remotely access some docker apps but I cannot access the unraid gui itself. This happens as often as a day after rebooting. 

I'm not sure where to begin to look. 

 

Thank you in advance

Post the diagnostics when the docker fails, for the hanging you can enable the syslog server and post that after a crash.

posting diagnostics! 

- after the latest "hang", did an unclean reboot and one disk has decided to not cooperate and seems like it has to be rebuilt. this happens probably once a year to a random drive. i have not rebuilt it yet as I want to figure out what is the cause of the system hanging

diagnostics-20230706-1117.zip

Not much to see after a reboot, you can do this:

On 6/26/2023 at 1:52 PM, JorgeB said:

for the hanging you can enable the syslog server and post that after a crash.

 

hey @JorgeBthanks for replying and checking the diagnostics. I attached a screenshot of the syslog settings I enabled when you originally posted the tutorial. The reason I attached it is because the folder (on cache) doesn't seem to have anything in it. Is there another setting that I need to enable? 

 

 

See the instructions, you need to input the server IP in the the "Remote syslog server", or just use the mirror to flash drive option.

was away for a little while and moved the system to another power source to make sure that wasnt causing the issues. server lasted 5-6 days of on time before it was unresponsive over the network. log attached.

 

3 main issues

1) server hanging

2) docker crash (was rebuilt less than a week ago)

3) upon rebooting after a hang, i cannot access the gui from my main desktop for 20-30minutes - i can only access it from my iOSl browser. (tried different browsers, incognito etc..)

syslog-192.168.2.40.log

Jul 12 12:01:13 MediaHub kernel: macvlan_broadcast+0x10a/0x150 [macvlan]
Jul 12 12:01:13 MediaHub kernel: ? _raw_spin_unlock+0x14/0x29
Jul 12 12:01:13 MediaHub kernel: macvlan_process_broadcast+0xbc/0x12f [macvlan]

 

Switching to ipvlan should fix it (Settings -> Docker Settings -> Docker custom network type -> ipvlan (advanced view must be enabled, top right)).

 

Also, and if if you haven't yet, check filesystem on this device:

 

Aug 12 02:24:12 MediaHub kernel: XFS (sdf1): Metadata corruption detected at xfs_dinode_verify+0xa0/0x732 [xfs], inode 0x6c2a77 dinode
Aug 12 02:24:12 MediaHub kernel: XFS (sdf1): Unmount and run xfs_repair

 

first of all thank you so much. appreciate the swift reply. server stopped responding over the network within 24hrs of making changes (within the last 12hrs). logs attached.

 

actions taken
- changed macvlan to ipvlan

- scanned and fixed crc errors on SDF1 (cache drive). currently no errors found. 

 

 

 

 

syslog-192.168.2.40.log

 

Unfortunately now there's nothing relevant logged, this usually points to a hardware issue, one thing you can try is to boot the server in safe mode with all docker/VMs disabled, let it run as a basic NAS for a few days, if it still crashes it's likely a hardware problem, if it doesn't start turning on the other services one by one.