Server 2012 - Partition Issues
-
I have not seen a span in a very long time, but that might be what it looks like.
-
@aaronstuder said in Server 2012 - Partition Issues:
@scottalanmiller said in Server 2012 - Partition Issues:
Maybe you did a span by accident?
No, I right clicked on the 836.05 GB Partition and Clicked "Extend Volume" then told it to use the unallocated space.
Did you delete the other one first?
-
@scottalanmiller said in Server 2012 - Partition Issues:
Did you delete the other one first?
Yes, that's how I had unallocated space
-
@Reid-Cooper said in Server 2012 - Partition Issues:
I have not seen a span in a very long time, but that might be what it looks like.
I have, and that is indeed what it looks like.
-
Kill it with fire
-
So it seems like I have multiple regions of the same disk that are linked together
How come I feel bad about this?
-
@aaronstuder said in Server 2012 - Partition Issues:
So it seems like I have multiple regions of the same disk that are linked together
How come I feel bad about this?
That is what is looks like. And that would be a span. But how it got there, no idea.
-
@aaronstuder said in Server 2012 - Partition Issues:
@scottalanmiller said in Server 2012 - Partition Issues:
Did you delete the other one first?
Yes, that's how I had unallocated space
You deleted all partitions there or just some?
-
@dafyre said in Server 2012 - Partition Issues:
@Reid-Cooper said in Server 2012 - Partition Issues:
I have not seen a span in a very long time, but that might be what it looks like.
I have, and that is indeed what it looks like.
That's what I was thinking.
-
@scottalanmiller Just the 63.95GB one.
-
@aaronstuder said in Server 2012 - Partition Issues:
@scottalanmiller Just the 63.95GB one.
That's the only one deleted, or left?
-
@scottalanmiller deleted.
-
@aaronstuder said in Server 2012 - Partition Issues:
@scottalanmiller deleted.
I wonder if that failed somehow.
-
Part of the problem is the free space was on the front of the drive, so it couldn't really extend the drive...
-
I was hoping it was smart, and could just extend out to the front of the front, but clearly not
-
So I am thinking this is the only way to fix this:
- Add a third drive in VMware, thin provisioned , 1TB.
- Make it E: or whatever.
- Copy folders one by one from *D: to E:
I don't think I want to keep the data on this drive (spanned, or whatever it is)
-
@aaronstuder said in Server 2012 - Partition Issues:
Part of the problem is the free space was on the front of the drive, so it couldn't really extend the drive...
Oh right, of course, I knew that that was an issue but didn't think about it. It can't do that because of the ToC. So it had to span instead of traditional extension.
-
@aaronstuder said in Server 2012 - Partition Issues:
So I am thinking this is the only way to fix this:
- Add a third drive in VMware, thin partitioned, 1TB.
- Make it E: or whatever.
- Copy folders one by one from *D: to E:
I don't think I want to keep the data on this drive (spanned, or whatever it is)
It's not THAT bad. Ideal? No. Horrible? No.
-
@aaronstuder said in Server 2012 - Partition Issues:
I was hoping it was smart, and could just extend out to the front of the front, but clearly not
That's a big ask for Microsoft's disk management
-
This really isn't that big a deal. It's one of the reason LVM (and by extension Dynamic Volumes) exists. Does it look pretty in Disk Manager? No. Does it affect the functionality or use of the drive? No.
