NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Solved
ReadyNAS Pro 6 on readyos v6.10.6 no frontview on boot
First of all let me right of the bat start by acknowledge that I'm aware I'm running "unsupported" software on legacy hardware. My setup has been working good for years and years since I due to secu...
Not a lot of clues here. You might want to search through all the log files and see if there is more information on what is killing apache. It might be one of the add-ons/apps (including ones you uninstalled that might not have uninstalled correctly).
The brute-force "fix" is to back up the files, do a factory default, rebuild the NAS, and then restore the data.
Yes, I’ve tried the boot menu OS reinstall but that didn’t help which is so wired!
Not a lot of clues here. You might want to search through all the log files and see if there is more information on what is killing apache. It might be one of the add-ons/apps (including ones you uninstalled that might not have uninstalled correctly).
The brute-force "fix" is to back up the files, do a factory default, rebuild the NAS, and then restore the data.
Haha! Yes, the brute force method... :smileyvery-happy: well to be perfectly honest I've already ordered (and received) a new set of disks to do just that!
I have the disks but now that I'm about to start the process of cloning almost 40 Tb (got 6 x 14 Tb array of disks) from my "frontline NAS" (I have two Pro-6 units) to the one on the inner more protected network I realized that it's going to be days of clogging up the network.. :smileylol:
My question here was more like a "hail Mary" kind of "finding an easier way out" :smileytongue: :smileylol:
J_Malmlund wrote:
My question here was more like a "hail Mary" kind of "finding an easier way out" :smileytongue: :smileylol:
The puzzle is that while we can see that apache failed, we aren't seeing anything that points to the cause. There might be something buried in the log zip that might help (looking around the boot-up time in kernel.log, system.log, dmesg.log, etc).
My guess is a corrupt configuration file, which an OS re-install does not over-write. They are downloaded when you save the configuration, so maybe you could look through there, too. But even if you identify the corrupted file, you need to re-create a new one, unless you have a configuration backup from before this happened that you can restore.
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
