January 21, 20179 yr So I have this warning today in UnRAID, never got this before. Server runs fine but this is showed as an error in Fix Common Problems. Posted diagnostics. derrickserver-diagnostics-20170121-1208.zip
January 21, 20179 yr Community Expert Looks like your logs have used up all the space. I don't really understand what I am seeing in your logs though. Is anything actually working? It looks like your appdata share is set to cache-yes (normally this would be set to only or prefer), and you have other shares that are cache-yes or cache-only, but you don't actually have a cache disk, and maybe because of that your user shares are broken and it is just stuck in a loop trying to start up the user shares. Never seen anything like this before.
January 21, 20179 yr Did you actually try to start the array? Previously there was an unsafe shutdown and it needs to do a parity check but it seems to be sitting in its "array not started" loop for hours.
January 21, 20179 yr Looks like your logs have used up all the space. I don't really understand what I am seeing in your logs though. Is anything actually working? It looks like your appdata share is set to cache-yes (normally this would be set to only or prefer), and you have other shares that are cache-yes or cache-only, but you don't actually have a cache disk, and maybe because of that your user shares are broken and it is just stuck in a loop trying to start up the user shares. Never seen anything like this before. Yes, there was a cache disk previously, but it's been removed. That works though. I just noticed that SMB is down and stuff, I guess it's because array is improperly started. *dunno why* So how would I clear out the logs? Did you actually try to start the array? Previously there was an unsafe shutdown and it needs to do a parity check but it seems to be sitting in its "array not started" loop for hours. Let me see if I can restart the array. It says it is started in UnRAID, but SMB is totally dead. So I think a reboot is in order. PS: I think one drive is on its way out, the SMART value for 'Current Pending Sector' is now at 320, and I got an email warning about this. Is it dangerous? Don't have any disks yet to replace if one fails. EDIT: OK, I can't stop the array, it's stuck cos there's no free space. What should I do now? How do I clear out the irrelevant logs?
January 21, 20179 yr Community Expert If you can go to each of your user shares and set them to cache-no and then reboot. If you can't then reboot and go to each of your user share and set them to cache-no.
January 21, 20179 yr If you can go to each of your user shares and set them to cache-no and then reboot. If you can't then reboot and go to each of your user share and set them to cache-no. I'd do it if I can stop the array, which I can't do because unraid can't write temporary files to stop the array. I need to clear out the log files you mentioned earlier through ssh, because the webgui is not responding anymore.
January 21, 20179 yr Community Expert If you can go to each of your user shares and set them to cache-no and then reboot. If you can't then reboot and go to each of your user share and set them to cache-no. I'd do it if I can stop the array, which I can't do because unraid can't write temporary files to stop the array. I need to clear out the log files you mentioned earlier through ssh, because the webgui is not responding anymore. It is already set to do an unclean shutdown parity check as it is, so you could just power it off. The syslogs are in /var/log
Archived
This topic is now archived and is closed to further replies.