Frontview missing images / JS after USB Recover

[jwishnie]

ReadyNAS NV+

Just stopped accepting SSH and HTTP connections.

Performed USB Restore with 4.1.14 image from here:
http://www.readynas.com/download/suppor ... 4.1.14.img

Frontview comes up with no images, no iframes, no js. Looks like this:


Performed OS Reinstall.

Same results.

I can ssh to the device now and see the following errors in Frontview error log:

[Sun Nov 16 01:28:16 2014] [error] [client 10.0.0.146] File does not exist: /frontview/ui/resource/js, referer: https://10.0.0.106/admin/
[Sun Nov 16 01:28:16 2014] [error] [client 10.0.0.146] File does not exist: /frontview/ui/resource/images, referer: https://10.0.0.106/admin/
[Sun Nov 16 01:28:16 2014] [error] [client 10.0.0.146] File does not exist: /frontview/ui/resource/theme, referer: https://10.0.0.106/admin/

Looking at the Frontview directory, the files do not exists!

# ls -a /frontview/ui/resource/
.  ..  html

What's going on? Can I restore these missing directories from somewhere and get frontview working again?

[mdgm-ntgr]

# df -h
# df -i

USB Boot Recovery really is a last resort and usually other things should be tried first.

[jwishnie]

Unable to connect to the device on any port and it only responding to ping, USB restore seemed the _least_ drastic thing I could do. But am happy to take your guidance!

# df -i
Filesystem            Inodes   IUsed   IFree IUse% Mounted on
/dev/hdc1             128000   26585  101415   21% /
tmpfs                  31583       1   31582    1% /USB
/dev/c/c             91455488  690490 90764998    1% /c
# df -h
Filesystem            Size  Used Avail Use% Mounted on
/dev/hdc1             1.9G  2.0G  9.7M 100% /
tmpfs                  16k     0   16k   0% /USB
/dev/c/c              2.7T  2.0T  786G  72% /c

[mdgm-ntgr]

Well USB Boot Recovery only helps if the firmware on the internal flash is corrupt.

Your output above shows that your 2GB OS partition is full. Since it is full the OS re-install could not complete successfully.

You will need to find what is filling it.

# du -csh /var/*
# du -csh /var/log/*
# du -csh /var/log/frontview/*
# du -csh /var/log/frontview/backup/*

You may wish to copy huge log files onto the data volume /c, then empty them e.g. (note the examples below might not be what is filling the OS partition)///

# mkdir /c/.logs
# cp /var/log/frontview/error.log /c/.logs
# echo "" > /var/log/frontview/error.log
# cp /var/log/upnp-av.log /c/.logs
# echo "" > /var/log/upnp-av.log

After you have freed up some space the next thing would to be check some config files (/etc/default/services, /etc/passwd, /etc/network/interfaces etc.) have not been corrupted and if all is O.K. then do another OS re-install

[jwishnie]

Thank you, that's super helpful. I will look for what is taking the space and let you know if a OS reinstall works once cleaned out.

So far:

/var/cache/minidlna is ~.5GB of cached art...

And Holy Cr*p, kernel.log is ~800MB--is there no logrotation by default?

[mdgm-ntgr]

Well you could remove that. There's likely other things as well that are filling it up, so keep looking. Usage of the OS partition should be well below 1GB.

Then after the OS Re-install install this Sparc add-on: http://www.readynas.com/forum/viewtopic.php?p=392371#p392371

Installing this add-on once will get the ReadyDLNA cache to be stored on the data volume instead of the OS partition. This would be a help as your OS partition would be less likely to fill up. Installing the Toggle add-on a second time would change it back to using the OS partition (not recommended).

[jwishnie]

Thanks mdgm, looks like Frontview, Kernel, and MiniDLNA logs are the culprits. I use that addon and maybe set up a logrotate cron job...

[mdgm-ntgr]

We already have log rotation setup though you could make it more aggressive.

Though if those logs filled up extremely quickly they may have been filled after the log rotation was run and before the next scheduled run of log rotation.