CorserMoon Posted July 14, 2022 Share Posted July 14, 2022 Hi all. Woke up this morning to Organizr not working (throwing "not writeable" error) as well as many other dockers not operating as expected. Next step was checking the log file which is 100% full. All disks/pools/shares are green and readable though. Log filled up with BTRFS and rsyslog write errors (I am using syslog server). Before I reboot to clear the log file, wanted your expert eyes on. executor-diagnostics-20220714-1053.zip Quote Link to comment
Solution JorgeB Posted July 14, 2022 Solution Share Posted July 14, 2022 Filesystem went read-only to avoid writing corrupt data, rebooting should fix it but this usually indicates a hardware problem or some other kernel memory corruption. 1 Quote Link to comment
CorserMoon Posted July 14, 2022 Author Share Posted July 14, 2022 1 minute ago, JorgeB said: Filesystem went read-only to avoid writing corrupt data, rebooting should fix it but this usually indicates a hardware problem or some other kernel memory corruption. OK, thanks for the insight. Bad storms last night and despite everything being plugged into UPS's, could have been flakey power issue. Quote Link to comment
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.