similar to: Centos 7, grub2-mkconfig, unsupported sector

m.roth at 5-cent.us wrote: > > Well, I get back from vacation, and three CentOS 7 boxes didn't come up > this morning (my manager and the other admin did the update & reboot). > On these three - but *not* another one or two, and I don't think those > others are Dells, they're supermicro's - the 327 kernel fell into the > rdosshell, I guess. I finally got

On Tue, Dec 29, 2015 at 2:43 PM, <m.roth at 5-cent.us> wrote: > m.roth at 5-cent.us wrote: >> >> Well, I get back from vacation, and three CentOS 7 boxes didn't come up >> this morning (my manager and the other admin did the update & reboot). >> On these three - but *not* another one or two, and I don't think those >> others are Dells,

Tru Huynh wrote: > On Fri, Jan 01, 2016 at 11:53:51PM +0100, Timothy Murphy wrote: >> My HP MicroServer crashes with a kernel panic >> when booted into kernel-3.10.0-327.3.1.el7.x86_64, >> but runs perfectly under kernel-3.10.0-229.20.1.el7.x86_64 . > AMD Turion64 cpu? > Could be related to: > https://bugs.centos.org/view.php?id=9860 > uptream at

On Mon, Dec 7, 2015 at 10:18 AM, Duncan Brown <centos2 at duncb.co.uk> wrote: > On 07/12/2015 14:40, Akemi Yagi wrote: >> >> This bug report: >> >> https://bugs.centos.org/view.php?id=9860 >> >> and its upstream (RH) reference: >> >> https://bugzilla.redhat.com/show_bug.cgi?id=1285235 >> >> might possibly be related to the

On Debian family of OSes Grub2 tools are prefixed with 'grub-', not with 'grub2-'. We have to detect the correct name of the tool to use it. Signed-off-by: Tomáš Golembiovský <tgolembi@redhat.com> --- v2v/linux_bootloaders.ml | 20 ++++++++++++++++++-- 1 file changed, 18 insertions(+), 2 deletions(-) diff --git a/v2v/linux_bootloaders.ml b/v2v/linux_bootloaders.ml index

On Debian family of OSes Grub2 tools are prefixed with 'grub-', not with 'grub2-'. We have to detect the correct name of the tool to use it. Signed-off-by: Tomáš Golembiovský <tgolembi@redhat.com> --- v2v/linux_bootloaders.ml | 17 +++++++++++++++-- 1 file changed, 15 insertions(+), 2 deletions(-) diff --git a/v2v/linux_bootloaders.ml b/v2v/linux_bootloaders.ml index

On Mon, Dec 7, 2015 at 4:45 AM, Johnny Hughes <johnny at centos.org> wrote: > On 12/06/2015 10:11 PM, Greg Lindahl wrote: (bit snip) >> Oh, wait: CentOS, love it or leave it. > > Correct. > > In fact, I would prefer you leave. No, I would prefer ALL of you leave. All of you who are not addressing the OP's issue should leave the thread. Just start a new thread, not

On Debian family of OSes Grub2 tools are prefixed with 'grub-', not with 'grub2-'. We have to detect the correct name of the tool to use it. Signed-off-by: Tomáš Golembiovský <tgolembi@redhat.com> --- v2v/convert_linux.ml | 21 +++++++++++++++++++-- 1 file changed, 19 insertions(+), 2 deletions(-) diff --git a/v2v/convert_linux.ml b/v2v/convert_linux.ml index

CentOS-7-x86_64-LiveKDE-1511.iso crashes on my AMD/ATI Radeon machine. I installed CentOS-7.2 by first installing CentOS-7-x86_64-LiveKDE-1503.iso, then appending GRUB_CMDLINE_LINUX_DEFAULT="initcall_blacklist=clocksource_done_booting" to /etc/default/grub and running update-grub. My question is: would there be any way, short of re-compiling the ISO, of altering the grub.cfg seen when

