Windows server 2003 scsi disk

Join Us Close. Join Tek-Tips Forums! Join Us! By joining you are opting in to receive e-mail. Promoting, selling, recruiting, coursework and thesis posting is forbidden. Students Click Here. Create a copy of the Windows XP Setup boot disk by using the diskcopy command, and then delete all files on the new disk. Copy the Ntdetect. Active 9 years, 4 months ago. Viewed times. Improve this question. Add a comment.

Active Oldest Votes. Once copied, reboot and let plug-and-pray do the work Improve this answer. Simon Catlin Simon Catlin 5, 3 3 gold badges 16 16 silver badges 20 20 bronze badges. Seems this is not sufficient. I looked into the driver manager to see which files are used. They already are present in the target disk, exact same content, byte to byte. Can you post the exact wording of the error - I'm interested to know if it's NTLDR problem or an inaccessible boot device stop screen.

Have you been able to boot into the recovery console and see the contents of the HDD? Can you post your BOOT. INI file? Part of that data was on iSCSI disks. I mounted these disks as "folders" on an existing physical drive on the server through Disk Management. I don't want to "logoff the target" because I've presented several disks through this one iSCSI target and some of them are still alive and in use..

Then you can disconnect from the Initiator. I think the taking those disks in particular "offline" is what I want to do skip the disconnect from the initiator right now. Anybody done this? The Computer Hero is an IT service provider. Yes Dan, this is what you want to do, disconnect them. There is no need to mess with the iscsi initiator on the box as you are decommission the server anyway. FYI you should always have the iscsi drive connected to 2 or more server with all but 1 of them disconnected, this way if a server goes down, you can right click and connect the drive to a different server.

The request is passed from the cluster disk driver to the Microsoft storage driver stack and finally to the driver specific to the HBA that communicates to the disks. It may also be passed to any multipath software running in the storage stack.

Once the disk has passed all of these tests, the disk resource is marked as online and the cluster service then continues to bring all other resources online. Each node in the cluster renews reservations for any LUNs it owns every three seconds. If the nodes of a cluster lose network communication with each other for example, if there is no communication over the private or public network , the nodes begin a process known as arbitration to determine ownership of the quorum disk.

The node that wins ownership of the quorum disk resources in total communication loss between cluster node will remain functional. Any nodes that cannot communicate and cannot maintain or acquire ownership of the quorum disk will terminate the cluster service and any resources that node was hosting will be moved to another node in the cluster.

The node that currently owns the quorum disk is the defending node. The defender assumes that it is defending against any cluster nodes that it cannot communicate with and for which it did not receive a shutdown notification.

All other nodes nodes that do not own the quorum disk and cannot communicate with the node that owns the quorum resource become challenging nodes. When the challenger detects the loss of all communications, it immediately requests a bus-wide SCSI reset to break any existing reservations.