dilligaf Posted November 17, 2011 Posted November 17, 2011 Hi all, Well I finally have a question I could not locate the answer to among all of the great information around here. If this issue has been posted and answered and I missed it via the search I apologize in advance. Is it normal to have a log file that is very large on my boot/flash drive? I have one showing around 1.85GB. Yikes! That is a decent size .txt file I do believe. Perhaps it has been there all along (although the date of the file is last week when I added two new drives to the array). I just happened to notice that an awful lot of my 4GB flash drive is being used up. It is located in \\TOWER\flash\logs. Every other file in that folder is a more reasonable 200KB or so. I first thought well maybe after some time UNRAID deletes older log files automatically? I am unable to open the file in any program so far (notepad, wordpad, and even MS Word.) to try to see what it contains. I cannot seem to delete the file via explorer over the network. Well, I delete it and then it shows right back up it seems. I have not yet shut down the server and tried to manually delete the file from the jump drive. Is this a sign of something going wrong? Again so far I am unable to even see what is within the log for error checking. Should I attempt to delete the file directly from the jump drive after shutting down the server? What is safe to try. Or am I worried about nothing? Edit/Update: I decided to reboot the server and upon reboot it is now running an (as far as I know) unscheduled parity check. More to worry about or see what happens? Thanks for any advice you can provide.
Joe L. Posted November 18, 2011 Posted November 18, 2011 Hi all, Well I finally have a question I could not locate the answer to among all of the great information around here. If this issue has been posted and answered and I missed it via the search I apologize in advance. Is it normal to have a log file that is very large on my boot/flash drive? I have one showing around 1.85GB. Yikes! That is a decent size .txt file I do believe. Perhaps it has been there all along (although the date of the file is last week when I added two new drives to the array). I just happened to notice that an awful lot of my 4GB flash drive is being used up. It is located in \\TOWER\flash\logs. Every other file in that folder is a more reasonable 200KB or so. I first thought well maybe after some time UNRAID deletes older log files automatically? I am unable to open the file in any program so far (notepad, wordpad, and even MS Word.) to try to see what it contains. I cannot seem to delete the file via explorer over the network. Well, I delete it and then it shows right back up it seems. I have not yet shut down the server and tried to manually delete the file from the jump drive. Is this a sign of something going wrong? Again so far I am unable to even see what is within the log for error checking. Should I attempt to delete the file directly from the jump drive after shutting down the server? What is safe to try. Or am I worried about nothing? Edit/Update: I decided to reboot the server and upon reboot it is now running an (as far as I know) unscheduled parity check. More to worry about or see what happens? Thanks for any advice you can provide. unRAID writes its log file to /var/log/syslog It does not write to the flash drive except when changing the disk configuration, or when starting and stopping the array. If you have a syslog.txt on your flash drive, it is one you created yourself by copying /var/log/syslog to it. You can delete the one on the flash drive if you like. you must stop the array before rebooting, otherwise, unRAID will consider it a un-expected shutdown and force a full parity check on reboot. Joe L.
dilligaf Posted November 18, 2011 Author Posted November 18, 2011 Thanks for the reply Joe. I was finally able to delete the log files from the flash drive directly. I also ran a checkdisk on the drive as one of the files would not delete as it came back as corrupted. The drive appears fine as of now but I am beginning to wonder if this particular drive is slowly going bad. As far as the parity checks. I believe I do stop the array before rebooting or powering down. I may be confused but I do not think the reboot and powerdown buttons in the web gui are available until the array is stopped? I made sure to stop the array this time, then power down, and then I removed the flash drive from the server (in order to delete those pesky log files). Upon reboot, I restarted the array and all appeared well. I then noticed it running a parity check again. Was this again an unexpected shutdown you think? or did it detect changes to the flash drive maybe and run a parity check?
Joe L. Posted November 18, 2011 Posted November 18, 2011 Thanks for the reply Joe. I was finally able to delete the log files from the flash drive directly. I also ran a checkdisk on the drive as one of the files would not delete as it came back as corrupted. The drive appears fine as of now but I am beginning to wonder if this particular drive is slowly going bad. As far as the parity checks. I believe I do stop the array before rebooting or powering down. I may be confused but I do not think the reboot and powerdown buttons in the web gui are available until the array is stopped? I made sure to stop the array this time, then power down, and then I removed the flash drive from the server (in order to delete those pesky log files). Upon reboot, I restarted the array and all appeared well. I then noticed it running a parity check again. Was this again an unexpected shutdown you think? or did it detect changes to the flash drive maybe and run a parity check? In order to record the fact that the shutdown was clean, it must write to the parity drive. If it cannot properly record the fact it was cleanly stopped, because the flash drive file-system is corrupted, or because you removed the flash drive from the server, it will perform a parity check on reboot. You basically need to stop the array once more, run checkdisk/scandisk on a window's Pc on the flash drive to fix any issues, then reboot. It will probably do another parity check if the prior clean shutdown had not been recorded properly on it, but after that, you should be ok.
Recommended Posts
Archived
This topic is now archived and is closed to further replies.