Front view does not load any more

[Stevenup]

Hi guys, 

after my NAS cashed recently i managed to restart it - via OS reninstall follwoing the step by step in the user manual. 

Now the ready nas has finisched the data check and i can access all data via file explorere via my windows computer. 

However i can no longer load front view. i did try to clear the catch on google chome, installed firefox and used IE but no luck. frontview is not loading. 

Using Raidar - it connects ok and shows all status ok (green). Ready NAS ver uses 4.1.14. 

Raidar v. 4.3.8

I dont know if i can access NAS via SSH - dont know how to use SSH - but is there a way of checking the log file of the OS partition via MS dos commands to clear the log ? or can is there another way to clear the NAS OS log files by booting via USB with ReadyNAS v 4.1.16 (latest) ? 

from reading the posts here on the forum, i believe the log file on the OS partition is full.

thanks for you help and support to get it back online. 

cheers, steven 

[mdgm]

A full 2GB OS partition is one possible reason that Frontview won't load. There are other possibilities e.g. a broken config usually related to an add-on. If it is a full OS partition or broken config and you can still access your data it's probably a straightforward fix, but it may not be.

You can't SSH in if you have not already enabled it, unfortunately. That would be the simplest way to troubleshoot this.

You can however boot to tech support mode (power down, then once it has powered off press and hold POWER button for about 15 seconds. The disk LEDs will blink about once every 5 seconds. Release the POWER button after the third blink).

Telnet can be used to troubleshoot it in tech support mode.

However if you are not familiar with that you may be better off backing up your data, then doing a factory reset (wipes all data, settings, everything) and restoring data from backup. Though the factory reset wipes everything including your logs so you wouldn't know for sure what went wrong.

[Stevenup]

hi mdgm, 

thanks for that - i am no expert but i managed to connect to the nas via telnet. please can you advicse the commands i need to use to find the OS partition and see the size of the log file? happy to privide screen shots for you to review and advise future instructions. 

The Factory is also a possiblity - however i prefrere to learn something here and like to attempt to fix it via telnet if you guys can assist me and guid me through this process. 

thanks, Steven 

[Stevenup]

see SSH screenshot. where to from here? thanks 

[StephenB]

Of course we don't know exactly what you did after you logging into the NAS.  Normally you'd enter the following commands to get normal access to the OS partition:

# start_raid.sh
# mount /dev/hdc1 /sysroot
# mount --bind /proc /sysroot/proc
# mount --bind /dev /sysroot/dev
# mount --bind /dev/pts /sysroot/dev/pts
# chroot /sysroot /bin/bash

