- Community Home
- >
- Servers and Operating Systems
- >
- HPE ProLiant
- >
- ProLiant Servers (ML,DL,SL)
- >
- Booting problems
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Forums
Discussions
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Community
Resources
Forums
Blogs
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО04-27-2004 02:57 AM
тАО04-27-2004 02:57 AM
Booting problems
I am using a COMPAQ ML350 G2 server loaded with WINDOWS NT4.0 Server,
with compaq smart 532 array controller installed on RAID level 5
I had a third party software CD (NERO-CD writing s/w) on the CD-ROM,
All of a sudden my server got hanged and i reset the server by switching off the power
and turning it on again, after that my server started giving a error message which is as follows
"Attempting to boot from C: drive"...
Please try to resolve my problem since i have so much of data.
My e-mail ID: hemee2001@yahoo.com
thank you.
regards
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО04-27-2004 03:15 AM
тАО04-27-2004 03:15 AM
Re: Booting problems
1) Have you tried to install Nero Image drive also or only the CD Writing software on same.
2) Second try to clear the NV RAM using the system configuration switch the process is you need to remove power from server. Make it on then power on server. Wait for a while then make it off then power on the server.
3) Use the smartstart cd check for the status of the array.
OR Use Win 2K bootable cd then provide controller driver then check for status of the HDD.
Check from any of the following options.
Regards,
Prashant S.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО04-27-2004 07:38 AM
тАО04-27-2004 07:38 AM
Re: Booting problems
This could be a corrupt Master Boot Record (MBR) on the NT4 disk. On older Proliants, with the F10 partition, the cursor would sit flashing at the top left of a blank screen when the MBR was corrupt (Only with NT4).
On new generation servers, G2, G3) with a Rom Based Setup Utility (RBSU) the system goes round in a loop reporting "Attempting to boot from C: drive" as in this case.
Microsoft fixed this issue in the Windows 2000 boot code.
You can build a fault tolerant bootable floppy disk to bypass the MBR on the hard disk and get the system up and running from floppy if this is indeed the problem.
Get to another NT4 system (With same Service Pack Rev) or a Windows 2000 system (laptop, desktop etc.) and insert a floppy disk. Format the floppy with FAT and copy NTLDR, NTDETECT.COM and BOOT.INI to this floppy. (You might have to change the folder views to see these top-level files).
Edit the boot.ini file on the floppy and make sure the "default=" and other values match the location of your NT4 installation. By default on an ML350G2 (with no F10 partition) it will be partition(1)\WINNT
If you are running Small Business Server, this will be \WINNT.SBS -so beware.
Once the BOOT.INI entries are correct for the faulty system, take the floppy disk to the ML350G2 and boot from it. It everything comes up OK then you know it's simply a MBR problem. This can be resolved permanently with a Microsoft utility called BCUPDATE.EXE.
It's not on their support site any longer but it is available for download from the following link (near the bottom).
http://www.autourdupc.com/Logiciel/NT4/DrvToolsNT.htm
I have e-mailed further details to the problem originator to help clarify the issue.
I hope this helps,
Brian
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО04-30-2004 05:42 AM
тАО04-30-2004 05:42 AM
Re: Booting problems
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО04-30-2004 06:05 AM
тАО04-30-2004 06:05 AM
Re: Booting problems
It was fixed with the bootable floppy disk.
The user contacted me by e-mail to inform me that it was MBR corruption as in my earlier reply.
I have asked him to update the forum but he hasn't done so yet.
Regards,
Brian