NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Unable to access config menus on NV+
I have an old NV+ that has lain unused for a couple of years - I've powered it up and all seems well, I can access some old files in my share. When I open the webpage in Chrome (or IE) I get the IN...
As before, I get a kernel panic - on close inspection, when I try to boot from USB to reload, I see the word 'recovering' flash up very briefly before 'kernel panic' appears.
Essentially, I get the same message sequence with difference revisions, except on one occasion with v3 when it hung at 'awaiting RAIDar'... but not repeated.
So, to sum up, if I try to reload from USB, I get 'usb init' then 'recovering' for a moment followed by 'kernel panic'
Rebooting after that gives 'Welcome to the ReadyNAS world' for some seconds, then 'booting' followed by 'ERR: Bad firmware' I get these results with just a single drive (several known good ones) in bay #1 or a full set of 500GB ones, both Western Dig and Seagate.
A long press on reset while power on starts the firmware reload, but ends in Bad firmware.
Interestingly, if I try and reload from USB with no drives fitted at all, I still get 'recovering' for a moment then 'kernel panic' - when firmware is reloaded, is it stored on flash memory and not on the drives, or does this sequence denote a failure in the SATA drive controller?
Can't think of anything else to try...
Thanks for suggestions so far, any further thoughts?
dermot
Essentially, I get the same message sequence with difference revisions, except on one occasion with v3 when it hung at 'awaiting RAIDar'... but not repeated.
So, to sum up, if I try to reload from USB, I get 'usb init' then 'recovering' for a moment followed by 'kernel panic'
Rebooting after that gives 'Welcome to the ReadyNAS world' for some seconds, then 'booting' followed by 'ERR: Bad firmware' I get these results with just a single drive (several known good ones) in bay #1 or a full set of 500GB ones, both Western Dig and Seagate.
A long press on reset while power on starts the firmware reload, but ends in Bad firmware.
Interestingly, if I try and reload from USB with no drives fitted at all, I still get 'recovering' for a moment then 'kernel panic' - when firmware is reloaded, is it stored on flash memory and not on the drives, or does this sequence denote a failure in the SATA drive controller?
Can't think of anything else to try...
Thanks for suggestions so far, any further thoughts?
dermot
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
