It seems that the recent firware 6.4.0 has caused several different issues so far but I am yet to see a solution that resolves my issues on the forum.
I upgraded to 6.4.0 at around 2pm yesterday and it appeared to work correctly, no boot issues.
My NAS is set to turn off at 1am and come back on at 9am, which it did according to the emails it sent me.
At 9:15am it should perform a FTP backup of a website which it started to do then stopped and emailed me - "Backup Status: Fail: connection cannot be established. Check the connection and authentication, if required."
I logged in to the admin interface and tried to re-run the backup job which it started to do then stopped a few minutes in and kicked me back out of the admin interface.
I was then unable to login to admin with the admin progress bar timing out.
My PC could see the NAS in File Explorer but couldnt access the folders or files due to a 'network error'
The Readycloud app can see the NAS but wont access anything.
I force powered down the NAS and then turned it back on again and it booted back up.
I could then access the NAS as normal through any interface I used but then after a few minutes it went back to the same error as before and refused me access.
When I do have access to the NAS it seems to be running slowly.
It wont power down gracefully and it refuses to reboot (but it will boot from a force shutdown), it just sits on the 'see you soon' screen
Raidar is showing the NAS as Healthy and raidar will browse the folders and files when using the IP but it wont open admin.
I have no idea what to do next. I am out of support with Netgear.
Does anyone have any bright ideas on what I can try. I have around 7TB of data that will take several days/weeks to rebuild.
2015-10-30 13:51:36: journalctl[12371]: segfault at 7f41532d8e70 ip 00007f415ab0cf71 sp 00007ffcf2010db0 error 4 in libsystemd-journal.so.0.0.3[7f415ab0a000+11000] 2015-10-30 13:51:36: journalctl[12376]: segfault at 7f928904de70 ip 00007f928f4d5f71 sp 00007ffee05820b0 error 4 in libsystemd-journal.so.0.0.3[7f928f4d3000+11000] 2015-09-24 01:00:25: ctscand[5631]: segfault at 7f66a2f3d870 ip 00007f66a18ce504 sp 00007f669f843988 error 6 in libc-2.19.so[7f66a1849000+19f000]
Overnight the NAS seemed to complete the reprocess of the snapshots and the NAS let me access it fully this morning. I have since removed all existing snapshots and stopped any new ones from being created.
Looking at the logs, the event that keeps repeating for the time period that the NAS was unusable is related to reprocessing of the snapshots so it looks like any other request to the NAS be it for data access, admin access or even for it to reboot was ignored due to the overloaded work that the firware update had started. Now that work is finished the NAS seems to be usable again.
The only advice I can give to others with the same issue is to try and remove any existing snapshots, stop new ones being created and leave the NAS on 24/7 until it becomes stable.
