Run with --check again.

 

Will do that as soon as I get home from work!

It probably will check out fine now.  Usually, if  reiserfsck needs to be run again, it will tell you.

I just got home a few minutes ago.  I logged on to unmenu to check the syslog, and it stated that the server was restarted, but it found 102 errors.  I don't have a UPC hooked up to the router, and it rained today.  In rare occasions the power goes out for a few minutes when it rains, but my wife said that she wasn't sure if the power went out or not.

 

The server appears to be working correctly.  I am running another parity check prior to running the --check hard drive.  I transfer a new movie to the server, and it was place in disk3, which was the one I was having issues with.  The movie plays fine, and I am able to move files around, which I wasn't able to do before.

 

I am hoping the errors aren't a big issue because I want to try to update to V5.14b.

Ran 2 parity checks.  One without fixing the errors, and one to fix the errors, but I still get 102 errors found.  How do I fix these errors?

syslog-2012-04-11.txt