NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Solved
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...
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.
Hello rantech,
It appears that the error message refers to critical kernel error the issue described requires assistance from the engineers and/or higher tier who can remote in to the NAS and fix this from the backend.
Unfortunately, It shows on your records that the support warranty of your product is already expired. You may try contacting support center and avail a support contract. That should allow you to extend the support for your product so they can escalate your issue to L3 or patiently wait for anyone in the community who has the knowledge in the SSH commands and fixing some issues from the backend.
Regards,
Marty_M
NETGEAR Community Team
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.
Hello rantech,
I do understand the frustrations, unfortunately the support warranty of the device is already out.
Regards,
Marty_M
NETGEAR Community TeamI'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.
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
