Multiple Probs: Insufficient Resources, FS Check, etc.

I've had my ReadyNas NV+ with 1GB of RAM and 4x500 seagate HDDs running in X-RAID for about a year now, and overall I've been quite happy. Recently, I've had some serious problems.

Let me start by saying that I have always had the following problem: Whenever I do a manual shutdown by pressing the power button on the front of the unit, the NAS powers down correctly, but when I power it on again, it always does a File System check. After I installed the 4.00 firmware, I could at least restart it via Frontview and it would not do the FS Check. This is extremely aggravating, as it often takes a couple of hours to check the file system.

Now, as for my current problem: This morning, I created a new share and set up CIFS access to it (as with all of my other shares). I then started to copy a few gigabytes of files from multiple sources on my Windows Vista PC to the new share. After a number of minutes, I got the "Insufficient system resources exist to complete the requested service" error. I have seen this error reported in the following places, but nobody seems to have found a solution:

viewtopic.php?f=23&t=3279&p=18850
viewtopic.php?f=21&t=12060

From this point forward, any attempt to access the NAS shares via Windows XP or Vista (on two different machines, one wired, he other wireless) resulted in the "insufficient system resources" error. Moreover, Frontview was extremely slow -- basically unusable. (Strangely, during this time, my Xbox360 could still stream WMV files off of a USB HDD attached to the NAS via the TwonkyMedia server I installed yesterday.) I tried multiple times to reboot the NAS via Frontview, but the NAS wouldn't reboot. Eventually I decided to do a manual reboot by holding on the power button on the front of the unit. Sadly, this brings us back to problem #1, where upon powering the unit back on, the unit did a File System Check which took forever. When the FS Check was done, things were as bad or worse than before I rebooted: Frontview was again extremely slow, but the ACT LED was blinking quickly (with all other LEDs solid), and I know that there was no disk activity. I no longer got the "insufficient system resources" error -- I was just getting 'network path not found' when using the name or IP address of the NAS. I could ping the unit via IP address, but not by host name ('nas').

I was eventually able to download the system logs from Frontview (after messing with the web interface for about 30 minutes), but here's where the next problem came. The logs don't seem to contain any activity from today (or yesterday even). For example, my system.log file ends with the following:

Apr 23 11:45:12 nas ntfs-3g[11599]: Unmounting /dev/sdb1 (USB1TB)
Apr 23 11:51:50 nas kernel: kjournald starting. Commit interval 5 seconds
Apr 23 11:51:50 nas kernel: EXT3 FS on sdb1, internal journal
Apr 23 11:51:50 nas kernel: EXT3-fs: mounted filesystem with ordered data mode.
Apr 23 11:51:53 nas exportfs[12055]: /etc/exports [1]: Neither 'subtree_check' or 'no_subtree_check' specified for export "*:/documents". Assuming default behaviour ('no_subtree_check'). NOTE: this default has changed since nfs-utils version 1.0.x
Apr 23 11:51:53 nas exportfs[12055]: /etc/exports [2]: Neither 'subtree_check' or 'no_subtree_check' specified for export "*:/WD1TB". Assuming default behaviour ('no_subtree_check'). NOTE: this default has changed since nfs-utils version 1.0.x
Apr 23 16:00:58 nas kernel: chn=2, statu/LP_S=0x(d0/d050)29, 16

(Note: Today is April 25.)

Does any of this make any sense?

I have powered down the unit again, and this time I've reinstalled the firmware by holding the reset switch on the back of the unit. It's still in the process of doing a FS Check, so I suppose there's hope that when it's done with the check I'll be in better shape, but somehow I doubt it.

Any thoughts? Can I send my zipped log files to someone to check them out?

Thanks,
Paul