Cant access any data or share.

[Stievo9997]

Hi All,

So some time ago i had the following problem: (in short: the readynas remote log & readydlna log filled the 2gb root volumel) and i was perfectly helped when the these where deleted or something by tech support with tech mode enabled on the nas.

https://community.netgear.com/t5/Using-your-ReadyNAS-in-Business/Can-t-access-any-data-anymore/m-p/1...

But know i have more or less the same problem, i can log in but the pages wont respond. The disk are known in the nas, but says 0mb left, and no size information about the disk. but on the front of the nas(display) it is correctly displayed.

So i think its the same issue again, who can help me, or can tell me how i can delete/clean them myself.

Thanks in advance.

[StephenB]

Even though your NAS is old, if you are the original owner you can use paid support for this (via my.netgear.com).

It is possible to clean it yourself if you know the linux command line.  Do you?

Also, do you have a backup of your data?

[Stievo9997]

I am the original owner. I would look at that option.

Yes i saw that is is possible, but i dont know the exact steps. i do have basis knowledge about linux / working with command line / putty.

If you show a guide of step by step information, i think i can complete it myself.

I dont have any backup, because i thought raid X would be sufficient.

[Stievo9997]

update:

I did a reboot and now when i try to login in to the nas by ip adress.

the browsers says, system error, please contact support.

[StephenB]

---

@Stievo9997 wrote:

update:

I did a reboot and now when i try to login in to the nas by ip adress.

the browsers says, system error, please contact support.

---

What does RAIDar say? https://kb.netgear.com/20684/ReadyNAS-Downloads#raidar

[Stievo9997]

raidar says, see attachment.

But on the front of the display is says al 4 disk with green led, and how many space is used/free correctly.

[StephenB]

That is a bit strange (no disks status on RAIDar, but normal disk status on the LCD panel).

It might be worth booting up again.

[Stievo9997]

After the reboot, the result are the same.

[StephenB]

I'm thinking this error might not be related to a full root, but of course you can check for that.

The first step is to boot the NAS into tech support mode.  See pages 23-24 here: http://www.downloads.netgear.com/files/GDC/RND2110/Duov1_NV+v1_HW_en_06Dec11.pdf

Then log into the NAS with telnet (not ssh).  The username is root, the password is infr8ntdebug.

Once in, you want to start RAID.

# start_raid.sh

Then mount the OS partition.  If you are using xraid, the command is

# mount /dev/hdc1 /sysroot

If you are running flexraid, the command is

# mount /dev/md0 /sysroot

Then chroot

# mount --bind /proc /sysroot/proc
# mount --bind /dev /sysroot/dev
# mount --bind /dev/pts /sysroot/dev/pts
# chroot /sysroot /bin/bash

Then use df to see if you are out of space or inodes

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

Post back with the results of the two df commands, and we can proceed from there.

[Stievo9997]

thnx for your help.

I did what you said, but the command:

mount --bind /dev/pts /sysroot/dev/pts

 is returning: no such file or directory.

i made a screenshot from the output / df, see attachment.

[StephenB]

Ok.  Let's not worry about the failed mount point.

Looking at the two df commands, you do have a full root partition, but you have plenty of inodes.

So the next step is to locate the large files.  Note that you are interested in really big files - hundreds of megabytes.  The basic procedure is to search for the largest folder, and look at what's inside it.  Generally it's in /var - and is either a runaway log file, or the ReadyDLNA cache.  Stuff in the cache you can just delete (and probably you should, even if that isn't the main problem). 

You can truncate runaway logs using

# echo > filename

One way to do the search process is to start with 

# cd //
# du -d1 -h

Then cd into the largest folder and repeat.  If the subfolder sizes are a lot smaller than the main folder, then the folder you are in has some big files.   So do 

# ls -lhS

[Stievo9997]

so i did this: (see attachment)

i found the cron.log which was 1.4 gb.

what steps do i need to take further?

[StephenB]

---

@Stievo9997 wrote:

what steps do i need to take further?

---

Now your root partition should be about 30% full.  You can confirm that with 

# df // -h

The next step is to restart the NAS

# shutdown -r now

Then see if you have access to the shares and the web ui.  Post back on that.

[Stievo9997]

Awesome!

After reboot, everything works back normal.

Many thanks for your support! 

[StephenB]

---

@Stievo9997 wrote:

After reboot, everything works back normal.

Great.  If you don't have ssh enabled, you might want to install the add-on for that.  That might let you avoid tech support mode the next time you need to get into the NAS.

You download the add-on from http://www.downloads.netgear.com/files/ReadyNAS/ADDON/4.2(X86)/EnableRootSSH_1.0.bin

Then you can reach the NAS with putty (or ssh).  The username is root, the password is the same as your NAS admin password.

---

@Stievo9997 wrote:

I dont have any backup, because i thought raid X would be sufficient.

---

It's not sufficient (as many people here have learned the hard way).  So you should put a backup plan in place for your NAS.  The least expensive approach is to get a USB drive or two.  You can connect drives directly to the NAS, but the backup speed is extremely slow.  It's faster to connect the USB drive to a PC, and backup the NAS over a ethernet.  If you want more information on how to set that up, just open a new topic on it.

[Stievo9997]

Thanks again, i will look into that.

I'm gonna make a back up now, thanks again for your detailed help and effort.