Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations Shaun E on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

XP Pro setup trouble on new disk. 2

Status
Not open for further replies.

kaishen

Technical User
Jun 16, 2004
3
DK
My primary harddisk crashed recently and thus I have to install XP pro again on a new drive. But this has proven more difficult than it has ever been before:

I boot from the XP Pro install CD as normal using a NTFS partition. My HDD is a ‘Maxtor DiamondMax Plus 9’ 160 Gb but I have set the partition size to 128 Gb (to circumvent the XP SP0 cap).

The program copies the setup files to the newly formatted disk and reboots to start the actual installation process. My problem is that it doesn’t boot but hangs with something like “OS not ready” and I have no idea why. Boot.ini, ntdetect.com and ntldr have all been copied correctly. I have tried both Fixboot and Fixmbr but that didn’t help. I still think it has something to do with the boot record but I have no idea what to try. I have installed XP on this computer before but never with a ‘raw’ HDD so the disk has always been bootable in advance. I hope someone can help me

- KS



My stats:
Cpu: AMD Athlon XP (Barton)
Specification: AMD Athlon(tm) XP 2600+
CPU Clock Speed: 1913.2 MHz
Clock multiplier: x 11.5, Front Side Bus Frequency: 166.4 MHz,
Bus Speed: 332.7 MHz
L1 Data Cache 64 KBytes, 2-way set associative, 64 Bytes line size
L1 Instruction Cache 64 KBytes, 2-way set associative, 64 Bytes line size
L2 Cache 512 KBytes, 16-way set associative, 64 Bytes line size
L2 Speed 1913.2 MHz (Full), L2 Location On Chip, L2 Data Prefetch Logic yes, L2 Bus Width 64 bits

Motherboard manufacturer: Abit
Motherboard model: NF7-S (nVidia-nForce2), 2.X
BIOS vendor: Phoenix Technologies, LTD
BIOS revision: 6.00 PG, BIOS release date: 11/21/2003
Chipset nVidia nForce2 rev. C1, Southbridge nVidia MCP-T rev. A4, Sensor chip Winbond W83627HF

RAM Type DDR-SDRAM (Kingston), RAM Size 512 Mbytes, CAS# Latency 2.0 clocks
RAS# to CAS# 2 clocks, RAS# Precharge 2 clocks, Cycle Time (TRAS) 5 clocks

AGP Status enabled, rev. 2.0 (GF4 TI4200), AGP Data Transfert Rate 4x, AGP Side Band Addressing supported, enabled, AGP Aperture Size 64 MBytes
 
I’ve tried that many times (many, many times) already, and just for the fun of it I tried again this morning. Still nothing! As I was absolutely exhausted when I wrote the first part I think I’ll elaborate a little.

The problem is not specific to a single hdd. I’ve tried to install xp on another other harddisk - usually my slave but set to master at the time. This had the same result. I’ve also tried with a *cough* corp. copy I have but still nothing. So it’s not the hdd nor is the CD that is the problem. I can access the hard drive using a bootdisk but not on its own – and all files seems to be copied correctly.


The exact error I get is: “Error loading Operating System” At the point where it should be busy loading my os. As I wrote before I still think it has something to do with my computer not writing the boot record correctly as I’m still able to boot using my old hdd - I just hope the integrity of my old hdd holds up until I can get a backup of it.

It is really weird so I hope someone can give me a hint.

- KS
 

What I do think will work:

1. Download Powermax from maxtor.com
2. Run it - perform low level format
3. In bios setup select LBA mode for disk
4. Install XP - do not use the Quick format option, use the regular option.
 
Thank you. Thank you. Thank you. :) That did it. I feel like such an idiot. I did do a full NTFS format with Partition Magic before I changed the drives but of course the boot record was then on the wrong disk...

Thank you once more.
-KS
 
By sheer co-incidence I believe I have a similar problem but am novice at these things( maybe theres a message therein)

