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 to a 316 box and it started queuing up the backups rather than running them. I was away from home so I used VPN to access frontview and it locked up at the first screen shot page which shows the 6.7.5 Firmware version. Couldn't get in. When I returned home and checked the system, could not bring up frontview and could not access mapped shares. The front panel display showed the error message "Walk_Up_Proc+359".
I restarted the 524 and it appeared to come back up okay and everything appeared to work except that I could not start any backup jobs - all backup jobs appeared to go into queue even though none were running; didn't matter if I used rsync or if I tried to run a backup to an attached USB drive. However, I could access all shares as mapped drives no problem. Unfortunately, after being on for a few hours (and after copying off one of my very critical shares to make sure I had another extra copy of it using windows drag and drop), when I went back into the web interface and viewed the shares, it reported all shares (except the share I just copied) as being 0 TB size. I tried to access the snapshots but even though it showed all the snapshots in the list, none appeared to have any content.
I then restarted the 524 one more time and again it appears to come back up okay and all the shares are again showing the correct sizes, I can browse the snapshots, and I can access all data via mapped shares but I still can't run any backup jobs. All backup jobs just go into the queue so the underlying issue is still there.
I'm assuming I have a hardware failure somewhere but am wondering if anyone has come across this error message before (I'd be panicking but I have a full backup of everything on my 316 so I need to get this sorted but it isn't an emergency).
I should also mention that I run two sets of full backups; one to an old ReadyNAS Pro and one to a ReadyNAS 316. The pro runs first. However, earlier on the day this developed, I started receiving email alerts about a large number of disc errors on Disc 4 on the Pro so I logged into it and shut it down (I was away and didn't want the situation to get any worse before I could deal with it). However, when the 524 tried to run backup jobs to the Pro, they all failed as it was now turned off. Shortly thereafter it started trying to run the backup jobs to the 316 and generated the messages about the backup jobs being in the queue. I see three possible scenarios:
1) Total coincidence that the 524 developed problems at the same time the Pro was shutdown and the backups failed
2) There is an underlying problem with the 524 that just happened to be triggered by the backup job failures (a memory problem?)
3) The backup job failures initiated and are the root cause of the problem with the 524 (which seems totally implausible to me but what do I know)
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.
11 Replies
Replies have been turned off for this discussion
Hello rantech,
The concern with the 524 is separate from the Pro since they are different hardware unit. If you could download and provide copy of the complete logs of 524 so we can check what might be causing this behavior. You may use file sharing website like wikisend to provide us a copy of the logs and just PM the download link.
Regards,
Marty_M
NETGEAR Community Team
I'm not at all worried about the Pro ... just that the backup jobs themselves run on the 524 and thought maybe the failure of the backup jobs to execute on the 524 cascaded to revealing a hardware problem on the 524... The pro is completely resynced and redundant again.
Created a support case this morning online ... I think this may be related to a support case I initiated in June where the system was showing DR share sizes as 0. At the time, support concluded it was a firmware issue to be resolved in a future update but now I'm thinking it was early symptoms of a now worsening hardware problem since I now have almost all shares (DR and regular) showing as 0 size..
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 TeamPurchased 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 Team
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
