Each time I reboot by readynas pro I get this email:
Volume scan found errors that it could not easily correct. Please ensure that you have current backups of all valuable data before performing a full volume scan by rebooting the NAS through Frontview with the volume scan option enabled.
***** File system check performed at Tue Jul 10 15:49:24 PDT 2012 ***** fsck 1.41.14 (22-Dec-2010) /dev/c/c contains a file system with errors, check forced. /dev/c/c: Extended attribute block 169512960 has reference count 4, should be 3.
/dev/c/c: UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY. (i.e., without -a or -p options)
It appears that I need to run fsck manually, anyone know how I should do this?
Thanks Quinghong. I am not concerned about the data, I have the backups taken care of. My question is how to run fsck manually to fix the "serious" errors it finds every time I reboot. Any ideas?
There is an option when you shut the unit down to runs volume scan. *Perform volume scan on next boot. This process can take several minutes to more than an hour depending on disk capacity and volume content.
This will run a fsck upon next boot up. I think this is what you are looking for...
Thank you, I have tried that as well. Every time it runs a volume scan, it still finds these errors and sends me that email. I am accustom to a few errors here and there but normally the volume scan finds and corrects these. I noticed that the verbage of the email that I referenced in the first post has changed from the normal one I receive when the unit finds errors and fixes them on the volume scan I have scheduled to occur on a weekly basis. This makes me think that the errors that it is finding are more serious.
I want to solve this issue as I am getting some weird behavior that I am afraid is related to this, yesterday people in the office had a number of random permission issues with different shares, and random insufficient disk space errors (not the case obviously).
There has been some changes to the fsck when the unit boots up. When you do a reboot, the unit would run a fsck. Previously upon the boot up fsck it would write the changes. Currently upon a normal reboot and starts to run the fsck, it runs the fsck as a read-only. The message shows gives you a heads up to backup the data if the filesystem is too corrupted for the fsck to recover. These seem to be in extreme cases, but it is best to be caution than sorry that the data is missing.
It does appear that the filesystem check has been helping your unit for sometime, and running the offline fsck will write the changes. There is a chance the filesystem can get too corrupted for fsck, so it is recommended for the backups before running the offline filesystem checks with these messages.
Ok, that is all fine, I guess I left out an important piece of info: everytime I boot the unit it goes through the file system check, even when I try to boot normally. This takes a long time and is very boring for everyone in the office. I thought if I did the fsck "manually" like the warning suggested it might be able to fix the error and would quit doing a check every time I boot. Is there a next level, ie what do you do if the fsck isn't able to find the errors and keeps checking on every boot?
Not sure if this is related or not, but I can no longer boot from frontview, I have to physically walk in there, touch the button, wait for it to get ready to shut down, press to shut down, and the fire it back up. Thanks for your continued help!
We were having a talk last night, and it looks like we are having a few other eyes taking a look at the logs. I will keep you posted to see what other steps we should do in this scenario.
I have confirmed this is normal behavior with the newest firmware. You will need to manual command the NAS to run the FSCK. Since the FSCK has helped you in the pasted We were trying to help control the FSCK from destroying the data. Informing you guys to backup the data before it forces the changes to the FS.
In the meantime, you can run the FSCK manual, or if you wanted to reboot; there is an option to skip FSCK.
Ok thats fine, the error message was changed in the update, I got that now. But that brings me back to my original question, how do I run fsck manually and will that help correct whatever problem I am having? As I have already stated, it runs automatically every time I boot now and takes a few hours and gives me the same error message every time. I would like to eliminate this behaviour.
Restating the same issue in a different way: The problem is the unit runs fsck every time it boots and sends me the error, I no longer can control that whether it goes through fsck or not, it goes through fsck regardless. How can I eliminate this behavior?
It looks like that you have already tried the manual option with the reboot and applying the following option: *Perform volume scan on next boot. This process can take several minutes to more than an hour depending on disk capacity and volume content.
Let's see if we are able to work something out over pm.
I am having the exact same problem, but I can't determine from this thread if running the reboot option with "Perform volume scan on next boot. This process can take several minutes to more than an hour depending on disk capacity and volume content" actually performs an fsck that writes the changes back?
