Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Checksum fail #7

Closed
themichaelbender opened this issue Oct 4, 2016 · 7 comments
Closed

Checksum fail #7

themichaelbender opened this issue Oct 4, 2016 · 7 comments

Comments

@themichaelbender
Copy link

With the current script using TP5, the checksums are failing during setup-lab.ps1. It appears they don't match. I've run through this twice with the same outcome.

VERBOSE: [7:54:27 PM] Calculating resource 'C:\Lability\ISOs\2016TP5_x64_EN.iso.checksum' checksum.
VERBOSE: [7:54:40 PM] Writing checksum '4D46EC27EA02B3255B2D6738241F71DB' to resource 'C:\Lability\ISOs\2016TP5_x64_EN.iso.checksum'.
VERBOSE: [7:54:40 PM] Resource 'C:\Lability\ISOs\2016TP5_x64_EN.iso' checksum does not match '6417BA460F95BD91DED05DFACD553783'.
Web resource 'http://care.dlservice.microsoft.com/dl/download/8/9/2/89284B3B-BA51-49C8-90F8-59C0A58D0E70/14300.1000.160324-1723.RS1_RELEASE_SVC_S
ERVER_OEMRET_X64FRE_EN-US.ISO' download failed.
At C:\Program Files\WindowsPowerShell\Modules\Lability\0.10.0\Lib\Resource.ps1:256 char:13

@theJasonHelmick
Copy link
Contributor

Checking into this --

@jdhitsolutions
Copy link
Collaborator

Is it possible the source ISOs have changed and the checksums are now wrong? Does the ISO download and can you use it? If so, then the checksum is merely an "accounting" problem.

@themichaelbender
Copy link
Author

If there was an optional to accept different hashes and move on, that would be great.

The ISO downloads and is useable.

@theJasonHelmick
Copy link
Contributor

Michael, I think I have discovered this issue, but it would help if you could confirm a few things. First, is the message your seeing after the download in Yellow or Red?
screen shot 2016-10-09 at 5 26 07 pm
If yellow as in the image, thats not an error -- it is a test that failed that prompted the download.

I believe what is happening is that after the download the script hangs -- but if you hit the return key it will continue. I will track this with the lability guys.

@themichaelbender
Copy link
Author

Appears to work now. Previous runs had no 'Press Enter' and script broke. Gremlins.

@theJasonHelmick
Copy link
Contributor

There is no 'Press Enter' -- its a bug in either PowerShell or Lability -- so I'm checking with the lability guys. I've had this happen with regular PowerShell scripts and long running processes -- so I'm half thinking its PowerShell and there is nothing I can do about that -- except warn students in the ReadMe.md and message that displays before the download begins. I've already changed those to reflect this possibility -- but I will report back here when I find out more. Thanks for the help!

@themichaelbender
Copy link
Author

The only thing I received this pass was another 'Press R to run once' prompt. Seemed to work this time. Will check later today. Thanks.

theJasonHelmick pushed a commit that referenced this issue Nov 4, 2016
pull bot pushed a commit to bruto001/PS-AutoLab-Env that referenced this issue Mar 4, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants