NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
ReadyNAS Pioneer Pro BUG: Unable to handle kernel null pointer dereference at (null)
Hello, I have not been using my ReadyNAS Pioneer Pro because I have four other Netgear NASs and this NAS has been problematic in the past. Since the NV+ can not be upgraded to OS 6, I decided to re...
How much memory do you have in the NAS?
Also, do you have any apps installed?
Hello Stephen,
Thanks for quick reply! There are no apps installed on this NAS as I just use the NAS to RSYNC data from the other NASs. It was also just factory reset within the week so it only has on it what you get from that.
As for memory, I never added any memory. It came with 1 DIMM in the NAS. The DIMM is a 1GB DIMM. The memory tests pass that you do through the hardware via the boot menu.
FWIW, I had the same experience with my ProPioneer over the past year. It has os 6.10.4. From time to time, without any entry in the logs or warning, no apps and temperatures OK, it behaves as you describe. I replaced it with a used RN526x. The ProPioneer is now #2 backup to the RN526. (#1 backup is USB that goes offsite regularly).
Hello Labdoc1,
Thanks for the reply. It is good to know that I am not alone with this issue with this model of hardware! With this issue I would never trust it to store any data that I did not have elsewhere. If the issue can not be resolved, I will use the NAS for parts as I have three other working Netgear NASs and one retired Netgear NV+. The NAS does hold six drives and does load/run the latest OS. If the NVRAM can be replaced, I would be willing to do that if people thought that would help. I will leave this issue open for a bit to get any ideas that people think might help. The link above shows the testing that I had done before with this issue. Have a great day.
I'd try removing the bond, and I'd also disable ipv6 if that is enabled.
No idea if that will help, but neither are actually needed, and it's easy to try them.
I disabled IPv6.
I also disabled the ReadyDLNA service as I do not need that.
I left the bond configured for now as I do not want to make too many changes at one.
I rebooted and it rebooted fine. I then shut it down, waited a minute, powered it on, and it booted fine. It is after poweron from the poweroff state that the issue happens (minus the one time of it just dropping off the network after being left on all night - that had never happened before). I will do several poweron tests and if the NAS still has the issue, I will break the network bond. I could also test with just one network cable. However, I recall the issue happening even when no network cable was attached. I will report back after several poweron tests.
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
