Forum Discussion

Aspirant

Apr 10, 2020

Readynas NV+ v1 hangs on boot after log download attempt

After trying to download the log files from Frontview, NAS won't boot, it goes into FS check and when it finishes it hangs at Booting...

I found a previous member from 2017 that seems to have had the exact same issue and it was resolved by somehow deleting the large log file in tech support mode using telnet which was preventing a reboot. Can anyone tell me how to find and apply this same solution? Do I do this myself with a tech reboot?

Bob

This was the original post and the kudo'd solution I found on the board:

I have a ReadyNAS NV+ v1 that will not boot. After power-up, it goes into checking quotas, then it displays 'Booting...' and never completes. After that, it will not respond to the power button. I believe it got into this state after I attempted Download All Logs from Frontview.

My NAS contains 4 2-TB data drives. Thinking that maybe I had a bad drive, I tried powering off, removing each drive in turn and powering up, but with the same result: it won't boot. I then removed all 4 data drives and inserted a scratch drive, and it booted successfully. It will boot no matter which position the scratch drive is installed in.

Then I tried Download All Logs with the scratch drive inserted, and FrontView stopped responding, and the NAS would not reboot, again getting hung at 'Booting...'.

At this point, I tried a different scratch drive, and it booted again successfully.

I reinstalled the firmware using the reset switch. It still booted fine with the scratch drive. I Cleared the logs using Frontview, and it still booted with the scratch drive. I reinstalled my 4 data drives, and it would not boot.

Any suggestions? Is it likely that the problem is in the bare NAS box itself, or is it on one or more of the drives, and if that's the case, is my data toast? It's possible I could obtain another bare NV+ box and plug my drives into it to try to get the data off, if that is a viable option. I don't know how the ReadyNAS OS architecture works, nor whether it depends on the data drives in order to boot, so I'm likely missing something (a lot) here.

I have no backup -- foolish, I know. The data is not mission-critical, but it would save some major inconvenience if we could recover it. The NAS was purchased in 2009, so it is long out of Netgear support.

Thank you,

Matt

Rebooting. Looks like huge backup log files prevented the logs from being downloaded.

I've copied the huge backup job logs to the hidden .logs folder on the C volume and emptied the original on the 2GB root volume.

The system should boot up fine now.

I checked the disk health and all look to be healthy.

Assuming it comes up fine now you may wish to backup your data.

4 Replies

StephenB
Guru
Apr 10, 2020
bkrupinski wrote:

I found a previous member from 2017 that seems to have had the exact same issue and it was resolved by somehow deleting the large log file in tech support mode using telnet which was preventing a reboot.

That's only one possible cause, so your solution might not be the same.

You could try using the boot menu, and selecting the option that skips the volume check. See pages 23-24 here: http://www.downloads.netgear.com/files/GDC/RND2110/Duov1_NV+v1_HW_en_06Dec11.pdf

Another option is to try paid netgear support (via my.netgear.com). Ask about per-incident support.

Are you familiar with the linux CLI interface?
- bkrupinski
  Aspirant
  Apr 10, 2020
  I've tried booting with the no volume check option and it goes right to the Booting... and freezes. I also booted in tech mode and I get an IP address and a debug mode code and the NAS appears under Raidair but I'm not at all familiar with Linux coding. I made some amateur attempts to connect using telnet from my mac but it was always refused.
  While the FS check is going on, the drives all appear on Raidar as healthy and this booting issue happened immediately after the download attempt of the logs which is why I suspect that to be the problem.
  
  I also sent an email to Netgear asking for a per incident look but haven't heard back yet. The device is not registered but I can't read the s/n and can't enter it under my devices so I'm going through customer support.
  Thanks for your help!
  - StephenB
    Guru
    Apr 11, 2020
    bkrupinski wrote:
    
    I've tried booting with the no volume check option and it goes right to the Booting... and freezes.
    
    The immediate failure means that the file system check isn't the cause of the freeze.
    
    bkrupinski wrote:
    
    I also booted in tech mode and I get an IP address and a debug mode code and the NAS appears under Raidair but I'm not at all familiar with Linux coding. I made some amateur attempts to connect using telnet from my mac but it was always refused.
    
    FWIW, the debug code is needed for Netgear's remote access. You don't need it locally.
    
    In tech support mode, you log in as root. The password is infr8ntdebug
    
    But that's only the first step. After that you need to manually mount the OS partition, and chroot. Then you can see if the OS partition is full or not.
    
    It's probably best to wait on support, as if you accidentally do damage they likely will deny support. JohnCM_S or Marc_V might be able to assist with the registration issue.