ReadyNAS Pro 6 stuck at Booting...

[SteveMathews]

Help!

For a few days now my Pro 6 has been hanging on the boot screen at about 5% complete.

Prior to this it has been stable for the last 3 months and hapily uploading/ synchronising to the Amazon Cloud. I expect the problem is tha the log files have swamped the partition but i can't confirm this and and i'm not sure how to proceeed!

can anyone help?

thanks

Steve 

[StephenB · Accepted solution]

---

@SteveMathews wrote:

if these are any help

---

Not really, ls -i shows the inode for each file, but it doesn't give you the number of inodes used.

If you use dlna, then go into /var/cache and delete the contents of the dlna cache folder.  

Then perhaps just try booting again.

[StephenB]

What firmware are you running?

[SteveMathews]

sorry, yes should have added it's on 6.6.0

thanks

Steve

[StephenB]

Was ssh enabled?  If so, see if you can log in that way.

[SteveMathews]

ssh was enabled but unfortunately it doesn't get far enought in the boot process to allow me to access with ssh

[StephenB]

did you try booting "read-only"?

[SteveMathews]

How do you do that? the only boot options i was aware of are:

Your storage system has the following boot modes:

• Normal. Initiates a normal boot process, just like booting using the Power button.
• Factory default. ...
• OS reinstall. ...
• Tech support. ...
• Skip volume check. ( ...
• Memory test. ...
• Disk test.

[StephenB]

I could be wrong here, since I am not running OS 6 on my pro.  But my understanding was that the conversion process also upgraded the boot loader.  Perhaps @mdgm-ntgr will chime in.

Maybe try the boot menu, and see what options are presented on the LCD???  If you don't see the "volume read-only", then maybe try "Skip Volume Check".  

Going in via tech support mode might be needed to assess the OS partition - you can then log in via telnet and manually mount it.  But that's messy.

[SteveMathews]

I can't see a read-only option and running the 'skip volume check' it still hangs on boot and it not accessable from ssh.

are there any instructions for how to go in via tech support mode?

thanks

steve

[StephenB]

Here's a link that might help:  https://onlyblueatwork.wordpress.com/2012/12/04/netgear-readynas-access-recovery/

Disclaimer:  I've never needed to do it myself.

[mdgm-ntgr]

Let us know how you get on. It's quite possible the problem could be a full 4GB root volume, but it could also be something else again.

[SteveMathews]

I may be getting somewhere but i keep getting kicked-out

Welcome to Secure Shell version 0.8.34.4.
Answers to Frequently Asked Questions: https://goo.gl/muppJj

[Pro Tip] Use 'Open as Window' to keep Control-W from closing your terminal!
[Pro Tip] See https://goo.gl/muppJj for more information.

Connecting to root/infr8ntdebug@192.168.0.51, port 23...
Loading NaCl plugin... done.

ssh_exchange_identification: Connection closed by remote host
NaCl plugin exited with status code 255.
(R)econnect, (C)hoose another connection, or E(x)it?
Connecting to root/infr8ntdebug@192.168.0.51, port 23...
Loading NaCl plugin... done.

ssh_exchange_identification: Connection closed by remote host
NaCl plugin exited with status code 255.
(R)econnect, (C)hoose another connection, or E(x)it?

Any ideas?

thanks

Steve 

[SteveMathews]

scrub that last comment - i was being a muppet!

Now i'm using telnet i'm in and have successfully mounted the drive

/dev/md0 is size 4.90G, used 2.9G Available 721.1M 81% used

is this full enough to prevent booting - i seem to recall in recent times it has been at about the 70-80% level....

thanks

steve

[StephenB]

It is still quite full - mine runs at ~40% full with Crashplan installed.

Check the inode usage also (df . -i)

[SteveMathews]

when i run df -i it returns 

df: invalid operation --i

does this mean the coreutils is not up to date?

i'm very rusty with linux so i'll need to look up some navigation commands before i go hunting around for the space-wasting files.

do you know where i'm likley to find the log files (most likely for amazon cloud sync) (and how to navigate there!)

thanks again

Steve

[StephenB]

---

@SteveMathews wrote:

when i run df -i it returns 

df: invalid operation --i

---

You need a path (which I left out).  For instance df . -i ought to give you the inode usage of the file system you are in.

[SteveMathews]

I still have a problem running this

# cd
# pwd
/root
# df  . -i
df: invalid option -- i
BusyBox v1.24.1 (2016-09-16 09:58:20 PDT) multi-call binary.

Usage: df [-PkmhT] [FILESYSTEM]...

[SteveMathews]

I did manage to get ls -i working though

# ls -i
     19 bin          417 init         256 mnt          176 run          213 tmp
      3 dev          123 lib          169 opt          177 sbin         214 usr
     66 etc          416 lib64          1 proc           1 sys          407 var
    122 home         167 media         18 root         212 sysroot

and ls -l

# ls -l
drwxr-xr-x    2       940 Sep 23 18:46 bin
drwxr-xr-x   13      3280 Nov 22 14:06 dev
drwxr-xr-x   11       820 Nov 22 14:06 etc
drwxr-xr-x    2        40 Sep 16 11:08 home
-rwxr-xr-x    1     74336 Sep 23 18:46 init
drwxr-xr-x    4       760 Sep 23 18:46 lib
lrwxrwxrwx    1         3 Sep 16 10:52 lib64 -> lib
drwxr-xr-x    3        60 Nov 22 12:44 media
drwxr-xr-x    1       302 Nov 18 17:06 mnt
drwxr-xr-x    2        40 Sep 16 10:46 opt
dr-xr-xr-x  118         0 Nov 22 12:44 proc
drwx------    3       140 Nov 22 15:28 root
drwxr-xr-x    3       100 Nov 22 14:06 run
drwxr-xr-x    2       700 Sep 23 18:46 sbin
dr-xr-xr-x   12         0 Nov 22 12:44 sys
drwxr-xr-x    2        40 Sep 16 10:46 sysroot
drwxrwxrwt    2        60 Nov 22 12:44 tmp
drwxr-xr-x    6       140 Sep 16 11:08 usr
drwxr-xr-x    6       120 Sep 26 18:53 var

if these are any help

[StephenB · Accepted solution]

---

@SteveMathews wrote:

if these are any help

---

Not really, ls -i shows the inode for each file, but it doesn't give you the number of inodes used.

If you use dlna, then go into /var/cache and delete the contents of the dlna cache folder.  

Then perhaps just try booting again.

[SteveMathews]

Bingo!

It's working now!

The worst files seemed to be in my squeezebox lib folder

artwork - 200Mb, and

spotify cache - 150Mb

I deleted both of these and it seems to be booting-up fine now.

I've ssh'd back in and the 4G partition is now at 71% which is higher than i'd like so i'll do a bit more digging over the next few days 

But i'm just relieved to have got it back up 

Thanks v much StephenB

Steve

[StephenB]

---

@SteveMathews wrote:

It's working now!

---

Great!  Glad I was able to help.