skunkypete

Been running without issues since swapping out the PSU, also got myself a UPS to hopefully extend the lifespan of this new PSU.

I swapped out the PSU yesterday and have had an uptime of 16 hours which is the longest in the past few days. Going to monitor for a few days to ensure that was indeed the issue.

So I setup syslog server to write to a share I created on the cache, hoping that provides better info. Just had a crash at 15:37, had been running fine for about 7 hours today without issue. syslog-192.168.1.111.log

Ran memtest, got through 2 passes with 0 errors.

It was running for almost an hour an then crashed. I lost access to the GUI and when I can reload it and sign back in the array operation says stopped unclean shutdown detected. In my flash logs folder I have 2 files, the syslog I just posted and a syslog-previous that shows last modified about 10 minutes prior to the crash. Not sure if I am looking at the wrong area for these logs. I have not done a memtest yet but can do so.

Ok, it just crashed again and this is what is in the logs folder on the flash drive. syslog

Sorry, I had that mirroring enabled but did not realize I was looking at the wrong log. I attached what was labeled as the syslog-previous from the flash drive. If this is still not the correct log I will wait for another crash and grab the log. syslog-previous

Hello, I am having an issue with my Unraid server crashing multiple times today. Not seeing anything stand out in the syslog but I also have not had to dig through them before. Seeing this in the log: Aug 8 10:34:58 skunkypete emhttpd: unclean shutdown detected Unraid: 6.12.11 Any assistance is appreciated, thanks. skunkypete-diagnostics-20240808-1041.zip skunkypete-syslog-20240808-1537.zip

Ok, I will give that a shot, thanks.

Thanks for the reply. I ran check filesystem and now it is showing roughly half the correct amount of used storage on the disk. Also, some data had been moved from the cache over to this disk on the array and when the mover ran the main correctly show the amount of calculated data moved over to the disk. On the diagnostics after running check filesystem without -n the df reports the same amount of data as the main page. skunkypete-diagnostics-20240419-0826.zip

Hello, I have a four disk array with a single parity drive. I recently added disk 1 to the array and currently have 8tb's of data on it. Yesterday the main page showed the correct amount of free and used space on the drive. The data is still present, unsure if this is an actual issue with the drive or just some kind of bug with reporting the amount of data on the drive. Currently a parity check is running after an unclean shutdown occurred earlier this morning. Hopefully I have added all the relevant information, if not let me know what else might be helpful in troubleshooting this. skunkypete-diagnostics-20240418-1455.zip