Strange 137GB problem on Windows 2000

[Guest Erik]

Hey there,

 

I have a windows 2000 advanced server computer running with 2 drives in it,

one (the one smaller then 137GB as a boot disk with windows installed on it,

the second one is bigger then 137 GB (200GB).

 

It's an old computer so the BIOS doesn't support a 48-bit LBA and there

aren't BIOS upgrades that do support it. So I bought a IDE/SATA raid

controller with a PCI slot, after I connected the drive the windows 2000

advanced server installation cd (including SP4) could easilly recognize the

disk at full size so I formatted it into 1 partition. After creating the

registry key 'EnableBigLba' all worked fine and windows could recognize the

big HDD.

 

But, and now I got quite confused, after copying lots of data unto the disk

about 160GB, windows said there was only 137 GB on the disk and there was

lots of space left (about 50GB).

But that's not right! I put more then 137 GB on the disk! So I summed up all

folder sizes apart to see if the sum of folders was greater then 137GB, but

it wasn't. I counted all the files that I copied on the source HDD and the

destination HDD (the server HDD), but they matched, there weren't any files

lost.

 

So now I'm wondering,

Is there really 137GB data on the disk so there must be data corruption,

OR

Is windows 2000 giving me wrong information and how should I know when the

disk is full then?

 

I hope anyone could help me understand what's happening, cause I don't think

it makes any sence.

 

Yours faithfully,

 

Erik Hubers

[Guest nesredep egrob]

Re: Strange 137GB problem on Windows 2000

 

On Wed, 5 Dec 2007 06:10:01 -0800, Erik <Erik@discussions.microsoft.com> wrote:

>Hey there,

>

>I have a windows 2000 advanced server computer running with 2 drives in it,

>one (the one smaller then 137GB as a boot disk with windows installed on it,

>the second one is bigger then 137 GB (200GB).

>

>It's an old computer so the BIOS doesn't support a 48-bit LBA and there

>aren't BIOS upgrades that do support it. So I bought a IDE/SATA raid

>controller with a PCI slot, after I connected the drive the windows 2000

>advanced server installation cd (including SP4) could easilly recognize the

>disk at full size so I formatted it into 1 partition. After creating the

>registry key 'EnableBigLba' all worked fine and windows could recognize the

>big HDD.

>

>But, and now I got quite confused, after copying lots of data unto the disk

>about 160GB, windows said there was only 137 GB on the disk and there was

>lots of space left (about 50GB).

>But that's not right! I put more then 137 GB on the disk! So I summed up all

>folder sizes apart to see if the sum of folders was greater then 137GB, but

>it wasn't. I counted all the files that I copied on the source HDD and the

>destination HDD (the server HDD), but they matched, there weren't any files

>lost.

>

>So now I'm wondering,

>Is there really 137GB data on the disk so there must be data corruption,

>OR

>Is windows 2000 giving me wrong information and how should I know when the

>disk is full then?

>

 

I think you should log in as the administrator and go to settings/control

Panel/Administative Tools/Computer Management/Disk Management

 

and see what it says on there. You can see the size of the disks and the

partitions and you can even with a right click see what is on the disk via the

Explorer.

That should get you in the mood to tell us what is going on

 

Borge in sunny Perth, Australia

 

>it makes any sence.

>

>Yours faithfully,

>

>Erik Hubers

[Guest lukesh]

RE: Strange 137GB problem on Windows 2000

 

Yeah, Go to disk management and check out how much space it shows there.

You can try running chkdsk to check the correct free space on the drive.

You can also run streams.exe from sysinternals to check if there are

alternate data streams.

 

"Erik" wrote:

> Hey there,

>

> I have a windows 2000 advanced server computer running with 2 drives in it,

> one (the one smaller then 137GB as a boot disk with windows installed on it,

> the second one is bigger then 137 GB (200GB).

>

> It's an old computer so the BIOS doesn't support a 48-bit LBA and there

> aren't BIOS upgrades that do support it. So I bought a IDE/SATA raid

> controller with a PCI slot, after I connected the drive the windows 2000

> advanced server installation cd (including SP4) could easilly recognize the

> disk at full size so I formatted it into 1 partition. After creating the

> registry key 'EnableBigLba' all worked fine and windows could recognize the

> big HDD.

>

> But, and now I got quite confused, after copying lots of data unto the disk

> about 160GB, windows said there was only 137 GB on the disk and there was

> lots of space left (about 50GB).

> But that's not right! I put more then 137 GB on the disk! So I summed up all

> folder sizes apart to see if the sum of folders was greater then 137GB, but

> it wasn't. I counted all the files that I copied on the source HDD and the

> destination HDD (the server HDD), but they matched, there weren't any files

> lost.

>

> So now I'm wondering,

> Is there really 137GB data on the disk so there must be data corruption,

> OR

> Is windows 2000 giving me wrong information and how should I know when the

> disk is full then?

>

> I hope anyone could help me understand what's happening, cause I don't think

> it makes any sence.

>

> Yours faithfully,

>

> Erik Hubers

[Guest Erik]

Re: Strange 137GB problem on Windows 2000

 

 

 

"nesredep egrob" wrote:

> On Wed, 5 Dec 2007 06:10:01 -0800, Erik <Erik@discussions.microsoft.com> wrote:

>

> >Hey there,

> >

> >I have a windows 2000 advanced server computer running with 2 drives in it,

> >one (the one smaller then 137GB as a boot disk with windows installed on it,

> >the second one is bigger then 137 GB (200GB).

> >

> >It's an old computer so the BIOS doesn't support a 48-bit LBA and there

> >aren't BIOS upgrades that do support it. So I bought a IDE/SATA raid

> >controller with a PCI slot, after I connected the drive the windows 2000

> >advanced server installation cd (including SP4) could easilly recognize the

> >disk at full size so I formatted it into 1 partition. After creating the

> >registry key 'EnableBigLba' all worked fine and windows could recognize the

> >big HDD.

> >

> >But, and now I got quite confused, after copying lots of data unto the disk

> >about 160GB, windows said there was only 137 GB on the disk and there was

> >lots of space left (about 50GB).

> >But that's not right! I put more then 137 GB on the disk! So I summed up all

> >folder sizes apart to see if the sum of folders was greater then 137GB, but

> >it wasn't. I counted all the files that I copied on the source HDD and the

> >destination HDD (the server HDD), but they matched, there weren't any files

> >lost.

> >

> >So now I'm wondering,

> >Is there really 137GB data on the disk so there must be data corruption,

> >OR

> >Is windows 2000 giving me wrong information and how should I know when the

> >disk is full then?

> >

>

> I think you should log in as the administrator and go to settings/control

> Panel/Administative Tools/Computer Management/Disk Management

>

> and see what it says on there. You can see the size of the disks and the

> partitions and you can even with a right click see what is on the disk via the

> Explorer.

> That should get you in the mood to tell us what is going on

>

> Borge in sunny Perth, Australia

>

>

> >it makes any sence.

> >

> >Yours faithfully,

> >

> >Erik Hubers

>

>

 

Diskmanager gave me the same information as the disk properties (tried that

already ;) ), size partition 186GB (I lost some gigs 2 years ago), and 137GB

used.

But I already got the answer on another forum, thanks for your help anyway

:).

 

It's only windows 2000 that's giving me the wrong information, there's

actually more data on the disk then windows show me. So everything works fine

exept the info windows give me.

[Guest lukesh]

Re: Strange 137GB problem on Windows 2000

 

This is weired. I have not heared of such a bug being reported earlier. If

windows is misreporting disk information, there has to be a reason for it.

 

"Erik" wrote:

>

>

> "nesredep egrob" wrote:

>

> > On Wed, 5 Dec 2007 06:10:01 -0800, Erik <Erik@discussions.microsoft.com> wrote:

> >

> > >Hey there,

> > >

> > >I have a windows 2000 advanced server computer running with 2 drives in it,

> > >one (the one smaller then 137GB as a boot disk with windows installed on it,

> > >the second one is bigger then 137 GB (200GB).

> > >

> > >It's an old computer so the BIOS doesn't support a 48-bit LBA and there

> > >aren't BIOS upgrades that do support it. So I bought a IDE/SATA raid

> > >controller with a PCI slot, after I connected the drive the windows 2000

> > >advanced server installation cd (including SP4) could easilly recognize the

> > >disk at full size so I formatted it into 1 partition. After creating the

> > >registry key 'EnableBigLba' all worked fine and windows could recognize the

> > >big HDD.

> > >

> > >But, and now I got quite confused, after copying lots of data unto the disk

> > >about 160GB, windows said there was only 137 GB on the disk and there was

> > >lots of space left (about 50GB).

> > >But that's not right! I put more then 137 GB on the disk! So I summed up all

> > >folder sizes apart to see if the sum of folders was greater then 137GB, but

> > >it wasn't. I counted all the files that I copied on the source HDD and the

> > >destination HDD (the server HDD), but they matched, there weren't any files

> > >lost.

> > >

> > >So now I'm wondering,

> > >Is there really 137GB data on the disk so there must be data corruption,

> > >OR

> > >Is windows 2000 giving me wrong information and how should I know when the

> > >disk is full then?

> > >

> >

> > I think you should log in as the administrator and go to settings/control

> > Panel/Administative Tools/Computer Management/Disk Management

> >

> > and see what it says on there. You can see the size of the disks and the

> > partitions and you can even with a right click see what is on the disk via the

> > Explorer.

> > That should get you in the mood to tell us what is going on

> >

> > Borge in sunny Perth, Australia

> >

> >

> > >it makes any sence.

> > >

> > >Yours faithfully,

> > >

> > >Erik Hubers

> >

> >

>

> Diskmanager gave me the same information as the disk properties (tried that

> already ;) ), size partition 186GB (I lost some gigs 2 years ago), and 137GB

> used.

> But I already got the answer on another forum, thanks for your help anyway

> :).

>

> It's only windows 2000 that's giving me the wrong information, there's

> actually more data on the disk then windows show me. So everything works fine

> exept the info windows give me.