Software-based VM-centric and flash-friendly VM storage + free version
Moderators: anton (staff), art (staff), Max (staff), Anatoly (staff)
-
galonga
- Posts: 33
- Joined: Tue Nov 27, 2007 10:02 pm
Thu May 01, 2008 7:52 pm
Hi folks
We´ve been having a real problem when trying to remove a SCSI device from an initiator using starport. More than often the initiator just crashes with a beautiful blue screen.
Also, if for some reason we have to reboot the initiator, the volume gets corrupted to the point of having to rebuild it (we tried with several volume flavors to the same result).
The initiator is running 2003 with SP2 on a dual core with 2 Gb RAM. The target is an old K6 with 544 RAM attached to an old IBM XP15 with 7 HDs. Starport version is 3.5.4 build 0x20080111. Starwind is 3.5.3 build 20080229
Any ideas?
-
anton (staff)
- Site Admin
- Posts: 4021
- Joined: Fri Jun 18, 2004 12:03 am
- Location: British Virgin Islands
-
Contact:
Fri May 02, 2008 12:03 am
Need to have both StarWind and StarPort logs. Initiator should not BSOD in any case... Do you have any third-party drivers from Veritas, Symantec etc software?
galonga wrote:Hi folks
We´ve been having a real problem when trying to remove a SCSI device from an initiator using starport. More than often the initiator just crashes with a beautiful blue screen.
Also, if for some reason we have to reboot the initiator, the volume gets corrupted to the point of having to rebuild it (we tried with several volume flavors to the same result).
The initiator is running 2003 with SP2 on a dual core with 2 Gb RAM. The target is an old K6 with 544 RAM attached to an old IBM XP15 with 7 HDs. Starport version is 3.5.4 build 0x20080111. Starwind is 3.5.3 build 20080229
Any ideas?
Regards,
Anton Kolomyeytsev
Chief Technology Officer & Chief Architect, StarWind Software
