Hi.
>>I would check your initrd.img and maybe make a new one pre-loading or with
raid5.
How such image could be prepared?
I posted my autoinstall in the original post, here it is again:
<config>
<disk dev="/dev/sda" label_type="msdos" unit_of_measurement="MB">
<!--
This disk's output was brought to you by the partition tool "parted",
and by the numbers 4 and 5 and the letter Q.
-->
<part num="1" size="106.97" p_type="primary" p_name="-"
flags="boot,raid" />
<part num="2" size="2097" p_type="primary" p_name="-" flags="raid"
/>
<part num="3" size="2098" p_type="primary" p_name="-" flags="raid"
/>
<part num="4" size="495803" p_type="primary" p_name="-"
flags="raid" />
</disk>
<disk dev="/dev/sdb" label_type="msdos" unit_of_measurement="MB">
<!--
This disk's output was brought to you by the partition tool "parted",
and by the numbers 4 and 5 and the letter Q.
-->
<part num="1" size="106.97" p_type="primary" p_name="-"
flags="boot,raid" />
<part num="2" size="2097" p_type="primary" p_name="-" flags="raid"
/>
<part num="3" size="2098" p_type="primary" p_name="-" flags="raid"
/>
<part num="4" size="495803" p_type="primary" p_name="-"
flags="raid" />
</disk>
<disk dev="/dev/sdc" label_type="msdos" unit_of_measurement="MB">
<!--
This disk's output was brought to you by the partition tool "parted",
and by the numbers 4 and 5 and the letter Q.
-->
<part num="1" size="106.97" p_type="primary" p_name="-"
flags="boot,raid" />
<part num="2" size="2097" p_type="primary" p_name="-" flags="raid"
/>
<part num="3" size="2098" p_type="primary" p_name="-" flags="raid"
/>
<part num="4" size="495803" p_type="primary" p_name="-"
flags="raid" />
</disk>
<disk dev="/dev/sdd" label_type="msdos" unit_of_measurement="MB">
<!--
This disk's output was brought to you by the partition tool "parted",
and by the numbers 4 and 5 and the letter Q.
-->
<part num="1" size="106.97" p_type="primary" p_name="-"
flags="boot,raid" />
<part num="2" size="2097" p_type="primary" p_name="-" flags="raid"
/>
<part num="3" size="2098" p_type="primary" p_name="-" flags="raid"
/>
<part num="4" size="495803" p_type="primary" p_name="-"
flags="raid" />
</disk>
<raid name="/dev/md2"
raid_level="raid5"
raid_devices="4"
spare_devices="0"
persistence="yes"
layout="left-symmetric"
chunk_size="256K"
devices="/dev/sda3 /dev/sdb3 /dev/sdc3 /dev/sdd3"
/>
<raid name="/dev/md1"
raid_level="raid5"
raid_devices="4"
spare_devices="0"
persistence="yes"
layout="left-symmetric"
chunk_size="256K"
devices="/dev/sda2 /dev/sdb2 /dev/sdc2 /dev/sdd2"
/>
<raid name="/dev/md3"
raid_level="raid5"
raid_devices="4"
spare_devices="0"
persistence="yes"
layout="left-symmetric"
chunk_size="256K"
devices="/dev/sda4 /dev/sdb4 /dev/sdc4 /dev/sdd4"
/>
<raid name="/dev/md0"
raid_level="raid1"
raid_devices="4"
spare_devices="0"
persistence="yes"
devices="/dev/sda1 /dev/sdb1 /dev/sdc1 /dev/sdd1"
/>
<fsinfo line="10" real_dev="/dev/md2" mp="/" fs="ext3"
options="defaults" dump="1" pass="1" />
<fsinfo line="20" real_dev="/dev/md0" mp="/boot" fs="ext3"
options="defaults" dump="1" pass="2" />
<fsinfo line="30" real_dev="devpts" mp="/dev/pts" fs="devpts"
options="gid=5,mode=620" dump="0" pass="0" />
<fsinfo line="40" real_dev="tmpfs" mp="/dev/shm" fs="tmpfs"
options="defaults" dump="0" pass="0" />
<fsinfo line="50" real_dev="/dev/md3" mp="/media" fs="ext3"
options="defaults" dump="1" pass="2" />
<fsinfo line="60" real_dev="proc" mp="/proc" fs="proc"
options="defaults" dump="0" pass="0" />
<fsinfo line="70" real_dev="sysfs" mp="/sys" fs="sysfs"
options="defaults" dump="0" pass="0" />
<fsinfo line="80" real_dev="/dev/md1" mp="swap" fs="swap"
options="defaults" dump="0" pass="0" />
<boel devstyle="udev"/>
</config>
Regards,
Stas.
2008/3/3, Tory M Blue <[EMAIL PROTECTED]>:
>
> On Sun, Mar 2, 2008 at 2:01 PM, Stas Oskin <[EMAIL PROTECTED]> wrote:
> ---------- Forwarded message ----------
> > From: Stas Oskin <[EMAIL PROTECTED]>
> > Date: 02/03/2008 19:23
> > Subject: New version, same errors :(
> > To: sisuite-users@lists.sourceforge.net
> >
> >
> > Hi.
> >
> > I tried the latest stable version of sysimager, in hopes this has the
> RAID
> > issues resolved. No luck - the image loading to client still stops with
> > ADD_NEW_DISK.
> >
> > Attached below the dump of my autoinstall file, and the errors I'm
> > receiving. Any help would be greatly appreciated.
> >
> > Regards,
> > Stas.
> >
> > (autoinstall)
> <SNIP>
> >
> > (Only errors)
> > Load software RAID modules.
> > insmod: cannot insert
> > `/lib/modules/2.6.21-boel_v4.0.2/kernel/drivers/md/md-mod.ko': File
> exists
> > (-1): File exists
> > insmod: cannot insert
> > `/lib/modules/2.6.21-boel_v4.0.2/kernel/drivers/md/md-mod.ko': File
> exists
> > (-1): File exists
> > modprobe: module raid5 not found.
> > modprobe: failed to load module raid5
> > modprobe: module raid6 not found.
> > modprobe: failed to load module raid6
>
>
> If your making a raid5 array shouldn't the raid5 module be found and
> installed? I would check your initrd.img and maybe make a new one
> pre-loading or with raid5.
>
> That sticks out like it's an issue to me..
>
> I would also like to see your autoinstall script, would be
> interesting to see why it's complaining about the size of the swap
> device. But in my quick read, your trying to install a raid5 system
> without a raid5 module.
>
> -Tory
>
> -------------------------------------------------------------------------
> This SF.net email is sponsored by: Microsoft
> Defy all challenges. Microsoft(R) Visual Studio 2008.
> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
> _______________________________________________
> sisuite-users mailing list
> sisuite-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/sisuite-users
>
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
sisuite-users mailing list
sisuite-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/sisuite-users
