NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
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...
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.
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
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
Thanks StephenB.
I'll give it a go over the weekend and report back!
No, not that. Something like:
# mount --bind /proc /sysroot/proc # mount --bind /dev /sysroot/dev # mount --bind /dev/pts /sysroot/dev/pts # chroot /sysroot /bin/bash # vgscan # vgchange -a y # mount /dev/c/c /c
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
