mark_s_maynard

Hi, about a week ago i started getting docker crashes where every service would fail and restart, during this the gui was also unreachable. it would then continue to do this until rebooted, then it would apprear to be fine for a certain amount of time and then do it all over again with the same results, after a few times it also disabled a disk due to connection issues. i was doing some maintenance on my gaming pc at the same time and noticed that the intake fan had died so assumed this was the cause and temps were making it die, so i re pasted the cpu and added a new intake fan and also replaced all the sata cables with new more reputable ones with the intention of rebuilding the drive and hoping everything would be fine now. unfortunately its the same issue again and i was hoping for some guidance on what to do. i will add diagnostics maynardserver-diagnostics-20250618-1246.zip

Thankyou i have started a new docker.img and all seems to be working now. was there any indication as to how it happened or how to prevent it happening again?

hi guys ive rebooted my system today and when it started back up the docker service failed to start and the logs show this error wrong fs type, bad option, bad superblock on /dev/loop3, missing codepage or helper program, or other error. ive checked the disks and tried deleting the docker.img file and tried to restart and i cant get anywhere and google isnt helping. does anyone have any idea where to start? im pulling my hair out maynardserver-diagnostics-20241106-2108.zip

OK thankyou

@itimpi did the logs give you any indication as to what the problem was?

sorry just realised that will be the ram version this is whats in the syslog on os usb. let me know if im looking in the wrong place maynardserver-diagnostics-20240105-0634 (1).zip maynardserver-diagnostics-20240104-0811.zip

hi i told it to mirror and also told it to write the logs to my server but at a quick glance before work im not sure it actually did as the arliest log i could find was shortly after the reboot yesterday. i will post anyway as i dont really know what im looking for maynardserver-diagnostics-20240105-0634.zip

Version: 6.12.6 like above every time i wake up for the last 3 mornings unraid is inaccessible via ssh or gui no docker or vms are running and i have to reboot the server. everything else works as it should but something is crashing the system overnight and i have no idea what. i cant check the logs as they are wiped on reboot. the main reason i cant think of is that maybe it is the appdata backup plugin or mover running overnight causing it but those are wild guesses and it only because they are the actions that run overnoght. any help would be greatly appreciated maynardserver-diagnostics-20240104-0811.zip

i had some issues a few months back and managed to fix them due to some help from someone here but ever since ive realised the cache never empties, at first i used unbalance and then the file manager to move files over manually when the drive got full but i realised that when moving files over some were not making the cut and my video library had missing files etc or i would go to watch a film and realise the file was missing even though it had download history in radarr etc. i was hoping someone could tell me what i have configured wrong and the best practice to fix it wether a fresh start or simple config change. thanks in advance. maynardserver-diagnostics-20231104-1326.zip

my daughter accidentally knocked an external drive in the array causing a loose connection causing it to become disabled and emulated. is there a way to just tell unraid to continue as normal as i know the data is fine and isnt critical data and easily replaced i dont want to wait days for it to rebuild?

ok took me a while to figure out xfs repair but i ran it and running -n now doesnt spit any errors so im going to spin it up and fingers crossed it will all work fine now, thankyou for your help

due to deprecated plugin and not checking on my part the entire appdata folder was cleared out and have to start from scratch anyway. so providing im not overly concerned about the appdata folder if i remove the troublesome drive and start again and run xfs_repair you think i should be back up and running. also sorry to be a noob but how do i run xfs repair? is it gui or cmdline?

that device shldnt be part of the pool im not sure how that happened and it only has 4.75 mb on it. i have removed it completely as i dont really have any need for it

i can do that later as i am not near the server but its not part of the array or cache its an unused seperate cache

cache is nvme in m.2 slot find attached result of check filesystem and new diagnostic disk 8 check.txt maynardserver-diagnostics-20230808-1245.zip