- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
ReadyNAS Duo v1 - Full OS Partition?
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
ReadyNAS Duo v1 - Full OS Partition?
I'm new to the community and seeking your help in resurrecting my ReadyNas Duo V1. Its behaviour became increasingly erratic recently and now I've lost access to the shares. Having researched the symptoms on this community, I suspect that I may have a full OS partition.
I've been using information on other posts to troubleshoot. Useful posts that I have followed to date are:
https://onlyblueatwork.wordpress.com/2012/12/04/netgear-readynas-access-recovery/
I did not have SSH enabled and am unable to install the add-on (presumably because the partition is full). I have however managed to start the NAS in Tech Support Mode (http://netgear.nas-central.org/wiki/TechSupportMode) and have been successful in Telnetting on to it using Putty. I've managed to mount the OS partition:
# /bin/start_raid.sh
# mount /dev/hdc1 /sysroot
Looking in /sysroot/var/log, I do see some big files:
-rw-r--r-- 1 0 0 4767744 messages
-rw-r--r-- 1 0 0 4603904 kern.log
-rw-r--r-- 1 0 0 8765440 daemon.log
-rw-r--r-- 1 0 0 81920 cron.log
-rw-r--r-- 1 0 0 15830829 syslog
-rw-r--r-- 1 0 0 53133312 auth.log
Now I'm nervous! What is the recommended way to clear space? Can I just delete say, auth.log?
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Re: ReadyNAS Duo v1 - Full OS Partition?
How full is the OS partition? (df and df -i can tell you this)
It's best not to delete the log files. You can empty them using echo > filename
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Re: ReadyNAS Duo v1 - Full OS Partition?
# /sysroot/bin/df -h
# /sysroot/bin/df -i
# /sysroot/usr/bin/du -csh /sysroot/var/*
# /sysroot/usr/bin/du -csh /sysroot/var/log/*
Normally we copy log files onto the data volume before emptying them just in case the logs contain information that may be useful for troubleshooting other issues.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Re: ReadyNAS Duo v1 - Full OS Partition?
# /sysroot/bin/df -h
Filesystem Size Used Avail Use% Mounted on
rootfs 7.7M 6.5M 1.3M 83% /
/dev/root 7.7M 6.5M 1.3M 83% /
tmpfs 16k 0 16k 0% /dev/shm
/dev/hdc1 1.9G 2.0G 64k 100% /sysroot
# /sysroot/bin/df -i
Filesystem Inodes IUsed IFree IUse% Mounted on
rootfs 2048 250 1798 13% /
/dev/root 2048 250 1798 13% /
tmpfs 7073 1 7072 1% /dev/shm
/dev/hdc1 128000 10969 117031 9% /sysroot
# /sysroot/usr/bin/du -csh /sysroot/var/*
16k /sysroot/var/backups
47M /sysroot/var/cache
16k /sysroot/var/ftpd
38M /sysroot/var/lib
16k /sysroot/var/local
32k /sysroot/var/lock
1.2G /sysroot/var/log
16k /sysroot/var/mail
16k /sysroot/var/netatalk
16k /sysroot/var/opt
544k /sysroot/var/run
371M /sysroot/var/spool
16k /sysroot/var/tmp
32k /sysroot/var/www
48k /sysroot/var/yp
1.6G total
# /sysroot/usr/bin/du -csh /sysroot/var/log/*
11M /sysroot/var/log/LeafP2P.log
0 /sysroot/var/log/LeafP2P.log.old
0 /sysroot/var/log/LeafP2P.log.old.old
0 /sysroot/var/log/LeafP2P.log.old.old.old
0 /sysroot/var/log/LeafP2P.log.old.old.old.old
0 /sysroot/var/log/LeafP2P.log.old.old.old.old.old
0 /sysroot/var/log/LeafP2P.log.old.old.old.old.old.old
0 /sysroot/var/log/LeafP2P.log.old.old.old.old.old.old.old
0 /sysroot/var/log/LeafP2P.log.old.old.old.old.old.old.old.old
51M /sysroot/var/log/auth.log
80k /sysroot/var/log/cron.log
64k /sysroot/var/log/cups
8.4M /sysroot/var/log/daemon.log
16k /sysroot/var/log/ddns
0 /sysroot/var/log/debug
0 /sysroot/var/log/dekoh_access.log
0 /sysroot/var/log/dekoh_access.log.old
0 /sysroot/var/log/dekoh_access.log.old.old
0 /sysroot/var/log/dekoh_access.log.old.old.old
0 /sysroot/var/log/dekoh_error.log
0 /sysroot/var/log/dekoh_error.log.old
0 /sysroot/var/log/dekoh_out.log
0 /sysroot/var/log/dekoh_out.log.old
0 /sysroot/var/log/dekoh_out.log.old.old
16k /sysroot/var/log/dmesg
32k /sysroot/var/log/exim
1.1G /sysroot/var/log/frontview
0 /sysroot/var/log/fsck.log
4.5M /sysroot/var/log/kern.log
16k /sysroot/var/log/ksymoops
0 /sysroot/var/log/lpr.log
0 /sysroot/var/log/mail.log
4.6M /sysroot/var/log/messages
0 /sysroot/var/log/mt-daapd.log
0 /sysroot/var/log/mt-daapd.log.old
0 /sysroot/var/log/netatalk.log
0 /sysroot/var/log/netatalk.log.old
0 /sysroot/var/log/netatalk.log.old.old
0 /sysroot/var/log/netatalk.log.old.old.old
0 /sysroot/var/log/netatalk.log.old.old.old.old
16k /sysroot/var/log/ntpstats
0 /sysroot/var/log/raidiator_version
0 /sysroot/var/log/raidiator_version.old
192k /sysroot/var/log/samba
0 /sysroot/var/log/slimserver.log
16k /sysroot/var/log/squeezecenter
16M /sysroot/var/log/syslog
256k /sysroot/var/log/upnp-av.log
0 /sysroot/var/log/upnp-av.log.old
0 /sysroot/var/log/upnp-av.log.old.old
0 /sysroot/var/log/upnp-av.log.old.old.old
0 /sysroot/var/log/upnp-av.log.old.old.old.old
0 /sysroot/var/log/upnp-av.log.old.old.old.old.old
0 /sysroot/var/log/upnp-av.log.old.old.old.old.old.old
0 /sysroot/var/log/upnp-av.log.old.old.old.old.old.old.old
0 /sysroot/var/log/upnp-av.log.old.old.old.old.old.old.old.old
0 /sysroot/var/log/upnp-av.log.old.old.old.old.old.old.old.old.old
0 /sysroot/var/log/user.log
1.2G total
# /sysroot/usr/bin/du -csh /sysroot/var/log/frontview/*
16k /sysroot/var/log/frontview/access.log
0 /sysroot/var/log/frontview/apache-ssl.pid.old
16k /sysroot/var/log/frontview/backup
16k /sysroot/var/log/frontview/command.log
0 /sysroot/var/log/frontview/disk_smart_2016_05_29.log
0 /sysroot/var/log/frontview/disk_smart_2016_06_05.log
0 /sysroot/var/log/frontview/disk_smart_2016_06_12.log
0 /sysroot/var/log/frontview/disk_smart_2016_06_20.log
0 /sysroot/var/log/frontview/disk_smart_2016_07_03.log
0 /sysroot/var/log/frontview/disk_smart_2016_07_19.log
0 /sysroot/var/log/frontview/disk_smart_2016_08_01.log
0 /sysroot/var/log/frontview/disk_smart_2016_08_14.log
0 /sysroot/var/log/frontview/disk_smart_2016_08_21.log
16k /sysroot/var/log/frontview/disk_smart_2016_08_30.log
16k /sysroot/var/log/frontview/disk_usage.log
0 /sysroot/var/log/frontview/disk_usage.log.old
0 /sysroot/var/log/frontview/ecounter_2016_08_30_2209.log
0 /sysroot/var/log/frontview/ecounter_2016_08_30_2241.log
0 /sysroot/var/log/frontview/ecounter_2016_08_31_2030.log
0 /sysroot/var/log/frontview/ecounter_2016_08_31_2030.log.old
0 /sysroot/var/log/frontview/ecounter_2016_08_31_2112.log
0 /sysroot/var/log/frontview/enclosure.log
0 /sysroot/var/log/frontview/enclosure.log.old
1.1G /sysroot/var/log/frontview/error.log
16k /sysroot/var/log/frontview/memory.log
0 /sysroot/var/log/frontview/memory.log.old
0 /sysroot/var/log/frontview/partitions_2016_05_29.log
0 /sysroot/var/log/frontview/partitions_2016_06_05.log
0 /sysroot/var/log/frontview/partitions_2016_06_12.log
0 /sysroot/var/log/frontview/partitions_2016_06_20.log
0 /sysroot/var/log/frontview/partitions_2016_07_03.log
0 /sysroot/var/log/frontview/partitions_2016_07_19.log
0 /sysroot/var/log/frontview/partitions_2016_08_01.log
0 /sysroot/var/log/frontview/partitions_2016_08_14.log
0 /sysroot/var/log/frontview/partitions_2016_08_21.log
0 /sysroot/var/log/frontview/partitions_2016_08_30.log
0 /sysroot/var/log/frontview/raid_config_2016_05_29.log
0 /sysroot/var/log/frontview/raid_config_2016_06_05.log
0 /sysroot/var/log/frontview/raid_config_2016_06_12.log
0 /sysroot/var/log/frontview/raid_config_2016_06_20.log
0 /sysroot/var/log/frontview/raid_config_2016_07_03.log
0 /sysroot/var/log/frontview/raid_config_2016_07_19.log
0 /sysroot/var/log/frontview/raid_config_2016_08_01.log
0 /sysroot/var/log/frontview/raid_config_2016_08_14.log
0 /sysroot/var/log/frontview/raid_config_2016_08_21.log
0 /sysroot/var/log/frontview/raid_config_2016_08_30.log
16k /sysroot/var/log/frontview/smart_errors_hdc
0 /sysroot/var/log/frontview/smart_errors_hdc.old
16k /sysroot/var/log/frontview/smart_errors_hde
0 /sysroot/var/log/frontview/smart_errors_hde.old
16k /sysroot/var/log/frontview/spool.err
0 /sysroot/var/log/frontview/spool.err.old
16k /sysroot/var/log/frontview/spool.log
0 /sysroot/var/log/frontview/spool.log.old
0 /sysroot/var/log/frontview/spool.log.old.old
0 /sysroot/var/log/frontview/status.log-new
0 /sysroot/var/log/frontview/status.log-new.old
0 /sysroot/var/log/frontview/status.log-new.old.old
0 /sysroot/var/log/frontview/status.log-old
0 /sysroot/var/log/frontview/status.log-old.old
0 /sysroot/var/log/frontview/status.log-old.old.old
0 /sysroot/var/log/frontview/status.log-old.old.old.old
1.1G total
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Re: ReadyNAS Duo v1 - Full OS Partition?
So: /sysroot/var/log/frontview/error.log at 1.1G would appear to be the biggest. Is this the likely culprit? What is the recommended next steps. Really appreciate your help here. Thanks so much.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Re: ReadyNAS Duo v1 - Full OS Partition?
The error log is full of "File does not exist: /frontview/ui/resource/html/presence"
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Re: ReadyNAS Duo v1 - Full OS Partition?
Should be safe to empty that one. That's got the errors related to the http/s service we use. If a problem is still there then likely fresh errors would start appearing in that one again.
You should try to free a bit more space than just that, but that's certainly the main one in this case.
You should then also check if files such as /etc/default/services, /etc/network/interfaces and others for which the default config is in /etc/default/config, look fine or whether they've been corrupted.
Which firmware are you running btw?
# cat /var/log/raidiator_version
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Re: ReadyNAS Duo v1 - Full OS Partition?
Thank you so much! I'm back in business!
I emptied the error log and restarted the NAS. I could now log into the admin page, but my media and backup shares were still not accessible through Windows Explorer.
\\<MYNAS>\media is not accessible. You might not have permission to use this network resource... The network path was not found.
Same result via name or IP address.
In the admin page in the Share Listing, I could see the shares, but only HTTP/S and Delete were visible.
I went into Services/Standard File Protocols and found that CIFS was no longer enabled. Switched it on, it restarted the service successfully.
Shares now accessible.
Thanks mdgm so much for your help!!
Is there some housekeeping that I should do to prevent a reoccurence?
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Re: ReadyNAS Duo v1 - Full OS Partition?
You may wish to update to 4.1.15, install EnableRootSSH and check the root volume usage from time to time using SSH.