ReadyNas 6.2 (NAS locks up entirely)

jaffacake wrote:
The 102 doesn't support RAID5, though, right? No parity in a mirror, so very different set-up despite same OS.

And I am running jbod, so there is no mirror at all.

That could be a clue (since I am still not seeing any signs of a memory leak). But there could be some other service that is responsible for the leak that I'm not running.

Antivirus is off, SNMP is off, and AFP is off. All other standard services are enabled.
ReadyCloud and ReadyRemote are on, Replicate is off.
Snapshots are daily, bitrot is turned on (but with no RAID that only enables CoW).
Apps are Plex and SMB Plus.

Lots of daily backup jobs, all are rsync.

Disk Spindown is enabled.

(EDIT- no iscsi LUNS are created, no use of timemachine)

Does not seem to be a memory leak. After disabling anti-virus and DLNA I still had a crash early this morning, but no swap space was in use.

Hi All,

I'm having the same issue. Everything was running stable with 6.1.9... I could run for months without having to perform any sort of maintenance.

Since upgrading to 6.2, 6.2.1, and 6.2.2, I've been experiencing lockouts at seemingly random times. Always during periods when the system is not in use. I first suspected a disk spin-down issue, but the problem has continued even after disabling spin-down.

My drive is only about 1/3 full.

I'm thinking about (but am reluctant to) trying to reset to factory defaults, wipe the drives, and replace all my data. But since reading that this has not helped other users with this problem, I'm even more reluctant to try this.

When the drive locks up, I cannot access my data via SAMBA, or via the admin web page on a local network connection. However... the drive still seems to be operating... according to the logs, events (e.g. backups to a local USB drive) still seem to happen. Perhaps this is a networking issue?

I'll send in my logs. I hope they help to identify the possible issue. Having to power cycle is both frustrating and worrisome regarding data loss.

Thanks,

Yesterday I set /proc/sys/kernel/panic and /proc/sys/kernel/panic_on_oops to restart my RN104 automatically if a kernel issue occures. Today I checked the logs and the system did reboot, which points out that this is most likely a kernel issue.
Today I'll just set the /proc/sys/kernel/panic to see if it's a kernel panic or a oops. How can I access the serial console (/dev/ttyS0) to attache a remote system to monitor the kernel issue (connector + pin description)?

Interesting.. Mine hang too after doing BTRFS Defrag with 20GB of Storage Sync data. Anyway, it's a dev/test box, so indeed netgear team need to take a look their code closely and full regression testing of OS. I can't even power off the system with front power button.

I've been reading about the OS6.2.2 freezing on (many)other topics. I had the same problem, the 90 days of support period was over so I had to pay more for a supportaccount then is had costed me to buy a new RN102, this is really ridiculus, when you buy a product, you can expact support for the same time of the warranty!

My problem was the interface, I could acces the data in windows but my apps were shut down, one of the apps was Plex, the most important app because 95% of all my data is video.

I have tried to fix this problem in my own way (not very smart). I was using a JBOD X-Raid situation, first disk 3tb seagate NAS HDD, and second an older 1tb disk from a media-center. I figured that all of my data (1,6tb) was stationed of the first drive. After many OS-reinstalls, even with USB I decided to remove the largest disk, move the second to the first slot and do a factory reset, after that I would reinsert the large 3tb drive and use everything. One problem, this drive will not be recognized so I first have to format the drive.

My question is:
1. How can I acces my data?
or 2. How can I get my drive back in to the nas so that it read it again?

I have Windows 7 and Ubuntu 14.0.4
I also have a storage device to read an external disk so I can hook it up to my laptop

Is there anyone who can help me (and read this dutch way of english)?

The support warranty of 90 days provides plenty of time for basic assistance with questions you have setting up the product and early use of it.

1. So you haven't done a backup your data?
2. This is something you should work through with support. Trying to fix this yourself you will likely only make the problem worse.

Dear mgdm,

You are completely wright. I am a fool for not having any backup. I know now that acting like this without help was foolish. My system was up and running for about a year without any trouble, until os 6.2.2, that is when everything went wrong. I was wondering, is it possible to restore the raid system with a program, as if the smaller second disk failed? Creating the same raid configuration as before.

When I start refilling my nas, I will of course make regular backups. I don't want to experience this again. But wright now I just want to get to the data, and if anyone could help, I would be very grateful. I have tried to access the disk thru ubuntu (because of the Linux idea) by still I only see the drive but not the data.

2nafish2
Firstly, if you really want the highest probability of getting your data back then just contact support, pay them and get it sorted out.

To clarify:

Your original setup was jbod with 1 volume on each disk, so you had one 3 tb volume and one 1 tb volume. If this was the case then you were not using Xraid, but flexraid. Is this correct?

During your attempts at OS reinstall you did a USB boot? Correct ?

You say you factory defaulted the nas with the 1 tb drive, correct? Did the unit work normally after this and did the GUI come up?
Then you put the 3 tb drive into slot 2, or did you replace the 1 tb disk in slot 1? Was the nas on when you did this?
You then presumably removed the 3 tb drive from the nas, correct?

vandermerwe,

i had a setup of one 3tb seagate disk (with no failures what so ever) and a 1tb disk added up to the volume of total 3,52tb. In my opinion that makes all of the data (1,6tb) on the first disk (coming from someone with no experience at all) So I used the second 1tb disk to factory reset my RN102.

When I tried to reinstall the OS I first tried the boot menu, three times without luck, then after contact with support I got a link with selfhelp pages including USB boot, so I tried that as well, also without luck.

After the factory reset with the 1tb disk everything is working just fine, i just have to create my folders again and start over. When I insert the second 3tb disk (RN102 powered off, Ilearned that the Nas can format the disk if you insert a disk when powered on) and then reboot, the 3tb disk shows red in the interface. When I powerup the Nas with only the 3tb disk, Raidar shows the Nas with IP and when I press setup I get the first problems all over again ERR_CONNICTION_REFUSED.
I powered down the Nas, took out the 3tb disk, inserted the 1tb disk, booted the Nas and everything is working again, I can acces the interface the the IP-adress and all of that.

When I connect the 3tb disk to my laptop via USB (sweex harddisk dock) SeaTools can detect the disk, I did a short generic test, it passed and with file recovery (cancelled after one hour) it came up with a list of files from the /root directory. Scanning the complety disk takes about 185 years so that is not an option.

I can see the disk in windows and Ubuntu but accessing it is something different.