On Mon, June 9, 2014 11:46, Steve Clark wrote:
Hi,
Don't know if you saw my prior email, but we experienced this exact same problem see log excerpts below: ... Jul 31 17:05:18 wolfpac kernel: pciehp 0000:00:1c.5:pcie04: Card not present on Slot(37) Jul 31 17:05:18 wolfpac kernel: pciehp 0000:00:1c.5:pcie04: Card present on Slot(37) Jul 31 17:05:18 wolfpac kernel: device eth5 left promiscuous mode Jul 31 17:05:19 wolfpac kernel: e1000e 0000:07:00.0: PCI INT A disabled Jul 31 17:05:20 wolfpac ntpd[2726]: Deleting interface #7 eth5, 192.168.198.95#123, interface stats: received=517, sent=522, dropped=0, active_time=108106 secs Jul 31 17:05:20 wolfpac ntpd[2726]: Deleting interface #8 eth5, fe80::290:bff:fe2a:acf3#123, interface stats: received=0, sent=0, dropped=0, active_time=108039 secs ...
This would randomly happen on systems that weren't connected directly to the internet. We experienced this on multiple systems. Since we upgraded to the latest elrepo driver and added pcie_aspm=off to our kernel command line we have never experienced the issue again.
Thank you. I did get your message and I simply have not had time to test its implementation as it necessarily involves a restart of the test system. I am trying to discover if there is some way of restarting a headless server and use a specific grub entry instead of the default. I want to leave the default unchanged until I can prove that any manual changes I make do not negatively impact a system restart.
If anyone knows if this is possible and if so, how it is done, I would welcome the information.
Regards,
James B. Byrne wrote:
On Mon, June 9, 2014 11:46, Steve Clark wrote:
<snip>
implementation as it necessarily involves a restart of the test system. I am trying to discover if there is some way of restarting a headless server and use a specific grub entry instead of the default. I want to leave the default unchanged until I can prove that any manual changes I make do not negatively impact a system restart.
If anyone knows if this is possible and if so, how it is done, I would welcome the information.
That's a no-brainer: change the default= line in grub from 0 to whatever the entry number is. Note that I'm not sure what happens if you add a kernel update in there, whether the post-install scripts will increment the number so as to continue to point to the correct kernel.
On Mon, Jun 9, 2014 at 12:45 PM, m.roth@5-cent.us wrote:
James B. Byrne wrote:
On Mon, June 9, 2014 11:46, Steve Clark wrote:
<snip> > implementation as it necessarily involves a restart of the test system. I > am trying to discover if there is some way of restarting a headless server > and use a specific grub entry instead of the default. I want to leave the > default unchanged until I can prove that any manual changes I make do not > negatively impact a system restart. > > If anyone knows if this is possible and if so, how it is done, I would > welcome the information.
If you happen to be fortunate enough and have (ipmi v2) Serial over LAN configured, you can reboot and change the boot selection.
That's a no-brainer: change the default= line in grub from 0 to whatever
Not really. James wrote that he does not want to "negatively impact a system restart". If I was in his shoes, I wouldn't change the grub default boot item without serial-over-lan access, a KVM switch with network access, or "remote hands" on site. Otherwise you just changed your default boot item and it could cyclically crash and (possibly) reboot.
the entry number is. Note that I'm not sure what happens if you add a kernel update in there, whether the post-install scripts will increment the number so as to continue to point to the correct kernel.
CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
On 06/09/2014 12:52 PM, SilverTip257 wrote:
On Mon, Jun 9, 2014 at 12:45 PM, m.roth@5-cent.us wrote:
James B. Byrne wrote:
On Mon, June 9, 2014 11:46, Steve Clark wrote:
<snip> > implementation as it necessarily involves a restart of the test system. I > am trying to discover if there is some way of restarting a headless server > and use a specific grub entry instead of the default. I want to leave the > default unchanged until I can prove that any manual changes I make do not > negatively impact a system restart. > > If anyone knows if this is possible and if so, how it is done, I would > welcome the information.
If you happen to be fortunate enough and have (ipmi v2) Serial over LAN configured, you can reboot and change the boot selection.
That's a no-brainer: change the default= line in grub from 0 to whatever
Not really. James wrote that he does not want to "negatively impact a system restart". If I was in his shoes, I wouldn't change the grub default boot item without serial-over-lan access, a KVM switch with network access, or "remote hands" on site. Otherwise you just changed your default boot item and it could cyclically crash and (possibly) reboot.
the entry number is. Note that I'm not sure what happens if you add a kernel update in there, whether the post-install scripts will increment the number so as to continue to point to the correct kernel.
This show how to do a one time boot and then the next time boot the original system
https://www.gnu.org/software/grub/manual/legacy/Booting-once_002donly.html
James B. Byrne wrote:
On Mon, June 9, 2014 11:46, Steve Clark wrote:
<snip>
implementation as it necessarily involves a restart of the test system. I am trying to discover if there is some way of restarting a headless server and use a specific grub entry instead of the default. I want to leave the default unchanged until I can prove that any manual changes I make do not negatively impact a system restart.
If anyone knows if this is possible and if so, how it is done, I would welcome the information.
That's a no-brainer: change the default= line in grub from 0 to whatever the entry number is. Note that I'm not sure what happens if you add a kernel update in there, whether the post-install scripts will increment the number so as to continue to point to the correct kernel.
mark