Thank you for the confirmation about raid and profiles. I used the installed /opt/kde3/bin/kxmleditor. I find copy/pasting large blocks from vi into a mailer awkward. I did find it a bit "busy", but I cannot find the namespace configuration preference in kxmleditor, so I had to write it off as free advertising. :) Vernon Anas Nashif wrote:
Hi, Raid is not supported when you use this feature. How did you manage to get all those namespaces in the control file? What editor did you use?
Anas
H. Vernon Jones wrote:
I have two identical five-disk SCSI systems, the first installed manually, the second I am installing via autoyast with a reference profile (including partitions) generated from the first machine. The hard drives are partitioned identically, three partitions, first 512MB, second 8GB, third ~59GB. I use the first as swap on all 5, the second partition on the first two drives RAID1 under md0, with the third partition of all drives as RAID5. This leaves the second partition on drives 3,4,5 unused.
When the autoinstall tries to partition the drives, it reverses the order of the 2nd and 3rd partitions on drives 3,4,5 (sdc,d,e{2,3}), giving the large third partition to the "unused" partition ( mounted by yast2 as /data{1,2,3} ) and confusing the RAID5 set.
The software raid table is below from system #1, as is the partitioning section from the ref profile.
Any pointers would be appreciated.
Thanks,
Vernon
# autogenerated /etc/raidtab by YaST2
raiddev /dev/md0 raid-level 1 nr-raid-disks 2 nr-spare-disks 0 persistent-superblock 1 chunk-size 4 device /dev/sda2 raid-disk 0 device /dev/sdb2 raid-disk 1
raiddev /dev/md1 raid-level 5 nr-raid-disks 5 nr-spare-disks 0 persistent-superblock 1 parity-algorithm left-symmetric chunk-size 128 device /dev/sda3 raid-disk 0 device /dev/sdb3 raid-disk 1 device /dev/sdc3 raid-disk 2 device /dev/sdd3 raid-disk 3 device /dev/sde3 raid-disk 4