perfSONAR User Q&A and Other Discussion

[Jim Warner <>]

Using CentOS 6.6, I'm getting the same behavior.

We have the dhcp server set up to provide the network info now, and that doesn't seem to work either.

While this was done as a new install, the computer and Myricom card have been working as a live CD client. And, of course, the network interface works just fine for the netinstall.

On Tue, Jan 13, 2015 at 5:34 AM, Aaron Brown <> wrote:

Hey Jim,

Could you try doing a standard CentOS install on the host? I’m curious if it’s a CentOS issue, or a perfSONAR Toolkit issue

Cheers,

Aaron

On Jan 13, 2015, at 8:26 AM, Jim Warner <> wrote:

Timely, I think.  I have this problem, too. But what I get is a hung system. This occurs right after I get congratulated for successfully installing and told to click the reboot button:

http://people.ucsc.edu/~warner/centos-boot-1.JPG

http://people.ucsc.edu/~warner/centos-boot-2.JPG

I don't see anything at the installation instructions cited in the FAQ that helps.

-jim

On Mon, Jan 12, 2015 at 3:58 PM, Jason Zurawski <> wrote:

Hey Chris;

On the matter of your NIC not holding a static address, see this FAQ item:

http://www.perfsonar.net/about/faq/#Q64

Hope this helps, thanks;

-jason

On Jan 12, 2015, at 4:50 PM, Chris Dagdigian <> wrote:

>
> Following up on my own note to avoid anyone wasting time on my older message ...
>
> Turns out perfSONAR installed mostly fine on the HP DL360 gen9.
>
> Looks like a UEFI booting or support issue with our server type. If I choose a "One time Legacy BIOS" boot and then choose "One-time boot from local hard disk" within the legacy BIOS I can actually boot into the installed system.
>
> That said, however, there are a few glitches:
>
> - Static IP and NIC device info presented during the install is not preserved; the NIC was set to "dhcp" on the node that used the FullInstall method
> - Static IP and NIC device info presented during the NetInstall is also not well handled; the NIC had all the static settings but BOOTPROTO was set to "DHCP" so it did not come up
>
>
> Regards,
> Chris
>
>> Chris Dagdigian <mailto:>
>> January 12, 2015 at 4:22 PM
>> 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