Hi all, I''ve put down CentOS 4 from the DVD image on a machine formally running Fedora Core 2. The layout was as such: /dev/hda = 120G /dev/hdc = 120G These are raided as below /boot = 128M /dev/md0 (ext3) Rest of Disk /dev/md1 /dev/md1 is then sliced up with LVM.... The install went fine (I used the following: linux vnc vncconnect=123.456.789.0:5500 (installs graphically via VNC to my desktop machine of 123.456.789.0). I formatted ALL disks and didn''t bring anything across from the old FC2 setup. Any ideas why it would hang at the GRUB prompt? Cheers, Matt.
Two drives: A, B My best guess is that your new grub is/was installed on drive B, and you are booting from drive A. So the old grub is booting, but there aren''t any files available to boot from. -Mike Matt Bottrell wrote:> I formatted ALL disks and didn''t bring anything across from the old FC2 setup. > Any ideas why it would hang at the GRUB prompt? > > Cheers, > > Matt.
I have the same partiotioning on one server. I''ve used 4.0 RC1, because it is AMD64. It boots properly. I have installed GRUB into partition, not into mbr. /root/anaconda-ks.cfg: bootloader --location=partition --append="rhgb quiet" # The following is the partition information you requested # Note that any partitions you deleted are not expressed # here so unless you clear all partitions first, this is # not guaranteed to work #part raid.18 --size=150 --ondisk=sda --asprimary #part raid.19 --size=150 --ondisk=sdb --asprimary #part raid.21 --size=100 --grow --ondisk=sdb #part raid.20 --size=100 --grow --ondisk=sda #raid /boot --fstype ext3 --level=RAID1 raid.18 raid.19 #raid pv.23 --fstype physical volume (LVM) --level=RAID1 raid.20 raid.21 #volgroup VolGroup00 --pesize=32768 pv.23 #logvol / --fstype ext3 --name=LogVol00 --vgname=VolGroup00 --size=10240 #logvol swap --fstype swap --name=LogVol01 --vgname=VolGroup00 --size=2048 #logvol /var --fstype ext3 --name=LogVol02 --vgname=VolGroup00 --size=4096 #logvol /tmp --fstype ext3 --name=LogVol03 --vgname=VolGroup00 --size=4096 #logvol /home --fstype ext3 --name=LogVol04 --vgname=VolGroup00 --size=2048 #logvol /rest --fstype ext3 --name=LogVol05 --vgname=VolGroup00 --size=129888 -- Sincerely Ivo Panacek
It''s RAIDed... hda = primary master hdc = secondary master Disks were wiped... nothing left from the old system... I''ll have a play... I''m going to use the CD images this go instead of DVD. I''ve done this type of build on hundreds of machines many times... normally never a problem. :( Though... I guess they aint CentOS 4 though. :( On Sat, 05 Mar 2005 23:00:04 -0700, Michael Best <mbest@pendragon.org> wrote:> Two drives: A, B > > My best guess is that your new grub is/was installed on drive B, and you > are booting from drive A. > > So the old grub is booting, but there aren''t any files available to boot > from. > > -Mike > > > Matt Bottrell wrote: > > I formatted ALL disks and didn''t bring anything across from the old FC2 setup. > > Any ideas why it would hang at the GRUB prompt? > > > > Cheers, > > > > Matt. > _______________________________________________ > CentOS mailing list > CentOS@caosity.org > http://lists.caosity.org/mailman/listinfo/centos >
Thanks Ivo... looking like I might need to do a KS.... Bugger... I really wished to do the VNC install.... On Sun, 6 Mar 2005 09:31:04 +0100, Ivo Panacek <ivo.panacek@gmail.com> wrote:> I have the same partiotioning on one server. > I''ve used 4.0 RC1, because it is AMD64. > It boots properly. > > I have installed GRUB into partition, not into mbr. > > /root/anaconda-ks.cfg: > > bootloader --location=partition --append="rhgb quiet" > # The following is the partition information you requested > # Note that any partitions you deleted are not expressed > # here so unless you clear all partitions first, this is > # not guaranteed to work > #part raid.18 --size=150 --ondisk=sda --asprimary > #part raid.19 --size=150 --ondisk=sdb --asprimary > #part raid.21 --size=100 --grow --ondisk=sdb > #part raid.20 --size=100 --grow --ondisk=sda > #raid /boot --fstype ext3 --level=RAID1 raid.18 raid.19 > #raid pv.23 --fstype physical volume (LVM) --level=RAID1 raid.20 raid.21 > #volgroup VolGroup00 --pesize=32768 pv.23 > #logvol / --fstype ext3 --name=LogVol00 --vgname=VolGroup00 --size=10240 > #logvol swap --fstype swap --name=LogVol01 --vgname=VolGroup00 --size=2048 > #logvol /var --fstype ext3 --name=LogVol02 --vgname=VolGroup00 --size=4096 > #logvol /tmp --fstype ext3 --name=LogVol03 --vgname=VolGroup00 --size=4096 > #logvol /home --fstype ext3 --name=LogVol04 --vgname=VolGroup00 --size=2048 > #logvol /rest --fstype ext3 --name=LogVol05 --vgname=VolGroup00 --size=129888 > > -- > Sincerely > Ivo Panacek > _______________________________________________ > CentOS mailing list > CentOS@caosity.org > http://lists.caosity.org/mailman/listinfo/centos >
> Bugger... I really wished to do the VNC install....But you can. I do vnc + ks installs almost exclusively. I have /tftpboot/pxelinux.cfg/<hexip>: default linux label linux kernel CentOS4/i386/vmlinuz append console=tty0 load_ramdisk=1 initrd=CentOS4/i386/initrd.img vnc vncconnect=<my-linux-vnc-server>:5500 network ks=nfs:<my-install-server>:/tftpboot/CentOS4/i386/ks and in that ks I have those things which I do not want to type manually in anaconda (timezone, nfs server, ...) -- Sincerely Ivo Panacek
Matt:> Hi all, > > I''ve put down CentOS 4 from the DVD image on a machine > formally running Fedora Core 2. > > The layout was as such: > > /dev/hda = 120G > /dev/hdc = 120G > > These are raided as below > > /boot = 128M /dev/md0 (ext3) > Rest of Disk /dev/md1How do you get /boot on a raid array? Doesn''t /boot have to be on a partiton that grub can read without raid being started? -- Micha
You have it in one Micha...
I pulled /boot and / off RAID.
ie: / -> /dev/hda1
/boot -> /dev/hdc1
(pulled apart the MD0 device).
Works fine....
I wasn''t thinking... I knew better than that!
On Sun, 6 Mar 2005 14:15:58 +0200, Micha Silver <Micha@arava.co.il>
wrote:> Matt:
>
> > Hi all,
> >
> > I''ve put down CentOS 4 from the DVD image on a machine
> > formally running Fedora Core 2.
> >
> > The layout was as such:
> >
> > /dev/hda = 120G
> > /dev/hdc = 120G
> >
> > These are raided as below
> >
> > /boot = 128M /dev/md0 (ext3)
> > Rest of Disk /dev/md1
>
> How do you get /boot on a raid array? Doesn''t /boot have to be on
a partiton
> that grub can read without raid being started?
>
> --
> Micha
> _______________________________________________
> CentOS mailing list
> CentOS@caosity.org
> http://lists.caosity.org/mailman/listinfo/centos
>
Man I wish grub DID support RAID devices.... *sigh* And yes... I do understand ''why''... :-) On Sun, 6 Mar 2005 23:38:40 +1100, Matt Bottrell <mbottrell@gmail.com> wrote:> You have it in one Micha... > > I pulled /boot and / off RAID. > > ie: / -> /dev/hda1 > /boot -> /dev/hdc1 > > (pulled apart the MD0 device). > > Works fine.... > > I wasn''t thinking... I knew better than that! > > > On Sun, 6 Mar 2005 14:15:58 +0200, Micha Silver <Micha@arava.co.il> wrote: > > Matt: > > > > > Hi all, > > > > > > I''ve put down CentOS 4 from the DVD image on a machine > > > formally running Fedora Core 2. > > > > > > The layout was as such: > > > > > > /dev/hda = 120G > > > /dev/hdc = 120G > > > > > > These are raided as below > > > > > > /boot = 128M /dev/md0 (ext3) > > > Rest of Disk /dev/md1 > > > > How do you get /boot on a raid array? Doesn''t /boot have to be on a partiton > > that grub can read without raid being started? > > > > -- > > Micha > > _______________________________________________ > > CentOS mailing list > > CentOS@caosity.org > > http://lists.caosity.org/mailman/listinfo/centos > > >
> How do you get /boot on a raid array? Doesn''t /boot have to be on a partiton > that grub can read without raid being started?But it works for me! There is CentOS 4.0 RC1 for x86_64 and I will install final version when released. Relevant part of instalation kickstart is: bootloader --location=partition --append="rhgb quiet" clearpart --all --drives=sda,sdb part raid.7 --size=150 --ondisk=sda --asprimary part raid.8 --size=150 --ondisk=sdb --asprimary part raid.11 --size=100 --grow --ondisk=sdb part raid.10 --size=100 --grow --ondisk=sda raid /boot --fstype ext3 --level=RAID1 raid.7 raid.8 raid pv.12 --fstype "physical volume (LVM)" --level=RAID1 raid.10 raid.11 volgroup VolGroup00 --pesize=32768 pv.12 logvol / --fstype ext3 --name=LogVol00 --vgname=VolGroup00 --size=10240 logvol swap --fstype swap --name=LogVol01 --vgname=VolGroup00 --size=2048 logvol /var --fstype ext3 --name=LogVol02 --vgname=VolGroup00 --size=4096 logvol /tmp --fstype ext3 --name=LogVol03 --vgname=VolGroup00 --size=4096 logvol /home --fstype ext3 --name=LogVol04 --vgname=VolGroup00 --size=2048 logvol /rest --fstype ext3 --name=LogVol05 --vgname=VolGroup00 --size=100 --grow -- Sincerely Ivo Panacek
Hmm... interesting... will play a little more.... On Sun, 6 Mar 2005 14:18:07 +0100, Ivo Panacek <ivo.panacek@gmail.com> wrote:> > How do you get /boot on a raid array? Doesn''t /boot have to be on a partiton > > that grub can read without raid being started? > > But it works for me! > > There is CentOS 4.0 RC1 for x86_64 and I will install final version > when released. > > Relevant part of instalation kickstart is: > > bootloader --location=partition --append="rhgb quiet" > clearpart --all --drives=sda,sdb > > part raid.7 --size=150 --ondisk=sda --asprimary > part raid.8 --size=150 --ondisk=sdb --asprimary > part raid.11 --size=100 --grow --ondisk=sdb > part raid.10 --size=100 --grow --ondisk=sda > > raid /boot --fstype ext3 --level=RAID1 raid.7 raid.8 > raid pv.12 --fstype "physical volume (LVM)" --level=RAID1 raid.10 raid.11 > > volgroup VolGroup00 --pesize=32768 pv.12 > logvol / --fstype ext3 --name=LogVol00 --vgname=VolGroup00 --size=10240 > logvol swap --fstype swap --name=LogVol01 --vgname=VolGroup00 --size=2048 > logvol /var --fstype ext3 --name=LogVol02 --vgname=VolGroup00 --size=4096 > logvol /tmp --fstype ext3 --name=LogVol03 --vgname=VolGroup00 --size=4096 > logvol /home --fstype ext3 --name=LogVol04 --vgname=VolGroup00 --size=2048 > logvol /rest --fstype ext3 --name=LogVol05 --vgname=VolGroup00 --size=100 --grow > > -- > Sincerely > Ivo Panacek > _______________________________________________ > CentOS mailing list > CentOS@caosity.org > http://lists.caosity.org/mailman/listinfo/centos >
> > > Man I wish grub DID support RAID devices.... *sigh* > And yes... I do understand ''why''... :-)Well, I think /boot CAN be on a mirrored (Raid 1) md device, if that''s any help. -- Micha
Jerry57 (GMail)
2005-Mar-06 15:08 UTC
[Centos] Problem: Hangs at GRUB prompt after install.
Hello Micha, If I am not mistaken, you are correct, it can be on raid1, but not raid0 or raid5. I had a similar problem in that my test system wouldn''t boot after installing/upgrading to CentOS-4. Just stopped at a grub> prompt. As it turned out, device.map was missing one of my drives (I am running raid5). The minute I added the device to device.map I could then boot normally. Below are my /boot/grum/device.map and /etc/fstab files. I added "(hd2) /dev/hdi" to the device.map. LABEL=/boot equates to /dev/hde1. [root@thorn grub]# cat device.map (fd0) /dev/fd0 (hd0) /dev/hde (hd1) /dev/hdg (hd2) /dev/hdi [root@thorn grub]# cat /etc/fstab # This file is edited by fstab-sync - see ''man fstab-sync'' for details /dev/md0 / ext3 defaults 1 1 LABEL=/boot /boot ext3 defaults 1 2 none /dev/pts devpts gid=5,mode=620 0 0 none /proc proc defaults 0 0 none /dev/shm tmpfs defaults 0 0 /dev/hde2 swap swap defaults 0 0 /dev/hdd4 /media/zip auto pamconsole,exec,noauto,managed 0 0 /dev/hdc /media/cdrecorder auto pamconsole,exec,noauto,managed 0 0 /dev/fd0 /media/floppy auto pamconsole,exec,noauto,managed 0 0 Unfortunately I think this is a hardware problem on this machine as I have seen this happen before. Only appears to be a problem during installs, updates (even kernel) don''t seem to cause any problems like this. jer Sunday, March 6, 2005, 7:01:53 AM, you wrote:>> >> >> Man I wish grub DID support RAID devices.... *sigh* >> And yes... I do understand ''why''... :-)> Well, I think /boot CAN be on a mirrored (Raid 1) md device, if that''s any > help.-- USE THE BEST . . . Linux for servers . . . Macintosh for graphics . . . Palm for mobility . . . Windows for solitaire!
Matt Bottrell wrote:> It''s RAIDed... > > hda = primary master > hdc = secondary master > > Disks were wiped... nothing left from the old system... I''ll have a play... > > I''m going to use the CD images this go instead of DVD. > I''ve done this type of build on hundreds of machines many times... > normally never a problem. :( Though... I guess they aint CentOS 4 > though. :(/boot can be a raid1, but the anaconda installer only installs the MBR on one of the two devices, which I think it plain dumb, but it''s easy to copy the MBR to the other drive. Removing the partititons or otherwise "starting over" in the installer does not remove the MBR on all disks. Glad to hear it''s working. -Mike
Michael Best wrote:> /boot can be a raid1, but the anaconda installer only installs the MBR > on one of the two devices, which I think it plain dumb, but it''s easy to > copy the MBR to the other drive.Yep, I put /boot on Linux software RAID-1 on all my machines. Dell has a .pdf that explains how to install grub on the other device (actually, it''s more comprehensive than this, but that''s the relevant part to this discussion). Here''s a listmail version of that .pdf: http://lists.us.dell.com/pipermail/linux-poweredge/2003-July/014331.html johnn
On Sun, 2005-03-06 at 11:53, Michael Best wrote:> /boot can be a raid1, but the anaconda installer only installs the MBR > on one of the two devices, which I think it plain dumb, but it''s easy to > copy the MBR to the other drive.Does anyone have experience with booting a machine with a dead primary drive? I did a little testing long ago with an IBM netfinity with scsi drives back when lilo installed on both drives of a RAID1 and found that it would work if you pulled the primary drive out. The rest of the md pairs still matched up, but any single partition reference would break because the device names shifted up. However, a more common failure mode for drives is to be visible at bootup but not actually work. Also, IDE controllers tend to hang if any drive is broken, and since the drive names don''t change, won''t the root reference be wrong with a copied MBR unless you physically move the drive to replace the broken one? I guess what I''m asking is whether it is worth the trouble to install GRUB on the mirror or if you''ll have to do extra work anyway. If you have to move the drives around you might as well reboot with the install CD in rescue mode and reinstall grub anyway. -- Les Mikesell les@futuresource.com
John Tan wrote:> Yep, I put /boot on Linux software RAID-1 on all my machines. Dell has a > .pdf that explains how to install grub on the other device (actually, > it''s more comprehensive than this, but that''s the relevant part to this > discussion). Here''s a listmail version of that .pdf: > > http://lists.us.dell.com/pipermail/linux-poweredge/2003-July/014331.htmlInteresting reading. My experience with kickstart installation of grub in the mbr is that it doesn''t work for CentOS 4, at least using software raid. The relevant kickstart lines were: zerombr yes bootloader --location=mbr part raid.11 --ondisk=hda --asprimary --start 1826 --end 1950 part raid.21 --ondisk=hdd --asprimary --start 1826 --end 1950 raid /boot --fstype=ext2 --level=RAID1 --device md0 raid.11 raid.21 But at reboot, no grub. So I reboot with "linux rescue" from the CD. Using the grub commands (with the ideas from the Dell reference) and knowing that my boot directory is in /dev/hda1 (/dev/hdd1) grub> device (hd0) /dev/hda grub> (hd0,0) grub setup (hd0) This solved the problem for next reboot. What went wrong? I kept the anaconda.log file from the installation (too bad that it is not saved in the /root directory) where I read: * moving (1) to step bootloadersetup * MBR not suitable as boot device; installing to partition (...) * GRUB command root (hd0,0) install /grub/stage1 d (hd0,0) /grub/stage2 p (hd0,0)/grub/grub.conf So there are 2 questions: - why did anaconda refuse to install grub in the mbr? - why my system not boating with grub in the partition? Maybe the mbr was not zeroed? If anyone understand more... I am pretty sure there is a bug there. I can show my ks.cfg and anaconda.log if usefull. Another concern that I have with kickstart is: how can I erase (or reuse) raid1 partitions without erasing others? Seems that the questions was frequently asked (google) but never answered. Any good clue? Thanks a lot for CentOS. Anne
I think that the installer (anaconda?) is broken in respect to installing grub on ANY raid-1 disk. I''ve tried 3 times to use the GUI install to install a simple IDE-based raid-1 set-up (hda & hdc) and all three installs hung at the grub prompt. In contrast, installing a raid-1 set-up with 3.4 (or 3.3) via GUI is successful. However anaconda will ONLY write/install grub onto the IDE disk of your choice (hda or hdc). Not both, which it should!!! On my 3.4 installs, I reboot the system to make sure that the raid-1 set-up is successful booting off of your "primary" disk (in this case, hda). Then I finish it by installing grub on the second disk (hdc), like this, # grub grub> root (hd1,0) Filesystem type is ext2fs, partition type 0xfd grub> setup (hd1) Checking if "/boot/grub/stage1" exists... yes Checking if "/boot/grub/stage2" exists... yes Checking if "/boot/grub/e2fs_stage1_5" exists... yes Running "embed /boot/grub/e2fs_stage1_5 (hd1)"... 16 sectors are embedded. succeeded Running "install /boot/grub/stage1 (hd1) (hd1)1+16 p (hd1,0)/boot/grub/stage2 /boot/grub/grub.conf"... succeeded Done. grub> quit I''ve tried to search Redhat''s bugzilla about this but I couldn''t turn up anything. Note: I''m not that adept at searching their database. So, I don''t know if this is a Centos issue or a RHEL4 issue. My guess is that this is a RHEL4 issue since the GUI raid-1 install using centos-3.4 works sucessfully. Michael Anne Possoz wrote:> John Tan wrote: > > >>Yep, I put /boot on Linux software RAID-1 on all my machines. Dell has a >>.pdf that explains how to install grub on the other device (actually, >>it''s more comprehensive than this, but that''s the relevant part to this >>discussion). Here''s a listmail version of that .pdf: >> >>http://lists.us.dell.com/pipermail/linux-poweredge/2003-July/014331.html > > > Interesting reading. > > My experience with kickstart installation of grub in the mbr is that > it doesn''t work for CentOS 4, at least using software raid. > > The relevant kickstart lines were: > zerombr yes > bootloader --location=mbr > part raid.11 --ondisk=hda --asprimary --start 1826 --end 1950 > part raid.21 --ondisk=hdd --asprimary --start 1826 --end 1950 > raid /boot --fstype=ext2 --level=RAID1 --device md0 raid.11 raid.21 > > But at reboot, no grub. > > So I reboot with "linux rescue" from the CD. > Using the grub commands (with the ideas from the Dell reference) > and knowing that my boot directory is in /dev/hda1 (/dev/hdd1) > grub> device (hd0) /dev/hda > grub> (hd0,0) > grub setup (hd0) > > This solved the problem for next reboot. > > What went wrong? I kept the anaconda.log file from the installation > (too bad that it is not saved in the /root directory) where I read: > > * moving (1) to step bootloadersetup > * MBR not suitable as boot device; installing to partition > (...) > * GRUB command root (hd0,0) > install /grub/stage1 d (hd0,0) /grub/stage2 p (hd0,0)/grub/grub.conf > > So there are 2 questions: > - why did anaconda refuse to install grub in the mbr? > - why my system not boating with grub in the partition? > Maybe the mbr was not zeroed? > > If anyone understand more... I am pretty sure there is a bug there. > I can show my ks.cfg and anaconda.log if usefull. > > > Another concern that I have with kickstart is: how can I erase > (or reuse) raid1 partitions without erasing others? > > Seems that the questions was frequently asked (google) but never > answered. Any good clue? > > > Thanks a lot for CentOS. > > Anne > > _______________________________________________ > CentOS mailing list > CentOS@caosity.org > http://lists.caosity.org/mailman/listinfo/centos >
I also concur.... 3.4 seens to be successful whilst 4.0 isn''t. :( I too have looked in the Bugzilla and couldn''t note anything in respect to it. :( On Mon, 07 Mar 2005 09:06:02 -0800, Michael <addymin@pacbell.net> wrote:> I think that the installer (anaconda?) is broken in respect to > installing grub on ANY raid-1 disk. > > I''ve tried 3 times to use the GUI install to install a simple IDE-based > raid-1 set-up (hda & hdc) and all three installs hung at the grub prompt. > > In contrast, installing a raid-1 set-up with 3.4 (or 3.3) via GUI is > successful. However anaconda will ONLY write/install grub onto the IDE > disk of your choice (hda or hdc). Not both, which it should!!! > > On my 3.4 installs, I reboot the system to make sure that the raid-1 > set-up is successful booting off of your "primary" disk (in this case, > hda). Then I finish it by installing grub on the second disk (hdc), > like this, > > # grub > grub> root (hd1,0) > Filesystem type is ext2fs, partition type 0xfd > > grub> setup (hd1) > Checking if "/boot/grub/stage1" exists... yes > Checking if "/boot/grub/stage2" exists... yes > Checking if "/boot/grub/e2fs_stage1_5" exists... yes > Running "embed /boot/grub/e2fs_stage1_5 (hd1)"... 16 sectors are > embedded. > succeeded > Running "install /boot/grub/stage1 (hd1) (hd1)1+16 p > (hd1,0)/boot/grub/stage2 /boot/grub/grub.conf"... succeeded > Done. > > grub> quit > > I''ve tried to search Redhat''s bugzilla about this but I couldn''t turn up > anything. Note: I''m not that adept at searching their database. > > So, I don''t know if this is a Centos issue or a RHEL4 issue. My guess > is that this is a RHEL4 issue since the GUI raid-1 install using > centos-3.4 works sucessfully. > > Michael > > Anne Possoz wrote: > > John Tan wrote: > > > > > >>Yep, I put /boot on Linux software RAID-1 on all my machines. Dell has a > >>.pdf that explains how to install grub on the other device (actually, > >>it''s more comprehensive than this, but that''s the relevant part to this > >>discussion). Here''s a listmail version of that .pdf: > >> > >>http://lists.us.dell.com/pipermail/linux-poweredge/2003-July/014331.html > > > > > > Interesting reading. > > > > My experience with kickstart installation of grub in the mbr is that > > it doesn''t work for CentOS 4, at least using software raid. > > > > The relevant kickstart lines were: > > zerombr yes > > bootloader --location=mbr > > part raid.11 --ondisk=hda --asprimary --start 1826 --end 1950 > > part raid.21 --ondisk=hdd --asprimary --start 1826 --end 1950 > > raid /boot --fstype=ext2 --level=RAID1 --device md0 raid.11 raid.21 > > > > But at reboot, no grub. > > > > So I reboot with "linux rescue" from the CD. > > Using the grub commands (with the ideas from the Dell reference) > > and knowing that my boot directory is in /dev/hda1 (/dev/hdd1) > > grub> device (hd0) /dev/hda > > grub> (hd0,0) > > grub setup (hd0) > > > > This solved the problem for next reboot. > > > > What went wrong? I kept the anaconda.log file from the installation > > (too bad that it is not saved in the /root directory) where I read: > > > > * moving (1) to step bootloadersetup > > * MBR not suitable as boot device; installing to partition > > (...) > > * GRUB command root (hd0,0) > > install /grub/stage1 d (hd0,0) /grub/stage2 p (hd0,0)/grub/grub.conf > > > > So there are 2 questions: > > - why did anaconda refuse to install grub in the mbr? > > - why my system not boating with grub in the partition? > > Maybe the mbr was not zeroed? > > > > If anyone understand more... I am pretty sure there is a bug there. > > I can show my ks.cfg and anaconda.log if usefull. > > > > > > Another concern that I have with kickstart is: how can I erase > > (or reuse) raid1 partitions without erasing others? > > > > Seems that the questions was frequently asked (google) but never > > answered. Any good clue? > > > > > > Thanks a lot for CentOS. > > > > Anne > > > > _______________________________________________ > > CentOS mailing list > > CentOS@caosity.org > > http://lists.caosity.org/mailman/listinfo/centos > > > _______________________________________________ > CentOS mailing list > CentOS@caosity.org > http://lists.caosity.org/mailman/listinfo/centos >