Background
1) I had 3 partions on my 120gb drive. (C: F: G:)+ some unallocated.
2) I wanted to re-install XPpro so ran setup
3) Created new partion for new OS install (10gb)
4) Decided on Full format of new partition
5) Machine appeared to hang (waited 5mins nothing happened on the formatting scale)
6) Shut down machine
7) Ran install again
8) Installed XP OK
9) Went to locate previous partitions F: & G: and whilst showing within disk management, they no longer have a file system format (previously NTFS) and cannot be accessed without re-formatting (which I have not done coz I want my data!)

Any ideas how I can reconnect to these previous partions?

All help needs to be low techy stuff coz I'm verrry afraid of what to do next!
Thanks in anticipation of the worst possible news.




If IT ain’t working Binnit and Reboot
 
Have you tried under Disk Management, Actions, Rescan disks?
 
bcastner
Yes but nothing changes...

Disk management shows them as being Healthy and still retaining their original partition sizes, when checking their properties they are identified as being RAW with 0 bytes (I am presuming this is because the O/S cannot read them properly)

I have also rechecked them by partially re-running setup to see what they look like in setup mode, the partition setup shows them a F: and G: but describes them as 'Unknown' file system.

Having looked at MS Knowledge base there is an article which suggests that the machine needs to reformat the existing system partition prior to creating new ones during an O/S install, it may well be that it was doing this when I powered down beliving it to have hung thus losing its flags.


I have a friend who is coming round to use Partion Magic on Weds but wondered if :-

1) There was a quick easy solution to re-connect
2) If I am likely to be able to recover the data or should I break down in tears and wave goodbye to it?

Fearing the worst....


If IT ain’t working Binnit and Reboot
 
bcastner
Thanks, I have now got testdisk (need to take it home) and will try it out.

When you say that PM may not be the best way to recover is there a reason for your concerns?

What do you consider the chances of recovery are?



If IT ain’t working Binnit and Reboot
 
Try PM.

I just think it is better as a partition editor for working drives than a repair tool for non-working partitions.

A RAW file system means that XP is not able to recognise what file system it is - which reinforces the idea that the partition type byte is wrong.

This requires so low-level editing of the partition table that is not the strong point of PM. (No offense to PM).

I believe TestDisk can do this. Alex Nichols, MVP, who is just great about Shell issue, suggested in a newsgroup post for a similar issue, and I now quote:

If so, the approach I would take is to get the trial download of BootIT NG from
Put the downloaded zip file in its own folder, extract components, run the bootitng.exe to make a bootable floppy.

Boot that; cancel Install, thus entering Maintenance, click Partition Work.

Select the drive on the left, then the partition and click Properties.
There you can select the Partition type it ought to be (either FAT 32 or HPFS/NTFS) and if there is an Unhide button, click that - OK out and see.

If that does not do it, or if the partition does not even show in Disk Management, get the free tool MBRWORK from the same site, put it on a DOS boot floppy, boot and run it.

USe the commands
7 to work with multiple drives and select the one to handle
1 to back up current state
3 then 4 to delete the present state
you will then be able to use
A
to search out partitions and build a new partition table
 
bcastner
Thanks for your further posting above, I took the Testdisk home last night, ran it and will send the results off to cgsecurity.org (as per their suggestion).

The good news is that the partitions are still in place and I was able to view the files, I did not venture further although it did offer the opportunity to change file system.

Here is the text of my drive, does this mean anything to you? I have highlighted the bits that appear to show the more interesting results, especially that the partitions still appear to be in HPFS - NTFS format!

Code:
Mon Jun 21 18:24:22 2004
TestDisk command line :
TestDisk 5.3, Data Recovery Utility, May 2004
Christophe GRENIER <grenier@cgsecurity.org>
[URL unfurl="true"]http://www.cgsecurity.org[/URL]
Windows version
Using locale 'C'.
file_read(4,1,buffer,234452609(14593/254/63)) seek err Invalid argument
Hard disk list
Disk /dev/sda - CHS 14593 255 63 - 114470 MB


