aguenPremium
join:2003-07-16
Grants Pass, OR | reply to DarkLogix
Re: [WIN7] Expanding a partition in win7 I believe you select the block size at time of format. The default size is 512. There is a drop down where you can select the size. |
|
 DarkLogixTexan and ProudPremium
join:2008-10-23
Baytown, TX
kudos:3 | Ya but any way to check what it is after the fact?
I've found the info on how, so I'll do that first.
And set it to 4k because that's what the cool kids are doing j/k but really because it'll mean that I won't have to worry about it as at 4k it's move the limit to 16TB and even if I put 4x 4TB drives in (the max that current drive availability would allow) with raid 5 I still wouldn't hit 16TB with this unit.
fsutil fsinfo ntfsinfo c: |
|
DarkLogixTexan and ProudPremium
join:2008-10-23
Baytown, TX
kudos:3 | Heres a screen capture of the command output |
|
|
|
aguenPremium
join:2003-07-16
Grants Pass, OR Reviews:
 ·Callcentric
 ·Verizon FiOS
| reply to DarkLogix
Based on what was displayed, specifically the "Bytes Per Physical Sector" you should apply this "optional" KB patch
»www.microsoft.com/en-us/download···id=12248
I'm not saying it will fix your particular issue but it can't hurt. It's basically just an updated ntfsutil.exe |
|
DarkLogixTexan and ProudPremium
join:2008-10-23
Baytown, TX
kudos:3 | well I tried but the WGA thing is bugged.
it says the version that downloads is no longer supported. |
|
DarkLogixTexan and ProudPremium
join:2008-10-23
Baytown, TX
kudos:3 | Because I said I would heres a print screen of the disk manager
for a fix what I'm doing is using my server to copy all the data from the 1st LUN to a 2ND lun (one perk of thin provisioning)
I made sure to select allocation unit size of 4096 and it didn't have any trouble making a 4TB partition (or well 3.5, I rounded it down from 3.6 because as you know a 2TB drive is not quite 2TB and the differance adds up |
|
DarkLogixTexan and ProudPremium
join:2008-10-23
Baytown, TX
kudos:3 | reply to aguen
said by aguen:Based on what was displayed, specifically the "Bytes Per Physical Sector" you should apply this "optional" KB patch
»www.microsoft.com/en-us/download···id=12248
I'm not saying it will fix your particular issue but it can't hurt. It's basically just an updated ntfsutil.exe
Well finally got the KB downloaded but my computer says already installed |
|
aguenPremium
join:2003-07-16
Grants Pass, OR Reviews:
·Callcentric
·Verizon FiOS
| reply to DarkLogix
I gotta tell ya, the fact that your using iSCSI to connect to the NAS is a complicating factor here. Because of this, the disk driver currently installed on your PC that handles your internal drive(s) is the one that's trying to manage these particular volumes. If you haven't already tried it, try running that same command on the new volume you added and see if it gives the same response for the "Bytes per Physical Sector". If it does, then I'd have to say your just SOL. If it gives back a value of 4096, then I's say it's an issue with the way that first volume was initially created and there is no way you can fix it within your PC.
Lastly, if you still want to push it, try giving a shout out to koitsu  , he may have more ideas. |
|
DarkLogixTexan and ProudPremium
join:2008-10-23
Baytown, TX
kudos:3 | It gives the same message but as seen in the screen shot the new volume is able to be formatted, I think its just a matter of the alocation unit size that was auto selected when the volume had been 2tb.
So I'm in the process of copying data from the 1st volume to the 2nd
just couldn't expand the 1st partition |
|
