[Webinar] Streamline your web hosting managementRegister Today

  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 692
  • Last Modified:

Post Install MINGETTY Error

Hello all, we were evaluating ESX 3.02 and had the system all set up but a week later went to 3.5. Immediately following install (using default options) we get an error that says INIT: Id "1" cannot execute /sbin/mingetty; respawning too fast: disabled for 5 minutes. This will just loop continuously and won't allow the system to finish coming up. I am able to boot into troubleshooting mode so am not sure what the issue could be. I also tried a clean install of the OS and still no luck. All the hardware is on the HCL so I think that can be ruled out. I performed a memory test (was suggested that may be an issue) but after running memtest86 it found no errors. Than I tried removing 1 of the 2 dimms at a time and still no luck. Any ideas would be appreciated, thanks!
  • 2
1 Solution
Watch this topic on the vmware communities (http://communities.vmware.com/message/851252). It can be the same problem with eventually maybe a solution.
Just got an email of vmware, they have a new build because of issues in upgrading:

Alert: possible upgrade issue when upgrading from ESX Server 3.0.1/3.0.2 to ESX Server 3.5
Products affected:

VMware ESX Server 3.5


VMware identified a possible upgrade issue when upgrading from ESX Server 3.0.1/3.0.2 to ESX Server 3.5.
To prevent the problem a new build of ESX Server 3.5 has been posted on the Virtual Infrastructure 3
download page[http://www.vmware.com/download/vi/].

Before upgrading to ESX Server 3.5 from ESX Server 3.0.1 or 3.0.2, please download the new build and
ensure the ESX Server 3.5 ISO or upgrade tarball to which you are upgrading has release date of 2/16/08
instead of 12/10/07.

Upgrades to ESX Server 3.5 with release date 12/10/07 from ESX Server 3.0.1 or 3.0.2 may require manual
RPM installation as described in KB 1003801.

If you have any questions, please contact support at 877-4-VMWARE.

MardukLitzerAuthor Commented:
bleeuwen, thanks for your responses.. After monitoring the sequence a little further and looking at some of the logs, I saw something related to USB-OHCI or something like that and decided to go into the BIOS and disabled USB support... It worked fine and the system boots up fine now, thanks so much!

Featured Post

Keep up with what's happening at Experts Exchange!

Sign up to receive Decoded, a new monthly digest with product updates, feature release info, continuing education opportunities, and more.

  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now