NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.

Forum Discussion

Chandler1's avatar
Chandler1
Aspirant
Dec 20, 2017

RND2000 Duo v1 - lockup after boot - OS partition full?

(NB: reposting since it appears my original post never got published for some reason...? https://community.netgear.com/t5/Using-your-ReadyNAS/RND2000-Duo-v1-lockup-after-boot-OS-partition-full/td-p/1447681)

 

Hello again forum!

 

TL;DR - think my OS partition is full. go to *** END STORY *** if you don't want to read my treatise Smiley Happy

 

*** START STORY ***

 

So my ReadyNAS has decided to stop working for me. Not sure when exactly it stopped working - we weren't home for the last week - but upon returning I found a NAS that I couldn't access (Network Shares, FrontView, RAIDar, ping, etc).

 

After troubleshooting networking issues, I attempted to power down the device via the power button to no avail. Left with no other option, I pulled the power (not much different to losing power, so...). Upon reconnection and powering up, I was overjoyed to see an email from my nas advising of the improper shutdown and a commencing RAID sync. Huzzah!

 

I then however find that whilst I was talking to it (and it me), it stopped responding (and access via the aforementioned methods ceases to work).

 

*** END STORY ***

 

NAS Details (sketchy as I haven't looked recently and I don't want to power it up just to get latest info)

Hardware: NETGEAR ReadyNAS Duo v1

Drives: 2 x 2TB WD RED WD20EFRX, RAID 1

Radiator Version: 4.1.15 (I think... it's been emailing me all the time to update to 4.1.16)

 

PC Details

Windows 10 Laptop, typically accessing via wirless (can jack in if required)

 

 

After a bit of Googling, I find a few posts that give me the impression that it is a full OS partition.

 

With this knowledge in hand, I'm now looking at fixing the issue but would like to have all the information at hand before I commence and potentiall brick my NAS. I do know my way around PCs, although am not familiar with *nix commands (have played with it a tiny bit many years a go on Red Hat GNOME & KDE, and I do have an Ubunto Live CD here somewhere...).

 

Sources:

 

Proposed process:

  • Remove Disk 2 (for data safety)
  • Boot NAS to Tech Support Mode (power button 20 seconds?)
  • SSH (Putty) to NAS - un: root / pw: infr8ntdebug
  • Mount partition:

 

# /bin/start_raid.sh
# mount /dev/hdc1 /sysroot

 

  • Confirm full partition:

 

# /sysroot/bin/df -h
# /sysroot/bin/df -i
# /sysroot/usr/bin/du -csh /sysroot/var/*
# /sysroot/usr/bin/du -csh /sysroot/var/log/*
  • Copy massive log/s to data parition as appropriate

 

# cp /sysroot/var/log/frontview/error.log   /???/backup_frontview_error.log
(change /frontview/error.log as appropriate, not sure on destination file/location?)

 

  • Empty log/s as required:

 

# echo > /sysroot/var/log/frontview/error.log
(change /frontview/error.log as appropriate)

 

  • Come back here when it doesn't work

16 Replies

Replies have been turned off for this discussion
  • mdgm-ntgr's avatar
    mdgm-ntgr
    NETGEAR Employee Retired

    There are multiple possibilities and a full root volume is one of them and perhaps the most likely.

     

    If the NAS is in the middle of a resync then only one of the disks would be usable for getting at the data anyway.

     

    It's situations like the one you've run into here that show some reasons why it's important to backup your data.

    • Chandler1's avatar
      Chandler1
      Aspirant

      Thanks mdgm.

       

      So my plan is good? (presuming it is a full root...)

       

      Can you advise on copying the large logs to the data partition? (I'm not a Linux user, although I'm working on it!)

       

      # cp /sysroot/var/log/frontview/error.log   /???/backup_frontview_error.log

       

      • StephenB's avatar
        StephenB
        Guru - Experienced User

        First check that the OS partition is full

        # cd //

        # df . -h

        # df . -i

         

        The first df will tell you the space usage on the OS partition.  Normally it would be no more than 25%

         

        The second df will tell you the inode usage on the OS partition.  Inodes are used for metadata, and if you run out you won't be able to create new files on the OS partition even if there is free space.

         

        Assuming you are running out of space: 

        You'd put the oversize logs on the C volume.  The best thing to do is park them in a share.

         

        So first create a subfolder in a share

        #mkdir /c/sharename/log_files

        Then 

        # cp /var/log/frontview/error.log /c/sharename/log_files/backup_frontview_error.log

         

         

         

NETGEAR Academy

Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology! 

Join Us!

ProSupport for Business

Comprehensive support plans for maximum network uptime and business peace of mind.

 

Learn More