![]() | |
![]() |
| | Thread Tools | Display Modes |
#1
| |||
| |||
|
#2
| |||
| |||
|
|
I have a 2 node sql 2005 cluster (64 bit ent edition) running on Windows Server 2003 (64 bit ent edition) utilizing an HP iscsi storage array. I recently became aware of the disk alignment issues with sans and wanted to test reconfiguring one of the shared drives. I picked a drive owned by node 1 and did the following: 1 - Deleted the physical drive resource from the cluster 2 - Ran diskpart on node 1, deleting the existing partition, created a new partition using align=64 3 - Using Disk Management I formatted the partition using 64k and assigned it the same drive letter it had formerly 4 - Added it back to the cluster as a disk resource All good up to this point. Problem is, I cannot fail over this drive to the other node (and this used to work). Running disk management on the other node, I can see the drive but it has no drive letter and I cannot assign it one. I've obviously missed a step but not sure which one, any help is appreciated.... |
#3
| |||
| |||
|
|
You probably need to reboot the second node. It didn't follow along with the changes. You can try a rescan of the disks on node 2 first, but I doubt that will help. -- Geoff N. Hiten Principal SQL Infrastructure Consultant Microsoft SQL Server MVP "JayInNC" <JayInNC (AT) discussions (DOT) microsoft.com> wrote in message news:30513CBF-8377-46B6-9076-C116401B7C8F (AT) microsoft (DOT) com... I have a 2 node sql 2005 cluster (64 bit ent edition) running on Windows Server 2003 (64 bit ent edition) utilizing an HP iscsi storage array. I recently became aware of the disk alignment issues with sans and wanted to test reconfiguring one of the shared drives. I picked a drive owned by node 1 and did the following: 1 - Deleted the physical drive resource from the cluster 2 - Ran diskpart on node 1, deleting the existing partition, created a new partition using align=64 3 - Using Disk Management I formatted the partition using 64k and assigned it the same drive letter it had formerly 4 - Added it back to the cluster as a disk resource All good up to this point. Problem is, I cannot fail over this drive to the other node (and this used to work). Running disk management on the other node, I can see the drive but it has no drive letter and I cannot assign it one. I've obviously missed a step but not sure which one, any help is appreciated.... |
![]() |
| Thread Tools | |
| Display Modes | |
| |