I am having a problem with the microsoft isci initiator on windows 2003 server. I had a vitual storage switch lose a backend scsi controller connnection to a scsi sata array. The result was that I lost all targets that were attached to the the defined LUN/controller port on the array.
I have managed to find a work around in order to be able to once again expose all luns and associated targets, and hence have all iscsi targets available. However, what I am finding, is that the server that was previoulsy attached to the lost targets, is unable to read the boot record, and ascertain the drive details. As far as it is concerned, it is a completely new volume ready to be formated (RAW). Whowever this is noty the case. I am able to attach to all drives that are behaving in this manner on a completely different server, and browse the volumes normally.
I have gone as far as unexposing the targets on the iscsi switch, and renaming the targets, attaching them to the server....but the same issue results. These new target are still unreadable.
I have re-installed the iscsi initiator... but the same results
So, if anyone can provide some words of wisdom, I would appreciate it.