Dual booting Win2K with WinXP, corrupt NTFS drive

[Guest]

I dual boot Windows 2000 Server + SP4 and Windows XP Professional + SP2

I currently have 4 drives - 2x80 Gig P-ATA, a 200G S-ATA and a 320G S-ATA
all of them are a single partition each (1 drive::1 partition).
Win2k server was installed by using the XP-Sp1 format and then installed via
the server disk onto an 80 Gig drive. A DVD drive and 2 drives (80Gig and
200Gig - both formatted and partitioned via XP-SP1 disk) later I install the
320 Gig with XP SP-1.

Now, until XP came along 2000 SP4 never wrote larger than around 120 Gig (as
much as it could write - even though it itself identified the partition size
(200 Gig) correctly) - so I never experience corruption, just an
inconveinience of wasted space on the 200Gig drive. With XP installed - I add
more to the 200 Gig drive that Win2k currently can see. During the next
reboot into 2000 server - 2K decides to blow away the drive index and rebuild
it to its liking - causing quite considerable corruption and data loss.

Drive listing currently looks like (on both OS's):
C:\ - 80 Gig (P-ATA) - NTFS - Win2k boot drive
D:\ - 80 Gig (P-ATA) - NTFS
E:\ - DVD (P-ATA) - NTFS
F:\ - 200 Gig (S-ATA) - NTFS
G:\ - 320 Gig (S-ATA) - - NTFS - WinXP boot drive

From Win XP I can move data to/from any of the drives without problems.

But from Windows 2000 if I do try to access any file that just happens to
fall outside of what it can see (no way of determining if it will), it will
rebuild the index with the next reboot - everytime causing data loss and
corruption.

I have checked out:
http://support.microsoft.com/default.aspx?scid=kb;en-us;305098
This article does not help as I am on Win2k Server SP4, with the SP4 rollup 1.
My registry already has the following:
Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\atapi\Parameters]
....
"EnableBigLba"=dword:00000001

 

[Dave Patrick]

The limitation may be within your drive controller driver or mobo bios
version. Check the manufacturer's web site.

--

Regards,

Dave Patrick ....Please no email replies - reply in newsgroup.
Microsoft Certified Professional
Microsoft MVP [Windows]
http://www.microsoft.com/protect

