Page 1 of 1
Error with VMware Server 1.0.5
Posted: Tue Apr 08, 2008 7:29 am
by eal
StarWind 3.5.3 publishes a 500 GB SATA disk which is attached to a Windows XP box running VMware Server 1.0.5 using the MS iSCSI Initiator 2.0.6.
I copied a test VM folder from the local disk to the iSCSI volume, added the VM to the VMware catalog and started it. I received a bunch of errors like this one
http://fitb.eu/download/vmware-server-error.html.
I could complete the bootstrap only if I selected "Continue" to forward the error to the guest.
What could it be?
Posted: Fri Apr 11, 2008 7:31 am
by Bohdan (staff)
Hello.
I hope you haven't exported your system disk via iSCSI.
Have you used DiskBridge or SPTI functionality to export your disk?
Anyway please zip and send us logs from StarWind installation directory. With the logs we can find the reason of the error. Thanks!
Posted: Fri Apr 11, 2008 7:54 am
by eal
bohdan (staff) wrote:Hello.
I hope you haven't exported your system disk via iSCSI.
No, the system disk is a PATA 80 GB disk and I created a 16 GB partition for installing Windows XP Pro 32-bit and StarWind 3.5.3. Rest of disk is unused.
Disk published by StarWind is a single independent SATA 500 GB disk.
bohdan (staff) wrote:Have you used DiskBridge or SPTI functionality to export your disk?
SPTI was used to create the iSCSI device associated to the local SATA 500 GB disk.
bohdan (staff) wrote:Anyway please zip and send us logs from StarWind installation directory. With the logs we can find the reason of the error. Thanks!
I will do it asap. Thank you.
Posted: Fri Apr 11, 2008 8:37 am
by Bohdan (staff)
Do not use SPTI for disk exporting. It is slow and designed mainly for burners. Please use DiskBridge instead.
Disk Bridge module does complete emulation of the SCSI layer that allows any type of hard drives (PATA/SATA/RAID) to be used by remote initiator clients.
Posted: Wed Apr 23, 2008 6:48 am
by eal
bohdan (staff) wrote:Do not use SPTI for disk exporting. It is slow and designed mainly for burners. Please use DiskBridge instead.
Disk Bridge module does complete emulation of the SCSI layer that allows any type of hard drives (PATA/SATA/RAID) to be used by remote initiator clients.
Thanks Bohdan. I re-exported the physical volume using Disk Bridge and errors disappeared.
Posted: Wed Apr 23, 2008 8:11 am
by Bohdan (staff)
Good.
