unable to connect to admin page. rest is working normal

[Hightower]

I am unable to connect to the administration page. Nothing have been changed since long time. Shares are accessible in windows, Android and media players. Website is running normal. It is given always the same ip adres by the modem.

Can not connect to website is the message
But the webserver is normally accessible
The webpage for the torrent addon (:8080) works fine. But no torrents active.

[Hightower · Accepted solution]

After some attempts to find a 2nd reason why it was not accessible. And I was unable to read or copy the error file (did not know how). I decided to reinstall the os. That did not change anything. So I cleared the whole system. And now I am putting the backup back.
Everything is now almost back as normal.
So problem solved but not the way I would like.
If my knowledge of telnet was as good as good old DOS I would investigate longer and would find and fix the problem. But telnet is way out of my comfort zone.
Thanks for your attempts to help me find the problem.

[StephenB]

What ReadyNAS; what firmware; what apps are installed?

I suggest making sure you have an up-to-date backup of the data.

[Hightower]

Ohh sorry for not putting it on I forgot
It's a readynas duo v1. With 2 x 2tb disc
It has I think the last version of its firmware.
Apps standard plus owncloud. And some apps to see the status on a android app. Don't know the names ans can not see it anymore

Edit addded

I backed up all data and this forum is my last resort before I preform a factory reset. But I am a bit afraid that the administration page remains unavailable after the reset. And only the administration page is unavailable the rest is working fine atm.

[StephenB]

It could be a full OS partition - the v1 only has 2 GB for that.

Is SSH enabled (and if so does it connect?)

[Hightower]

SSH enabled for the Nas utils app.
Failed to connect to /192.168.2.1 (port 22): connecttion refused)
Connect failed: ECONNREFUSED (Connection refused)

[StephenB]

Options are

(a) boot in tech support mode, and telnet into the box.  You'd need to manually mount the OS partition.  There's some info here: https://community.netgear.com/t5/Using-your-ReadyNAS/Readynas-NV-V1-Mounting-OS-partition-in-support...

(b) Try an OS reinstall, and if that fails go right to the factory reset.

[Hightower]

Going to try it this evening.
No experience with telnet but going to Google it.

[Hightower]

connected to the telnet mode od the readynas duo v1,

but all other commands in the link given are not working.

wich directory are the supposed problem giving log files

[StephenB]

Did you get an error when you entered start_raid.sh ?

Log files are in /var/log, but you can't see that unless you can start raid and then mount the OS partition.

[Hightower]

no error with the raid command

only with the sytemroot mounting.

after you set me to the correct path i started searching the community with different key words and i found

this :ReadyNAS-Duo-v1-Full-OS-Partition

and the correct mount for the duo v1 was

# mount /dev/hdc1 /sysroot

and for the NX in your link was

# mount /dev/md0 /sysroot

 that gave the error

so i used the echo > error.log command as shown in that link. as mine was as big as in the link.

but now is the question how to unmount the sysroot and restart the nas it self

edit:

reboot worked in telnet, it just took longer then expected. shares are availible  admin page still not,webserver is not availible and the torrent page is not availible. is this becouse i did not unmount the systemroot yet?

[StephenB]

---

@Hightower wrote:

is this becouse i did not unmount the systemroot yet?

---

No, it should have been unmounted when you did the reboot.

Was the OS partition in fact full?  It's sounding like your admin UI issue has a different cause.

[mdgm-ntgr]

There are possible side effects if the root volume is full e.g. the /etc/default/services file may be corrupted when attempts to modify it fail.

Did you check the tail of that error log before you emptied it to see if it gave any clues as to why Frontview was inaccessible?

[Hightower · Accepted solution]

After some attempts to find a 2nd reason why it was not accessible. And I was unable to read or copy the error file (did not know how). I decided to reinstall the os. That did not change anything. So I cleared the whole system. And now I am putting the backup back.
Everything is now almost back as normal.
So problem solved but not the way I would like.
If my knowledge of telnet was as good as good old DOS I would investigate longer and would find and fix the problem. But telnet is way out of my comfort zone.
Thanks for your attempts to help me find the problem.