(1949) Bug Report: Console will not restart after install of new build

Update. If I try to restart holding the PIG key. I then try to select any of those options it satys there and stuck in that menu for eternity.

Full console lock-up, no response to any keystrokes. Have to manually switch off the console.

Sounds like the console is having trouble finding the Wholehog application on the disc. Have you tried powercycling a couple of times?

I'd say this is either the sign of a bad hard drive or corrupt data on the disc. If it is the latter you can try imaging the hard drive using the .iso from the web.

I have cycled through several times.

Would that explain why it would not even access Console Test? Doesn't that work outside the Wholehog application.

If it is the harddrive. That is going to be the 2nd replacement in 3 years. Does that sound right for a console that does not take many hard hits. It was working fine no indications of problems. Install new buid and issues. Seems fishy.

So I was finally able to get the drive to degrade back to 1932. Believe that something weird happened when I upgraded tyo 1949. Think I will stick with 1932 for now. Any thoughts? The Harddrive appears to be working fine in 1932. Should I try to re install 1949? Do you think the build is solid or should I skip it?

I was able to upgrade three consoles from 2.3.1 to 2.3.2 using the FPSPKG here in the test lab and they all boot under 60s on each try. Perhaps it is related to the number of show files previously on the disk or related to the upgrade cycles you went through (i.e. not having used an ISO for the last couple of upgrades) We feel 2.3.2 is a stable build, but it might be neccessary in some cases to back up your show files and do a complete image install on the desk to insure that the entire package is being installed correctly. I am still looking into this boot time issue and seeing what particular scenarios might cause such a long/failed boot after upgrade.

You are correct that I have been doing upgrades for a number of builds. I did a full install of build 1932 and upgrade to 1949 on two different drives, one is a back-up. Will let this ride and see if I have anymore issues.

Thanks for your support.

Spoke to soon. So I did a full install of 2.3.1. Then upgraded to 2.3.2. Did a full cycle down. Restarted the console same original issue.

So I tried to do an full install of 2.3.2 from the disk and it would not allow me to to a clean install of 2.3.2. I had to get back to 2.3.1 before I could do a clean install of 2.3.2. It would not let me overwrite the upgrade of 2.3.2. Currently I am cycling down to see if I get an error again. Does this seem odd that I am seeing all of this? Should I be wary of some total failure of my console.

These tests have been tried on two different drives.

Thanks.

Done testing. 2.3.2 will not boot up after a power down locks in the splash screen showing bios info Have gone back to 2.3.1. It starts up everytime.

Just turned on our 3rd console that we had upgraded to 2.3.2 yesterday. Has the same locked splash screens. We are installing 2.3.1 currently. So it appears that this build has problems. Seems that it should be seriously looked at.

We can help with this, if you tell us what to look for, if you are not able to reproduce this in the shop.

Thanks.

Joshua,

We are currently looking into this problem as a top priority. Right now it appears that the ISO image can sometimes cause the console to either not reboot or to reboot very slow (>7 min). However we have found that if you use an FPSPKG to upgrade this problem does not occur.

Also right now there is no major reason to upgrade a Wholehog 3 console from 2.3.1 to 2.3.2 as the changes in 2.3.2 were mainly bug fixes related to PC products. However I understand the desire to be on the current release.

We hope to have a resolution to this installation problem ASAP.

thanks for your patience,

Thanks Brad. I should have picked up the fact that Chris was upgrading using the FPSPKG method. We will stick with 2.3.1.

Thanks again for the support with this issue.