NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Yoda1492
Jan 24, 2021Luminary
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...
StephenB
Jan 24, 2021Guru - Experienced User
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.
Yoda1492
Jan 24, 2021Luminary
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.
- SandsharkJan 25, 2021Sensei
The NAS will say "ReadyNAS" if there is nothing present except +5V, so a lot can be wrong. Your best bet is to acquire a VGA cable to connect to the VGA header in the unit and see if you see anything going on during boot that could explain it.
If you just want to take some stabs at it, the first thing is to get more RAM. Others have reported problems with 6.10.x on legacy systems with only 1GB of RAM. Since all Intel based native OS6 NAS come with at least 2GB, Netgear is not going to be checking that it'll work in 1GB. Since bad RAM could also be it and DDR2 RAM is so cheap these days, replacing the existing DIMM at the same time might also help.
Another real possibility is a failing power supply. If you have a spare ATX supply, you can install that externally and see if it fixes the issue. Since it takes a while to see if it's really fixed, you'll want to use masking tape to fill the gap where the cable comes out and cover the power supply fan opening so the chassis fan draws air over the drives. You may need a SATA to 4-pin Molex power adapter or 4-pin Molex splitter to make it work.
- Yoda1492Jan 26, 2021Luminary
Hello Sandshark,
Thanks for all the input! I do have the VGA cable and previously used that with a monitor to watch the NAS poweron and boot sequence. A lot of that information and screenshots are in the link above. Back in 2016 when I was originally troubleshooting this same issue, I used a camcorder and recorded video of the NAS booting so that I could get screenshots of anything of value. I still have those videos and do not mind creating new videos if needed.
It does seem like a very low level (motherboard, RAM, NVRAM, CPU, power supply, battery) kind of issue since it happens right when you power on the system. The OS it not even booted at that point.
To do some more testing, I setup several large backups and let that run overnight. This time the NAS was working fine the next day and the backups completed like normal.
I only did a few poweroff / poweron tests which all passed, but this was not enough poweron tests for any kind of conclusions.
I have some spare RAM from various PCs. I also have a graveyard of spare power supplys from replacing all the PC factory power supplies with 650Watt or 700Watt modular power supplies. I am using a new replacement power supply that is the exact same model as the original power supply; so if the original power supply is not enough power, then the same is true for the replacement power supply. I still have the original power supply since replacing the power supply did not fix the issue. I do have 4-pin MOLEX splitters and SATA to MOLEX adapters.
I will start with looking into adding RAM first. If that does not resolve it, I will try replacing the RAM. Let me gather up the RAM that I have to see if any of that RAM is compatible with this NAS. Although the current DIMM passes all memory tests, I can certainly see how having more RAM can help. I will provide an update soonest. Thanks for the ideas and input.
Related Content
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!