RN10400 NAS won't boot HELP

Question

I have a office Ready NAS that won't boot or show a managment menu. Files are not accessable, data recovery is imporant. Front panel says booting then goes black and no data when I touch the power button.

I have run dagnostics using raidar from NETGEAR. All drives show up with green checks, Firmware is 6.9.4. I can not SSH in to device as I don't think that was ever enabled. Users say drives where not out of space but I don't know what to base that one on.

It seems to me that part of the volume is full as error logs are full of failed to create. I was unable to download logs just what shows up in the dag window. Is there an easy fix or is the best method for data recovery and replace the unit I guess?

HELP!

Dagnostics output

Volume root is 100.00% full

2019-10-20 06:02:12: ufsd: "mount" (sdd2): is mounted as NTFS at 2019-10-20 13:02:12
2019-10-13 06:02:10: ufsd: "mount" (sdd2): is mounted as NTFS at 2019-10-13 13:02:10
2019-10-10 06:02:01: ufsd: "mount" (sdd2): is mounted as NTFS at 2019-10-10 13:02:01
2019-10-06 06:02:11: ufsd: "mount" (sdd2): is mounted as NTFS at 2019-10-06 13:02:11
2019-10-04 06:02:13: ufsd: "mount" (sdd2): is mounted as NTFS at 2019-10-04 13:02:13
2019-09-30 06:02:11: ufsd: "mount" (sdd2): is mounted as NTFS at 2019-09-30 13:02:11

09 22:04:35: DB (main) schema version: 24 ==> 24
2020-05-09 22:04:35: rndb_create() ==> 3 (448ms)
2020-05-09 22:04:35: Error create table (db)
2020-05-09 22:04:35: dba create failed
2020-05-09 22:04:33: Failed to start ReadyNAS System Daemon.
2020-05-09 21:54:49: dba create failed
2020-05-09 21:54:48: Error create table (db)
2020-05-09 21:54:44: rndb_create() ==> 3 (1526ms)
2020-05-09 21:54:43: DB (main) schema version: 24 ==> 24
2020-05-09 21:54:33: Failed to start ReadyNAS System Daemon.
2020-05-09 21:44:33: DB (main) schema version: 24 ==> 24
2020-05-09 21:44:33: rndb_create() ==> 3 (480ms)
2020-05-09 21:44:33: Error create table (db)

Thanks in advance

Marc_V · Answer

JFRedwards

&nbsp;

Welcome to the Community!

&nbsp;

The Volume root is full as per the logs, the OS Volume and/or Data volume got full and that is one reason why your NAS is not booting up properly. Have you tried booting the NAS on Read only?

&nbsp;

if you are comfortable using SSH, you can boot the NAS on Tech Support mode and follow good instructions from posts answered by StephenB and others. Otherwise, another option would be to contact Support.

&nbsp;

HTH

&nbsp;

Regards

StephenB · Answer

JFRedwards:
&nbsp;
ReadyNAS systems put a small OS partition on the disks (4 GB).&nbsp; The system boots from the partition, and that is where linux and the ReadyNAS application are installed.&nbsp; That partition is what we mean by "volume root".&nbsp; It's not at all the same as the data volume.
&nbsp;
As&nbsp;Marc_V&nbsp;suggests, you can contact Netgear paid support (via my.netgear.com ) and have them fix this.&nbsp; You could also look yourself, but there may be damage to the NAS configuration files which would be hard to troubleshoot - Netgear can repair those.&nbsp; If you want to use paid support, it is best not to attempt repairs yourself.
&nbsp;
Either way, you would need to be in the office to boot up the NAS in tech support mode.&nbsp; Netgear can then access the NAS remotely (using a code that is displayed on the LCD).&nbsp; You could alternatively access the linux CLI using telnet.&nbsp; We can give you some guidance on how to do that if you like.
&nbsp;
Instructions for booting into tech support mode are on pages 28-29 here:&nbsp;http://www.downloads.netgear.com/files/GDC/READYNAS-100/ReadyNAS_%20OS6_Desktop_HM_EN.pdf

JFRedwards · Answer

&nbsp;&nbsp;Thanks for everyones help,&nbsp;At this point I think using paid support is best, Hopefully there is a decent way to get it booted and working. If it was my device I would just do it myself, but with my guess being other configuration issues to arise I am sure it will be a pain.&nbsp;I need to backup the data right away after getting it working.

JFRedwards · Answer

Hi&nbsp;StephenB&nbsp;Marc_V&nbsp;&nbsp;After attempting to get paid customer support and having multiple issues with whatever gateway processor netgear uses I phoned technical support and waited for about 2 and a half hours, talking to someone then booking a call back with a specialists.&nbsp;&nbsp;Call back never came and the support ticket was gone from my support page.&nbsp;So 24 hours later I decided to make this work on my own, my plan was to make 2 attempts to get this working and then remove the drives and hopefully use&nbsp;reclaime to get the data. I wanted to post my experence as it was difficult getting all the information in one post as it took me a fair bit of time to get everything sorted.&nbsp;I booted the device in tech support mode "Instructions for booting into tech support mode are on pages 28-29 here:&nbsp;http://www.downloads.netgear.com/files/GDC/READYNAS-100/ReadyNAS_%20OS6_Desktop_HM_EN.pdf&nbsp;I used putty to telnet in to the device and used root and&nbsp;infr8ntdebug as the password and started the chroot# rnutil chroot&nbsp;Using df command I could see that the drive was at 100%.&nbsp;# df&nbsp;I attempted to rm any temp files from clamav as was suggested in posts and the disk was still 100%# cd /var/lib/clamav# rm -r clamav-*.tmpAfter that i attemped to go hunting&nbsp;# cd /var/logs# ls -l&nbsp; I deleted the large files I could find.&nbsp;# rm -r user.log.old# rm -r user.log# rm -r syslog# rm -r auth.log.old# rm -r daemon.log# rm -r daemon.log.old&nbsp;I now have 88% used and have been able to boot the NAS and access the web interface.&nbsp;&nbsp;Why would the system not clear old log files and am I going to have more problems in the future with this device? I expect a production model to not get filled up with log files over the years. Am I missing something? Can Someone educate me on why this happend?&nbsp; I would think a production model would have a cronjob to rotate logs?&nbsp;What else could I clean up in the root partition?&nbsp;&nbsp;My plan is now to do a backup to another drive and put it back in service. Maybe do an update after I do that.&nbsp; What Other Maintance should I do before putting it back in service?&nbsp;Thanks in advance!!&nbsp;&nbsp;

Sandshark · Answer

88% is still way too full.&nbsp; Do you run Plex?&nbsp; It is notorious for leaving behind transcode fragments.&nbsp; Another thing that has happened to some is an error on a backup job to a USB drive where the drive is not properly mounted, so the mount point directory in the OS partition is treated as a real directory and the destination for the backup job.

Forum Discussion

RN10400 NAS won't boot HELP

9 Replies

Related Content

Readynas rn10400 btrfs error

ReadyNAS RN10400 Stuck at Boot Menu

After update firmware 6.4.0, RN10400 doesnt boot

Rn10400 data recovery

Power issues RN10400

NETGEAR Academy

ProSupport for Business