- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
RN316 will not boot. Corrupt?
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I just bought this RN316 used and am planning on using it to backup my 516...
I am familiar with the boot menu, and can't get it to show up on this machine. I think the internal storage is corrupt or something and I need to reinstall the OS.
When I boot now (with a LCD hooked up) I get the message: "This is not a bootable disk. Please insert a bootable floppy and press any key to try again . . ." The display on the front of the machine just reads: Booting...
Is there any way to create a bootable usb drive that will reinstall the OS onto the onboard storage?
I have tried it with a HDD in it and without, can't get to the boot menu.
Solved! Go to Solution.
Accepted Solutions
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
All Replies
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Re: RN316 will not boot. Corrupt?
Thanks Stephen! That's exactly what I'm looking for!
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Re: RN316 will not boot. Corrupt?
Is there a trick to getting the tool to recognize a img file? I've tried putting the 6.4 img in the same folder as well as 6.2.4. Nothing populates in the Firmware Image area.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Re: RN316 will not boot. Corrupt?
Nevermind... I got it. Apparently you have to drop it in the x86 folder, not the root.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Re: RN316 will not boot. Corrupt?
Just an update... In case anyone runs into the problem I did. This did solve the problem. The NAS is up and running flawlessly.