perfSONAR User Q&A and Other Discussion

[Chris Dagdigian <>]

Hi folks,

I'm starting to build the first 3 perfSONAR systems for a small 
pharmaceutical ScienceDMZ project and ran into some issues with the ISO 
based installers. I'll also be in Ohio for the upcoming workshop and am 
looking forward to meeting folks.

So far both the full install and netInstall ISOs result in non-bootable 
server systems. On one system I get a "no bootable device" boot 
complaint after I chose "use full disk" during the NetInstall process. 
On a 2nd test server I got to the grub menu after the install but the 
actual boot fails with some sort of "not found" error - this was on a 
server where I selected "replace existing Linux system" during the disk 
query phase.

It looks like the install goes fine but so much of the normal CentOS 
prompts are hidden that I can't quite tell what is going on.

Gut feeling is that the grub/bootloader stuff is going in badly or it's 
not handling a UEFI enabled boot environment well.

These are 3x HP DL360s with 8GB RAM, a bunch of 10-Gig NICs and a pair 
of 1.2TB SAS disks mirrored as a RAID0 volume via the standard HP controller

I'm somewhat comfortable digging into CentOS debugging but figured I'd 
ask the list before diving in to see if there are common issues or 
workarounds  - or if anyone knows some Anaconda magic that would decloak 
the hidden CentOS install questions that are presumably pre-populated 
via the kickstart file.

And finally any HP Proliant server tips/advice would be appreciated as 
well. I could not even boot off of the perfSONAR installer ISOs without 
triggering a "one time legacy BIOS boot" event in the HP ILO remote 
management interface. I figure there may be a number of HP config or 
BIOS settings that may need to be tweaked or tuned.

Regards,
Chris