OM_SMTD .ISO Boot Files Are Corrupt as They're Currently Being Hosted (PRE-DOWNLOAD)

I downloaded the files twice and checked hashes, coming up with the same value both times:

$ md5sum OM_SMTD_710_A00_Full.iso

423585e402b2387fbd79876dfa34b5e8  OM_SMTD_710_A00_Full.iso

$ sha1sum OM_SMTD_710_A00_Full.iso

65e36eaf69f0eb72394b7c4921058f6e90a9e338  OM_SMTD_710_A00_Full.iso

$ md5sum OM_SMTD_700_A02_Full.iso

b9890a6d205e10e464514c6cd160809f  OM_SMTD_700_A02_Full.iso

$ sha1sum OM_SMTD_700_A02_Full.iso

7ae776354162c94b21c02b60b378b3a3f2761a7b  OM_SMTD_700_A02_Full.iso

Expected hashes from the download pages:

MD5: 1e55ddc6965927acbf394dfd7f466e99 OM_710_SMTD_A00_001.iso

SHA1: 78efc2a2c5cb349771ab0aebb648407a7625718d OM_710_SMTD_A00_001.iso

MD5: 55d4157cc67eea583320dfc9bb4f5fa1 OM_SMTD_700_A02_Full.iso

SHA1: c33baf91fd2b476c50b9ed42616876c6c408c09e OM_SMTD_700_A02_Full.iso

I did this twice with the same results and therefore feel fairly certain the images I downloaded are not identical to the ones that were meant to be uploaded and distributed. Different copies of these files are hosted internally to Dell vs. externally so if you still have the images you downloaded intact I would appreciate if you could generate hashes for those and post them here; if not I will try to move forward with this as-is. If you are on Windows and don't readily have a means to determine the hashes you might want to try fciv from Microsoft (support.microsoft.com/.../841290) or md5deep.sourceforge.net (3rd party tool). Once a fix is in place it will take up to 24 hours to propagate a change to all our CDNs. I will update this thread with the progress. Thanks for bringing this to our attention.

Thanks for the detailed report. I am looking into this.

I found this to be true as well.  I concatenated these two parts just now, and this created an image with a passing MD5.

That's interesting though, because I tried doing exactly the same thing yesterday (twice actually), and it didn't work either time.  The first time I downloaded the two parts and concatenated them, I got a checksum mismatch.  Then, the second time I tried, I re-downloaded both parts, concatenated them, and when I tried to calculate the checksum, it would fail.  When I say "fail", I mean that the checksum utility would crash.  So I tried 2 or 3 other hash utilities, but none of those would calculate it either.  I deleted those two pairs of part 1 and 2, so unfortunately I can't provide checksums for them.

So why did it work today and not yesterday?  Good question.. The only thing I did differently today was download parts 1 and 2 from the PowerEdge 2950's driver page instead of the PowerEdge 2900's (the model number of the server I'm servicing).  Does DELL, by chance, host multiple copies of the same filename in different logical locations on their farms?  That might explain why I obtained a different result by downloading the same two files (or what would usually be the same two files) from the driver page for a different server..

Hi Cousinit99,

Good to hear that there is no breakage on the file posted. But if you are considering that checksums (md5) are not matching (your local download against the online link) because of the checksum utility crash, then the assumption might be not right. Ideally, Ideally if your Hashcalc or check sum utility is not corrupted along with the online posted files being intact, downloaded file's check sum (md5) might not match with online file ONLY if the download is not fully successful / partial / broken. Have you by chance checked the downloaded file sizes and compared them as well with online files. You can check these too, if in case you come across these situations again. Good luck :)

Thanks

Vivek

I'm having a little trouble following you, so I'm not really sure how to respond.

All I know, is that when you perform a procedure once, you should get the same result when you perform it a second time, assuming the continuity of all factors.  I told you already, that this is not (and was not) a download corruption issue.  I would attempt to replicate the problem, but it would seem that OM 7.10 A00 has been removed from the PowerEdge 2900's list of driver downloads where I downloaded it two days ago.  The latest version listed now is 7.00 A02.  So oh well, moving on..

I too would like to know when this will be resolved. I have an R710 in which the OS crashed and I'm trying to reload it. The 7.1.0 DVD doesn't work as stated by the cousinit99 and the 6.5.0 version that came with the server is failing to work because it can't find "C:\remindpopup2.vbs".

I've updated the BIOS, RAID and network firmware since the server was purchased a year ago, so I'm assuming one of those is the contributor to 6.5.0 not working.

The R710 download page still lists revision A00 for the download, so I'd like to ask a DELL rep when it will be updated with the newer version (A02 as cousinit99 mentioned?).

Please let me know ASAP, my R710 is just sitting dead in the water the longer this drags out...

Avdf,

Can you check and attempt the download and continue with your deployment using  : OM_SMTD_710_A00_Full.iso from.

Ideally this DVD is not server specific.MD5 checksums match there.. You can utilize them as well.

Thanks

Vivek

Hi everybody,

I just wanted to update this thread to point out that SMTD 7.2 is now available. The info and link is at  the direct download link is ftp://ftp.dell.com/secure/FOLDER01100376M/1/OM_SMTD_720_A00.iso .

If you're still having trouble with 7.1 you might give this one a try. I downloaded it here and the file does not seem to be corrupt. Thanks again.

[Edited: Thanks to StarkSA for pointing out the link was bad and theflash1932 for finding the right one!]

Here it is:

ftp://ftp.dell.com/secure/FOLDER01184482M/1/OM_SMTD_720_A01.iso

2008R2 is very easy to install on a 2950 directly from the media.

The link provided to SMTD 7.2 is dead.

I am trying to restage a PowerEdge 2950 with Windows Server 2008 R2.

I've tried SMTD disks that came with various servers (so these are Dell supplied - not downloaded and burned).

Versions 6.5 Rev A00 from April 2011 and 7.0 Rev A00 from March 2012 result is the same.

In the dialogue, I have chosen to create the utility partition.

After it displays that it has created, formatted and copied files to the utility partition it reboots.

At the point after rebooting where it would normally ask to load the Windows OS disk, the message box with the Cannot find C:\remindpopup2.vbs appears.

Rick

I found that re-initializing the Virtual Disk when booting eliminates the Cannot find script C:\remindpopup2.vbs message and allows you to continue.

Now, I'm having trouble with the OS install disk throwing a message that the CD/DVD driver cannot be found.

I've never had so much trouble installing an OS, before.

Rick

"message that the CD/DVD driver cannot be found"

99 times out of 100 this means the OS media is bad ... I'd try re-downloading and/or re-burning.

if you do redownload, try using a utility that you can verify the hash value of the iso after its downloaded. This is what it should be for OM_SMTD_720_A01.iso  

MD5: 1664aa1bd59c6b33a9c7f5c47e30b697

Sha 1: a00720efc76d3aef9032ed9f657f5da9919287a9

www.dell.com/.../poweredge-2900

I use this one www.digitalvolcano.co.uk/.../md5-hash (be patient, verifying the hash can take about 5 mins....)