A
Anthony J. Biacco
Guest
Hi,
I've got a brand new install of Windows Server 2003 Enterprise Edition
w/SP2 on a Dell PowerEdge 860 with 2 500GB SATA drives in a RAID1
configuration on a Dell SAS 5iR controller.
I installed the OS on a 25GB NTFS partition. No problem.
I then tried to create a new 25GB partition out of the unallocated
space (basic disk, NTFS, default allocation unit size). LDM
hourglassed for a minute, then came back with "The operation did not
complete. Check the System Log for more information on the error". No
messages were in the log. The volume shows as allocated, but not
formatted or assigned its drive letter. If i try to format after the
fact, I get a "The format did not complete successfully" error. The
only way to get it to work is to reboot the server after the
allocation, then format after the reboot. Then it will be successfull.
I've also tried this as a dynamic disk instead of basic. Same results.
I found a KB article (826823) describing a related problem but
microsoft says it was included in SP2, and i can confirm the modified
files i have are newer than the patched ones.
Any help is solving this problem is appreciated.
-Tony
I've got a brand new install of Windows Server 2003 Enterprise Edition
w/SP2 on a Dell PowerEdge 860 with 2 500GB SATA drives in a RAID1
configuration on a Dell SAS 5iR controller.
I installed the OS on a 25GB NTFS partition. No problem.
I then tried to create a new 25GB partition out of the unallocated
space (basic disk, NTFS, default allocation unit size). LDM
hourglassed for a minute, then came back with "The operation did not
complete. Check the System Log for more information on the error". No
messages were in the log. The volume shows as allocated, but not
formatted or assigned its drive letter. If i try to format after the
fact, I get a "The format did not complete successfully" error. The
only way to get it to work is to reboot the server after the
allocation, then format after the reboot. Then it will be successfull.
I've also tried this as a dynamic disk instead of basic. Same results.
I found a KB article (826823) describing a related problem but
microsoft says it was included in SP2, and i can confirm the modified
files i have are newer than the patched ones.
Any help is solving this problem is appreciated.
-Tony