ReadyNas Pro6 will not start

Some lines that look like they point to something don't because they are designed for another unit type and just always fail on devices they are not intended for (such as looking for a display when there is none or a different style).  I do not know if that is the case here, and don't currently have a Pro6 set up to see if it also has that.  But the basic indication is that the NAS hardware is mostly working.  Unfortunately, the boot process doesn't continue to display everything on the monitor.  One thing that can cause it to stop at that particular point is not being able to recognize the hardware on which it is running.  I think it's Netgear's effort to prevent anything similar to Xpenology.  I don't know if it would be detectable with RAIDar if that's the case, but probably not since RAIDar wouldn't know what to call it.  The exact product type is in an encrypted file in the flash (ProBE, Pro Pioneer, Pro6, or Ultra6Plus), but there must be something else it looks for because the NAS will boot even with that file missing.  What that something else is, I have not been able to determine, but I suspect the DMI data.

Of course, it could also stop if the small part of the firmware that's on the flash and passes control to the drives is corrupt.  It doesn't really look like that, but a USB recovery could be the answer.  In order to do that, you'll need to create an OS4.2.x style recovery but use a modified OS6 image like is used to convert initially to OS6.  Either that or completely USB recover to OS4.2.x and then re-convert.  Just remember not to put your volume back into the unit until it's back at OS6 -- use a scratch drive for everything.  OS6 native USB recovery won't work because it's not written to recognize legacy hardware.

Hi!

Thank you for tips!

Folowing this link https://kb.netgear.com/30267/RAIDiator-4-2-USB-Recovery-Tool Looks like it missing some file. Stops at:

SYSLINUX 3.73 2009-01-25 EBIOS Copyright (C) 1994-2008 H. Peter Anvin

Loading kernel ............................................

Loading initrd.gz.............................ready.

And no more....

Display says ReadyNAS

The guide tells me to copy firmware file and release notes from the zip file. When I am generating USB i can just pick xml file and copy this file to USB. Removing xml file, I can choose the .31 file

There are files missing on the USB stick. Probobly issue with windows 10?

---

nautic_no wrote:

 

 

The guide tells me to copy firmware file and release notes from the zip file. When I am generating USB i can just pick xml file and copy this file to USB. Removing xml file, I can choose the .31 file

 

---

What xml file?

The RAIDiator-x86-4.2.31_Release_Notes.html file

The files on the USB:

24.10.2020 12:21 525 syslinux.cfg
24.10.2020 12:21 2 701 168 kernel
24.10.2020 12:21 2 681 717 initrd.gz
24.10.2020 14:17 1 417 RAIDiator-x86-4.2.31_Release_Notes.html

Sorry for many posts, I had to split it up. I am able to boot on Centos. Is it possible to fix this issue from Centos?

---

nautic_no wrote:

The fies on the USB:

24.10.2020 12:21 525 syslinux.cfg
24.10.2020 12:21 2 701 168 kernel
24.10.2020 12:21 2 681 717 initrd.gz
24.10.2020 14:17 1 417 RAIDiator-x86-4.2.31_Release_Notes.html

---

Try just putting the firmware image in the USB recovery folder, and leave out the release notes.

Hi!

I have already tried this. Then the firmware file appears in dropdown and are copied to USB stick. Still not booting. I tried to copy rest of the files from PC to USB. Then it says Missing operating system. I hope you have more tips!

Best regards

---

nautic_no wrote:

I have already tried this. Then the firmware file appears in dropdown and are copied to USB stick. Still not booting. I tried to copy rest of the files from PC to USB. Then it says Missing operating system. I hope you have more tips!

 

---

It shouldn't need the release notes file, but you could try copying it manually to the USB stick after you create it.

I don't think you will see much more on the screen, but about 30 seconds the NAS should power down.

I left it alone for 30 minutes, nothing happens.

A message runs fast over screen while running recovery utility creating USB stick. It sais:

