Jump to content

ODROID HC1/HC2/MC1 Buster Server img.xz checksum failure


rmh2

Recommended Posts

From https://www.armbian.com/odroid-hc1/ I have downloaded Armbian_20.05.2_Odroidxu4_buster_legacy_4.14.180.img.xz on several different machines and internet connections and done a checksum verification using several different utilities and there is always a mismatch.  Armbian_20.05.1_Odroidxu4_buster_legacy_4.14.180.img.xz.sha says the SHA-256 checksum should be

 

   DDAF33314FAE4515E047702257CCA93CC0C088D73F81118EA8CE6911E89210EB

 

but the checksum utilities always report

 

   E8E31E653798EBC0FFCE9205A6D7BD625EA58F8728339E4D04604A002D737DEE

 

I downloaded Armbian_20.05.2_Odroidxu4_focal_current_5.4.41.img.xz (which doesn't work with the OMV install script by Ryecoaaron) and its checksum is correct.  Is the DDAF..10EB checksum really correct?

 

EDIT:

I can't reply because I only get one post per day (really?) and apparently it hasn't been 24 hours yet.  Gaa.

 

Thanks for the quick response; appreciated as always.

 

It looks like the two SHA-256 Buster checksums from the main odroid-hc1/ page have now been removed, and the archive/ checksum you linked to has the checksum reported by the utilities.  So the answer to my "is the DDAF..10EB" checksum really correct?" question is "No, E8E3..7DEE is the correct checksum."  Correct?

Edited by rmh2
cannot reply to reply
Link to comment
Share on other sites

Link to comment
Share on other sites

Repeat from edit:

 

It looks like the two SHA-256 Buster checksums from the main odroid-hc1/ page have now been removed, and the archive/ checksum you linked to has the checksum reported by the utilities.  So the answer to my "is the DDAF..10EB" checksum really correct?" question is "No, E8E3..7DEE is the correct checksum."  Correct?

Link to comment
Share on other sites

Guest
This topic is now closed to further replies.
×
×
  • Create New...

Important Information

Terms of Use - Privacy Policy - Guidelines