nj123
asked on
Windows 2000 SP 3 fails to boot up at Splash Screen
I have a Dell 330 Precision with a 18GB Ultra SCSI boot up hard drive (refered hence forth as "Disk C1") connected by an Adaptec 29160N SCSI Controller card. The hard disk, Disk C1, is loaded with windows 2000 Profession SP 3 operating system. There is no other OS but the hard disk has Norton Utilities 2003 and Antivirus. The Norton utilities ran weekly to defrag the drive.
Recently I had a boot-up problem. The boot progresses naturally in the beginning, goes past the bios setup, where it correctly detects the Disk C1. It then goes through the blank screen saying "Starting Windows" and the white bar at the bottom goes through, the black screen. The screen switches to the Windows splash screen saying ... "Windows 2000 Profession, Built on NT Technology". Below the blue stripe there is progress bar about 75% finished saying "starting window....". The progress bar stays there for over 3 hours, and there is no disk activity. The computer fails to boot-up.
I have narrowed the problem to the SCSI hard drive, Disk C1, by trial and error. Replacing the hard drive with another (called Disk C2) and re-installing windows, works and the computer boots up fine. If I have the tainted Hard Disk C1 in SCSI chain (with a different ID setting then 0), the computer still hangs up even if try booting from a good bootable disk Disk C2.
Among other things, I have:
a) Checked the SCSI drive through the Bios for errors. It is error free
b) Tried repairing windows 2000 using startup CDROM containing Windows 2000+SP1 and installing the SCSI driver through F6. Unfortunately the startup proceeds, installs all drivers and stalls for over 6 hours at "Starting Windows".
c) I have tried a bootable disk with Boot.ini, ntldr, ntdetect.com etc. The bootable disk works with a new format scsi (Disk C2) but fails with the old scsi, the Disk C1. Because of the /SOS option the, I could see that the memory was checked fine and it stopped at the "check file system".
d) I have also run the dell diagnostic on the system, all hardware including the hard disk, Disk C1, checks out okay.
I need the data in the disk and would like to know why the disk failed; viral, software or hardware. So my question is how do I get to access the disk? And what could be wrong with it?
Thanks,
nj123
Recently I had a boot-up problem. The boot progresses naturally in the beginning, goes past the bios setup, where it correctly detects the Disk C1. It then goes through the blank screen saying "Starting Windows" and the white bar at the bottom goes through, the black screen. The screen switches to the Windows splash screen saying ... "Windows 2000 Profession, Built on NT Technology". Below the blue stripe there is progress bar about 75% finished saying "starting window....". The progress bar stays there for over 3 hours, and there is no disk activity. The computer fails to boot-up.
I have narrowed the problem to the SCSI hard drive, Disk C1, by trial and error. Replacing the hard drive with another (called Disk C2) and re-installing windows, works and the computer boots up fine. If I have the tainted Hard Disk C1 in SCSI chain (with a different ID setting then 0), the computer still hangs up even if try booting from a good bootable disk Disk C2.
Among other things, I have:
a) Checked the SCSI drive through the Bios for errors. It is error free
b) Tried repairing windows 2000 using startup CDROM containing Windows 2000+SP1 and installing the SCSI driver through F6. Unfortunately the startup proceeds, installs all drivers and stalls for over 6 hours at "Starting Windows".
c) I have tried a bootable disk with Boot.ini, ntldr, ntdetect.com etc. The bootable disk works with a new format scsi (Disk C2) but fails with the old scsi, the Disk C1. Because of the /SOS option the, I could see that the memory was checked fine and it stopped at the "check file system".
d) I have also run the dell diagnostic on the system, all hardware including the hard disk, Disk C1, checks out okay.
I need the data in the disk and would like to know why the disk failed; viral, software or hardware. So my question is how do I get to access the disk? And what could be wrong with it?
Thanks,
nj123
CrazyOne
Can you not chain the C2 and C1 disk together and boot to the C2 disk. If so then you should be able to gain access to the C1 disk to get your data.
Also have tried booting to the Recovery Console and run this command
chkdsk /r
To start the Recovery Console, use any of the following methods:
Start your computer with the Windows 2000 Setup floppy disks, or with the Windows 2000 CD-ROM. At the "Welcome to Setup" screen, press F10, or press R to repair, and then C to start the Recovery Console.
chkdsk /r
To start the Recovery Console, use any of the following methods:
Start your computer with the Windows 2000 Setup floppy disks, or with the Windows 2000 CD-ROM. At the "Welcome to Setup" screen, press F10, or press R to repair, and then C to start the Recovery Console.
Of course that is presuming the dirvers will install.
ASKER
When I boot from C2 alone it boots fine. If I connect C2 (ID 0) and C1 (ID 8) together, it fails to boot up.
I will try your second suggestion in a minute...although it does not boot from CRROM with W2K and C1 connected.
I will try your second suggestion in a minute...although it does not boot from CRROM with W2K and C1 connected.
ASKER
Yes Drives to install fine.
ASKER
Read last as...
Drivers do install fine
Drivers do install fine
ASKER
With regards to ...
At the "Welcome to Setup" screen, press F10, or press R to repair, and then C to start the Recovery Console.
The computer seem to hangs at: "Setup is Starting Windows 2000".
At the "Welcome to Setup" screen, press F10, or press R to repair, and then C to start the Recovery Console.
The computer seem to hangs at: "Setup is Starting Windows 2000".
>>>although it does not boot from CRROM with W2K and C1 connected.
It doesn't. You do have your BIOS setup to boot from CD?
It doesn't. You do have your BIOS setup to boot from CD?
ASKER
With regards to ...
At the "Welcome to Setup" screen, press F10, or press R to repair, and then C to start the Recovery Console.
The computer seem to hangs at: "Setup is Starting Windows 2000".
At the "Welcome to Setup" screen, press F10, or press R to repair, and then C to start the Recovery Console.
The computer seem to hangs at: "Setup is Starting Windows 2000".
See if using these help any
download and create the Win2000 setup disks
http://www.tech24.com/tools/bootdisks/win2kpro.asp
download and create the Win2000 setup disks
http://www.tech24.com/tools/bootdisks/win2kpro.asp
Is the C1 disk a SCSI as well? If so you may be able to get to the recovery console with both disks hooked up.
ASKER
>> It doesn't. You do have your BIOS setup to boot from CD?
Ofcourse!! The computer is booting from the CDROM using the CDROM bootup option in the BIOS.
ASKER
>> It doesn't. You do have your BIOS setup to boot from CD?
Ofcourse!! The computer is booting from the CDROM using the CDROM bootup option in the BIOS.
ASKER
>> It doesn't. You do have your BIOS setup to boot from CD?
Ofcourse!! The computer is booting from the CDROM using the CDROM bootup option in the BIOS.
ASKER
> See if using these help any
> download and create the Win2000 setup disks
> http://www.tech24.com/tools/bootdisks/win2kpro.asp
The files you suggested are quite handy. The system goes through the process of loading the OS. It hangs up at "Setup is Starting Windows 2000".
> download and create the Win2000 setup disks
> http://www.tech24.com/tools/bootdisks/win2kpro.asp
The files you suggested are quite handy. The system goes through the process of loading the OS. It hangs up at "Setup is Starting Windows 2000".
ASKER
>Is the C1 disk a SCSI as well? If so you may be able to
> get to the recovery console with both disks hooked up.
Yes both Disk C1 and C2 are scsi. As I mentioned earlier, hooking both together with different ID did not work....
> get to the recovery console with both disks hooked up.
Yes both Disk C1 and C2 are scsi. As I mentioned earlier, hooking both together with different ID did not work....
Boy this hard drive is really playing stubborn. Are both disks the same make and model in other words are they Identical? The reason I ask is it could be the controller (the electronics on the back) have soured and if that is the case using another controller may revive the disk.
ASKER
CrazyOne: I agree that it is stubborn; and thanks for your persistance. The drives are different make. C1 (the old drive) is Fijutsu MAJ3182MP while C2 (a reformated new drive with working OS) is Seagate ST318451LW; both 18GB. I am conviced that C1 sends a command to the processor that overwhelms the processor. (I did a hot install of C1 after starting from C2...oops...and notice that the system was pegged and did not come out of it).
If you cannot boot to C2 while C1 is installed, I would begin to suspect termination problems.
If I remember correctly that adapter is LVD - do you have a terminator block on the end of the SCSI ribbon or are you using the last drive to terminate? Your best option is an active terminator at the end and all termination disabled on all devices in between.
Also, make absolutely sure that you do NOT enable term power on any of your devices attached to that adapter - it provides it's own term power.
If I remember correctly that adapter is LVD - do you have a terminator block on the end of the SCSI ribbon or are you using the last drive to terminate? Your best option is an active terminator at the end and all termination disabled on all devices in between.
Also, make absolutely sure that you do NOT enable term power on any of your devices attached to that adapter - it provides it's own term power.
ASKER
Yes the SCSI cable and Drove is Low Voltage Differential. The scsi ribbon has a external terminator block at the end. Can you plese explain the term power comment ? From the Fujitsu web site http://www.fel.fujitsu.com/support/disk/manuals/al6_ig.pdf it seems you need to enable TERMPWR (see comment 5).
I see that comment, however, your adapter supplies it's own power. Double-powering the BUS is not good for the card.
See here:
http://ask.adaptec.com/cgi-bin/adaptec_tic.cfg/php/enduser/std_adp.php?p_sid=bBRLUMEg&p_lva=&p_faqid=936&p_created=996867913&p_sp=cF9ncmlkc29ydD0mcF9yb3dfY250PTEzMCZwX3NlYXJjaF90ZXh0PTI5MTYwTiZwX3NlYXJjaF90eXBlPTMmcF9wcm9kX2x2bDE9NjYmcF9wcm9kX2x2bDI9NjgmcF9jYXRfbHZsMT1_YW55fiZwX3NvcnRfYnk9ZGZsdCZwX3BhZ2U9MQ**&p_li=
You might also want to try to update the Dell's BIOS and the Adaptec's BIOS.
See here:
http://ask.adaptec.com/cgi-bin/adaptec_tic.cfg/php/enduser/std_adp.php?p_sid=bBRLUMEg&p_lva=&p_faqid=936&p_created=996867913&p_sp=cF9ncmlkc29ydD0mcF9yb3dfY250PTEzMCZwX3NlYXJjaF90ZXh0PTI5MTYwTiZwX3NlYXJjaF90eXBlPTMmcF9wcm9kX2x2bDE9NjYmcF9wcm9kX2x2bDI9NjgmcF9jYXRfbHZsMT1_YW55fiZwX3NvcnRfYnk9ZGZsdCZwX3BhZ2U9MQ**&p_li=
You might also want to try to update the Dell's BIOS and the Adaptec's BIOS.
ASKER
I did try removing the TERMPWR enable. Did not help...the drives were not recognized in the BIOS. Also the Dell motherboard has a new bios including the adaptec Bios.
This question is still open and getting old. If any of the comment(s) above helped you please accept it as an answer or split the points who ever helped you in this question. Your attention in finalising this question is very much appreciated. Thanks in advance,
****** PLEASE DO NOT ACCEPT THIS AS AN ANSWER ********
- If you would like to close this question and have your points refunded, please post a question in community support area on https://www.experts-exchange.com/Community_Support/ giving the address of this question. Thank you
Pasha
Cleanup Volunteer
****** PLEASE DO NOT ACCEPT THIS AS AN ANSWER ********
- If you would like to close this question and have your points refunded, please post a question in community support area on https://www.experts-exchange.com/Community_Support/ giving the address of this question. Thank you
Pasha
Cleanup Volunteer
ASKER
In the end this is what I did:
a) I used disk commander commander from Winternals to recover the data
b) Substitute the disk and re-installed the data as files.
I tried disk copy but that did not work. This leads me to believe that there was a file that prevented the reboot of the system.
I had Norton Antivirus which is regularly updated so I believe it was windows or Norton Utilities created file.
Since I was not able to resolve the answer I keep the points. :-).
a) I used disk commander commander from Winternals to recover the data
b) Substitute the disk and re-installed the data as files.
I tried disk copy but that did not work. This leads me to believe that there was a file that prevented the reboot of the system.
I had Norton Antivirus which is regularly updated so I believe it was windows or Norton Utilities created file.
Since I was not able to resolve the answer I keep the points. :-).
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.