Leading up to: "Volume scan found errors that it could..."
Where I'm at : Volume scan found errors that it could not easily correct.
What has been happening. Since June 4, I have been getting volume scan corrected errors six times. Sometimes from me manually rebooting or from the weekly scan.
Other problems I have been experiencing for the past ~6 weeks. All shares becomes read only; everything is default public, no accounts created. Reboot would fix (via frontview). Happening at least once a week. Share would become unresponsive, hang. Frontview allowed me to reboot and run a scan / fix. Once a week. Reformatted USB backup drives, replaced one, unplugged all of them. Any combination of the above. ~40% of the reboots would result in an unsuccessful boot. Hard off (I usually pulled the power plug and let it sit for a few minutes). Switched to a new, over sized UPS.
In the past week it has become more often; so I started looking at the SMART status on each drive. One showed 234 reallocated errors. I replaced the drive. Rebuild successful. Rebooted, full check on FS and Quota (no quotas setup). Hung at 77% quota check (hours went by). Hard off, reboot and FS check succesful (repaired). Everything seemed fine. Dumped the recent vacation videos and photos (5+GB). No problems with the transfer. Then I tried to copy a set of the videos off to edit locally, failed. The box went completely offline. RAIDar finds nothing... Hard reboot. Comes up. Reboot request with FS scan. Never reboots. Ping works, no frontview, no file access. Hard off and power on. Never finished booting. Says Fan FAIL on the front! Power up and it works great! Backed up my recent file dump (5gb) and reboot with FS check. Quota check to 20% and it completely goes offline (continuous ping starts failing, RAIDar stops finding anything). Front of the unit displays FS 19%, I hard powered off. Will reboot in a few minutes. It's like groundhog day with slight variations. It's super annoying. Any ideas on how to proceed / guesses? I cannot consistently create the same problems, so I'm stumped. I keep thinking power supply and after searching; it is probably a good idea. The fans are fine. The connections are solid, no loose screws, etc. There is no dust in the unit (~6 months old?).
fyi: I do have backups, but would prefer not to use them!
Which log file dump is the most useful to put here? RECENT fs_check.log (before recent failed boot / fs check) ---- START ----
***** File system check forced at Sat Jul 28 15:14:45 EDT 2012 ***** fsck 1.41.14 (22-Dec-2010) e2fsck 1.42.3 (14-May-2012) Pass 1: Checking inodes, blocks, and sizes Inode 21496332 has a bad extended attribute block 343935539. Clear? yes
Inode 21496332, i_blocks is 3552, should be 3544. Fix? yes
Inode 21496333 has a bad extended attribute block 343935540. Clear? yes
Inode 21496333, i_blocks is 2968, should be 2960. Fix? yes
/dev/c/c: ***** FILE SYSTEM WAS MODIFIED ***** /dev/c/c: 171379/75923456 files (2.8% non-contiguous), 526311105/1214775296 blocks
***** File system check performed at Sun Jul 29 14:19:06 EDT 2012 ***** fsck 1.41.14 (22-Dec-2010) /dev/c/c contains a file system with errors, check forced. /dev/c/c: Inode 21496371 has a bad extended attribute block 343935579.
/dev/c/c: UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY. (i.e., without -a or -p options)
Re: Leading up to: "Volume scan found errors that it could..
Powered on after being stuck at 19% fs check. Did the same thing, stuck at 19%. Another reboot and it came online, but I received the same notice of 'UNEXPECTED INCONSISTENCY'. It started a resync (x2) and says it has ~5+ hours left. It's online and I copied a gig of files off it with success... Why the resync?
