ReadyNas 104 6.2.5 -> 6.4.0 Checksum error

[alexejCederholm]

I am trying to update my ReadyNas 104 from 6.2.5 to 6.4.0 both through the pop-up windows and also through using the manual update method. The download completetes ok, but during the reboot I can see in the display Updating FW and a second later it say ERR Image checksum mismatch. I have tried 3 different browsers and downloaded the file several times with the same error.

Any suggestions how to proceed?

Thank you in advance.

[AlexPe · Accepted solution]

Hi Everyone,

So the issue with the Checksum error is from the BusyBox Md5sum utility. It has a bug that we are still not sure how it is occurring, we are working hard to reproduce it. We are trying to figure out why this bug is affecting some boxes and not affecting others. So there is still a lot of work to be done.

For this issue, you have some options for resolution,

1. You can retry USB boot and see if this fixes the problem, preliminary reports show that this does not fix the issue

(USB Boot Instructions)

2. I have a Debian package that you can install on your ReadyNAS OS6 ARM machine to update the device to 6.4.0 upon reboot.

(ReadyNAS OS 6: RN100/RN2120 cannot update due to invalid checksum)

3.  Create a ticket with support and have Netgear L3 group manually upgrade your device.

The Debian package will work so likely there will be no need for item three, 

Thanks again for your patience and help diagnosing this issue.

Alex

[StephenB]

Do you have ssh enabled?

[alexejCederholm]

Yes SSH is enabled

[StephenB]

You might want to check the OS partition fullness.  

df . -h

df . -i

Also when manually installing, you do need to unzip before you upload.

[alexejCederholm]

df . -h gives me:

Filesystem      Size  Used Avail Use% Mounted on

/dev/md0        4.0G  2.1G  1.8G  55% /

df . -i gives me:

Filesystem     Inodes IUsed IFree IUse% Mounted on

/dev/md0        65536 15538 49998   24% /

To me it looks like plenty of free space and yes I upload the .img file and not the .zip file.

[AlexPe]

AlexjCederholm,

Have you run any maintenance on this system? Defrag? Balance?

Can you show me the output of this command

# btrfs fi df /dev/md127

thanks,

Alex

[alexejCederholm]

I get this error:

root@AlexejHemma:/dev# btrfs fi df /dev/md127

ERROR: can't access '/dev/md127'

[AlexPe]

Oh man sorry, It needs to be the name of the volume,

So if "data" is the name of the volume then it will look like 

#btrfs fi df /data

[alexejCederholm]

Ohh ok, that command gives me this output:

root@AlexejHemma:/# btrfs fi df /data

Data, single: total=3.38TiB, used=3.31TiB

System, RAID1: total=32.00MiB, used=448.00KiB

System, single: total=4.00MiB, used=0.00B

Metadata, RAID1: total=4.00GiB, used=2.60GiB

[AlexPe]

Ok, can you download the logs? Send them by following this link Send Me Logs

Put in subject line: ATTN: ALEX RN104 6.2.5 to 6.4.0 error

Thanks,

Alex

[alexejCederholm]

I have just sent the logs to you Alex, thank you in advance.

[AlexPe]

Alex,

Yes thank you, I received the logs and we are working on them right now.

I will update you shortly with the next steps, be advised, this may need forward over to Netgear support to create a case for tracking.

Regards,

Alex

[AlexPe]

Hi Alex,

I'm going to PM with you instructions.

I see the mismatch, I do not see the log data from this time because of log trunction.

Alex

[anserk]

What was the fix for this? Upgrade from 6.2.5 to 6.4.0 also fails for me. In the initrd.log file I see:

Update image checksum mismatch (7d47463d9c9014d7dc3a1cd8b88d33a7/ef94c251d3c39b3da7d2b13a014adf08)!

I'm not sure where it gets these checksums as the downloaded .img file has neither of them. Also, I tried updating several times, and the second checksum in the log is always different (the first one stays intact).

Update:

I looked through the logs, and it appears the OS gets MD5 checksum from a special URL containing the following response:

name=ReadyNASOS,version=6.4.0,time=1443207354,size=63391744,md5sum=7d47463d9c9014d7dc3a1cd8b88d33a7,arch=arm,descr=ReadyNASOS Update,release_notes=http://kb.netgear.com/app/answers/detail/a_id/29938

Problem is, like I said before, the actual downloaded image has a different checksum. So either the image published on Netgear site is corrupted, or that special webpage has invalid MD5 checksum. Please fix this.

[AlexPe]

Hi Anserk,

As of right now, we are still working on the root cause. I'll post the solution once we have concluded the troubleshooting with our engineering staff.

I appreciate your patience. If you would like to log a ticket with our customer support please do so, if not we should have an update soon.

Alex

[wgrava]

Same problem here. Waiting for further instructions ...

[AlexPe]

Thank you everyone, we have retrieved some good data from alexej's machine. We could use a comparison system. If any of you're interested please pm me directly.

Thank you for your patience,

Alex

[hueykiller]

Hello what is the status? I have the same Problem?

[wgrava]

Alex, I can contribute additional info. Please let me know what I have to do. Not too savvy technically here so please be detailed. Thanks. Wilson

[alexejCederholm]

Hi,

The support team managed to solve the issue yesterday, unfortuantly I don't know how as they did it through remote connecting to the Nas. Hopefully Alex can either provide a step by step solution or do the same for you.

[anserk]

I performed USB recovery as described elsewhere on this forum, and everything is working for me now. It took only 30 minutes for the whole process including USB drive preparation.

[AlexPe · Accepted solution]

Hi Everyone,

So the issue with the Checksum error is from the BusyBox Md5sum utility. It has a bug that we are still not sure how it is occurring, we are working hard to reproduce it. We are trying to figure out why this bug is affecting some boxes and not affecting others. So there is still a lot of work to be done.

For this issue, you have some options for resolution,

1. You can retry USB boot and see if this fixes the problem, preliminary reports show that this does not fix the issue

(USB Boot Instructions)

2. I have a Debian package that you can install on your ReadyNAS OS6 ARM machine to update the device to 6.4.0 upon reboot.

(ReadyNAS OS 6: RN100/RN2120 cannot update due to invalid checksum)

3.  Create a ticket with support and have Netgear L3 group manually upgrade your device.

The Debian package will work so likely there will be no need for item three, 

Thanks again for your patience and help diagnosing this issue.

Alex

[wgrava]

Option number 2 solved the problem. Thanks.