New drive/volume problem on Server 2003

[Guest polastine]

I'm running Server 2003 Std. SP2 (fully up to date). I had an 130GB IDE

HDD (letter D:) that I replaced with a 1TB (that's terabyte) SATA drive.

After hooking it up, it showed up as the G: drive, with space reported

correctly.

 

Then I used a tool called SelfImage (highly recommended BTW) to mirror

the entire IDE disk on to the SATA one. When that was over, I went into

the logical volume manager, deleted the old letter assignment (D:), the

new drive's letter assignment (G:) and rebooted.

 

When Windows came up again, I went into the volume manager and assigned

the letter D: to the 1GB SATA volume. That went great, except that now

Windows Explorer thinks it's still seeing the 130GB IDE drive, which is

obviously incorrect. The volume manager correctly reports the full

(healthy) 1TB primary partition, it's just Explorer that claims I'm

running out of disk space on it, and in fact tells me there's only 10MB

left and won't let me get past 130GB.

 

I *have* to use the D: letter on this volume, I have tons of paths,

shortcuts and installations that point to the drive.

 

Is there some sort of volume cache or something that's causing this, and

how can I fix it?

 

Thanks in advance, this is driving me crazy.

[Guest Pegasus \(MVP\)]

Re: New drive/volume problem on Server 2003

 

 

"polastine" <noone@example.com> wrote in message

news:OFQiHBsJJHA.5704@TK2MSFTNGP02.phx.gbl...

> I'm running Server 2003 Std. SP2 (fully up to date). I had an 130GB IDE

> HDD (letter D:) that I replaced with a 1TB (that's terabyte) SATA drive.

> After hooking it up, it showed up as the G: drive, with space reported

> correctly.

>

> Then I used a tool called SelfImage (highly recommended BTW) to mirror the

> entire IDE disk on to the SATA one. When that was over, I went into the

> logical volume manager, deleted the old letter assignment (D:), the new

> drive's letter assignment (G:) and rebooted.

>

> When Windows came up again, I went into the volume manager and assigned

> the letter D: to the 1GB SATA volume. That went great, except that now

> Windows Explorer thinks it's still seeing the 130GB IDE drive, which is

> obviously incorrect. The volume manager correctly reports the full

> (healthy) 1TB primary partition, it's just Explorer that claims I'm

> running out of disk space on it, and in fact tells me there's only 10MB

> left and won't let me get past 130GB.

>

> I *have* to use the D: letter on this volume, I have tons of paths,

> shortcuts and installations that point to the drive.

>

> Is there some sort of volume cache or something that's causing this, and

> how can I fix it?

>

> Thanks in advance, this is driving me crazy.

 

I think that SelfImage left some of the partition table settings at the

values that were valid for the 130 GByte disk. I have seen similar problems

with other imaging products.

[Guest polastine]

Re: New drive/volume problem on Server 2003

 

 

 

Pegasus (MVP) wrote:

> I think that SelfImage left some of the partition table settings at the

> values that were valid for the 130 GByte disk. I have seen similar problems

> with other imaging products.

 

I guess that's possible. Is there any way to fix it?

 

Thanks

[Guest Edwin vMierlo [MVP]]

Re: New drive/volume problem on Server 2003

 

you can try this http://support.microsoft.com/kb/832316

 

and use the "extend filesystem"

 

 

"polastine" <noone@example.com> wrote in message

news:OKmxIisJJHA.1156@TK2MSFTNGP05.phx.gbl...

>

>

> Pegasus (MVP) wrote:

> > I think that SelfImage left some of the partition table settings at the

> > values that were valid for the 130 GByte disk. I have seen similar

problems

> > with other imaging products.

>

> I guess that's possible. Is there any way to fix it?

>

> Thanks

[Guest Pegasus \(MVP\)]

Re: New drive/volume problem on Server 2003

 

 

"polastine" <noone@example.com> wrote in message

news:OKmxIisJJHA.1156@TK2MSFTNGP05.phx.gbl...

>

>

> Pegasus (MVP) wrote:

>> I think that SelfImage left some of the partition table settings at the

>> values that were valid for the 130 GByte disk. I have seen similar

>> problems with other imaging products.

>

> I guess that's possible. Is there any way to fix it?

>

> Thanks

 

You could use a different imaging method. Here is one that works for

workstations. I haven't tried it with AD servers:

1. Partition & format the new disk.

2. Mark the system partition "active".

3. Use one of these methods:

a) Run both disks as slave disks in some other machine, or

b) Boot the server with a Bart PE boot CD.

4. Use robocopy.exe to copy the old disk to the new disk.

[Guest polastine]

Re: New drive/volume problem on Server 2003

 

 

 

Edwin vMierlo [MVP] wrote:

> you can try this http://support.microsoft.com/kb/832316

>

> and use the "extend filesystem"

 

Oh YES!!! That absolutely did it. Explorer is reporting 900+ GB free on

the disk!

 

Thank you so much, you MVP guys rock =)

[Guest Edwin vMierlo [MVP]]

Re: New drive/volume problem on Server 2003

 

 

"polastine" <noone@example.com> wrote in message

news:%23VZwrPtJJHA.456@TK2MSFTNGP06.phx.gbl...

>

>

> Edwin vMierlo [MVP] wrote:

> > you can try this http://support.microsoft.com/kb/832316

> >

> > and use the "extend filesystem"

>

> Oh YES!!! That absolutely did it. Explorer is reporting 900+ GB free on

> the disk!

>

> Thank you so much, you MVP guys rock =)

 

you're very welcome !