Analyse Disk /dev/sda - CHS 14593 255 63 - 114470 MB
Geometry from MBR: head=255 sector=63
check_part 07
NTFS at 9561/1/1
test_FAT : Boot sector doesn't have the endmark 0xAA55


test_FAT()
 5 L FAT16 LBA            10836   1  1 14591 254 63   60340077
sector_size  0
cluster_size 0
reserved     0
fats         0
dir_entries  0
sectors      0
media        00
fat_length   0
secs_track   0
heads        0
hidden       0
total_sect   0
check_part 0E
get_geometry_from_list_part_aux head=255 nbr=4
Current partitions:
Invalid NTFS boot
 1 P HPFS - NTFS              0   1  1  9560 254 63  153597402
 1 P HPFS - NTFS              0   1  1  9560 254 63  153597402
 2 * HPFS - NTFS           9561   1  1 10835 254 63   20482812
 3 E extended LBA         10836   0  1 14591 254 63   60340140
test_FAT : Boot sector doesn't have the endmark 0xAA55
 5 L FAT16 LBA            10836   1  1 14591 254 63   60340077
 5 L FAT16 LBA            10836   1  1 14591 254 63   60340077

search_part()
Disk /dev/sda - CHS 14593 255 63 - 114470 MB

Results
Mon Jun 21 18:32:31 2004
TestDisk command line :
TestDisk 5.3, Data Recovery Utility, May 2004
Christophe GRENIER <grenier@cgsecurity.org>
[URL unfurl="true"]http://www.cgsecurity.org[/URL]
Windows version
Using locale 'C'.
file_read(4,1,buffer,234452609(14593/254/63)) seek err Invalid argument
Hard disk list
Disk /dev/sda - CHS 14593 255 63 - 114470 MB


Analyse Disk /dev/sda - CHS 14593 255 63 - 114470 MB
Geometry from MBR: head=255 sector=63
check_part 07
NTFS at 9561/1/1
test_FAT : Boot sector doesn't have the endmark 0xAA55


test_FAT()
 5 L FAT16 LBA            10836   1  1 14591 254 63   60340077
sector_size  0
cluster_size 0
reserved     0
fats         0
dir_entries  0
sectors      0
media        00
fat_length   0
secs_track   0
heads        0
hidden       0
total_sect   0
check_part 0E
get_geometry_from_list_part_aux head=255 nbr=4

[b]Current partitions:
Invalid NTFS boot
 1 P HPFS - NTFS              0   1  1  9560 254 63  153597402
 1 P HPFS - NTFS              0   1  1  9560 254 63  153597402
 2 * HPFS - NTFS           9561   1  1 10835 254 63   20482812
 3 E extended LBA         10836   0  1 14591 254 63   60340140
test_FAT : Boot sector doesn't have the endmark 0xAA55
 5 L FAT16 LBA            10836   1  1 14591 254 63   60340077
 5 L FAT16 LBA            10836   1  1 14591 254 63   60340077
[/b]
search_part()
Disk /dev/sda - CHS 14593 255 63 - 114470 MB
NTFS at 3824/0/1
sectors_per_cluster       8
mft_lcn                   786432
mftmirr_lcn               2560359
clusters_per_mft_record   -10
clusters_per_index_record 1
[b]   D HPFS - NTFS           3824   0  1  6373 254 63   40965750 [Data]
NTFS at 6374/0/1
sectors_per_cluster       8
mft_lcn                   262144
mftmirr_lcn               639587
clusters_per_mft_record   -10
clusters_per_index_record 1
   D HPFS - NTFS           6374   0  1  7010 254 63   10233405 [Photos]
NTFS at 7011/0/1
sectors_per_cluster       8
mft_lcn                   786432
mftmirr_lcn               2560359
clusters_per_mft_record   -10
clusters_per_index_record 1
   D HPFS - NTFS           7011   0  1  9560 254 63   40965750 [Music]
NTFS at 9561/1/1
sectors_per_cluster       8
mft_lcn                   786432
mftmirr_lcn               1280175
clusters_per_mft_record   -10
clusters_per_index_record 1
   D HPFS - NTFS           9561   1  1 10835 254 63   20482812
