s986

reformat to the same? ZFS?

I set the cache to unassigned, rebooted, array started and parity check did not start. attached log. tower-syslog-20240616-1133.zip

I noticed the in dashboard system memory, ZFS is always 100% here is system log that is showing these errors. I had drives with health problems and when I looked the drive error it was old age, but now I removed all drives and kept the necessary ones and until I but new drive to expand the capacity. thanks tower-syslog-20240616-0905.zip

here is syslog, rebooting and no new entry in syslog or 6 mins now. s986-syslog-20240610-1513.zip

Hi, I increased the time to 200 and tried rebooting and it did not reboot, I had to power cycle, attached diagnostics after reboot s986-diagnostics-20240610-1816.zip

Hi thankyou @JorgeB for replying, I timed the stopping time, and it was 56 seconds while Shutdown timeout is 120 seconds, also not sure what you mean see ZFS crash and how to identify any issue!

Parity starts every time i reboot, please help, diagnostics attached. s986-diagnostics-20240609-1816.zip

@JorgeB attached is normal boot 1 day 9 hours, I log out after each session. i only noticed below screen capture.

@JorgeB attached is normal boot 1 day 9 hours, I log out after each session. i only noticed below screen capture. s986-diagnostics-20231017-1718.zip

closed them all, so far running in normal boot not safe mode and no errors. If errors occur I will save diagnostics and reboot in safe mode and monitor. till that error happens then I will upload diagnostics. thanks for replies and support.

Log shows similar errors even in safe mode with no dockers and no plugins. as for GUI, usually yes at least one GUI open sometimes more. s986-diagnostics-20231016-0621.zip

I will tonight I thought after deleting netdata all is good, I will start it in safe mode and report back. question: can i use it normal in safe mode, or what should I expect or do?

hi, something is happening with memory and /devices!! please see diagnostics I hope I captured it. s986-diagnostics-20231015-1708.zip

Thanks for your replies, I found another post in Dutch non the less, where one replied the netdata docker is causing this over write to syslog (The reply). I deleted netdata docker and restarted the unraid, so far no red text as in no errors. I will update here if log refills again, however how much is normal for log size to be?? Thanks.

Would this help?