Are these servers using local storage or a SAN?
Journaling wasn't introduced to VMFS until ESX3 so, unless you have inadvertently upgraded a shared VMFS volume, I'm not sure why ESX2.x would provide this error.
Can you post the output of fdisk -l /dev/sd*/b from the ESX2.5.2 host?
The servers are running local storage.
I ran the command you listed and I didn't get anything for a result.
Also, every time I now try to re-clone the VM or migrate the VM to the ESX 3 box, I just get an Operation Timed Out error.
Did you replace the * in the command with the letter of your VMFS volume?
Run a df to find out if it's sda,sdb...etc.
Can your 2.5.x server read the VMFS volume properly? Are the other VMs working ok?
I tried the command with a couple volumes listed. The location of our vmdk files is /vmfs/vmhba0\ :0\ :0\ :5. I also tried a volume /dev/shm to see if that would return any results, but it didn't.
I rebooted our Virtual Center server, which is VC 2.0, and now when I try to power our the machines, I just get nothing; just a black screen with the listed tasks running at the bottom saying "In Progress", yet it's been in progress for a while now.
I've also tried cloning the system again and just like with the turning it on, nothing happens; it just sits there saying "In Progress".
I tried logging in to the web interface of our ESX 2.5.2 box directly and after I put in my username and password, it never does anything; I just get the loading bar at the bottom. It never fails or succeeds. Maybe that box needs to be restarted or something; which will be a pain because it's running about 12 VM's on it. It also kinda worries me, becuase the others are production machines and if I shut them off, I hope I can start them up again.
Another strange thing that I just checked...
I restarted the VC services again and relogged into VC and it showed Disconnected from our ESX 2 server. I tried reconnecting, but the Disconnect and Reconnect options were both greyed out. I closed out VC and logged back into it and now the ESX 2 box shows connected. I then checked the status of the VM's on it and noticed that the ESX 2 box isn't reporting any statistics; not for itself or the VM's it's hosting; everything just sits at 0.
Hi modeverything I had a similar issue, with the same error message and the inability to do anything in the virtual centre console.
The problem turned out to be no available disk space on the esx servers system partitions.
I noticed this by rebooting the ESX server and seeing Filure messages during startup when mounting the partitions. THis in turn had stopped services from staring up properly.
Hope this helps
I had this exact problem on 3 x v3.0.1 servers and it was resolved just by rebooting the VC server.
Simply restarting the services might have done it, but the reboot definitely did it!
I ran into this problem. Rebooting the VCS did not resolve the problem. Since the error mentioned "journal provider" I ran the "df" command and discovered that the partition for "/var/logs" was 100% full.
After deleting old log files, the problem went away.
I just encountered the problem today. All my ESX hosts had plenty of space, but the Virtual Center server had no space left on the C drive.
Deleted some stuff and instantly fixed the problem. Didn't even need to restart the service.
.... FOUND IT ......
VMWARE ESX 3.5 Upd 1
Optimizing the servers we deleted:
- The files in the folder /var/log
- *.log of every Virtual Machine
- *.hlog of every Virtual Machine
It seems that the journal file is stored somewhere between those files and the ESX is trying to write using an unexisting file.
To solve this problem, reboot the ESX and then restart the VC Services.
We got this same error message "failed to create journal file provider" and it turned out to be because the C: drive on our VC was full.
And in my case I just created requested file by hand on ESX 3.5 U3 server