Solved

SBS 2008 on ESXi unexpected shutdown

Posted on 2009-07-01
7
1,395 Views
Last Modified: 2012-05-07
Hi all,

We had some unexpected shutdown's on our SBS 2008 running on ESXi.
We have following warning in the event viewer:
The driver has detected that device \Device\RaidPort0 has old or out-of-date firmware. Reduced performance may result.

Does anyone know the reason of this error en how to fix it?

Thx in advance
Robby
0
Comment
Question by:techneitsolutions
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
7 Comments
 
LVL 9

Expert Comment

by:drequinox
ID: 24755458
this error probably cannot really cause a reboot, but in order to fix the error.
If you are using SAN , contact the vendor and find out the latest firmware for you HBA cards. this should fix the issue.
even if not using SAN then check your harddisk controller , its make and model and contact the vendor to provide you the latest firmware.
0
 
LVL 6

Expert Comment

by:davismisbehavis
ID: 24758023
What version of ESX are you running and what kind of vSCSI adapter are you using on the SBS virtual machine?  I am presuming the errors are in the Windows event logs so the issue is with the C: drive of the SBS server

What hardware version is the VM on,  this should be displayed in the top right hand corner when you open the settings of the machine.

Vmware uses emulation to ensure compatibility for VM's,  i.e emulating old hardware to ensure maximum compatibility,  It's interesting that SBS has picked this up that it's old firmware,  almost as if it has spotted that vmware is using older adapters to ensure compatibility.

Just out of interest is SBS 2008 supported on virtual platforms by Microsoft?
0
 

Author Comment

by:techneitsolutions
ID: 24761128
@ drequinox: we do not use SAN, the server is installed on a HP server with intern RAID 5 controller.

@ davismisbehavis: The version of ESXi is 3.5 and the vSVSI adapter is LSI Logic.
the VM Version is 4.

The server did crash 5 minutes ago and we had a blue screen with following error:
BAD_POOL_CALLER

any suggestion?
Robby
0
Efficient way to get backups off site to Azure

This user guide provides instructions on how to deploy and configure both a StoneFly Scale Out NAS Enterprise Cloud Drive virtual machine and Veeam Cloud Connect in the Microsoft Azure Cloud.

 

Author Comment

by:techneitsolutions
ID: 24762439
In attachement, I added a screenshot of the blue screen.

It's the second time it happened today.

Anyone an idea was may cause this?


bluescreen-server.JPG
0
 

Expert Comment

by:smaguire
ID: 24813431
its an ongoing issue between Microsoft and VMWare, We are getting the same problem except we are using Windows Server 2008 with Dell SAN & ESXi 3.5.
The following link suggests upgrading to ESXi 4 should fix the problem, I am still doing a lot of investigation, but at the end we will have to upgrade our SAN firmware and ESXi 3.5 to the latest.
here is the link:
http://communities.vmware.com/message/1287105
 
0
 

Author Comment

by:techneitsolutions
ID: 25393251
i upgradet to esxi 4.0 but the problem is still not solved. The sbs still crashes ...
0
 

Accepted Solution

by:
techneitsolutions earned 0 total points
ID: 25895654
no solution to this.

We upgrade to w2008 and we have no problem anymore
0

Featured Post

Technology Partners: We Want Your Opinion!

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Suggested Solutions

HOW TO: Connect to the VMware vSphere Hypervisor 6.5 (ESXi 6.5) using the vSphere (HTML5 Web) Host Client 6.5, and perform a simple configuration task of adding a new VMFS 6 datastore.
When rebooting a vCenters 6.0 and try to connect using vSphere Client we get this issue "Invalid URL: The hostname could not parsed." When we get this error we need to do some changes in the vCenter advanced settings to fix the issue.
Teach the user how to edit .vmx files to add advanced configuration options Open vSphere Web Client: Edit Settings for a VM: Choose VM Options -> Advanced: Add Configuration Parameters:
This Micro Tutorial steps you through the configuration steps to configure your ESXi host Management Network settings and test the management network, ensure the host is recognized by the DNS Server, configure a new password, and the troubleshooting…

756 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question