One rare possibility could be you triggered some of the infamous UEFI bugs, that already killed some series of Samsung and Lenovo notebooks.
It works like this: UEFI specs propose a non volatile memory (nvram or eeprom) that can be accessed by the OS to store settings or debugging information. Linux actually uses this feature in case of a kernel panic: If ...
No, it is not possible to destroy the BIOS (legacy or UEFI) in this manner with that command.
Even if you somewhat managed to destroy the UEFI partition, core BIOS files will not be affected, as they reside in non-volatile memory (flash-based, mostly) socketed on your motherboard.
UEFI partition hosts additional software components (eg: debugger, driver, ...
I would use an industrial IDE SSD...(another option). It doesn't sound like you need much space, and there are SSDs made specifically for this purpose. I would NOT bother with IDE adapters and consumer-level SSDs for this application. If you do go for compact flash, again, try something that's purpose-built for the application.
There's no option here. Since the advent of the Nehalem and newer CPU's, the POST time on HP systems has grown tremendously.
I see that you're using this as a workstation. Is there any option to leave the system running and take advantage of some of the BIOS power management options?
Does it have to be a SATA SSD?
CompactFlash cards are pin-for-pin compatible with the ATA standard 1.
Which means you can use a passive electrical adapter to connect one to an IDE cable (or two!).
Would this give you enough space (I've seen some mahoosive CF cards...), I wonder.
It'd give you the reliability of solid state memory, and the oldness of ...
This turned out to be a very interesting question. There are lots of links out there on this topic but they are ambiguous in describing the difference/relationship between the two. Best description I've found of the hard drive configuration for a Windows OS is this one: http://www.ntfs.com/hard-disk-basics.htm.
It appears that MBR and Partition Table are ...
In general, I base the system performance profile on the application and intended use of the server. I typically work with:
Low-latency transaction-heavy systems.
Virtualization hosts (VMware).
Linux-based ERP servers.
The systems that require deterministic performance and low-latency are typically set to a high-performance ...
The first problem that you write in UNIX style. But the UEFI uses DOS style.
So your sequence of commands:
mount blk0 aaa
aaa: // !!! change disk in dos stile
cd EFI\debian // use backslashes
grubx64.efi // run bootloader without "./"
The second problem - you have nothing written about the disk partitioning system.
You can`t use ...
I had this problem with a Fedora 22 Live image on an USB stick created as per UEFI boot of USB sticks using
livecd-iso-to-disk --efi --format --reset-mbr Fedora-Live-Xfce-x86_64-22-3.iso /dev/sdX
Which gives a bootable GPT-organized disk with a VFAT partition.
Then I tried to myy a ZOTAC Nano CI320 using that stick and found myself in a EFI ...
This is outlined in the document you linked under the "Tuning Procedures" heading.
In order to enter the Advanced system options menu for modifying a G6 or newer HP ProLiant for a low-latency application, you need to get to the main BIOS screen by pressing F9 during POST.
Once there, type Ctrl-A. This will present an additional menu named "Service Options"...
While fun, rm -rf / can only break a havoc inside its own little jail -- and that is the partition(s) it is given. It cannot mess up disk MBR, nor it cannot magically destroy your computer.
Something else is wrong in your case.
The following Dell Whitepaper goes in depth on the differences between the different power profiles:
http://en.community.dell.com/techcenter/extras/m/white_papers/20248740 (page 20-36)
Below you can find some relevant pieces of information mentioned in the whitepaper:
Each profile simply enables/disables some BIOS features, the table below provides an ...
Having the same “PCle training error: Internal Storage Slot”. I replaced one of the two capacitors on the PCIe RAID controller that was showing signs of breakdown (expanded housing). 1500uf @ 6.3V. The system now boots and has been running for more than 24 horus.
The other answers seem to agree that wiping the BIOS is probably not your problem, so here's another thought:
My computer, when switched into UEFI mode, skips the BIOS screen completely. No manufacturer's logo, no nothing. It just tries to boot and tells me there's no bootable media (or boots).
If I remember the key to enter setup, I can whack it as the ...
Use kexec to reboot your server. This skips the pre-boot procedures entirely, and reboots into a Linux kernel at the end of the Linux shutdown process, rather than resetting the hardware and going to POST.
Unfortunately kexec is a bit cumbersome to use, so I wrote a script to make it easier to work with: kexec-reboot will allow you to choose a kernel from ...
There's a special firmware update needed to allow the use of E5-2600V2 CPUs in systems originally equipped with V1 CPUs.
You need to download it to a USB key and boot the server from it in order to upgrade your platform.
Use the HP Service Pack for ProLiant. It's a bootable DVD image, which will upgrade all the firmware on your server, including the BIOS.
If you don't have a DVD drive, or don't want to use one, you can use the HP USB Key Utility on a windows computer to create a bootable USB key from the image.
A third choice is to use the iLO console, and mount the image ...
Use a supported PCIe SSD.
Your problem is likely due to the hardware not addressing the PCIe x2 interface correctly.
To verify the situation, look in the Rom-Based Setup Utility (RBSU - press F9) bios screen and see if the card is detected. If it does show up, then your issue is at the OS level. Update your server firmware if you haven't already, just to ...
I don't know how the USB controller ended up disabled on your system... I'd love to know what happened right before you asked this question...
But you do have a couple of options to recover. Since there's no PS/2 port on this line of servers, I guess keyboard input doesn't work. Is there an OS loaded already? Are you suuuure that your keyboard/KVM switch is ...
The firmware for that server is located on HP's website.
Here's where to get it.
Don't assume that a system this old has any recent firmware updates.
Here's your BIOS download.
Here's your ILO download.
Here's your RAID controller download.
If you're asking Server Fault for advice on this, you're definitely not on the leading edge of the hardware/systems side of low-latency design. That's fine, but this is a narrow space, and engineers in the industry tend not to share information.
I've managed trading systems in multiple environments, and the tuning parameters and tweaks made in one company ...
Remove power from the server. Unplug the cables. Let the machine sit for a few minutes. Plug the cables back in and power on.
If this doesn't work, you'll want to reset NVRAM.
Take a look at the HP ProLiant DL360p Gen8 Server Maintenance and Service Guide
You have to clear the CPU errors... Try the sequence detailed here.
If you have ...
I'd trash the server. The G5 ProLiants are on the wrong side of the compatibility curve and at the point where their value has dropped too far to try to diagnose issues. The going rate for a DL380 G5 is ~$200US. They can be found for far less (chassis down to $30).
Where did you get the new motherboard? If it's from the HP parts depot (through support ...