This assumes you are running XRAID. (Note you don't actually enter the # at the beginning).

After that you can look at the OS fullness by entering:

# df // -h
# df // -i

The first command tells you how much free space there is on the OS partition.   Normally only 25% of the space is used.

The second command tells you how many inodes are used.  It's rare to run out of inodes, but it can happen, so it's worth checking.

[Stevenup]

Hi StephenB, 

thank you soo much for your help and support. I hvae managed to follow your instructions and connect via Telnet to my NAs. i then used the code you provided and to the follwoing information back. 

root@24M39C7S0028C:/# df // -h
Filesystem Size Used Avail Use% Mounted on
/dev/hdc1 1.9G 2.0G 6.6M 100% /
root@24M39C7S0028C:/# df // -i
Filesystem Inodes IUsed IFree IUse% Mounted on
/dev/hdc1 128000 14356 113644 12% /
root@24M39C7S0028C:/# 

also see - attached print screen. 

however, i am not sure how to interprete the above - is this confirming the OS partition is full (100%) - if so, where to from here? 

if you could guid me with future code - or advise future steps - much appreciatd

thanks steven . 

[StephenB]

---

@Stevenup wrote:

however, i am not sure how to interprete the above - is this confirming the OS partition is full (100%) - if so, where to from here? 

---

Yes, this confims that the OS partition is full (only 6.6M left).

The next step is to figure out where the space is going (and why).

• Do you have any add-ons installed?
• Do you use ReadyDLNA?

ReadyDLNA by default put its cache in the OS partition, but there is an add-on that will move that to the C volume. 

Another possibility is that the logs are simply too big.  So also try

# df /var/log -h

and post that info here.

[Stevenup]

Hi StephenB, 

thank you, 

I have entered the code you provided and got this:

I did not us DLNA or any other apps in my configuration while in use. 

however - did after the crash do a USB boot verson 4.1.16 and a OS reinstall. 

So i dont know if any of the above apps or ReadyDLNA would be activated by default. 

I would also have to check both hard drives for errors/fault. I am not 100% sure even though they are less then two years old HD. 

thank you for your future advise on how the clear the catch and any other suggestoins on finxing this issue. 

Steven 

[Stevenup]

Here again the screen shot as it has not worked in the previous post.

[mdgm]

He meant du not df

# du -csh /var/log

[Stevenup]

Hi mdgm, 

when i use your code command, this will be shown on telnet:

root@24M39C7S0028C:/# du -csh /var/log
1.4G /var/log
1.4G total
root@24M39C7S0028C:/#

[StephenB]

---

@mdgm wrote:

He meant du not df

# du -csh /var/log

---

Yes, sorry about that...

[StephenB]

That's the problem then (or at least most of it).

Try doing 

# find /var/log -printf '%s %p\n'| sort -nr | head -10

That should tell you which log file(s) are too big.  You should see a list of the biggest 10 files sorted by size (largest first).

[Stevenup]

I have now entered the last part of the code you sent to identify the log file size and which they are. this is what i got. 

root@24M39C7S0028C:/# find /var/log -printf '%s %p\n'| sort -nr | head -10
404781868 /var/log/syslog
396760372 /var/log/messages
396533839 /var/log/kern.log
183844899 /var/log/LeafP2P.log
33604440 /var/log/upnp-av.log
1360322 /var/log/frontview/spool.err
806782 /var/log/frontview/error.log
393862 /var/log/frontview/access.log
262674 /var/log/cron.log
262164 /var/log/samba/log.nmbd.old

Print screen also attached. I hope the above tells you more than me. 

What are the next steps from here? 

Thanks again for your great support. much appreciated to do this with your advise and no knowledge of coding !! Stephan 

[StephenB]

---

@Stevenup wrote:

I have now entered the last part of the code you sent to identify the log file size and which they are. this is what i got. 

root@24M39C7S0028C:/# find /var/log -printf '%s %p\n'| sort -nr | head -10
404781868 /var/log/syslog
396760372 /var/log/messages
396533839 /var/log/kern.log
183844899 /var/log/LeafP2P.log

...

---

Well, these 4 total ~1.28 GiB, which is about 65% of the space in your OS partition. Though I think syslog and messages are actually folders, and not files. 

Try truncating the last two (which will empty them, so they will be 0 size).

# echo > var/log/kern.log
# echo > var/log/LeafP2P.log

That might be enough to let you reboot the NAS and get into frontview.  You can then try clearing the logs from Frontview. 

Though it might be better if you look into var/log/syslog and /var/log/messages, and see if there is a large file in those folders that is taking the space.  If there is, you can truncate those as well. You can use ls for that, or adjust the command to 

# find /var/log/syslog -printf '%s %p\n'| sort -nr | head -10
# find /var/log/messages -printf '%s %p\n'| sort -nr | head -10

[Stevenup]

---

I have entered the to lines of code belwo - and tried to restart after that to see if i can reach front view - didnt work. System check to 12 hours but front view did not load at all. 

Try truncating the last two (which will empty them, so they will be 0 size).

# echo > var/log/kern.log
# echo > var/log/LeafP2P.log

That might be enough to let you reboot the NAS and get into frontview.  You can then try clearing the logs from Frontview. 

THis is what i go: 

root@24M39C7S0028C:/# find /var/log -printf '%s %p\n'| sort -nr | head -10
404825816 /var/log/syslog
396800323 /var/log/messages
183844899 /var/log/LeafP2P.log
33604440 /var/log/upnp-av.log
1360322 /var/log/frontview/spool.err
806782 /var/log/frontview/error.log
393862 /var/log/frontview/access.log
292701 /var/log/cron.log
262164 /var/log/samba/log.nmbd.old
173142 /var/log/auth.log

Though it might be better if you look into var/log/syslog and /var/log/messages, and see if there is a large file in those folders that is taking the space.  If there is, you can truncate those as well. You can use ls for that, or adjust the command to 

# find /var/log/syslog -printf '%s %p\n'| sort -nr | head -10
# find /var/log/messages -printf '%s %p\n'| sort -nr | head -10

---

Then i repeated the procedure and entered the two lines above and got the follwoing: 

root@24M39C7S0028C:/# find /var/log/syslog -printf '%s %p\n'|sort -nr | head -10
404825816 /var/log/syslog
root@24M39C7S0028C:/# find /var/log/messages -printf '%s %p\n' | sort -nr | head -10
396800323 /var/log/messages
root@24M39C7S0028C:/#

After doing the above i have again restarted the system normally - however sitll front view does not start up or is reachable. 

to see all the code and results see print screen attached. 

Where to from here? thank you guys. 

Steven 

[StephenB]

I suggest that you shouldn't put your responses inside one of my quotes, as it makes it hard for me sort out what you are saying.  

How much free space do you have in the OS partition at the moment?  (You'll need to do the df // -h command again in order to see that).

[StephenB]

Also, I just fired up my own NV+, and looked at /var/log

syslog and messages are both files, not folders.  So you can truncate them as well.

# echo > var/log/syslog
# echo > var/log/messages

That will free up about 760 MiB of space.

[Stevenup]

Hi Sorry it has taken me a while to get back to you. 

For my understanding to check the free space on the OS partition can i just connect to the NAS and straigth away type in the one line of code for that or do i always have to go thorugh the first few lines of code from one of the first replys before using the du //-i and du//-h commands? /var/log

today as i tried it again i got all of this not sure whats going on but Front view is still not working! 

thanks guys or your help. 

Steven 

BusyBox v1.2.1 (2010.01.20-23:43+0000) Built-in shell (ash)
Enter 'help' for a list of built-in commands.

# find /var/log/syslog -pringf '%s %p\n' | sort -nr | head -10
-sh: sort: not found
-sh: head: not found
# start_raid.sh
# mount /dev/hdc1 /sysroot
# mount --bind /proc /sysroot/proc
# mount --bind /dev /sysroot/dev
# mount --bind /dev/pts /sysroot/dev/pts
# chroot /sysroot /bin/bash
root@24M39C7S0028C:/# df //-h
df: `//-h': No such file or directory
root@24M39C7S0028C:/# df // -i
Filesystem Inodes IUsed IFree IUse% Mounted on
/dev/hdc1 128000 14368 113632 12% /
root@24M39C7S0028C:/# du -csh /var/log
804M /var/log
804M total
root@24M39C7S0028C:/# find /var/log -printf '%s %p/n'| sort -nr | head -10
16384 /var/log/n16384 /var/log/cups/n3824 /var/log/cups/error_log/n148892 /var/log/cups/access_log/n0 /var/log/cups/access_log.O/n0 /var/log/cups/page_log/n0 /var/log/cups/error_log.O/n0 /var/log/cups/access_log.old/n0 /var/log/cups/access_log.O.old/n0 /var/log/cups/error_log.old/n0 /var/log/cups/page_log.old/n0 /var/log/cups/error_log.O.old/n0 /var/log/cups/page_log.old.old/n0 /var/log/cups/access_log.old.old/n0 /var/log/cups/access_log.O.old.old/n0 /var/log/cups/access_log.old.old.old/n0 /var/log/cups/access_log.O.old.old.old/n0 /var/log/cups/access_log.old.old.old.old/n0 /var/log/cups/access_log.O.old.old.old.old/n0 /var/log/cups/access_log.old.old.old.old.old/n0 /var/log/cups/access_log.O.old.old.old.old.old/n0 /var/log/cups/access_log.old.old.old.old.old.old/n16384 /var/log/exim/n0 /var/log/exim/mainlog/n22515 /var/log/exim/paniclog/n0 /var/log/exim/mainlog.old/n0 /var/log/exim/paniclog.old/n0 /var/log/exim/mainlog.old.old/n0 /var/log/exim/mainlog.old.old.old/n0 /var/log/exim/mainlog.old.old.old.old/n0 /var/log/exim/mainlog.old.old.old.old.old/n0 /var/log/exim/mainlog.old.old.old.old.old.old/n0 /var/log/exim/mainlog.old.old.old.old.old.old.old/n16384 /var/log/frontview/n16384 /var/log/frontview/backup/n116 /var/log/frontview/memory.log/n1038 /var/log/frontview/spool.log/n1360322 /var/log/frontview/spool.err/n0 /var/log/frontview/.update_checked/n0 /var/log/frontview/.Advanced/n806782 /var/log/frontview/error.log/n393862 /var/log/frontview/access.log/n50 /var/log/frontview/smart_errors_hdc/n114 /var/log/frontview/status.log-sync/n50 /var/log/frontview/smart_errors_hde/n209 /var/log/frontview/disk_usage.log/n0 /var/log/frontview/partitions_2010_05_30.log/n0 /var/log/frontview/partitions_2010_04_25.log/n0 /var/log/frontview/partitions_2010_02_28.log/n0 /var/log/frontview/command.log/n0 /var/log/frontview/status.log-old/n0 /var/log/frontview/partitions_2011_03_06.log/n0 /var/log/frontview/.admin_passwd_changed/n0 /var/log/frontview/partitions_2010_06_06.log/n0 /var/log/frontview/partitions_2010_05_02.log/n0 /var/log/frontview/partitions_2010_03_07.log/n0 /var/log/frontview/partitions_2010_06_13.log/n0 /var/log/frontview/partitions_2010_05_09.log/n0 /var/log/frontview/partitions_2010_03_21.log/n0 /var/log/frontview/partitions_2010_06_20.log/n325 /var/log/frontview/enclosure.log/n0 /var/log/frontview/partitions_2010_05_16.log/n0 /var/log/frontview/partitions_2010_04_04.log/n302 /var/log/frontview/partitions_2011_08_07.log/n302 /var/log/frontview/partitions_2010_06_27.log/n0 /var/log/frontview/partitions_2010_05_23.log/n302 /var/log/frontview/partitions_2010_04_18.log/n302 /var/log/frontview/partitions_2010_07_04.log/n302 /var/log/frontview/partitions_2010_07_11.log/n302 /var/log/frontview/partitions_2010_07_25.log/n302 /var/log/frontview/partitions_2011_05_01.log/n302 /var/log/frontview/partitions_2010_10_10.log/n302 /var/log/frontview/partitions_2010_08_01.log/n508 /var/log/frontview/ecounter_2021_01_07_1256.log/n302 /var/log/frontview/partitions_2010_08_08.log/n302 /var/log/frontview/partitions_2010_08_15.log/n302 /var/log/frontview/partitions_2010_08_29.log/n302 /var/log/frontview/partitions_2010_08_22.log/n302 /var/log/frontview/partitions_2010_09_05.log/n302 /var/log/frontview/partitions_2010_09_12.log/n302 /var/log/frontview/partitions_2010_09_19.log/n302 /var/log/frontview/partitions_2010_09_26.log/n302 /var/log/frontview/partitions_2010_07_18.log/n302 /var/log/frontview/partitions_2010_10_03.log/n302 /var/log/frontview/partitions_2010_10_17.log/n302 /var/log/frontview/partitions_2010_10_24.log/n302 /var/log/frontview/partitions_2010_10_31.log/n302 /var/log/frontview/partitions_2010_11_09.log/n302 /var/log/frontview/partitions_2010_11_14.log/n302 /var/log/frontview/partitions_2010_11_21.log/n302 /var/log/frontview/partitions_2010_11_28.log/n302 /var/log/frontview/partitions_2010_12_05.log/n302 /var/log/frontview/partitions_2010_12_12.log/n302 /var/log/frontview/partitions_2010_12_19.log/n302 /var/log/frontview/partitions_2010_12_26.log/n302 /var/log/frontview/partitions_2011_01_02.log/n302 /var/log/frontview/partitions_2011_01_09.log/n302 /var/log/frontview/partitions_2011_01_17.log/n302 /var/log/frontview/partitions_2011_01_23.log/n302 /var/log/frontview/partitions_2012_04_08.log/n302 /var/log/frontview/partitions_2011_01_30.log/n302 /var/log/frontview/partitions_2012_11_11.log/n302 /var/log/frontview/partitions_2011_02_06.log/n302 /var/log/frontview/partitions_2011_02_13.log/n302 /var/log/frontview/partitions_2011_02_20.log/n302 /var/log/frontview/partitions_2011_02_27.log/n302 /var/log/frontview/partitions_2011_03_13.log/n302 /var/log/frontview/partitions_2011_03_20.log/n302 /var/log/frontview/partitions_2011_04_01.log/n302 /var/log/frontview/partitions_2011_04_03.log/n302 /var/log/frontview/partitions_2011_04_10.log/n6287 /var/log/frontview/status.log-new/n302 /var/log/frontview/partitions_2012_12_30.log/n302 /var/log/frontview/partitions_2011_04_17.log/n302 /var/log/frontview/partitions_2011_04_24.log/n9534 /var/log/frontview/disk_smart_2012_12_30.log/n302 /var/log/frontview/partitions_2011_05_20.log/n302 /var/log/frontview/partitions_2011_05_22.log/n302 /var/log/frontview/partitions_2011_05_29.log/n302 /var/log/frontview/partitions_2011_06_05.log/n302 /var/log/frontview/partitions_2011_06_12.log/n302 /var/log/frontview/partitions_2011_06_19.log/n302 /var/log/frontview/partitions_2011_06_26.log/n302 /var/log/frontview/partitions_2011_07_03.log/n302 /var/log/frontview/partitions_2011_07_10.log/n302 /var/log/frontview/partitions_2011_07_17.log/n302 /var/log/frontview/partitions_2011_07_24.log/n302 /var/log/frontview/partitions_2011_07_31.log/n302 /var/log/frontview/partitions_2011_08_14.log/n302 /var/log/frontview/partitions_2011_08_21.log/n302 /var/log/frontview/partitions_2011_08_28.log/n302 /var/log/frontview/partitions_2011_09_04.log/n302 /var/log/frontview/partitions_2011_09_11.log/n302 /var/log/frontview/partitions_2011_09_18.log/n302 /var/log/frontview/partitions_2011_09_25.log/n302 /var/log/frontview/partitions_2011_10_02.log/n302 /var/log/frontview/partitions_2011_10_17.log/n302 /var/log/frontview/partitions_2011_10_27.log/n302 /var/log/frontview/partitions_2011_10_30.log/n302 /var/log/frontview/partitions_2011_11_06.log/n302 /var/log/frontview/partitions_2011_11_13.log/n302 /var/log/frontview/partitions_2011_11_20.log/n302 /var/log/frontview/partitions_2011_11_27.log/n302 /var/log/frontview/partitions_2011_12_06.log/n302 /var/log/frontview/partitions_2011_12_13.log/n302 /var/log/frontview/partitions_2011_12_18.log/n302 /var/log/frontview/partitions_2011_12_25.log/n302 /var/log/frontview/partitions_2012_01_01.log/n302 /var/log/frontview/partitions_2012_01_11.log/n302 /var/log/frontview/partitions_2012_01_15.log/n302 /var/log/frontview/partitions_2012_01_22.log/n302 /var/log/frontview/partitions_2012_01_29.log/n302 /var/log/frontview/partitions_2012_02_05.log/n302 /var/log/frontview/partitions_2012_02_12.log/n302 /var/log/frontview/partitions_2012_02_19.log/n302 /var/log/frontview/partitions_2012_03_04.log/n302 /var/log/frontview/partitions_2012_03_11.log/n302 /var/log/frontview/partitions_2012_03_18.log/n302 /var/log/frontview/partitions_2012_03_25.log/n302 /var/log/frontview/partitions_2012_04_01.log/n9534 /var/log/frontview/disk_smart_2013_01_20.log/n302 /var/log/frontview/partitions_2012_04_15.log/n302 /var/log/frontview/partitions_2012_04_22.log/n302 /var/log/frontview/partitions_2012_04_29.log/n302 /var/log/frontview/partitions_2012_05_06.log/n302 /var/log/frontview/partitions_2012_05_13.log/n302 /var/log/frontview/partitions_2012_05_20.log/n302 /var/log/frontview/partitions_2012_05_27.log/n302 /var/log/frontview/partitions_2012_06_03.log/n302 /var/log/frontview/partitions_2012_06_11.log/n302 /var/log/frontview/partitions_2012_06_17.log/n302 /var/log/frontview/partitions_2012_06_24.log/n302 /var/log/frontview/partitions_2012_07_01.log/n302 /var/log/frontview/partitions_2012_08_06.log/n302 /var/log/frontview/partitions_2012_08_12.log/n0 /var/log/frontview/partitions_2012_08_26.log/n0 /var/log/frontview/partitions_2012_08_21.log/n302 /var/log/frontview/partitions_2012_09_23.log/n302 /var/log/frontview/partitions_2012_10_01.log/n302 /var/log/frontview/partitions_2012_10_15.log/n302 /var/log/frontview/partitions_2012_10_21.log/n302 /var/log/frontview/partitions_2012_10_28.log/n302 /var/log/frontview/partitions_2012_11_04.log/n2688 /var/log/frontview/raid_config_2020_04_02.log/n302 /var/log/frontview/partitions_2012_11_25.log/n302 /var/log/frontview/partitions_2012_12_02.log/n302 /var/log/frontview/partitions_2012_12_09.log/n302 /var/log/frontview/partitions_2012_12_16.log/n302 /var/log/frontview/partitions_2012_12_28.log/n5 /var/log/frontview/apache-ssl.pid/n302 /var/log/frontview/partitions_2013_01_06.log/n302 /var/log/frontview/partitions_2013_01_14.log/n302 /var/log/frontview/partitions_2013_01_20.log/n302 /var/log/frontview/partitions_2013_01_27.log/n15 /var/log/frontview/raid_config_2020_02_16.log/n2691 /var/log/frontview/raid_config_2020_08_23.log/n2689 /var/log/frontview/raid_config_2020_12_17.log/n2690 /var/log/frontview/raid_config_2021_01_01.log/n0 /var/log/frontview/memory.log.old/n511 /var/log/frontview/ecounter_2021_01_04_1728.log/n9533 /var/log/frontview/disk_smart_2013_01_06.log/n9534 /var/log/frontview/disk_smart_2013_01_14.log/n503 /var/log/frontview/ecounter_2021_01_06_1719.log/n9533 /var/log/frontview/disk_smart_2013_01_27.log/n2067 /var/log/frontview/raid_config_2020_02_22.log/n2067 /var/log/frontview/raid_config_2021_01_11.log/n2688 /var/log/frontview/raid_config_2020_06_20.log/n0 /var/log/frontview/apache-ssl.pid.old/n2690 /var/log/frontview/raid_config_2020_03_01.log/n0 /var/log/frontview/spool.err.old/n509 /var/log/frontview/ecounter_2021_01_05_1546.log/n2693 /var/log/frontview/raid_config_2019_11_26.log/n0 /var/log/frontview/spool.err.old.old/n0 /var/log/frontview/smart_errors_hdc.old/n0 /var/log/frontview/disk_usage.log.old/n0 /var/log/frontview/spool.err.old.old.old/n0 /var/log/frontview/spool.log.old/n16384 /var/log/frontview/spool.err.old.old.old.old/n0 /var/log/frontview/spool.log.old.old/n2689 /var/log/frontview/raid_config_2020_12_25.log/n16384 /var/log/frontview/spool.log.old.old.old/n511 /var/log/frontview/ecounter_2021_01_06_1357.log/n0 /var/log/frontview/partitions_2010_05_30.log.old/n0 /var/log/frontview/partitions_2010_04_25.log.old/n0 /var/log/frontview/.update_checked.old/n0 /var/log/frontview/status.log-new.old/n0 /var/log/frontview/status.log-old.old/n0 /var/log/frontview/partitions_2010_02_28.log.old/n0 /var/log/frontview/partitions_2011_03_06.log.old/n0 /var/log/frontview/partitions_2010_05_02.log.old/n0 /var/log/frontview/partitions_2010_03_21.log.old/n0 /var/log/frontview/partitions_2010_05_16.log.old/n0 /var/log/frontview/partitions_2010_05_23.log.old/n0 /var/log/frontview/partitions_2012_08_26.log.old/n0 /var/log/frontview/partitions_2012_08_21.log.old/n0 /var/log/frontview/partitions_2010_06_06.log.old/n0 /var/log/frontview/partitions_2010_03_07.log.old/n0 /var/log/frontview/partitions_2010_06_13.log.old/n0 /var/log/frontview/partitions_2010_05_09.log.old/n0 /var/log/frontview/partitions_2010_06_20.log.old/n0 /var/log/frontview/enclosure.log.old/n0 /var/log/frontview/partitions_2010_04_04.log.old/n16384 /var/log/ksymoops/n16384 /var/log/ntpstats/n16384 /var/log/samba/n16384 /var/log/samba/cores/n16384 /var/log/samba/cores/smbd/n0 /var/log/samba/cores/smbd/core/n16384 /var/log/samba/cores/nmbd/n29847 /var/log/samba/log.smbd/n135236 /var/log/samba/log.nmbd/n0 /var/log/samba/log.smbd.old/n262164 /var/log/samba/log.nmbd.old/n16384 /var/log/samba/log.smbd.old.old/n0 /var/log/samba/log.smbd.old.old.old/n32768 /var/log/samba/log.smbd.old.old.old.old/n16384 /var/log/ddns/n42 /var/log/raidiator_version/n2048 /var/log/dmesg/n173142 /var/log/auth.log/n404825816 /var/log/syslog/n292701 /var/log/cron.log/n58429 /var/log/daemon.log/n1 /var/log/kern.log/n0 /var/log/lpr.log/n0 /var/log/mail.log/n7418 /var/log/user.log/n9570 /var/log/debug/n396800323 /var/log/messages/n16384 /var/log/squeezecenter/n0 /var/log/squeezecenter/server.log/n0 /var/log/squeezecenter/perfmon.log/n0 /var/log/squeezecenter/server.log.old/n0 /var/log/squeezecenter/server.log.old.old/n0 /var/log/squeezecenter/server.log.old.old.old/n0 /var/log/squeezecenter/server.log.old.old.old.old/n33 /var/log/slimserver.log/n13254 /var/log/netatalk.log/n33604440 /var/log/upnp-av.log/n102283 /var/log/mt-daapd.log/n0 /var/log/ReadyNAS_Remote.log/n32768 /var/log/fsck.log/n1 /var/log/LeafP2P.log/n0 /var/log/dekoh_out.log/n0 /var/log/LeafP2P.log.old/n0 /var/log/mt-daapd.log.old/n2295 /var/log/readyNASVault.log/n0 /var/log/netatalk.log.old/n59 /var/log/dekoh_error.log/n0 /var/log/mt-daapd.log.old.old/n0 /var/log/LeafP2P.log.old.old/n0 /var/log/mt-daapd.log.old.old.old/n1 /var/log/leafp2p.log/n0 /var/log/mt-daapd.log.old.old.old.old/n0 /var/log/LeafP2P.log.old.old.old/n0 /var/log/mt-daapd.log.old.old.old.old.old/n0 /var/log/LeafP2P.log.old.old.old.old/n0 /var/log/mt-daapd.log.old.old.old.old.old.old/n32768 /var/log/ReadyNAS_Remote.log.old/n0 /var/log/mt-daapd.log.old.old.old.old.old.old.old/n0 /var/log/LeafP2P.log.old.old.old.old.old/n0 /var/log/LeafP2P.log.old.old.old.old.old.old/n0 /var/log/mt-daapd.log.old.old.old.old.old.old.old.old/n0 /var/log/mt-daapd.log.old.old.old.old.old.old.old.old.old/n16384 /var/log/LeafP2P.log.old.old.old.old.old.old.old/n0 /var/log/mt-daapd.log.old.old.old.old.old.old.old.old.old.old/n49152 /var/log/mt-daapd.log.old.old.old.old.old.old.old.old.old.old.old/n
root@24M39C7S0028C:/# echo > log/kern.log
bash: log/kern.log: No such file or directory
root@24M39C7S0028C:/# echo > log/LeafP2P.log
bash: log/LeafP2P.log: No such file or directory
root@24M39C7S0028C:/# find var log/syslog -printf '%s %p\n'| sort -nr | head -10
ffind: log/syslog: No such file or directory
in404825816 var/log/syslog
396800323 var/log/messages
129335296 var/cache/minidlna/files.db
33604440 var/log/upnp-av.log
10485760 var/lib/mysql/ibdata1
7716864 var/cache/e2fsck/8fbe9718-2b05-4c4d-b27a-e5ef23680c6d-dirinfo-zzEPAz
5259264 var/cache/e2fsck/8fbe9718-2b05-4c4d-b27a-e5ef23680c6d-dirinfo-FjFGW8
5242880 var/lib/mysql/ib_logfile1
5242880 var/lib/mysql/ib_logfile0
2575658 var/cache/minidlna/art_cache/c/Music/AC_DC/Jailbreak
root@24M39C7S0028C:/# find /var/log/messages -pringf %s %p\n'| sort -nr | head -10
> df//-h
> df// -h
> start_raid.sh
> mount /dev.hdc1 /sysroot
> mount --bind /proc /sysroot/proc
> mount --bind /dev /sysroot/dev
> mount --bind /dev/pts /sysroot/dev/pts
> chroot /sysroot /bin/bash
> df //-i

---

[StephenB]

---

@Stevenup wrote:

root@24M39C7S0028C:/# df //-h
df: `//-h': No such file or directory

> df//-h
> df// -h

> df //-i

---

---

The spaces after the df and the // in these commands matter, you need to be more careful in your typing.

# df // -h
# df // -i

The first command is the one that matters most, since it gives the total amount of free space on the OS partition.  Can you run that one again?

You have plenty of inodes, so you can stop running the -i one.

---

@Stevenup wrote:

For my understanding to check the free space on the OS partition can i just connect to the NAS and straigth away type in the one line of code for that or do i always have to go thorugh the first few lines of code from one of the first replys before using the du //-i and du//-h commands? /var/log

You need to run them all after you reboot the NAS into tech support mode.  

If you are just reconnecting (w/o rebooting the NAS), just run the chroot one.

---

@Stevenup wrote:

Front view is still not working! 

---

Freeing up the space probably won't be enough.  After we get enough space freed up, we can try doing an OS reinstall.

Did you truncate syslog and messages?

[mdgm]

If freeing up space on the 2GB root volume did not resolve the problem then it's likely some configuration has been corrupted. An OS Re-install probably won't fix that.

[StephenB]

---

@mdgm wrote:

An OS Re-install probably won't fix that.

---

True, but it is easy to try, and it might resolve it.

The only other option I can think of is to back up the files and do a factory default.  I don't think @Stevenup can isolate and repair the configuration.

[Stevenup]

Hi Stephen, 

ok no worries. 

How much space is on the OS: 

root@24M39C7S0028C:/# df // -h
Filesystem Size Used Avail Use% Mounted on
/dev/hdc1 1.9G 1.4G 562M 72% /
root@24M39C7S0028C:/# df // -i
Filesystem Inodes IUsed IFree IUse% Mounted on
/dev/hdc1 128000 14368 113632 12% /

[Stevenup]

root@24M39C7S0028C:/# du -csh /var/log
804M /var/log
804M total
root@24M39C7S0028C:/#

[Stevenup]

Hi Stephen, 

i have now restarted the system with a reinstalled OS system. and i can access front view agina. I have cleared all the loggs and messages. 

i will now update the firmware to 4.1.16 (latest) and let you know how it all goes. 

so far, thanks heaps for your support on this. all data is still there and front view is accessable. 

Steven