[/b]
FAT32 at 14067/0/1
FAT32
FAT1 : 32-8263
FAT2 : 8264-16495
start_rootdir : 16496 root cluster : 2
Data : 16496-8445951
sectors : 8445952
cluster_size : 8
no_of_cluster : 1053682 (2 - 1053683)
fat_length 8232 calculated 8232
   D FAT32 LBA            14067   0  1 14592 187 46    8445952 [FACTORY]
get_geometry_from_list_part_aux head=255 nbr=4
[b]
Results
   D HPFS - NTFS           3824   0  1  6373 254 63   40965750 [Data]
   D HPFS - NTFS           6374   0  1  7010 254 63   10233405 [Photos]
   D HPFS - NTFS           7011   0  1  9560 254 63   40965750 [Music]
   D HPFS - NTFS           9561   1  1 10835 254 63   20482812
   D FAT32 LBA            14067   0  1 14592 254 63    8450190 [FACTORY]

   D HPFS - NTFS           7011   0  1  9560 254 63   40965750 [Music]
[/b]
dir_partition inode=5
   D HPFS - NTFS           7011   0  1  9560 254 63   40965750 [Music]
Directory /
      5 dr-xr-xr-x     0      0         0 27-Apr-2004 19:53 .
      5 dr-xr-xr-x     0      0         0 27-Apr-2004 19:53 ..
     51 dr-xr-xr-x     0      0         0 27-Apr-2004 20:00 Music
   1756 dr-xr-xr-x     0      0         0 27-Apr-2004 20:37 RECYCLER
     28 dr-xr-xr-x     0      0         0 27-Apr-2004 19:58 System Volume Information

dir_partition inode=51
   D HPFS - NTFS           7011   0  1  9560 254 63   40965750 [Music]
Directory /Music
     51 dr-xr-xr-x     0      0         0 27-Apr-2004 20:00 .
      5 dr-xr-xr-x     0      0         0 27-Apr-2004 19:53 ..
7 - Enrique Iglesias
   1009 dr-xr-xr-x     0      0         0 29-Apr-2004 21:37 A Present For Everyone - Busted
   1325 dr-xr-xr-x     0      0         0 29-Apr-2004 20:16 Air Guitar 3
   3486 dr-xr-xr-x     0      0         0 27-Apr-2004 20:35 American Pie - Don McLean
   3437 dr-xr-xr-x     0      0         0 27-Apr-2004 20:34 As Time Goes By..._The Great American Songbook Vol. 2 - Rod Stewart
List of partition type
00 empty                01 FAT12                02 XENIX root           
03 XENIX /usr           04 FAT16 <32M           05 extended             
06 FAT16 >32M           07 HPFS - NTFS          09 AIX data             
0a OS/2 Boot Manager    0b FAT32                0c FAT32 LBA            
0e FAT16 LBA            0f extended LBA         10 OPUS                 
11 hid. FAT12           12 Compaq Diagnostics   14 hid. FAT16 <32M      
16 hid. FAT16 >32M      17 hid. HPFS/NTFS       18 AST swap             
19 Willowtech Photon    1b hid. FAT32           1c hid. FAT32 LBA       
1e hid. FAT16 LBA       20 Willowsoft OFS1      24 NEC MS-DOS 3.x       
38 Theos                3c PMagic recovery      40 VENIX 80286          
41 Personal RISC        42 W2K Dynamic/SFS      50 OnTrack DM RO        
51 OnTrack DM RW-NOVEL  52 CP/M-Microport V/386 53 OnTrack DM WO ???    
54 OnTrack DM DDO       55 EZ-Drive             56 GoldenBow VFeature   
61 SpeedStor            63 Unixware, HURD, SCO  64 NetWare 286          
65 NetWare 3.11+        67 Novell               68 Novell               
69 Novell               70 DiskSecure MB        75 PC/IX                
80 Minix v1.1-1.4a      81 Linux (Old)          82 Linux Swap           
83 Linux                85 Linux extended       86 NT FAT16 V/S set     
87 HPFS FT mirror-V/S set 8e LVM                  93 Amoeba               
94 Amoeba bad block     a0 NoteBIOS save2disk   a5 FreeBSD              
a6 OpenBSD              a9 NetBSD               b7 BSDI                 
b8 BSDI swap            c1 secured FAT12        c4 secured FAT16        
c6 sec. Huge-bad FAT16  c7 Syrinx Boot-bad NTFS d8 CP/M-86              
db CP/M                 de Dell Utility         e1 SpeedStor FAT12 ext  
e3 DOS RO               e4 SpeedStor FAT16 ext  eb BeFS                 
f1 Storage Dimensions   f2 DOS secondary        f4 SpeedStor            
fd Linux RAID           fe LANstep              ff Xenix bad block

