Hp Proliant Safe Mide
Server is a Proliant DL320 G5. Single dual-core Xeon, 3GB of RAM. SATA drives in a mirror, boot controller is a PCI-E HP something-200 controller with 64MB of cache. (No battery, but it's only used for read.)Machine runs W2k3 x64 R2, SP2. It was working fine, and over the weekend decided to reboot itself (not sure why) and now it won't boot. It hangs on the GUI screen in normal startup, and if I boot safe mode it stops right after displaying ACPITABL.DAT.I'm guessing that acpitabl.dat is NOT the culprit, and rather something else that's in there.
But I don't know how to find out WTF is wrong since it won't even boot safe mode.I.really. don't want to have to rebuild this box, it's our tape backup machine and other utilities (Trend A/V server and other minor stuff). I can survive with it down for a day or two while I troubleshoot, but I'm at a loss.I took the drives off of the HP controller and put them on the onboard Intel SATA, and then ran the Seagate diagnostics on them (they're both 80GB HP-branded Barracudas). They test out fine.
The RAM is OK according to the HP tester and the Windows Memory Diagnostic. I'm thinking it's software, but again I'm at a loss on how to get in and fix it. I'm building a UBCD4Win right now, but I don't even know what to look at to figure out what is causing the hang once I get in. Originally posted by:But if you can't boot from a CD then you may indeed have a motherboard problem. Do you have any status LED's on the mobo that you can read? Is the system under warranty?
HP has excellent server support. I had a non-warranty mobo swap-out for a Proliant.
It cost about $1000. No status leds that are visible when it is closed, no. Nothing other than 'Generic error' LED which isn't lit.System is under warranty (next-biz day for 3 years) and I'm on the phone with HP now. We pulled the array card, and he's having me try booting from the smartstart (OS install and diags) CD. THAT isn't even working. He's thinking motherboard or PSU and I'm inclined to agree.I took the drives and threw them in another near-identical HP (celeron instead of Xeon) and they booted to the installed copy of W2k3 just fine. So it's not my drives/data, yay.editNew motherboard should be here tomorrow, I'll update the post with results.
Hi Guys,I have total of 6. 300 GB SAS 2.5 SC drives running on HP DL380 G8 server. The 6 drives are divided into 2 logical drives with logical drive 1 (RAID 1) containing Windows Server 2012 while remainder 4 are grouped to logical drive 2 (RAID 5).Recently, the disk in bay 1 failed which is part of logical drive 1 (RAID1). The Server continued to boot up for few days with one failed drive until I replaced it with new one. Now the Server is not booting to start screen after the RAID 1 has been rebuilt.
I see the Windows logo and spinning circles but right before it gets to start screen, the Server reboots again. I have tried various advanced tools built in Windows Server 2012 to make it boot up without any success. How can I make the Server boot up again normally?
Hp Proliant Boot Into Safe Mode
I realized this question was still open so I thought I would post my solution.After researching my issue online and talking with a tech support rep from whom we bought the server and have it under warranty with, none of the solutions I found that were to repair the OS to be able to boot worked. I ended up deleting the array, recreating the array and re-installing the OS. This server has 2 arrays, one holds the operating system and the second holds all the data such as the files for the hyper-v virtual machines so none of the data was lost. After reinstalling the OS I just had to reinstall a couple pieces of software and re-connect the vm's to hyper-v. It took most of the day to complete, but was a unique learning experience.mxtj - to answer your question, yes, I could boot to array management. But it would not let me delete the array so I had to use the HP Smart Start Diagnostic program in order to delete and re-create the array.
This sounds like you didn't duplicate the hard drive prior to raiding it. Tsk, tsk, tsk.I've said it before and I will say it again. You have to do a 1:1 duplicate of your original HD (that would be the one that is fully bootable and has those instructions written to it.) Raiding 2 drives doesn't typically do that.After you have duplicated the two, then you will allow the drives to raid together again.Your issue sounds like your original BOOTABLE DRIVE of your RAID is the one that went bad. Now you have replaced that one, allowed (once again) for a raid to build, but missing the boot instructions written to the hard drive.
Thus leaving you with raided drive incapable of booting. Now you have to add a boot directory to your drives.Cheers!