similar to: grub issues on reinstall. [resolved-ish]

Hi all. sorry for an immediate question after subscribing, but I've managed to back myself into a frustrating corner. I've done some googling and come up dry, I figured I should try to post to the list while I dig through the archives. I have an issue with grub on a centos reinstall. my system previously had 1x 120g ide drive, 3 1tb sata drives in raid 5 md, 2 300 g in a raid 1 md,the

> > Well, i''m using here the qla2340 on several boxes. It works > > with Xen 2.0 but noch with Xen 3.0. as part of SUSE Linux 10.0: > > Interesting. If the driver really doews work flawlessly in > Xen 2, then I think the culprit has to be interrupt routeing. > > Under Xen 3, does /proc/interrupts show you''re receiving interrupts? I cannot boot with

> > Well, i''m using here the qla2340 on several boxes. It works > > with Xen 2.0 but noch with Xen 3.0. as part of SUSE Linux 10.0: > > Interesting. If the driver really doews work flawlessly in > Xen 2, then I think the culprit has to be interrupt routeing. > > Under Xen 3, does /proc/interrupts show you''re receiving interrupts? I cannot boot with

I've got two pendrives. I want to install a Debian on them. RAID1. Ok... ... After I installed it in RAID1, it works perfectly, ok! :) When I pull out one of the pendrive [good pendrive], it still boots up, hurrah :) But: ... When I pull out the other pendrive [i plug in the first one i tried] it say's: GRUB hard disk error What can I do? I already tried: grub-install /dev/sdc

Hey list, I recently started working with kickstart. It is awesome! I really had no idea how easy it would be to use. I do have one strange issue, that's really not that important, but that I'd like to figure out. I like to watch all the kernel boot messages go by in text mode by default, and when I've set up a box in the past, I've modified grub's menu.lst file to remove

I installed the xen 2.6 binary tarball on my Linux 2.6 Fedora Core x86 system and added the entry to the grub.con file. I am still not able to get it up and working. It keeps restarting itself during the boot process. I''ve managed to capture the contents of the boot at the end before it restarts: error opening /dev/console error dup2''ing fd of 0 to 0 error

Hi, I have updated the kernel to 2.4.21-27.0.2 on Centos 3.4 (was 3.3 when I did the kernel update) and have modified grub.conf to use the single CPU kernel: # grub.conf generated by anaconda # # Note that you do not have to rerun grub after making changes to this file # NOTICE: You have a /boot partition. This means that # all kernel and initrd paths are relative to /boot/, eg. #

This is irritating: I've got a server I just upgraded to 5.4, then rebooted, only to discover that it just *sits* there at the grub boot menu. I looked at grub.conf, and uncommented hiddenmenu (which should have been done long ago). It *still* sits there when I reboot. Any clues, folks? mark grub.conf: #boot=/dev/sda default=0 timeout=5 splashimage=(hd0,0)/grub/splash.xpm.gz

I've also had a few Xen systems grub entry issues. I'm not yet sure what triggers the events, but I do think there *may* be a correlation to the "/boot" part. I've found the Xen servers that have "/boot" before any of the the lines like "/boot/xen.gz" ended up missing complete grub entries. Not sure it's 100% true. Anyone else comment? Thanks PJ On

Hey, I built a 2.6.18.8-xen kernel and created the initial ram disk by following the instructions in README file in Xen source package. Then I put a entry for new kernel in /boot/grub/menu.lst (I am using CentOS 5). Here is the menu.lst: ########################################## default=1 timeout=5 splashimage=(hd0,0)/grub/splash.xpm.gz hiddenmenu title CentOS (2.6.18-8.el5) root

Hello Xen-users, I am trying to load two executables into a single VM at different addresses. The goal is to pass control to the first executable, which will treat the second executable as data. Can PV-Grub be used to accomplish this? I suspect ordinary Grub should be able to do this, outside of Xen, with a configuration like this: menu.lst: title a multiboot test root (hd0,0)

Hey, I ran a yum update and it installed a new kernel. ?? ... ?? Installed: ??? kernel.x86_64 0:2.6.32-71.29.1.el6? kernel-devel.x86_64 0:2.6.32-71.29.1.el6 but it did not modify the grub.conf file. ? #boot=/dev/sda ? default=0 ? timeout=5 ? splashimage=(hd0,0)/grub/splash.xpm.gz ? hiddenmenu ? title CentOS (2.6.32-71.el6.x86_64) ?? ?????? root (hd0,0) ?? ?????? kernel

I recently installed CentOS 5.1 on a DL71 ASI notebook. After my yum update the timeout parameter in /boot/grub/grub.conf file has no effect. It sits at the grub screen forever unless I press the enter key to select a kernel, at which point it will boot. Any help or suggestions to fix this would be much appreciated CentOS release 5.2 (Final) Kernel 2.6.18-92.1.18.el5 on an i686 # grub.conf

I have a grub.conf (below) with pci=nomsi, also /proc/cmdline and dmesg | more do not show the pci=nomsi. How can this be? there are no strange characters after quiet and before pci=nomsi. It was edited with vi. What can I do to get this parameter in my kernel boot line. Jerry ----------------- default=0 timeout=5 splashimage=(hd0,0)/boot/grub/splash.xpm.gz hiddenmenu title CentOS

Good evening all, I''ve all but finished installing Xen 2.0.5, XenLinux 2.6.10 and Debian GNU/Linux 3.0r4 into /boot on a colo box currently (and temporarily) running CentOS. I''ve chrooted into the debian install (chroot /boot /bin/bash) and was able to set everything up, install requisite packages, install xen, etc. Now I''m at the last step and I''ve run into

Hey guys, what I am trying to do is a chainload into grub2 installation in a DomU. So far I determined, PV-GRUB does not understand grub2''s grub.cfg notation. So I created a dummy menu.lst which has the needed root kernel and initrd rows and then referenced this to the DomUs config. The main intention to do this, is to be able to use kernel upgrades without touching the menu.lst for

I'm playing with software RAID and LVM in some virtual machines and I've run into an issue that I can't find a good answer to in the docs. I have the following RAID setup: md0: sda1 and sdb1, RAID 1. This is /boot md1: sda2 and sdb2, RAID 1. This is a PV for LVM. VolGroup00, this is the volume group and md1 is the only PV in it. LogVol00 is swap LogVol01 is / LogVol02 is /home

HI, We've started to see several issues with the Xen releases. Going back to basics I've used this guide https://wiki.centos.org/HowTos/Xen/Xen4QuickStart Once the install process is complete the grub.conf looks like this: default=0 timeout=5 splashimage=(hd0,0)/boot/grub/splash.xpm.gz hiddenmenu title CentOS (3.18.21-17.el6.x86_64) root (hd0,0) kernel /boot/xen.gz

I am installing Xen on a remote server. I left the other kernels on the grub.conf and made xen the default to boot from. The box didn''t boot into Xen on reboot but I''m not sure why. Here is my Xen config file: # grub.conf generated by anaconda # # Note that you do not have to rerun grub after making changes to this file # NOTICE: You have a /boot partition. This means that #

On 8/5/2015 12:34 PM, Chris Murphy wrote: > On Wed, Aug 5, 2015 at 9:12 AM, Bowie Bailey <Bowie_Bailey at buc.com> wrote: >> I am trying to upgrade my system from 500GB drives to 1TB. > I'm going to guess that there are no IDE drives that have 4096 byte > physical sectors, but it's worth confirming you don't have such a > drive because the current partition