NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
jaidank
Aug 09, 2013Aspirant
ReadyNAS NV+ v2 'no disk detected' after upgrade [SOLVED]
Having owned and loved a Duo v1 for many years I bought a pre-owned NV+ v2 without disks.
I installed one of my ST3500418AS (500GB on HCL of both Duo and NV+ v2) in the NV+ and did a factory default boot.
Everything went perfectly and the NV+ came up running 5.3.8
Now the bad news.
Aware of the potential 'power down boot loader' problem, I decided to reinstall 5.3.8.
During the required reboot got a corrupt volume error.
After that, every attempt to reboot, or another factory default boot gets ERR: no disks detected!
As it happens I also got a Duo v2 as part of the 'deal'.
After getting past the 'power down boot loader problem' this did a perfect 'factory default' boot with the same ST3500418AS and came up with 5.3.8
The Duo v2 even handled a 5.3.8 reinstall in its stride.
So I took the initialised ST3500418AS from the Duo v2 and put it in the NV+. Still ERR: no disks detected!
Has anybody encountered a problem like this.
BTW, the NV+ v2, which looks new and was with full (matching serial number) packaging was previously registered and is thus devoid of warranty and support.
Any help appreciated (and don't worry; it didn't cost much :-)
Cheers, Aidan
I installed one of my ST3500418AS (500GB on HCL of both Duo and NV+ v2) in the NV+ and did a factory default boot.
Everything went perfectly and the NV+ came up running 5.3.8
Now the bad news.
Aware of the potential 'power down boot loader' problem, I decided to reinstall 5.3.8.
During the required reboot got a corrupt volume error.
After that, every attempt to reboot, or another factory default boot gets ERR: no disks detected!
As it happens I also got a Duo v2 as part of the 'deal'.
After getting past the 'power down boot loader problem' this did a perfect 'factory default' boot with the same ST3500418AS and came up with 5.3.8
The Duo v2 even handled a 5.3.8 reinstall in its stride.
So I took the initialised ST3500418AS from the Duo v2 and put it in the NV+. Still ERR: no disks detected!
Has anybody encountered a problem like this.
BTW, the NV+ v2, which looks new and was with full (matching serial number) packaging was previously registered and is thus devoid of warranty and support.
Any help appreciated (and don't worry; it didn't cost much :-)
Cheers, Aidan
9 Replies
Replies have been turned off for this discussion
- mdgm-ntgrNETGEAR Employee RetiredCan you get it to boot into tech support mode?
- jaidankAspirant
mdgm wrote: Can you get it to boot into tech support mode?
Hi mdgm,
I have just tried and yes. After 'booting' for a few minutes:
DebugMode[55366]
192.168.0.221
And the disk 1 led is lit.
I forgot to mention in my original posting that there was disk access sound before the 'ERR: no disks detected'.
Also the 'retired' ST3500418AS had perfect Smart stats (from my Duo v1, one week ago today).
I also tried the disk in a different slot. Finally I tried my second retired ST3500418AS (same heritage & clean SMART; slightly older) without success.
So there is hope??
I have tried telent and am prompted for username/password.
I have tried admin/55366 etc. without success. Not that I know what to do if/when I get in (I am a unix user).
Cheers,
Aidan - mdgm-ntgrNETGEAR Employee RetiredSo are your disks in the NAS?
- jaidankAspirant
mdgm wrote: So are your disks in the NAS?
Yes. Just one. I think its the one that scanned and installed perfectly the first time (before the failed upgrade) and installed perfectly in the Duo V2.
I read your 'Re: Another 'Booting..." NV+ issue' and understand that debug mode is only accessible by Netgear support. I don't suppose you have the required skills and inclination? I have set up port mapping on my router and could share my IP (effective) address with you via PM. Not to mention reboot it in debug mode again (its off atm).
Should I install the second ST3500418AS too?
PS: just saw your PM. On this boot (DebugMode) there is no disk let lit.
Will try hot unplug/plug (is that safe in debug mode)
All help appreciated.
Aidan - jaidankAspirantI have a nasty feeling that there may be electrical SATA connection problem.
I dont do this very often, and may be imagining it, but the disks slid in VERY easily.
I seem to remember that a little bit of pressure was required to get the SATA connector into the chassis.
I better hide my screwdriver set :-) - mdgm-ntgrNETGEAR Employee RetiredHardware failure does sound like a strong possibility here.
- jaidankAspirantMany thanks mdgm.
I really appreciate your efforts with this basket case.
All the best,
Aidan - jaidankAspirantSo it was time to break out the screwdrivers.
VERY nicely made unit. Quite easy to take apart.
I unplugged an plugged the sata backplane several times to make sure it wasn't a connection issue there. It wasn't.
As there had not been any disk sounds for quite a while I guessed there might be a sata power supply problem so I
was thinking of running a disk, out of the chassis with external sata power but sata data connected to the NV+.
Before doing that (I have to purchase the kit) I decided to (carefully) test the voltages on the (all) empty sata power connectors.
No power! (3.3v, 5v, or 12v). Thinking about sourcing a replacement sata backplane.
Another hour staring at the sata backplane and checking continuity with a multimeter.
It seemed to me that both 12v and 5v should be coming from the main board via the smaller of the two connectors;
the 12v via the middle pins on the capacitor side and the 5v the middle pins on the sata connector side.
The 12v fed to u3, u4, u7, u8 for (conditioning?) on the way to the sata; with 4 independent circuits, now thinking sata
backplane is not the problem.
Carefully test the voltage at u3, u4, u7, u8 with one disk fitted; less than 9v.
Can't see an obvious place on the main board to test voltage so was about to write off the unit (main board too expensive, right?)
Last minute hunch, test the voltage from the psu as it enters the main board; less than 9v.
Seems like the psu is the culprit; verified my multimeter on a 12v car battery; no smells from it though.
What do people think? Am I on the right track or deluding myself.
Can anybody recommend a source for a replacement psu?
Cheers,
Aidan - jaidankAspirantIn summary, the re-upgrade was a red herring; the problem was an intermittently faulty power supply.
It only supplied around 9V, enough to power the motherboard but not the disks (not reliably anyway).
Netgear support not very helpful; could not tell me where I could buy a replacement PSU.
I bought and fitted an aftermarket PSU and everything now seems fine. I am absolutely thrilled
and cannot wait to migrate my new disks from my trusty Duo v1 (via factory reset an restore).
Special thanks due to mdgm who helped with DebugMode and focused me on a hardware problem.
Cheers, Aidan
Related Content
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!