Greetings,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?

The alert email have said please backup all of your important data before you fsck it.

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).

Did you want to send me the logs so I can check the other part of the logs to see how things are running?www.readynas.com/kb/faq/misc/how_do_i_send_all_logs

Volume scan | NETGEAR Communities

15 Replies

Replies have been turned off for this discussion

OOM-9
NETGEAR Expert
Jul 16, 2012
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.
truittvance
Aspirant
Jul 17, 2012
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?

Thanks for your continued help.
StephenB
Guru - Experienced User
Jul 17, 2012
I am wondering if the volume scans run fsck "manually"
OOM-9
NETGEAR Expert
Jul 17, 2012
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.
sircoolio
Tutor
Jul 21, 2012
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?

How do we fix this problem?

Forum Discussion

Volume scan

15 Replies

Related Content

Volume Expansion question

Volume scan failed to run properly #26188803

Scan with Netgear Armor not working

AX4200 RBR750 Vulnerability scan schedule

RAXE500: DoS Attack RST Scan

NETGEAR Academy

ProSupport for Business