similar to: os-prober

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

I''m trying to run Xen on Arch Linux with UEFI boot. I followed the steps for Xen in the Arch Linux Wiki https://wiki.archlinux.org/index.php/Xen I get the following when attempting to boot: Loading Xen 4.2.2 ... WARNING: no console will be available to the OS Loading Linux linux ... Loading initial ramdisk ... Unfortunately there is no console so I cannot determine what has gone wrong,

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

This grub.cfg from a default fedora 19 Beta install caused pygrub failures.The previous pygrub commit fixed taht. So this example file added for reference. Signed-off-by: Marcel Mol <marcel@mesa.nl> --- tools/pygrub/examples/fedora-19.grub2 | 117 +++++++++++++++++++++++++++++++++ 1 files changed, 117 insertions(+), 0 deletions(-) create mode 100644 tools/pygrub/examples/fedora-19.grub2

You get these if you install Debian Wheezy as HVM and then try to convert to PV. This is Debian bug #603391. Signed-off-by: Ian Campbell <ian.campbell@citrix.com> Tested-by: Tril <tril@metapipe.net> --- tools/pygrub/examples/debian-wheezy-hvm.grub2 | 104 +++++++++++++++++++++++++ tools/pygrub/src/GrubConf.py | 6 +- 2 files changed, 109 insertions(+), 1

Confirmed this issue. To reproduce: Install a fresh Wheezy AMD64 guest under Xen 4.1 (hypervirtualized, boot from the debian-7.1.0-amd64-CD-1.iso). Use "entire disk" automatic layout for partitioning, this creates /dev/xvda1 for / and /dev/xvda5 for swap. It will create /boot/grub/grub.cfg with many references to (/dev/xvda,msdos1) which works fine when the machine is booted

On Sat, 2013-09-28 at 20:59 -0700, Tril wrote: > Backtrace from manual run of the buggy GrubConf.py: > # python /usr/lib/xen-4.1/lib/python/grub/GrubConf.py grub2 grub.cfg > WARNING:root:Unknown directive load_video > WARNING:root:Unknown directive terminal_output > WARNING:root:Unknown image directive load_video > Traceback (most recent call last): > File

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,

I''ve just built and installed xen 4.2 -rc1 (72160635df2c) (from /usr/local/xen-rc-4.2/), which seemed to go fine, along with all dependencies listed in readme (on a clean debian-squeeze base). After a few days of head bashing I can''t configure grub to boot into the xen kernel. Initially I was getting a whole load of python errors as xen installed into

Hi, folks, 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 one the three up by going back to the 228.14

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

Hello CentOS users, in the recent time I keep getting the logwatch warnings from my 2 dedicated servers running CentOS 7.4.1708. I guess because of the numerous kernel updates (because of Spectre+Meltdown) in the near past? Could someone please suggest me, which files in my /boot partition would be safe to delete? I would like to avoid the situation of having to boot the rescue partiton etc.

This should probably be a bug report for the fail2ban EPEL maintainer, the problem was introduced in version 0.9.3 >From the file /etc/fail2ban/action.d/iptables-common.conf ... # Option: lockingopt # Notes.: Option was introduced to iptables to prevent multiple instances from # running concurrently and causing irratic behavior. -w was introduced # in iptables 1.4.20, so

I'm afraid I don't know what may or may not have happened to your installation, just that this fake-start-stop-daemon thing is very likely interfering with the operation of Xen by not actually starting daemons. I suggest you try asking somewhere like the debian-users list to see if anyone there knows what this thing is or what to do about it. Ian. On Tue, 2015-06-02 at 15:22 +0200,

Hi, Thanks for your answer. During the Debian jessie installation, I had a problem at grub step. The os-prober part was stuck : grub was at 66 % (os-prober tried to browse all the VM on LVM partitions) After more than 15 minutes, os-prober seems to be stuck, so I rebooted the server. I had to boot in rescue mode, then, reinstalled grub and modified it to add

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!"

On 27/09/17 07:56, Sorin Srbu wrote: >> -----Original Message----- >> From: CentOS [mailto:centos-bounces at centos.org] On Behalf Of Phil Perry >> Sent: den 26 september 2017 21:46 >> To: centos at centos.org >> Subject: Re: [CentOS] Semi-OT: hardware: NVidia proprietary driver, C7.4 >> >> On 26/09/17 18:40, m.roth at 5-cent.us wrote: >>> This is

On Sat, Jan 23, 2016 at 01:50:42PM +0000, Timothy Murphy wrote: > If I boot into CentOS on my home server from a Live CD or USB stick > and go to Troubleshoot, it lists OS's it finds on the machine. > How does it find these OS's? > Presumably it looks through all the partitions on all the hard disks > for something that looks like an OS? > But how exactly does it identify

Jonathan Billings wrote: > On Tue, Aug 11, 2015 at 12:59:58PM -0400, m.roth at 5-cent.us wrote: >> So, since I haven't yet found where /var/log/httpd is created, what >> would >> a default package make the ownership of the directory? Does it expect it >> to be apache:root? > > Just a data point: > > $ rpm -qp --qf='[%-11{filemodes:perms}

> -----Original Message----- > From: CentOS [mailto:centos-bounces at centos.org] On Behalf Of Phil Perry > Sent: den 26 september 2017 21:46 > To: centos at centos.org > Subject: Re: [CentOS] Semi-OT: hardware: NVidia proprietary driver, C7.4 > > On 26/09/17 18:40, m.roth at 5-cent.us wrote: > > This is really frustrating. I've got a server with two K20c Tesla