NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
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
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
27 Replies
Replies have been turned off for this discussion
- Ok, the NAS is back up, and Frontview is back to normal speed -- but I can't access any of my shares. CIFS, FTP, and HTTP are all hosed.
entering \\192.168.0.200\ (the address of my nas) into a 'run' dialog yields the following message:
"The network path was not found"
Other problems:
1.) I cannot enable the FTP service. I consistently get the message "Error starting FTP service."
2.) I cannot upgrade my firmware. If I try to use a local file (RAIDiator-4.01c1-p2), the NAS verifies the image and then I get the following message: "Invalid Checksum detected in the update file". And if I try to update the firmware with a remote image, I get "Error encountered uploading update image."
3.) Accessing my shares over HTTP barely works. I can read directories but not files.
Please help! - I too have had my NAs box for nearly two years and have been very pleased with its operation.
Unfortunately today without changing any settings i was unable to log onto the device through window vista.
I get the error "Insufficient system resources"
As you describe the activity light is flashing like crazy and all 3 (My population) drive lights are on.
I can however access the shares via the ip addess xxx.xxx.xxx.xxx/shares in my internet browser and was able to see all the shares still in place and acces the ones i required.
I am in a mild panic at the moment as the reason I purchased a NAS device was to ensure all my files were safe and protected.
this device contains all my work documentation.
the device has emailed me the message
"RAID sync started on volume C.
[Tue Jun 16 17:15:17 WEST 2009]"
So i guess that explanis the activity.
I have tried to update locally from the latest image on the website and got the update failed.
I have also been mailed the message
"Improper shutdown detected.
To ensure data integrity, a filesystem check should be performed as soon as possible. In Frontview:
1. Click on the System button.
2. Go to the Shutdown tab.
3. Enable the volume scan on next boot checkbox.
4. Reboot the device."
This was received after I used the manual shutdown and restart after the failed image update.
Is this just related to the fact that whilst the raid sync is running the NAS device simply cannot cope with anymore requests at this time and will therefore go away?
If this is the case, why does it still let me access via the Front View shares URL listed above.
I have tried to Access the NAs from another Vista PC in my house, both are connected by Ethernet cable and it also is ecperiencing the same issue. I have therefore atributed the error to the NAS rather than the client PC.
I am becoming very nervous now and wondered if anyone else is experiencing this issue or indeed if the previous poster managed to clarify this strange behaviour.
..... begins to bite nails in anticipation of an expert response. - After 2 years of flawless service, my ReadNAS NV+ with 1Gb RAma dn X-RAID 3x2Tb disks + 2 x 2Tb USB disks (for Backup of the NAS) have started to give me a problem
When accessing the NAS from my Win7x64 machine I got the error "insufficient system resources exist to complete the requested service" and when using my XBMC machine I get the error "Invalid Argument" when connecting to the NAS.
First I did the Microsoft solution and rebooted the NAS and checked the FileSystem when Booting. That made not difference.
So I logged in thru SSH and "top" is not showing anything unusual. Nothing is using a lot of CPU or Memory, I don't have a lot of connections to the box (netstat -an), I can access all of the FS and both external USB drives, thru SSH. So I assume the Filesystem and rest of the NAS is working as it should.
Then I stopped AFP, NFS, CIFS and the FTP services and started the services one by one and tested them then one by one.
- FTP works or all users but the admin user.
- NFS does not work
- AFS does not work
- The problem is still there with CIFS.
I also have a problem downloadning the Logs so I can't provide that yet. When I can I will ...
Model: ReadyNAS NV+ [X-RAID]
Firmware: RAIDiator 4.1.8 [1.00a043]
Memory: 1024 MB [2.5-3-3-7]
Volume C: Online, X-RAID, 3 disks, 77% of 3701 GB used
Any ideas? - You can still see most logs under /var/log via SSH
What happens if you do a "df -h"? - Thanks for the link to the logs, I did not know that. :)
... and thanks for putting me in the right direction! I think I got it now!
I started with doing a simple "df -h" which gave me:Filesystem Size Used Avail Use% Mounted on
/dev/hdc1 1.9G 2.0G 0 100% /
tmpfs 16k 0 16k 0% /USB
/dev/c/c 3.6T 2.8T 880G 77% /c
/c/home 3.6T 2.8T 880G 77% /home/ftp/homes
/c/MUSIC 3.6T 2.8T 880G 77% /home/ftp/MUSIC
/c/ftpul 3.6T 2.8T 880G 77% /home/ftp/ftpul
/c/media 3.6T 2.8T 880G 77% /home/ftp/media
/dev/sda1 1.8T 1.5T 379G 80% /USB/USB_HDD_3
/dev/sdb1 1.8T 369G 1.4T 20% /USB/USB_HDD_4
So then I did "ls /var/log -ahlS" and that gave me:total 1.2G
-rw-r--r-- 1 root root 610M Jan 21 00:48 syslog
-rw-r--r-- 1 root root 610M Jan 21 00:48 daemon.log
-rw-r--r-- 1 root root 1.6M Jan 21 00:47 upnp-av.log
-rw-r--r-- 1 root root 625k Jan 21 01:09 cron.log
-rw-r--r-- 1 root root 618k Jan 21 01:09 auth.log
-rw-r--r-- 1 root root 233k Jan 21 00:50 user.log
-rw-r----- 1 root root 161k Jan 21 00:51 proftpd.log
-rw-r--r-- 1 root root 105k Oct 30 17:22 mt-daapd.log
-rw-r--r-- 1 root root 62k Jan 21 00:51 kern.log
The syslog and deamon.log files are 610M so I moved first the "syslog" file and did df -h again:Filesystem Size Used Avail Use% Mounted on
/dev/hdc1 1.9G 1.4G 610M 70% /
Then I moved the "daemon.log" file.
So, it seems like the logs are not autorotating and they are not cleared or moved or anything like that. Seems like this is a silly "Disk full problem".
I'll keep trying things for a little more but I guess I'll try and set up some kind of automatic clear of the logs in the /var/log folder.
Now things start to work as it should. If it doesn't I'll come back here ... - The disk_usage.log (one of the ones not found under /var/log, but can easily be generated using "df -h" via SSH) is one of the first things to look at if you have major OS issues and experience problems such as not being able to download the logs. For one reason or another rarely there can be a problem where the OS partition fills up. It is odd that those logs got that full. Looking occasionally at how full the OS partition is, is a good idea. Normally there should be plenty of space free.
Now it is possible that some things on the OS partition could've got corrupted so normally when you have an issue like this it's best to work with tech support to diagnose the issue and correct it. - Hi there!
I just fell too in the same situation as of today... I am an IT guy, but not that much linux... I'm missing some details on how to clear the log files.
My df -h looks like that:
NAS:/c# df -h
Filesystem Size Used Avail Use% Mounted on
/dev/hdc1 1.9G 2.0G 0 100% /
tmpfs 16k 0 16k 0% /USB
/dev/c/c 694G 527G 167G 76% /c
/c/Divers 694G 527G 167G 76% /home/ftp/Divers
/c/PartagePat 694G 527G 167G 76% /home/ftp/PartagePat
/c/Software 694G 527G 167G 76% /home/ftp/Software
/c/backup 694G 527G 167G 76% /home/ftp/backup
/dev/sda1 1.8T 522G 1.3T 29% /USB/SeagateExt
NAS:/c#
So I guess my hdc1 device is full... How do I clean it up? The bigges file listed on ls /var/log -ahlS, is only 94M...
Oh my device is a ReadyNAS duo with 2 750gb drives about 70% full...
Thanks for the help!
EDIT:
After a hardware reboot (the web interface did not want to reboot or shutdown the Duo but I thought it did), my hdc1 is at 96% (1.9G on 1.9G). I regained access to my shares without having Windows popping weird error messages. I am still interested to see which files I can target for deletion to give me room for another 2-3 years... - Any addons installed?
When did you purchase the Duo?
Have you tried contacting NetGear tech support (http://www.readynas.com/support) for assistance? - Addons: not really, except for the Bittorrent client and the readynas remote.
Probably half of 2008.
Not really tried to contact support as I always look out on the support forums first. Should I? - I have had the "Insufficient resources" error as well, while copying some backup-data from a DVD. At first I could still browse the other folders on the NAS, but after a reboot of the NAS (did not reboot my PC between the first error and my NAS-reboot) I couldn't access the NAS at all!
After a reboot of the NAS -and- my PC, all seems well. However I am scared s**t-less that my NAS is corrupting / has corrupted my data, or that more serious error will follow. Should I be worried?
As for support: I could not contact them through the support-page, as it bailed on me with a message that roughly said: "your ticket could not be processed due to technical difficulties".
Thanks in advance for any help!
System specs:
ReadyNas Dus RND2000
Windows XP MCE SP3
2x 1TB Western Digital disk
Addons:
SSHToggle
APT add-on
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