Writing MBR: no access,

Did not successfully update the MBR; continuing

I have choosed running as administrator.

Possible the cause?

What to do?

---

nautic_no wrote:

 

Writing MBR: no access,

Did not successfully update the MBR; continuing

 

---

Have you tried a different USB stick?

Hi

Tried another stick, same issue.

I have run this: (syslinux from usbRecovery catalog)

C:\>syslinux.exe -m D:
Accessing physical drive: No access.
Did not successfully update the MBR; continuing...

Puhhh! At last it worked! I unzipped to a new catalog and some warnings popped up. Accepted warnings and suddenly it worked! Now I have to update to 6! Thank you!

The /ADMIN page are blank! I have 1 disk, thats enough?

---

nautic_no wrote:

The /ADMIN page are blank! I have 1 disk, thats enough?

---

One disk should be enough (it shouldn't be part of the array).

Are you still running 4.2.31?

What status is RAIDar giving you?

Hi!

I have one 2 TB disk,

What disk system shall I choose?

1. Expandable Volum (X-RAID2)   (dont show admin page)
2. Flexible Volum (Flex-raid) (dont show admin page)
3. Erase Volum (not tried)

Still on 4.2.31

Raidar telling Healhy.

Best regards

Nautic_no

With one disk, it really doesn't matter what you choose, since you will be running jbod anyway.

If the disk is formatted, then the system might need you to do a factory default with the boot menu.  There will be a delay (10 minutes) before the default starts - that is intended to give you time to override the xraid/flexraid mode via RAIDar.  Another option is to zero or unformat the disk in a windows PC.  If the disk is unformatted, the NAS should automatically do a factory install on power up.

Note that choosing the xraid/flexraid mode doesn't work with RAIDar 6.5, so if you are trying to do that then you should just wait the 10 minutes.

Hi!

I am using 4.2.31. Using usbrecovery I got it to work. The admin page is blank. Not able to setup anything. I have tried Factory Default and OS Reinstall. Waited 10 minutes. Nothing helps. Hope you have tip for me!

Hi!

Something wrong with the model name Look at attached file

You probably need help from Netgear to repair the flash.  The mods ( JohnCM_S and Marc_V ) might be willing to take a look remotely.  Paid Netgear support is another option, since you are running 4.2.x firmware.

FWIW, you don't need to mask a local (private) IP address, since it is not routable over the internet.  

Hi!

Here is the booting:

MBR

H

SYSLINUX 3.31 v1.07 Tue Feb 15 11:31:02 PST 2011

FOUND SMBIOS

Copyright (c) 1994-2005 H. Peter Anvin

02F8

Normal

FactoryDefault

OSReinstall

TechSupport

SkipVolCheck

MemoryTest

TestDisks

Loading

18

1B

To Be Filled By O.E.M.

To Be Filled By O.E.M.

07/26/2010 FLAME6-MB V2.0

To Be Filled By O.E.M.

kernel.........

Loading initrd.gz........

Ready

_

---

nautic_no wrote:

Hi!

Here is the booting:

 

18

1B

To Be Filled By O.E.M.

To Be Filled By O.E.M.

07/26/2010 FLAME6-MB V2.0

To Be Filled By O.E.M.

 

---

It gets all that from the DMI, so it's properly identifying the hardware.  But it gets the serial number and unit type (ProBE, Pro Pioneer, Pro6, or Ultra6Plus, all of which use the same motherboard) from an encrypted file in flash.  With OS4.2.x, that matters, because different models have different options enabled in the software.  Since your flash was corrupted, it appears that file was too.  As StephenB said, the way to potentially get that fixed is to ask one of the mods to do it for you.  They'll need a photo of the model and serial number label and the unit in support mode.  The encryption key and file format have not been made public, so you can't fix it yourself.

BTW, your BIOS is the most up to date one available.

Hi!

Thanks!

Shall I upload picture here?

Nautic_No

I hope to get some help.