ReadyNAS ultra6 shares not reachable / frontview does not persist changes
I am facing the same issue as several others here in the forum where the NAS has become unreachable and frontview does not persist changes anymore.
I am guessing OS partition full.
In the past, NETGEAR would provide support for this and remotely log on the machine and do some fixes over telnet (enabled thru boot menu). As the device is end of life I can't get support from them anymore (tried this).
I was able to log onto the machine with telnet. However, I notice there is no full blown linux on there. So I feel rather limited in recursively trying to find large files etc.
Is there anyone who can give me some information on what folders to check and what to delete to make space. Or which statements to run on the machine?
It would be very very helpful and I already thank you sincerely.
PS: Rather bummed that NETGEAR is not providing a decent document on this.
I was able to log onto the machine with telnet. However, I notice there is no full blown linux on there. So I feel rather limited in recursively trying to find large files etc.
Try entering
# start_raid.sh
# mount /dev/md0 /sysroot
# mount --bind /proc /sysroot/proc
# mount --bind /dev/pts /sysroot/dev/pts
# mount --bind /sys /sysroot/sys
# chroot /systoor /bin/bash
That will actually mount the OS partition and chroot - giving you the full range of linux commands in the OS partition, and also letting you examine the OS partition.
Then you check fullness with df // -h and df // -i.
PS: Rather bummed that NETGEAR is not providing a decent document on this.
I used to work for NETGEAR and have looked at a number of problems with these symptoms in the past. The issue is that every problem is different. I could write something easily that would work as more or less a best practice for a few common cases, but that wouldn't be very applicable in others. Doing the wrong thing can sometimes make a problem worse. Writing a good document that covers off pretty much everything would be a major undertaking.
A lot of threads here ignore some basic things that should be done like checking the health of the disks and the state of the RAID before starting the RAID. There's also syncing writes, unmounting the root volume and stopping the RAID properly when you're done as well.
will truncate the file to 0 size. Logfilename can include the full path, or you can use cd to enter the appropriate folder (cd /var/log for example).
You can truncate a couple of these (to get the OS partition below 50% or so), which will let you reboot. You can then clear the logs from frontview to shrink the rest.
Re: ReadyNAS ultra6 shares not reachable / frontview does not persist changes
Plex is notorious for leaving behind scraps from transcoding that can be huge. A couple users have reported issues that seem to stem from an improperly mounted USB drive, so what should have just been a symbolic link to the drive, which is in the OS partition, was an actual directory and contained files intended for the USB drive. Other apps, especially anything you added via apt-get directly, could also be creating the problem.
But you have to be carefulo that you are really looking at a directory in the OS partition, not to something elsewhere via a symbolic link.
Re: ReadyNAS ultra6 shares not reachable / frontview does not persist changes
Thanks everyone for helping out.
I found the culprit. After some investigation and ls -ltRS, I noticed I had a cache folder under /var/ from the minidlna app plugin which I tried somewhere in the past. This cache folder had been collecting media information in a .db file which was insanely huge. After removing this file, df -h went from 100 to 26% and the device booted again as before.
Reimporting an old config wasnt succesful, but I just quickly reconfigured the file sharing services to access the NAS again. I am now in the process of copying files over to another drive... phew.
Thanks a ton to everyone in this thread here and the pms I got!
I will have a look into it once I have a backup of my files. It looks very interesting thanks!
Another thing you could do is convert your Ultra to run OS-6. That doesn't have that particular problem, and also would give you SMB3 (among other things). If you want to do that (or just want more information) let us know.
The process does require a full reset/reformatting of the disks - so you would need to reconfigure the NAS and restore files from the backup.
Yeah that sounds very interesting... is there some kind of easy walkthru for it?
(Optionally) make sure the latest BIOS is installed before you do the conversion. To do this you install http://www.readynas.com/download/addons/x86/4.2/BIOS_Update_Package_0.5-x86.bin as an add-on and reboot the NAS. Do this after you backup the NAS. This isn't necessary, but if you so want to update the bios it is easiest to do it prior to conversion
Basic instructions for the conversion itself are
BACKUP, BACKUP, BACKUP
Upload PREPR4TOR6_0.1-x86.bin as an add-on using the ReadyNAS web gui, but do not reboot afterwards (avoids the need to do manual factory resets)
Upload R4toR6_6.9.5.bin using the ReadyNAS web gui firmware update
After you upload the addon+firmware and reboot, it will update the firmware and start a factory default.
Go through the setup process on the converted NAS
Restore files from the backup.
Note that there is a significant bug in 6.10.5, so I don't recommend upgrading your software to that until it is fixed. 6.10.3 would be a good upgrade though.
Netgear won't provide paid support on a converted NAS, so that is one consideration. There is a small risk that the process could fail, and if that were to happen it might not be possible to get the NAS running again.
If you do decide to convert the Ultra, then you should also consider increasing the RAM. Shipping OS-6 NAS have at least 2 GB of RAM, your Ultra only has 1 GB. Some folks have run into out-of-memory conditions with only 1 GB. The upgrade is inexpensive, and is simple to do.
