RND4000 trying to boot from USB but OS Index Error
Hi Team,
I have an RND4000 NV+ 4 Bay. It is stuck on boot, I have done the initialisation of OS already, still the same. I have downloaded both the oldest and newest radiator bios firmware files from the support page. Loaded them one at a time on a blank FAT32 format USB in the root directory, then placed the USB in the front USB socket on the NAS unit. Held the power but down for 20 secs until the display indicated USB boot mode. In both instances the sequence stopped with an error "BIOS INFO: OS Index ERROR". This would happen with or without disks being in.
I cant find any reference to the error.
RAIDar cant see the unit.
Any suggestions would be helpful, the disks have data on them.
Re: RND4000 trying to boot from USB but OS Index Error
That's not how you create a USB recovery drive. But how you do it depends on which version of the NV+ you have, which is the reason for @StephenB 's question.
Thx Stephen for the response. It has NV+ on the front grille.
There is some risk when running the USB recovery, so it would be good to make sure it is the right step first.
I suggest powering down and removing the disks in the NAS (labeling by slot). Then power up. Normally you would then see a "no disks" message on the LCD screen of the NAS. Are you seeing that?
If you are, then I suggest powering down again, and reinserting the disks. Then power up. Let us know what is on the LCD screen (if anything). Also install RAIDar, and see if it can find your NAS. If it can, let us know what status it is showing (posting a screenshot is a good way to do that).
Re: RND4000 trying to boot from USB but OS Index Error
After removing the disks and powering on I see the message 'No Disks'. I can power the unit down by pressing and holding the power button.
I insert the disks again and reboot, the units remains 'booting...' and hangs there.
When I engage raidar it cannot see the unit and asks me to rescan.
There are no other NAS units on my network. I assume it cannot see it as the unit has not reached the stage where an IP address is established.
I can NOT power the unit down by pressing and holding the power button when it is in the 'booting' phase so I have to remove the power cord to power it down.
Re: RND4000 trying to boot from USB but OS Index Error
Stephen, just letting you know I am trying to get my hands on a spare drive. I appreciate your help and as soon as I get one I'll be straight back to you.
Re: RND4000 trying to boot from USB but OS Index Error
I have a spare drive now - its a Seagate Barracuda 160GB. I'll remove the data drives and number them. I will place the spare drive in a caddy and await instructions.
I will place the spare drive in a caddy and await instructions.
Just put the drive into slot 1, and then boot up the NAS and do a factory default. This normally will do a fresh factory install on the NAS. If that works (and the system boots normally), then the boot issue is actually due to something on the operational disks, and not the flash memory.
Re: RND4000 trying to boot from USB but OS Index Error
Hi Stephen,
I did get that disk and tried to run it up in the old chassis and it failed with a 'disk error - no disk'.
BUT I did get a hold of an identical chassis. I tried the same disk in that with the factory reset and it worked. I then put my original disks in the new chassis and it went thru an update of the firmware onto the disks, and then booted to the disks. I can see all my data in the original format so I have copied the data off, so at least that is done.
I tried first putting the new disk back in the old chassis and it hung on booting; then tried the original disks with the same result.
My take is the old chassis has some sort of 'boot' issue internally - be it the bios or something else.
Re: RND4000 trying to boot from USB but OS Index Error
Your symptoms sound more like a power related issue. "No disks" with a drive inserted is typically a hardware problem, not a firmware one (assuming you know the drive is good), Replacement supplies are available, but IMHO it's not a worthwhile expense at this point due to the age of the NAS and since you've recovered your data. Not to mention I'm just guessing that would even fix the problem.
I did get that disk and tried to run it up in the old chassis and it failed with a 'disk error - no disk'.
BUT I did get a hold of an identical chassis. I tried the same disk in that with the factory reset and it worked. I then put my original disks in the new chassis and it went thru an update of the firmware onto the disks, and then booted to the disks. I can see all my data in the original format so I have copied the data off, so at least that is done.
I tried first putting the new disk back in the old chassis and it hung on booting; then tried the original disks with the same result.
My take is the old chassis has some sort of 'boot' issue internally - be it the bios or something else.
Stephen what would you suggest from here?
Pete
I agree with @Sandshark that this is likely a power issue with the old chassis.
If the replacement is a chassis you can keep, then I suggest keeping the old one around. It's possible that something on the system board of the replacement will fail, and if so you can shift back to the old chassis (also moving the power supply from the replacement back to the old chassis).
If the replacement isn't yours to keep, then you should find a more current storage solution (and you might want to plan for that anyway, given that the Netgear stopped manufacturing your NAS about 10 years ago). Definitely shop around, I think it's increasingly clear that Netgear has silently left the NAS market, so you likely will need to switch to a different vendor.
