Bugzilla – Bug 140071
autoyast is unable to create RAID1 mirrors
Last modified: 2006-01-04 09:50:08 UTC
I am unable to create a raid mirror successfully. I have determined that the problem is that while the 2 disks get partitioned correctly, when autoyast assembles the raid mirrors, only the partitions on the second disk get assigned to each raid device! The raid_name directive is set for each pair of partitions, but for some reason the ones on /dev/sda are not assigned to the array. So the installation fails with a cryptic number as - not too suprisingly - it wants 2 partitions in each mirror. Currently my workaround is to turn on confirm, and then in the install dialog manually add the partitions on the first disk into each raid device. This works, but reduces the utility of the automated installation....... Here is my partitioning code: <drive> <device>/dev/md</device> <initialize config:type="boolean">false</initialize> <partitions config:type="list"> <partition> <filesystem config:type="symbol">ext3</filesystem> <format config:type="boolean">true</format> <fstopt>noatime,acl,user_xattr</fstopt> <mount>/</mount> <partition_id config:type="integer">131</partition_id> <partition_nr config:type="integer">0</partition_nr> <raid_options> <persistent_superblock config:type="boolean">true</persistent_superb lock> <chunk_size>4</chunk_size> <raid_type>raid1</raid_type> </raid_options> </partition> <partition> <filesystem config:type="symbol">ext3</filesystem> <format config:type="boolean">true</format> <fstopt>noatime,acl,user_xattr</fstopt> <mount>/var</mount> <partition_id config:type="integer">131</partition_id> <partition_nr config:type="integer">1</partition_nr> <raid_options> <persistent_superblock config:type="boolean">true</persistent_superb lock> <chunk_size>4</chunk_size> <raid_type>raid1</raid_type> </raid_options> </partition> <partition> <filesystem config:type="symbol">ext3</filesystem> <format config:type="boolean">true</format> <fstopt>noatime,acl,user_xattr</fstopt> <mount>/usr</mount> <partition_id config:type="integer">131</partition_id> <partition_nr config:type="integer">2</partition_nr> <raid_options> <persistent_superblock config:type="boolean">true</persistent_superblock> <chunk_size>4</chunk_size> <raid_type>raid1</raid_type> </raid_options> </partition> </partitions> <use>all</use> </drive> <drive> <device>/dev/sda</device> <initialize config:type="boolean">false</initialize> <partitions config:type="list"> <partition> <format config:type="boolean">false</format> <partition_id config:type="integer">253</partition_id> <raid_name>/dev/md0</raid_name> <raid_type>raid</raid_type> <size>6gb</size> <partition_type>primary</partition_type> </partition> <partition> <filesystem config:type="symbol">swap</filesystem> <format config:type="boolean">true</format> <mount>swap</mount> <partition_id config:type="integer">130</partition_id> <size>1gb</size> <partition_type>primary</partition_type> </partition> <partition> <format config:type="boolean">false</format> <partition_id config:type="integer">253</partition_id> <raid_name>/dev/md1</raid_name> <raid_type>raid</raid_type> <size>4gb</size> <partition_type>primary</partition_type> </partition> <partition> <format config:type="boolean">false</format> <partition_id config:type="integer">253</partition_id> <raid_name>/dev/md2</raid_name> <raid_type>raid</raid_type> <size>max</size> <partition_type>primary</partition_type> </partition> </partitions> <use>all</use> </drive> <drive> <device>/dev/sdb</device> <initialize config:type="boolean">false</initialize> <partitions config:type="list"> <partition> <format config:type="boolean">false</format> <partition_id config:type="integer">253</partition_id> <raid_name>/dev/md0</raid_name> <raid_type>raid</raid_type> <size>6gb</size> <partition_type>primary</partition_type> </partition> <partition> <filesystem config:type="symbol">swap</filesystem> <format config:type="boolean">true</format> <mount>swap</mount> <partition_id config:type="integer">130</partition_id> <size>1gb</size> <partition_type>primary</partition_type> </partition> <partition> <format config:type="boolean">false</format> <partition_id config:type="integer">253</partition_id> <raid_name>/dev/md1</raid_name> <raid_type>raid</raid_type> <size>4gb</size> <partition_type>primary</partition_type> </partition> <partition> <format config:type="boolean">false</format> <partition_id config:type="integer">253</partition_id> <raid_name>/dev/md2</raid_name> <raid_type>raid</raid_type> <size>max</size> <partition_type>primary</partition_type> </partition> </partitions> <use>all</use> </drive> I've hacked at this for a few days - is there something I'm missing or is this a bug? thanks, edgar nielsen DHAP Digital
please report bugs for "SUSE Linux 10.0 OSS" against "SUSE Linux 10.0"
Hi Edgar, there is no `openSUSE 10.0', openSUSE is a project, the product's name is still SUSE Linux. Please attach the yast logfiles of your autoyast run here.
Created attachment 61387 [details] yast logs
Created attachment 61388 [details] yast config file
OK, here are the attached yast logs as a compressed tarball. Notes: 1) When the confirmation gui came up, I manually added in the missing sda partitions to the 3 raid arrays. Also attached is my yast xml file, albeit with passwords and such modified for security..... thanks, edgar nielsen
that's a known bug and I fixed that for 10.1 already. I can provide you a patch for the installation source if you are interested. You can also try to use SUSE Linux 10.1 alpha4 or one of the next betas.
Do you mean I can use the autoyast from 10.1? I need to be using the 10.0 distribution, but I have no objection to trying to use the autoyast system from 10.1 if you think that would work. I'll take the patch in any case as that would probably be the quickest fix.... Is there any info on how to splice the 10.1 autoyast into 10.0? thanks, edgar nielsen
No, you can't use autoyast from 10.1 for 10.0. I'll attach a script to this bug. Go to the root of the installation source (that's where the "media.1" and the "suse" directory is) and let the attached script run. A file "driverupdate" should be created and hopefully that fixes your problem on i386 and x86_64
Created attachment 61938 [details] patch autoyast