Often times, on older servers, you could not boot from CD, since you were using the IDE/SCSI interface during setup, and would get a bluescreen even after loading the correct drivers.
I would create the setup floppies from CD (winnt32 /OX or /B i cant remember)
Boot from the floppies, and start setup from there, still pressing F6 and specifiying you particular SCSI boot driver.... and I will bet that will work.
I am able to boot from CD. That is how I get through the text portion of the install. Then the machine reboots, the graphical portion appears after proper BIOS, Perc, and SCSI initialization, then it hits the BSOD.
After reading this again... I see you are getting completely through text mode setup..... that leads me to believe you either have the wrong driver or a driver/firmware mismatch.
Are you running firmware version 2.7.1.3571, A09, from:
Well, I checked, and that is a SCSI CD rom. I still say create the boot floppies, boot from those, and load the driver at the appropriate time. Thats all I could see as a possible issue.
I able to boot from the CD-Rom. I am able to load the begining of Win2K from the CD-Rom to the HDD. When the machine reboots during the install, it bypasses the CD-Rom as normal and boots from the container. After the Win2K graphics come up, that's when the BSOD that states "Inaccessible Boot Device."
Since I have nothing but time, I will try the install disks.
Just because I have time, I put a Windows XP Pro cd in and it installed correctly. So I can rule out hardware and firmware problems. Driver and/or Hardware compatability still are possiblities.
What does installing a different OS prove? Absolutely nothing. Different install techniques, different drivers, etc..... the only thing you could gain from that, is that your hardware is *probably* functioning normally.
True, I will give you that the "hardware is probably funtioning normally."
That is positive, and I will work off of that.
Followed your advice and created the 4 Win2K boot disks. Found most current versions on the Web. Install of Win2k Adv Srv went fine. No problems and the system is running fine. Thanks for the suggestion.
Another member of the team said he tried the install disks. He created them from our CD. One problem and we did not try again. It may have been a bad copy or a bad disk, but it was not the same problem we were having before.
I don't know if the disks I have are the same as the ones he made. Given that another OS could be installed leads me to a driver or compatability issue that was cleared up with my version of the install disks.
Thanks for your help and time. May you have happy Holidays and a joyous New Year.
Method 8 in this article was specifically your issue. Used to happen to us all the time installing NT4 on HP netservers... Nowadays most all servers use an IDE interface for the CDROM, so this does not happen much, but on older models using SCSI CD's, it was hit or miss. Bascially booting from the SCSI bus would let you install a driver pressing F6, but it never really was getting loaded. Booting from floppy worked every time.
Hope you find a solution, I have the same intermittent problem with my Dell PE 400SC. If it does boot up and run, I get file corruption. Don't know whether it's memory or Hard disk. All tests are fine ... maybe I should return my Dell and buy an HP ...
Quino
153 Posts
0
December 18th, 2003 14:00
Often times, on older servers, you could not boot from CD, since you were using the IDE/SCSI interface during setup, and would get a bluescreen even after loading the correct drivers.
I would create the setup floppies from CD (winnt32 /OX or /B i cant remember)
Boot from the floppies, and start setup from there, still pressing F6 and specifiying you particular SCSI boot driver.... and I will bet that will work.
KStop8
6 Posts
0
December 18th, 2003 17:00
Quino
153 Posts
0
December 18th, 2003 18:00
After reading this again... I see you are getting completely through text mode setup..... that leads me to believe you either have the wrong driver or a driver/firmware mismatch.
Are you running firmware version 2.7.1.3571, A09, from:
http://support.dell.com/FileLib/Type.aspx?c=us&l=en&s=DHS&Category=0&OS=WNT5&OSL=EN&SvcTag=&SysID=PWE_PNT_P03_2400&DeviceID=1373
Are you using that driver as well, version v.2.7.1.4944 for Windows 2000?
That should work.....
What is the partition size you are installing Windows 2000 to?
Message Edited by Quino on 12-18-2003 02:28 PM
KStop8
6 Posts
0
December 20th, 2003 11:00
Sorry about the delay. I am running the latest firmware and drivers. I also ensured the BIOS is current as well.
I am putting Win2K Advanced Server on a 32 GB partition of a RAID 5 array.
Quino
153 Posts
0
December 20th, 2003 12:00
Well, I checked, and that is a SCSI CD rom. I still say create the boot floppies, boot from those, and load the driver at the appropriate time. Thats all I could see as a possible issue.
KStop8
6 Posts
0
December 21st, 2003 12:00
Why you think the problem is with the CD-Rom?
I able to boot from the CD-Rom. I am able to load the begining of Win2K from the CD-Rom to the HDD. When the machine reboots during the install, it bypasses the CD-Rom as normal and boots from the container. After the Win2K graphics come up, that's when the BSOD that states "Inaccessible Boot Device."
Since I have nothing but time, I will try the install disks.
KStop8
6 Posts
0
December 21st, 2003 19:00
Quino
153 Posts
0
December 22nd, 2003 05:00
Installing XP pro rules out nothing.
What does installing a different OS prove? Absolutely nothing. Different install techniques, different drivers, etc..... the only thing you could gain from that, is that your hardware is *probably* functioning normally.
KStop8
6 Posts
0
December 23rd, 2003 11:00
True, I will give you that the "hardware is probably funtioning normally."
That is positive, and I will work off of that.
Followed your advice and created the 4 Win2K boot disks. Found most current versions on the Web. Install of Win2k Adv Srv went fine. No problems and the system is running fine. Thanks for the suggestion.
Another member of the team said he tried the install disks. He created them from our CD. One problem and we did not try again. It may have been a bad copy or a bad disk, but it was not the same problem we were having before.
I don't know if the disks I have are the same as the ones he made. Given that another OS could be installed leads me to a driver or compatability issue that was cleared up with my version of the install disks.
Thanks for your help and time. May you have happy Holidays and a joyous New Year.
Quino
153 Posts
0
December 23rd, 2003 13:00
Glad to hear it worked.
http://support.microsoft.com/default.aspx?scid=kb;en-us;122926&Product=win2000 is a great resource.
Method 8 in this article was specifically your issue. Used to happen to us all the time installing NT4 on HP netservers... Nowadays most all servers use an IDE interface for the CDROM, so this does not happen much, but on older models using SCSI CD's, it was hit or miss. Bascially booting from the SCSI bus would let you install a driver pressing F6, but it never really was getting loaded. Booting from floppy worked every time.
GrantC007
6 Posts
0
January 15th, 2004 06:00
Hi
Hope you find a solution, I have the same intermittent problem with my Dell PE 400SC. If it does boot up and run, I get file corruption. Don't know whether it's memory or Hard disk. All tests are fine ... maybe I should return my Dell and buy an HP ...
Grant