We had system kinda crash with these error and then we had to bring it up some how by system repair.
This is a Windows Server 2003 as we are yet to move out. We are running VMware 6.5 on a Cisco Hyperflex system.
The device, \Device\Scsi\symmpi1, is not ready for access yet.
The driver detected a controller error on \Device\Harddisk0.
The device, \Device\Scsi\symmpi1, is not ready for access yet.
The driver detected a controller error on \Device\Harddisk0.
The device, \Device\Scsi\symmpi1, is not ready for access yet.
The driver detected a controller error on \Device\Harddisk0.
The device, \Device\Scsi\symmpi1, is not ready for access yet.
The driver detected a controller error on \Device\Harddisk0.
The device, \Device\Scsi\symmpi1, is not ready for access yet.
The driver detected a controller error on \Device\Harddisk0.
The device, \Device\Scsi\symmpi1, is not ready for access yet.
The driver detected a controller error on \Device\Harddisk0.
The device, \Device\Scsi\symmpi1, is not ready for access yet.
The driver detected a controller error on \Device\Harddisk0.
Where exactly are you seeing those errors?
This error is on one of Win2K3 server system log
If the "system crash" was within Windows itself, and these are Windows log messages, you might be better off seeking assistance on a Microsoft user forum such as:
I'll move this thread to the Windows guest area of VMTN but leave it active for others to see in case they can help.