If IT ain’t working Binnit and Reboot
 
bcastor
I have submitted data to Grenier, see what happens if I get a reply, thanks for the other URL, looks helpful.

A colleague has suggested that this could just require an edit to the Boot.ini file which, following the interrupted format on the 1st install, may now assume that there is only 1 primary disk, does this seem reasonable to you? I will check my Boot.ini file at lunchtime and re-post.

Thanks for your pointers and "victim support" so far!


If IT ain’t working Binnit and Reboot
 
TestDisk does not care about the boot.ini. The reports above show at least a serious issue with the MBR of the drive.

 
bcastner

Are you able to translate the meaning of the following compared with the results?
Code:
Current partitions:
Invalid NTFS boot
 1 P HPFS - NTFS              0   1  1  9560 254 63  153597402
 1 P HPFS - NTFS              0   1  1  9560 254 63  153597402
 2 * HPFS - NTFS           9561   1  1 10835 254 63   20482812
 3 E extended LBA         10836   0  1 14591 254 63   60340140
test_FAT : Boot sector doesn't have the endmark 0xAA55
 5 L FAT16 LBA            10836   1  1 14591 254 63   60340077
 5 L FAT16 LBA            10836   1  1 14591 254 63   60340077
===================================================
Code:
Results
   D HPFS - NTFS           3824   0  1  6373 254 63   40965750 [Data]
   D HPFS - NTFS           6374   0  1  7010 254 63   10233405 [Photos]
   D HPFS - NTFS           7011   0  1  9560 254 63   40965750 [Music]
   D HPFS - NTFS           9561   1  1 10835 254 63   20482812
   D FAT32 LBA            14067   0  1 14592 254 63    8450190 [FACTORY]

The top looks like its reporting an error, the reports seem to indicate things are healthy. Are you/anyone able to explain all the different numbers to me a simpleton?



If IT ain’t working Binnit and Reboot
 
The top is the attempt to read the partition table. Note the issue with the #4 partition. Which in your case is unfortunately the Boot record.

The bottom panel you list above is a best attempt to read a single partition record.

Ignore it until the first panel is cleaned up.

Note in your post much above, that one partition entries showed FF number of partitions under it, all of it nonsense. Until you get some specific advice, do nothing. You might want to post your last two or the threads in forum578


 
Yikes! I hit Submit Post instead of Preview by mistake.

forum528

Post a link to this discussion, and ask for advice and comments.

But do not fiddle with the partition tables or anything else until you see a clear answer. My guess is your data is recoverable, as are your original partitions. If you are very carefull about the issue.

Best,
Bill Castner

 
bcasttner
Thanks again for your postings, I will start a fresh/tidy post in the alternative forum as suggested.
Martin

If IT ain’t working Binnit and Reboot
 
bcastner
Its the big day (tonight) I now have had several responses from Grenier and feel confident to give it a shot (fortunately with with some assistance.)

However, a further thought occurred to me, during reading up various postings around the WWW, several people have used an alternative machine HD as master and connected the 'corrupted' drive as slave then recovered the data according.

Do you think this is an option for me?


If IT ain’t working Binnit and Reboot
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top