NV+ V2 stuck at booting

---

Craigatitus2 wrote:

 

A factory Default may be the next step if the OS Reinstall doesn't work...    I don't know what else to try...

 

 

---

If you are the original purchaser, then per-incident paid support from Netgear would be an option.

If you don't have a backup then that's worth considering.

I am the original purchaser.  Do you know approximately how much the paid support costs?  Money is a little tight right now.

Thanks

Craig.

---

Craigatitus2 wrote:

I am the original purchaser.  Do you know approximately how much the paid support costs?  Money is a little tight right now.

 

Thanks

Craig.

---

I don't work for Netgear, and don't have access to their current prices (and they might depend on the region).

But $75 US is the amount I recall.  

If you needed Data Recovery it would be a lot more (starts at $200, and depends on the time that takes). However, there's no reason to think that data recovery is involved, based on the info we know so far.

Ok I think i have some progress but it may still be too early to tell.

Since i read that sometimes the disks themselves can cause various Readynas units to get stuck at booting.  I decided to shut the unit down and remove disks and boot it up again one at a time.  So first i removed disk 1 and booted it up and it stopped at the exact same place of stuck at "booting...".   

I then shut it down again and inserted disk 1 back in and turned it on.  This time the unit proceeded on past booting and appears to have loaded up somewhat normally (Transmission is failing to start  "transmission-daemon Error loading config file -- exiting. (daemon.c:498)") and i can now get into Frontview.

Now the unit indicates that C: is unprotected and Not-Redundant.   All shares are there with what looks like all files in place.  Frontview does not say its running a Resync or anything.  Shouldn't it be automatically trying to resync now or will that attempt on the next boot?  

The message "kernel: program smartctl.org is using a deprecated SCSI ioctl, please convert it to SG_IO" is still appearing in the syslogs but at least now i see the other services starting up and looking normal.

Ok a reboot of the unit doesn't seem to kick off the resync either and the volume is still "unprotected".  Can someone recommend the best way to resync the volume?  Should i hot pull the first drive and then put it back in?  Are there linux commands to kick the process off?

On a side note, the reboot fixed the issue with Transmission and now both Transmission and Sabnzbd are working.

Thanks

Craig.