-
Cache disk: Unmountable: wrong or no file system (diagnostic file included)
Server has been up and running for 1,5 days now. It seems like all is ok from my side, and I have Dockers up and running again. selje-tower-diagnostics-20260123-1017.zip If anybody wanna do a hopefully last check of the diag file I would greatly appreciate it.
-
Cache disk: Unmountable: wrong or no file system (diagnostic file included)
Hmm... Finally got my hardrives back up and running. I moved the backup of my cache - back to the cache, but I now get a message that I don't have any "No Docker containers installed". The docker.img is copied back to the cache... selje-tower-diagnostics-20260121-2348.zip
-
Cache disk: Unmountable: wrong or no file system (diagnostic file included)
Backup and reformat the cache pool then I guess? Would not a backup now of the cache pool bring the errors back into the new pool?
-
Cache disk: Unmountable: wrong or no file system (diagnostic file included)
Last 2 memory sticks comes back perfect. Here are the newest diags.selje-tower-diagnostics-20260121-1825.zip
-
Cache disk: Unmountable: wrong or no file system (diagnostic file included)
Oh, no. You were definitively right again. Several 1000 errors on the first memstick pair (the one I changed) in november. I have to pairs with 2x8gb on each stick. Running a test on the other pair now... will post result on this... And a new diag file if this pair does not fail.
-
Cache disk: Unmountable: wrong or no file system (diagnostic file included)
Ok. Will do that. If this AGAIN is memory errors, it is the 3rd time in 1 year. Wonder what to do if it is again the same thing.
-
Cache disk: Unmountable: wrong or no file system (diagnostic file included)
After doing this it seems the cache pool started up again, at least for now. Here are the diags.selje-tower-diagnostics-20260120-2047.zip
-
Cache disk: Unmountable: wrong or no file system (diagnostic file included)
Unraid have been running fine for 1,5 months now after I had to swap a few bad memory sticks. I have not been accessing it for a few weeks, but when accessing today I found none of the dockers started. Obviously because of the error my Cache drive. I tried rebooting, but I don't really understand the diagfiles. Any help on this is greatly appreciated. tower-diagnostics-20260120-0012.zip
-
[Plugin] FanCrtl Plus
Hi. So I have installed Fan Control, Dynamix Temp sensor and Nuovoton drivers to be able to see my PWM sensors. My problem is that when identifying my fans they dont turn off/turn up to 100% or pulse. I only have 3 PWM fans setup like this: The fans are what I expect the to be, I have not been able to verify for sure, but from visually checking it looks like this. My BIOS settings are like this: As you can see both chassis fans are set to PWM mode. They are also both set to CPU as "source" which probably is wrong, but I don't know what I should choose here. Any help is appreciated: These are the found PWMS, however I think there is only something available fans at 1,3 and 7. Or do I actually need to test all of them to be sure? (Just thought of this now...)
-
I can not access Unraid GUI or telnet from time to time
It certainly looks better now as far as I can see. Already packed my 2 errored ram and returning them. They were installed in January 2025, had no errors at that time. Does this make sense that they are already broken? I am getting worried Unraid is eating ram? :) syslog-Tower (5).log
-
I can not access Unraid GUI or telnet from time to time
Holy F........ I had this freaking thing 1 year ago, but not the same errors though. Thanks though. Will do it! Update: So far the two first memsticks are failing massively.... How can this happen? It is only a year ago since I changed 2 of the sticks and tested all of the. Server has just been running for 6 of the last 12 months maximum...
-
I can not access Unraid GUI or telnet from time to time
Another day, another crash. Syslog attached.syslog-Tower (271025).rar Everytime the parity check also starts... So my server is either dead or running a parity checks these days. And to my knowledge, I have done nothing specific that should cause this. My initial thought was some problems with the dockers and they hogging the network card, but I have not been running any dockers for a while now so...
-
I can not access Unraid GUI or telnet from time to time
Hmmm... I thought the syslog would continue. Should I mirror the syslog to USB, I read somewhere that that could screw up the flash disk aswell...? Will this give you more data? Anyways I restarted the syslog server I guess that is what you meant about starting a new log.
-
I can not access Unraid GUI or telnet from time to time
syslog-Tower.rarThe problem persists. I have been away for a few days, but when I returned I could not access the server again. I have not done anything else the last couple of months than to install an extra instance of wordpress, but for the last couple of crashes I am not even running those containers, as I was worried about a port conflict.
-
I can not access Unraid GUI or telnet from time to time
syslog-Tower.rarI have been away for a few days. This is the same syslog as last time but in rar format. I can see my server is not accessible yet again...
tormi
Members
-
Joined
-
Last visited