NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
ReadyNAS NV (Sparc) OS Partition Full
Hi
I've been doing a lot of googling and think I'm nearly at the point I can get access back to my NV Frontview.
Basically, NFS started to fail, then CIFS went down, then I got all sorts of odd things happen in frontview. Anyway, I first did the reinstall OS boot option thinking that would help, but then I got corrupt Frontview (did get CIFS access back though), so now I've managed to get in via telnet (I never have enablled rootSSH access), mounted the OS partition like so:
# /bin/start_raid.sh
# mount /dev/hdc1 /sysroot
# /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 10M 100% /sysroot
# /sysroot/bin/df -i
Filesystem Inodes IUsed IFree IUse% Mounted on
rootfs 2048 248 1800 13% /
/dev/root 2048 248 1800 13% /
tmpfs 31583 1 31582 1% /dev/shm
/dev/hdc1 128000 7789 120211 7% /sysroot
# /sysroot/usr/bin/du -csh /sysroot/var/log/*
0 /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
32k /sysroot/var/log/LeafP2P.log.old.old.old.old
64k /sysroot/var/log/auth.log
64k /sysroot/var/log/cron.log
64k /sysroot/var/log/cups
80k /sysroot/var/log/daemon.log
16k /sysroot/var/log/ddns
32k /sysroot/var/log/debug
16k /sysroot/var/log/dmesg
0 /sysroot/var/log/dmesg.old
32k /sysroot/var/log/exim
720k /sysroot/var/log/frontview
32k /sysroot/var/log/fsck.log
3.1M /sysroot/var/log/kern.log
16k /sysroot/var/log/ksymoops
0 /sysroot/var/log/lpr.log
0 /sysroot/var/log/mail.log
3.1M /sysroot/var/log/messages
16k /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
16k /sysroot/var/log/ntpstats
0 /sysroot/var/log/proftpd.log
0 /sysroot/var/log/proftpd.log.old
0 /sysroot/var/log/proftpd.log.old.old
0 /sysroot/var/log/proftpd.log.old.old.old
0 /sysroot/var/log/proftpd.log.old.old.old.old
0 /sysroot/var/log/proftpd.log.old.old.old.old.old
0 /sysroot/var/log/proftpd.log.old.old.old.old.old.old
0 /sysroot/var/log/proftpd.log.old.old.old.old.old.old.old
0 /sysroot/var/log/proftpd.log.old.old.old.old.old.old.old.old
32k /sysroot/var/log/proftpd.log.old.old.old.old.old.old.old.old.old
16k /sysroot/var/log/raidiator_version
0 /sysroot/var/log/raidiator_version.old
192k /sysroot/var/log/samba
1.7G /sysroot/var/log/syslog
16k /sysroot/var/log/user.log
1.7G total
So, can I safely clean /sysroot/var/log/syslog with the follwing?
echo "" > /sysroot/var/log/syslog
if I should first copy it to the data partition, how to do first mount that?
Many thanks in advance
21 Replies
Replies have been turned off for this discussion
That's the main log. Best to copy it in case it contains something important in case there's something else wrong.
If you're familiar with LVM2 commands such as vgscan and vgchange it's pretty straightforward to mount the data volume (at your own risk of course and assuming the data volume is fine).
That's what I thought, but unfortunately I don't have a scooby when it comes to LVM2 commands such as vgscan and vgchange.
I'm pretty sure my data volume is fine.
Any chance you could let me know the commands I would need to mount it?
Thanks again.
Ok, a bit more googling gets me:
start_raid.sh
mount /dev/hdc1 /sysroot
chroot /sysroot
mount proc
vgscan
vgchange -ay c
mount -aObviously I've done the first two lines to get me where I am now, but is the rest of that sequence of commands correct? I'd rather copy the syslog if I can.
The only reason to copy it to the data volume is to archive it for later analysis. It's good to keep it of course, but if you aren't familar with the commands you could get into trouble.
You could just empty it and get the NAS running again. Then regularly download the logs from the web ui over the next days/weeks, and keep an eye on the sizes and also the contents of syslog.
- http://kb.netgear.com/app/answers/detail/a_id/20684/~/readynas-downloads?cid=wmt_netgear_organic
This shows me 4.1.14, as does clicking "Check for Update".
Where do I go for the latest version (it used to be so much easier on readynas.com)?Googling "ReadyNAS 4.1.15" works. http://kb.netgear.com/app/answers/detail/a_id/30914/~/raidiator-version-4.1.15-(sparc)
It should be showing up on the update server though.
Aaaaaaaagh!
I thought I now how a fully working system again, but it appears that I can't remotely write files via FTP.
I think I've narrowed this down to the FTP server on the ReadyNAS ignoring the values I've input for the passive port range, so when an FTP client issues the PASV command, the response if more often than not a port well outside the range I've specified (and opened in firewalls at each location), in this case ports 1024-1074.
This explains why for the last two days most of the files that have been written (they come from a remote IP camera periodically saving still jpegs to the ReadyNAS) have zero byte length while the odd file is sucessfully written (when the random passive port gets lucky and falls in the range opened in the firewalls.
Can anyone help me get the FTP server on the ReadyNAS to correctly use the range specified in Frontview once more? I did download the logs and in services.conf it matches what I have in frontview:
FTP_MODE=user
FTP_PASSIVE_END=1074
FTP_PASSIVE_START=1024
FTP_PORT=21
FTP_UPLOAD_RESUME=1There are also loads of entries in daemon.log like:
Sep 20 16:29:47 MyNAS proftpd[26292]: MyNAS ((*clientexternalip*)[*clientexternalip*]) - Refused PORT 192,168,254,2,234,158 (address mismatch)
which I'm assuming is only because the FTP client on the IP camera is trying active mode since passive mode is failing?
Is my only option now to use EnableRootSSH and manually configure the ProFTPd config? (I suppose worrying about voiding the warranty on a NAS this old is a little pointless anyway).
Did the IP camera ever work?
rickwookie wrote:
Sep 20 16:29:47 MyNAS proftpd[26292]: MyNAS ((*clientexternalip*)[*clientexternalip*]) - Refused PORT 192,168,254,2,234,158 (address mismatch)
.
This is port 60062 (234*256+158). It could be an active connection.
Did the NAS IP address change? Can you give any details on the camera's FTP configuration, and/or a more complete connection log?
It's been working every weekday for the last two months, right up until I did the OS re-install that corrupted Frontview this last weekend. No IP addresses or hostnames have changed at either end and my firewall router configuration is the same.
I've actually gone ahead now and enabled the SSH access, since I figured there was no way this was going to get resolved using Frontview alone, and Telnet-ing in using the support mode was a real pain tbh.
FTP tranfers are now compleating successfully, since I've added
PassivePorts 1024 1074
to /etc/proftpd.conf
The entire file consisted of just:
Include /etc/frontview/proftpd/ftps.conf
Include /etc/frontview/proftpd/User.confand neither of those files, nor /etc/frontview/proftpd/Shares.conf that User.conf 'Include's make any reference to PassivePorts or FTP_PASSIVE_START or anything like it.
I would love to know where the link is from the frontview settings to the proftpd config files to make it all work as it should again, but for now at least I've got the FTP server configured to work as I need it.
I strongly suspect that there will be other settings from the file services page that are not making it through to the associated configs, but maybe they are working as expect with the default settings. Certainly Master Browser is suspect since the ReadyNAS doesn't seem to show up under Network in Windows Explorer anymore, but I can browser it fine if I type the hostname or IP address into the address bar.
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
