NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
rantech
Jul 29, 2017Aspirant
Readynas 524 Crashing "Walk_Up_Proc+359" Error Message
Readynas 524 (OS 6.7.5) crashing with serious problems (including reporting shares as 0 space consumed). First symptom was email alerts that backup jobs were already in queue - I run backups daily t...
- Aug 04, 2017
L3 support found kernel error and multiple errors indicating a corrupt file system but have not been able to advise the root cause - no explanation for why things went haywire. Ran a memory test and no indications of a memory problem. Since I have redundant backups, they advised I restore the box to "factory default" from the boot menu which apparently restores the kernel and wipes the file system.
FYI: Wish I'd known that a factory default restore would fix the kernel and get the box working again before I paid for a support contract.
Anyway, not knowing why the box cratered, I can only hope it doesn't happen again. This is the second Readynas to crater on me in 2 months and it is starting to become frustrating. My NVX failed in June reporting two simultaneous dead disks but in that case it was an old chassis and relatively old disks.
rantech
Aug 01, 2017Aspirant
Purchased a support contract and it has progressed up to L3 support today. Waiting for L3 to investigate and respond.
I've owned 5 Readynas units (NV+, NVX, Pro, 524 and a 316) and set up at least 7 or 8 for friends and associates and I guess I'm really not thrilled about having to purchase a fairly expensive support contract just to get a 4 month old box working again. I've never used SSH and have never done anything with the box other than thru the normal user interface so I can't really see how I could have caused a critical kernel error - the only scenario that I can envision is for the kernel to have corrupted due to a hardware problem (e.g., memory) and the hardware is supposed to be under warranty?
I really think that on something like a kernel error, tech support should investigate to the point of determining whether or not it is a hardware problem or something done by the user and then require a support contract only if it can be determined the problem was caused by the user and not hardware.
I'll have to decide whether I purchase anymore Readynas boxes for myself in the future but I definitely won't be setting up anymore for friends and associates. Should any of those folks have this type of issue, I'd never hear the end of it.
Marty_M
Aug 01, 2017NETGEAR Employee Retired
Hello rantech,
I do understand the frustrations, unfortunately the support warranty of the device is already out.
Regards,
Marty_M
NETGEAR Community Team
- StephenBAug 01, 2017Guru - Experienced User
I'm thinking someone from Netgear should review the logs. Perhaps capture them, and hopefully a mod will ask to review them.
On the main issue - have you looked at disk health? One of the bad things in OS6 is that the disk alerts now have a pretty high threshold. So when you get the logs, perhaps look in disk_info.log and see if there are pending sectors, reallocated sectors, unrecoverable errors, etc.
Also it might be useful to know what apps and services you have running.
- rantechAug 01, 2017Aspirant
Logs are with support now. I have checked the disks and they are all clean (zero errors reported on any disk). There are no Apps running on the box. The only services running are: SMB, RSYNC, HTTP, HTTPS, and Antivirus
At one time I had some DR backup jobs running on this box which wrote to DR shares on this box. The backup jobs were stopped awhile ago but the DR shares are still there. The only other unique things that happened about the time the box cratered were: there were (4) backup jobs from this box pushing to a Readynas Pro using RSYNC and they all failed as the Pro was offline at the time (1 hr later the RSYNC backups to my 316 reported going into the queue rather than executing which was the first sign of problems). The only other thing that happened was I had VPN'd into mynetwork remotely and accessed the web interface via Chrome on an IOS device in order to shut down the RSYNC Backups to the Pro to prevent anymore failures. It was at the time I tried to bring up the web interface during this VPN session that I first noticed the interface was locked up and would not load past the splash screen.
- Marty_MAug 02, 2017NETGEAR Employee Retired
Hello rantech,
It does appear that our level 3 support is already handling and further debugging the case. Hopefully it can be resolved soon, please keep us posted.
Regards,
Marty_M
NETGEAR Community Team
Related Content
NETGEAR Academy

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