I've experienced something similar with existing lvm layouts... dd is
your friend ;)
Regards
Pablo
El jue, 17-04-2008 a las 11:02 +0200, Joel Andres Granados escribió:
> Lazic Aleksandar wrote:
> > Hi all,
> >
> > we use a custom layout in ks preinstall script
> >
> > ---
> > clearpart --all --initlabel
> > part raid.01 --ondisk hdb --size=... --asprimary part raid.02 --ondisk
> > hdb --size=... --asprimary part raid.03 --ondisk hdb --size=...
> > part raid.04 --ondisk hdb --size=...
> > part swap --ondisk hdb --size
> > part /data/data1 --ondisk hdb --asprimary --size 1 --grow --fstype=ext3
> > part raid.11 --ondisk hdc --size=... --asprimary part raid.12 --ondisk
> > hdc --size=... --asprimary part raid.13 --ondisk hdc --size=...
> > part raid.14 --ondisk hdc --size=...
> > part swap --ondisk hdc --size
> > part /data/data2 --ondisk hdc --asprimary --size 1 --grow --fstype=ext3
> > raid /boot --level=1 --device=md0 --fstype=ext3 raid.01 raid.11
> > raid / --level=1 --device=md1 --fstype=ext3 raid.02 raid.12
> > raid /netavis --level=1 --device=md2 --fstype=ext3 raid.03 raid.13
> > raid /var/lib/mysql --level=1 --device=md3 --fstype=ext3 raid.04 raid.14
> > ---
> >
> > After a test installation we want to make the final installation but we
> > get always the following error:
> >
> > ValueError: md1 is already in mdList.
> >
> > This is on a CentOS 5.1 installation.
> > I have try to add a:
> >
> > os.system("mdadm -S /dev/md*")
> >
> > But this wasn't th solution ;-(.
> >
> > I have also try with --useexisting but in this stage there aren't any
> > md's?!
> >
> > When I make a 'mdadm --detail -s' then I see only md1 not md0 on the
> > tty2.
> >
> > Please can anybody help me :-)
> >
> > The screenshots of the output are available under:
> >
> > http://solutions.netavis.net/Part_error01.jpg
> > http://solutions.netavis.net/Part_error02.jpg
> > http://solutions.netavis.net/Part_error03.jpg
> >
> > BR
> >
> > Aleks
> >
> > _______________________________________________
> > Kickstart-list mailing list
> > Kickstart-list@xxxxxxxxxx
> > https://www.redhat.com/mailman/listinfo/kickstart-list
>
> This is a known bug, it happens when you are trying to install over a system that had raid in the past. This issue is already solved in RHEL5.2. My advice to you is to format the HD before installation. With the previously installed system, or put a %pre section in the kickstart that does that for you.
>
> Regards
>
--
Pablo Iranzo Gómez (Pablo.Iranzo@xxxxxxxxxx)
RHCE/Global Profesional Services Consultant Spain
Phone: +34 645 01 01 49 (CET/CEST)
GnuPG KeyID: 0xFAD3CF0D
---
Dirección Comercial: C/Jose Bardasano Baos, 9, Edif. Gorbea 3, planta 3ºD, 28016 Madrid, Spain
Dirección Registrada: Red Hat S.L., C/ Velazquez 63, Madrid 28001, Spain
Inscrita en el Reg. Mercantil de Madrid – C.I.F. B82657941
Attachment:
signature.asc
Description: Esta parte del mensaje =?ISO-8859-1?Q?est=E1?= firmada digitalmente
_______________________________________________ Kickstart-list mailing list Kickstart-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/kickstart-list