On Thursday, 11 August 2016 00:35:55 CEST Tomáš Golembiovský wrote: > On Debian family of OSes Grub2 tools are prefixed with 'grub-', not with > 'grub2-'. We have to detect the correct name of the tool to use it. > > Signed-off-by: Tomáš Golembiovský <tgolembi@redhat.com> > --- > v2v/convert_linux.ml | 21 +++++++++++++++++++-- > 1 file changed, 19

On Monday, 12 September 2016 13:20:47 CEST Tomáš Golembiovský wrote: > On Debian family of OSes Grub2 tools are prefixed with 'grub-', not with > 'grub2-'. We have to detect the correct name of the tool to use it. > > Signed-off-by: Tomáš Golembiovský <tgolembi@redhat.com> > --- > v2v/linux_bootloaders.ml | 20 ++++++++++++++++++-- > 1 file changed, 18

When I run "grub2-mkconfig" on my CentOS-7.1 desktop I get the warning (4 times) /usr/sbin/grub2-probe: error: cannot find a GRUB drive for /dev/block/8. Check your device.map. What exactly does this mean? My device map looks perfectly normal to me: [root at helen ~]# cat /boot/grub2/device.map (hd0) /dev/sda (hd1) /dev/sdb This makes me reluctant to boot into

As of the latest updates to anaconda and grub2 for Fedora 18, it is now possible to install with /boot as a btrfs subvolume. The way that grub2 is handling this is the "reach down" to the files it needs as if the subvolume was a directory. Is this OK? At this point I am not worried about snapshots or any other complexities. If the subvolume name is known. should grub2 be able to

I have RHEL 7 Beta installed in dual boot with CentOS 6.x. Since RHEL 7 installed GRUB2, I had problem that RHEL 7 is default boot. My personal solution was to go to /etc/grub.d and run command: mv 10_linux 31_linux grub2-mkconfig -o /boot/grub2/grub.cfg Explanation: - /etc/grub.d is where grub2 writes down config files used to create boot menu. - OS-prober creates 30_os-prober file in

Hello, I have installed the Xen 4.1.1 and a working kernel 2.6.32.43 which supports Xen on a Ubuntu Linux 10.04 LTS. However, I have never successfully booted the Hypervisor and Dom0. The screen is always black after some kernel messages rapidly go by. I think that I may pass the wrong parameters to the kernel or Hypervisor with GRUB2. Can any one share his/her working grub.cfg for GRUB2 with

On Wed, Sep 14, 2016 at 9:06 AM, Gary Stainburn <gary at ringways.co.uk> wrote: > I don't know if this additional information helps. Looking at he efibootmgr > output, is the centos entry pointing to the right place? > > Also, any idea why the update isn't being make permenant? Probably because the specified file wasn't found by the firmware on partition 1, so it

Hi, folks, Got an old HP box with a P800 Smart Array controller. The HP RAID box plugged into it's failing, and we got a new JetStor. Anyone know if we can just plug the JetStor in and set it to passthrough, or if we have to use the P800's firmware to set up the RAID, or other gotchas? I *think* we could use the RAID boxes firmware to build the RAID, but last resort would be

I installed CentOS 7 on a Shuttle X27D box (dual-core Atom 330), and so far it seems to work fine, but it didn't set up a Grub2 entry for the existing Windows XP installation in the first partition (MBR). Running os-prober generates no output. fdisk shows that the NTFS partition is still present as /dev/sda1, and still has the bootable flag set. I added a menuentry for Windows to the end of

Running CentOS 6.7, on an older HP DL580 G5. We've got a Dell 12-bay RAID box plugged into a PERC H800 (aka LSI Liberator) that we put in the HP, and that works fine. We've got a new RAID (a JetStor), and are trying to plug it in. The layout is that the Dell RAID is dual-pathed DAS. Each PERC has two DAS ports. We've got the Dell RAID in the top port of each PERC. I *thought* I could

Question 1: has anyone used preupgrade (I used it with fc 17 -> 19, and it pretty much appeared to work, but that was on a couple of worksttions)? Opinions? Question 2: is grub still supported, or is there something that *FORCES* you to use grub2? mark "grub2 must DIE!"