April 12, 20233 yr Hi all, my unraid server went offline today and I couldn't get the array restarted. I also was unable to run the diagnostics via the webgui but did manage to gather some info before rebooting. The build is fairly new ~ 2weeks and I haven't had a problem till today. I moved the drives over from a Truenas ZFS pool and rysnc'd the data to to the pool and then destroyed the zfs pool and added the drives to the unraid pool. Only mentioning this for context but i don't think this process of zfs --> array should have anything to do with array going offline but wanted to confirm!! Short excerpt from the diagnostics... ******************************************************************** Starting diagnostics collection... Warning: file_put_contents(): Only -1 of 8 bytes written, possibly out of free disk space in /usr/local/emhttp/plugins/dynamix/scripts/diagnostics on line 317 tail: write error: No space left on device Warning: file_put_contents(): Only -1 of 15 bytes written, possibly out of free disk space in /usr/local/emhttp/plugins/dynamix/scripts/diagnostics on line 326 Warning: file_put_contents(): Only -1 of 12 bytes written, possibly out of free disk space in /usr/local/emhttp/plugins/dynamix/scripts/diagnostics on line 326 Warning: file_put_contents(): Only -1 of 16 bytes written, possibly out of free disk space in /usr/local/emhttp/plugins/dynamix/scripts/diagnostics on line 326 Warning: file_put_contents(): Only -1 of 13 bytes written, possibly out of free disk space in /usr/local/emhttp/plugins/dynamix/scripts/diagnostics on line 326 Warning: file_put_contents(): Only -1 of 124 bytes written, possibly out of free disk space in /usr/local/emhttp/plugins/dynamix/scripts/diagnostics on line 326 Warning: file_put_contents(): Only -1 of 1044 bytes written, possibly out of free disk space in /usr/local/emhttp/plugins/dynamix/scripts/diagnostics on line 326 Warning: file_put_contents(): Only -1 of 521 bytes written, possibly out of free disk space in /usr/local/emhttp/plugins/dynamix/scripts/diagnostics on line 326 Warning: file_put_contents(): Only -1 of 11 bytes written, possibly out of free disk space in /usr/local/emhttp/plugins/dynamix/scripts/diagnostics on line 326 Warning: file_put_contents(): Only -1 of 15 bytes written, possibly out of free disk space in /usr/local/emhttp/plugins/dynamix/scripts/diagnostics on line 326 Warning: file_put_contents(): Only -1 of 14 bytes written, possibly out of free disk space in /usr/local/emhttp/plugins/dynamix/scripts/diagnostics on line 326 Warning: file_put_contents(): Only -1 of 5079 bytes written, possibly out of free disk space in /usr/local/emhttp/plugins/dynamix/scripts/diagnostics on line 326 Warning: file_put_contents(): Only -1 of 11 bytes written, possibly out of free disk space in /usr/local/emhttp/plugins/dynamix/scripts/diagnostics on line 326 Warning: file_put_contents(): Only -1 of 83 bytes written, possibly out of free disk space in /usr/local/emhttp/plugins/dynamix/scripts/diagnostics on line 342 Warning: file_put_contents(): Only -1 of 2 bytes written, possibly out of free disk space in /usr/local/emhttp/plugins/dynamix/scripts/diagnostics on line 363 Warning: file_put_contents(): Only -1 of 34 bytes written, possibly out of free disk space in /usr/local/emhttp/plugins/dynamix/scripts/diagnostics on line 365 Warning: file_put_contents(): Only -1 of 2 bytes written, possibly out of free disk space in /usr/local/emhttp/plugins/dynamix/scripts/diagnostics on line 363 Warning: file_put_contents(): Only -1 of 34 bytes written, possibly out of free disk space in /usr/local/emhttp/plugins/dynamix/scripts/diagnostics on line 365 echo: write error: No space left on device echo: write error: No space left on device echo: write error: No space left on device echo: write error: No space left on device echo: write error: No space left on device echo: write error: No space left on device echo: write error: No space left on device echo: write error: No space left on device echo: write error: No space left on device echo: write error: No space left on device ************************************************************ I did grab the diagnostics via ssh but alot of the files are zero in size due to the space error. I'm going to swap out the USB boot drive for starters and looking for pointers! Thanks for your help inadvance! Array + Pools: Shares: Docker Mappings: Diagnostics: diagnostics.txt tower-diagnostics-20230412-0715.zip Edited April 12, 20233 yr by NOAV arrange the screenshots
April 12, 20233 yr Community Expert This is the problem, rootfs is full, and it usually means you have something writing to a mapping outside /mnt/user, and that goes to RAM, check all container mappings.
April 12, 20233 yr Community Expert Solution Your krusader appdata mapping goes to /mnt/cache, but you have no pool named 'cache'. Probably you renamed your pool without fixing that mapping.
April 12, 20233 yr Author Thank you both for your help! Correct I added a second drive to the cache pool and had renamed it! Thanks again!
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.