:
|I dual boot Windows 2000 Server + SP4 and Windows XP Professional + SP2
|
| I currently have 4 drives - 2x80 Gig P-ATA, a 200G S-ATA and a 320G S-ATA
| all of them are a single partition each (1 drive::1 partition).
| Win2k server was installed by using the XP-Sp1 format and then installed
via
| the server disk onto an 80 Gig drive. A DVD drive and 2 drives (80Gig and
| 200Gig - both formatted and partitioned via XP-SP1 disk) later I install
the
| 320 Gig with XP SP-1.
|
| Now, until XP came along 2000 SP4 never wrote larger than around 120 Gig
(as
| much as it could write - even though it itself identified the partition
size
| (200 Gig) correctly) - so I never experience corruption, just an
| inconveinience of wasted space on the 200Gig drive. With XP installed - I
add
| more to the 200 Gig drive that Win2k currently can see. During the next
| reboot into 2000 server - 2K decides to blow away the drive index and
rebuild
| it to its liking - causing quite considerable corruption and data loss.
|
| Drive listing currently looks like (on both OS's):
| C:\ - 80 Gig (P-ATA) - NTFS - Win2k boot drive
| D:\ - 80 Gig (P-ATA) - NTFS
| E:\ - DVD (P-ATA) - NTFS
| F:\ - 200 Gig (S-ATA) - NTFS
| G:\ - 320 Gig (S-ATA) - - NTFS - WinXP boot drive
|
| From Win XP I can move data to/from any of the drives without problems.
|
| But from Windows 2000 if I do try to access any file that just happens to
| fall outside of what it can see (no way of determining if it will), it
will
| rebuild the index with the next reboot - everytime causing data loss and
| corruption.
|
| I have checked out:
| http://support.microsoft.com/default.aspx?scid=kb;en-us;305098
| This article does not help as I am on Win2k Server SP4, with the SP4
rollup 1.
| My registry already has the following:
| Windows Registry Editor Version 5.00
|
| [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\atapi\Parameters]
| ...
| "EnableBigLba"=dword:00000001
|

 

[Andy]

I dual boot Windows 2000 Server + SP4 and Windows XP Professional + SP2

I currently have 4 drives - 2x80 Gig P-ATA, a 200G S-ATA and a 320G S-ATA
all of them are a single partition each (1 drive::1 partition).
Win2k server was installed by using the XP-Sp1 format and then installed via
the server disk onto an 80 Gig drive. A DVD drive and 2 drives (80Gig and
200Gig - both formatted and partitioned via XP-SP1 disk) later I install the
320 Gig with XP SP-1.

Now, until XP came along 2000 SP4 never wrote larger than around 120 Gig (as
much as it could write - even though it itself identified the partition size
(200 Gig) correctly) - so I never experience corruption, just an
inconveinience of wasted space on the 200Gig drive. With XP installed - I add
more to the 200 Gig drive that Win2k currently can see. During the next
reboot into 2000 server - 2K decides to blow away the drive index and rebuild
it to its liking - causing quite considerable corruption and data loss.

Drive listing currently looks like (on both OS's):
C:\ - 80 Gig (P-ATA) - NTFS - Win2k boot drive
D:\ - 80 Gig (P-ATA) - NTFS
E:\ - DVD (P-ATA) - NTFS
F:\ - 200 Gig (S-ATA) - NTFS
G:\ - 320 Gig (S-ATA) - - NTFS - WinXP boot drive

From Win XP I can move data to/from any of the drives without problems.

But from Windows 2000 if I do try to access any file that just happens to
fall outside of what it can see (no way of determining if it will), it will
rebuild the index with the next reboot - everytime causing data loss and
corruption.

I have checked out:
http://support.microsoft.com/default.aspx?scid=kb;en-us;305098
This article does not help as I am on Win2k Server SP4, with the SP4 rollup 1.
My registry already has the following:
Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\atapi\Parameters]
...
"EnableBigLba"=dword:00000001

Run Disk Management under Windows 2000, and look at the capacity of
the two SATA disks where it says

Disk 2
Basic
###.## GB
Online

and

Disk 3
Basic
###.## GB
Online

If the disk sizes are not correct, then Windows 2000 is not properly
configured to access large disks.

 

[Guest]

Thanks for the reply guys, I really do appreciate it.

The limitation may be within your drive controller driver
or mobo bios version. Check the manufacturer's web site.

I will look into the 2000 controller driver, however, I do execute the same
program, make the same selections etc. to install the drivers from the same
disk for both OS's.

I will say that XP has absoloutly no problems accessing any part of any
drive at anytime - so it I would be sceptical to say it is a hardware problem.

My mobo is an INTEL Socket 478, ASUS P4P800. With a P4 2.4GHz chip running
at 533MHz FSB. I will go on to say that an identical spec machine with a 2.4c
chip which can run at 800 MHz FSB also suffers the identical symptoms.

Disk Management under Windows 2000 for the two SATA disks are reported as:
Basic
186.30 GB
Online

Basic
298.09 GB
Online

Any other ideas? I can post you guys any DirectX info, whatever you guys
want/need.

 

[Dave Patrick]

1024 bytes = 1 kbyte, 1024 kbytes = 1 mbyte and so on.

200,000,000,000/1024/1024/1024 = 186 gB

320,000,000,000/1024/1024/1024 = 298 gB

What you see is all there is.

--

Regards,

Dave Patrick ....Please no email replies - reply in newsgroup.
Microsoft Certified Professional
Microsoft MVP [Windows]
http://www.microsoft.com/protect

:
| Thanks for the reply guys, I really do appreciate it.
|
| >The limitation may be within your drive controller driver
| > or mobo bios version. Check the manufacturer's web site.
| I will look into the 2000 controller driver, however, I do execute the
same
| program, make the same selections etc. to install the drivers from the
same
| disk for both OS's.
|
| I will say that XP has absoloutly no problems accessing any part of any
| drive at anytime - so it I would be sceptical to say it is a hardware
problem.
|
| My mobo is an INTEL Socket 478, ASUS P4P800. With a P4 2.4GHz chip running
| at 533MHz FSB. I will go on to say that an identical spec machine with a
2.4c
| chip which can run at 800 MHz FSB also suffers the identical symptoms.
|
| Disk Management under Windows 2000 for the two SATA disks are reported as:
| Basic
| 186.30 GB
| Online
|
| Basic
| 298.09 GB
| Online
|
| Any other ideas? I can post you guys any DirectX info, whatever you guys
| want/need.

 

[Guest]

Yes, I understand that - apparently so does the disk size reporting part of
Win2k.

Unfortunatly when it comes to being able to actually use any of the space
reported Win2k fails. It may sound hard to beleive, but yes, Win2k knows that
correct sizes of the drives but when accessing them in 2k (after writing to
them with XP) - will destroy the XP disk index and put "it's" version on - in
the process of doing so causing data loss and data corruption. Not to mention
that it can sometimes take 1/2 a day to do this.

 

[Dave Patrick]

Never heard of this one before. Sounds like your drive controller is
mis-handling the drives. I'd get in touch with the controller driver
developer.

--

Regards,

Dave Patrick ....Please no email replies - reply in newsgroup.
Microsoft Certified Professional
Microsoft MVP [Windows]
http://www.microsoft.com/protect

:
| Yes, I understand that - apparently so does the disk size reporting part
of
| Win2k.
|
| Unfortunatly when it comes to being able to actually use any of the space
| reported Win2k fails. It may sound hard to beleive, but yes, Win2k knows
that
| correct sizes of the drives but when accessing them in 2k (after writing
to
| them with XP) - will destroy the XP disk index and put "it's" version on -
in
| the process of doing so causing data loss and data corruption. Not to
mention
| that it can sometimes take 1/2 a day to do this.

 

[Guest]

Thanks for your time, I will try to reinstall 2000 sometime and only
Microsoft drivers instead of the MOBO driver disk - I think that this page
may be relevant to my situation:
http://www.intel.com/support/chipsets/iaa/sb/cs-009292.htm

 

[Dave Patrick]

Microsoft doesn't do driver development. The drivers that are included on
the install CD-Rom come from the hardware manufacturers. The difference you
might possibly see would be driver versions.

--

Regards,

Dave Patrick ....Please no email replies - reply in newsgroup.
Microsoft Certified Professional
Microsoft MVP [Windows]
http://www.microsoft.com/protect

:
| Thanks for your time, I will try to reinstall 2000 sometime and only
| Microsoft drivers instead of the MOBO driver disk - I think that this page
| may be relevant to my situation:
| http://www.intel.com/support/chipsets/iaa/sb/cs-009292.htm

 

[Guest]

Sorry, I did not realize that another reply had been made, thank you.

Yes, I was thinking that perhaps ASUS have supplied a old driver and simply
have not issued an update for the board.

FYI, it would appear that my problem has gone away with a repair install of
2000 Server. After the repair I then re-applied SP4, the SP4 rollup then any
other updates found on windows update. So far I have been able to access the
drives as you would expect to be able to.

I am quite perplexed about how other identical spec machines here have
suffered as well. One would expect a repair install to only fix things like
corruption etc - I believe that my machine still runs the same drivers as
before as I did not supply any driver disks in the process and it *appears*
to be the same driver. As you noted about differing driver versions - it may
be using a later driver version as I had not particulary noticed which
version was previously on. Thanks for all your help, hopefully this is the
end of my troubles.

 

[Dave Patrick]

Glad to hear things are working. You're welcome.

--

Regards,

Dave Patrick ....Please no email replies - reply in newsgroup.
Microsoft Certified Professional
Microsoft MVP [Windows]
http://www.microsoft.com/protect

:
| Sorry, I did not realize that another reply had been made, thank you.
|
| Yes, I was thinking that perhaps ASUS have supplied a old driver and
simply
| have not issued an update for the board.
|
| FYI, it would appear that my problem has gone away with a repair install
of
| 2000 Server. After the repair I then re-applied SP4, the SP4 rollup then
any
| other updates found on windows update. So far I have been able to access
the
| drives as you would expect to be able to.
|
| I am quite perplexed about how other identical spec machines here have
| suffered as well. One would expect a repair install to only fix things
like
| corruption etc - I believe that my machine still runs the same drivers as
| before as I did not supply any driver disks in the process and it
*appears*
| to be the same driver. As you noted about differing driver versions - it
may
| be using a later driver version as I had not particulary noticed which
| version was previously on. Thanks for all your help, hopefully this is the
| end of my troubles.