Reply

Failed to update RAIDiator 4.2.31 to 6.x

xhen
Aspirant

Failed to update RAIDiator 4.2.31 to 6.x

Dear experts.

In order to update/disable the SMB1 of the device for company security reasons

today I tried to update my fantastic ReadyNas 2100 ,

I updater to the version RAIDiator 4.2.31 without any problem and them tried to update to OS 6

following these instructions

https://blah.cloud/just-for-fun/upgrading-a-legacy-readynas-from-raidiator-4-2-x-to-6-2-x/

and this

https://community.netgear.com/t5/ReadyNAS-Storage-Apps-Current/ReadyNAS-OS-6-9-3-Run-on-existing-x86...

 

I uploaded the R4toR6_Prep_Addon.bin but by error I restarted the device. (was doing other things at the same time and forgot not to restart it, S***T)

 

so after restar the device, Blue light  fixed, and one Eth blinking, the other eth is fixed, NO light on disks (it has 4 HD od 1TB)

I tried these steps

https://kb.netgear.com/24872/How-do-I-access-the-boot-menu-on-my-ReadyNAS-1500-2100

Factory default and OS reinstall

but when I restart, press the reset and power, all lights are fixed, them I press backup,

The USB led is iluminated and Led disk1,

press backup again

The USB led is iluminated and Led disk2,

press backup again

The USB led is iluminated and Led disk3,

press backup again

The USB led is iluminated and Led disk4,

press backup again

The USB led is not ilumintaed and Led disk1,

press backup again

The USB led is not ilumintaed and Led disk2,

press backup again

The USB led is not ilumintaed and Led disk3,

press backup again

The USB led is not ilumintaed and Led disk4,

press backup again

The USB led is ilumintaed and all Leds at same time.

during the previous steps I have selected Boot Menu Mode Press and release the SYS / Reset button but nothing do, 

no reboot nothing after pressing reset always all leds iluminated but nothing.

I test this with and without all Disk and nothing happens....

I tried to use the RAIDiator 4.2.x USB recovery but I can not run on windows 10.

I tried to copu the RAIDiator-x86-Version-4-2-31.bin directly in a USB

https://kb.netgear.com/000038793/RAIDiator-x86-Version-4-2-31

but doesnt worked.

it has not get any IP address (I conected to diferent networks and not DHCP request.)

I dont know what else to do, you are my last chance.

 

Regards,

Model: RNRX4000|ReadyNAS 2100 Chassis only
Message 1 of 10

Accepted Solutions
StephenB
Guru

Re: Failed to update RAIDiator 4.2.31 to 6.x


@xhen wrote:

If is the V1 what can I do? I dont mind to use the version

RAIDiator 4.2.31 is not mandatory to use the OS 6

I just want to recover the device...it was really nice device, never a issue or problem


@mdgm might have some ideas.  My guess is that USB recovery should work.  The process is here: https://kb.netgear.com/30267/RAIDiator-4-2-USB-Recovery-Tool  If you try it, run usbrecovery.exe with elevated privilege (not stated in the guide).

View solution in original post

Message 4 of 10

All Replies
StephenB
Guru

Re: Failed to update RAIDiator 4.2.31 to 6.x

While you can convert the 2100v2, you cannot convert the older 2100v1.

 

Can you confirm that the model is a v2?

Message 2 of 10
xhen
Aspirant

Re: Failed to update RAIDiator 4.2.31 to 6.x

I will confirm tomorrow at the office.

If is the V1 what can I do? I dont mind to use the version

RAIDiator 4.2.31 is not mandatory to use the OS 6

I just want to recover the device...it was really nice device, never a issue or problem

Message 3 of 10
StephenB
Guru

Re: Failed to update RAIDiator 4.2.31 to 6.x


@xhen wrote:

If is the V1 what can I do? I dont mind to use the version

RAIDiator 4.2.31 is not mandatory to use the OS 6

I just want to recover the device...it was really nice device, never a issue or problem


@mdgm might have some ideas.  My guess is that USB recovery should work.  The process is here: https://kb.netgear.com/30267/RAIDiator-4-2-USB-Recovery-Tool  If you try it, run usbrecovery.exe with elevated privilege (not stated in the guide).

Message 4 of 10
xhen
Aspirant

Re: Failed to update RAIDiator 4.2.31 to 6.x

I tried that tool also , but gives me error on windows 10 x64 (side-by side error) and I was unable to run and create the USB for recovery.

 

Edit this coment: I am trying from home and the tool worked OMG!!

in the company computers was not worked, sure a security policy!!!

I am so happy tomorrw I will try to recover with the usb created at home!!!

 

I will reply tomorrow

 

Message 5 of 10
xhen
Aspirant

Re: Failed to update RAIDiator 4.2.31 to 6.x

Hello everyone

finally I recovered my devide!!!

thank you so much!!!!

I see that is version 1 so as you told me I can not update to OS6 no?

Model:ReadyNAS 2100 v1 [X-RAID2]
Serial:2A5609R200XXXX
Firmware:RAIDiator 4.2.31 
Memory:1024 MB [6-6-6-24 DDR2 ECC]
IPv4 address: 1+2:192.168.1.20
Volume C:Online, X-RAID2, 4 disks, 97% of 2759 GB used
Message 6 of 10
mdgm
Virtuoso

Re: Failed to update RAIDiator 4.2.31 to 6.x

Great!


The V1 has a 32-bit Intel CPU. OS6 for x86_64 requires a 64-bit Intel CPU. That's why it won't work on your V1.

Message 7 of 10
xhen
Aspirant

Re: Failed to update RAIDiator 4.2.31 to 6.x

understood, thanks so much for your help!!! I really appreciate!!!

have a fantastic weekend!!!

 

Message 8 of 10
Sandshark
Sensei

Re: Failed to update RAIDiator 4.2.31 to 6.x

Try running the USB creation tool as administrator.  You may also need to try another device.  Make sure you are following all the restrictions, especially that it is FAT formatted and must have only one partition, as don't know how the creation tool will react if they are not met.  In some cases, the USB will appear to be fine but not work, but there may be cases where it fails to be created properly.  Some devices have a hidden partition (usually associated with encryption), so check for that in Disk Management.

 

I really hope USB recovery works, as the warning about doing the OS6 conversion on an incompatible system is that you can brick the unit.

Message 9 of 10
mdgm
Virtuoso

Re: Failed to update RAIDiator 4.2.31 to 6.x


@Sandshark wrote:

I really hope USB recovery works, as the warning about doing the OS6 conversion on an incompatible system is that you can brick the unit.


The user already has successfully done USB Boot Recovery. The process to upgrade to OS6 doesn't touch the bootloader and even if OS6 has code that would mess things up it wouldn't be able to run that 64-bit code.

 

So USB Boot Recovery should always work to recover these systems from an unsuccessful attempt to update to OS6.

Message 10 of 10
Top Contributors
Discussion stats
  • 9 replies
  • 1806 views
  • 2 kudos
  • 4 in conversation
Announcements