similar to: Boot from degraded sw RAID 1

I never thought I'd say this, but I think it's easier to do this with GRUB 2. Anyway I did an installation to raid1's in CentOS 6's installer, which still uses GRUB legacy. I tested removing each of the two devices and it still boots. These are the commands in its log: : Running... ['/sbin/grub-install', '--just-copy'] : Running... ['/sbin/grub',

Hi all! Doing some tests with CentOS 5.5 on a KVM virtual machine, after doing the installation, I added a second disk. But when trying to boot from it, I get the following error: --------------------------------------------------------------------- root (hd1,0) Error 21: Selected disk does not exist --------------------------------------------------------------------- The two disks are

doing that grub-install /dev/sda will give me the "corresponding BIOS device" error. But now I fixed it by doing a manual grub install. first boot with cd1 and type linux rescue at the prompt when you're at the linux prompt after detecting and mounting the partitions, do a "chroot /mnt/sysimage" then # grub --batch #grub> root (hd0,0) Filesystem type is ext2fs,

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi all! Doing some tests with CentOS 5.5 on a KVM virtual machine, after doing the installation, I added a second disk. But when trying to boot from it, I get the following error: - --------------------------------------------------------------------- root (hd1,0) Error 21: Selected disk does not exist -

Dear All, I have a K8S-MX Asus Athlon 64 Motherboard with a 754 pin 3000+ CPU, which I cam trying to install 4.1 Centos 64 bit. The problem seems to arise when installing onto Mirrored disks, I have noticed that from Centos 4 onwards it tries to rebuild the arrays as it installs which slows the whole process right down across all platforms I have tried it on. In addition, the install

Hello, I have two disks sda and sdb. One of the was broken so I have changed the broken disk with a working one. I started the server in rescue mode, and created the partional table, and added all the partitions to the software raid. *I have added the partitions to the RAID, and reboot.* # mdadm /dev/md0 --add /dev/sdb1 # mdadm /dev/md1 --add /dev/sdb2 # mdadm /dev/md2 --add /dev/sdb3 # mdadm

On 08/05/2015 10:23 AM, Chris Murphy wrote: > Nothing about hd0 or hd1 gets baked into the bootloader code. It's an > absolute reference to a physical drive at the moment in time the > command is made. Is that true? If I have a system with two disks, where device.map labels one as hd0 and the other as hd1, and I swap those numbers, the resulting boot sector will differ by one bit.

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 scheme you've posted would be sub-optimal if it does have 4096

hi! raid 1 arrays: I already have 2 systems running this same raid1 config. 1 sys has 2 120 gb 1 sys has 1 120gb and 1 200gb but matching the raid partitions this system here that is giving me fits right now has 1 250gb and 1 200gb. I tried it w/a new 250 gb for the 2nd drive but the same results. Will not boot. in druid, when I am config. the raid arrays, I always create the boot partitions

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

I have a virtual machine that had been running fine using a RAW disk image (IDE). I am in the process of converting this virtual machine to use a single LVM and virtio. (For LVM backup snapshots and easy resizing purposes (no LVM within the guest)) I create the LVM and copied all the files from the existing RAW image to an ext3 under the LVM. However, I cannot get it to boot. It has to do

I am trying to upgrade my system from 500GB drives to 1TB. I was able to partition and sync the raid devices, but I cannot get the new drive to boot. This is an old system with only IDE ports. There is an added Highpoint raid card which is used only for the two extra IDE ports. I have upgraded it with a 1TB SATA drive and an IDE-SATA adapter. I did not have any problems with the system

On 8/6/2015 4:39 PM, Chris Murphy wrote: > On Thu, Aug 6, 2015 at 2:29 PM, Bowie Bailey <Bowie_Bailey at buc.com> wrote: >> On 8/6/2015 4:21 PM, Chris Murphy wrote: >>> On Thu, Aug 6, 2015 at 2:08 PM, Bowie Bailey <Bowie_Bailey at buc.com> wrote: >>> >>>> Doing a new install on the two 1TB drives is my current plan. If that >>>>

On Thu, Aug 6, 2015 at 2:57 PM, Bowie Bailey <Bowie_Bailey at buc.com> wrote: > On 8/6/2015 4:39 PM, Chris Murphy wrote: >> >> On Thu, Aug 6, 2015 at 2:29 PM, Bowie Bailey <Bowie_Bailey at buc.com> wrote: >>> >>> On 8/6/2015 4:21 PM, Chris Murphy wrote: >>>> >>>> On Thu, Aug 6, 2015 at 2:08 PM, Bowie Bailey <Bowie_Bailey at

On Thu, Aug 6, 2015 at 2:59 PM, Gordon Messmer <gordon.messmer at gmail.com> wrote: > On 08/05/2015 10:23 AM, Chris Murphy wrote: >> >> Nothing about hd0 or hd1 gets baked into the bootloader code. It's an >> absolute reference to a physical drive at the moment in time the >> command is made. > > > Is that true? If I have a system with two disks,

On 8/6/2015 5:11 PM, Chris Murphy wrote: > On Thu, Aug 6, 2015 at 2:57 PM, Bowie Bailey <Bowie_Bailey at buc.com> wrote: >> >> Ok. I'll give that a try tomorrow. Just a couple of questions. >> >> install --stage2=/boot/grub/stage2 /grub/stage1 d (hd0,1) /grub/stage2 p >> (hd0,1)/grub/grub.conf >> >> It looks like this mixes paths relative to

I have something very strange that occurred. After updating the kernel on my host CentOS 7 Dell 2950iii I have found that one of my CentOS 7 guest VMs will no longer boot... it just stops at the grub prompt (a second VM functions just fine). I have no idea why this problem occurred and have been unable to fix it. On google I have found several suggestions as to how to repair grub but so far

--- scripts/install.py | 247 ++++++++++++++++++++++++++++++++++++++++++++++++++++ 1 files changed, 247 insertions(+), 0 deletions(-) create mode 100755 scripts/install.py diff --git a/scripts/install.py b/scripts/install.py new file mode 100755 index 0000000..ddffb53 --- /dev/null +++ b/scripts/install.py @@ -0,0 +1,247 @@ +#!/usr/bin/python +# +# install.py - configure local boot/root disk

I am using Xen 3.3 from source. My PV guest boots fine with the normal kernel and initrd options When I boot the guest with PV GRUB I only get: GNU GRUB version 0.97 (65536K lower / 0K upper memory) [ Minimal BASH-like line editing is supported. For the first word, TAB lists possible command completions. Anywhere else TAB lists the possible

created 2 partitions on laptop (/ and swap) formatted them. mounted both source and target (under /mnt on each machine) rsync -a / from desktop -> laptop (Note: OS on desktop is on sdb5. On laptop it's going to sda1) Now I need to put grub on mbr of laptop boot: linux rescue chroot /mnt/sysimage Here is my problem grub-install /dev/sda The file /boot/grub/stage1 not read correctly. Can