Partition not visible during setup - visible in My Computer

[nottoman]

I connected a larger hard drive from an XP Machine to a Win 7 machine via USB and shrunk the volume to create a new partition. Both partitions showed up in My Computer and I even created a folder in the new partition. I wanted to use the hard drive in another machine to install XP Pro on, but during setup it just shows one partition - I want to install XP on the other partition. Redid the operation, ran CHKDSK, etc. No change - any ideas?

 

[foscooter]

Are all partions set to "Active" in Disk Management?

 

[nottoman]

Only one partition can be set to Active, correct?
I will mark the one not showing up as Active and see what happens.

http://www.microsoft.com/resources/documentation/windows/xp/all/proddocs/en-us/dm_active_partition.mspx?mfr=true

 

[foscooter]

As long as the drive is not shown as "unallocated."

 

[nottoman]

I think it's showing up correctly.
Even when I mark the second partition as Active, during Windows XP setup in another machine, it won't show up, and there is no space shown as Unallocated.

 

[nottoman]

Maybe it's just the fact that the partitions were created in Windows 7 ?

 

[pat]

The partition may be marked as a dinamic disk and will probably have trouble to mount with XP.

What you can do is to delete the partition anf recreate it with XP. Format it, then put the HDD back to Win7 machine and do the transfer again.

 

[foscooter]

^+1

 

[nottoman]

Well, I ran Seagate Seatools because I thought there must be something faulty in the drive - that's just too weird. The disk properties in Disk Management show it as a Basic Disk. The short and long tests passed, so I thought it was OK.
I deleted both partitions and recreated them, formatted them and then put them in another PC to install XP. The setup window showed both partitions, so I was happy there was some logic to this, but somewhere during the process there was a restart and a CHKDSK screen came up saying one of the disks needed to be checked for consistency. Here's the log -- what do you think? I'm a bit worried about the drive.

Checking file system on H:
The type of the file system is NTFS.
Volume label is Data.


One of your disks needs to be checked for consistency. You
may cancel the disk check, but it is strongly recommended
that you continue.
Windows will now check the disk.
The attribute of type 0x90 and instance tag 0x9 should be after
attribute of type 0x90 and instance tag 0x6 in file 0x9.
All attribute of type 0x90 and instance tag 0x9 should be indexed
in file 0x9.
Sorting attribute records for file record segment 9.
The multi-sector header signature for VCN 0x0 of index $I30
in file 0x5 is incorrect.
32 c7 f4 02 71 de fb 0e 75 01 ca fd 65 fb 0e c8 2...q...u...e...
f4 02 5d 94 fb 05 75 01 89 ca 96 fb 08 c9 f4 02 ..]...u.........
Correcting error in index $I30 for file 5.
The index bitmap $I30 in file 0x5 is incorrect.
Correcting error in index $I30 for file 5.
The down pointer of current index entry with length 0x18 is invalid.
00 00 00 00 00 00 00 00 18 00 00 00 03 00 00 00 ................
ff ff ff ff ff ff ff ff 00 00 00 00 00 00 00 00 ................
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
Sorting index $I30 in file 5.
Cleaning up minor inconsistencies on the drive.
CHKDSK is recovering lost files.
Recovering orphaned file $MFT (0) into directory file 5.
Recovering orphaned file $MFTMirr (1) into directory file 5.
Recovering orphaned file $LogFile (2) into directory file 5.
Recovering orphaned file $Volume (3) into directory file 5.
Recovering orphaned file $AttrDef (4) into directory file 5.
Recovering orphaned file . (5) into directory file 5.
Recovering orphaned file $Bitmap (6) into directory file 5.
Recovering orphaned file $Boot (7) into directory file 5.
Recovering orphaned file $BadClus (8) into directory file 5.
Recovering orphaned file $Secure (9) into directory file 5.
Recovering orphaned file $UpCase (10) into directory file 5.
Recovering orphaned file $Extend (11) into directory file 5.
Recovering orphaned file SYSTEM~1 (27) into directory file 5.
Recovering orphaned file System Volume Information (27) into directory file 5.
Creating index $SII for file 9.
Inserting an index entry with Id 256 into index $SII of file 9.
Inserting an index entry with Id 257 into index $SII of file 9.
Inserting an index entry with Id 258 into index $SII of file 9.
Inserting an index entry with Id 259 into index $SII of file 9.
Repairing the security file record segment.
The security descriptor in file 0x5 is invalid.
Replacing missing or invalid security descriptor for file 5.
The MFT mirror is different from the MFT.
Correcting errors in the Master File Table (MFT) mirror.
The upcase file content is incorrect.
Correcting errors in the uppercase file.
Correcting errors in the Volume Bitmap.
Windows has made corrections to the file system.

182691179 KB total disk space.
0 KB in 1 files.
8 KB in 9 indexes.
0 KB in bad sectors.
71551 KB in use by the system.
65536 KB occupied by the log file.
182619620 KB available on disk.

4096 bytes in each allocation unit.
45672794 total allocation units on disk.
45654905 allocation units available on disk.

Internal Info:
20 00 00 00 15 00 00 00 13 00 00 00 00 00 00 00 ...............
00 00 00 00 00 00 00 00 04 00 00 00 00 00 00 00 ................
1c 4e 0e 00 00 00 00 00 d0 12 13 00 00 00 00 00 .N..............
ec 60 21 00 00 00 00 00 00 00 00 00 00 00 00 00 .`!.............
00 00 00 00 00 00 00 00 6a ce 88 07 00 00 00 00 ........j.......
00 61 47 6b 00 00 00 00 01 00 00 00 00 00 00 00 .aGk............
%

 

[scout_03]

there could be a bad sector where the partition start so disk give error why you dont format all the disk and made one partition install xp then after that use this to create the other partition it's free http://www.partition-tool.com/personal.htm

 

[nottoman]

This hard drive is on its way out - ran CHKDSK again - 109908336 KB in bad sectors. Toast
Thanks for all your help.

 

[nottoman]

Best answer selected by nottoman.