NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
AMM
Jan 19, 2015Aspirant
ReadyNAS NV+ v1- boot troubleshooting
Hi, I've read all the boot hang threads in the forum and have a game plan to troubleshoot my own boot hang, but before I start, I want to have a plan a, b, c, etc. and I have a couple of questions to try to maintain my x-raid data.
First, this is what happened. My NAS has been humming along happily for 4.5 years. The other day we had a brief 2-second power outage...enough to make the clocks all go back to 12:00. That night or next day, I noticed my HTPC was not able to connect to this NAS.
I have two ReadNAS's both connected to the same UPS. The NVX was fine, but this one said it was waiting for IP on the LCD. I could see it was hung up there, so I shut it down via the power button. Then restarted it. Then it just hung at Booting - Please wait. Now the only way to power it off is to pull the plug. I received no error emails prior to this event so I know whatever went wrong was instant.
So now I will troubleshoot.
1) Power off, mark disc locations and remove all disks and test each one with the diagnostic tool. Hopefully only one drive is bad, if any.
2) Try booting with a spare good disk.
2) If hangs, power down and try booting into an OS reinstall from flash.
3) If still no successful boot, try an OS install from USB image. This is where one question is. I don't upgrade firmware if I'm happy with the one I have, and I was, so it's on a very old one- v4.1.7. I don't see where I could get an image of this version anymore. So if I upgrade to the latest radiator version in this step, will that screw up the readability of my good x-raid drives when I re-install them? Or will this be ok to do?
4) If I can get it to boot on the spare drive, then power down, re-install just the good raid-x drives in their original locations leaving the bad one out and boot up on them (fingers crossed).
5) If it boots, hot-add a new replacement drive to sync into the raid.
Another question. Let's say all the diagnostic tests find all drives to be ok.
Then I was thinking I would try booting it with 3 drives in at a time (always in their original positions) to see which one is causing the boot issue. This should still maintain my data, correct? It won't boot on the bad drive, and when it does boot, it will be just the same as step 4 above so figure I am ok to test this way, yes?
I doubt it is the momory, but I'll run that test too if no success.
First, this is what happened. My NAS has been humming along happily for 4.5 years. The other day we had a brief 2-second power outage...enough to make the clocks all go back to 12:00. That night or next day, I noticed my HTPC was not able to connect to this NAS.
I have two ReadNAS's both connected to the same UPS. The NVX was fine, but this one said it was waiting for IP on the LCD. I could see it was hung up there, so I shut it down via the power button. Then restarted it. Then it just hung at Booting - Please wait. Now the only way to power it off is to pull the plug. I received no error emails prior to this event so I know whatever went wrong was instant.
So now I will troubleshoot.
1) Power off, mark disc locations and remove all disks and test each one with the diagnostic tool. Hopefully only one drive is bad, if any.
2) Try booting with a spare good disk.
2) If hangs, power down and try booting into an OS reinstall from flash.
3) If still no successful boot, try an OS install from USB image. This is where one question is. I don't upgrade firmware if I'm happy with the one I have, and I was, so it's on a very old one- v4.1.7. I don't see where I could get an image of this version anymore. So if I upgrade to the latest radiator version in this step, will that screw up the readability of my good x-raid drives when I re-install them? Or will this be ok to do?
4) If I can get it to boot on the spare drive, then power down, re-install just the good raid-x drives in their original locations leaving the bad one out and boot up on them (fingers crossed).
5) If it boots, hot-add a new replacement drive to sync into the raid.
Another question. Let's say all the diagnostic tests find all drives to be ok.
Then I was thinking I would try booting it with 3 drives in at a time (always in their original positions) to see which one is causing the boot issue. This should still maintain my data, correct? It won't boot on the bad drive, and when it does boot, it will be just the same as step 4 above so figure I am ok to test this way, yes?
I doubt it is the momory, but I'll run that test too if no success.
6 Replies
Replies have been turned off for this discussion
- NhellieVirtuosoThe troubleshooting plan is good. :)
3) If still no successful boot, try an OS install from USB image. This is where one question is. I don't upgrade firmware if I'm happy with the one I have, and I was, so it's on a very old one- v4.1.7. I don't see where I could get an image of this version anymore. So if I upgrade to the latest radiator version in this step, will that screw up the readability of my good x-raid drives when I re-install them? Or will this be ok to do?
-if the drives detected that there is a new FW on the flash, it should automatically upload it on the drives. However, if this does not happen, you can also perform another OS reinstall.
4.1.7 is really old, you can find it here though:
http://www.readynas.com/?p=4662 - AMMAspirantThanks Nhellie!
Looks like you changed the URL to the firmware. The URL to Netgear support is a dead end, but I went to the first URL you provided and I believe it was there. If this is the correct one? - RNR4_RND4_RND2_4.1.7_WW_src.zip.
I must write the contents of this zip to the USB flash drive using Rawrite32.zip, correct? How much space does the flash drive need for this?
I'm glad you could help me get the same firmware version I have. That simplifies the process (and worry). I'd rather not upgrade the firmware during this...just adds more posible things that can throw fixing this off, imo. - NhellieVirtuosoYeah, I did since I thought it is much better if you donwload it on ReadyNAS' official page.
Check the instructions on this link:
http://home.bott.ca/webserver/?p=159 - AMMAspirantOk, I guess what I downloaded is no good for a USB flash because it's not an .img file. It's a zip. It must be the installation files for the NAS upgrade downloads.
Does anyone know where I might find a sparc firmware USB boot disc image of v4.1.7 available for download?
Those USB flash drive instructions mention old versions of Windows. Does NTRawrite still work to write an image on Win 7 or 8 64 bit? - NhellieVirtuosoNot sure why 4.1.7 was removed, oldest one I can find is 4.1.8 http://www.downloads.netgear.com/files/ ... -4.1.8.zip
I believe they still work on newer versions, haven't tried it myself. - mdgm-ntgrNETGEAR Employee RetiredThat's not the USB Boot Recovery image. This is one: http://www.readynas.com/download/support/ReadyNAS_USB_Flash_Recovery-4.1.7.img
Do you have a backup of your data?
Boot Recovery is not recommended until after ruling out other possibilities. It's seems very unlikely to me that the problem would be with the internal flash.
Related Content
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!