How can I find out what is happening? (case #18901615)

I seem to have the same problem - requesting a download of logs crashed my NV+ so that it wouldn't reboot.

I eventually tried a "reload firmware" restart (using the reset hole) and that brought it all back to life - just had to enter a few network parameters and an admin password.

Beware though, I then tried to download the logs again and got exactly the same result!

Once you have recovered with an OS reinstall, it would be a great time to update/create your backup so you can then do a factory default. Apparently there is a problem with the size of the log file.

davebush better to open a new thread rather than revive another one. Also please open a support case at my.netgear.com

Downloading the logs works fine for me. The first thing I'd suspect would be the OS partition being very full perhaps due to a log file that wasn't truncated properly for some reason.

It wasn't an attempt to revive, merely passing on information. The backup log files were 219MB and 136MB - after I deleted them download logs works fine.

Thanks Dave. It is good to know that someone else out there has seen this. It did happen the last time I downloaded the logs but the Duo synced ok and cames back on-line. From memory, the boot partition was only ~50% full when I last looked so I do not believe it is a O/S partition full problem although I will check when I get it back on-line.

Latest update from NetGear Support: no L3 reponse as yet, Duo still in telnet mode waiting for them. The L2 Engineer cames back overnight with the less than helpful suggestion of:

Thank you for your response. I do apologize for the inconvenience that this has caused you. Please upgrade your NAS firmware to the beta firmware 4.1.10[T3]. You may download the firmware on the link below: viewtopic.php?f=17&t=59222 Thanks again for choosing NETGEAR. Have a great day!

I am struggling to see how I can upgrade the firmware when the Duo cannot boot ...

Gave up waiting for Netgear Support. Duo was in telnet mode waiting for L3 for over 2 weeks. During this time I received no communication from L3 and all I got from the L2 contact was silly suggestions.

Following Dave's advice, I rebooted and did a O/S Reinstall and the Duo is back on line.

The / filesystem is only 52%:

Filesystem 1k-blocks Used Available Use% Mounted on /dev/hdc1 2031872 1046160 985712 52% / tmpfs 16 0 16 0% /USB /dev/c/c 1935855664 1203994352 731861312 63% /c

so how do I clean out the "backup log files" to stop this happening again?

I used the SSH feature, but if you look on the "backups" page there's a list of backup jobs. One of the icons to the right is labeled "delete log"........

I prefer to use ssh: where do they live so I can delete them from the shell?

Can you post the output of the following?:

# df -h
# df -i
# du -csh /var/log/frontview/backup

ianch-nas:/# df -h
Filesystem            Size  Used Avail Use% Mounted on
/dev/hdc1             1.9G  1.0G  960M  52% /
tmpfs                  16k     0   16k   0% /USB
/dev/c/c              1.8T  1.2T  697G  63% /c
ianch-nas:/# df -i
Filesystem            Inodes   IUsed   IFree IUse% Mounted on
/dev/hdc1             128000   11974  116026   10% /
tmpfs                   7073       1    7072    1% /USB
/dev/c/c             60981248   85630 60895618    1% /c
ianch-nas:/# du -csh /var/log/frontview/backup
134M    /var/log/frontview/backup
134M    total

Thanks ..