vivasindustries
Contributor
Contributor

Stuck at Running swapob jd start.

Hello i think i have very big problem.

Today when i try to start my server it stucks at

Starting up services
Running swapob jd start

The problem is there over 10 minutes. Can you please tell me what can i do now, why this does not want to start?

Thanks in advance!

0 Kudos
5 Replies
CarlosGonzalez
Contributor
Contributor

Hi "vivasindustries",

I'm having the same issue since we upgrade to ESXi6U2, but more than 20 mins waitting until the ESXi finish to start. First was "usbarbitrator" service (solved configuring to not to check in the startup), and now is that one.

Did you find a solution already?

Thanks in advance to all the community.

0 Kudos
CarlosGonzalez
Contributor
Contributor

HI,

Hae someone find the solution to this problem?

My servers takes more than 20/30 mins in start up.


First in "usbarbitrator service", and then in "swapob jd start". This is crazy.... just when upgrade to ESXi 6.0U2.

Hope someone can help us...

Thanks in advance!

0 Kudos
R_Brightwell
Enthusiast
Enthusiast

Getting the same issue - ESXi loading seems to hang at "Starting up services" step "Running swapob jd start".  We are on build 3620759.  Any news on a cause/fix?

0 Kudos
jason3111
Contributor
Contributor

The best thing to do, is to be patient.

The worse thing to do, is to hard shut.

You don't have to hard shutdown.

Typically, it can take 30 minutes to boot ESXi.

I have hosts with completely insane hardware resource, and some with much lower resources.

They all boot at roughly in 30 minutes.

If any host is 'stuck' at a point in boot, give it a solid 10 minutes to see if it changes.

- Jason

0 Kudos
RickyBinOKC
Contributor
Contributor

I'm going to have to respectfully disagree with a 30-minute reboot being normal.  We have SAN-booted UCS blades with 48 cores and 1TiB of memory and they normally don't take anywhere near that long to reboot.

What we finally determined to be the problem with our situation was related to having a lot of shared RDM LUNs used by clustered Windows servers that were taking a long time to interrogate while booting.  These pages were helpful: ESXi/ESX hosts with visibility to RDM LUNs being used by MSCS nodes with RDMs may take a long time t... and ESXi Slow Boot with MSCS - VMware vSphere Blog

After putting in the fix to mark the shared MSCS-clustered LUNs as perennially reserved, our servers reboot in <5 minutes from shutdown command to back-in-service.

0 Kudos